SIST TBR 003 E1:2004

• Abstract:

  Technical characteristics of terminal equipment which is capable of connection to a T, or coincident S and T, reference point at an interface to a public telecommunications network presented as an ISDN basic access point

• Status: Published
• Publication Date: 30-Sep-2004
• ICS: 33.080 - Integrated Services Digital Network (ISDN)
• 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-237C
• Ref Project: ETSI TBR 003 ed.1 (1995-11) - Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN basic access

SIST TBR 003 E1:2004 is the Slovenian standard identical to ETSI TBR 3 Edition 1 for Integrated Services Digital Network (ISDN) terminal equipment. It specifies the technical attachment requirements for terminal equipment that connects to an ISDN basic access point at a T, or coincident S and T, reference point on a public telecommunications network. The document covers physical connection, electrical behavior, Layer 1, Layer 2 and Layer 3 procedures, power feeding, protection, and the test material used to check them.

What does SIST TBR 003 E1:2004 specify?

SIST TBR 003 E1:2004 specifies the technical characteristics for terminal equipment capable of connection to an ISDN basic access interface. In practice, it tells suppliers and test labs what the terminal must do at the access point so it can interwork with the public ISDN network.

The document is organized into a short front matter, then clauses 1 to 11, followed by annexes A to G.

Annex	What it covers
A	Guidance for completing the TBR-RT, plus Layer 1 and overvoltage requirements
B	Layer 1 tests and power feeding tests
C	Layer 2 test suite
D	Layer 3 test suite
E	PIXIT proforma and guidance for filling it in
F	Changes with respect to the base standards and related requirements
G	Basic telecommunication services and supplementary services

The structure matters because the document is not just a list of requirements. It also gives the test cases and proformas used to check a terminal against those requirements.

What are the key requirements of SIST TBR 003 E1:2004?

General and protection requirements

SIST TBR 003 E1:2004 separates the attachment requirements from safety and EMC topics. Clauses 6 and 7 state that there are no safety requirements and no Electro-Magnetic Compatibility (EMC) requirements under this TBR, so conformity work for those topics comes from other documents.

Clause 8 covers overvoltage protection. It addresses impulse transfer from mains in common mode and transverse mode, and conversion of common mode to transverse mode. For a product designer, this means the terminal must survive the relevant surge environment at the access interface.

Layer 1 - physical, electrical and interface behavior

Clause 9 defines the Layer 1 requirements. It starts with physical characteristics for three connection cases and the standard cords used with ISDN basic access. This is important because wiring, pin use and cord characteristics affect interoperability right at the socket.

Clause 9.2 covers electrical characteristics such as bit rate, jitter, timing relationship between input and output, transmitter output impedance, pulse shape and amplitude, pulse unbalance, voltage on other test loads, and receiver sensitivity. In practice, these are the signal-quality checks that determine whether the terminal can send and receive a clean ISDN basic access signal.

Clause 9.3 covers the functional frame organization and line code. That tells the reader how bits are arranged in the frame and how the physical layer signal is encoded.

Clause 9.4 covers interface procedures, including D-channel access, multipoint contention resolution, collision detection, activation and deactivation, frame alignment, multiframing, and the idle channel code on the B-channels. These items matter because they control how the terminal starts up, shares the bus when several terminals are present, and recovers from changes in line state.

Clause 9.5 covers power feeding. It defines functions at the access leads, current transient behavior, Power Source 1 consumption under normal and restricted power conditions, galvanic isolation, and limits on power source and sink during transient conditions. For buyers and integrators, this is the part that affects whether a terminal can be powered from the line and how it behaves when power changes or the interface is disturbed.

Layer 2 - data link behavior and TEI management

Clause 10 specifies the Layer 2 requirements for peer-to-peer communication. It includes the frame structure, with flag, address, control, information and Frame Check Sequence (FCS) fields, plus the coding conventions used to read those fields.

Clause 10 also defines the address and control variables used on the data link layer, including Service Access Point Identifier (SAPI) and Terminal Endpoint Identifier (TEI). These are important because they control which service or terminal a frame belongs to, especially on shared access.

