Section: 6.1.3.2.3 Abnormal cases
Content: The following abnormal cases can be identified: a) Expiry of timers In the mobile station: On the first expiry of the timer T3380, the MS shall resend the ACTIVATE SECONDARY PDP CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic PDP context activation re-attempt shall be performed. On the network side: On the first expiry of the timer T3385, the network shall resend the message REQUEST SECONDARY PDP CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall abort the procedure. b) MS initiated secondary PDP context activation procedure for an already activated PDP context (On the network side) If the NSAPI matches that of an already activated PDP context, the network shall deactivate the existing PDP context locally without notification to the MS and proceed with the requested PDP context activation. The case of a TI match is described in subclause 8.3.2. c) no PDP context with linked TI activated (on the network side) The network shall then check whether there is an activated PDP context for the TI given in the Linked TI IE in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message. If there is no active PDP context for the specified TI, the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT message, cause code indicating "unknown PDP context". d) no PDP context with Linked TI activated (on the mobile station side) The MS shall check whether there is an activated PDP context for the TI given in the Linked TI IE in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. If there is no active PDP context for the specified TI, the MS shall reply with a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, cause code indicating "unknown PDP context". e) MS initiated secondary PDP context activation procedure for a PDN connection established for emergency bearer services (on the network side) If the MS initiated secondary PDP context activation procedure is for a PDN connection established for emergency bearer services the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT message, cause code indicating "activation rejected, unspecified". f) no TFT IE is received in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message (on the mobile station side) The MS shall either: A) reply with a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, cause code indicating "semantic error in the TFT operation"; or B) optionally, to support networks compliant with earlier versions of the protocol, accept the network requested secondary PDP context activation and proceed as specified in subclause 6.1.3.2.1a. If another PDP context with the same PDP address and APN without a TFT exists, the MS shall deactivate this old PDP context without a TFT by explicit peer-to-peer signalling between the MS and the network. If during a previous inter-system change from S1 mode to A/Gb or Iu mode the default PDP context linked to the new PDP context was mapped from an EPS bearer context, the MS shall follow option A. NOTE 1: A network implementing this version of the protocol will always include a request for a TFT when requesting the activation of a non-default PDP context. If a PDP context for the TI given in the Linked TI IE exists, then the TFT in the ACTIVATE SECONDARY PDP CONTEXT REQUEST or the REQUEST SECONDARY PDP CONTEXT ACTIVATION message is checked for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is an operation other than "Create a new TFT". The network shall reject the activation request with cause "semantic error in the TFT operation". The MS shall reject the activation request with cause "semantic error in the TFT operation". b) Syntactical errors in TFT operations: 1) When the TFT operation is "Create a new TFT" and the packet filter list in the TFT IE is empty. 2) Void. 3) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. The network shall reject the activation request with cause "syntactical error in the TFT operation". The MS shall reject the activation request with cause "syntactical error in the TFT operation". c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the network determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT does not contain any packet filter applicable for the uplink direction. NOTE 2: When BCM='MS only', the MS is allowed to include a TFT with packet filters without any explicit direction information, i.e. with value "00", and such packet filters are applicable for both uplink and downlink directions. The network shall reject the activation request with cause "semantic errors in packet filter(s)". The MS shall reject the activation request with cause "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation is "Create a new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation is "Create a new TFT" and two or more packet filters in all TFTs associated with this PDP address and APN would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 2) the network shall not diagnose an error, further process the new activation request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the MS and the network, the network shall deactivate the PDP context(s) for which it has deleted the packet filters. In cases 1) and 3) the network shall reject the activation request with cause "syntactical errors in packet filter(s)". In case 2) the MS shall not diagnose an error, further process the new activation request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the network and the MS, the MS shall deactivate the PDP context(s) for which it has deleted the packet filters. In cases 1) and 3) the MS shall reject the activation request with cause "syntactical errors in packet filter(s)". Otherwise, the network shall accept the activation request by replying to the MS with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message. In case of network requested secondary PDP context activation procedure the MS shall accept the activation request by replying to the network with an ACTIVATE SECONDARY PDP CONTEXT REQUEST message. Figure 6.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated secondary PDP context activation procedure Figure 6.5a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network requested secondary PDP context activation procedure