SIST ETS 300 940 E1:2005
(Main)Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface; Layer 3 specification (GSM 04.08 version 5.4.1)
Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface; Layer 3 specification (GSM 04.08 version 5.4.1)
This ETS specifies the procedures used at the radio interface (Reference Point Um, see GSM 04.02) for Call Control (CC), Mobility Management (MM) and Radio Resource (RR) management. When the notations for further study or FS or FFS are present in this document they mean that the indicated text is not a normative portion of this standard. These procedures are defined in terms of messages exchanged over the control channels of the radio interface. The control channels are described in GSM 04.03. The structured functions and procedures of this protocol and the relationship with other layers and entities are described in general terms in TS GSM 04.07.
Digitalni celični telekomunikacijski sistem (faza 2+) - Specifikacija tretje plasti za vmesnik mobilnega radia (GSM 04.08, različica 5.4.1)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-februar-2005
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D 6SHFLILNDFLMDWUHWMHSODVWL]D
YPHVQLNPRELOQHJDUDGLD *60UD]OLþLFD
Digital cellular telecommunications system (Phase 2+) (GSM); Mobile radio interface;
Layer 3 specification (GSM 04.08 version 5.4.1)
Ta slovenski standard je istoveten z: ETS 300 940 Edition 1
ICS:
33.070.01 Mobilni servisi na splošno Mobile services in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 940
TELECOMMUNICATION April 1997
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-030408QR3
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2+);
Mobile radio interface layer 3 specification
(GSM 04.08 version 5.4.1)
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
ETS 300 940 (GSM 04.08 version 5.4.1): April 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
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
Contents
Foreword .21
0 Scope.23
0.1 Scope of the Technical Specification.23
0.2 Application to the interface structures.23
0.3 Structure of layer 3 procedures .23
0.4 Test procedures.23
0.5 Use of logical channels.23
0.6 Overview of control procedures .24
0.6.1 List of procedures.24
0.7 Applicability of implementations .25
1 Normative references.27
2 Definitions and abbreviations .31
2.1 Random values.31
2.2 Vocabulary.31
3 Radio Resource management procedures .33
3.1 Overview/General.33
3.1.1 General .33
3.1.2 Services provided to upper layers.33
3.1.2.1 Idle mode.33
3.1.2.2 Dedicated mode .33
3.1.2.3 Group receive mode.34
3.1.2.4 Group transmit mode .34
3.1.3 Services required from data link and physical layers.34
3.1.4 Change of dedicated channels.34
3.1.4.1 Change of dedicated channels using SAPI = 0.34
3.1.4.2 Change of dedicated channels using other SAPIs than 0 .35
3.1.4.3 Sequenced message transfer operation.35
3.1.4.3.1 Variables and sequence numbers.35
3.1.4.3.1.2 Send sequence number N(SD).35
3.1.4.3.2 Procedures for the initiation, transfer
execution and termination of the
sequenced message transfer
operation .35
3.1.4.3.2.2 Transfer Execution.35
3.1.5 Procedure for Service Request and Contention Resolution.36
3.2 Idle mode procedures.37
3.2.1 Mobile Station side .37
3.2.2 Network side.37
3.2.2.1 System information broadcasting.37
3.2.2.2 Paging .38
3.3 RR connection establishment.38
3.3.1 RR connection establishment initiated by the MS.38
3.3.1.1 Entering the dedicated mode : immediate assignment
procedure.38
3.3.1.1.1 Permission to access the network.38
3.3.1.1.2 Initiation of the immediate assignment
procedure .39
3.3.1.1.3 Answer from the network .40
3.3.1.1.3.1 On receipt of a CHANNEL REQUEST
message.40
Page 4
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
3.3.1.1.3.2 Assignment rejection.41
3.3.1.1.4 Assignment completion.41
3.3.1.1.5 Abnormal cases.42
3.3.1.2 Entering the group transmit mode: uplink access
procedure.42
3.3.1.2.1 MS side .42
3.3.1.2.1.1 Uplink investigation procedure.42
3.3.1.2.1.2 Uplink access procedure .43
3.3.1.2.2 Network side .43
3.3.1.2.3 Abnormal cases.43
3.3.2 Paging procedure .43
3.3.2.1 Paging initiation by the network .43
3.3.2.2 Paging response.45
3.3.2.3 Abnormal cases.45
3.3.3 Notification procedure .46
3.3.3.1 Notification of a call.46
3.3.3.2 Joining a VGCS or VBS call.46
3.3.3.2 "Reduced NCH monitoring" mechanism .47
3.4 Procedures in dedicated mode and in group transmit mode.48
3.4.1 SACCH procedures.48
3.4.1.1 General.48
3.4.1.2 Measurement report.48
3.4.2 Transfer of messages and link layer service provision.49
3.4.3 Channel assignment procedure .49
3.4.3.1 Channel assignment initiation.50
3.4.3.2 Assignment completion.51
3.4.3.3 Abnormal cases.51
3.4.4 Handover procedure.52
3.4.4.1 Handover initiation.52
3.4.4.2 Physical channel establishment.54
3.4.4.2.1 Finely synchronized cell case.54
3.4.4.2.2 Non synchronized cell case.54
3.4.4.2.3 Pseudo-synchronized cell case .55
3.4.4.2.4 Pre-synchronized cell case .55
3.4.4.3 Handover completion.55
3.4.4.4 Abnormal cases.56
3.4.5 Frequency redefinition procedure .57
3.4.5.1 Abnormal cases.57
3.4.6 Channel mode modify procedure.57
3.4.6.1 Normal channel mode modify procedure.58
3.4.6.1.1 Initiation of the channel mode modify
procedure .58
3.4.6.1.2 Completion of channel mode modify
procedure .58
3.4.6.1.3 Abnormal cases.58
3.4.6.2 Channel mode modify procedure for a voice group call
talker .58
3.4.6.2.1 Initiation of the channel mode modify
procedure .58
3.4.6.2.2 Completion of mode change procedure.58
3.4.6.2.3 Abnormal cases.59
3.4.7 Ciphering mode setting procedure.59
3.4.7.1 Ciphering mode setting initiation .59
3.4.7.2 Ciphering mode setting completion .59
3.4.8 Additional channel assignment procedure.60
3.4.8.1 Additional assignment procedure initiation .60
3.4.8.2 Additional assignment procedure completion .60
3.4.8.3 Abnormal cases.60
3.4.9 Partial channel release procedure .61
3.4.9.1 Partial release procedure initiation.61
Page 5
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
3.4.9.2 Abnormal cases.61
3.4.10 Classmark change procedure .61
3.4.11 Classmark interrogation procedure.61
3.4.11.1 Classmark interrogation initiation.62
3.4.11.2 Classmark interrogation completion.62
3.4.12 Indication of notifications and paging informations.62
3.4.13 RR connection release procedure .63
3.4.13.1 Normal release procedure .63
3.4.13.1.1 Channel release procedure initiation in
dedicated mode and in group transmit
mode.63
3.4.13.1.2 Abnormal cases.64
3.4.13.2 Radio link failure in dedicated mode.64
3.4.13.2.1 Mobile side .64
3.4.13.2.2 Network side.64
3.4.13.3 RR connection abortion in dedicated mode.65
3.4.13.4 Uplink release procedure in group transmit mode.65
3.4.14 Receiving a RR STATUS message by a RR entity.65
3.4.15 Group receive mode procedures.65
3.4.15.1 MS side .65
3.4.15.1.1 Reception of the VGCS or VBS
channel.65
3.4.15.1.2 Monitoring of downlink messages and
related procedures .65
3.4.15.1.2.1 Channel assignment procedure.65
3.4.15.1.2.2 Frequency redefinition procedure .66
3.4.15.1.2.3 Channel mode modify procedure.66
3.4.15.1.2.4 Notification and paging information.66
3.4.15.1.2.5 Uplink status messages.66
3.4.15.1.2.6 Channel release message .66
3.4.15.1.3 Uplink reply procedure .66
3.4.15.1.4 Leaving the group receive mode .67
3.4.15.1.4.1 Returning to idle mode .67
3.4.15.1.4.2 Going to group transmit mode .67
3.4.15.2 Network side .67
3.4.15.2.1 Provision of messages on the VGCS
or VBS channel downlink.67
3.4.15.2.1.1 General .67
3.4.15.2.1.2 Provision of general information
messages.67
3.4.15.2.1.3 Provision of messages related to the
voice group call uplink channel .68
3.4.15.2.2 Release of the VGCS or VBS
Channels.68
3.4.15.3 Failure cases.69
4 Elementary procedures for Mobility Management.69
4.1 General .69
4.1.1 Type of MM procedures.69
4.1.2 MM sublayer states.70
4.1.2.1 MM sublayer states in the MS.70
4.1.2.1.1 Main states .70
4.1.2.1.2 Substates of the MM IDLE state.73
4.1.2.2 The update Status.74
4.1.2.3 MM sublayer states on the network side.75
4.2 Behaviour in MM IDLE State .76
4.2.1 Primary Service State selection .76
4.2.1.1 Selection of the Service State after Power On. .76
4.2.1.2 Other Cases.77
4.2.2 Detailed Description of the MS behaviour in MM IDLE State. .77
Page 6
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
4.2.2.1 Service State, NORMAL SERVICE.77
4.2.2.2 Service State, ATTEMPTING TO UPDATE .78
4.2.2.3 Service State, LIMITED SERVICE .78
4.2.2.4 Service State, NO IMSI.78
4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE .79
4.2.2.6 Service State, SEARCH FOR PLMN.79
4.2.2.7 Service State, RECEIVING GROUP CALL (NORMAL
SERVICE).79
4.2.2.8 Service State, RECEIVING GROUP CALL (LIMITED
SERVICE).80
4.2.3 Service state when back to state MM IDLE from another state .80
4.3 MM common procedures.81
4.3.1 TMSI reallocation procedure.81
4.3.1.1 TMSI reallocation initiation by the network.81
4.3.1.2 TMSI reallocation completion by the MS .81
4.3.1.3 TMSI reallocation completion in the network.82
4.3.1.4 Abnormal cases.82
4.3.2 Authentication procedure.83
4.3.2.1 Authentication request by the network.83
4.3.2.2 Authentication response by the MS.83
4.3.2.3 Authentication processing in the network.83
4.3.2.4 Ciphering key sequence number.83
4.3.2.5 Unsuccessful authentication.84
4.3.2.6 Abnormal cases.84
4.3.3 Identification procedure.85
4.3.3.1 Identity request by the network .85
4.3.3.2 Identification response by the MS.85
4.3.3.3 Abnormal cases.85
4.3.4 IMSI detach procedure.86
4.3.4.1 IMSI detach initiation by the MS .86
4.3.4.2 IMSI detach procedure in the network .86
4.3.4.3 IMSI detach completion by the MS.86
4.3.4.4 Abnormal cases.86
4.3.5 Abort procedure .87
4.3.5.1 Abort procedure initiation by the network .87
4.3.5.2 Abort procedure in the MS.87
4.3.6 MM information procedure.87
4.3.6.1 MM information procedure initiation by the network.87
4.3.6.2 MM information procedure in the MS .87
4.4 MM specific procedures.88
4.4.1 Location updating procedure.88
4.4.2 Periodic updating.89
4.4.3 IMSI attach procedure .90
4.4.4 Generic Location Updating procedure.90
4.4.4.1 Location updating initiation by the MS .90
4.4.4.1a Network Request for Additional MS Capability Information .90
4.4.4.2 Identification request from the network .90
4.4.4.3 Authentication by the network.90
4.4.4.4 Ciphering mode setting by the network .90
4.4.4.5 Attempt Counter.90
4.4.4.6 Location updating accepted by the network.91
4.4.4.7 Location updating not accepted by the network .91
4.4.4.8 Release of RR connection after location updating .92
4.4.4.9 Abnormal cases on the MS side.92
4.4.4.10 Abnormal cases on the network side .93
4.5 Connection management sublayer service provision.94
4.5.1 MM connection establishment.94
4.5.1.1 MM connection establishment initiated by the MS .94
4.5.1.2 Abnormal cases.97
4.5.1.3 MM connection establishment initiated by the network.98
Page 7
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
4.5.1.4 Abnormal cases.98
4.5.1.5 MM connection establishment for emergency calls.99
4.5.1.6 Call re-establishment.99
4.5.1.6.1 Call re-establishment, initiation by the
MS. 100
4.5.1.6.2 Abnormal cases. 101
4.5.1.7 Forced release during MO MM connection establishment. 102
4.5.2 MM connection information transfer phase. 102
4.5.2.1 Sending CM messages. 103
4.5.2.2 Receiving CM messages . 103
4.5.2.3 Abnormal cases. 103
4.5.3 MM connection release. 103
4.5.3.1 Release of associated RR connection. 103
4.5.3.2 Uplink release in a voice group call . 104
4.6 Receiving a MM STATUS message by a MM entity. 104
5 Elementary procedures for circuit-switched Call Control. 105
5.1 Overview . 105
5.1.1 General . 105
5.1.2 Call Control States. 108
5.1.2.1 Call states at the MS side of the interface. 108
5.1.2.1.1 Null (State U0). 108
5.1.2.1.2 MM Connection pending (U0.1). 108
5.1.2.1.3 Call initiated (U1). 108
5.1.2.1.4 Mobile originating call proceeding (U3)108
5.1.2.1.5 Call delivered (U4). 108
5.1.2.1.6 Call present (U6) . 108
5.1.2.1.7 Call received (U7). 108
5.1.2.1.8 Connect Request (U8). 108
5.1.2.1.9 Mobile terminating call confirmed (U9) 108
5.1.2.1.10 Active (U10). 108
5.1.2.1.11 Disconnect request (U11). 108
5.1.2.1.12 Disconnect indication (U12) . 109
5.1.2.1.13 Release request (U19). 109
5.1.2.1.14 Mobile originating modify (U26). 109
5.1.2.1.15 Mobile terminating modify (U27). 109
5.1.2.2 Network call states . 109
5.1.2.2.1 Null (State N0). 109
5.1.2.2.2 MM connection pending (N0.1) . 109
5.1.2.2.3 Call initiated (N1). 109
5.1.2.2.4 Mobile originating call proceeding (N3)109
5.1.2.2.5 Call delivered (N4). 109
5.1.2.2.6 Call present (N6) . 109
5.1.2.2.7 Call received (N7). 109
5.1.2.2.8 Connect request (N8). 110
5.1.2.2.9 Mobile terminating call confirmed (N9) 110
5.1.2.2.10 Active (N10). 110
5.1.2.2.11 {Not used}. 110
5.1.2.2.12 Disconnect indication (N12) . 110
5.1.2.2.13 Release request (N19). 110
5.1.2.2.14 Mobile originating modify (N26). 110
5.1.2.2.15 Mobile terminating modify (N27). 110
5.1.2.2.16 Connect Indication (N28). 110
5.2 Call establishment procedures. 110
5.2.1 Mobile originating call establishment. 111
5.2.1.1 Call initiation . 111
5.2.1.2 Receipt of a setup message . 112
5.2.1.3 Receipt of a CALL PROCEEDING message. 113
5.2.1.4 Notification of progressing mobile originated call. 113
Page 8
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
5.2.1.4.1 Notification of interworking in
connection with mobile originated call
establishment .113
5.2.1.4.2 Call progress in the PLMN/ISDN
environment.114
5.2.1.5 Alerting.114
5.2.1.6 Call connected.115
5.2.1.7 Call rejection.115
5.2.1.8 Transit network selection.115
5.2.1.9 Traffic channel assignment at mobile originating call
establishment.116
5.2.1.10 Call queuing at mobile originating call establishment.116
5.2.2 Mobile terminating call establishment.116
5.2.2.1 Call indication.116
5.2.2.2 Compatibility checking .117
5.2.2.3 Call confirmation .117
5.2.2.3.1 Response to SETUP.117
5.2.2.3.2 Receipt of CALL CONFIRMED and
ALERTING by the network .117
5.2.2.3.3 Call failure procedures .118
5.2.2.3.4 Called MS clearing during mobile
terminating call establishment .118
5.2.2.4 Notification of interworking in connection with mobile
terminating call establishment.118
5.2.2.5 Call accept .119
5.2.2.6 Active indication .119
5.2.2.7 Traffic channel assignment at mobile terminating call
establishment.119
5.2.2.8 Call queuing at mobile terminating call establishment.119
5.2.2.9 User connection attachment during a mobile terminating
call.119
5.3 Signalling procedures during the "active" state .120
5.3.1 User notification procedure.120
5.3.2 Call rearrangements.120
5.3.3 Not used .120
5.3.4 Support of Dual Services.120
5.3.4.1 Service Description .120
5.3.4.2 Call establishment.121
5.3.4.2.1 Mobile Originating Establishment.121
5.3.4.2.2 Mobile Terminating Establishment .121
5.3.4.3 Changing the Call Mode.122
5.3.4.3.1 Initiation of in-call modification.122
5.3.4.3.2 Successful completion of in-call
modification.122
5.3.4.3.3 Change of the channel configuration .123
5.3.4.3.4 Failure of in-call modification.123
5.3.4.4 Abnormal procedures .123
5.4 Call clearing .125
5.4.1 Terminology .125
5.4.2 Exception conditions.125
5.4.3 Clearing initiated by the MS.125
5.4.3.1 Initiation of call clearing.125
5.4.3.2 Receipt of a DISCONNECT message from the MS.126
5.4.3.3 Receipt of a RELEASE message from the network.126
5.4.3.4 Receipt of a RELEASE COMPLETE message from the
MS.126
5.4.3.5 Abnormal cases.126
5.4.4 Clearing initiated by the network .126
5.4.4.1 Clearing when tones/announcements provided.126
Page 9
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
5.4.4.1.1 Receipt of a DISCONNECT message
with progress indicator #8 from the
network . 127
5.4.4.1.2 Expiry of timer T306 . 127
5.4.4.2 Clearing when tones/announcements not provided. 127
5.4.4.2.1 Receipt of a DISCONNECT message
without progress indicator or with
progress indicator different from #8
from the network . 127
5.4.4.2.2 Receipt of a RELEASE message from
the MS. 127
5.4.4.2.3 Abnormal cases. 127
5.4.4.3 Completion of clearing. 127
5.4.4.3.1 Abnormal cases. 128
5.4.5 Clear collision. 128
5.5 Miscellaneous procedures. 128
5.5.1 In-band tones and announcements. 128
5.5.2 Call collisions. 128
5.5.3 Status procedures . 128
5.5.3.1 Status enquiry procedure. 128
5.5.3.2 Reception of a STATUS message by a CC entity . 129
5.5.3.2.1 STATUS message with incompatible
state. 129
5.5.3.2.2 STATUS message with compatible
state. 129
5.5.4 Call re-establishment, MS side . 129
5.5.4.1 Indication from the mobility management sublayer . 129
5.5.4.2 Reaction of call control. 130
5.5.4.3 Completion of re-establishment. 130
5.5.4.4 Unsuccessful outcome. 130
5.5.5 Call re-establishment, network side. 130
5.5.5.1 State alignment. 130
5.5.6 Progress. 130
5.5.7 DTMF protocol control procedure . 131
5.5.7.1 Start DTMF request by the MS . 131
5.5.7.2 Start DTMF response by the network. 131
5.5.7.3 Stop DTMF request by the MS . 131
5.5.7.4 Stop DTMF response by the network . 131
5.5.7.5 Sequencing of subsequent start DTMF requests by the
MS . 131
6 Support of packet services. 133
7 Examples of structured procedures. 134
7.1 General . 134
7.1.1 Paging request. 135
7.1.2 Immediate assignment . 135
7.1.3 Service request and contention resolution . 136
7.1.4 Authentication. 136
7.1.5 Ciphering mode setting. 137
7.1.6 Transaction phase . 137
7.1.6.1 Channel mode modify. 137
7.1.7 Channel release. 138
7.2 Abnormal cases . 139
7.3 Selected examples . 139
7.3.1 Location updating . 140
7.3.2 Mobile originating call establishment. 142
7.3.3 Mobile terminating call establishment. 146
7.3.4 Call clearing . 149
7.3.5 DTMF protocol control . 150
Page 10
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
7.3.6 Handover .151
7.3.7 In-call modification .153
7.3.8 Call re-establishment.154
8 Handling of unknown, unforeseen, and erroneous protocol data.155
8.1 General .155
8.2 Message too short.155
8.3 Unknown or unforeseen transaction identifier .155
8.4 Unknown or unforeseen message type.156
8.5 Non-semantical mandatory information element errors.156
8.5.1 Radio resource management.157
8.5.2 Mobility management .157
8.5.3 Call control.157
8.6 Unknown and unforeseen IEs in the non-imperative message part .157
8.6.1 IEIs unknown in the message.157
8.6.2 Out of sequence IEs .157
8.6.3 Repeated IEs .158
8.7 Non-imperative message part errors .158
8.7.1 Syntactically incorrect optional IEs .158
8.7.2 Conditional IE errors .158
8.8 Messages with semantically incorrect contents .158
9 Message functional definitions and contents.159
9.1 Messages for Radio Resources management.160
9.1.1 Additional assignment.162
9.1.1.1 Mobile Allocation.162
9.1.1.2 Starting Time.162
9.1.2 Assignment command .163
9.1.2.1 Mode of the First Channel.164
9.1.2.2 Description of the Second Channel .164
9.1.2.3 Mode of the Second Channel .164
9.1.2.4 Mobile Allocation and Frequency List, after the starting
time .164
9.1.2.5 Starting Time.164
9.1.2.6 Reference cell frequency list .165
9.1.2.7 Cell Channel Description.165
9.1.2.8 Cipher Mode Setting.165
9.1.2.9 VGCS target mode Indication.166
9.1.3 Assignment complete.166
9.1.4 Assignment failure.167
9.1.5 Channel mode modify.167
9.1.5.1 Channel Description.167
9.1.5.2 VGCS target mode Indication.167
9.1.6 Channel mode modify acknowledge.168
9.1.7 Channel release.169
9.1.7.1 Channel description and mobile allocation.169
9.1.7.2 Group Cipher Key Number.169
9.1.8 Channel request.170
9.1.9 Ciphering mode command .172
9.1.10 Ciphering mode complete.173
9.1.10.1 Mobile Equipment Identity.173
9.1.11 Classmark change .173
9.1.11.1 Additional MS Classmark Information.173
9.1.11.2 MS Classmark .173
9.1.12 Classmark enquiry .174
9.1.13 Frequency redefinition.175
9.1.13.1 Cell Channel Description.175
9.1.14 Handover access.175
9.1.15 Handover command .176
9.1.15.1 Synchronization Indication.177
Page 11
ETS 300 940 (GSM 04.08 version 5.4.1): April 1997
9.1.15.2 Mode of the First Channel. 177
9.1.15.3 Description of the Second Channel. 177
9.1.15.4 Mode of the Second Channel. 177
9.1.15.5 Frequency Channel Sequence, Frequency List, Frequency
short list and Mobile Allocation, after time. 178
9.1.15.6 Starting Time. 178
9.1.15.7 Reference cell frequency list . 179
9.1.15.8 Real Time Difference. 179
9.1.15.9 Timing Advance . 179
9.1.15.10 Cipher Mode Setting . 179
9.1.15.11 VGCS target mode indication. 179
9.1.16 Handover complete. 180
9.1.16.1 Mobile Observed Time Difference . 180
9.1.17 Handover failure . 180
9.1.18 Immediate assignment . 181
9.1.18.1 Mobile Allocation. 181
9.1.18.2 Starting Time. 181
9.1.18.3 IA Rest Octets (Frequency parameters, before time) . 181
9.1.19 Immediate assignment extended. 182
9.1.19.1 Unnecessary IEs. 182
9.1.19.2 Mobile Allocation. 183
9.1.19.3 Starting Time. 183
9.1.19.4 Maximum message length. 183
9.1.19.5 IAX Rest Octets . 183
9.1.20 Immediate assignment reject. 184
9.1.20.1 Use of the indexes . 184
9.1.20.2 Filling of the message. 184
9.1.21 Measurement report . 185
9.1.22 Paging request type 1. 186
9.1.22.1 Unnecessary IE . 186
9.1.22.2 Channels needed for Mobiles 1 and 2. 186
9.1.22.3 Mobile Identities. 186
9.1.22.4 P1 Rest Octets. 186
9.1.23 Paging request type 2. 187
9.1.23.1 Channels needed for Mobiles 1 and 2. 187
9.1.23.2 Mobile Identity 3 . 187
9.1.23.3 P2 Rest Octets. 187
9.1.24 Paging request type 3. 188
9.1.24.1 Chan
...
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...