The ISDN-Protocol

Chapter 4a
This chapter is designed to provide the student with a reference about the protocols used for ISDN-Primary Rate Access.

OBJECTIVES:
Upon completion of this chapter the student will be able to: describe the ISDN layer model describe the function of the different layers within this model describe the elements a layer3 message consists of describe the function of timers on layer3 describe simple ISDN traffic cases on layer3 level

GSM ISDN-E Accesses and Services Operation in MSC/VLR

In t

t io e n na
Bl n a

lly
EN/LZT 123 1207 R1A

4a The ISDN-Protocol

4a The ISDN-Protocol
Table of Contents
Topic Page

SCOPE...............................................................................................133 LAYER 1 ............................................................................................135 LAYER 2 ............................................................................................138 LAYER 3 ............................................................................................141

EN/LZT 123 1207 R1A

GSM ISDN-E Accesses and Services Operation in MSC/VLR

In t

t io e n na
Bl n a

lly

ii

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

SCOPE
This chapter is intended to be used as a reference. It does not replace the specifications it is extracted from. Although the signaling and addressing principles for Primary Rate Access (PRA) and Basic Access (BA) are quite similar, this chapter covers those aspects with a main focus on PRA. The S-reference point is not a main issue covered in this chapter.

Conventions
In order to provide help for reading the relevant specifications and to avoid misunderstandings the important basics are explained shortly.

ISDN-Reference points
The ISDN-reference model defines functional units and reference points that divide those units. The functional units and the reference points are shown in Figure 4a-1.

TE
NT2 TA

NT
LT/ET NT1

T S

Figure 4a-1: Functional units and reference points of the ISDN reference model.

In general, signaling is performed between LT/ET and TE. The NT1 is transparent for signaling and performs only a conversion of layer1. NT2 provides switching and supervision functions and serves as an end-point of signaling from the LT/ET point of view. The logical communication queue can be described as follows: LT/ET <=> NT2 <=> TE.

The layer model

Communication in ISDN is based on a 3-layer model as shown in Figure 4a-2.

EN/LZT 123 1207 R1A

133

GSM ISDN-E Accesses and Services Operation in MSC/VLR

In communication between two entities, there can be more than one instance of each layer. Each instance is communicating with a peer instance in the other entity. All of these layer instances are managed by one layer-management instance per entity. The layer management instance can also communicate to its peer instance via layer1 3. Layer 1 is also called the physical layer and layer 2 is also called the data link layer. The layer-to-layer and the layer-to-management communication within one entity is performed by using so-called primitives. These primitives are a set of basic commands for usage within one entity and should not be mixed up with protocol elements in peer-to-peer communication.

Layer management

application processes

Layer 2 instances

Layer 3 Layer 2 Layer 1

physical interf ace

Layer 2 Layer2 management

Figure 4a-2: The ISDN Layer-model

Primitives
In the ETSI-specifications there are naming conventions for these primitives. Some examples are shown in Table 1 Primitive
DL-UNIT DATA-REQUEST

Direction
Layer3 -> Data Link Layer

Function
Request a message unit to be sent using unacknowledged information transfer service Request a message unit to be sent using unacknowledged information transfer service to the peer-management instance Request activation of the physical layer (layer1)

MDL-UNIT DATA-REQUEST

Management -> Data Link Layer

PH-ACTIVATE-REQUEST

Data Link Layer-> Physical Layer

Table 1: Examples for primitives

134 EN/LZT 123 1207 R1A

4a The ISDN-Protocol

LAYER 1
This section covers supervision principles on the 2Mbit/s PCM30 link between LT/ET and NT1/NT2 as specified in ITU-T Rec. G.703 and G.704

Frame structure
The PCM30 frame consists of 32 time-slots (TS). Each TS contains 8 bit and is transferred 8000 times a second. This results in a data rate of (8bit/TS 32 TS/frame) 8000 frames/s =2048 kbit/s.
32 channels x 8 bit = 256 bit