The clause goes on to define multiple frame operation, unacknowledged information transfer, TEI assignment, TEI check, TEI removal, and TEI identity verify procedures. In practice, these procedures are what allow the network and the terminal to identify each other, establish reliable data exchange, and recover from link errors.

Clause 10.10 lists the system parameters such as timers, retransmission limits, maximum information field size, and the number of outstanding I-frames. These are the values a tester or implementer must respect when validating Layer 2 behavior.

Layer 3 - call control and message coding

Clause 11 covers Layer 3 requirements for circuit switched call control. It defines the call states at the user side and network side, as well as states associated with the global call reference. This gives the state model for call setup, connection, clearing, suspension and resumption.

Clause 11.2 defines the functional content of the Layer 3 messages, including Alerting, Call proceeding, Connect, Disconnect, Release, Resume, Setup, Status, Suspend, Restart and their acknowledgement or reject messages. This is the core of ISDN call control: if these messages are wrong, the terminal may set up calls incorrectly or fail to clear them properly.

Clause 11.3 defines the general message format and the coding of key information elements such as Bearer capability, Called party number, Called party subaddress, Cause, Channel identification, High layer compatibility, Low layer compatibility, Notification indicator, Progress indicator, Restart indicator and Sending complete. For implementers, this is the part that links the signalling message to the type of service and the requested channel.

Clause 11.4 covers the procedures for circuit switched call establishment, call clearing, call rearrangements, collisions, error handling, user notification and restart. Clause 11.5 defines TE timers used by Layer 3 procedures. These clauses matter because they describe how a terminal must behave during real call events, including errors and unusual timing conditions.

What terms does SIST TBR 003 E1:2004 define?

• Terminal Endpoint Identifier (TEI) - The identifier used in Layer 2 management to distinguish a terminal endpoint on the access.
• Service Access Point Identifier (SAPI) - The Layer 2 address field value that identifies which service access point a frame belongs to.
• D-channel - The ISDN channel used for signalling and access procedures, including contention and call control.
• B-channel - The bearer channel used for circuit-switched traffic.
• Bearer capability - The Layer 3 information element that describes the kind of bearer service requested or supported.
• Call reference - The identifier that ties Layer 3 messages to a specific call instance.
• Multiframe operation - The Layer 2 mode in which frames are organized and acknowledged across multiple frames.
• Frame Check Sequence (FCS) - The field used to check whether a Layer 2 frame has been received correctly.

Who uses SIST TBR 003 E1:2004?

This standard is used by terminal equipment designers, ISDN product engineers, and test laboratories that need to verify attachment to ISDN basic access. It is also used by quality managers and conformity assessment teams when checking whether a terminal meets the expected physical, electrical and signalling behavior.

Network operators and integrators use it when specifying how equipment may attach to the public telecommunications network. Buyers and procurement teams use it to compare products at a technical level, especially where Layer 1, Layer 2, Layer 3 and power-feeding behavior matter for interoperability.

Which standards are used with SIST TBR 003 E1:2004?

Standard or recommendation	What it contributes
ETS 300 125	Base material for the data link layer primitives and related definitions
ETS 300 012	Basis for Layer 1 and overvoltage-related requirements discussed in annex F
ETS 300 102-1	Base material for Layer 3 message and information element behavior, including compatibility-related coding
I-ETS 300 313	Earlier basis for timing tolerances and Layer 2 response-time related changes
I-ETS 300 322	Earlier basis for basic access point-to-point configurations and RESTART-related testing
CCITT Recommendation X.200	Reference model used in the definitions section for Layer 1 and higher layers

What does the SIST TBR 003 E1:2004 document contain?

The document contains detailed frame formats, signal and bit layouts, message formats, call-state diagrams, and procedure descriptions for ISDN basic access. It also contains many test cases and test suites, especially in annexes B, C and D, for electrical characteristics, interface procedures, Layer 2 and Layer 3 behavior.

Annex E provides the PIXIT proforma used to record implementation-specific test information. Annex A gives guidance for completing the TBR-RT and links the choices in that proforma to the relevant Layer 1, overvoltage and power-feeding requirements.

