SlideShare a Scribd company logo
5
Most read
11
Most read
14
Most read
PGW/GGSN
PART - 02
Mustafa Golam
Table of Contents
Optional Configurations
Route/VRF
APN
CDR
SACC/PISC
EPG/PGW Configuration Overview
Connectivity and Routing
 Forwarding Table Filters
 GTP Properties
 L2TP
 DHCP
 RADIUS
PDP Context Properties
EPS Bearer Properties
Quality of Service
Resilience
Optional Configuration
SACC
PISC
Credit Control
 Policy and Charging Control
 Aware Policy-Based Routing
 Static Access Control
Operation and Maintenance
Traffic Redirection
Shared IP Pool
MS BTS BSC
RNCNODE-BMS
SGSN GGSN
SGSN GGSN
MSC
SCP/Camel
HLR OSS
Corporate
LAN
Gs
SMS
Um Abis Gb
Ge
Gn
GomGr
Gn
Gn
Gn
Gn
Um Iub Iu
Gi
Gi
Gd
GSM
WCDMA ISP
PCRF
PS Core Network Architecture
Connectivity and Routing
EPG can be designed to use traffic separation purpose. Traffic separation
can be achieved by using one of the following solutions or both:
A single routing instance with firewall filters (the master routing instance)
Multiple routing instances (virtual routing instances)
Connectivity and Routing:
Configuring Multiple Routing Instances
Main Virtual Instances :
Traffic separation by main networks/interfaces.
Routing Instance Name Objective
Gi-vrf To separate network for Gi interface
Gn-vrf To separate network for Gn interface
Gom-vrf To separate network for O&M interface
Gy_Gx-vrf To separate network for Gy/Gx interface
IUPS-vrf To separate network for 3GDT interface
Connectivity and Routing:
Configuring Multiple Routing Instances
Main Virtual Instances : Traffic separation by main networks/interfaces
Gi-vrf {
instance-type vrf;
interface ge-2/0/1.151;
interface ge-3/0/1.251;
route-distinguisher 1:1;
vrf-import reject-all;
vrf-export reject-all;
protocols {
ospf {
export static;
area 0.0.0.7 {
interface ge-2/0/1.151;
interface ge-3/0/1.251
{
metric 10;
}
}
}
}
Gn-vrf {
instance-type vrf;
interface ge-2/0/0.150;
interface ge-3/0/0.250;
route-distinguisher 1:2;
vrf-import reject-all;
vrf-export reject-all;
protocols {
ospf {
export static;
area 0.0.0.6 {
interface ge-2/0/0.150;
interface ge-3/0/0.250;
}
}
}
}
Connectivity and Routing:
Configuring Multiple Routing Instances
Main Virtual Instances : Traffic separation by main networks/interfaces
Gom-vrf {
instance-type vrf;
interface ge-2/0/0.155;
interface ge-3/0/0.255;
route-distinguisher 1:3;
vrf-import reject-all;
vrf-export reject-all;
protocols {
ospf {
rib-group ggsn-om-sec;
export [ static direct ];
area 0.0.0.1 {
interface ge-2/0/0.155;
interface ge-3/0/0.255;
}
}
}
Gy-GOM {
instance-type virtual-router;
interface ge-2/0/0.205;
interface ge-3/0/0.206;
routing-options {
static {
route 10.77.98.0/28 next-table inet.0;
}
}
protocols {
ospf {
rib-group Gy_GOM_to_inet0;
export static;
area 0.0.0.6 {
interface ge-2/0/0.205;
interface ge-3/0/0.206;
}
Connectivity and Routing:
Configuring Multiple Routing Instances
Main Virtual Instances : Traffic separation by main networks/interfaces
IUPS_VRF {
instance-type virtual-router;
interface ge-2/0/0.310;
interface ge-3/0/0.311;
routing-options {
static {
route 41.77.16.24/29 next-table Gn-vrf.inet.0;
route 41.77.16.16/29 next-table Gn-vrf.inet.0;
}
}
protocols {
ospf {
rib-group IUPS_VRF_to_Gn-vrf;
export from_static;
area 0.0.0.8 {
interface ge-2/0/0.310 {
metric 1;
}
interface ge-3/0/0.311 {
metric 1;
GTP Properties
[edit services epg pgw gtp]
keepalive-interval 200; Seconds between sending keepalive messages on idle path
t3-response-time 5; Seconds between control message retries
n3-requests 3; Total number of transmissions allowed for a control message
gn-s5-routing-instance Gn-vrf; Routing instance for GTP traffic
version-list 99; GTP version name
GTP-C tunnels the relevant session and mobility management
messages between the EPG and the SGSN and the MME. It is
responsible for establishment and administration of the GTP - User
plane (GTP-U) tunnels used for transporting the uplink and downlink
encapsulated Transfer (T-PDUs) containing the payload.
L2TP Configuration
In order to setup the GGSN and PDN Gateway (PGW) for L2TP, a P-GGSN2
or PB-GGSN3 Services Physical Interface Card (PIC) must be configured to
run L2TP software applications .
[edit services epg pgw apn apn-name]
l2tp {
l2tp-routing-instance routing-instance-name;
hide-avps;
lac-address-range lac-address-range;
lns {
all-primary;
max-retries attempts;
(blacklisting-timeout minutes |
blacklisting-forever);
server address {
(use-default-port | port number);
max-ppp-sessions number;
}
}
message-attributes {
calling-number;
called-number;
}
ppp {
authentication {
message-attributes {
override-user-info;
}
protocol
(none | pap | chap);
user-name {
as-string string;
predefined
(imsi | msisdn | imsi-at-apn | msisdn-at-apn);
}
user-password password;
}
proxy-lcp-timeout milliseconds;
retry-timeout seconds;
max-retry attempts;
mru bytes;
}
DHCP Configuration
When the EPG is configured to allocate IPv4 addresses from a configured DHCP
server, it requests IP addresses for each context from DHCP server and dynamically
allocate. But only IPv4 can be assigned by DHCP sever.
[edit services epg pgw apn]
apn01-inband-dhcp {
routing-instance Gi-vrf;
gi-address-range 20.255.20.0/27;
pdp-context {
creation unblocked;
address {
21.12.0.0/15;
}
address-allocation dhcp-client; [declaring
DHCP enabled enabled address allocation]
}
dhcp {
server {
10.0.0.1 {
retry 5;
timeout 4;
}
}
server {
10.0.0.2 {
retry 6;
timeout 4;
RADIUS Configuration
RADIUS AAA servers are configured per APN. If the RADIUS server is located in
the external Internet Protocol (IP) network defined for an APN, then it is called an
inband RADIUS server. If the RADIUS server is located outside the external IP
network defined for an APN, then it is called a shared RADIUS server, because a
shared RADIUS server can be associated with several APNs. A shared server can be
used for both accounting and authentication in several APNs.
radius {
accounting {
message-attributes {
apn-identifier;
charging-gateway;
charging-characteristics;
ggsn-address;
gprs-qos;
gprs-qos-extended;
imsi;
user-location-info;
user-plmn-id;
msisdn;
pdp-type;
sgsn-plmn-id;
ggsn-plmn-id;
charging-identifier;
acct-input-octets;
acct-output-octets;
acct-output-packets;
acct-input-packets;
}
shared-server
Outband_RADIUS_Server;
message-for-every-context;
}
}
PDP Context Properties Configuration
[edit services epg pgw pdp-context]
limit 300000;
payload-limit 98000;
policing {
maximum-bandwidth-uplink 11000;
maximum-bandwidth-downlink 84000;
}
Signaling {
sgsn-creates-per-second 1000
ggsn-deletes-per-second 1000
}
session-control {
idle-timeout default timeout 10 [*in minutes]
}
PDP context and EPS bearer properties are configured in Global level. These properties
is applied to all APNs. Some of the properties can be configured in APN level.
Quality of Service Configuration
The EPG controls the priority for handling different types of GPRS and EPS traffic
by using QoS classes. Under most circumstances, the default mapping works
properly. Modify the mappings only if there is contention for bandwidth among the
various traffic classes or to disable uplink DSCP remapping.
QoS Mappings
Uplink QoS Mappings
Downlink QoS Mappings
DSCP Names
Policing of PDP Context or EPS Bearer Bandwidth
Policing for the GGSN or PGW
Policing for an APN
Service Aware Bandwidth Management
Throughput Limitation Profile for SACC
Quality of Service Configuration:
QoS Mappings DL traffic are IP bearer packets arriving at GGSN on Gi interface
[edit services epg pgw apn apn-name]
uplink-dscp-remapping {
background {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
conversational-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
interactive-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
streaming-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
[edit services epg pgw apn apn-name]
uplink-dscp-remapping {
background {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
conversational-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
interactive-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
streaming-1 {
low-drop-precedence dscp-name;
medium-drop-precedence dscp-name;
high-drop-precedence dscp-name;
}
Quality of Service Configuration:
Policing of PDP Context By configuring the maximum BW for DL and UL traffic,
and thus enforcing boundaries, correct QoS negotiations can be ensured.
[edit services epg pgw apn apn-name pdp-context]
policing {
maximum-bandwidth-downlink value;
maximum-bandwidth-uplink value;
no-policing;
}
[edit services epg pgw rule-space name bandwidth-control] throughput-limitation
profile-name
{ access-control-rule 111 112 113]; }
[edit services epg pgw rule-space name bandwidth-control throughput-limitation
profile-name]
uplink-limitation 64;
downlink-limitation 128;
To configure a throughput limitation profile for SACC.
Configuring QoS Class for GTP-C Traffic
By configuring GTP-C QoS class, higher efficiency and reliability of signaling
packets can be ensured.
[edit services epg pgw gtp]
diffserv dscp-name;
By default, af31 is used, which is assured forwarding class 3, low drop precedence,
for all GTP-C traffic.
[edit services epg pgw gtp]
diffserv AF31;
[edit services epg pgw gtp]
allocation-retention-priority
{ high-priority value; medium-priority value; }
Further Study
3GPP Documentation
www.juniper.net
kb.juniper.net/
YouTube
www.ericsson.com
www.huawei.com
Google
When you’re confused
Q??

More Related Content

PPTX
SGSN- serving gprs support node - Platform - HW, SW and CLI
DOCX
4g interview-question
PPTX
Introduction to Evolved Packet Core Networks
PDF
VoLTE Interfaces , Protocols & IMS Stack
PDF
Lte signaling
PPTX
IMS + VoLTE Overview
PPTX
EPG PGW SAPC SACC PISC Configuration
PDF
Simplified Call Flow Signaling: 2G/3G Voice Call
SGSN- serving gprs support node - Platform - HW, SW and CLI
4g interview-question
Introduction to Evolved Packet Core Networks
VoLTE Interfaces , Protocols & IMS Stack
Lte signaling
IMS + VoLTE Overview
EPG PGW SAPC SACC PISC Configuration
Simplified Call Flow Signaling: 2G/3G Voice Call

What's hot (20)

PDF
Evolution of Core Networks
PDF
Best practices-lte-call-flow-guide
PDF
UMTS/LTE/EPC Call Flows for CSFB
PPSX
Paging in LTE
PDF
Epc cups overview
PDF
Doc6 mpls vpn-ppt
PPTX
Diameter based Interfaces and description
PDF
MPLS L3 VPN Deployment
PDF
Mobile Networks Architecture and Security (2G to 5G)
PDF
volte ims network architecture
PPT
Initial LTE call Setup Flow
PDF
UMTS core network and its evolution
PDF
Beginners: Open RAN Terminology – Virtualization, Disaggregation & Decomposition
PDF
5G Basic Call Flows.pdf
DOC
Lte interview questions
PDF
LTE EPC Technology Essentials
PDF
Core cs overview (1)
PDF
Lte system signaling procedures
PDF
VoWifi 03 - vowifi epdg aaa and architecture (pdf ppt)
PPT
3 g call flow
Evolution of Core Networks
Best practices-lte-call-flow-guide
UMTS/LTE/EPC Call Flows for CSFB
Paging in LTE
Epc cups overview
Doc6 mpls vpn-ppt
Diameter based Interfaces and description
MPLS L3 VPN Deployment
Mobile Networks Architecture and Security (2G to 5G)
volte ims network architecture
Initial LTE call Setup Flow
UMTS core network and its evolution
Beginners: Open RAN Terminology – Virtualization, Disaggregation & Decomposition
5G Basic Call Flows.pdf
Lte interview questions
LTE EPC Technology Essentials
Core cs overview (1)
Lte system signaling procedures
VoWifi 03 - vowifi epdg aaa and architecture (pdf ppt)
3 g call flow
Ad

Similar to PGW GGSN Optional Services Configuration (20)

PDF
Traffic Engineering Using Segment Routing
PDF
IP Infusion Application Note for 4G LTE Fixed Wireless Access
PPT
Title Subtitle
PPT
Title Subtitle
PPT
Chapter14ccna
PPT
Chapter14ccna
PPTX
OpenStack MeetUp - OpenContrail Presentation
PPT
Name Based Net Architectures
PPT
Name Based Net Architectures
PDF
Инновации Cisco для операторов связи
PPT
Copy Of Copy Of Gprs
PPTX
redGuardian DP100 large scale DDoS mitigation solution
PPT
Gprs
PDF
BGP Security Best Practices that Matter, presented at PHNOG 2025
PPTX
8 - Configuring a VPRN Nokia Router.pptx
PDF
3G Mobile Internet
PDF
P&G BT Global Services - LLD Final Revision Year 2008.
PDF
BGP Traffic Engineering with SDN Controller
Traffic Engineering Using Segment Routing
IP Infusion Application Note for 4G LTE Fixed Wireless Access
Title Subtitle
Title Subtitle
Chapter14ccna
Chapter14ccna
OpenStack MeetUp - OpenContrail Presentation
Name Based Net Architectures
Name Based Net Architectures
Инновации Cisco для операторов связи
Copy Of Copy Of Gprs
redGuardian DP100 large scale DDoS mitigation solution
Gprs
BGP Security Best Practices that Matter, presented at PHNOG 2025
8 - Configuring a VPRN Nokia Router.pptx
3G Mobile Internet
P&G BT Global Services - LLD Final Revision Year 2008.
BGP Traffic Engineering with SDN Controller
Ad

More from Mustafa Golam (7)

PPTX
BIND DNS IPWorks Introduction To Advanced
PPTX
Sapc upcc-pcrf- part 2 tbp
PPTX
Sapc upcc-pcrf- part 1 tbp
PDF
GGSN-Gateway GPRS Support Node
PPTX
Packet core network basics
PPT
Sample template to report internet dns's performance
PPT
GPRS/EDGE Basics / knowledge sharing
BIND DNS IPWorks Introduction To Advanced
Sapc upcc-pcrf- part 2 tbp
Sapc upcc-pcrf- part 1 tbp
GGSN-Gateway GPRS Support Node
Packet core network basics
Sample template to report internet dns's performance
GPRS/EDGE Basics / knowledge sharing

Recently uploaded (20)

PDF
Encapsulation theory and applications.pdf
PDF
Univ-Connecticut-ChatGPT-Presentaion.pdf
PDF
Transform Your ITIL® 4 & ITSM Strategy with AI in 2025.pdf
PPTX
Tartificialntelligence_presentation.pptx
PPTX
TLE Review Electricity (Electricity).pptx
PDF
Unlocking AI with Model Context Protocol (MCP)
PPTX
cloud_computing_Infrastucture_as_cloud_p
PDF
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
PDF
From MVP to Full-Scale Product A Startup’s Software Journey.pdf
PDF
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
PDF
Web App vs Mobile App What Should You Build First.pdf
PDF
August Patch Tuesday
PDF
Mushroom cultivation and it's methods.pdf
PDF
A comparative study of natural language inference in Swahili using monolingua...
PDF
NewMind AI Weekly Chronicles - August'25-Week II
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PDF
Heart disease approach using modified random forest and particle swarm optimi...
PPTX
Group 1 Presentation -Planning and Decision Making .pptx
PDF
Zenith AI: Advanced Artificial Intelligence
PDF
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Encapsulation theory and applications.pdf
Univ-Connecticut-ChatGPT-Presentaion.pdf
Transform Your ITIL® 4 & ITSM Strategy with AI in 2025.pdf
Tartificialntelligence_presentation.pptx
TLE Review Electricity (Electricity).pptx
Unlocking AI with Model Context Protocol (MCP)
cloud_computing_Infrastucture_as_cloud_p
ENT215_Completing-a-large-scale-migration-and-modernization-with-AWS.pdf
From MVP to Full-Scale Product A Startup’s Software Journey.pdf
Video forgery: An extensive analysis of inter-and intra-frame manipulation al...
Web App vs Mobile App What Should You Build First.pdf
August Patch Tuesday
Mushroom cultivation and it's methods.pdf
A comparative study of natural language inference in Swahili using monolingua...
NewMind AI Weekly Chronicles - August'25-Week II
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
Heart disease approach using modified random forest and particle swarm optimi...
Group 1 Presentation -Planning and Decision Making .pptx
Zenith AI: Advanced Artificial Intelligence
Profit Center Accounting in SAP S/4HANA, S4F28 Col11

PGW GGSN Optional Services Configuration

  • 2. Table of Contents Optional Configurations Route/VRF APN CDR SACC/PISC
  • 3. EPG/PGW Configuration Overview Connectivity and Routing  Forwarding Table Filters  GTP Properties  L2TP  DHCP  RADIUS PDP Context Properties EPS Bearer Properties Quality of Service Resilience Optional Configuration SACC PISC Credit Control  Policy and Charging Control  Aware Policy-Based Routing  Static Access Control Operation and Maintenance Traffic Redirection Shared IP Pool
  • 4. MS BTS BSC RNCNODE-BMS SGSN GGSN SGSN GGSN MSC SCP/Camel HLR OSS Corporate LAN Gs SMS Um Abis Gb Ge Gn GomGr Gn Gn Gn Gn Um Iub Iu Gi Gi Gd GSM WCDMA ISP PCRF PS Core Network Architecture
  • 5. Connectivity and Routing EPG can be designed to use traffic separation purpose. Traffic separation can be achieved by using one of the following solutions or both: A single routing instance with firewall filters (the master routing instance) Multiple routing instances (virtual routing instances)
  • 6. Connectivity and Routing: Configuring Multiple Routing Instances Main Virtual Instances : Traffic separation by main networks/interfaces. Routing Instance Name Objective Gi-vrf To separate network for Gi interface Gn-vrf To separate network for Gn interface Gom-vrf To separate network for O&M interface Gy_Gx-vrf To separate network for Gy/Gx interface IUPS-vrf To separate network for 3GDT interface
  • 7. Connectivity and Routing: Configuring Multiple Routing Instances Main Virtual Instances : Traffic separation by main networks/interfaces Gi-vrf { instance-type vrf; interface ge-2/0/1.151; interface ge-3/0/1.251; route-distinguisher 1:1; vrf-import reject-all; vrf-export reject-all; protocols { ospf { export static; area 0.0.0.7 { interface ge-2/0/1.151; interface ge-3/0/1.251 { metric 10; } } } } Gn-vrf { instance-type vrf; interface ge-2/0/0.150; interface ge-3/0/0.250; route-distinguisher 1:2; vrf-import reject-all; vrf-export reject-all; protocols { ospf { export static; area 0.0.0.6 { interface ge-2/0/0.150; interface ge-3/0/0.250; } } } }
  • 8. Connectivity and Routing: Configuring Multiple Routing Instances Main Virtual Instances : Traffic separation by main networks/interfaces Gom-vrf { instance-type vrf; interface ge-2/0/0.155; interface ge-3/0/0.255; route-distinguisher 1:3; vrf-import reject-all; vrf-export reject-all; protocols { ospf { rib-group ggsn-om-sec; export [ static direct ]; area 0.0.0.1 { interface ge-2/0/0.155; interface ge-3/0/0.255; } } } Gy-GOM { instance-type virtual-router; interface ge-2/0/0.205; interface ge-3/0/0.206; routing-options { static { route 10.77.98.0/28 next-table inet.0; } } protocols { ospf { rib-group Gy_GOM_to_inet0; export static; area 0.0.0.6 { interface ge-2/0/0.205; interface ge-3/0/0.206; }
  • 9. Connectivity and Routing: Configuring Multiple Routing Instances Main Virtual Instances : Traffic separation by main networks/interfaces IUPS_VRF { instance-type virtual-router; interface ge-2/0/0.310; interface ge-3/0/0.311; routing-options { static { route 41.77.16.24/29 next-table Gn-vrf.inet.0; route 41.77.16.16/29 next-table Gn-vrf.inet.0; } } protocols { ospf { rib-group IUPS_VRF_to_Gn-vrf; export from_static; area 0.0.0.8 { interface ge-2/0/0.310 { metric 1; } interface ge-3/0/0.311 { metric 1;
  • 10. GTP Properties [edit services epg pgw gtp] keepalive-interval 200; Seconds between sending keepalive messages on idle path t3-response-time 5; Seconds between control message retries n3-requests 3; Total number of transmissions allowed for a control message gn-s5-routing-instance Gn-vrf; Routing instance for GTP traffic version-list 99; GTP version name GTP-C tunnels the relevant session and mobility management messages between the EPG and the SGSN and the MME. It is responsible for establishment and administration of the GTP - User plane (GTP-U) tunnels used for transporting the uplink and downlink encapsulated Transfer (T-PDUs) containing the payload.
  • 11. L2TP Configuration In order to setup the GGSN and PDN Gateway (PGW) for L2TP, a P-GGSN2 or PB-GGSN3 Services Physical Interface Card (PIC) must be configured to run L2TP software applications . [edit services epg pgw apn apn-name] l2tp { l2tp-routing-instance routing-instance-name; hide-avps; lac-address-range lac-address-range; lns { all-primary; max-retries attempts; (blacklisting-timeout minutes | blacklisting-forever); server address { (use-default-port | port number); max-ppp-sessions number; } } message-attributes { calling-number; called-number; } ppp { authentication { message-attributes { override-user-info; } protocol (none | pap | chap); user-name { as-string string; predefined (imsi | msisdn | imsi-at-apn | msisdn-at-apn); } user-password password; } proxy-lcp-timeout milliseconds; retry-timeout seconds; max-retry attempts; mru bytes; }
  • 12. DHCP Configuration When the EPG is configured to allocate IPv4 addresses from a configured DHCP server, it requests IP addresses for each context from DHCP server and dynamically allocate. But only IPv4 can be assigned by DHCP sever. [edit services epg pgw apn] apn01-inband-dhcp { routing-instance Gi-vrf; gi-address-range 20.255.20.0/27; pdp-context { creation unblocked; address { 21.12.0.0/15; } address-allocation dhcp-client; [declaring DHCP enabled enabled address allocation] } dhcp { server { 10.0.0.1 { retry 5; timeout 4; } } server { 10.0.0.2 { retry 6; timeout 4;
  • 13. RADIUS Configuration RADIUS AAA servers are configured per APN. If the RADIUS server is located in the external Internet Protocol (IP) network defined for an APN, then it is called an inband RADIUS server. If the RADIUS server is located outside the external IP network defined for an APN, then it is called a shared RADIUS server, because a shared RADIUS server can be associated with several APNs. A shared server can be used for both accounting and authentication in several APNs. radius { accounting { message-attributes { apn-identifier; charging-gateway; charging-characteristics; ggsn-address; gprs-qos; gprs-qos-extended; imsi; user-location-info; user-plmn-id; msisdn; pdp-type; sgsn-plmn-id; ggsn-plmn-id; charging-identifier; acct-input-octets; acct-output-octets; acct-output-packets; acct-input-packets; } shared-server Outband_RADIUS_Server; message-for-every-context; } }
  • 14. PDP Context Properties Configuration [edit services epg pgw pdp-context] limit 300000; payload-limit 98000; policing { maximum-bandwidth-uplink 11000; maximum-bandwidth-downlink 84000; } Signaling { sgsn-creates-per-second 1000 ggsn-deletes-per-second 1000 } session-control { idle-timeout default timeout 10 [*in minutes] } PDP context and EPS bearer properties are configured in Global level. These properties is applied to all APNs. Some of the properties can be configured in APN level.
  • 15. Quality of Service Configuration The EPG controls the priority for handling different types of GPRS and EPS traffic by using QoS classes. Under most circumstances, the default mapping works properly. Modify the mappings only if there is contention for bandwidth among the various traffic classes or to disable uplink DSCP remapping. QoS Mappings Uplink QoS Mappings Downlink QoS Mappings DSCP Names Policing of PDP Context or EPS Bearer Bandwidth Policing for the GGSN or PGW Policing for an APN Service Aware Bandwidth Management Throughput Limitation Profile for SACC
  • 16. Quality of Service Configuration: QoS Mappings DL traffic are IP bearer packets arriving at GGSN on Gi interface [edit services epg pgw apn apn-name] uplink-dscp-remapping { background { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } conversational-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } interactive-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } streaming-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } [edit services epg pgw apn apn-name] uplink-dscp-remapping { background { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } conversational-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } interactive-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; } streaming-1 { low-drop-precedence dscp-name; medium-drop-precedence dscp-name; high-drop-precedence dscp-name; }
  • 17. Quality of Service Configuration: Policing of PDP Context By configuring the maximum BW for DL and UL traffic, and thus enforcing boundaries, correct QoS negotiations can be ensured. [edit services epg pgw apn apn-name pdp-context] policing { maximum-bandwidth-downlink value; maximum-bandwidth-uplink value; no-policing; } [edit services epg pgw rule-space name bandwidth-control] throughput-limitation profile-name { access-control-rule 111 112 113]; } [edit services epg pgw rule-space name bandwidth-control throughput-limitation profile-name] uplink-limitation 64; downlink-limitation 128; To configure a throughput limitation profile for SACC.
  • 18. Configuring QoS Class for GTP-C Traffic By configuring GTP-C QoS class, higher efficiency and reliability of signaling packets can be ensured. [edit services epg pgw gtp] diffserv dscp-name; By default, af31 is used, which is assured forwarding class 3, low drop precedence, for all GTP-C traffic. [edit services epg pgw gtp] diffserv AF31; [edit services epg pgw gtp] allocation-retention-priority { high-priority value; medium-priority value; }