0 1 15 16 17 30 31
Synchronization and quality supervision D-channel signalling

30 traffic channels

Figure 4a-3

TS-0 is used for synchronization and layer1 quality supervision. Frame synchronization is provided by a synchronization word transmitted in every even numbered frame (0,2,). The first TS of odd numbered frame contains information about the remoteend status (Remote Alarm Indication, RAI ) or even more detailed information about the location of an error that occurred.

CRC-4
The latter case is available when so called CRC-4 supervision is used. CRC-4 supervision of PCM-frames also allows quality supervision, by means of countable bit-errors.The CRC-4 checksum is calculated for so called Sub-Multi-Frames (SMF). 1 SMF consists of 8 PCM frames. Each even numbered frame carries one bit of the 4-bit CRC word (CRC= Cyclic Redundancy Check). The bit-order in an SMF pair is shown in Table 2. 1 multi-frame (MF) consists of two SMF. The MF- alignment word (001011) is carried in bit 1 of the first 6 odd-numbered frames. This enables the receiving end to locate the MF. If one

EN/LZT 123 1207 R1A

135

GSM ISDN-E Accesses and Services Operation in MSC/VLR

side needs to transmit RAI to the remote side, it sets the A-bits to binary 1.
SMFNo.
TS-0 Bit 1 C1 0 C2 0 C3 1 C4 0 C1 1 C2 1 C3 E C4 E TS-0 Bit 2 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 TS-0 Bit 3 0 A 0 A 0 A 0 A 0 A 0 A 0 A 0 A TS-0 Bit 4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 1 Sa4 TS-0 Bit 5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 1 Sa5 TS-0 Bit 6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 0 Sa6 TS-0 Bit 7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 1 Sa7 TS-0 Bit 8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8 1 Sa8

Frame No.

0 S M F 1 1 2 3 4 5 6 7 8 S M F 2 9 10 11 12 13 14 15

Table 2 : The table shows the bit order in TS-0 when using CRC-4 supervision.

The CRC-word (C1=MSB) transmitted is always to check the contents of the last received SMF. If the receiving side finds an SMF faulty, it has to set the E-bits in the next transmitted MF according to Table 3. The received E-bits are always evaluated, even if the frame is found faulty by the CRC-check.

136

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

Sa-bits
The bits Sa4 - Sa8 are used as spare-bits. They can be used to point out the source of an error in order to make maintenance activities more effective1. E1 Bit (Frame13) 1 1 0 0 E2 Bit (Frame 13) 1 0 1 0 CRC-Result Last SMF-1 fault free Last SMF-2 fault free Last SMF-1 fault free Last SMF-2 faulty Last SMF-1 faulty Last SMF-2 fault free Last SMF-1 faulty Last SMF-2 faulty

Table 3: Meaning of E-Bits in CRC-4 multi-frame

Using CRC-4 check means to have the number of bit-faults available. With this input, the following values can easily be calculated: Bit Fault Frequency (BFF) Disturbance Frequency (DF) Errored Second (ES) (second with faults in parts per million) Severely Errored Second (SES) Degraded Minute (DM)

If the quality of a line reaches a set low-limit value, the operator can be notified in order to take the line out of service.

In the ERICSSON implementation these bits are used for Sectionalized Supervision

EN/LZT 123 1207 R1A

137

GSM ISDN-E Accesses and Services Operation in MSC/VLR

LAYER 2
The ISDN layer2 is also referred as the User-Network InterfaceData Link Layer. In general terms, the tasks of layer2 are: Provision of end-to-end addressing Provision of negotiation mechanisms for the assignment of logical addresses Provision of error-free data transmission Identification of TEs

Layer 2 Addressing
The address of a layer 2 entity consists of two parts: TEI-value SAPI-value

On the user side, the TEI-value identifies the TE. With only few exceptions, it can be considered as a physical address. On the network side, the TEI identifies a layer 2 process in the ET. The SAPI-value identifies the service access point (SAP) towards layer 3 within this layer 2 instance. In ISDN, the layer 3 offers several different services. The SAPI value determines the service wanted. The addressing of two different TEs on different SAPIs is shown in Figure 4a-4.