The test material is organized so that implementers can verify startup, collision handling, TEI procedures, call establishment, clearing, suspend and resume behavior, and power-feeding behavior under different conditions. That makes the standard useful both for design validation and for formal conformance testing.

SLOVENSKI STANDARD
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 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 3
BASIS for November 1995
REGULATION
Source: ETSI TC-TE Reference: DTBR/TE-05003
ICS: 33.080
ISDN, terminal equipment, basic access
Key words:
Integrated Services Digital Network (ISDN);
Attachment requirements for terminal equipment to connect
to an ISDN using ISDN basic 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 - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
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 3: 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 3: November 1995
Contents
Foreword .13
The-machine-processable-ATS.13
1 Scope .15
2 Normative references.15
3 Definitions, symbols and abbreviations.16
3.1 Definitions .16
3.2 Abbreviations .18
4 General.19
5 Definitions of primitives .20
5.1 Generic names .20
5.1.1 DL-ESTABLISH.20
5.1.2 DL-RELEASE .21
5.1.3 DL-DATA.21
5.1.4 DL-UNIT DATA.21
5.1.5 MDL-ASSIGN .21
5.1.6 MDL-REMOVE .21
5.1.7 MDL-ERROR.21
5.1.8 MDL-UNIT DATA.21
5.1.9 PH-DATA.22
5.1.10 PH-ACTIVATE.22
5.1.11 PH-DEACTIVATE.22
5.1.12 MPH-INFORMATION.22
5.2 Primitive types.22
5.2.1 REQUEST.22
5.2.2 INDICATION.22
5.2.3 RESPONSE .22
5.2.4 CONFIRM.23
5.3 Parameter definition.23
5.3.1 Priority indicator.23
5.3.2 Message unit .23
6 Safety requirements .24
7 Electro-Magnetic Compatibility (EMC) requirements .25
8 Overvoltage protection requirements .25
8.1 Impulse transfer from mains, common mode.25
8.2 Impulse transfer from mains, transverse mode.25
8.3 Conversion of common mode to transverse mode.25
9 Layer 1 requirements .26
9.1 Physical characteristics.26
9.1.1 Case A.26
9.1.2 Case B.27
9.1.3 Case C .27
9.1.4 Standard ISDN basic access TE cord.28
9.1.5 ISDN reference cord.28
9.2 Electrical characteristics .29
9.2.1 Bit rate .29
9.2.2 Jitter and bit-phase relationship between TE input and output .29

Page 4
TBR 3: November 1995
9.2.2.1 Test configurations. 29
9.2.2.2 Timing extraction jitter. 31
9.2.2.3 Total phase deviation input to output . 31
9.2.3 TE transmitter output impedance . 32
9.2.4 Pulse shape and amplitude (binary ZERO) . 33
9.2.5 Pulse unbalance . 34
9.2.5.1 Pulse amplitude when transmitting a high density pattern. 34
9.2.5.2 Pulse unbalance of an isolated couple of pulses . 34
9.2.6 Voltage on other test loads . 35
9.2.6.1 400 Ω load. 35
9.2.6.2 5,6 Ω load. 37
9.2.7 Longitudinal conversion loss of the transmitter output . 37
9.2.8 TE receiver input impedance. 39
9.2.9 Receiver sensitivity - Noise and distortion immunity. 39
9.2.10 Longitudinal Conversion Loss (LCL) of the receiver inputs . 39
9.3 Functional characteristics. 40
9.3.1 Binary organization of the frame. 40
9.3.1.1 TE to NT. 40
9.3.1.2 NT to TE. 41
9.3.1.3 Relative bit positions . 41
9.3.2 Line code . 41
9.4 Interface procedure . 42
9.4.1 D-channel access procedure. 42
9.4.1.1 Interframe (Layer 2) time fill. 42
9.4.1.2 Multipoint contention resolution mechanism. 42
9.4.1.3 Collision detection. 42
9.4.2 Activation/deactivation . 43
9.4.2.1 TE states. 43
9.4.2.1.1 State F1 (Inactive). 43
9.4.2.1.2 State F2 (Sensing) . 43
9.4.2.1.3 State F3 (Deactivated) . 43
9.4.2.1.4 State F4 (awaiting signal). 43
9.4.2.1.5 State F5 (identifying input) . 43
9.4.2.1.6 State F6 (synchronized) . 43
9.4.2.1.7 State F7 (activated). 44
9.4.2.1.8 State F8 (lost framing). 44
9.4.2.2 Signals . 44
9.4.2.3 Activation/deactivation procedure for TEs . 44
9.4.2.3.1 Specification of the procedure. 44
9.4.2.3.2 Timer values. 50
9.4.2.4 TE activation times. 51
9.4.2.5 Deactivation times. 51
9.4.3 Frame alignment procedures. 51
9.4.4 Multiframing . 52
9.4.5 Idle Channel Code on the B-Channels . 52
9.5 Power feeding . 52
9.5.1 Functions specified at the access leads . 52
9.5.2 Current transient. 52
9.5.3 Power Source 1 consumption. 52
9.5.3.1 Normal power conditions . 52
9.5.3.2 Restricted power conditions. 53
9.5.3.2.1 Power available to the TE
"designated" for restricted power
operation . 53
9.5.3.2.2 Power available to locally powered
and "non-designated" TEs. 53
9.5.4 Galvanic isolation. 53
9.5.5 Limitations on power source and sink during transient conditions . 54
9.5.5.1 Current/time limitations for TEs . 54
9.5.5.1.1 Current/time limitations for remotely
powered TEs in normal mode . 54
9.5.5.1.2 Current/time limitations for designated
TEs in restricted mode . 54

