D.3 An example of a coding for group 3 facsimile (9,6 kbit/s, transparent)

24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS

D.3.1 Mobile station to network direction

8

7

6

5

4

3

2

1

0

0

0

0

0

1

0

0

octet 1

Bearer capability IEI

0

0

0

0

0

1

1

1

Length of the bearer capability contents

octet 2

1

0

1

0

0

0

1

1

not

ext

full rate

only MS

GSM

circ.

mode

facsimile

group 3

octet 3

1

0

1

1

1

0

0

0

not

ext

comp-ress.

unstructured

full

dupl.

pt to

pt

no NIRR

de-mand

octet 4

1

0

0

0

0

0

0

1

not

ext

access id.

no rate

adaption

I.440/450

octet 5

0

0

1

0

0

0

0

0

ext

layer 1

default layer 1

sync

octet 6

0

0

0

1

0

1

0

1

ext

(syn)

no

neg

(syn)

9.6 kbit/s

octet 6a

0

1

1

0

0

0

1

1

ext

16 kbit/s

inter. rate

no

NICtx

no

NICrx

(parity) none

octet 6b

1

0

0

0

0

0

1

1

not

ext

transparent

none

(modem type)

octet 6c

D.3.2 Network to mobile station direction

8

7

6

5

4

3

2

1

0

0

0

0

0

1

0

0

octet 1

Bearer capability IEI

0

0

0

0

0

1

1

1

Length of the bearer capability contents

octet 2

1

0

1

0

0

0

1

1

not

ext

spare

spare

GSM

circ.

mode

facsimile

group 3

octet 3

1

0

1

1

1

0

0

0

not

ext

comp-ress.

unstructured

full

dupl.

pt to

pt

no NIRR

de-mand

octet 4

1

0

0

0

0

0

0

1

not

ext

access id.

no rate

adaption

I.440/450

octet 5

0

0

1

0

0

0

0

0

ext

layer 1

default layer 1

sync

octet 6

0

0

0

1

0

1

0

1

ext

(syn)

no

neg

(syn)

9.6 kbit/s

octet 6a

0

1

1

0

0

0

1

1

ext

16 kbit/s

inter. rate

no

NICtx

no

NICrx

(parity) none

octet 6b

1

0

0

0

0

0

0

0

not

ext

transparent

none

(modem type)

octet 6c

Annex E (informative):
Comparison between call control procedures specified in 3GPP TS 24.008 and ITU-T Recommendation Q.931

This annex summarizes a comparison of the procedures for call control as specified in ITU-T Recommendation Q.931 (blue book) and 3GPP TS 24.008.

If no comment is given, it means that the procedures specified in ITU-T Recommendation Q.931 and 3GPP TS 24.008 are similar. However, it should be noted that even in such cases the procedures may be described in slightly different ways in the two documents.

Table E.1/3GPP TS 24.008: Circuit-switched call control procedures

Procedure

Q.931

3GPP TS 24.008

Call establishment at the originating interface

5.1

5.2.1

– call request

5.1.1

5.2.1.1.1

en-bloc sending only

– B-channel selection originating

5.1.2

not applicable

– overlap sending

5.1.3

not supported

– invalid call information

5.1.4

5.2.1.1.2

– call proceeding, en-bloc sending

5.1.5.1

5.2.1.1.3

– call proceeding, overlap sending

5.1.5.2

not supported

– notification of interworking at the originating interf.

5.1.6

5.2.1.1.4

– call confirmation indication

5.1.7

5.2.1.1.5

– call connected

5.1.8

5.2.1.1.6

– call rejection

5.1.9

5.2.1.1.7

– transit network selection

5.1.10

5.2.1.1.8

Table E.1/3GPP TS 24.008: Circuit-switched call control procedures (continued)

Procedure

Q.931

3GPP TS 24.008

Call establishment at the destination interface

5.2

5.2.2

– call indication

5.2.1

5.2.2.1

procedure for multiple terminal configuration not required, i.e. delivery of SETUP messages on broadcast data links is not supported

– compatibility checking

5.2.2

5.2.2.2

equivalent, except that delivery of SETUP messages on broadcast data links is not supported

– B-channel selection destination

5.2.3

not applicable

– overlap receiving

5.2.4

not supported

– call confirmation information

5.2.5

5.2.2.3

equivalent, except that delivery of SETUP messages on broadcast data links is not supported

– notification of interworking at the terminating interf.

5.2.6

5.2.2.4

– call accept indication

5.2.7

5.2.2.5

– active indication

5.2.8

5.2.2.6

equivalent, except that SETUP messages are not sent on broadcast data links

– non-selected user clearing

5.2.9

not applicable

Table E.1/3GPP TS 24.008: Circuit-switched call control procedures (continued)

Procedure

Q.931

3GPP TS 24.008

Call clearing

5.3

5.4

– terminology

5.3.1

5.4.1

terminology adapted to A/Gb mode and GERAN Iu mode applications

– exception conditions

5.3.2

5.4.2

only case a) of clause 5.3.2 of Rec. Q.931 applies. All other exceptions apply to functions which are not relevant to A/Gb mode and GERAN Iu mode

– clearing initiated by the user/MS

5.3.3

5.4.3

– clearing initiated by the network

5.3.4

5.4.4

– clearing when tones/announcements are provided

5.3.4.1

5.4.4.1.1 and 5.4.4.2.1

exception: if not already connected, the traffic channel is connected in order to provide the tone/announcement

– clearing when tones/announcements are not provided

5.3.4.2

5.4.4.1.2 and 5.4.4.2.3

– completion of clearing

5.3.4.3

5.4.4.1.3 and 5.4.4.2.5

Clear collision

5.3.5

5.4.5

Table E.1/3GPP TS 24.008: Circuit-switched call control procedures (continued)

Procedure

Q.931

3GPP TS 24.008

In-band tones and announcements

5.4

5.5.1

Restart procedure

5.5

not supported

Call rearrangements

5.6

5.3.4

call suspension/call re-establishment not supported on the radio path.

The functions, if required, are to be supported locally in the MS. On the radio interface, the notification procedure of Rec. Q.931 (clause5.6.7) applies

Call collisions

5.7

5.5.2

call collisions cannot occur

Emergency call establishment at the originating interface

not specified

not supported

5.2.1.2

In-call modification

Annex O

Rec. Q.931 is incomplete with regard to in-call modification procedures

5.3.4

DTMF protocol control procedures

not specified

not supported

5.3.3

Call re-establishment

not specified

not supported

5.5.4

Status enquiry procedure

5.8.10, 5.8.11

5.5.3

User-to-user signalling

7

3GPP TS 24.010 [21]

User notification procedure

5.9

5.3.1

Annex F (informative):
A/Gb mode specific cause values for radio resource management

See 3GPP TS 44.018 [84].

Annex G (informative):
3GPP specific cause values for mobility management

This annex describes the cause values for the mobility management procedures for non-GPRS services (MM) and GPRS services (GMM). Clauses G1 to G5 are valid for both MM and GMM. However, the following codes are applicable for non-GPRS services only:

#38 Call cannot be identified

Clause G.6 applies only for GMM procedures.