Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 16
SGSN Enhancements for 16.0 ▀
Release Change Reference, StarOS Release 16 ▄
513
call-control-profile profile_name
[ no ] eir-profile profile_name
end
Notes:
no
disassociates an EIR profile with the call control profile.
The EIR parameters configured under the EIR profile associated with the call control profile take precedence
over those configured in the MAP service.
CSCuc21648, CSCud69746, CSCud12642 - Support higher than 16 Mbps bit
rate flag in 3G S4-SGSN
Feature Changes
S4-SGSN Support for “Higher Bit Rates than 16 Mbps” Flag
As per 3GPP R9 specifications, the SGSN can now be aware if the UE is capable of supporting extended R7 bit rates.
The “higher bit rates than 16 Mbps” flag is used for this purpose. This flag is sent by the RNC in the Initial UE message
or Re-location Complete message or by Peer S4-SGSN / MME in Forward Relocation Request / Context Response
message. The SGSN also supports sending “higher Bit Rates than 16 Mbps flag” as part of MM Context in Context
response/Forward Relocation request/Identification request during Old ISRAU/SRNS handover procedures. The SGSN
stores the UE capability in the MM-context. During PDP context activation, the per bearer bit rate or APN-AMBR is
capped based on the flag's value. If the RNC is not 3GPP R9 compliant, the SGSN does not receive this flag. A new CLI
keyword
The “higher bit rates than 16 Mbps” flag is used for this purpose. This flag is sent by the RNC in the Initial UE message
or Re-location Complete message or by Peer S4-SGSN / MME in Forward Relocation Request / Context Response
message. The SGSN also supports sending “higher Bit Rates than 16 Mbps flag” as part of MM Context in Context
response/Forward Relocation request/Identification request during Old ISRAU/SRNS handover procedures. The SGSN
stores the UE capability in the MM-context. During PDP context activation, the per bearer bit rate or APN-AMBR is
capped based on the flag's value. If the RNC is not 3GPP R9 compliant, the SGSN does not receive this flag. A new CLI
keyword
ue-3gpp-compliance-unknown restrict-16mbps
is introduced under the sgsn-service to support this
functionality. When the CLI is configured, the SGSN caps the APN-AMBR for non-GBR bearers to “16” Mbps and
rejects activation of GBR bearers with GBR higher than “16” Mbps. If not, APN-AMBR and GBR higher than “16”
Mbps are allowed.
rejects activation of GBR bearers with GBR higher than “16” Mbps. If not, APN-AMBR and GBR higher than “16”
Mbps are allowed.
Consider the scenarios where UE 3GPP compliance is not known and the CLI is configured to restrict bitrate to 16
Mbps or it is known that UE is not capable of supporting bitrates higher than 16Mbps; the Session Manager uses the
flag to perform the following actions:
Mbps or it is known that UE is not capable of supporting bitrates higher than 16Mbps; the Session Manager uses the
flag to perform the following actions:
1. The APN-AMBR is restricted to “16” Mbps during PDP activation of non-GBR bearers, particularly the default
bearer.
2. If the PGW upgrades the APN-AMBR in Create Session Response during non-GBR bearer activation, then the
APN-AMBR is retained as “16” Mbps and same is indicated to the UE in an Activate Accept.
3. If the PGW upgrades APN-AMBR in Update Bearer Request for non-GBR bearer, then the APN-AMBR is
restricted to “16” Mbps and only if the APN-AMBR changes, the PGW init bearer modification procedure is
continued. In case APN-AMBR does not change, then Update Bearer Response is sent immediately.
continued. In case APN-AMBR does not change, then Update Bearer Response is sent immediately.
4. For GBR bearers, Update Bearer Request with GBR/MBR higher than “16” Mbps is rejected with “No resources
available”.
5. Activation of GBR bearers with MBR/GBR higher than “16” Mbps in Create Bearer Request is rejected with
cause “No resources available”.
6. After S3 SRNS, Modify Bearer Command is initiated to modify the APN-AMBR to “16” Mbps for Non-GBR
bearers having bitrates higher than 16 Mbps.
7. After S3 SRNS, GBR bearers having bitrates higher than “16” Mbps are de-activated.
Previous Behavior: The S4-SGSN did not restrict bitrate to “16” Mbps for UE's not capable of handling higher
bitrates, the RNC had to downgrade the bitrates during RAB assignment procedure.
bitrates, the RNC had to downgrade the bitrates during RAB assignment procedure.