Page 5
TBR 3: November 1995
9.5.5.1.3 Current/time limitations for non-
designated and locally powered TEs in
restricted mode.54
9.5.5.1.4 Protection against PS1 interruption .55
9.5.5.2 Other TE requirements.56
9.5.5.2.1 Minimum TE start up current .56
9.5.5.2.2 Protection against short term
interruptions .57
9.5.5.2.3 Behaviour at the switch-over.57
9.5.5.3 Current unbalance .58
9.5.5.3.1 DC unbalance of power sink 1.58
9.5.5.3.2 Current unbalance in a pair.58
10 Layer 2 requirements .60
10.1 Frame structure for peer-to-peer communication.60
10.1.1 General.60
10.1.2 Flag sequence.60
10.1.3 Address field.61
10.1.4 Control field .61
10.1.5 Information field.61
10.1.6 Transparency .61
10.1.7 Frame Check Sequence (FCS) field .61
10.1.8 Format convention.62
10.1.8.1 Numbering convention.62
10.1.8.2 Order of bit transmission .62
10.1.8.3 Field mapping convention.62
10.1.9 Invalid or incompatible frames .63
10.2 Elements of procedures and formats of fields for data link layer peer-to-peer
communication.63
10.2.1 General.63
10.2.2 Address field format .63
10.2.3 Address field variables .63
10.2.3.1 Address field extension bit (EA) .63
10.2.3.2 Command/Response field bit (C/R).64
10.2.3.3 Service Access Point Identifier (SAPI) .64
10.2.3.4 Terminal Endpoint Identifier (TEI).64
10.2.3.4.1 TEI for broadcast data link connection .64
10.2.3.4.2 TEI for point-to-point data link
connection.65
10.2.4 Control field formats .65
10.2.4.1 Information transfer (I) format.65
10.2.4.2 Supervisory (S) format.66
10.2.4.3 Unnumbered (U) format .66
10.2.5 Control field parameters and associated state variables .66
10.2.5.1 Poll/Final bit .66
10.2.5.2 Multiple frame operation - variables and sequence
numbers.66
10.2.5.2.1 Modulus .66
10.2.5.2.2 Send state variable V(S).66
10.2.5.2.3 Acknowledge state variable V(A).67
10.2.5.2.4 Send sequence number N(S) .67
10.2.5.2.5 Receive state variable V(R) .67
10.2.5.2.6 Receive sequence number N(R) .67
10.2.6 Frame types .67
10.2.6.1 Commands and responses .67
10.2.6.2 Information (I) command .68
10.2.6.3 Set Asynchronous Balanced Mode Extended (SABME)
command.68
10.2.6.4 DISConnect (DISC) command .68
10.2.6.5 Unnumbered Information (UI) command.68
10.2.6.6 Receive Ready (RR) command/response.69
10.2.6.7 REJect (REJ) command/response.69
10.2.6.8 Receive Not Ready (RNR) command/response.69

