Content for TS 51.010-1 Word version: 13.11.0
45 Session Management Procedures
45.1 Definition
45.2 PDP context activation
45.3 PDP context modification procedure
45.4 PDP context deactivation procedure
45.5 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors
46 LLC and SNDCP Tests
47 Dual Transfer Mode
...
...
45 Session Management Procedures p. 4288
45.1 Definition p. 4288
45.2 PDP context activation p. 4288
45.2.1 Initiated by the mobile station p. 4288
45.2.1.1 Attach initiated by context activation/QoS Offered by Network is the QoS Requested p. 4288
45.2.1.2 QoS Offered by Network is a lower QoS p. 4290
45.2.1.2.1 QoS Accepted by MS p. 4290
45.2.1.2.2 QoS Rejected by MS p. 4291
45.2.2 PDP context activation requested by the network, successful and unsuccessful p. 4293
45.2.3 Void
45.2.4 Abnormal cases p. 4296
45.2.4.1 T3380 Expiry p. 4296
45.2.4.2 Collision of MS initiated and network requested PDP context activation p. 4298
45.2.4.3 Network initiated PDP context activation request for an already activated PDP context (on the MS side) p. 4300
45.2.4.4 Network reject with Extended Wait Timer p. 4301
45.2.5 Secondary PDP context activation procedures p. 4303
45.2.5.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS p. 4303
45.2.5.1.1 QoS Offered by Network is the QoS Requested p. 4303
45.2.5.1.2 QoS Offered by Network is a lower QoS p. 4304
45.2.5.1.2.1 QoS accepted by MS p. 4304
45.2.5.1.2.2 QoS rejected by MS p. 4306
45.2.5.2 Unsuccessful Secondary PDP Context Activation Procedure Initiated by the MS p. 4308
45.2.5.3 Abnormal cases p. 4309
45.2.5.3.1 T3380 Expiry p. 4309
45.3 PDP context modification procedure p. 4310
45.3.1 Network initiated PDP context modification p. 4310
45.3.2 MS initiated PDP context modification p. 4313
45.3.2.1 MS initiated PDP Context Modification accepted by network p. 4313
45.3.2.2 MS initiated PDP Context Modification not accepted by the network p. 4314
45.3.3 Abnormal cases p. 4315
45.4 PDP context deactivation procedure p. 4319
45.4.1 PDP context deactivation initiated by the MS p. 4319
45.4.2 PDP context deactivation initiated by the network p. 4321
45.4.3 Abnormal cases p. 4323
45.4.3.1 T3390 Expiry p. 4323
45.4.3.2 Collision of MS and network initiated PDP context deactivation requests p. 4325
45.4.4 PDP context deactivation initiated by the network / Tear down indicator p. 4327
45.5 Unknown or Unforeseen Transaction Identifier/Non-semantical Mandatory Information Element Errors p. 4329
45.5.1 Error cases p. 4329
46 LLC and SNDCP Tests p. 4334
46.1 LLC Tests p. 4334
46.1.1 Default Conditions p. 4335
46.1.2 Test cases p. 4335
46.1.2.1 Unacknowledged data transfer p. 4335
46.1.2.1.1 Data transmission in protected mode p. 4335
46.1.2.1.2 Data transmission in unprotected mode p. 4336
46.1.2.1.3 Reception of I frame in ADM p. 4337
46.1.2.2 Acknowledged data transfer p. 4338
46.1.2.2.1 Link establishment p. 4338
46.1.2.2.1.1 Link establishment from MS to SS p. 4338
46.1.2.2.1.2 Link establishment from SS to MS p. 4339
46.1.2.2.1.3 Loss of UA frame p. 4340
46.1.2.2.1.4 Total loss of UA frame p. 4341
46.1.2.2.1.5 DM response p. 4342
46.1.2.2.2 MS sends I+S frames p. 4343
46.1.2.2.2.1 Checking N(S) p. 4343
46.1.2.2.2.2 Busy condition at the peer, with RR sent for resumption of transmission p. 4344
46.1.2.2.2.3 Busy condition at the peer, with ACK sent for resumption of transmission p. 4346
46.1.2.2.2.4 SACK frame p. 4348
46.1.2.2.3 Reception of I + S frames at the MS p. 4349
46.1.2.2.3.1 Checking N(R) p. 4349
46.1.2.2.3.2 MS handling busy condition during bi-directional data transfer p. 4350
46.1.2.2.3.3 SACK frame p. 4352
46.1.2.2.3.4 ACK frame p. 4353
46.1.2.2.4 Link Reestablishment p. 4354
46.1.2.3 Collision of commands and responses p. 4358
46.1.2.3.1 Collision of SABM p. 4358
46.1.2.3.2 Collision of SABM and DISC p. 4359
46.1.2.3.3 Collision of SABM and XID commands p. 4360
46.1.2.4 Unsolicited response frames p. 4361
46.1.2.4.1 Unsolicited DM p. 4361
46.1.2.5 FRMR frames p. 4362
46.1.2.5.1 Sending FRMR due to undefined command control field p. 4362
46.1.2.5.2 Sending FRMR due to reception of an S frame with incorrect length p. 4363
46.1.2.5.3 Sending FRMR due to reception of an I frame information field exceeding the maximum length p. 4364
46.1.2.5.4 Frame reject condition during establishment of ABM p. 4366
46.1.2.6 Multiple Connections p. 4367
46.1.2.6.1 Simultaneous acknowledged and unacknowledged data transfer on the same SAPI p. 4367
46.1.2.6.2 Simultaneous acknowledged and unacknowledged data transfer on different SAPIs p. 4368
46.1.2.7 XID Negotiation p. 4369
46.1.2.7.1 Negotiation initiated by the SS during ABM, for T200 and N200 p. 4369
46.1.2.7.2 Negotiation initiated by the SS during ADM, for N201-I p. 4370
46.1.2.7.3 Negotiation initiated by the SS (using XID, for IOV-UI) p. 4371
46.1.2.7.4 Negotiation initiated by the SS (during ADM, for N201-U) p. 4372
46.1.2.7.5 Negotiation initiated by the SS (during ADM, for IOV-UI) p. 4373
46.1.2.7.6 Negotiation initiated by the SS (during ABM, for Reset) p. 4376
46.1.2.7.7 XID command with unrecognised type field p. 4378
46.1.2.7.8 XID Response with out of range values p. 4379
46.2 SNDCP Tests p. 4380
46.2.1 Default Conditions p. 4380
46.2.2 Test cases p. 4380
46.2.2.1 Data transfer p. 4380
46.2.2.1.1 Mobile originated normal data transfer with LLC in acknowledged mode p. 4380
46.2.2.1.2 Mobile originated normal data transfer with LLC in unacknowledged mode p. 4382
46.2.2.1.3 Usage of acknowledged mode for data transmission before and after PDP Context modification, on different SAPIs p. 4384
46.2.2.1.4 Reset indication during unacknowledged mode p. 4386
46.2.2.1.5 Reset indication during acknowledged mode p. 4387
46.2.2.1.6 Inter SGSN (with NAS container / new Routing Area / SGSN indicated Reset) PS Handover / Synchronized cell case / successful p. 4389
46.2.2.2 Segmentation p. 4390
46.2.2.2.1 LLC link re-establishment on reception of SN-DATA PDU with F=0 in ack mode in the Receive First Segment state p. 4390
46.2.2.2.2 LLC link re-establishment on receiving second segment with F=1 and with different PCOMP and DCOMP values in the acknowledged mode data transfer p. 4391
46.2.2.2.3 Single segment N-PDU from MS p. 4392
46.2.2.3 Link Release p. 4393
46.2.2.4 XID negotiation p. 4394
46.2.2.4.1 Response from MS on receiving XID request from the SS p. 4394
46.2.2.4.2 Response from MS on receiving an XID request from the SS with an unassigned entity number p. 4396
46.2.2.4.3 Response from MS on receiving an XID response from the SS with unrecognised type field p. 4397
46.2.2.5 LLC link release on receiving "Invalid XID response" from the network during link establishment procedure p. 4398
47 Dual Transfer Mode p. 4399
47.1 Reallocation of CS resources p. 4399
47.1.1 Reallocation of CS resources / Assignment Command p. 4399
47.1.2 Reallocation of CS resources / Handover Command p. 4401
47.1.3 Intra frequency reallocation of CS resources / DTM Assignment Command p. 4404
47.1.4 Inter frequency reallocation of CS resources / DTM Assignment Command p. 4405
47.2 Release of CS resources p. 4408
47.3 Handover p. 4409
47.3.1 Handover to same routeing area p. 4409
47.3.1.1 Handover to same routeing area whilst in dedicated mode & MM Ready / Completed on the main DCCH p. 4409
47.3.1.2 Handover to same routeing area whilst in DTM with downlink TBF Established p. 4411
47.3.1.3 Handover to same routeing area whilst in DTM with both DL & UL TBFs p. 4413
47.3.2 Handover to different routeing area whilst in DM p. 4419
47.3.2.1 Handover to different routeing area whilst in DM / Performed on main DCCH / RAU complete before CS release p. 4419
47.3.2.2 Handover to different routeing area whilst in DM / Performed on main DCCH / CS release before RAU complete p. 4420
47.3.3 Handover to different routeing area whilst in DTM p. 4422
47.3.4 Handover to UTRAN while in DTM p. 4428
47.4 Session Management p. 4440
48_49 Void
