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