SIST TBR 004 E1:2004
(Main)Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN primary rate access
- Abstract
Candidate NET5 (prETS 300 156) needs to be revised according to the according to the guidance in the CTR Handbook to produce an ETS as a Candidate CTR. It may be necessary to include those Clauses of other ETSs that are called up by Candidate NET 5
- Status
- Published
- Publication Date
- 30-Sep-2004
- Technical Committee
- SPS - Signalling protocols and switching
- Current Stage
- 6060 - National Implementation/Publication (Adopted Project)
- Start Date
- 01-Oct-2004
- Due Date
- 01-Oct-2004
- Completion Date
- 01-Oct-2004
- Mandate
- T-237D
SIST TBR 004 E1:2004 is the Slovenian version of TBR 004 Edition 1 from ETSI. It specifies the technical attachment requirements for terminal equipment that connects to an Integrated Services Digital Network (ISDN) using ISDN primary rate access. In practice, it tells manufacturers, test labs and conformity assessors what the interface must do at Layers 1, 2 and 3 so the terminal can work on a primary-rate ISDN line.
What does SIST TBR 004 E1:2004 specify?
SIST TBR 004 E1:2004 covers the technical requirements for terminal equipment intended to connect to an ISDN via ISDN primary rate access. Clause 1 gives the scope, clauses 2 to 11 cover references, definitions, general rules, primitives, safety, EMC, overvoltage protection, Layer 1, Layer 2, Layer 3 and TE timers.
The document is organized so that the core protocol requirements are followed by annexes for guidance and testing. Clauses 6 and 7 state that safety and Electro-Magnetic Compatibility (EMC) requirements are not specified under this TBR; those areas are handled elsewhere.
| Annex | What it covers |
|---|---|
| Annex A | Guidance for completing the TBR-RT, including Layer 1, overvoltage, Layer 2 and Layer 3 parts |
| Annex B | Layer 1 test material, including measurements, setup, frame alignment and CRC processing |
| Annex C | Layer 2 test case selection and Layer 2 test suite |
| Annex D | Layer 3 test case selection and Layer 3 test suite |
| Annex E | PIXIT guidance and proformas for Layer 1, Layer 2 and Layer 3 |
| Annex F | Changes with respect to the named base standards |
| Annex G | Basic telecommunication services and supplementary services |
What are the key requirements of SIST TBR 004 E1:2004?
SIST TBR 004 E1:2004 sets the attachment behaviour for the physical interface, data link procedures and call control procedures of ISDN terminal equipment. The main practical point is that a terminal is not judged only by signalling format - it must also meet electrical limits, manage link states correctly and exchange valid call-control messages.
General applicability and scope control
Clause 4 says each requirement applies either to all terminal equipment in scope or only to a stated subset. That matters because implementers and test labs must check the applicability of each clause before deciding what to test or declare.
Clauses 6 and 7 also matter operationally: safety and EMC are outside this TBR. A product still has to meet the relevant legal or product-specific obligations, but those are not defined here.
Clause 5 primitives and interface language
Clause 5 defines the primitives used between adjacent layers and between a layer and layer management, with names such as DL-ESTABLISH, DL-RELEASE, DL-DATA, PH-ACTIVATE and PH-DEACTIVATE. It also defines primitive types such as REQUEST, INDICATION, RESPONSE and CONFIRM, plus parameters such as Priority indicator and Message unit.
In practice, this gives a common control vocabulary for the Layer 2 and Layer 1 procedures. Designers and test writers use these primitive names to describe exactly when the terminal should request, indicate, confirm or respond to a network event.
Clause 8 overvoltage protection
Clause 8 sets overvoltage protection requirements for impulse transfer from mains in common mode and transverse mode, and for conversion of common mode to transverse mode. Annex A shows that these requirements are selected according to the TBR-RT and whether the terminal equipment is mains powered.
That matters for hardware design and verification. If the terminal has mains power, the overvoltage path has to be considered during compliance planning and test selection.
Clause 9 Layer 1 requirements
Clause 9 covers the physical interface in detail. It includes hardwired and alternative connection means, output-port requirements such as waveform shape, impedance towards ground, clock accuracy, output jitter and line coding, and input-port requirements such as return loss, immunity to attenuation and reflections, jitter tolerance, tolerable longitudinal voltage and impedance towards ground.
Clause 9 also defines the frame structure, TS0 allocation, CRC-4 multiframe handling, sub-multiframes, timeslot assignment and maintenance functions. For the reader, this means the terminal must transmit and receive clean primary-rate signals and must recover and maintain frame alignment correctly, not just pass bits.
Clause 10 Layer 2 requirements
Clause 10 defines the peer-to-peer frame format and field coding for the data link layer, including the address field, control field, information field, transparency rules and Frame Check Sequence (FCS). It also defines frame types such as I, SABME, DISC, UI, RR, REJ, RNR, UA and DM.
The clause goes on to define Terminal Endpoint Identifier (TEI) management, multiple frame operation, retransmission behaviour, exception handling and system parameters such as timers and counters. In practice, this is what makes the terminal able to set up, maintain, recover and clear its data link correctly on a shared ISDN access.
Clause 11 Layer 3 requirements
Clause 11 covers call control. It defines user-side and network-side call states, the functional meaning of messages such as ALERTING, CALL PROCEEDING, CONNECT, DISCONNECT, RELEASE, STATUS and SETUP, and the coding of information elements such as Bearer capability, Called party number, Cause, Channel identification, High Layer Compatibility and Low Layer Compatibility.
It also defines circuit-switched call control procedures for call establishment, call clearing, call rearrangements, collisions, error handling, user notification, restart and TE timers. For a buyer or integrator, this is the part that tells whether the terminal can place, accept, clear and recover calls in the way the ISDN network expects.
Annexes as the conformance bridge
Annexes B, C and D turn the protocol requirements into test material. Annex B gives Layer 1 tests, Annex C gives Layer 2 test cases, and Annex D gives Layer 3 test cases. That matters because implementers usually need both the requirement text and the associated verification path.
What terms does SIST TBR 004 E1:2004 define?
- terminal equipment (TE) - The equipment that connects to the ISDN access and is the subject of the attachment requirements.
- network termination (NT) - The network-side termination referenced in the Layer 1 definition of frame alignment and interface behaviour.
- frame alignment - The function that lets the TE or NT recover the time-division multiplexed channels.
- Terminal Endpoint Identifier (TEI) - The identifier used in Layer 2 management to distinguish terminal endpoints on the access.
- Service Access Point Identifier (SAPI) - The Layer 2 address field value that identifies the service access point.
- Frame Check Sequence (FCS) - The frame field used for error detection in Layer 2 frames.
- Cyclic Redundancy Check (CRC) - The error-checking method used for Layer 1 multiframe processing and monitoring.
Who uses SIST TBR 004 E1:2004?
SIST TBR 004 E1:2004 is used by manufacturers of ISDN terminal equipment, especially equipment designed for primary rate access. It is also used by interface and protocol engineers who need to implement Layer 1, Layer 2 and Layer 3 behaviour consistently.
Test laboratories and conformity assessment teams use it to build verification plans, select test cases and judge results against the defined procedures. Quality managers, buyers and network-side technical teams use it when they need to specify or review ISDN-compatible terminal behaviour before deployment.
Which standards are used with SIST TBR 004 E1:2004?
| Standard or recommendation | What it contributes |
|---|---|
| ETS 300 011 | Base material for Layer 1 and related changes listed in Annex F |
| ETS 300 125 | Base material for Layer 2, including primitive definitions referenced in Clause 5 |
| ETS 300 102-1 | Base material for Layer 3 message and call-control behaviour |
| I-ETS 300 313 | Earlier Layer 2 material referenced in Annex F changes |
| I-ETS 300 322 | Earlier Layer 2 and Layer 3 test-related material referenced in Annex F changes |
| ETS 300 196 | Coding and use of the Notification indicator for supplementary services |
| CCITT Recommendations V.110 and X.30 | Options and coding related to bearer capability, rate adaptation and modem-related behaviour |
| Recommendation I.460 | E-bit-based rate indication mentioned in bearer capability coding |
These references matter because they provide the detailed foundation that this TBR reuses or adapts. A reader working on implementation or testing should treat them as the companion documents that explain the underlying Layer 1, Layer 2 and Layer 3 behaviours.
What does the SIST TBR 004 E1:2004 document contain?
SIST TBR 004 E1:2004 contains many tables, figures and procedures for ISDN primary rate access behaviour. Clause 9 includes signal, frame and CRC material for Layer 1, while Clause 10 includes frame formats, state handling, TEI management and retransmission procedures for Layer 2.
Clause 11 contains message coding and call-control procedures, including the detailed structure of information elements such as Bearer capability, Called party number, Cause, Channel identification, High Layer Compatibility and Low Layer Compatibility. It also covers error handling and restart behaviour.
Annex B provides laboratory test conditions and measurement methods for output and input ports, jitter, return loss, longitudinal voltage and frame alignment. Annexes C and D give scripted test suites for Layer 2 and Layer 3, and Annex E supplies PIXIT guidance and proformas for capturing implementation-specific details before testing.
Get Certified
Connect with accredited certification bodies for this standard

