SIST TBR 003 E1:2004/A1:2004
(Amendment)Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access
Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access
Revision of known shortcomings in the TTCN at layers 1, 2 and 3. Completion of the TTCN DIS to IS conversion. New tests will only be developed at the specific request of the ACTE/NTRAC group and then only where it can be shown that the test is technically possible and capable of being implemented in TTCN within the timescale of the work item. New Work Item supported by BAPT, Belgacom, BT, France Telecom, NTRA and OFCOM.
Digitalno omrežje z integriranimi storitvami (ISDN) - Priključitvene zahteve za terminalsko opremo za priključevanje na omrežje ISDN prek osnovnega dostopa ISDN
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST TBR 003 E1:2004/A1:2004
01-oktober-2004
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 3ULNOMXþLWYHQH]DKWHYH]D
WHUPLQDOVNRRSUHPR]DSULNOMXþHYDQMHQDRPUHåMH,6'1SUHNRVQRYQHJDGRVWRSD
,6'1
Integrated Services Digital Network (ISDN); Attachment requirements for terminal
equipment to connect to an ISDN using ISDN basic access
Ta slovenski standard je istoveten z: TBR 003/A1 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST TBR 003 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 003 E1:2004/A1:2004
---------------------- Page: 2 ----------------------
SIST TBR 003 E1:2004/A1:2004
TBR 3
AMENDMENT A1
December 1997
Source: DTA Reference: RTBR/DTA-005068
ICS: 33.020
Key words: access, basic, ISDN, rate, terminal, testing, type approval
This amendment A1 modifies
the Technical Basis for Regulation TBR 3 (1995)
Integrated Services Digital Network (ISDN);
Attachment requirements for terminal equipment to connect
to an ISDN using ISDN basic access
Urgent Technical Correction
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 003 E1:2004/A1:2004
Page 2
TBR 3: 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 003 E1:2004/A1:2004
Page 3
TBR 3: November 1995/A1: December 1997
Foreword
This amendment to Technical Basis for Regulation (TBR) has been produced by ETSI Project Digital
Terminals and Access (DTA).
This amendment should be considered as an urgent technical correction.
This 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 1, 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 003 E1:2004/A1:2004
Page 4
TBR 3: November 1995/A1: December 1997
Amendments
Page 16, subclause 3.1
Amend definition as indicated:
designated terminal: A terminal which is permitted to draw power from Power Source 1 (PS1) under both
normal and restricted power conditions in the absence of any other power source.
non-designated terminal: A terminal which is only permitted to draw power from Power Source 1 (PS1)
under normal power conditions in the absence of any other power source.
Page 37, subclause 9.2.7
Amend the line below the figure 9.7 as indicated:
The Longitudinal Conversion Loss: LCL = 20 log |E /V | dB
10 L T
The voltages V and E should be measured within the frequency range from 10 kHz up to 300 KHz
T L
1 MHz using selective test voltage measuring equipment.
Page 43, subclause 9.4.2.1.1
Amend definition as indicated:
Definition: In this inactive (powered off) state, the TE is not transmitting and cannot detect the presence
of any input signals. In the case of locally powered TEs which cannot detect the
appearance/disappearance of PS1, this state is entered when local power is not present. For locally
powered TEs that can detect PS1, state F1.0 is entered whenever loss of local power (required to support
all TEI functions) is detected, and state F1.1 is entered when the absence of power from PS1 is detected
and local power is available.No requirements are applicable for locally powered TEs for absence of PS1.
Page 45, subclause 9.4.2.3.1
Insert note and amend test as indicated:
Requirement: A TE which is powered from PS1 shall follow the procedures described in the finite state
matrix table shown in table 9.7.
A TE which is locally powered and does not have a connection detector capable of detecting the presence
of PS1 shall follow the procedures described in the finite state matrix table shown in table 9.8.
A TE which is locally powered and has a connection detector capable of detecting the presence of PS1
shall follow the procedures described in the finite state matrix table shown in table 9.9.
NOTE: Where requirements are not subject for testing in all possible states, the corresponding
behaviour is implicitly checked in the tests for other states.
Test: The test shall be conducted according to annex B, TTCN test cases AD1aF1_PS&_LP_-on,
AD1bF10_LP-on, AD1cF11_LP-off, AD1dF11_PS-on, AD2F11_CHK_T3, AD3aF2_PS_-off, AD3bF2_LP--
off, AD4F2_RX_-I0, AD5F2_RX_-I2, AD6F2_RX_-I4, AD7F2_RX_-IX, AD8F2_CHK_T3, CPF2PHAI,
AD9aF3_PS_-off, AD9bF3_LP_-off, AD10F3_PH_-AR, AD11F3_RX_-I0, AD12F3_RX_-I2, AD13F3_RX_-
I4, AD14F3_RX_-IX, AD15F3_CHK_T3, CPF3MPHIID, CPF3PHAI, AD16aF4_PS_-off, AD16bF4_LP_-
off, AD17F4_RX_-I0, AD18F4_RX_-I2, AD19F4_RX-I4, AD21F4_CHK_T3, CPF4MPHIID, CPF4PHAI,
CPF4PHDI_T3exp, CPF4Tlayer2, AD22aF5_PS_-off, AD22bF5_LP_-off, AD23F5_RX_-I0, AD24F5_RX_-
I2, AD25F5_RX_-I4, AD26F5_RX_-IX, AD27F5_CHK_T3, CPF5MPHIID, CPF5PHAI, CPF5PHDI_I0T3,
CPF5PHDI_T3expa, CPF5PHDI_T3expb, AD28aF6_PS_-off, AD28bF6_LP_-off, AD28cF6_PS-off,
AD29F6_Lostfr, AD30F6_PH_-AR, AD31F6_RX_-I0, AD32F6_RX_-I2, AD33F6_RX_-I4,
AD34F6_CHK_T3, CPF6PHAIa, CPF6PHAIb, CPF6PHDI_T3exp, CPF6PHDI_I0T3, CPF6PHDI_I0,
CPF6PHARa, CPF6PHARb, AD35aF7_PS_-off, AD35bF7_LP_-off, AD35cF7_PS-off, AD36F7_Lostfr,
AD37F7_RX_-I0, AD38F7_RX_-I2, AD39F7_RX_-I4, CPF7PHDI_I0, CPF7DIS_I2, CPF7DIS_IX,
---------------------- Page: 6 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 5
TBR 3: November 1995/A1: December 1997
AD40aF8_PS_-off, AD40bF8_LP_-off, AD41F8_PH_-AR, AD42F8_RX-I0, AD43F8_RX_-I2,
AD44F8_RX_-I4, AD45F8_RX_-IX, AD46F8_CHK_T3, CPF8MPHIIDa, CPF8MPHIIDb, CPF8PHAIb,
CPF8PHAIc, CPF8PHDI_T3exp, CPF8PHDI_I0T3, CPF8PHDI_I0b, and CPF8PHARa and CPF8PHARb.
Page 46, subclause 9.4.2.3.1, table 9.7
Amend table as indicated:
Table 9.7: Activation/deactivation Layer 1 finite state matrix table for
TEs powered from PS1
State Name Inactive Sensing Deactivated Awaiting Identifying Synchro- Activated Lost
signal input nized Framing
State Number F1 F2 F3 F4 F5 F6 F7 F8
INFO Sent INFO 0 INFO 0 INFO 0 INFO 1 INFO 0 INFO 3 INFO 3 INFO 0
Detection of PS1 F2 --- --- --- --- --- --- ---
(note 2)
Disappearance of --- F1 MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d)
PS1 for at least F1 PH-DI PH-DI PH-DI PH-DI PH-DI
500 ms (note 2) F1 F1 F1 F1 F1
PH-ACTIVATE / | ST. T3 | | --- | ---
REQUEST F4
Expiry T3 / / --- PH-DI PH-DI Not / PH-DI
F3 F3 applicable F3
Receive INFO 0 / MPH-II(c) --- --- --- PH-DI PH-DI PH-DI
(notes 4 and 5) F3 F3 F3 F3
Receive any signal / --- --- F5 --- / / ---
(note 1)
Receive INFO 2 / MPH-II(c) F6 (note 3) F6 --- F6 F6
F6
Receive INFO 4 / MPH-II(c) PH-AI (note 3) PH-AI PH-AI --- PH-AI
PH-AI S/ R T3 S/R T3 S/R T3 S/R T3
F7 F7 F7 F7 F7
Lost Framing / //// F8 F8 ---
--- No change, no action. PH-AI Primitive PH-ACTIVATE INDICATION.
| Impossible by the definition of the PH-DI Primitive PH-DEACTIVATE
Layer 1 service. INDICATION.
/ Impossible situation. ST. T3 Start timer T3.
a, b; Fn Issue primitives "a" and "b" and then go S/R T3 Stop and reset timer T3.
to state "Fn".
MPH-II(c) Primitive MPH-INFORMATION
INDICATION (connected).
MPH-II(d) Primitive MPH-INFORMATION
INDICATION (disconnected).
(continued)
---------------------- Page: 7 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 6
TBR 3: November 1995/A1: December 1997
Table 9.7 (concluded): Activation/deactivation Layer 1 finite state matrix table for
TEs powered from PS1
NOTE 1: This event reflects the case where a signal is received which is not INFO 2 or INFO 4. To
ensure that a TE takes appropriate action when receiving a signal to which it cannot
synchronize, operation of TEs should be verified where the received signal is any bit pattern
(containing at least three ZEROs in each frame interval) to which TEs conforming to
subclause 9.4.3 are not able to synchronize. In the TTCN test cases in annex B, clause B.4,
this signal is called INFO X.
NOTE 2: If more than one power feeding source can be used as declared in items 1 and 2 of annex A,
table A.1, the reaction of the TE may be different from that described. It may be necessary
then to analyse the behaviour of the TE, when tested according to annex B, clause B.4, and
when powered as declared by the supplier (see annex E, table E.2).
NOTE 3: Two responses are possible. Either:
a) the TE shall enter state F5 within 5 ms. Where this option is implemented by the
TE, the requirements associated with state F5 are applicable; or
b) on receipt of INFO 2, the TE shall enter state F6 within 5 ms; and on receipt of
INFO 4, the TE shall enter state F7 within 5 ms, stop and reset timer T3, and
send PH-AI. Where this option is implemented by the TE, the requirements
associated with state F5 are not applicable.
NOTE 4: The timer T4 shall be started when leaving state F7 or F8 upon the reception of INFO 0. The
corresponding PH-DI will be delivered to Layer 2 only, if Layer 1 does not re-enter an active
state before expiry of this timer. The value of this timer is in the range of 500 ms to 1 000 ms.
This prevents the loss of an on-going communication caused by spurious effects.
NOTE 5: INFO 0 shall be detected when 48 or more contiguous binary ONEs have been received and
the TE shall perform the actions specified in table 9.7. Conformance shall be tested with a
sinusoidal signal having a voltage of 100 mV peak-to-peak (with a frequency in the range of
2 kHz to 1 000 kHz, preferably 100 kHz). TE being in state F6 or F7 shall react on receipt of
this signal by transmitting INFO 0 within a period of time 250 μs to 25 ms.
---------------------- Page: 8 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 7
TBR 3: November 1995/A1: December 1997
Page 48, subclause 9.4.2.3.1, table 9.8
Amend table as indicated:
Table 9.8: Activation/deactivation Layer 1 finite state matrix table for locally powered
TEs unable to detect PS1
State Name Inactive Sensing Deactiv- Awaiting Identifying Synchro- Activated Lost
ated signal input nized Framing
State Number F1 F2 F3 F4 F5 F6 F7 F8
INFO Sent INFO 0 INFO 0 INFO 0 INFO 1 INFO 0 INFO 3 INFO 3 INFO 0
Loss of power / F1 MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d) MPH-II(d)
F1 PH-DI PH-DI PH-DI PH-DI PH-DI
F1 F1 F1 F1 F1
Application of F2 --- --- --- --- --- --- ---
power (note 2)
Detect PS1 No requirements apply
PH-ACTIVATE / | ST. T3 | | --- | ---
REQUEST F4
Expiry T3 / / --- PH-DI PH-DI Not / PH-DI
F3 F3 applicable F3
Receive INFO 0 / MPH-II(c) --- --- --- PH-DI PH-DI PH-DI
(notes 4 and 5) F3 F3 F3 F3
Receive any signal / --- --- F5 --- / / ---
(note 1)
Receive INFO 2 / MPH-II(c) F6 (note 3) F6 --- F6 F6
F6
Receive INFO 4 / MPH-II(c) PH-AI (note 3) PH-AI PH-AI --- PH-AI
PH-AI S/R T3 S/R T3 S/R T3 S/R T3
F7 F7 F7 F7 F7
Lost Framing / / / / / F8 F8 ---
--- No change, no action. PH-AI Primitive PH-ACTIVATE INDICATION.
| Impossible by the definition of the PH-DI Primitive PH-DEACTIVATE
Layer 1 service. INDICATION.
/ Impossible situation. ST. T3 Start timer T3.
a, b; Fn Issue primitives "a" and "b" and then
go to state "Fn".
MPH-II(c) Primitive MPH-INFORMATION S/R T3 Stop and reset timer T3.
INDICATION (connected).
MPH-II(d) Primitive MPH-INFORMATION
INDICATION (disconnected).
(continued)
---------------------- Page: 9 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 8
TBR 3: November 1995/A1: December 1997
Table 9.8 (concluded): Activation/deactivation Layer 1 finite state matrix table for locally powered
TEs unable to detect PS1
NOTE 1: This event reflects the case in which a signal is received which is not INFO 2 or INFO 4. To
ensure that a TE takes appropriate action when receiving a signal to which it cannot
synchronize, operation of TEs should be verified where the received signal is any bit pattern
(containing at least three ZEROs in each frame interval) to which TEs conforming to
subclause 9.4.3 are not able to synchronize. In the TTCN test cases in annex B, clause B.4,
this signal is called INFO X.
NOTE 2: The term power could be the full operational power or backup power. Backup power is
defined such that it is enough to hold the TEI values in memory and maintain the capability of
receiving and transmitting Layer 2 frames associated with the TEI procedures. If more than
one power feeding source can be used as declared in items 1 and 2O.1.2 of annex A,
table A.13.2, the reaction of the TE may be different from that described. It may be
necessary then to analyse the behaviour of the TE, when tested according to annex B,
clause B.4, and when powered as declared by the supplier (see annex E, table E.2).
NOTE 3: Two responses are possible. Either:
a) the TE shall enter state F5 within 5 ms. Where this option is implemented by the
TE, the requirements associated with state F5 are applicable; or
b) on receipt of INFO 2, the TE shall enter state F6 within 5 ms; and on receipt of
INFO 4, the TE shall enter state F7 within 5 ms, stop and reset timer T3, and
send PH-AI. Where this option is implemented by the TE, the requirements
associated with state F5 are not applicable.
NOTE 4: The timer T4 shall be started when leaving the states F7 or F8 upon reception of INFO 0.
The corresponding PH-DI will be delivered to Layer 2 only, if Layer 1 does not re-enter state
F7 before expiry of this timer. The value of this timer is in the range of 500 ms to 1 000 ms.
This prevents the loss of on-going communication caused by spurious effects.
NOTE 5: INFO 0 shall be detected when 48 or more contiguous binary ONEs have been received and
the TE shall perform the actions specified in table 9.8. Conformance shall be tested with a
sinusoidal signal having a voltage of 100 mV peak-to-peak (with a frequency in the range
2 kHz to 1 000 kHz, preferably 100 kHz). TE being in state F6 or F7 shall react on receipt of
this signal by transmitting INFO 0 within a period of time 250 ms to 25 ms.
Page 51, subclause 9.4.2.3.1, table 9.9
Delete table 9.9.
NOTE: Changes to table 9.8 have made table 9.9 superfluous, it is therefore deleted.
Page 56, subclause 9.5.5.1.4
Delete entire subclause.
---------------------- Page: 10 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 9
TBR 3: November 1995/A1: December 1997
Page 61, clause 10
Add the following text to the bottom of the first paragraph:
Requirement: "Before the procedures of this clause are invoked, a physical layer connection shall be
activated between the TE and the network. All layer 2 frames shall be sent to the physical layer using a
PH-DATA request primitive".
NOTE: The reception of a PH-DI primitive by layer 2 implies the discarding of all outstanding
PH-DATA requests and all LAPD frames in queue.
Test: The requirement is implicitly verified by the tests in annex B, subclause B.4.2, (Test
Group ISDN1/Cp).
Page 71, subclause 10.4.1
Amend the list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test case TC14001 and annex B
subclause B.4.42, TTCN test cases CPF4PHDI_T3exp, CPF5PHDI_I0T3, CPF5PHDI_T3expa,
CPF5PHDI_T3expb, CPF6PHDI_T3exp, CPF6PHDI_I0T3, CPF6PHDI_I0, CPF6PHARa, CPF7PHDI_I0,
CPF8PHDI_T3exp, and CPF8PHDI_I0T3, CPF8PHDI_I0b and CPF8PHARa.
Page 72, subclause 10.5.1
Add the following text to the end of the subclause:
Test: This requirement is implicitly tested by other TEI management tests.
Page 72, subclause 10.5.2
Amend the list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test case TC13014 and test preamble
PR37004, and annex B, subclause B.4.42, TTCN test cases CPF2PHAI, CPF3PHAI, CPF4PHAI,
CPF4Tlayer2, CPF5PHAI, CPF6PHAIa, CPF6PHAIb, CPF6PHARb, and CPF8PHAIb, CPF8PHAIc and
CPF8PHARb.
Page 74, subclause 10.5.4.2
Amend text as indicated:
Requirement: At the TE, automatic TEI values shall be removed by sending an MDL-REMOVE-
REQUEST primitive to the data link layer entity under the following conditions:
- on receipt from the ASP of an identity remove message;
- on receipt of an MPH-INFORMATION INDICATION (disconnected) primitive;
- on receipt of an MDL-ERROR-INDICATION primitive indicating that the data link layer entity has
assumed possible multiple-assignment of a TEI value, rather than requesting a TEI check
procedure by the transmission of an identity verify request message.
Test: The test shall be conducted according to annex C, TTCN test cases TC14021, TC14022, TC24007,
TC27031 and test preamble PR31401, and annex B, subclause B.4.4, TTCN test cases CPF3MPHIID,
CPF4MPHIID, CPF5MPHIID, CPF8MPHIIDa and CPF8MPHIIDb.
---------------------- Page: 11 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 10
TBR 3: November 1995/A1: December 1997
Page 74, 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 74, subclause 10.5.5.3
Delete entire subclause.
Page 76, subclause 10.6.1.1
Amend text as indicated:
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 77, subclause 10.6.1.2
Amend the list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test case TC24004 and TC25002, and
annex B, subclause B.4.42, TTCN test cases CPF2PHAI, CPF3PHAI, CPF4PHAI, CPF4Tlayer2,
CPF5PHAI, CPF6PHAIa, CPF6PHAIb, CPF6PHARa, CPF6PHARb, CPF8PHAIb, CPF8PHAIc, and
CPF8PHARa and CPF8PHARb.
Page 78, subclause 10.6.2
Amend list of test cases as indicated:
Test: The test shall be conducted according to annex C, TTCN test case TC27012., and annex B,
subclause B.4.4, TTCN test cases CPF4PHDI_T3exp, CPF5PHDI_I0T3, CPF5PHDI_T3expa,
CPF5PHDI_T3expb, CPF6PHDI_T3exp, CPF6PHDI_I0T3, CPF6PHDI_I0, CPF6PHARa, CPF7PHDI_I0,
CPF8PHDI_T3exp, CPF8PHDI_I0T3, CPF8PHDI_I0b, CPF8PHARa.
Page 78, subclauses 10.6.3 and 10.6.3.1
Delete entire subclauses.
Page 81, subclause 10.7.4
Delete test case TC28407 from the list of test cases.
Page 82, subclause 10.7.5.3
Delete test case TC27416 from the list of test cases.
---------------------- Page: 12 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 11
TBR 3: November 1995/A1: December 1997
Page 82, subclause 10.7.5.4
Delete test case TC27405 from the first list of test cases and delete TC27407 from the second list of test
cases.
Page 82, 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 test is specified.
Page 83, subclause 10.8
Delete test case TC28408 from the list of test cases.
Page 84, subclause 10.9.4
Delete test cases TC24007 and TC28019 from the list of test cases.
Page 158, subclause 11.4.2.2.2
Delete entire subclause.
Page 161, subclause 11.4.2.3.2
Replace existing note by:
Test:
NOTE: This requirement specifies an allowed exception to the requirements in
subclauses 11.4.2.4 and 11.4.2.5. A specific test is not required.
Page 162, subclause 11.4.3.4.2
Delete test case TC11001 from the list of test cases.
Page 165, subclause 11.4.6.1
Delete entire subclause.
Page 166, subclause 11.4.6.3
Add test cases TC11908 and TC11909 to the list of test cases.
---------------------- Page: 13 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 12
TBR 3: November 1995/A1: December 1997
Page 167, subclause 11.4.6.5.1
Amend text as indicated:
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".
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 167, subclause 11.4.6.5.2
Delete entire subclause.
Page 168, subclause 11.4.6.6.1
Amend text as indicated:
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.
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:
---------------------- Page: 14 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 13
TBR 3: November 1995/A1: December 1997
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 and , TC10718, TC11118 and TC11920.
Page 171, subclause 11.5
Amend text as indicated:
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 be is 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 173 to 176 clause A.2
Replace entire clause A.2. by the following:
A.2 Layer 1 and overvoltage requirements TBR-RT
Table A.1: Layer 1 and overvoltage conditions table
Reference Condition Status Support Comment
(Y/N)
1 Is TE mains powered? o Affects requirements in
clause 8.
2 Is TE PS1 powered? o Affects requirements in
subclauses 9.4 and
9.5.
3 Does TE have a connection detector? c1 Affects requirements in
subclause 9.4.
34 Is the TE intended to operate as a C2c1 Affects requirements in
designated TE? subclause 9.5.
45 Does the TE have a connection to earth? O Affects requirements in
subclause 9.5.
56 Is the TE intended for use only in a O Affects requirements in
physical point-to-point configuration? subclauses 9.2 and
9.4.
67 Is the TE capable of transmitting INFO 3 O Affects requirements in
within 5 ms of receipt of INFO 2 or INFO 4 subclause 9.4.
in state F4?
c1 = n/a if A1.2 else o.
c2 = o if A.1.2 else n/a.
---------------------- Page: 15 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 14
TBR 3: 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 A.1.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 Case A o1
2 9.1.2 Case B o1
3 9.1.3 Case C o1
o1. One or more options shall be chosen.
---------------------- Page: 16 ----------------------
SIST TBR 003 E1:2004/A1:2004
Page 15
TBR 3: November 1995/A1: December 1997
Table A.4: Layer 1 electrical characteristics requirements table
No. Reference TBR Requirement Status Support
(Y/N)
1 9.2.1 Bit rate m
2 9.2.2.2 Timing extraction jitter, configuration 1) m
3 9.2.2.2 Timing extraction jitter, configuration 2) c2c1
4 9.2.2.2 Timing extraction jitter, configuration 3a) c1c2
5 9.2.2.2 Timing extraction jitter, configuration 3b) c1c2
6 9.2.2.2 Timing extraction jitter, configuration 4) m
7 9.2.2.3 Total phase deviation input to output, configuration m
1)
8 9.2.2.3 Total phase deviation input to output, configuration c1c2
2)
9 9.2.2.3 Total phase deviation input to output, configuration c1c2
3a)
10 9.2.2.3 Total phase deviation input to output, configuration c1c2
3b)
11 9.2.2.3 Total phase deviation input to output, configuration m
4)
12 9.2.3 a) TE transmitter output impedance, requirement (a) m
13a 9.2.3 b) TE transmitter output impedance, requirement (b) m
at 50 ohm load
13b 9.2.3 b) TE transmitter output impedance, requirement (b) c1c2
at 400 ohm load
14 9.2.4 Pulse shape and amplitude (binary ZERO) m
15 9.2.5.1 Pulse amplitude when transmitting a high density m
pattern
16 9.2.5.2 Pulse unbalance of an isolated couple of pulses m
17 9.2.6.1 Voltage on other test loads: 400 ohm load c1c2
18 9.2.6.2 Voltage on other test loads: 5,6 ohm load c1c2
19 9.2.7 Longitudinal Conversion Loss (LCL) of the m
transmitter outputs
20 9.2.8 TE receiver input impedance m
21 9.2.9 (1) Receiver sensitivity - Noise and distortion m
immunity, configuration (1)
22 9.2.9 (2) Receiver sensitivity - Noise and distortion c1c2
immunity, configuration (2)
23 9.2.9 (3a) Receiver sensitivity - Noise and distortion c1c2
immunity, configuration (3a)
24 9.2.9 (3b) Receiver sensitivity - Noise and distortion c1c2
immunity, configuration (3b)
25 9.2.9 (4) Receiver sensitivity - Noise and distortion m
immunity, configuration (4)
26 9.2.10 Longitudinal Conversion Loss (LCL) of the m
receiver inputs
c1c2 = n/a if A.1.56 else m.
Table A.5: Layer 1 functional characteristics requirements table
No. Reference TBR Re
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.