Page 6
TBR 3: November 1995
10.2.6.9 Unnumbered Acknowledgement (UA) response . 69
10.2.6.10 Disconnected Mode (DM) response . 70
10.3 Provision of point-to-point signalling connections . 70
10.4 Procedures for unacknowledged information transfer . 70
10.4.1 Transmission of unacknowledged information . 70
10.4.2 Receipt of unacknowledged information. 70
10.5 Terminal Endpoint Identifier (TEI) management procedures. 71
10.5.1 General . 71
10.5.2 TEI assignment procedure . 71
10.5.2.1 Expiry of timer T202. 72
10.5.3 TEI check procedure . 72
10.5.4 TEI removal procedure . 73
10.5.4.1 Action taken by the data link layer entity receiving the
MDL-REMOVE-REQUEST primitive. 73
10.5.4.2 Conditions for TEI removal . 73
10.5.5 TEI identity verify procedure . 73
10.5.5.1 General . 73
10.5.5.2 Operation of the TEI identity verify procedure. 73
10.5.5.3 Expiry of timer T202. 73
10.5.6 Formats and codes. 74
10.5.6.1 General . 74
10.5.6.2 Layer management entity identifier. 75
10.5.6.3 Reference number (Ri) . 75
10.5.6.4 Message type. 75
10.5.6.5 Action indicator (Ai). 75
10.6 Procedures for establishment and release of multiple frame operation. 75
10.6.1 Establishment of multiple frame operation . 75
10.6.1.1 General . 75
10.6.1.2 Establishment procedures . 76
10.6.1.3 Procedure on expiry of timer T200. 77
10.6.2 Termination of multiple frame operation. 77
10.6.3 Collision of unnumbered commands and responses . 77
10.6.3.1 Identical transmitted and received commands . 77
10.7 Procedures for information transfer in multiple frame operation. 77
10.7.1 Transmitting I-frames. 77
10.7.2 Receiving I-frames. 78
10.7.2.1 P bit set to 1 . 78
10.7.2.2 P bit set to 0 . 78
10.7.3 Receiving acknowledgements . 79
10.7.4 Receiving REJ frames . 79
10.7.5 Receiving RNR frames . 80
10.7.5.1 Receiving a valid RNR command or response . 80
10.7.5.2 Expiry of timer T200 during "peer receiver busy". 80
10.7.5.3 Receiving a valid RNR command or response during
"peer receiver busy" . 81
10.7.5.4 Receiving a valid RR or REJ command or response
during "peer receiver busy" . 81
10.7.5.5 Appropriate supervisory response frame. 81
10.7.6 Waiting acknowledgement. 81
10.8 Re-establishment of multiple frame operation . 82
10.9 Exception condition reporting and recovery . 82
10.9.1 N(S) sequence error . 82
10.9.2 Invalid frame condition. 83
10.9.3 Frame rejection condition . 83
10.9.4 Multiple-assignment of TEI value. 83
10.10 List of system parameters. 83
10.10.1 Timer T200 . 83
10.10.2 Maximum number of retransmissions (N200) . 84
10.10.3 Maximum number of octets in an information field (N201). 84
10.10.4 Maximum number of transmission of the TEI identity request message
(N202). 84
10.10.5 Maximum number of outstanding I-frames (k) . 84
10.10.6 Timer T202 . 84

