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.
---------------------- Page: 1 ----------------------
SIST TBR 033:2000
---------------------- Page: 2 ----------------------
SIST TBR 033:2000
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: 3 ----------------------
SIST TBR 033:2000
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: 4 ----------------------
SIST TBR 033:2000
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: 5 ----------------------
SIST TBR 033:2000
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: 6 ----------------------
SIST TBR 033:2000
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: 7 ----------------------
SIST TBR 033:2000
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: 8 ----------------------
SIST TBR 033:2000
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 Sta
...
SLOVENSKI STANDARD
SIST TBR 033:2000
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)
SIST TBR 033:2000 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST TBR 033:2000
---------------------- Page: 2 ----------------------
SIST TBR 033:2000
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: 3 ----------------------
SIST TBR 033:2000
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: 4 ----------------------
SIST TBR 033:2000
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: 5 ----------------------
SIST TBR 033:2000
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: 6 ----------------------
SIST TBR 033:2000
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: 7 ----------------------
SIST TBR 033:2000
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: 8 ----------------------
SIST TBR 033:2000
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
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.