Layer 3 Layer 2 Layer 1

TEI=68 SAPI=63

Layer 3 Layer 2 Layer 1

TEI=72 SAPI=16

TEI=127 SAPI=0

D-Channel

Figure 4a-4: The picture shows the addressing of two TEs, one with TEI 68 and the other with TEI 72 on different SAPIs.

The protocol used on layer2 is called LAPD (Link Access Procedure for D-channels) and is derived from the HDLC
138 EN/LZT 123 1207 R1A

4a The ISDN-Protocol

protocol. The set of primitives and the communication mechanisms of the LAPD protocol are not discussed in this document. For detailed information refer to [3.]or to Q.921. The structure of a layer2 address field is shown in Figure 4a-5.

Layer2 frame structure

A layer2 frame containing an information field (e.g. layer3 information) looks like the following:
8 1 7 0 4 3 Flag 0 0 0 0 Address (high order octet) Address (low order octet) Control Control Information 6 5 2 0 1 1
Octet

1 2 3 4 5

FCS (first octet) FCS (second octet) Flag 0 0 0 0

N-2 N-1 0 1 N

Table 4: A layer2 frame containing an information field

The address field can be found in octet 2 and 3 in the layer2 frame. It contains the SAPI and the TEI value. The TEI field is able to code an address space of 128.
8 7 6 5 SAPI TEI 4 3 2 1 C/R EA=0 EA=1 Octet 2 Octet 3

Figure 4a-5: LAPD address field

EN/LZT 123 1207 R1A

139

GSM ISDN-E Accesses and Services Operation in MSC/VLR

The C/R bit indicates whether the frame contains a command or a response. The usage of this bit is shown in Table 5.
Command/Response Command Response Direction Network side user side User side network side Network side user side User side network side C/R value 1 0 0 1

Table 5: Usage of the C/R-bit

The values for the SAPI and for the TEI are not free of choice, but have to be chosen according to Table 6 and Table 7.
SAPI Value 0 1-15 16 17-31 63 All others Related layer 3 or management entity Call control procedures Reserved for future standardization Packet communication conforming to X.25 level 3 procedures Reserved for future standardization Layer 2 management procedures Not available for Q.921 procedures

Table 6: SAPI- values for layer 3 services

TEI Value 00-630 64-126

User Type Non-automatic TEI assignment user equipment Automatic TEI assignment user equipment

Table 7: Assignment rules for TEI-values

For single point-to-point connections (e.g. connection of PABX) TEI 0 is the recommended value (see [2.]). The administration and the addressing of TEs in this case is done by the NT2 of the PABX.

140

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

LAYER 3
This chapter gives examples about different traffic cases seen from the layer 3 point-of-view as well as an overview concerning the structure of layer3 messages. The layer3 information is carried in the layer2 information field. The size of this information field depends on the type of message. For different message types there can be a different number of additional information elements belonging to this message. The general format of a layer3 message is shown in Table 8.

Layer3 message format

8 7 6 5 4 3 2 1 1 2
3

Protocol discriminator 0 0 0 0
Length of call reference value (oct).

Call reference value 0 Message type

Other information elements as required

Table 8: Layer3 message format

The protocol discriminator determines the protocol variant that must be applied to this message. These can either be national variants or other protocols like QSIG (protocol for inter-PABX communication). The call reference identifies a call or a service transaction on layer3. This identification is necessary due to the fact that there can be several active calls/transactions on one layer2 connection. The length of the call reference is given in the second octet and may vary, depending on the network and type of access. The default minimum length for BA is 1, for PRA 2 octets. Other values can be used if supported by the network. After the associated call/service transaction is cleared, the call reference value may be used to identify another action.

Information elements
The message type describes the kind of message, similar to a command, and is followed by a various number of information elements (comparable to command-parameters). These information elements are either optional or mandatory. Most information element can have a variable number of octets. Therefore each information element contains a length identifier
EN/LZT 123 1207 R1A 141

