для Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 16
SGSN Enhancements for 16.5 ▀
Release Change Reference, StarOS Release 16 ▄
463
New Behavior: The RAB-release and establishment is done after acknowledging the GGSN modification with UPCR
without direct tunnel. This is followed by UPCQ with Direct tunnel information from SGSN post rab-assignment
success. The modified call-flow during RNC RAB modification procedure is as follows:
without direct tunnel. This is followed by UPCQ with Direct tunnel information from SGSN post rab-assignment
success. The modified call-flow during RNC RAB modification procedure is as follows:
1. An UPCQ from GGSN is received for a PDP-context
2. MS modify request and MS modify accept procedures occur.
3. Direct tunnel is disabled during this step and UPCR is sent to the GGSN with cause as “Accepted” (DTI
2. MS modify request and MS modify accept procedures occur.
3. Direct tunnel is disabled during this step and UPCR is sent to the GGSN with cause as “Accepted” (DTI
information is not sent).
4. Direct tunnel procedure is initiated and the RAB is released and re-established.
5. UPCQ is sent to GGSN with DTI information, UPCR is received from the GGSN.
5. UPCQ is sent to GGSN with DTI information, UPCR is received from the GGSN.
Customer Impact: When the GGSN tries to forward the downlink data to the RNC during PDP-modification
procedure initiated by GGSN, error-indication will not be received during the RAB-release and RAB re-assignment
procedures.
procedure initiated by GGSN, error-indication will not be received during the RAB-release and RAB re-assignment
procedures.
CSCus50162 - QOS : Incorrect Reliability Class Mapping from QCI=5
Feature Changes
Improve Reliability Class Mapping
During handovers involving Inter-RAT, some UEs experienced issues with existing behavior, which required the UEs to
be powered off/on (reboot) to acquire service. Those issues should be resolved with the behavior changes identified
below.
be powered off/on (reboot) to acquire service. Those issues should be resolved with the behavior changes identified
below.
Previous Behavior: In situations where the SDU error ratio = 10*-6, the MME and SGSN each implemented QoS
mapping of reliability class =2.
mapping of reliability class =2.
New Behavior: The MME and SGSN behavior has been modified such that in situations where the SDU error ratio =
10*-6, the MME and SGSN each implement QoS mapping of reliability class =3.
10*-6, the MME and SGSN each implement QoS mapping of reliability class =3.
CSCus80817 - RAB-SetupOrModify message should not include some fields in
case of Modi
Feature Changes
Configurable RANAP IE in RAB Assignment Request
According to 3GPP 25.413 Section 8.2.2: “For each RAB requested to be modified, the message may contain:
RAB ID (mandatory);
NAS Synchronisation Indicator;
RAB parameters;
Transport Layer Information;
User Plane Information.
At a RAB modification, it is only possible to include information elements (IEs), other than the RAB ID and possibly
the NAS Synchronisation Indicator, in the RAB ASSIGNMENT REQUEST message when a previously set value for
the NAS Synchronisation Indicator, in the RAB ASSIGNMENT REQUEST message when a previously set value for