ANCE
Mexican certification and testing association.

Intertek Slovenia
Intertek testing, inspection, and certification services in Slovenia.
LNE (Laboratoire National de Métrologie et d'Essais)
French national laboratory for metrology and testing.
Sponsored listings
Frequently Asked Questions
SIST TBR 004 E1:2004 is a standardization document published by the Slovenian Institute for Standardization (SIST). Its full title is "Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN primary rate access". This standard covers: Candidate NET5 (prETS 300 156) needs to be revised according to the according to the guidance in the CTR Handbook to produce an ETS as a Candidate CTR. It may be necessary to include those Clauses of other ETSs that are called up by Candidate NET 5
Candidate NET5 (prETS 300 156) needs to be revised according to the according to the guidance in the CTR Handbook to produce an ETS as a Candidate CTR. It may be necessary to include those Clauses of other ETSs that are called up by Candidate NET 5
SIST TBR 004 E1:2004 is classified under the following ICS (International Classification for Standards) categories: 33.080 - Integrated Services Digital Network (ISDN). The ICS classification helps identify the subject area and facilitates finding related standards.
SIST TBR 004 E1:2004 is associated with the following European legislation: Standardization Mandates: T-237D. When a standard is cited in the Official Journal of the European Union, products manufactured in conformity with it benefit from a presumption of conformity with the essential requirements of the corresponding EU directive or regulation.
SIST TBR 004 E1:2004 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
SLOVENSKI STANDARD
01-oktober-2004
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'13ULNOMXþ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 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
TECHNICAL TBR 4
BASIS for November 1995
REGULATION
Source: ETSI TC-BTC Reference: DTBR/BTC-02035
ICS: 33.080
ISDN, terminal equipment, primary rate access
Key words:
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
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 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 1995. All rights reserved.
New presentation - see History box
Page 2
TBR 4: November 1995
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 3
TBR 4: November 1995
Contents
Foreword .12
The machine processable ATS .12
1 Scope .14
2 Normative references.14
3 Definitions, symbols and abbreviations.15
3.1 Definitions .15
3.2 Abbreviations .17
4 General.18
5 Definitions of primitives .19
5.1 Generic names .19
5.1.1 DL-ESTABLISH.19
5.1.2 DL-RELEASE .19
5.1.3 DL-DATA.20
5.1.4 DL-UNIT DATA.20
5.1.5 MDL-ASSIGN .20
5.1.6 MDL-REMOVE .20
5.1.7 MDL-ERROR.20
5.1.8 MDL-UNIT DATA.20
5.1.9 PH-DATA.20
5.1.10 PH-ACTIVATE.21
5.1.11 PH-DEACTIVATE.21
5.2 Primitive types.21
5.2.1 REQUEST.21
5.2.2 INDICATION.21
5.2.3 RESPONSE .21
5.2.4 CONFIRM.21
5.3 Parameter definition.21
5.3.1 Priority indicator.21
5.3.2 Message unit .22
6 Safety requirements .23
7 Electro-Magnetic Compatibility (EMC) requirements .23
8 Overvoltage protection requirements .23
8.1 Impulse transfer from mains, common mode.23
8.2 Impulse transfer from mains, transverse mode.23
8.3 Conversion of common mode to transverse mode.23
9 Layer 1 requirements .23
9.1 Physical characteristics.23
9.1.1 Hardwired connection.24
9.1.2 Alternative means of connection .24
9.2 Specification at the output port .25
9.2.1 Waveform shape.25
9.2.2 Impedance towards ground.26
9.2.3 Clock accuracy.27
9.2.4 Output jitter.27
9.2.5 Line coding .27
9.3 Specification at the input port.28
Page 4
TBR 4: November 1995
9.3.1 Return loss. 28
9.3.2 Immunity to attenuation and reflections. 28
9.3.3 Jitter tolerance . 28
9.3.4 Tolerable longitudinal voltage . 29
9.3.5 Impedance towards ground . 29
9.4 Frame structure. 30
9.4.1 Frame length. 30
9.4.2 Number of bits per timeslot. 30
9.4.3 Number of timeslots per frame . 30
9.4.4 Assignment of bits in Time-Slot 0 (TS0). 30
9.4.5 Allocation of bits 1 to 8 of the frame for a complete multiframe . 30
9.4.6 Sub-Multiframes (SMF) . 31
9.4.7 Cyclic Redundancy Check (CRC). 31
9.4.7.1 Multiplication/division process. 31
9.4.7.2 Encoding procedure. 31
9.4.7.3 Decoding procedure. 32
9.4.8 Use of bit 1 in 2 048 kbit/s CRC-4 multiframe . 32
9.4.9 Timeslot assignment. 32
9.5 Operational functions .32
9.5.1 Definition of signals at the interface. 33
9.5.2 Layer 1 states at the TE. 33
9.5.3 State tables. 34
9.5.4 Maintenance at the interface . 35
9.5.4.1 Definitions of maintenance signals . 35
9.5.4.2 Maintenance functions . 36
9.5.4.2.1 Anomalies and defect detection. 36
9.5.4.2.2 Detection of defect indication signals. 36
9.5.4.2.3 Consequent actions . 36
9.5.5 Frame alignment and CRC procedures at 2 048 kbit/s interface . 37
9.5.5.1 Loss of frame alignment . 37
9.5.5.2 Strategy for frame alignment recovery. 37
9.5.5.3 CRC multiframe alignment using information in bit 1 of
the basic frame . 38
9.5.5.4 CRC bit monitoring. 38
9.5.5.5 Monitoring for false frame alignment . 38
10 Layer 2 requirements. 39
10.1 Frame structure for peer-to-peer communication . 39
10.1.1 General . 39
10.1.2 Flag sequence . 39
10.1.3 Address field. 39
10.1.4 Control field. 40
10.1.5 Information field . 40
10.1.6 Transparency. 40
10.1.7 Frame Check Sequence (FCS) field. 40
10.1.8 Format convention. 40
10.1.8.1 Numbering convention . 40
10.1.8.2 Order of bit transmission. 41
10.1.8.3 Field mapping convention . 41
10.1.9 Invalid or incompatible frames. 41
10.2 Elements of procedures and formats of fields for data link layer peer-to-peer
communication. 42
10.2.1 General . 42
10.2.2 Address field format. 42
10.2.3 Address field variables. 42
10.2.3.1 Address field Extension bit (EA) . 42
10.2.3.2 Command/Response field bit (C/R) . 42
10.2.3.3 Service Access Point Identifier (SAPI). 43
10.2.3.4 Terminal Endpoint Identifier (TEI). 43
10.2.3.4.1 TEI for broadcast data link connection. 43
10.2.3.4.2 TEI for point-to-point data link
connection. 43
10.2.4 Control field formats . 44
Page 5
TBR 4: November 1995
10.2.4.1 Information transfer (I) format.44
10.2.4.2 Supervisory (S) format.44
10.2.4.3 Unnumbered (U) format .44
10.2.5 Control field parameters and associated state variables .45
10.2.5.1 Poll/Final bit .45
10.2.5.2 Multiple frame operation - variables and sequence
numbers.45
10.2.5.2.1 Modulus .45
10.2.5.2.2 Send state variable V(S).45
10.2.5.2.3 Acknowledge state variable V(A).45
10.2.5.2.4 Send sequence number N(S) .45
10.2.5.2.5 Receive state variable V(R) .45
10.2.5.2.6 Receive sequence number N(R) .46
10.2.6 Frame types .46
10.2.6.1 Commands and responses .46
10.2.6.2 Information (I) command .46
10.2.6.3 Set Asynchronous Balanced Mode Extended (SABME)
command.47
10.2.6.4 DISConnect (DISC) command .47
10.2.6.5 Unnumbered Information (UI) command.47
10.2.6.6 Receive Ready (RR) command/response.47
10.2.6.7 REJect (REJ) command/response.47
10.2.6.8 Receive Not Ready (RNR) command/response.47
10.2.6.9 Unnumbered Acknowledgement (UA) response .48
10.2.6.10 Disconnected Mode (DM) response.48
10.3 Provision of point-to-point signalling connections.48
10.4 Procedures for unacknowledged information transfer.48
10.4.1 Transmission of unacknowledged information.48
10.4.2 Receipt of unacknowledged information .49
10.5 Terminal Endpoint Identifier (TEI) management procedures.49
10.5.1 General.49
10.5.2 TEI assignment procedure .49
10.5.2.1 Expiry of timer T202 .50
10.5.3 TEI check procedure .50
10.5.4 TEI removal procedure.51
10.5.4.1 Action taken by the data link layer entity receiving the
MDL-REMOVE-REQUEST primitive .51
10.5.4.2 Conditions for TEI removal.51
10.5.5 TEI identity verify procedure.51
10.5.5.1 General.51
10.5.5.2 Operation of the TEI identity verify procedure .51
10.5.5.3 Expiry of timer T202 .51
10.5.6 Formats and codes .52
10.5.6.1 General.52
10.5.6.2 Layer management entity identifier.52
10.5.6.3 Reference number (Ri).53
10.5.6.4 Message type .53
10.5.6.5 Action indicator (Ai).53
10.6 Procedures for establishment and release of multiple frame operation .53
10.6.1 Establishment of multiple frame operation.53
10.6.1.1 General.53
10.6.1.2 Establishment procedures.53
10.6.1.3 Procedure on expiry of timer T200 .54
10.6.2 Termination of multiple frame operation.55
10.6.3 Collision of unnumbered commands and responses .55
10.6.3.1 Identical transmitted and received commands .55
10.7 Procedures for information transfer in multiple frame operation .55
10.7.1 Transmitting I-frames .55
10.7.2 Receiving I-frames .55
10.7.2.1 P bit set to 1.56
10.7.2.2 P bit set to 0.56
10.7.3 Receiving acknowledgements.56
10.7.4 Receiving REJ frames.57
Page 6
TBR 4: November 1995
10.7.5 Receiving RNR frames . 58
10.7.5.1 Receiving a valid RNR command or response . 58
10.7.5.2 Expiry of timer T200 during "peer receiver busy". 58
10.7.5.3 Receiving a valid RNR command or response during
"peer receiver busy" . 58
10.7.5.4 Receiving a valid RR or REJ command or response
during "peer receiver busy" . 58
10.7.5.5 Appropriate supervisory response frame. 59
10.7.6 Waiting acknowledgement. 59
10.8 Re-establishment of multiple frame operation . 60
10.9 Exception condition reporting and recovery . 60
10.9.1 N(S) sequence error . 60
10.9.2 Invalid frame condition. 60
10.9.3 Frame rejection condition . 60
10.9.4 Multiple-assignment of TEI value. 61
10.10 List of system parameters. 61
10.10.1 Timer T200 . 61
10.10.2 Maximum number of retransmissions (N200) . 61
10.10.3 Maximum number of octets in an information field (N201). 61
10.10.4 Maximum number of transmission of the TEI identity request message
(N202). 62
10.10.5 Maximum number of outstanding I-frames (k) . 62
10.10.6 Timer T202 . 62
10.10.7 Layer 2 response time . 62
11 Layer 3 requirements. 62
11.1 Overview of call control . 62
11.1.1 Call states at the user side of the interface . 62
11.1.1.1 Null state (U0) . 62
11.1.1.2 Call initiated (U1). 63
11.1.1.3 Overlap sending (U2). 63
11.1.1.4 Outgoing call proceeding (U3) . 63
11.1.1.5 Call delivered (U4) . 63
11.1.1.6 Call present (U6). 63
11.1.1.7 Call received (U7) . 63
11.1.1.8 Connect request (U8). 63
11.1.1.9 Incoming call proceeding (U9) . 63
11.1.1.10 Active (U10) . 64
11.1.1.11 Disconnect request (U11) . 64
11.1.1.12 Disconnect indication (U12) . 64
11.1.1.13 Suspend request (U15). 64
11.1.1.14 Resume request (U17). 64
11.1.1.15 Release request (U19). 64
11.1.1.16 Overlap receiving (U25) . 64
11.1.2 Network call states. 64
11.1.2.1 Null state (N0) . 64
11.1.2.2 Call initiated (N1). 64
11.1.2.3 Overlap sending (N2). 65
11.1.2.4 Outgoing call proceeding (N3) . 65
11.1.2.5 Call delivered (N4) . 65
11.1.2.6 Call present (N6). 65
11.1.2.7 Call received (N7) . 65
11.1.2.8 Connect request (N8). 65
11.1.2.9 Incoming call proceeding (N9) . 65
11.1.2.10 Active (N10) . 65
11.1.2.11 Disconnect request (N11) . 66
11.1.2.12 Disconnect indication (N12) . 66
11.1.2.13 Suspend request (N15). 66
11.1.2.14 Resume request (N17). 66
11.1.2.15 Release request (N19). 66
11.1.2.16 Call abort (N22). 66
11.1.2.17 Overlap receiving (N25) . 66
11.1.3 States associated with the global call reference. 66
Page 7
TBR 4: November 1995
11.1.3.1 Call states at the user side of the interface .66
11.1.3.1.1 Null (Rest 0).66
11.1.3.1.2 Restart (Rest 2) .66
11.1.3.2 Call states at the network side of the interface.67
11.1.3.2.1 Null (Rest 0).67
11.1.3.2.2 Restart request (Rest 1) .67
11.2 Message functional definitions and content.67
11.2.1 Alerting .68
11.2.2 Call proceeding .69
11.2.3 Connect .70
11.2.4 Connect acknowledge.70
11.2.5 Disconnect.71
11.2.6 Information .71
11.2.7 Notify .72
11.2.8 Progress.72
11.2.9 Release .73
11.2.10 Release complete.73
11.2.11 Resume.74
11.2.12 Resume acknowledge.74
11.2.13 Resume reject .74
11.2.14 Setup .74
11.2.15 Setup acknowledge .76
11.2.16 Status .76
11.2.17 Status enquiry.77
11.2.18 Suspend .77
11.2.19 Suspend acknowledge .77
11.2.20 Suspend reject .77
11.2.21 Messages used with the global call reference.78
11.2.21.1 Restart .78
11.2.21.2 Restart acknowledge .79
11.3 General message format and information elements coding.79
11.3.1 Overview.79
11.3.2 Protocol discriminator.80
11.3.3 Call reference.80
11.3.4 Message type .81
11.3.5 Other information elements.82
11.3.5.1 Coding rules.82
11.3.5.1.1 Codeset 0.84
11.3.5.2 Extensions of codesets.84
11.3.5.3 Locking shift procedure .85
11.3.5.4 Non-locking shift procedure.86
11.3.5.5 Bearer capability .86
11.3.5.6 Call identity .93
11.3.5.7 Call state.94
11.3.5.8 Called party number .95
11.3.5.9 Called party subaddress.96
11.3.5.10 Cause .97
11.3.5.11 Channel identification .103
11.3.5.12 High Layer Compatibility.105
11.3.5.13 Low Layer Compatibility.107
11.3.5.14 Notification indicator .115
11.3.5.15 Progress indicator.115
11.3.5.16 Restart indicator.116
11.3.5.17 Sending complete.117
11.4 Circuit switched call control procedures .117
11.4.1 Call establishment at the originating interface.117
11.4.1.1 Call request.118
11.4.1.2 Overlap sending.118
11.4.1.3 Call proceeding.118
11.4.1.3.1 Call proceeding, en-bloc sending.118
11.4.1.3.2 Call proceeding, overlap sending.118
11.4.1.4 Call confirmation indication.119
11.4.1.5 Call connected.119
Page 8
TBR 4: November 1995
11.4.2 Call establishment at the destination interface . 119
11.4.2.1 Incoming call . 119
11.4.2.2 Address and compatibility checking. 119
11.4.2.2.1 Compatibility checking. 120
11.4.2.2.2 Address checking. 120
11.4.2.3 B-channel selection - destination . 120
11.4.2.3.1 SETUP message delivered by
point-to-point data link. 120
11.4.2.3.2 SETUP message delivered by
broadcast data link. . 121
11.4.2.4 Overlap receiving . 121
11.4.2.5 Call confirmation . 121
11.4.2.5.1 Response to en-bloc SETUP or
completion of overlap receiving. 121
11.4.2.6 Call accept . 122
11.4.2.7 Active indication . 122
11.4.3 Call clearing . 122
11.4.3.1 Terminology . 122
11.4.3.2 Exception conditions . 122
11.4.3.3 Clearing initiated by the user. 122
11.4.3.4 Clearing initiated by the network . 123
11.4.3.4.1 Clearing when tones/announcements
provided. 123
11.4.3.4.2 Clearing when tones/announcements
not provided. 123
11.4.3.4.3 Completion of clearing . 123
11.4.3.5 Clear collision. 124
11.4.4 Call rearrangements . 124
11.4.5 Call collisions . 124
11.4.6 Handling of error conditions. 124
11.4.6.1 Protocol discrimination error . 124
11.4.6.2 Call reference procedural errors . 125
11.4.6.3 Message type or message sequence errors. 125
11.4.6.4 Duplicated information elements. 126
11.4.6.5 Mandatory information element errors. 126
11.4.6.5.1 Mandatory information element
missing . 126
11.4.6.5.2 Mandatory information element
content error. 126
11.4.6.6 Non-mandatory information element errors . 127
11.4.6.6.1 Unrecognized information element . 127
11.4.6.6.2 Non-mandatory information element
content error. 128
11.4.6.7 Status enquiry procedure. 128
11.4.6.8 Receiving a STATUS message . 129
11.4.7 User notification procedure. 129
11.4.8 Restart procedure. 129
11.5 TE timers. 129
Annex A (normative): TBR Requirements Table (TBR-RT) . 130
A.1 Guidance for completion of the TBR-RT . 130
A.2 Layer 1 and overvoltage requirements TBR-RT. 130
A.3 Layer 2 TBR-RT. 132
A.4 Layer 3 TBR-RT. 134
Annex B (normative): Layer 1 tests . 136
B.1 Scope and general information. 136
B.1.1 Scope . 136
Page 9
TBR 4: November 1995
B.1.2 General information .136
B.1.2.1 Additional information to support the test.136
B.1.3 Connection of the simulator to the IUT .136
B.1.4 Connection of the IUT to ground.137
B.1.5 Environmental conditions.137
B.1.6 Pulse measurements.137
B.2 Specification at the output port.138
B.2.1 Waveform shape .138
B.2.1.1 Pulse shape and amplitude of a mark (pulse).138
B.2.1.2 Peak voltage of a space (no pulse).139
B.2.1.3 Ratio of the amplitudes of positive and negative pulses at the centre of
the pulse.140
B.2.1.4 Ratio of the widths of positive and negative pulses at the nominal half
amplitude.141
B.2.2 Impedance towards ground of the transmitter output .142
B.2.3 Bit rate when unsynchronized.143
B.2.4 Output jitter .144
B.2.5 HDB3 coding.146
B.3 Specification at the input port.147
B.3.1 Return loss.147
B.3.2 Immunity to attenuation and reflections .148
B.3.3 Minimum tolerance to jitter.149
B.3.4 Tolerable longitudinal voltage .150
B.3.5 Impedance towards ground of the receiver inputs.151
B.4 Frame structure.152
B.4.1 Generation of frame alignment word .153
B.4.2 CRC processing.154
B.5 Operational functions .156
B.5.1 States-matrix at the IUT user side .156
B.5.2 Frame alignment (without the test of CRC procedure) .157
B.5.3 CRC multiframe alignment.159
Annex C (normative): Layer 2 tests .161
C.1 Test case selection .161
C.2 Layer 2 test suite .162
Annex D (normative): Layer 3 tests .241
D.1 Test case selection .241
D.2 Layer 3 test suite .243
Annex E (informative): Protocol Implementation eXtra Information for Testing (PIXIT) .367
E.1 Introduction.367
E.2 References.367
E.3 Proforma structure and contents.367
E.4 Table/item identification.367
E.5 Guidance on completing the PIXIT .367
E.6 Environmental test conditions .368
Page 10
TBR 4: November 1995
E.7 Layer 1 PIXIT. 368
E.8 Layer 2 PIXIT. 371
E.9 Layer 3 PIXIT. 372
Annex F (informative): Justifications for the requirements in the TBR. 376
F.1 Principles applicable to the whole TBR . 376
F.1.1 General principles . 376
F.1.2 Requirements vs. definitions . 376
F.1.3 Error conditions . 376
F.1.4 General editori
...