GSM ISDN-E Accesses and Services Operation in MSC/VLR

in the first octet of the associated data. An example for a layer3 frame carrying the message type SETUP is given in Figure 4a-6. According to the ETSI recommendation, there are different coding sets of information elements in order to allow national or private functional extensions. A switch between these coding sets can be achieved by using a so called "shift operator". This shift operator ("1001Lxxx") can either be valid for all following information elements or only for the next information element, depending on the setting of a "locking bit" (L). Caution: When referring the ETSI specification one has to distinguish carefully between message types and information elements for packet and for circuit switched data Figure 4a-6 shows the structure of a layer2 frame carrying a layer3 SETUP message with all mandatory and some optional information elements.
8 7 6 5 4 3 2 1

Message type

Layer2
8 1 7 0 4 3 2 Flag 0 0 0 0 0 Address (high order octet) Address (low order octet) Control Control Information 6 5 1 1
Octet

Layer3

0 0

0 0

0 0

0 0

0 0

1 1

0 0

1 0

-> SETUP -> Bearer capability

length of bearer capability contents (= 12 t)

1 2 3 4
8 7 6 5 4 3 2 1 1 2
3

->Channel Identification

Length of channel identification t t

-> Called party number

Protocol discriminator 0 0 0 0
Length of call reference value (oct).

Length of called party number contents

FCS (first octet) FCS (second octet) Flag 0 0 0 0

N-2 N-1 0 1 N

Call reference value 0 Message type

->Calling party number

Other information elements as required

Length of calling party number contents

Figure 4a-6: A layer3 frame with message type SETUP contained in a layer2 frame.

142

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

Shift operator
The complete set of information elements of code-set 0 (which is the ETSI default code-set that is active if no shift operator is used) for message type SETUP can be found in Table 9. For detailed information on the contained information elements please refer to [3.]
Message type: SETUP Significance: global Direction: both Information element Protocol discriminator Call reference Message type Sending complete Bearer capability Channel identification Network specific facility Display Keypad facility Calling party number Calling party subaddress Called party number Called party subaddress Transit network selection Low layer compatibility High layer compatibility Reference (subclause) 4.2 4.3 4.4 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 4.5 Direction Both Both Both Both Both Both Both nu un Both Both Both Both un Both Both Type M M M O (Note 1) M (Note 2) M O (Note 3) O (Note 4) O (Note 6) O (Note 7) O (Note 8) O (Note 9) O (Note 10) O (Note 11) O (Note 12) O (Note 13) Length 1 2-* 1 1 6-8 3-* 2-* (Note 5) 2-34 2-* 2-23 2-* 2-23 2-* 2-18 2-5

Table 9: Information elements for message type SETUP

Timers
In order to avoid deadlock situations, there are timers for nearly every transaction started either in the ET as well as in the TE. If a message is issued, the timer is started. If the appropriate response is not received before the expiry of this timer, action is taken independently. There are different timers for the network side (ET) and for the user side (TE/NT2). A summary of these timers on the network and on the user side is shown in Table 10 to Table 13.

EN/LZT 123 1207 R1A

143

GSM ISDN-E Accesses and Services Operation in MSC/VLR

Timer number T301

Time-out value Minimum 3 min 10-15 s (Note 5)

State of call Call received Overlap sending

Cause for start

Normal stop

At the first expiry Clear call

At the second expiry Timer is not restarted Timer is not restarted

Crossreference (Note 2)

ALERT received SETUP ACK sent Receipt of INFO, restarts T302

CONNECT received

T302

With sending complete indication, or network alert, or connect request received

T303

4s (Note 1)

Call present

SETUP sent

T304

20 s (provisional values)

Overlap receiving

T305

30 s

Disconnect indication

T306

30 s (Note 6)

Disconnect indication

SETUP ACK received. Sending of INFO restarts T304 DISC without progress indicator No. 8 sent DISC with progress indicator No. 8 sent

