Integrated Services Digital Network (ISDN); Attachment requirements for terminal equipment to connect to an ISDN using ISDN primary rate access

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

Digitalno omrežje z integriranimi storitvami (ISDN) - Priključitvene zahteve za terminalsko opremo za priključevanje na omrežje ISDN prek primarnega dostopa ISDN

General Information

Status
Published
Publication Date
30-Sep-2004
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Oct-2004
Due Date
01-Oct-2004
Completion Date
01-Oct-2004
Mandate

Buy Standard

Standardization document
TBR 004 E1:2004
English language
435 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

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

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

SIST TBR 004 E1:2004

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

SIST TBR 004 E1:2004
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: 3 ----------------------

SIST TBR 004 E1:2004
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: 4 ----------------------

SIST TBR 004 E1:2004
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: 5 ----------------------

SIST TBR 004 E1:2004
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: 6 ----------------------

SIST TBR 004 E1:2004
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: 7 ----------------------

SIST TBR 004 E1:2004
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: 8 ----------------------

SIST TBR 004 E1:2004
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.
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.