Page 7
TBR 3: November 1995
10.10.7 Layer 2 response time.84
11 Layer 3 requirements .85
11.1 Overview of call control.85
11.1.1 Call states at the user side of the interface .85
11.1.1.1 Null state (U0).85
11.1.1.2 Call initiated (U1) .85
11.1.1.3 Overlap sending (U2).85
11.1.1.4 Outgoing call proceeding (U3).85
11.1.1.5 Call delivered (U4).85
11.1.1.6 Call present (U6).85
11.1.1.7 Call received (U7).86
11.1.1.8 Connect request (U8) .86
11.1.1.9 Incoming call proceeding (U9).86
11.1.1.10 Active (U10).86
11.1.1.11 Disconnect request (U11).86
11.1.1.12 Disconnect indication (U12).86
11.1.1.13 Suspend request (U15) .86
11.1.1.14 Resume request (U17) .86
11.1.1.15 Release request (U19) .87
11.1.1.16 Overlap receiving (U25).87
11.1.2 Network call states .87
11.1.2.1 Null state (N0).87
11.1.2.2 Call initiated (N1) .87
11.1.2.3 Overlap sending (N2).87
11.1.2.4 Outgoing call proceeding (N3).87
11.1.2.5 Call delivered (N4).87
11.1.2.6 Call present (N6).87
11.1.2.7 Call received (N7).88
11.1.2.8 Connect request (N8) .88
11.1.2.9 Incoming call proceeding (N9).88
11.1.2.10 Active (N10).88
11.1.2.11 Disconnect request (N11).88
11.1.2.12 Disconnect indication (N12).88
11.1.2.13 Suspend request (N15) .88
11.1.2.14 Resume request (N17) .88
11.1.2.15 Release request (N19) .89
11.1.2.16 Call abort (N22) .89
11.1.2.17 Overlap receiving (N25).89
11.1.3 States associated with the global call reference .89
11.1.3.1 Call states at the user side of the interface .89
11.1.3.1.1 Null (Rest 0).89
11.1.3.1.2 Restart (Rest 2) .89
11.1.3.2 Call states at the network side of the interface.89
11.1.3.2.1 Null (Rest 0).89
11.1.3.2.2 Restart request (Rest 1) .89
11.2 Message functional definitions and content.90
11.2.1 Alerting .92
11.2.2 Call proceeding .93
11.2.3 Connect .94
11.2.4 Connect acknowledge.95
11.2.5 Disconnect.95
11.2.6 Information .96
11.2.7 Notify .96
11.2.8 Progress.97
11.2.9 Release .98
11.2.10 Release complete.98
11.2.11 Resume.99
11.2.12 Resume acknowledge.99
11.2.13 Resume reject .100
11.2.14 Setup .101
11.2.15 Setup acknowledge .102
11.2.16 Status .102

Page 8
TBR 3: November 1995
11.2.17 Status enquiry. 103
11.2.18 Suspend. 103
11.2.19 Suspend acknowledge. 104
11.2.20 Suspend reject. 104
11.2.21 Messages used with the global call reference. 104
11.2.21.1 Restart. 105
11.2.21.2 Restart acknowledge . 105
11.3 General message format and information elements coding . 106
11.3.1 Overview. 106
11.3.2 Protocol discriminator . 106
11.3.3 Call reference . 107
11.3.4 Message type. 108
11.3.5 Other information elements . 109
11.3.5.1 Coding rules. 109
11.3.5.1.1 Codeset 0. 111
11.3.5.2 Extensions of codesets. 112
11.3.5.3 Locking shift procedure. 113
11.3.5.4 Non-locking shift procedure . 114
11.3.5.5 Bearer capability . 115
11.3.5.6 Call identity. 124
11.3.5.7 Call state . 124
11.3.5.8 Called party number. 125
11.3.5.9 Called party subaddress . 128
11.3.5.10 Cause. 129
11.3.5.11 Channel identification. 137
11.3.5.12 High layer compatibility . 139
11.3.5.13 Low layer compatibility . 142
11.3.5.14 Notification indicator. 152
11.3.5.15 Progress indicator . 152
11.3.5.16 Restart indicator. 154
11.3.5.17 Sending complete . 154
11.4 Circuit switched call control procedures. 154
11.4.1 Call establishment at the originating interface. 155
11.4.1.1 Call request. 155
11.4.1.2 Overlap sending. 155
11.4.1.3 Call proceeding . 155
11.4.1.3.1 Call proceeding, en-bloc sending. 155
11.4.1.3.2 Call proceeding, overlap sending. 156
11.4.1.4 Call confirmation indication . 156
11.4.1.5 Call connected . 156
11.4.2 Call establishment at the destination interface . 156
11.4.2.1 Incoming call . 156
11.4.2.2 Address and compatibility checking. 157
11.4.2.2.1 Compatibility checking. 157
11.4.2.2.2 Address checking. 157
11.4.2.3 B-channel selection-destination . 158
11.4.2.3.1 SETUP message delivered by
point-to-point data link. 158
11.4.2.3.2 SETUP message delivered by
broadcast data link. . 158
11.4.2.4 Overlap receiving . 159
11.4.2.5 Call confirmation . 159
11.4.2.5.1 Response to en-bloc SETUP or
completion of overlap receiving. 159
11.4.2.6 Call accept . 160
11.4.2.7 Active indication . 160
11.4.2.8 Non-selected user clearing . 160
11.4.3 Call clearing . 160
11.4.3.1 Terminology . 160
11.4.3.2 Exception conditions . 160
11.4.3.3 Clearing initiated by the user. 161
11.4.3.4 Clearing initiated by the network . 161