ALERT, CONNECT CALL PROC or SETUP ACK received, REL COMPLETE received if SETUP sent on point-point data link Send INFO; receive CALL PROC, ALERT or CONNECT REL or DISC received

Clear if call information determined to be definitely incomplete; else send CALL PROC Retransmit SETUP; restart T303. If REL COMPLETE has been received, clear the call

Mandatory

Clear network connection. Enter call abort state

Mandatory

Clear the call

Timer is not restarted

Network sends REL

Timer is not restarted

Mandatory only if 5.2.4 implement ed Mandatory

REL or DISC received

Stop the tone/announceme nt. Send REL

Timer is not restarted

T307

3 min

Null

SUSPEND ACK sent

RES ACK sent

T308

4s (Note 1)

Release request

REL sent

REL COMPLETE or REL received

Cleare the network connection. Release call identity Retransmit REL and restart T308

Timer is not restarted

Mandatory when inband tones/anno uncements are provided; see 5.4, 5.3.4.1, and Rec. I.300Series Mandatory

T309

90 s

Any stable state

Data link disconnection. Calls in stable states are not lost CALL PROC received

Data link reconnected

Clear network connection. Release B-channel and call reference

Place B-channel in maintenance condition Release call reference (Note 9) Timer is not restarted

Mandatory

Mandatory

T310

10 s (Note 7)

Incoming Call Proceeding

ALERT, CONNECT or DISC received. If DISC, retain cause and continue timing

Clear call in accordance with 5.2.5.3

Timer is not restarted

Mandatory

Table 10: Timers on the network side (1)

144

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

Timer number

Defaut time-out value T303 + 2 s

State of call

Cause for start

Normal stop

At the first expiry

At the second expiry

Crossreference

T312

Call Present, Call Abort, etc. Receiving segmented message Restart request

SETUP sent or resent on broadcast data link Message segment received RESTART sent

Timeout

(Note 4)

Timer is not restarted

Mandatory

T314

4s

Last message segment received

Discard message

Timer is not restarted

Mandatory see Annex H Mandatory when 5.5 is implement ed Mandatory when 5.5 is implement ed Optional. See 6.3

T316

2 min

RESTART ACK received

RESTART may be retransmitted several times Maintenance notification

RESTART may be retransmitted several times Timer is not restarted

T317

(Note 3)

Restart

RESTART received

Internal clearing of call references

T320

30 s (Note 8)

a) For Bchannel access: active b) For Dchannel access: null

T321

30 s

Any call state

a) For B-channel access: connection b)For Dchannel access: DL-ESTABLISHMENT Confirmation or DL-ESTABLISHMENT indication received c) Last logical channel, cleared received D-channel failure

Call request packet received; or incoming call packet delivered; or DISC received; or for Dchannel access DLRELEASE indication received

a) For B-channel access: disconnect link layer and initiate clearing b) For D-channel access: send DLRELEASE request

Timer is not restarted

Response to layer 3 message received

Send DL-ESTABLISHMENT request on both Dchannels

Timer is not restarted

Mandatory when Annex is implement ed Mandatory when 5.8.10 is implement ed

T322

4s

Any all state

STATUS ENQ sent

STATUS DISC REL or REL COMPLETE received

STATUS ENQ may be retransmitted several times

STATUS ENQ may be retransmitted several times

NOTES 1 This default value assumes the use of default values at layer 2 (i.e. N200 + 1] times T200). Whether these values should be modified when layer 2 default values are modified by an automatic negotiation procedure is for further study. 2 The network may already have applied an internal alerting supervision timing function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used. 3 The value of this timer is implementation dependent but should be less than the value of T316. 4 If in the call abort state, the call reference is released. Otherwise, no action is taken on expiry of timer T312. 5 The value of timer T302 may vary beyond these limits, e.g. as a result of called party number analysis. 6 The value of timer T306 may depend on the length of the announcement. 7 The value of timer T310 may be different in order to take into account the characteristics of a private network. 8 This value may vary by network-user agreement. 9 The restart procedures contained in 5.5 may be used on B-channels in the maintenance condition.

