Section: 6.1.3.2.2a Unsuccessful secondary PDP context activation requested by the network
Content: Upon receipt of the REQUEST SECONDARY PDP CONTEXT ACTIVATION message, the MS may reject the network requested secondary PDP context activation by sending the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message to the network. The message contains the same TI as included in the REQUEST SECONDARY PDP CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes: # 26: insufficient resources; # 31: activation rejected, unspecified; # 40: feature not supported; # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 43: unknown PDP context; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 46: PDP context without TFT already activated; # 48: request rejected, Bearer Control Mode violation; or # 95 - 111: protocol errors. The MS should reply with the REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message with cause #48 "request rejected, Bearer Control Mode violation" if the previously negotiated Bearer Control Mode is 'MS-only'. If a PDP context for the TI given in the Linked TI IE exists, then the TFT in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message is checked by the MS for different types of TFT IE errors as specified in subclause 6.1.3.2.3. Upon receipt of a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, the network shall stop timer T3385 and enter state PDP-INACTIVE.