Section: 6.1.3.2.1 Successful Secondary PDP Context Activation Procedure Initiated by the MS
Content: In order to request a PDP context activation with the same PDP address and APN as an already active PDP context, the MS shall send an ACTIVATE SECONDARY PDP CONTEXT REQUEST message to the network, enter the state PDP-ACTIVE-PENDING and start timer T3380. The message shall contain the selected NSAPI. The MS shall ensure that the selected NSAPI is not currently being used by another Session Management entity in the MS. The message shall also include a QoS profile, a requested LLC SAPI and the Linked TI. The QoS profile is the requested QoS. If present, the TFT shall be sent transparently through the SGSN to the GGSN to enable packet classification and policing for downlink data transfer. If the selected Bearer Control Mode is 'MS/NW' and a TFT IE is included in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the MS shall set the packet filter direction parameter of each packet filter in the TFT to a value different from "00". The MS shall allocate packet filter identifiers for all packet filters included in the TFT. Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST, the network shall validate the message by verifying the TI given in the Linked TI IE to be any of the active PDP context(s). The same GGSN address shall be used by the SGSN as for the already established PDP context(s) for that PDP address. The network shall select a radio priority level based on the QoS negotiated and shall reply with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message, if the request can be accepted. NOTE 1: If the MS requested a value for a QoS parameter that is not within the range specified by 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ]  [81], the network should negotiate the parameter to a value that lies within the specified range. Upon receipt of the message ACTIVATE SECONDARY PDP CONTEXT ACCEPT, the MS shall stop timer T3380 and enter the state PDP-ACTIVE. If the offered QoS parameters received from the network differ from the QoS requested by the MS, the MS shall either accept the negotiated QoS or initiate the PDP context deactivation procedure. In A/Gb mode the MS shall initiate establishment of the logical link for the LLC SAPI indicated by the network with the offered QoS and selected radio priority level if no logical link has been already established for that SAPI. If the LLC SAPI indicated by the network can not be supported by the MS, the MS shall initiate the PDP context deactivation procedure. In Iu mode, both SGSN and MS shall store the LLC SAPI and the radio priority in the PDP context. If an Iu mode to A/Gb mode Routing Area Update is performed, the new SGSN shall initiate establishment of the logical link using the negotiated LLC SAPI, the negotiated QoS profile and selected radio priority level stored in the PDP context as in an A/Gb mode to A/Gb mode Routing Area Update. An MS, which is capable of operating in A/Gb mode, shall use a valid LLC SAPI, while an MS which is not capable of operating in A/Gb mode shall indicate the LLC SAPI value as "LLC SAPI not assigned" in order to avoid unnecessary value range checking and any other possible confusion in the network. When the MS uses a valid LLC SAPI, the network shall return a valid LLC SAPI. The network shall return the "LLC SAPI not assigned" value only when the MS uses the "LLC SAPI not assigned" value. NOTE 2: The radio priority level and the LLC SAPI parameters, though not used in Iu mode, shall be included in the messages, in order to support handover between Iu mode and A/Gb mode networks. At inter-system change from Iu mode to A/Gb mode, SM shall locally deactivate the active PDP context(s) if SM does not have the following parameters: - LLC SAPI; and - radio priority.