Table 11: Timers on the network side (2)

EN/LZT 123 1207 R1A

145

GSM ISDN-E Accesses and Services Operation in MSC/VLR

Timer number T301

Defaut time-out value Minimum 3 min.

State of call Call Delivered

Cause for start

Normal stop

At the first expiry Clear call

At the second expiry Timer is not restarted

Crossreference Mandator y when Annex D is implemented (Note 3) Mandator y only if 5.2.4 is implemented

ALERT received

CONNECT received

T302

15 s

Overlap receiving

SETUP ACK sent Restart when INFO received

T303

4s (Note 1)

Call Initiated

SETUP sent

T304

30 s

Overlap Sending

INFO sent Restarted when INFO sent again DISC sent REL sent

T305 T308

30 s 4s (Note 1)

Disconnect Request Release request

INFO received with sending complete indication; or internal alerting; or internal connection; or a determination that sufficient information has been received ALERT (Annex D), CONNECT (Annex D), SETUP ACK, CALL PROC or REL COMPLETE received CALL PROC, ALERT, CONNECT or DISC received REL or DISC received REL COMPLETE or REL received

Clear if call information determined to be incomplete; else send CALL PROC

Timer is not restarted

Retransmit SETUP; restart T303. If REL COMPLETE was received, clear the call (Annex D) DISC sent

Clear internal connection. Send REL COMPLETE. Enter Null state

Timer is not restarted

Mandator y when Annex D is implemented; otherwise optional Optional

REL sent Retransmit REL; and restart T308.

Timer is not restarted B-channel is placed in maintenance condition. Call reference released (Note 5) Timer is not restarted

Mandator y Mandator y

T309

90 s

Any stable state

T310 (Note 4)

30-120 s

Outgoing Call Proceeding

Data link disconnection. Calls in stable states are not lost CALL PROC received

Data link reconnected

Clear internal connection. Release B-channel and call reference Send DISC

Optional

ALERT, CONNECT, DISC, or PROGRESS received CONNECT ACK received Last message segment received RESTART ACK received

Timer is not restarted

T313 T314

4s (Note 1) 4s

T316

2 min

Connect request Receiving Segmented Message Restart Request

CONNECT sent Message segment received RESTART sent

Send DISC Discard message

Timer is not restarted Timer is not restarted RESTART may be retransmitted several times

RESTART may be retransmitted several times

T317

(Note 2)

Restart

RESTART received

Internal clearing of call reference

Maintenance notification

Timer is not restarted

T318

4s

Resume Request

RES sent

RES ACK or RES REJ received

Send RELEASE message with cause No. 102

Timer is not restarted

Mandator y when Annex D is implement ed Mandator y Not initially required Mandator y when 5.5 is implement ed Mandator y when 5.5 is implement ed Mandator y when 5.6 is implement ed

Table 12: Timers on the user side (1)

146

EN/LZT 123 1207 R1A

4a The ISDN-Protocol

Timer number T319

Defaut time-out value 4s

State of call Suspend Request

Cause for start

Normal stop

At the first expiry

At the second expiry Timer is not restarted

Crossreference Mandator y when 5.6 is implement ed Mandator y when Annex F is implement ed Mandator y when 5.8.10 is implement ed

SUSPEND sent

SUSPEND ACK or SUSP REJ received

Enter Active state. Notify user application

T321

30 s

Any call state

D-channel failure

Response to layer 3 message received

Send DL-ESTABLISHMENT request on both D-channels

Timer is not restarted

T322

4s

Any call state

STATUS ENQ sent

STATUS, DISC, REL, REL COMPLETE received

STATUS ENQ may be retransmitted several times

STATUS ENQ may be retransmitted several times

NOTES 1 2 2 3 5

