Content for TS 24.008 Word version: 18.6.0
0…
2…
4…
4.2…
4.3…
4.4…
4.7…
4.7.5…
5…
5.3…
6…
9…
9.3…
9.3.18…
9.4…
9.4.9…
9.5…
9.5.10…
10…
10.5.4
10.5.5…
A…
E…
I…
6 Support for packet services
6.1 GPRS Session management
6.1.1 General
6.1.2 Session management states
6.1.2A PDP address allocation
6.1.3 Session Management procedures
6.3 Coordination between SM and GMM for supporting ISR
6.4 MSISDN notification procedure
7 Examples of structured procedures
8 Handling of unknown, unforeseen, and erroneous protocol data
8.1 General
8.2 Message too short
8.3 Unknown or unforeseen transaction identifier
8.4 Unknown or unforeseen message type
8.5 Non-semantical mandatory information element errors
8.6 Unknown and unforeseen IEs in the non-imperative message part
8.7 Non-imperative message part errors
8.8 Messages with semantically incorrect contents
...
...
6 Support for packet services p. 318
6.1 GPRS Session management p. 318
6.1.1 General p. 318
6.1.2 Session management states p. 318
6.1.2.1 Session management states in the MS p. 319
6.1.2.1.1 PDP-INACTIVE p. 319
6.1.2.1.2 PDP-ACTIVE-PENDING p. 319
6.1.2.1.3 PDP-INACTIVE-PENDING p. 319
6.1.2.1.4 PDP-ACTIVE p. 319
6.1.2.1.5 PDP-MODIFY_PENDING p. 319
6.1.2.1.6 MBMS-ACTIVE-PENDING |R6| p. 319
6.1.2.1.7 MBMS-ACTIVE |R6| p. 319
6.1.2.2 Session management states on the network side p. 321
6.1.2.2.1 PDP-INACTIVE p. 321
6.1.2.2.2 PDP-ACTIVE-PENDING p. 321
6.1.2.2.3 PDP-INACTIVE-PENDING p. 321
6.1.2.2.4 PDP-ACTIVE p. 321
6.1.2.2.5 PDP-MODIFY-PENDING p. 321
6.1.2.2.6 MBMS-ACTIVE-PENDING |R6| p. 322
6.1.2.2.7 MBMS-INACTIVE-PENDING |R6| p. 322
6.1.2.2.8 MBMS-ACTIVE |R6| p. 322
6.1.2A PDP address allocation |R8| p. 323
6.1.2A.1 General p. 323
6.1.2A.1.1 Interworking with PDN based on IP p. 323
6.1.2A.1.2 Interworking with PDN based on PPP p. 323
6.1.2A.2 IP address allocation via NAS signalling p. 324
6.1.3 Session Management procedures p. 324
6.1.3.0 General |R11| p. 324
6.1.3.1 PDP context activation p. 324
6.1.3.1.1 Successful PDP context activation initiated by the mobile station p. 325
6.1.3.1.2 Successful PDP context activation requested by the network p. 328
6.1.3.1.3 Unsuccessful PDP context activation initiated by the MS p. 328
6.1.3.1.3.1 General p. 328
6.1.3.1.3.2 Handling of network rejection due to SM cause #26 p. 329
6.1.3.1.3.3 Handling of network rejection due to SM cause other than SM cause #26 p. 331
6.1.3.1.3A Void
6.1.3.1.4 Unsuccessful PDP context activation requested by the network p. 334
6.1.3.1.5 Abnormal cases p. 334
6.1.3.1.6 Handling Activate PDP context request for MS configured for dual priority |R11| p. 336
6.1.3.2 Secondary PDP Context Activation Procedure p. 337
6.1.3.2.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS p. 337
6.1.3.2.1a Successful Secondary PDP Context Activation Procedure Requested by the network |R7| p. 338
6.1.3.2.2 Unsuccessful Secondary PDP Context Activation Procedure initiated by the MS p. 339
6.1.3.2.2.1 General p. 339
6.1.3.2.2.2 Handling of network rejection due to SM cause #26 p. 339
6.1.3.2.2.3 Handling of network rejection due to SM cause other than SM cause #26 p. 341
6.1.3.2.2a Unsuccessful secondary PDP context activation requested by the network |R7| p. 342
6.1.3.2.3 Abnormal cases p. 343
6.1.3.3 PDP context modification procedure p. 346
6.1.3.3.1 Network initiated PDP Context Modification p. 347
6.1.3.3.2 MS initiated PDP Context Modification accepted by the network p. 348
6.1.3.3.3 MS initiated PDP Context Modification not accepted by the network p. 349
6.1.3.3.3.1 General p. 349
6.1.3.3.3.2 Handling of network rejection due to SM cause #26 p. 350
6.1.3.3.3.3 Handling of network rejection due to SM cause other than SM cause #26 p. 351
6.1.3.3.3a Network initiated PDP Context Modification not accepted by the MS |R7| p. 353
6.1.3.3.4 Abnormal cases p. 353
6.1.3.4 PDP context deactivation procedure p. 358
6.1.3.4.1 PDP context deactivation initiated by the MS p. 358
6.1.3.4.2 PDP context deactivation initiated by the network p. 359
6.1.3.4.3 Abnormal cases p. 361
6.1.3.4a Void
6.1.3.5 Void
6.1.3.5a Notification procedure |R9| p. 362
6.1.3.5a.1 General p. 362
6.1.3.5a.2 Notification procedure initiation by the network p. 362
6.1.3.5a.3 Notification procedure in the MS p. 363
6.1.3.6 Receiving a SM STATUS message by a SM entity p. 363
6.1.3.7 Protocol configuration options |R5| p. 364
6.1.3.8 MBMS context activation |R6| p. 364
6.1.3.8.1 Successful MBMS context activation p. 365
6.1.3.8.2 Unsuccessful MBMS context activation requested by the MS p. 365
6.1.3.8.2.1 General p. 365
6.1.3.8.2.2 Handling of network rejection due to SM cause #26 p. 365
6.1.3.8.2.3 Handling of network rejection due to SM cause other than SM cause #26 p. 366
6.1.3.8.3 Unsuccessful MBMS context activation requested by the network p. 367
6.1.3.8.4 Abnormal cases p. 368
6.1.3.9 MBMS context deactivation |R6| p. 368
6.1.3.10 MBMS protocol configuration options |R6| p. 369
6.1.3.11 Handling of APN based congestion control |R10| p. 369
6.1.3.11A Handling of group specific session management congestion control |R13| p. 370
6.1.3.12 Handling session management request for MS configured for dual priority |R11| p. 370
6.1.3.13 Handling of network rejection not due to APN based congestion control |R12| p. 371
6.1.3.14 Handling of WLAN offload control |R12| p. 371
6.2 Void
6.3 Coordination between SM and GMM for supporting ISR |R8| p. 371
6.4 MSISDN notification procedure |R8| p. 372
7 Examples of structured procedures p. 372
8 Handling of unknown, unforeseen, and erroneous protocol data p. 372
8.1 General p. 372
8.2 Message too short p. 373
8.3 Unknown or unforeseen transaction identifier p. 373
8.3.1 Call Control p. 373
8.3.2 Session Management p. 374
8.4 Unknown or unforeseen message type p. 375
8.5 Non-semantical mandatory information element errors p. 375
8.5.1 Radio resource management p. 376
8.5.2 Mobility management p. 376
8.5.3 Call control p. 376
8.5.4 GMM mobility management p. 376
8.5.5 Session management p. 376
8.6 Unknown and unforeseen IEs in the non-imperative message part p. 377
8.7 Non-imperative message part errors p. 377
8.8 Messages with semantically incorrect contents p. 378