Page 9
TBR 3: November 1995
11.4.3.4.1 Clearing when tones/announcements
provided .161
11.4.3.4.2 Clearing when tones/announcements
not provided .161
11.4.3.4.3 Completion of clearing .162
11.4.3.5 Clear collision .162
11.4.4 Call rearrangements.162
11.4.4.1 Call suspension .163
11.4.4.2 Call suspended.163
11.4.4.3 Call suspend error .163
11.4.4.4 Call re-establishment.163
11.4.4.5 Call resume errors.163
11.4.4.6 Double suspension .164
11.4.5 Call collisions.164
11.4.6 Handling of error conditions .164
11.4.6.1 Protocol discrimination error.164
11.4.6.2 Call reference procedural errors.164
11.4.6.3 Message type or message sequence errors .165
11.4.6.4 Duplicated information elements .166
11.4.6.5 Mandatory information element errors.166
11.4.6.5.1 Mandatory information element
missing.166
11.4.6.5.2 Mandatory information element
content error .166
11.4.6.6 Non-mandatory information element errors.167
11.4.6.6.1 Unrecognized information element.167
11.4.6.6.2 Non-mandatory information element
content error .168
11.4.6.7 Status enquiry procedure.168
11.4.6.8 Receiving a STATUS message.169
11.4.7 User notification procedure .169
11.4.8 Restart procedure.169
11.5 TE timers .170
Annex A (normative): TBR Requirements Table (TBR-RT).171
A.1 Guidance for completion of the TBR-RT.171
A.2 Layer 1 and overvoltage requirements TBR-RT .172
A.3 Layer 2 TBR-RT .175
A.4 Layer 3 TBR-RT .178
Annex B (normative): Conformance test principles for Layer 1.181
B.1 Scope and general information .181
B.1.1 Scope.181
B.1.2 General information .181
B.1.3 Definitions and abbreviations.181
B.1.4 Environmental conditions.182
B.1.5 Test case selection .182
B.2 Electrical characteristics tests .187
B.2.1 Bit rate when transmitting an INFO 1.187
B.2.2 TE jitter characteristics .188
B.2.2.1 TE jitter measurement characteristics (test A).188
B.2.2.2 TE output phase deviation (test B).189
B.2.3 TE transmitter output impedance.191
B.2.3.1 Test A.191
B.2.3.2 Test B.192
B.2.3.3 Test C.193
B.2.3.4 Test D.194

Page 10
TBR 3: November 1995
B.2.3.5 Test E . 195
B.2.4 Pulse shape and amplitude. 196
B.2.5 Pulse unbalance. 197
B.2.5.1 Pulse amplitude . 197
B.2.5.2 Pulse unbalance of an isolated couple of pulses. 198
B.2.6 Voltage on other test loads. 199
B.2.6.1 Test A . 199
B.2.6.2 Test B . 200
B.2.7 Longitudinal conversion loss of transmitter output. 201
B.2.8 Receiver input characteristics . 202
B.2.8.1 TE receiver input impedance. 202
B.2.8.1.1 Test A. 202
B.2.8.1.2 Test B. 203
B.2.8.1.3 Test C . 204
B.2.8.1.4 Test D . 205
B.2.8.2 Receiver sensitivity - noise and distortion immunity .
...