8.7 Abnormal cases
3GPP44.060General Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 17TS
8.7.0 General
The following abnormal cases apply:
– If the PDCH containing the mobile station’s only assigned TAI value is removed, the mobile station shall, if it has at least one ongoing uplink TBF, perform an abnormal release with access retry (see sub-clause 8.7.2, and otherwise shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If the NC Measurement Parameters are sent in more than one instance of the PACKET MEASUREMENT ORDER message, the mobile station shall not obey the measurement order until all instances of the message has been correctly received;
– If the mobile station receives a Timing Advance Index and a Timing Advance Timeslot Number for one direction within a PACKET POWER CONTROL/TIMING ADVANCE message and the corresponding TBF does not exist, the Timing Advance Index and the Timing Advance Timeslot Number for that direction shall be ignored;
– While a TBF is in progress, if a mobile station receives a PACKET UPLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, PACKET UPLINK ACK/NACK, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or a PACKET CS RELEASE INDICATION message with message escape bit indicating EGPRS (resp. GPRS) contents whereas the current TBF mode is GPRS (resp. EGPRS), the mobile station shall ignore the message;
– While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message without extension message content related to R99 whereas the current TBF mode is EGPRS, the mobile station shall ignore the message;
– While a TBF is in progress, if a mobile station receives a PACKET DOWNLINK ASSIGNMENT message with extension message content related to R99 whereas the current TBF mode is GPRS, the mobile station shall ignore the EGPRS related information and act as a GPRS MS not supporting EGPRS;
– In Iu mode, if the network receives a PACKET CONTROL ACKNOWLEDGEMENT message with an incorrect timeslot in the TN_RRBP field for the given radio block, then the message shall be ignored;
– If a mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, MULTIPLE TBF UPLINK ASSIGNMENT, MULTIPLE TBF DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE, MULTIPLE TBF TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message that would result in one or more TBFs with FANR activated and one or more TBFs with FANR not activated when considering all concurrent TBFs assigned to that mobile station, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If a mobile station receives a PACKET UPLINK ASSIGNMENT, PACKET DOWNLINK ASSIGNMENT, PACKET TIMESLOT RECONFIGURE or PACKET CS RELEASE INDICATION message assigning two or more RLC entities operating in the same RLC mode to a TBF, or assigning more RLC entities than the mobile station supports, the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.2);
– If a mobile station receives DTR information including the TN/PDCH-pair field indicating a timeslot or a PDCH-pair which is not assigned to the mobile station as part of TBF (see sub-clause 8.1.8), the mobile station shall perform an abnormal release without retry (see sub-clause 8.7.1);
– If a mobile station receives a PACKET CS RELEASE INDICATION message including an inconsistent RTTI configuration assignment as per the conditions specified in sub-clause 7.1.3.6, the mobile station shall perform an abnormal release with access retry if there is at least one ongoing uplink TBF (see sub-clause 8.7.2), otherwise it shall perform an abnormal release without retry (see sub-clause 8.7.1).
8.7.1 Abnormal release without retry
The mobile station shall abort all TBFs on PDCH(s) in progress and report an RLC/MAC failure to upper layers. The mobile station in packet transfer mode or MAC-Shared state shall return to packet idle mode or MAC-Idle state; the mobile station in dual transfer mode or MAC-DTM state shall return to dedicated mode or MAC-Dedicated state. Upon enhanced CS release while in dual transfer mode, on receipt of PACKET CS RELEASE INDICATION message, the mobile station shall abort all TBFs in progress and return to packet idle mode when the RR connection is released. Upon mobile originated or mobile terminated RR connection establishment, on receipt of IMMEDIATE ASSIGNMENT message while in packet transfer mode, the mobile station shall enter dedicated mode. The DRX mode procedures shall be applied as specified in sub-clause 5.5.1.5.
8.7.2 Abnormal release with access retry
The mobile station shall abort all TBFs in progress. The mobile station in packet transfer mode shall return to packet idle mode and initiate the establishment of one or more new uplink TBFs, using the procedures on CCCH, PCCCH or EC-CCCH, as defined in sub-clause 7.1 and 3GPP TS 44.018.
The mobile station in dual transfer mode shall return to dedicated mode and initiate the establishment of one new uplink TBF (if exclusive allocation is used) or one or more new uplink TBFs (if exclusive allocation is not used) using the appropriate DTM procedure on the main DCCH, defined in 3GPP TS 44.018. Upon enhanced CS release, on receipt of PACKET CS RELEASE INDICATION message, the mobile station shall abort all TBFs in progress and return to packet idle mode and initiate the establishment of one or more new uplink TBFs, using the procedures on CCCH or PCCCH when the RR connection is released.
Upon mobile originated or mobile terminated RR connection establishment, on receipt of IMMEDIATE ASSIGNMENT message while in packet transfer mode, the mobile station shall enter dedicated mode and initiate the establishment of one new uplink TBF (if exclusive allocation is used) or more new uplink TBFs (if exclusive allocation is not used) using the appropriate DTM procedure on the main DCCH, as defined in 3GPP TS 44.018.
In case the mobile station fails to establish a new uplink TBF, the mobile station shall report an RLC/MAC failure to upper layers for that TBF. The DRX mode procedures shall be applied, as specified in sub-clause 5.5.1.5.
8.7.3 Abnormal release with system information
The mobile station shall abort all of the TBFs indicated in the assignment message containing invalid frequency parameter information and proceed as follows:
– If there are no on-going TBFs it shall immediately return to the BCCH /EC-BCCH and reread all relevant BCCH/EC-BCCH and PBCCH information;
– If the mobile station had one ongoing uplink TBF when the abnormal release occurred, the mobile station shall then perform an abnormal release with access retry (see sub-clause 8.7.2);
– If the mobile station had no ongoing uplink TBFs when the abnormal release occurred, it shall perform an abnormal release without retry (see sub-clause 8.7.1);
– Otherwise, the mobile station shall maintain all its ongoing TBFs that were in progress prior to receiving the assignment message containing invalid frequency parameter information and provide a failure indication to the upper layers associated with the aborted TBFs.
8.7.4 Abnormal release with RR connection establishment retry
The mobile station shall abort all TBFs in progress and report an RLC/MAC failure to upper layers. The mobile station in packet transfer mode shall return to the CCCH configuration, enter packet idle mode and initiate the establishment of the RR connection as specified in 3GPP TS 44.018.