SIST TBR 033:2000
(Main)Integrated Services Digital Network (ISDN); Attachment requirements for packet mode terminal equipment to connect to an ISDN using ISDN basic access
Integrated Services Digital Network (ISDN); Attachment requirements for packet mode terminal equipment to connect to an ISDN using ISDN basic access
This TBR will define the attachment requirements for packet-mode terminals to access the ISDN packet-mode bearer service using an ISDN basic access. Only essential requirements contained in ETS 300 007 will be covered. This TBR will form the basis of CTR 033 in accordance with the scope from TRAC.
Digitalno omrežje z integriranimi storitvami (ISDN) - Zahteve za priključitev terminalske opreme v paketnem načinu na ISDN z uporabo osnovnega dostopa ISDN
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
3SIST TBR 033:
01-DYJXVW
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 =DKWHYH]DSULNOMXþLWHY
WHUPLQDOVNHRSUHPHYSDNHWQHPQDþLQXQD,6'1]XSRUDERRVQRYQHJDGRVWRSD
,6'1
Integrated Services Digital Network (ISDN); Attachment requirements for packet mode
terminal equipment to connect to an ISDN using ISDN basic access
Ta slovenski standard je istoveten z: TBR 033 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
3SIST TBR 033: en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
TECHNICAL TBR 33
BASIS for December 1997
REGULATION
Source: SPS Reference: DTBR/SPS-05119
ICS: 33.020
Key words: ISDN, packet mode, terminal, basic, access
Integrated Services Digital Network (ISDN);
Attachment requirements for packet mode terminal equipment
to connect to an ISDN using ISDN basic 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 2
TBR 33: 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 3
TBR 33: December 1997
Contents
Foreword .11
1 Scope .13
2 Normative references.13
3 Definitions and abbreviations .14
3.1 Definitions .14
3.2 Abbreviations .15
4 General.16
4.1 General requirements for the access of the PH .16
4.1.1 Channel used for the access of the PH.16
4.1.2 Requirements for layer 1.17
4.1.2.1 Requirements for complete layer 1 (comprising D-channel
and B-channels as a whole) .17
4.1.2.2 Requirements for layer 1 with respect to the selected
channel .17
4.1.3 Requirements for layer 2 of the D-channel.17
4.1.3.1 Requirements for data link connections with SAPI 0.17
4.1.3.2 Requirements for data link connections with SAPI 16.18
4.1.3.3 Requirements for data link connections with SAPI 63.18
4.1.4 Notification classes.19
4.1.5 Requirements for layer 3 of the D-channel.19
4.1.5.1 Outgoing calls.19
4.1.5.2 Incoming calls.19
4.1.5.3 Use of outgoing and incoming calls to support access of
the PH.20
5 Definitions of primitives .20
6 Safety requirements .20
7 Electro-Magnetic Compatibility (EMC) requirements .20
8 Overvoltage protection requirements .20
8.1 Impulse transfer from mains, common mode.20
8.2 Impulse transfer from mains, transverse mode.20
8.3 Conversion of common mode to transverse mode.20
9 Layer 1 requirements .21
9.1 Physical characteristics (on-demand layer 1) .21
9.2 Electrical characteristics (on-demand layer 1).21
9.3 Functional characteristics (on-demand layer 1).21
9.4 Interface procedure (on-demand layer 1) .21
9.4.1 D-channel access procedure .21
9.4.1.1 Interframe (layer 2) time fill.21
9.4.1.2 Multipoint contention resolution mechanism.21
9.4.1.3 Collision detection.22
9.4.2 Activation/deactivation.22
9.4.2.1 TE states .22
9.4.2.2 Signals.22
9.4.2.3 Activation/deactivation procedure for TEs .22
9.4.2.3.1 Specification of the procedure .22
9.4.2.3.2 Timer values .22
9.4.2.4 TE activation times .22
Page 4
TBR 33: December 1997
9.4.2.5 Deactivation times. 22
9.4.3 Frame alignment procedures. 23
9.4.4 Multiframing . 23
9.4.5 Idle Channel Code on the B-Channels . 23
9.5 Power feeding (on-demand layer 1). 23
9.6 Semi-permanent layer 1 requirements. 23
9.6.1 Activation/deactivation . 23
9.6.1.1 TE States . 23
9.6.1.1.1 State F1 (Inactive). 23
9.6.1.1.2 State F2 (Sensing) . 23
9.6.1.1.3 State F3 (Deactivated) . 23
9.6.1.1.4 State F6 (synchronized) . 23
9.6.1.1.5 State F7 (activated). 23
9.6.1.1.6 State F8 (lost framing). 23
9.6.2 Signals . 24
9.6.3 Specification of the Activation/deactivation procedure for semi-permanent
layer 1 TEs. 24
9.6.4 TE activation times . 27
9.6.5 Deactivation times . 27
10 Layer 2 D-channel requirements . 28
10.1 Frame structure for peer-to-peer communication . 28
10.1.1 General . 28
10.1.2 Flag sequence . 28
10.1.3 Address field. 28
10.1.4 Control field. 28
10.1.5 Information field . 29
10.1.6 Transparency. 29
10.1.7 Frame Check Sequence (FCS) field. 29
10.1.8 Format convention. 29
10.1.8.1 Numbering convention . 29
10.1.8.2 Order of bit transmission. 29
10.1.8.3 Field mapping convention . 29
10.1.9 Invalid or incompatible frames. 29
10.2 Elements of procedures and formats of fields for data link layer peer-to-peer
communication. 29
10.2.1 General . 29
10.2.2 Address field format. 29
10.2.3 Address field variables. 29
10.2.3.1 Address field extension bit (EA). 30
10.2.3.2 Command/Response field bit (C/R) . 30
10.2.3.3 Service Access Point Identifier (SAPI). 30
10.2.3.4 Terminal Endpoint Identifier (TEI). 30
10.2.3.4.1 TEI for broadcast data link connection. 30
10.2.3.4.2 TEI for point-to-point data link
connection. 30
10.2.4 Control field formats . 30
10.2.4.1 Information transfer (I) format. 30
10.2.4.2 Supervisory (S) format . 30
10.2.4.3 Unnumbered (U) format. 30
10.2.5 Control field parameters and associated state variables. 31
10.2.5.1 Poll/Final bit. 31
10.2.5.2 Multiple frame operation - variables and sequence
numbers . 31
10.2.5.2.1 Modulus. 31
10.2.5.2.2 Send state variable V(S) . 31
10.2.5.2.3 Acknowledge state variable V(A) . 31
10.2.5.2.4 Send sequence number N(S). 31
10.2.5.2.5 Receive state variable V(R). 31
10.2.5.2.6 Receive sequence number N(R). 31
10.2.6 Frame types. 31
10.2.6.1 Commands and responses. 31
10.2.6.2 Information (I) command. 32
Page 5
TBR 33: December 1997
10.2.6.3 Set Asynchronous Balanced Mode Extended (SABME)
command.32
10.2.6.4 DISConnect (DISC) command .32
10.2.6.5 Unnumbered Information (UI) command.32
10.2.6.6 Receive Ready (RR) command/response.33
10.2.6.7 REJect (REJ) command/response.33
10.2.6.8 Receive Not Ready (RNR) command/response.33
10.2.6.9 Unnumbered Acknowledgement (UA) response .33
10.2.6.10 Disconnected Mode (DM) response.33
10.3 Provision of point-to-point signalling connections.33
10.4 Procedures for unacknowledged information transfer.33
10.4.1 Transmission of unacknowledged information.33
10.4.2 Receipt of unacknowledged information .33
10.5 Terminal Endpoint Identifier (TEI) management procedures.34
10.5.1 General.34
10.5.2 TEI assignment procedure .34
10.5.2.1 Expiry of timer T202 .34
10.5.3 TEI check procedure .34
10.5.4 TEI removal procedure.34
10.5.4.1 Action taken by the data link layer entity receiving the
MDL-REMOVE-REQUEST primitive .34
10.5.4.2 Conditions for TEI removal.34
10.5.5 TEI identity verify procedure.34
10.5.5.1 General.34
10.5.5.2 Operation of the TEI identity verify procedure .34
10.5.6 Formats and codes .34
10.6 Procedures for establishment and release of multiple frame operation .35
10.6.1 Establishment of multiple frame operation.35
10.6.1.1 General.35
10.6.1.2 Establishment procedures.35
10.6.1.2.1 Establishment initiation .35
10.6.1.2.2 Establishment response .35
10.6.1.3 Procedure on expiry of timer T200 .36
10.6.2 Termination of multiple frame operation.36
10.7 Procedures for information transfer in multiple frame operation .36
10.7.1 Transmitting I-frames .36
10.7.2 Receiving I-frames .36
10.7.2.1 P bit set to 1.36
10.7.2.2 P bit set to 0.36
10.7.3 Receiving acknowledgements.37
10.7.4 Receiving REJ frames.37
10.7.5 Receiving RNR frames.38
10.7.5.1 Receiving a valid RNR command or response.38
10.7.5.2 Expiry of timer T200 during "peer receiver busy" .38
10.7.5.3 Receiving a valid RNR command or response during
"peer receiver busy".39
10.7.5.4 Receiving a valid RR or REJ command or response
during "peer receiver busy".39
10.7.5.5 Appropriate supervisory response frame.39
10.7.6 Waiting acknowledgement .40
10.8 Re-establishment of multiple frame operation .40
10.9 Exception condition reporting and recovery.41
10.9.1 N(S) sequence error.41
10.9.2 Invalid frame condition .41
10.9.3 Frame rejection condition.41
10.9.4 Multiple-assignment of TEI value .41
10.10 List of system parameters.42
10.10.1 Timer T200.42
10.10.2 Maximum number of retransmissions (N200).42
10.10.3 Maximum number of octets in an information field (N201) .42
10.10.4 Maximum number of transmission of the TEI identity request message
(N202) .42
10.10.5 Maximum number of outstanding I-frames (k) .42
Page 6
TBR 33: December 1997
10.10.6 Timer T202 . 42
10.10.7 Layer 2 response time . 42
11 Layer 3 D-channel requirements . 43
11.1 Overview of call control . 43
11.1.1 Call states at the user side of the interface . 43
11.1.1.1 Null state (U0) . 43
11.1.1.2 Call initiated (U1). 43
11.1.1.3 Call proceeding (U3) . 43
11.1.1.4 Call present (U6). 43
11.1.1.5 Call received (U7) . 44
11.1.1.6 Connect request (U8). 44
11.1.1.7 Incoming call proceeding (U9) . 44
11.1.1.8 Active (U10) . 44
11.1.1.9 Disconnect request (U11) . 44
11.1.1.10 Disconnect indication (U12) . 44
11.1.1.11 Release request (U19). 44
11.1.2 Network call states. 44
11.1.2.1 Null state (N0) . 44
11.1.2.2 Call initiated (N1). 44
11.1.2.3 Outgoing call proceeding (N3) . 44
11.1.2.4 Call present (N6). 45
11.1.2.5 Call received (N7) . 45
11.1.2.6 Connect request (N8). 45
11.1.2.7 Incoming call proceeding (N9) . 45
11.1.2.8 Active (N10) . 45
11.1.2.9 Disconnect request (N11) . 45
11.1.2.10 Disconnect indication (N12) . 45
11.1.2.11 Release request (N19). 45
11.1.2.12 Call abort (N22). 45
11.1.3 States associated with the global call reference. 46
11.1.3.1 Call states at the user side of the interface. 46
11.1.3.1.1 Null (Rest 0) . 46
11.1.3.1.2 Restart (Rest 2). 46
11.1.3.2 Call states at the network side of the interface . 46
11.1.3.2.1 Null (Rest 0) . 46
11.1.3.2.2 Restart request (Rest 1). 46
11.2 Message functional definitions and content . 46
11.2.1 Alerting. 47
11.2.2 Call proceeding. 48
11.2.3 Connect . 48
11.2.4 Connect acknowledge . 49
11.2.5 Disconnect. 49
11.2.6 Release. 50
11.2.7 Release complete. 50
11.2.8 Setup . 51
11.2.9 Status. 52
11.2.10 Status enquiry. 52
11.2.11 Messages used with the global call reference. 52
11.2.11.1 Restart. 52
11.2.11.2 Restart acknowledge . 52
11.3 General message format and information elements coding . 53
11.3.1 Overview. 53
11.3.2 Protocol discriminator . 53
11.3.3 Call reference . 53
11.3.4 Message type. 53
11.3.5 Other information elements . 55
11.3.5.1 Coding rules. 55
11.3.5.1.1 Codeset 0. 55
11.3.5.2 Extensions of codesets. 56
11.3.5.3 Locking shift procedure. 56
11.3.5.4 Non-locking shift procedure . 56
11.3.5.5 Bearer capability . 56
Page 7
TBR 33: December 1997
11.3.5.6 Call state.58
11.3.5.7 Called party number .58
11.3.5.8 Called party subaddress.58
11.3.5.9 Calling party number.58
11.3.5.10 Calling party subaddress .60
11.3.5.11 Cause .61
11.3.5.12 Channel identification .61
11.3.5.13 Restart indicator.61
11.4 Call control procedures for the control of packet-mode access of the PH .62
11.4.1 Call establishment at the originating interface.62
11.4.1.1 Call request.62
11.4.1.2 Overlap sending.62
11.4.1.3 Call proceeding.62
11.4.1.4 Call confirmation indication.62
11.4.1.5 Call connected.63
11.4.2 Call establishment at the destination interface.63
11.4.2.1 Incoming call.63
11.4.2.2 Compatibility checking.63
11.4.2.3 Channel selection-destination.64
11.4.2.4 Overlap receiving.64
11.4.2.5 Call confirmation.64
11.4.2.6 Call accept.65
11.4.2.7 Active indication.65
11.4.2.8 Non-selected user clearing.65
11.4.3 Call clearing.65
11.4.3.1 Terminology.65
11.4.3.2 Exception conditions.65
11.4.3.3 Clearing initiated by the user .66
11.4.3.4 Clearing initiated by the network.66
11.4.3.4.1 Clearing when tones/announcements
provided .66
11.4.3.4.2 Clearing when tones/announcements
not provided .66
11.4.3.4.3 Completion of clearing .66
11.4.3.5 Clear collision .66
11.4.4 Call rearrangements.67
11.4.5 Call collisions.67
11.4.6 Handling of error conditions .67
11.4.6.1 Call reference procedural errors.67
11.4.6.2 Message type or message sequence errors .67
11.4.6.3 Duplicated information elements .67
11.4.6.4 Mandatory information element errors.67
11.4.6.4.1 Mandatory information element
missing.67
11.4.6.5 Non-mandatory information element errors.67
11.4.6.5.1 Unrecognized information element.68
11.4.6.5.2 Non-mandatory information element
content error .68
11.4.6.6 Status enquiry procedure.69
11.4.6.7 Receiving a STATUS message.69
11.4.7 User notification procedure .70
11.4.8 Restart procedure.70
11.5 TE timers .70
12 X.25.71
12.1 X.25 requirements .71
12.2 X.25 procedures .71
12.2.1 Data link protocol supporting the X.25 packet level protocol .71
12.2.2 X.25 packet level protocol .71
12.2.3 Outgoing and incoming virtual calls.71
12.2.4 Identification of X.25 terminals .71
Page 8
TBR 33: December 1997
Annex A (normative): TBR Requirements Table (TBR-RT) . 72
A.1 Guidance for completion of the TBR-RT . 72
A.2 General classification of requirements TBR-RT. 73
A.3 Layer 1 and overvoltage requirements TBR-RT. 75
A.3.1 On-demand layer 1 requirement tables. 75
A.3.2 Semi-permanent layer 1 requirement tables. 79
A.4 Layer 2 TBR-RT. 83
A.5 Layer 3 TBR-RT. 86
Annex B (normative): Conformance test principles for layer 1 . 88
B.1 Scope and general information. 88
B.1.1 Scope . 88
B.1.2 General information. 88
B.1.3 Definitions and abbreviations . 88
B.1.4 Environmental conditions . 88
B.1.5 Test case selection . 89
B.2 Electrical characteristics tests . 92
B.3 Functional characteristic tests . 92
B.4 Interface procedure tests. 92
B.4.1 The TTCN Graphical form (TTCN.GR). 92
B.4.2 The TTCN Machine Processable form (TTCN.MP). 92
B.5 Power feeding. 93
Annex C (normative): Layer 2 tests . 94
C.1 The TTCN Graphical form (TTCN.GR) .94
C.2 The TTCN Machine Processable form (TTCN.MP) . 94
Annex D (normative): Layer 3 tests . 95
D.1 The TTCN Graphical form (TTCN.GR) .95
D.2 The TTCN Machine Processable form (TTCN.MP) . 95
Annex E (normative): Partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma . 96
E.1 Introduction. 96
E.2 References . 96
E.3 Proforma structure and contents . 96
E.4 Table/item identification. 96
E.5 Guidance on completing the PIXIT. 96
E.6 Environmental test conditions. 96
Page 9
TBR 33: December 1997
E.7 Layer 1 PIXIT .97
E.8 Layer 2 PIXIT .99
E.9 Layer 3 PIXIT .102
Annex F (informative): Justifications for the requirements in the TBR .104
F.1 Principles applicable to the whole TBR .104
F.1.1 General principles.104
F.1.2 Requirements versus definitions.104
F.1.3 Error conditions.104
F.1.4 General editorial changes to text from the base standards .105
F.1.5 Detailed list of changes with respect to the base standards.105
F.1.6 Untested requirements .106
F.1.7 Primitives .106
F.1.8 Supplementary services.106
F.1.9 Article 4(e) of the Directive.106
F.2 Changes with respect to TBR 3.106
F.2.1 Changes for layer 1.107
F.2.1.1 Protection requirements .107
F.2.1.2 Detailed list of changes with respect to TBR 3.107
F.2.2 Changes for layer 2 of the D-channel .108
F.2.3 Changes for layer 3 of the D-channel .109
Annex G (normative): List of supported telecommunication services .112
G.1 Basic telecommunication services .112
G.2 Supplementary services for the access connection.112
Annex H (informative): Examples for TE access configurations with small sets of requirements .113
Annex J (informative): Bibliography.115
History.116
Page 10
TBR 33: December 1997
Blank page
Page 11
TBR 33: December 1997
Foreword
This Technical Basis for Regulation (TBR) has been produced by the Signalling Protocols and Switching
(SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This TBR resulted from a mandate from the Commission of the European Community (CEC) to provide
harmonized standards for the support of the Council Directive 91/263/EEC ("The Terminal Equipment
Directive").
Annex F provides information relating to the articles of the Directive 91/263/EEC.
Annexes A, B, C, D, E and G are normative whereas annexes F, H and J are informative.
Overview of the Abstract Test Suites (ATSs)
This TBR is accompanied by the following ATSs (see annexes B, C and D):
- T33L1_7 (layer 1);
- T33L2_3 (layer 2);
- T33L3_5 (layer 3).
Page 12
TBR 33: December 1997
Blank page
Page 13
TBR 33: December 1997
1 Scope
This Technical Basis for Regulation (TBR) specifies the technical requirements under articles 4(c) to 4(f)
of Directive 91/263/EEC for Terminal Equipment (TE) to be attached to the pan-European Integrated
Services Digital Network (ISDN) at an interface at the T reference point or coincident S and T reference
point for a basic access. These requirements are intended to ensure that the essential requirements of
Directive 91/263/EEC continue to be met when up to eight Terminal Equipments are simultaneously
connected at the coincident S and T reference point. These requirements are taken from TBR 3 [9],
ETS 300 007 [10], ETS 300 047-3 [12], ETS 300 012 [11], ETS 300 102-1 [13] and ETS 300 125 [14].
This TBR does not contain the essential requirements of Article 4 (g) for interworking via the public
network, and so does not provide any guarantee of correct terminal-to-terminal operation.
NOTE 1: Although this TBR provides the technical attachment requirements, it does not contain
the full specification of the user side of the ISDN user-network interface. Important
information necessary for correct working can be found only in the base standards
mentioned above.
This TBR specifies these requirements for TE that:
a) access Packet Handler (PH) of an ISDN through either on-demand B- or D-channel mode or
semi-permanent B-channel mode basic services (case B of X.31) and those supplementary
services that are specified in annex G; and
b) is capable of handling either incoming calls only, outgoing calls only or both incoming and outgoing
calls.
This TBR applies to all TE that is intended for connection to the forms of ISDN access referred to above,
irrespective of whether the TE provides additional interfaces, telecommunications services or functions for
which other TBRs or national approval requirements apply.
This TBR does not specify the requirements for a packet mode TE that uses on-demand B-channel circuit
mode access (case A of X.31); the requirements for such a TE are contained in TBR 3 [9].
NOTE 2: This TBR is not applicable to TE which may be supplied in some countries for
connection to an ISDN telecommunications service corresponding to, but not
compatible with, the pan-European ISDN basic access standards.
2 Normative references
This TBR incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this TBR only when incorporated in it by amendment or revision. For undated references the
latest edition of the publication referred to applies.
[1] CCITT Recommendation G.117 (1988): "Transmission aspects of unbalance
about earth (Definitions and methods)".
[2] CCITT Recommendation I.411 (1988): "ISDN user-network interfaces -
Reference configurations".
[3] CCITT Recommendation I.430 (1988): "Basic user-network interface - Layer 1
specification".
[4] EN 60603-7 (1993): "Connectors for frequencies below 3 MHz for use with
printed boards; Part 7: Detail specification for connectors, 8-way, including fixed
and free connectors with common mating features; (IEC 603-7:1990)".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General Concepts".
Page 14
TBR 33: December 1997
[6] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 2: Abstract Test Suite
specification".
[7] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation (TTCN)".
[8] TBR 2 (1997): "Attachment requirements for Data Terminal Equipment (DTE) to
connect to Packet Switched Public Data Networks (PSPDNs) for CCITT
Recommendation X
...
SLOVENSKI STANDARD
01-junij-2000
'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL ,6'1 =DKWHYH]DSULNOMXþLWHY
WHUPLQDOVNHRSUHPHYSDNHWQHPQDþLQXQD,6'1]XSRUDERRVQRYQHJDGRVWRSD
,6'1
Integrated Services Digital Network (ISDN); Attachment requirements for packet mode
terminal equipment to connect to an ISDN using ISDN basic access
Ta slovenski standard je istoveten z: TBR 033 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 33
BASIS for December 1997
REGULATION
Source: SPS Reference: DTBR/SPS-05119
ICS: 33.020
Key words: ISDN, packet mode, terminal, basic, access
Integrated Services Digital Network (ISDN);
Attachment requirements for packet mode terminal equipment
to connect to an ISDN using ISDN basic 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 2
TBR 33: 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 3
TBR 33: December 1997
Contents
Foreword .11
1 Scope .13
2 Normative references.13
3 Definitions and abbreviations .14
3.1 Definitions .14
3.2 Abbreviations .15
4 General.16
4.1 General requirements for the access of the PH .16
4.1.1 Channel used for the access of the PH.16
4.1.2 Requirements for layer 1.17
4.1.2.1 Requirements for complete layer 1 (comprising D-channel
and B-channels as a whole) .17
4.1.2.2 Requirements for layer 1 with respect to the selected
channel .17
4.1.3 Requirements for layer 2 of the D-channel.17
4.1.3.1 Requirements for data link connections with SAPI 0.17
4.1.3.2 Requirements for data link connections with SAPI 16.18
4.1.3.3 Requirements for data link connections with SAPI 63.18
4.1.4 Notification classes.19
4.1.5 Requirements for layer 3 of the D-channel.19
4.1.5.1 Outgoing calls.19
4.1.5.2 Incoming calls.19
4.1.5.3 Use of outgoing and incoming calls to support access of
the PH.20
5 Definitions of primitives .20
6 Safety requirements .20
7 Electro-Magnetic Compatibility (EMC) requirements .20
8 Overvoltage protection requirements .20
8.1 Impulse transfer from mains, common mode.20
8.2 Impulse transfer from mains, transverse mode.20
8.3 Conversion of common mode to transverse mode.20
9 Layer 1 requirements .21
9.1 Physical characteristics (on-demand layer 1) .21
9.2 Electrical characteristics (on-demand layer 1).21
9.3 Functional characteristics (on-demand layer 1).21
9.4 Interface procedure (on-demand layer 1) .21
9.4.1 D-channel access procedure .21
9.4.1.1 Interframe (layer 2) time fill.21
9.4.1.2 Multipoint contention resolution mechanism.21
9.4.1.3 Collision detection.22
9.4.2 Activation/deactivation.22
9.4.2.1 TE states .22
9.4.2.2 Signals.22
9.4.2.3 Activation/deactivation procedure for TEs .22
9.4.2.3.1 Specification of the procedure .22
9.4.2.3.2 Timer values .22
9.4.2.4 TE activation times .22
Page 4
TBR 33: December 1997
9.4.2.5 Deactivation times. 22
9.4.3 Frame alignment procedures. 23
9.4.4 Multiframing . 23
9.4.5 Idle Channel Code on the B-Channels . 23
9.5 Power feeding (on-demand layer 1). 23
9.6 Semi-permanent layer 1 requirements. 23
9.6.1 Activation/deactivation . 23
9.6.1.1 TE States . 23
9.6.1.1.1 State F1 (Inactive). 23
9.6.1.1.2 State F2 (Sensing) . 23
9.6.1.1.3 State F3 (Deactivated) . 23
9.6.1.1.4 State F6 (synchronized) . 23
9.6.1.1.5 State F7 (activated). 23
9.6.1.1.6 State F8 (lost framing). 23
9.6.2 Signals . 24
9.6.3 Specification of the Activation/deactivation procedure for semi-permanent
layer 1 TEs. 24
9.6.4 TE activation times . 27
9.6.5 Deactivation times . 27
10 Layer 2 D-channel requirements . 28
10.1 Frame structure for peer-to-peer communication . 28
10.1.1 General . 28
10.1.2 Flag sequence . 28
10.1.3 Address field. 28
10.1.4 Control field. 28
10.1.5 Information field . 29
10.1.6 Transparency. 29
10.1.7 Frame Check Sequence (FCS) field. 29
10.1.8 Format convention. 29
10.1.8.1 Numbering convention . 29
10.1.8.2 Order of bit transmission. 29
10.1.8.3 Field mapping convention . 29
10.1.9 Invalid or incompatible frames. 29
10.2 Elements of procedures and formats of fields for data link layer peer-to-peer
communication. 29
10.2.1 General . 29
10.2.2 Address field format. 29
10.2.3 Address field variables. 29
10.2.3.1 Address field extension bit (EA). 30
10.2.3.2 Command/Response field bit (C/R) . 30
10.2.3.3 Service Access Point Identifier (SAPI). 30
10.2.3.4 Terminal Endpoint Identifier (TEI). 30
10.2.3.4.1 TEI for broadcast data link connection. 30
10.2.3.4.2 TEI for point-to-point data link
connection. 30
10.2.4 Control field formats . 30
10.2.4.1 Information transfer (I) format. 30
10.2.4.2 Supervisory (S) format . 30
10.2.4.3 Unnumbered (U) format. 30
10.2.5 Control field parameters and associated state variables. 31
10.2.5.1 Poll/Final bit. 31
10.2.5.2 Multiple frame operation - variables and sequence
numbers . 31
10.2.5.2.1 Modulus. 31
10.2.5.2.2 Send state variable V(S) . 31
10.2.5.2.3 Acknowledge state variable V(A) . 31
10.2.5.2.4 Send sequence number N(S). 31
10.2.5.2.5 Receive state variable V(R). 31
10.2.5.2.6 Receive sequence number N(R). 31
10.2.6 Frame types. 31
10.2.6.1 Commands and responses. 31
10.2.6.2 Information (I) command. 32
Page 5
TBR 33: December 1997
10.2.6.3 Set Asynchronous Balanced Mode Extended (SABME)
command.32
10.2.6.4 DISConnect (DISC) command .32
10.2.6.5 Unnumbered Information (UI) command.32
10.2.6.6 Receive Ready (RR) command/response.33
10.2.6.7 REJect (REJ) command/response.33
10.2.6.8 Receive Not Ready (RNR) command/response.33
10.2.6.9 Unnumbered Acknowledgement (UA) response .33
10.2.6.10 Disconnected Mode (DM) response.33
10.3 Provision of point-to-point signalling connections.33
10.4 Procedures for unacknowledged information transfer.33
10.4.1 Transmission of unacknowledged information.33
10.4.2 Receipt of unacknowledged information .33
10.5 Terminal Endpoint Identifier (TEI) management procedures.34
10.5.1 General.34
10.5.2 TEI assignment procedure .34
10.5.2.1 Expiry of timer T202 .34
10.5.3 TEI check procedure .34
10.5.4 TEI removal procedure.34
10.5.4.1 Action taken by the data link layer entity receiving the
MDL-REMOVE-REQUEST primitive .34
10.5.4.2 Conditions for TEI removal.34
10.5.5 TEI identity verify procedure.34
10.5.5.1 General.34
10.5.5.2 Operation of the TEI identity verify procedure .34
10.5.6 Formats and codes .34
10.6 Procedures for establishment and release of multiple frame operation .35
10.6.1 Establishment of multiple frame operation.35
10.6.1.1 General.35
10.6.1.2 Establishment procedures.35
10.6.1.2.1 Establishment initiation .35
10.6.1.2.2 Establishment response .35
10.6.1.3 Procedure on expiry of timer T200 .36
10.6.2 Termination of multiple frame operation.36
10.7 Procedures for information transfer in multiple frame operation .36
10.7.1 Transmitting I-frames .36
10.7.2 Receiving I-frames .36
10.7.2.1 P bit set to 1.36
10.7.2.2 P bit set to 0.36
10.7.3 Receiving acknowledgements.37
10.7.4 Receiving REJ frames.37
10.7.5 Receiving RNR frames.38
10.7.5.1 Receiving a valid RNR command or response.38
10.7.5.2 Expiry of timer T200 during "peer receiver busy" .38
10.7.5.3 Receiving a valid RNR command or response during
"peer receiver busy".39
10.7.5.4 Receiving a valid RR or REJ command or response
during "peer receiver busy".39
10.7.5.5 Appropriate supervisory response frame.39
10.7.6 Waiting acknowledgement .40
10.8 Re-establishment of multiple frame operation .40
10.9 Exception condition reporting and recovery.41
10.9.1 N(S) sequence error.41
10.9.2 Invalid frame condition .41
10.9.3 Frame rejection condition.41
10.9.4 Multiple-assignment of TEI value .41
10.10 List of system parameters.42
10.10.1 Timer T200.42
10.10.2 Maximum number of retransmissions (N200).42
10.10.3 Maximum number of octets in an information field (N201) .42
10.10.4 Maximum number of transmission of the TEI identity request message
(N202) .42
10.10.5 Maximum number of outstanding I-frames (k) .42
Page 6
TBR 33: December 1997
10.10.6 Timer T202 . 42
10.10.7 Layer 2 response time . 42
11 Layer 3 D-channel requirements . 43
11.1 Overview of call control . 43
11.1.1 Call states at the user side of the interface . 43
11.1.1.1 Null state (U0) . 43
11.1.1.2 Call initiated (U1). 43
11.1.1.3 Call proceeding (U3) . 43
11.1.1.4 Call present (U6). 43
11.1.1.5 Call received (U7) . 44
11.1.1.6 Connect request (U8). 44
11.1.1.7 Incoming call proceeding (U9) . 44
11.1.1.8 Active (U10) . 44
11.1.1.9 Disconnect request (U11) . 44
11.1.1.10 Disconnect indication (U12) . 44
11.1.1.11 Release request (U19). 44
11.1.2 Network call states. 44
11.1.2.1 Null state (N0) . 44
11.1.2.2 Call initiated (N1). 44
11.1.2.3 Outgoing call proceeding (N3) . 44
11.1.2.4 Call present (N6). 45
11.1.2.5 Call received (N7) . 45
11.1.2.6 Connect request (N8). 45
11.1.2.7 Incoming call proceeding (N9) . 45
11.1.2.8 Active (N10) . 45
11.1.2.9 Disconnect request (N11) . 45
11.1.2.10 Disconnect indication (N12) . 45
11.1.2.11 Release request (N19). 45
11.1.2.12 Call abort (N22). 45
11.1.3 States associated with the global call reference. 46
11.1.3.1 Call states at the user side of the interface. 46
11.1.3.1.1 Null (Rest 0) . 46
11.1.3.1.2 Restart (Rest 2). 46
11.1.3.2 Call states at the network side of the interface . 46
11.1.3.2.1 Null (Rest 0) . 46
11.1.3.2.2 Restart request (Rest 1). 46
11.2 Message functional definitions and content . 46
11.2.1 Alerting. 47
11.2.2 Call proceeding. 48
11.2.3 Connect . 48
11.2.4 Connect acknowledge . 49
11.2.5 Disconnect. 49
11.2.6 Release. 50
11.2.7 Release complete. 50
11.2.8 Setup . 51
11.2.9 Status. 52
11.2.10 Status enquiry. 52
11.2.11 Messages used with the global call reference. 52
11.2.11.1 Restart. 52
11.2.11.2 Restart acknowledge . 52
11.3 General message format and information elements coding . 53
11.3.1 Overview. 53
11.3.2 Protocol discriminator . 53
11.3.3 Call reference . 53
11.3.4 Message type. 53
11.3.5 Other information elements . 55
11.3.5.1 Coding rules. 55
11.3.5.1.1 Codeset 0. 55
11.3.5.2 Extensions of codesets. 56
11.3.5.3 Locking shift procedure. 56
11.3.5.4 Non-locking shift procedure . 56
11.3.5.5 Bearer capability . 56
Page 7
TBR 33: December 1997
11.3.5.6 Call state.58
11.3.5.7 Called party number .58
11.3.5.8 Called party subaddress.58
11.3.5.9 Calling party number.58
11.3.5.10 Calling party subaddress .60
11.3.5.11 Cause .61
11.3.5.12 Channel identification .61
11.3.5.13 Restart indicator.61
11.4 Call control procedures for the control of packet-mode access of the PH .62
11.4.1 Call establishment at the originating interface.62
11.4.1.1 Call request.62
11.4.1.2 Overlap sending.62
11.4.1.3 Call proceeding.62
11.4.1.4 Call confirmation indication.62
11.4.1.5 Call connected.63
11.4.2 Call establishment at the destination interface.63
11.4.2.1 Incoming call.63
11.4.2.2 Compatibility checking.63
11.4.2.3 Channel selection-destination.64
11.4.2.4 Overlap receiving.64
11.4.2.5 Call confirmation.64
11.4.2.6 Call accept.65
11.4.2.7 Active indication.65
11.4.2.8 Non-selected user clearing.65
11.4.3 Call clearing.65
11.4.3.1 Terminology.65
11.4.3.2 Exception conditions.65
11.4.3.3 Clearing initiated by the user .66
11.4.3.4 Clearing initiated by the network.66
11.4.3.4.1 Clearing when tones/announcements
provided .66
11.4.3.4.2 Clearing when tones/announcements
not provided .66
11.4.3.4.3 Completion of clearing .66
11.4.3.5 Clear collision .66
11.4.4 Call rearrangements.67
11.4.5 Call collisions.67
11.4.6 Handling of error conditions .67
11.4.6.1 Call reference procedural errors.67
11.4.6.2 Message type or message sequence errors .67
11.4.6.3 Duplicated information elements .67
11.4.6.4 Mandatory information element errors.67
11.4.6.4.1 Mandatory information element
missing.67
11.4.6.5 Non-mandatory information element errors.67
11.4.6.5.1 Unrecognized information element.68
11.4.6.5.2 Non-mandatory information element
content error .68
11.4.6.6 Status enquiry procedure.69
11.4.6.7 Receiving a STATUS message.69
11.4.7 User notification procedure .70
11.4.8 Restart procedure.70
11.5 TE timers .70
12 X.25.71
12.1 X.25 requirements .71
12.2 X.25 procedures .71
12.2.1 Data link protocol supporting the X.25 packet level protocol .71
12.2.2 X.25 packet level protocol .71
12.2.3 Outgoing and incoming virtual calls.71
12.2.4 Identification of X.25 terminals .71
Page 8
TBR 33: December 1997
Annex A (normative): TBR Requirements Table (TBR-RT) . 72
A.1 Guidance for completion of the TBR-RT . 72
A.2 General classification of requirements TBR-RT. 73
A.3 Layer 1 and overvoltage requirements TBR-RT. 75
A.3.1 On-demand layer 1 requirement tables. 75
A.3.2 Semi-permanent layer 1 requirement tables. 79
A.4 Layer 2 TBR-RT. 83
A.5 Layer 3 TBR-RT. 86
Annex B (normative): Conformance test principles for layer 1 . 88
B.1 Scope and general information. 88
B.1.1 Scope . 88
B.1.2 General information. 88
B.1.3 Definitions and abbreviations . 88
B.1.4 Environmental conditions . 88
B.1.5 Test case selection . 89
B.2 Electrical characteristics tests . 92
B.3 Functional characteristic tests . 92
B.4 Interface procedure tests. 92
B.4.1 The TTCN Graphical form (TTCN.GR). 92
B.4.2 The TTCN Machine Processable form (TTCN.MP). 92
B.5 Power feeding. 93
Annex C (normative): Layer 2 tests . 94
C.1 The TTCN Graphical form (TTCN.GR) .94
C.2 The TTCN Machine Processable form (TTCN.MP) . 94
Annex D (normative): Layer 3 tests . 95
D.1 The TTCN Graphical form (TTCN.GR) .95
D.2 The TTCN Machine Processable form (TTCN.MP) . 95
Annex E (normative): Partial Protocol Implementation eXtra Information for Testing (PIXIT)
proforma . 96
E.1 Introduction. 96
E.2 References . 96
E.3 Proforma structure and contents . 96
E.4 Table/item identification. 96
E.5 Guidance on completing the PIXIT. 96
E.6 Environmental test conditions. 96
Page 9
TBR 33: December 1997
E.7 Layer 1 PIXIT .97
E.8 Layer 2 PIXIT .99
E.9 Layer 3 PIXIT .102
Annex F (informative): Justifications for the requirements in the TBR .104
F.1 Principles applicable to the whole TBR .104
F.1.1 General principles.104
F.1.2 Requirements versus definitions.104
F.1.3 Error conditions.104
F.1.4 General editorial changes to text from the base standards .105
F.1.5 Detailed list of changes with respect to the base standards.105
F.1.6 Untested requirements .106
F.1.7 Primitives .106
F.1.8 Supplementary services.106
F.1.9 Article 4(e) of the Directive.106
F.2 Changes with respect to TBR 3.106
F.2.1 Changes for layer 1.107
F.2.1.1 Protection requirements .107
F.2.1.2 Detailed list of changes with respect to TBR 3.107
F.2.2 Changes for layer 2 of the D-channel .108
F.2.3 Changes for layer 3 of the D-channel .109
Annex G (normative): List of supported telecommunication services .112
G.1 Basic telecommunication services .112
G.2 Supplementary services for the access connection.112
Annex H (informative): Examples for TE access configurations with small sets of requirements .113
Annex J (informative): Bibliography.115
History.116
Page 10
TBR 33: December 1997
Blank page
Page 11
TBR 33: December 1997
Foreword
This Technical Basis for Regulation (TBR) has been produced by the Signalling Protocols and Switching
(SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This TBR resulted from a mandate from the Commission of the European Community (CEC) to provide
harmonized standards for the support of the Council Directive 91/263/EEC ("The Terminal Equipment
Directive").
Annex F provides information relating to the articles of the Directive 91/263/EEC.
Annexes A, B, C, D, E and G are normative whereas annexes F, H and J are informative.
Overview of the Abstract Test Suites (ATSs)
This TBR is accompanied by the following ATSs (see annexes B, C and D):
- T33L1_7 (layer 1);
- T33L2_3 (layer 2);
- T33L3_5 (layer 3).
Page 12
TBR 33: December 1997
Blank page
Page 13
TBR 33: December 1997
1 Scope
This Technical Basis for Regulation (TBR) specifies the technical requirements under articles 4(c) to 4(f)
of Directive 91/263/EEC for Terminal Equipment (TE) to be attached to the pan-European Integrated
Services Digital Network (ISDN) at an interface at the T reference point or coincident S and T reference
point for a basic access. These requirements are intended to ensure that the essential requirements of
Directive 91/263/EEC continue to be met when up to eight Terminal Equipments are simultaneously
connected at the coincident S and T reference point. These requirements are taken from TBR 3 [9],
ETS 300 007 [10], ETS 300 047-3 [12], ETS 300 012 [11], ETS 300 102-1 [13] and ETS 300 125 [14].
This TBR does not contain the essential requirements of Article 4 (g) for interworking via the public
network, and so does not provide any guarantee of correct terminal-to-terminal operation.
NOTE 1: Although this TBR provides the technical attachment requirements, it does not contain
the full specification of the user side of the ISDN user-network interface. Important
information necessary for correct working can be found only in the base standards
mentioned above.
This TBR specifies these requirements for TE that:
a) access Packet Handler (PH) of an ISDN through either on-demand B- or D-channel mode or
semi-permanent B-channel mode basic services (case B of X.31) and those supplementary
services that are specified in annex G; and
b) is capable of handling either incoming calls only, outgoing calls only or both incoming and outgoing
calls.
This TBR applies to all TE that is intended for connection to the forms of ISDN access referred to above,
irrespective of whether the TE provides additional interfaces, telecommunications services or functions for
which other TBRs or national approval requirements apply.
This TBR does not specify the requirements for a packet mode TE that uses on-demand B-channel circuit
mode access (case A of X.31); the requirements for such a TE are contained in TBR 3 [9].
NOTE 2: This TBR is not applicable to TE which may be supplied in some countries for
connection to an ISDN telecommunications service corresponding to, but not
compatible with, the pan-European ISDN basic access standards.
2 Normative references
This TBR incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this TBR only when incorporated in it by amendment or revision. For undated references the
latest edition of the publication referred to applies.
[1] CCITT Recommendation G.117 (1988): "Transmission aspects of unbalance
about earth (Definitions and methods)".
[2] CCITT Recommendation I.411 (1988): "ISDN user-network interfaces -
Reference configurations".
[3] CCITT Recommendation I.430 (1988): "Basic user-network interface - Layer 1
specification".
[4] EN 60603-7 (1993): "Connectors for frequencies below 3 MHz for use with
printed boards; Part 7: Detail specification for connectors, 8-way, including fixed
and free connectors with common mating features; (IEC 603-7:1990)".
[5] ISO/IEC 9646-1: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 1: General Concepts".
Page 14
TBR 33: December 1997
[6] ISO/IEC 9646-2: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 2: Abstract Test Suite
specification".
[7] ISO/IEC 9646-3: "Information technology - Open Systems Interconnection -
Conformance testing methodology and framework - Part 3: The Tree and
Tabular Combined Notation (TTCN)".
[8] TBR 2 (1997): "Attachment requirements for Data Terminal Equipment (DTE) to
connect to Packet Switched Public Data Networks (PSPDNs) for CCITT
Recommendation X.25
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...