This default value assumes the use of default values at layer 2, i.e. [N200 + 1] times T200. Whether these values should be modified when layer 2 default values are odified by an automatic negotiation procedure is for further study. The value of this timer is implementation dependent, but should be less than the value of T316. The user may already have applied an internal alerting supervision timing function, e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used. T310 is not started if progress indicator 1 or 2 has been delivered in the CALL PROCEEDING message or in a previous PROGRESS message. The restart procedures contained in 5.5 may be used on B-channels in the maintenance conditions.

Table 13: Timers on the user side (2)

Traffic cases
In order to give some help for the understanding of the principles of DSS1 signaling some traffic cases are shown in the following figures. To provide a better overview, not all timers and all possible actions are shown. The timers shown always belong to the network element to their left.

EN/LZT 123 1207 R1A

147

 148

GSM ISDN-E Accesses and Services Operation in MSC/VLR

Successful call attempt

TE A
Off hook dial tone some digits
T304

ET A
SETUP SETUPACK
T304 1 T302

ET B

TE B

INFO
T302

missing digits
T304

INFO
T302 T303

SETUP

ringing tone (2)

ALERT

ALERT

phone rings

SETUP conversation

phone rings

CONN

CONN

off hook

CONN ACK

CONN ACK

EN/LZT 123 1207 R1A

display of charging info

(1) ( 2)

FAC AOC

T304 is started on the TE and is not shown in the following diagrams At this time, the B-Channel is switched through

EN/LZT 123 1207 R1A 149

Unsuccessful call attempt (B-subscriber not responding)

TE A
Off hook dial tone some digits SETUP SETUPACK
T304 1 T302

ET A

ET B

TE B

INFO
T304 T302

missing digits

INFO
T304 T302 T303

SETUP

ringing tone (2)

ALERT

ALERT

phone rings

T301 1 T3031

SETUP

DISC
T305 T308

REL
4a The ISDN-Protocol

REL

REL COM

REL COM

(1)

T301 expiery before T303 expiery

 150

GSM ISDN-E Accesses and Services Operation in MSC/VLR

Unsuccessful call attempt (B-subscriber busy)

TE A
Off hook dial tone some digits SETUP SETUPACK INFO
T302 T302

ET A

ET B

TE B

missing digits

INFO
T303

SETUP

REL

busy

SETUP 1
T303

SETUP 1

busy tone

DISC
T305

REL ACK

REL REL ACK

EN/LZT 123 1207 R1A

(1)

ETS 300-102 recommends that the call should be cleared on second expiery of timer T303

EN/LZT 123 1207 R1A 151

Successful call attempt (direct connect

TE A ET A ET B

1)

TE B

D3-CONNECT request

SETUP
T303

SETUP

D3-CONNECT indication

CALL PROC D3-CONNECT confirm

CONN

CONN

D3-CONNECT response

CONN ACK

CONN ACK

4a The ISDN-Protocol

(1)

a direct connection without ALERT indication is set up for example between two computers

 152

GSM ISDN-E Accesses and Services Operation in MSC/VLR

Normal call release

TE A

ET A

ET B

TE B

on hook

DISC
T305

DISC

disconnection tone

REL Release call reference REL COM

T308

REL

on hook Release call reference

EN/LZT 123 1207 R1A

REL COM

4a The ISDN-Protocol

References:
[1.] ETS 300 011-1 Integrated Services Digital Network (ISDN) Primary rate User-Network Interface (UNI) Part 1: Layer 1 specification [2.] ETS 300 125 Integrated Services Digital Network (ISDN) User-network interface data link layer specification Application of CCITT Recommendations Q.920/I.440 and Q.921/I.441 [3.] ETS 300 102-1 Integrated Services Digital Network (ISDN) User-network interface layer 3 Specifications for basic call control [4.] ITU-T Recommendation Q. 931 Digital Subscriber Signalling System No. 1 (DSS1) User-network interface layer 3 Specifications for basic call control

EN/LZT 123 1207 R1A

153

GSM ISDN-E Accesses and Services Operation in MSC/VLR

In t

t io e n na
Bl n a

lly

154

EN/LZT 123 1207 R1A