SlideShare a Scribd company logo
1 of 82
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 1
LTE Outbound Roaming
Session for PCRF
Samir Mohanty
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 2
Agenda
 Overview
 Roaming Network Architecture
 QoS in details
 PCRF Roaming Feature
 Configuring Roaming Tables
 Lab Session
 Q&A
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 3
LTE Outbound Roaming Overview
 Service to ATT LTE subscribers roaming on
another carrier’s PLMN network with compatible
LTE devices.
 Serving both 2G/3G and 4G roaming needs for
outbound LTE subscribers.
 Traffic will pass through the IXC Zone, which is a
new zone physically connected to the core zone in
the Gn VRF.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 4
LTE Roaming Architecture
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 5
GERAN/UTRAN Roaming Architecture
with S4-SGSN
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 6
GERAN/UTRAN Roaming Architecture
with Gn/Gp SGSN connected to
PGW
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 7
Nodes, Interfaces and Protocols
Node Interface Protocol
SGW – PGW S8 GTP (GTP-C 3GPP TS 29.274 and GTP-
U 3GPP TS 29.281)
MME - HSS S6a Diameter Base Protocol (IETF RFC 3588)
and 3GPP TS 29.272)
S4-SGSN - HSS S6d Diameter Base Protocol (IETF RFC 3588)
and 3GPP TS 29.272)
Gn/Gp SGSN -
HLR
Gr MAP protocol over SS7
hPCRF - vPCRF S9 Diameter Base Protocol (IETF RFC 3588)
and 3GPP TS 29.125)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 8
3GPP and GSMA
 3GPP Specs describe 10 ways to roam
 GSM IR.88 reduces the number to 4
 Interfaces to support:
1. S8: Inter-PLMN reference point providing user and control plane between
the Serving GW in the VPLMN and the PDN GW in the HPLMN. S8 is the
inter PLMN variant of S5. The S8 interface (GTP based) uses GTP version 1
for the User plane, and GTP version 2 for the Control plane. Nodes supporting
the S8-GTP based interface are compliant to 3GPP TS 29.274 Release 8 or
later, and 3GPP TS 29.281 Release 8 or later.
2. Gp: Inter-PLMN reference point providing user and control plane between
the SGSN in the VPLMN and the PDN GW in the HPLMN acting as a GGSN.
Gp is the inter PLMN variant of Gn.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 9
Scenario 1: HPMN only has PGW as the gateway
for roaming, 2G/3G Access via Gp interface
NOTE: For simplicity, HSS, PCRF, and MME
are omitted in the figures.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 10
Scenario 2: HPMN has both GGSN and PGW as
the gateway for roaming, 2G/3G Access via Gp
interface
NOTE: For simplicity, HSS, PCRF, and MME
are omitted in the figures.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 11
Scenario 3: HPMN has only PGW as the gateway
for roaming, 2G/3G Access via S4/S8 interfaces.
NOTE: For simplicity, HSS, PCRF, and MME
are omitted in the figures.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 12
Scenario 4: HPMN has both PGW and GGSN as
the gateway for roaming, 2G/3G Access via S4/S8
or Gp interfaces
NOTE: For simplicity, HSS, PCRF, and MME
are omitted in the figures.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 13
SMS over SGs Roaming Architecture
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 14
Circuit Switched Fallback (CSFB)
Roaming Architecture
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 15
GRX Network
 GRX: GRPS Roaming eXchange
 GRX created to carry GTP-tunnels between
different GSM operators
 GRX interconnects in excess of 300 networks and
has proven highly successful
 GRX specification does not meet requirements of
an all-IP LTE network
 IPX as replacement
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 16
GRX Model (GPRS Roaming eXchage)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 17
IPX Network
 IPX: IP Packet eXchange
 IPX is an inter-Service Provider IP backbone
network architecture which connects Mobile
Network Operators (MNOs), Fixed Network
Operators (FNOs) Internet Service Providers (ISPs)
and Application Service Providers (ASPs)
 Core enhancement to GRX are end-to-end QoS
and introduction of IPX Proxy
 IPX is isolated from the public Internet and security
rules are defined to prevent unintended access
to/from
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 18
IPX Model (IP eXchange)
End-to-end SLA
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 19
GRX and IPX Networks
 GRX becomes one of the Service Community types
in the IPX Network
 Only Service Providers that are GPRS/UMTS/LTE
network operators connect to the GRX
 Other types of Service Providers in the IPX Network
do not connect to the GRX service
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 20
GRX and IPX Networks (cont.)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 21
Aicent IPX
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 22
ATT Logical Architecture
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 23
Impacted Elements
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 24
Roaming Architecture with DEA
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 25
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 26
Syniverse IPX Topology
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 27
SPGW/GGSN Connectivity to VPLMN
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 28
Overall ATT Mobile Core
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 29
ASR5500 Overview
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 30
Neo Consumer Architecture
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 31
DNS Flow Diagram
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 32
High Level Logical View of IXC Zone
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 33
High Level Logical Network View
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 34
Functions of IXC Zone
 Access to GRX/IPX providers for both inbound and
outbound roaming.
 Access layer for roaming specific platforms such as
DEA and IXC DNS.
 Security between external GRX/IPX providers and
core zone.
• A pair of IXC firewalls will control access into the IXC
zone.
• There will also be intrusion protection systems deployed
in the zone to inspect all DNS traffic.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 35
EPS Bearers
 EPS bearers provide the UE access to PDN
services and associated applications
 Default Bearer is established during initial attach
and maintained throughout the lifetime of the
connection (always-on IP connectivity)
 Additional Dedicated Bearers can be established
dynamically when UE requests specific services
(e.g. VoLTE)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 36
LTE Bearer Stacking
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 37
ESP Bearers Types
 2 types of EPS Bearers
 Guaranteed Bit Rate (GBR)
Associated ARP and QCI
Allocates resources at admission control
May have separate Maximum Bit Rate (MBR)
 Non-Guaranteed Bit Rate (non-GBR)
Associated ARP and QCI
No resource reservation
May have a Maximum Bit Rate (MBR)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 38
EPS Bearer Types (cont.)
 GBR bearers are established on demand
 Inactivity timers used to free up resources
 Non-GBR bearers can remain established for long
periods (always connected)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 39
QoS Performance Measures
 Throughput: Bit rate, i.e. speed
 Delay: Specified by the packet delay budget. LTE
defines nine categories for delay, with 50 ms being
tightest and 300 ms being the slackest. The latter
value is used for delay tolerant applications
 Packet Loss: Defined as the Packet Error Loss
Rate, and is similar to the packet delay budget in
having nine categories with 10−6 being best and
10−2 being the worst
 Priority: Specified by the Allocation/Retention
Priority (APR) parameter
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 40
Service Level QoS Parameters
 Applied per SDF (Service Data Flow) or per SDF
aggregate
 Parameters are:
 QCI: QoS Class Identifier
 ARP: Allocation and Retention Priority
 GBR: Guaranteed Bit Rate
 MBR: Maximum Bit Rate
 AMBR: Aggregate Maximum Bit Rate
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 41
QCI and ARP
 QoS Class Identifier (QCI)
To control packet forwarding treatment
 Allocation and Retention Priority (ARP)
To decide if bearer establishment can be accepted or
rejected in case resource limitations exist
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 42
QoS Class Identifier
 QCI: QoS Class Identifier
 Used as a reference to a specific packet forwarding
behavior (e.g. packet loss rate,packet delay budget)
to be provided to a service data flow (SDF)
 May be implemented in the access network by the
QCI referencing node specific parameters that
control packet forwarding treatment (e.g.
scheduling weights, admission thresholds, queue
management thresholds, link layer protocol
configuration, etc.), that have been pre-configured
by the operator at a specific node(s) (e.g. eNodeB).
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 43
Standardized QCI Values
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 44
Allocation/Retention Priority (ARP)
 ARP encoding:
 PCI: Pre-emption Capability
 PL: Priority Level
 PVI: Pre-emption Vulnerability
Bits
Octets 8 7 6 5 4 3 2 1
1 Type = 155 (decimal)
2 to 3 Length = n
4 Spare Instance
5 Spare PCI PL Spare PVI
6 to (n+4) These octet(s) is/are present only if explicitly specified
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 45
Priority Level
 PL: Priority Level
 Used for deciding whether a bearer establishment
or modification request can be accepted or needs
to be rejected in case of resource limitations
 Typically used for admission control of GBR traffic
 Also used to decide which existing bearers to pre-
empt during resource limitations
 Values 1 to 15 with 1 as the highest priority level
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 46
Pre-emption Vulnerability
 PVI: Pre-emption Vulnerability
 1-bit value: 0 or 1
 Indicates whether a service data flow can lose
resources assigned to it in order to admit a service
data flow with a higher priority level
 Enabled: 0
 Disabled: 1
 Default EPS-Bearer has PVI enabled
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 47
Pre-emption Capability
 PCI: Pre-emption Capability
 1-bit value: 0 or 1
 Indicates whether a service data flow can get
resources that were already assigned to another
service data flow with a lower priority level
 Enabled: 0
 Disabled: 1
 Default EPS-Bearer has PCI disabled
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 48
Dedicated EPS Bearer Rates
 GBR (Guaranteed Bit Rate): Network resources
allocated based on GBR are fixed and do not
change after bearer establishment or modification.
This is hence a guaranteed service data flow.
 MBR (Maximum Bit Rate): This parameter limits the
bit rate that can be expected to be provided to GBR
bearer, and is enforced by network shaper to
restrict the traffic to its maximum bit rate
agreement.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 49
Default EPS Bearer Rates
 AMBR (Aggregate Maximum Bit Rate): This
parameter is used for non-GBR flows, and has two
types, APN-AMBR and UE-AMBR
 APN-AMBR (Access Point Name AMBR): The
APN-AMBR parameter refers to the maximum bit
rate that can be consumed by all non-GBR bearers
and all PDN connections of a specific APN. This
parameter is enforced in both the downlink and the
uplink.
 UE-AMBR (User Equipment AMBR): refers to the
maximum bit rate allowed for all non-GBR bearer
aggregates for the respective UE. The parameter is
enforced in both the downlink and the uplink.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 50
Uplink/Downlink
 GBR and MBR are defined per bearer while the
AMBR parameters are defined per a group of
bearers
 All throughput parameters (GBR, MBR, APN-AMBR
and UE-AMBR) have two components, one for
downlink and another for uplink.
 Uplink and downlink are usually set to different
values (higher downlink)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 51
Default Bearer Setup
HSS sends APN-
AMBR, ARP and
QCI to MME
HSS sends APN-
AMBR, ARP and
QCI to MME
MME stores
receicev QoS
values in UE
context
MME stores
receicev QoS
values in UE
context
APN-AMBR/QCI/ARP
sent in CSR
APN-AMBR/QCI/ARP
sent in CSR
APN-
AMBR/QCI/ARP
forwarded to PCRF
APN-
AMBR/QCI/ARP
forwarded to PCRF
PCRF modifies
QoS values if
needed and
responds back to
PGW with new
values
PCRF modifies
QoS values if
needed and
responds back to
PGW with new
values
PGW forwards
new values in
response
PGW forwards
new values in
response
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 52
ATT QoS Settings for Default EPS Bearer
 APN-AMBR based on SSTI (Subscribed Speed Tier
Indicator) from MIND
 QCI set to 8
 ARP: Priority 10, PCI and PVI enabled
Speed Tier
Indicator
APN-AMBR DL APN-AMBR UL
Low 3.072Mbps (LTE/3G) 3.072Mbps (LTE/3G)
Medium 6.144Mpbs(LTE/3G) 6.144Mpbs(LTE) – 5.696Mbps
(3G)
High 70Mbps(LTE) – 21Mbps(3G) 25Mbps(LTE) – 5.696Mbps (3G)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 53
PCRF behavior in ATT
 For POST subscribers (grandfathered unlimited)
PCRF mirrors back QoS values received from PGW
 For MRC (Monthly Recurring Charge– new
subscribers or ungrandfathered) and SBP (Session
Based Pricing) based on the SSTI of the subscriber
APN-AMBR is enforced
 For MRC and SBP subscribers threshold triggers
are set in the PGW
 For MRC if the threshold is reached (e.g.
3GB/month) speed is throttled
 For SBP the session is blocked
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 54
QoS while roaming
 QoS values for on-net subscribers might not be
supported on visited PLMN
 QCI value restrictions might be in place in visited
PLMN (e.g. ATT currently does not allow QCI=7)
 Speed restrictions might be in place in visited
PLMN
 Initial HSS provided values might not be mapped as
desired in visited MME
 PCRF assigned QoS values might mot be
acceptable in visited PLMN
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 55
PCRF Roaming Feature
 Introduced to address potential QoS issues for
roaming subscribers
 Addition of 2 new tables in PCRF decision core:
 Location Mapping Table: Allows PCRF to
differentiate QoS assignments based on PLMN ID
(MCC/MNC) and APN
 QoS Mapping Table: Once PLMNID/APN
determined, allows granular QoS assignments
based on RAT type, Billing Plan and Tracking or
Routing Areas
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 56
Location Mapping Decision Table
 LocMapping Table maps the APN and PLMNID to a
ROAMING-GROUP
 ROAMING-GROUP used as Input to QoS Mapping
Table
LOCMapping Table
Input Input Output
apn plmnid ROAMING_GROUP
PHONE 302720 1
BROADBAND 302720 1
any any 0
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 57
QoS Mapping Decision Table
 QOSMapping table maps roaming_group, RAT
type, RAI/TAI, billing plan and SSTI attributes to
QoS_Ref, roaming_zone and domestic
 If QoS_Ref is not defined (operator error) then subscriber will be defaulted to POST and
QoS values will be mirrored back to PCEF
 Catch all entry for Roaming_Group=1 is to cover CCR-Update cases
QoSMapping Table
Input Input Input Input Input Input Input Input Output Output Output
ROAMING_GROUP rat_type RAI_LAC RAI_RAC TAI_TAC_HB TAI_TAC_LB billing_plan ssti QOS_REF
ROAMING_ZON
E domestic
1 EUTRAN ANY ANY ANY ANY MRC H 1 Off-Net No
1 EUTRAN ANY ANY ANY ANY SBP H 2 Off-Net No
1 ANY ANY ANY ANY ANY ANY ANY mirror    
ANY ANY ANY ANY ANY ANY ANY ANY 0    
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 58
QoS Profiles Table
 Output from the QoS Mapping Table is QoS Ref
 Assigns a specific QoS to subscriber
 AMBR values should be consistent with GTP Coding (TS29.274 and 29.060); otherwise,
PGW will choose the largest value that conforms with GTP code but lower than what's
provisioned
QoSProfiles Table
QoSRef APNAMBR-UL APNAMBR-DL QoS Class PCI PL (Priority
Level)
PVI
1 100kbps 100kbps Interactive-4 Disabled 10 Disabled
2 1500Kbps 3500Kpbs Interactive-4 Disabled 10 Disabled
3 10000kpbs 40000kbps Interactive-4 Disabled 10 Disabled
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 59
QoS Class to QCI mapping
QOS-Class to QCI mapping
QoS Class QCI
Conversational-1 1
Conversational-2 2
Streaming-1 3
Streaming-2 4
Interactive-1 5
Interactive-2 6
Interactive-3 7
Interactive-4 8
Background 9
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 60
RMS Table
 Roaming Management Service Table
 Maintained by ATT
 Downloaded nightly to PCRF
 Contains all known MCC/MNC and SGSN IP
addresses from ATT and foreign PLMNs
 Output is Roaming Zone and Domestic indicator
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 61
Decision Logic
Credit Control Request (MCC/MNC,
SGSN-IP-Address, APN) received by
PCRF from PCEF (PGW)
is
MCC/MNC
defined in
RMS table?
No
Yes
Use MCC/MNC and Roaming Zone values from RMS table
is SGSN_IP
address
defined in
RMS table?
Exit and execute the
default processing
(Roaming zone
=ON_NET, and default
QoS value configured
based on Speed Tier
and RAT type)
Exit and execute the
default processing
(Roaming zone
=ON_NET, and default
QoS value configured
based on Speed Tier
and RAT type)
No
Yes
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 62
Decision Logic (cont.)
is
ROAMING
GROUP = 0?
Select first ROAMING_GROUP to match
MCC/MNC and APN the Location Mapping Table
Yes
Exit and execute
default processing
(Roaming zone =From
RMS table, and default
QoS value configured
based on Speed Tier
and RAT type).
Exit and execute
default processing
(Roaming zone =From
RMS table, and default
QoS value configured
based on Speed Tier
and RAT type).
No
From the Qos Mapping Table select the first entry
that matches Roaming Group, RAT, TAI or RAI,
Billing Plan, SSTI
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 63
Decision Logic (cont.)
is QoS_Ref
equal to
“mirror”?
Yes
Exit and mirror back
received QoS values
Exit and mirror back
received QoS values
No
is QoS_Ref
equal to 0?
Yes
Exit and execute
default processing
(Roaming zone =From
RMS table, and default
QoS value configured
based on Speed Tier
and RAT Type)
Exit and execute
default processing
(Roaming zone =From
RMS table, and default
QoS value configured
based on Speed Tier
and RAT Type)
No
• From the QoS Profiles Table (QoSProfiles)
using the QoSRef as key select QoS values
• PCRF replies with CCA-I with the selected
QoS values, either AMBR or
AMBR/QCI/ARP
• From the QoS Profiles Table (QoSProfiles)
using the QoSRef as key select QoS values
• PCRF replies with CCA-I with the selected
QoS values, either AMBR or
AMBR/QCI/ARP
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 64
Implementation
 Initial creation of Location Mapping Table and QoS
Mapping Table
 Done as part of the Implementation Guide
 Following slides will cover the addition of a visited
PLMN for customized QoS assignment to roaming
ATT subscribers
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 65
PCRF Log in
 Log in to PCRF, click Cisco logo
 Select Decision Tables
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 66
Decision Tables
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 67
Location Mapping Table
 Select Location Mapping Table
 Use green down arrow key to add a row and green minus sign to
remove a row under Actions
 Enter new PLMN_ID, APN and ROAMING_GROUP
 At a minimum, LOCMapping table should have the catch-all entry
(*ANY*,*ANY*,0)
Add
Remove
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 68
Import table from CSV file
 In place of manual entry, a CSV file is imported
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 69
Select CSV file to import
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 70
QoS Mapping Table
 Select QoS Mapping Table
 Use green down arrow key to add a row and green minus sign
to remove a row under Actions
 At a minimum, QOSMapping table should have the catch-all
entry
Add
Remove
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 71
Import table from CSV file
 In place of manual entry, a CSV file is imported
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 72
Select CSV file to import
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 73
QoS Defintion
 Two types of QoS definitions
 APN Aggregate: To set only APN-AMBR DL/UL
 Extended Default EPS Bearer: To set APN-AMBR
DL/UL, QCI and ARP
 QoS Definitions are named and an appropriate
naming scheme is required, e.g.:
AGG_LOR_01
AGG_LOR_EXT_01
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 74
APN Aggregate Definition
 Log in to PCRF and select PCRF
 Go to Configuration->QOS -> QOS Information
 Click “+” to add new QOS. Select APN Aggregate
for QOS Level
 Populate the necessary fields.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 75
APN Aggregate Definition (cont.)
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 76
Extended Default EPS Bearer
 Log in to PCRF and select PCRF
 Go to Configuration->QOS -> QOS Information
 Click “+” to add new QOS. Select Extended Default
EPS Bearer for QoS Level
 Populate the necessary fields.
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 77
Extended Default EPS Bearer
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 78
Import CSV files
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 79
Lab Session
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 80
Q&A
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 81
Thank You
Lte outbound roaming_session

More Related Content

What's hot

SGSN- serving gprs support node - Platform - HW, SW and CLI
SGSN- serving gprs support node  - Platform - HW, SW and CLI SGSN- serving gprs support node  - Platform - HW, SW and CLI
SGSN- serving gprs support node - Platform - HW, SW and CLI Mustafa Golam
 
2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network
2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network
2G / 3G / 4G / IMS / 5G Overview with Focus on Core NetworkHamidreza Bolhasani
 
Simplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach ProcedureSimplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach Procedure3G4G
 
Technical_Training_of_5G_Networking_Design.pptx
Technical_Training_of_5G_Networking_Design.pptxTechnical_Training_of_5G_Networking_Design.pptx
Technical_Training_of_5G_Networking_Design.pptxBijoy Banerjee
 
Simplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice CallSimplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice Call3G4G
 
LTE Attach Call Flow_Vi.pptx
LTE Attach Call Flow_Vi.pptxLTE Attach Call Flow_Vi.pptx
LTE Attach Call Flow_Vi.pptxGaganVerma62
 
Lte system signaling procedures
Lte system signaling proceduresLte system signaling procedures
Lte system signaling procedurestharinduwije
 
LTE and EPC Specifications
LTE and EPC SpecificationsLTE and EPC Specifications
LTE and EPC Specificationsaliirfan04
 
VoLTE Interfaces , Protocols & IMS Stack Explained
VoLTE Interfaces , Protocols & IMS Stack ExplainedVoLTE Interfaces , Protocols & IMS Stack Explained
VoLTE Interfaces , Protocols & IMS Stack ExplainedVikas Shokeen
 
Lte principle
Lte principleLte principle
Lte principleHatim100
 
IP Concept in LTE
IP Concept in LTEIP Concept in LTE
IP Concept in LTESofian .
 
Call flow and MS attach in LTE
Call flow and MS attach in LTECall flow and MS attach in LTE
Call flow and MS attach in LTEShashank Asthana
 

What's hot (20)

SGSN- serving gprs support node - Platform - HW, SW and CLI
SGSN- serving gprs support node  - Platform - HW, SW and CLI SGSN- serving gprs support node  - Platform - HW, SW and CLI
SGSN- serving gprs support node - Platform - HW, SW and CLI
 
2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network
2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network
2G / 3G / 4G / IMS / 5G Overview with Focus on Core Network
 
Simplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach ProcedureSimplified Call Flow Signaling: Registration - The Attach Procedure
Simplified Call Flow Signaling: Registration - The Attach Procedure
 
Ip ran v1.1
Ip ran v1.1Ip ran v1.1
Ip ran v1.1
 
Technical_Training_of_5G_Networking_Design.pptx
Technical_Training_of_5G_Networking_Design.pptxTechnical_Training_of_5G_Networking_Design.pptx
Technical_Training_of_5G_Networking_Design.pptx
 
3 g call flow
3 g call flow3 g call flow
3 g call flow
 
EVPN Introduction
EVPN IntroductionEVPN Introduction
EVPN Introduction
 
Simplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice CallSimplified Call Flow Signaling: 2G/3G Voice Call
Simplified Call Flow Signaling: 2G/3G Voice Call
 
LTE Attach Call Flow_Vi.pptx
LTE Attach Call Flow_Vi.pptxLTE Attach Call Flow_Vi.pptx
LTE Attach Call Flow_Vi.pptx
 
Lte system signaling procedures
Lte system signaling proceduresLte system signaling procedures
Lte system signaling procedures
 
IMS + VoLTE Overview
IMS + VoLTE OverviewIMS + VoLTE Overview
IMS + VoLTE Overview
 
LTE and EPC Specifications
LTE and EPC SpecificationsLTE and EPC Specifications
LTE and EPC Specifications
 
VoLTE Interfaces , Protocols & IMS Stack Explained
VoLTE Interfaces , Protocols & IMS Stack ExplainedVoLTE Interfaces , Protocols & IMS Stack Explained
VoLTE Interfaces , Protocols & IMS Stack Explained
 
PS Core Presentation
PS Core PresentationPS Core Presentation
PS Core Presentation
 
Lte signaling
Lte signalingLte signaling
Lte signaling
 
Lte principle
Lte principleLte principle
Lte principle
 
SS7 & SIGTRAN
SS7 & SIGTRANSS7 & SIGTRAN
SS7 & SIGTRAN
 
5G Network Overview
 5G Network Overview 5G Network Overview
5G Network Overview
 
IP Concept in LTE
IP Concept in LTEIP Concept in LTE
IP Concept in LTE
 
Call flow and MS attach in LTE
Call flow and MS attach in LTECall flow and MS attach in LTE
Call flow and MS attach in LTE
 

Similar to Lte outbound roaming_session

PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktycznie
PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktyczniePLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktycznie
PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktyczniePROIDEA
 
Advanced: Private Networks & 5G Non-Public Networks
Advanced: Private Networks & 5G Non-Public NetworksAdvanced: Private Networks & 5G Non-Public Networks
Advanced: Private Networks & 5G Non-Public Networks3G4G
 
Introduction to Segment Routing
Introduction to Segment RoutingIntroduction to Segment Routing
Introduction to Segment RoutingMyNOG
 
Cisco vnp workshop 16-17 april v1-0
Cisco  vnp workshop 16-17 april v1-0Cisco  vnp workshop 16-17 april v1-0
Cisco vnp workshop 16-17 april v1-0liemgpc2
 
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...PROIDEA
 
cisco-cpak-100g-lr4=-datasheet.pdf
cisco-cpak-100g-lr4=-datasheet.pdfcisco-cpak-100g-lr4=-datasheet.pdf
cisco-cpak-100g-lr4=-datasheet.pdfHi-Network.com
 
Cisco connect winnipeg 2018 gain insight and programmability with cisco dc ...
Cisco connect winnipeg 2018   gain insight and programmability with cisco dc ...Cisco connect winnipeg 2018   gain insight and programmability with cisco dc ...
Cisco connect winnipeg 2018 gain insight and programmability with cisco dc ...Cisco Canada
 
Intel® Ethernet Update
Intel® Ethernet Update Intel® Ethernet Update
Intel® Ethernet Update Michelle Holley
 
BGP filtering - Zagreb 2013
BGP filtering - Zagreb 2013 BGP filtering - Zagreb 2013
BGP filtering - Zagreb 2013 Wardner Maia
 
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...gogo6
 
Modern Wireless Communication System
Modern Wireless Communication SystemModern Wireless Communication System
Modern Wireless Communication SystemDinesh Suresh Bhadane
 
Advanced Topics and Future Directions in MPLS
Advanced Topics and Future Directions in MPLS Advanced Topics and Future Directions in MPLS
Advanced Topics and Future Directions in MPLS Cisco Canada
 
BGP evolution -from SDN perspective
BGP evolution -from SDN perspectiveBGP evolution -from SDN perspective
BGP evolution -from SDN perspectiveMiya Kohno
 
AIRCOM LTE Webinar 4 - LTE Coverage
AIRCOM LTE Webinar 4 - LTE CoverageAIRCOM LTE Webinar 4 - LTE Coverage
AIRCOM LTE Webinar 4 - LTE CoverageAIRCOM International
 
cisco-glc-fe-100lx-rgd-datasheet.pdf
cisco-glc-fe-100lx-rgd-datasheet.pdfcisco-glc-fe-100lx-rgd-datasheet.pdf
cisco-glc-fe-100lx-rgd-datasheet.pdfHi-Network.com
 
SLT-IX Setting up an Internet Exchange : Sri Lankan experience
SLT-IX Setting up an Internet Exchange : Sri Lankan experienceSLT-IX Setting up an Internet Exchange : Sri Lankan experience
SLT-IX Setting up an Internet Exchange : Sri Lankan experienceAPNIC
 
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v10020190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100M3L Inc.
 
QoS in 5G You Tube_Pourya Alinezhad
QoS in 5G You Tube_Pourya AlinezhadQoS in 5G You Tube_Pourya Alinezhad
QoS in 5G You Tube_Pourya AlinezhadPourya Alinezhad
 

Similar to Lte outbound roaming_session (20)

PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktycznie
PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktyczniePLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktycznie
PLNOG 7: Klaudiusz Staniek - MPLS a QoS - praktycznie
 
Advanced: Private Networks & 5G Non-Public Networks
Advanced: Private Networks & 5G Non-Public NetworksAdvanced: Private Networks & 5G Non-Public Networks
Advanced: Private Networks & 5G Non-Public Networks
 
Introduction to Segment Routing
Introduction to Segment RoutingIntroduction to Segment Routing
Introduction to Segment Routing
 
Cisco vnp workshop 16-17 april v1-0
Cisco  vnp workshop 16-17 april v1-0Cisco  vnp workshop 16-17 april v1-0
Cisco vnp workshop 16-17 april v1-0
 
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...
PLNOG 13: Krzysztof Konkowski: Cisco Access Architectures: GPON, Ethernet, Ac...
 
cisco-cpak-100g-lr4=-datasheet.pdf
cisco-cpak-100g-lr4=-datasheet.pdfcisco-cpak-100g-lr4=-datasheet.pdf
cisco-cpak-100g-lr4=-datasheet.pdf
 
Cisco connect winnipeg 2018 gain insight and programmability with cisco dc ...
Cisco connect winnipeg 2018   gain insight and programmability with cisco dc ...Cisco connect winnipeg 2018   gain insight and programmability with cisco dc ...
Cisco connect winnipeg 2018 gain insight and programmability with cisco dc ...
 
Intel® Ethernet Update
Intel® Ethernet Update Intel® Ethernet Update
Intel® Ethernet Update
 
BGP filtering - Zagreb 2013
BGP filtering - Zagreb 2013 BGP filtering - Zagreb 2013
BGP filtering - Zagreb 2013
 
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...
IoT Field Area Network Solutions & Integration of IPv6 Standards by Patrick G...
 
Modern Wireless Communication System
Modern Wireless Communication SystemModern Wireless Communication System
Modern Wireless Communication System
 
Advanced Topics and Future Directions in MPLS
Advanced Topics and Future Directions in MPLS Advanced Topics and Future Directions in MPLS
Advanced Topics and Future Directions in MPLS
 
BGP evolution -from SDN perspective
BGP evolution -from SDN perspectiveBGP evolution -from SDN perspective
BGP evolution -from SDN perspective
 
AIRCOM LTE Webinar 4 - LTE Coverage
AIRCOM LTE Webinar 4 - LTE CoverageAIRCOM LTE Webinar 4 - LTE Coverage
AIRCOM LTE Webinar 4 - LTE Coverage
 
cisco-glc-fe-100lx-rgd-datasheet.pdf
cisco-glc-fe-100lx-rgd-datasheet.pdfcisco-glc-fe-100lx-rgd-datasheet.pdf
cisco-glc-fe-100lx-rgd-datasheet.pdf
 
SLT-IX Setting up an Internet Exchange : Sri Lankan experience
SLT-IX Setting up an Internet Exchange : Sri Lankan experienceSLT-IX Setting up an Internet Exchange : Sri Lankan experience
SLT-IX Setting up an Internet Exchange : Sri Lankan experience
 
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v10020190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100
20190409 ip showcase-nab19_m3_l-currentstatus-st2110-over-25gbe_v100
 
Gpon Network
Gpon NetworkGpon Network
Gpon Network
 
Gpon Network
Gpon NetworkGpon Network
Gpon Network
 
QoS in 5G You Tube_Pourya Alinezhad
QoS in 5G You Tube_Pourya AlinezhadQoS in 5G You Tube_Pourya Alinezhad
QoS in 5G You Tube_Pourya Alinezhad
 

More from Samir Mohanty

More from Samir Mohanty (6)

Samir's whitepaper5g
Samir's whitepaper5gSamir's whitepaper5g
Samir's whitepaper5g
 
5 g communication with ai & iot
5 g  communication with ai & iot5 g  communication with ai & iot
5 g communication with ai & iot
 
GPRS training
GPRS trainingGPRS training
GPRS training
 
5g New Revolution
5g New Revolution 5g New Revolution
5g New Revolution
 
5 gppt
5 gppt5 gppt
5 gppt
 
Overview of python 2019
Overview of python 2019Overview of python 2019
Overview of python 2019
 

Recently uploaded

New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024BookNet Canada
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr BaganFwdays
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationSafe Software
 
Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Enterprise Knowledge
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyAlfredo García Lavilla
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brandgvaughan
 
costume and set research powerpoint presentation
costume and set research powerpoint presentationcostume and set research powerpoint presentation
costume and set research powerpoint presentationphoebematthew05
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubKalema Edgar
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsMemoori
 
Human Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsHuman Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsMark Billinghurst
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitecturePixlogix Infotech
 
"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii Soldatenko"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii SoldatenkoFwdays
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piececharlottematthew16
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...Fwdays
 
Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 3652toLead Limited
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticsKotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticscarlostorres15106
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxNavinnSomaal
 
Artificial intelligence in cctv survelliance.pptx
Artificial intelligence in cctv survelliance.pptxArtificial intelligence in cctv survelliance.pptx
Artificial intelligence in cctv survelliance.pptxhariprasad279825
 
APIForce Zurich 5 April Automation LPDG
APIForce Zurich 5 April  Automation LPDGAPIForce Zurich 5 April  Automation LPDG
APIForce Zurich 5 April Automation LPDGMarianaLemus7
 

Recently uploaded (20)

New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
New from BookNet Canada for 2024: BNC CataList - Tech Forum 2024
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
 
Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024Designing IA for AI - Information Architecture Conference 2024
Designing IA for AI - Information Architecture Conference 2024
 
Commit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easyCommit 2024 - Secret Management made easy
Commit 2024 - Secret Management made easy
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
 
costume and set research powerpoint presentation
costume and set research powerpoint presentationcostume and set research powerpoint presentation
costume and set research powerpoint presentation
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding Club
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial Buildings
 
Human Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR SystemsHuman Factors of XR: Using Human Factors to Design XR Systems
Human Factors of XR: Using Human Factors to Design XR Systems
 
Understanding the Laravel MVC Architecture
Understanding the Laravel MVC ArchitectureUnderstanding the Laravel MVC Architecture
Understanding the Laravel MVC Architecture
 
"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii Soldatenko"Debugging python applications inside k8s environment", Andrii Soldatenko
"Debugging python applications inside k8s environment", Andrii Soldatenko
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piece
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
 
Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365Ensuring Technical Readiness For Copilot in Microsoft 365
Ensuring Technical Readiness For Copilot in Microsoft 365
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticsKotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptx
 
Artificial intelligence in cctv survelliance.pptx
Artificial intelligence in cctv survelliance.pptxArtificial intelligence in cctv survelliance.pptx
Artificial intelligence in cctv survelliance.pptx
 
APIForce Zurich 5 April Automation LPDG
APIForce Zurich 5 April  Automation LPDGAPIForce Zurich 5 April  Automation LPDG
APIForce Zurich 5 April Automation LPDG
 

Lte outbound roaming_session

  • 1. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 1 LTE Outbound Roaming Session for PCRF Samir Mohanty
  • 2. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 2 Agenda  Overview  Roaming Network Architecture  QoS in details  PCRF Roaming Feature  Configuring Roaming Tables  Lab Session  Q&A
  • 3. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 3 LTE Outbound Roaming Overview  Service to ATT LTE subscribers roaming on another carrier’s PLMN network with compatible LTE devices.  Serving both 2G/3G and 4G roaming needs for outbound LTE subscribers.  Traffic will pass through the IXC Zone, which is a new zone physically connected to the core zone in the Gn VRF.
  • 4. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 4 LTE Roaming Architecture
  • 5. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 5 GERAN/UTRAN Roaming Architecture with S4-SGSN
  • 6. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 6 GERAN/UTRAN Roaming Architecture with Gn/Gp SGSN connected to PGW
  • 7. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 7 Nodes, Interfaces and Protocols Node Interface Protocol SGW – PGW S8 GTP (GTP-C 3GPP TS 29.274 and GTP- U 3GPP TS 29.281) MME - HSS S6a Diameter Base Protocol (IETF RFC 3588) and 3GPP TS 29.272) S4-SGSN - HSS S6d Diameter Base Protocol (IETF RFC 3588) and 3GPP TS 29.272) Gn/Gp SGSN - HLR Gr MAP protocol over SS7 hPCRF - vPCRF S9 Diameter Base Protocol (IETF RFC 3588) and 3GPP TS 29.125)
  • 8. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 8 3GPP and GSMA  3GPP Specs describe 10 ways to roam  GSM IR.88 reduces the number to 4  Interfaces to support: 1. S8: Inter-PLMN reference point providing user and control plane between the Serving GW in the VPLMN and the PDN GW in the HPLMN. S8 is the inter PLMN variant of S5. The S8 interface (GTP based) uses GTP version 1 for the User plane, and GTP version 2 for the Control plane. Nodes supporting the S8-GTP based interface are compliant to 3GPP TS 29.274 Release 8 or later, and 3GPP TS 29.281 Release 8 or later. 2. Gp: Inter-PLMN reference point providing user and control plane between the SGSN in the VPLMN and the PDN GW in the HPLMN acting as a GGSN. Gp is the inter PLMN variant of Gn.
  • 9. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 9 Scenario 1: HPMN only has PGW as the gateway for roaming, 2G/3G Access via Gp interface NOTE: For simplicity, HSS, PCRF, and MME are omitted in the figures.
  • 10. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 10 Scenario 2: HPMN has both GGSN and PGW as the gateway for roaming, 2G/3G Access via Gp interface NOTE: For simplicity, HSS, PCRF, and MME are omitted in the figures.
  • 11. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 11 Scenario 3: HPMN has only PGW as the gateway for roaming, 2G/3G Access via S4/S8 interfaces. NOTE: For simplicity, HSS, PCRF, and MME are omitted in the figures.
  • 12. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 12 Scenario 4: HPMN has both PGW and GGSN as the gateway for roaming, 2G/3G Access via S4/S8 or Gp interfaces NOTE: For simplicity, HSS, PCRF, and MME are omitted in the figures.
  • 13. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 13 SMS over SGs Roaming Architecture
  • 14. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 14 Circuit Switched Fallback (CSFB) Roaming Architecture
  • 15. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 15 GRX Network  GRX: GRPS Roaming eXchange  GRX created to carry GTP-tunnels between different GSM operators  GRX interconnects in excess of 300 networks and has proven highly successful  GRX specification does not meet requirements of an all-IP LTE network  IPX as replacement
  • 16. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 16 GRX Model (GPRS Roaming eXchage)
  • 17. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 17 IPX Network  IPX: IP Packet eXchange  IPX is an inter-Service Provider IP backbone network architecture which connects Mobile Network Operators (MNOs), Fixed Network Operators (FNOs) Internet Service Providers (ISPs) and Application Service Providers (ASPs)  Core enhancement to GRX are end-to-end QoS and introduction of IPX Proxy  IPX is isolated from the public Internet and security rules are defined to prevent unintended access to/from
  • 18. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 18 IPX Model (IP eXchange) End-to-end SLA
  • 19. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 19 GRX and IPX Networks  GRX becomes one of the Service Community types in the IPX Network  Only Service Providers that are GPRS/UMTS/LTE network operators connect to the GRX  Other types of Service Providers in the IPX Network do not connect to the GRX service
  • 20. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 20 GRX and IPX Networks (cont.)
  • 21. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 21 Aicent IPX
  • 22. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 22 ATT Logical Architecture
  • 23. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 23 Impacted Elements
  • 24. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 24 Roaming Architecture with DEA
  • 25. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 25
  • 26. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 26 Syniverse IPX Topology
  • 27. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 27 SPGW/GGSN Connectivity to VPLMN
  • 28. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 28 Overall ATT Mobile Core
  • 29. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 29 ASR5500 Overview
  • 30. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 30 Neo Consumer Architecture
  • 31. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 31 DNS Flow Diagram
  • 32. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 32 High Level Logical View of IXC Zone
  • 33. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 33 High Level Logical Network View
  • 34. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 34 Functions of IXC Zone  Access to GRX/IPX providers for both inbound and outbound roaming.  Access layer for roaming specific platforms such as DEA and IXC DNS.  Security between external GRX/IPX providers and core zone. • A pair of IXC firewalls will control access into the IXC zone. • There will also be intrusion protection systems deployed in the zone to inspect all DNS traffic.
  • 35. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 35 EPS Bearers  EPS bearers provide the UE access to PDN services and associated applications  Default Bearer is established during initial attach and maintained throughout the lifetime of the connection (always-on IP connectivity)  Additional Dedicated Bearers can be established dynamically when UE requests specific services (e.g. VoLTE)
  • 36. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 36 LTE Bearer Stacking
  • 37. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 37 ESP Bearers Types  2 types of EPS Bearers  Guaranteed Bit Rate (GBR) Associated ARP and QCI Allocates resources at admission control May have separate Maximum Bit Rate (MBR)  Non-Guaranteed Bit Rate (non-GBR) Associated ARP and QCI No resource reservation May have a Maximum Bit Rate (MBR)
  • 38. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 38 EPS Bearer Types (cont.)  GBR bearers are established on demand  Inactivity timers used to free up resources  Non-GBR bearers can remain established for long periods (always connected)
  • 39. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 39 QoS Performance Measures  Throughput: Bit rate, i.e. speed  Delay: Specified by the packet delay budget. LTE defines nine categories for delay, with 50 ms being tightest and 300 ms being the slackest. The latter value is used for delay tolerant applications  Packet Loss: Defined as the Packet Error Loss Rate, and is similar to the packet delay budget in having nine categories with 10−6 being best and 10−2 being the worst  Priority: Specified by the Allocation/Retention Priority (APR) parameter
  • 40. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 40 Service Level QoS Parameters  Applied per SDF (Service Data Flow) or per SDF aggregate  Parameters are:  QCI: QoS Class Identifier  ARP: Allocation and Retention Priority  GBR: Guaranteed Bit Rate  MBR: Maximum Bit Rate  AMBR: Aggregate Maximum Bit Rate
  • 41. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 41 QCI and ARP  QoS Class Identifier (QCI) To control packet forwarding treatment  Allocation and Retention Priority (ARP) To decide if bearer establishment can be accepted or rejected in case resource limitations exist
  • 42. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 42 QoS Class Identifier  QCI: QoS Class Identifier  Used as a reference to a specific packet forwarding behavior (e.g. packet loss rate,packet delay budget) to be provided to a service data flow (SDF)  May be implemented in the access network by the QCI referencing node specific parameters that control packet forwarding treatment (e.g. scheduling weights, admission thresholds, queue management thresholds, link layer protocol configuration, etc.), that have been pre-configured by the operator at a specific node(s) (e.g. eNodeB).
  • 43. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 43 Standardized QCI Values
  • 44. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 44 Allocation/Retention Priority (ARP)  ARP encoding:  PCI: Pre-emption Capability  PL: Priority Level  PVI: Pre-emption Vulnerability Bits Octets 8 7 6 5 4 3 2 1 1 Type = 155 (decimal) 2 to 3 Length = n 4 Spare Instance 5 Spare PCI PL Spare PVI 6 to (n+4) These octet(s) is/are present only if explicitly specified
  • 45. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 45 Priority Level  PL: Priority Level  Used for deciding whether a bearer establishment or modification request can be accepted or needs to be rejected in case of resource limitations  Typically used for admission control of GBR traffic  Also used to decide which existing bearers to pre- empt during resource limitations  Values 1 to 15 with 1 as the highest priority level
  • 46. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 46 Pre-emption Vulnerability  PVI: Pre-emption Vulnerability  1-bit value: 0 or 1  Indicates whether a service data flow can lose resources assigned to it in order to admit a service data flow with a higher priority level  Enabled: 0  Disabled: 1  Default EPS-Bearer has PVI enabled
  • 47. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 47 Pre-emption Capability  PCI: Pre-emption Capability  1-bit value: 0 or 1  Indicates whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level  Enabled: 0  Disabled: 1  Default EPS-Bearer has PCI disabled
  • 48. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 48 Dedicated EPS Bearer Rates  GBR (Guaranteed Bit Rate): Network resources allocated based on GBR are fixed and do not change after bearer establishment or modification. This is hence a guaranteed service data flow.  MBR (Maximum Bit Rate): This parameter limits the bit rate that can be expected to be provided to GBR bearer, and is enforced by network shaper to restrict the traffic to its maximum bit rate agreement.
  • 49. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 49 Default EPS Bearer Rates  AMBR (Aggregate Maximum Bit Rate): This parameter is used for non-GBR flows, and has two types, APN-AMBR and UE-AMBR  APN-AMBR (Access Point Name AMBR): The APN-AMBR parameter refers to the maximum bit rate that can be consumed by all non-GBR bearers and all PDN connections of a specific APN. This parameter is enforced in both the downlink and the uplink.  UE-AMBR (User Equipment AMBR): refers to the maximum bit rate allowed for all non-GBR bearer aggregates for the respective UE. The parameter is enforced in both the downlink and the uplink.
  • 50. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 50 Uplink/Downlink  GBR and MBR are defined per bearer while the AMBR parameters are defined per a group of bearers  All throughput parameters (GBR, MBR, APN-AMBR and UE-AMBR) have two components, one for downlink and another for uplink.  Uplink and downlink are usually set to different values (higher downlink)
  • 51. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 51 Default Bearer Setup HSS sends APN- AMBR, ARP and QCI to MME HSS sends APN- AMBR, ARP and QCI to MME MME stores receicev QoS values in UE context MME stores receicev QoS values in UE context APN-AMBR/QCI/ARP sent in CSR APN-AMBR/QCI/ARP sent in CSR APN- AMBR/QCI/ARP forwarded to PCRF APN- AMBR/QCI/ARP forwarded to PCRF PCRF modifies QoS values if needed and responds back to PGW with new values PCRF modifies QoS values if needed and responds back to PGW with new values PGW forwards new values in response PGW forwards new values in response
  • 52. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 52 ATT QoS Settings for Default EPS Bearer  APN-AMBR based on SSTI (Subscribed Speed Tier Indicator) from MIND  QCI set to 8  ARP: Priority 10, PCI and PVI enabled Speed Tier Indicator APN-AMBR DL APN-AMBR UL Low 3.072Mbps (LTE/3G) 3.072Mbps (LTE/3G) Medium 6.144Mpbs(LTE/3G) 6.144Mpbs(LTE) – 5.696Mbps (3G) High 70Mbps(LTE) – 21Mbps(3G) 25Mbps(LTE) – 5.696Mbps (3G)
  • 53. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 53 PCRF behavior in ATT  For POST subscribers (grandfathered unlimited) PCRF mirrors back QoS values received from PGW  For MRC (Monthly Recurring Charge– new subscribers or ungrandfathered) and SBP (Session Based Pricing) based on the SSTI of the subscriber APN-AMBR is enforced  For MRC and SBP subscribers threshold triggers are set in the PGW  For MRC if the threshold is reached (e.g. 3GB/month) speed is throttled  For SBP the session is blocked
  • 54. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 54 QoS while roaming  QoS values for on-net subscribers might not be supported on visited PLMN  QCI value restrictions might be in place in visited PLMN (e.g. ATT currently does not allow QCI=7)  Speed restrictions might be in place in visited PLMN  Initial HSS provided values might not be mapped as desired in visited MME  PCRF assigned QoS values might mot be acceptable in visited PLMN
  • 55. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 55 PCRF Roaming Feature  Introduced to address potential QoS issues for roaming subscribers  Addition of 2 new tables in PCRF decision core:  Location Mapping Table: Allows PCRF to differentiate QoS assignments based on PLMN ID (MCC/MNC) and APN  QoS Mapping Table: Once PLMNID/APN determined, allows granular QoS assignments based on RAT type, Billing Plan and Tracking or Routing Areas
  • 56. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 56 Location Mapping Decision Table  LocMapping Table maps the APN and PLMNID to a ROAMING-GROUP  ROAMING-GROUP used as Input to QoS Mapping Table LOCMapping Table Input Input Output apn plmnid ROAMING_GROUP PHONE 302720 1 BROADBAND 302720 1 any any 0
  • 57. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 57 QoS Mapping Decision Table  QOSMapping table maps roaming_group, RAT type, RAI/TAI, billing plan and SSTI attributes to QoS_Ref, roaming_zone and domestic  If QoS_Ref is not defined (operator error) then subscriber will be defaulted to POST and QoS values will be mirrored back to PCEF  Catch all entry for Roaming_Group=1 is to cover CCR-Update cases QoSMapping Table Input Input Input Input Input Input Input Input Output Output Output ROAMING_GROUP rat_type RAI_LAC RAI_RAC TAI_TAC_HB TAI_TAC_LB billing_plan ssti QOS_REF ROAMING_ZON E domestic 1 EUTRAN ANY ANY ANY ANY MRC H 1 Off-Net No 1 EUTRAN ANY ANY ANY ANY SBP H 2 Off-Net No 1 ANY ANY ANY ANY ANY ANY ANY mirror     ANY ANY ANY ANY ANY ANY ANY ANY 0    
  • 58. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 58 QoS Profiles Table  Output from the QoS Mapping Table is QoS Ref  Assigns a specific QoS to subscriber  AMBR values should be consistent with GTP Coding (TS29.274 and 29.060); otherwise, PGW will choose the largest value that conforms with GTP code but lower than what's provisioned QoSProfiles Table QoSRef APNAMBR-UL APNAMBR-DL QoS Class PCI PL (Priority Level) PVI 1 100kbps 100kbps Interactive-4 Disabled 10 Disabled 2 1500Kbps 3500Kpbs Interactive-4 Disabled 10 Disabled 3 10000kpbs 40000kbps Interactive-4 Disabled 10 Disabled
  • 59. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 59 QoS Class to QCI mapping QOS-Class to QCI mapping QoS Class QCI Conversational-1 1 Conversational-2 2 Streaming-1 3 Streaming-2 4 Interactive-1 5 Interactive-2 6 Interactive-3 7 Interactive-4 8 Background 9
  • 60. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 60 RMS Table  Roaming Management Service Table  Maintained by ATT  Downloaded nightly to PCRF  Contains all known MCC/MNC and SGSN IP addresses from ATT and foreign PLMNs  Output is Roaming Zone and Domestic indicator
  • 61. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 61 Decision Logic Credit Control Request (MCC/MNC, SGSN-IP-Address, APN) received by PCRF from PCEF (PGW) is MCC/MNC defined in RMS table? No Yes Use MCC/MNC and Roaming Zone values from RMS table is SGSN_IP address defined in RMS table? Exit and execute the default processing (Roaming zone =ON_NET, and default QoS value configured based on Speed Tier and RAT type) Exit and execute the default processing (Roaming zone =ON_NET, and default QoS value configured based on Speed Tier and RAT type) No Yes
  • 62. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 62 Decision Logic (cont.) is ROAMING GROUP = 0? Select first ROAMING_GROUP to match MCC/MNC and APN the Location Mapping Table Yes Exit and execute default processing (Roaming zone =From RMS table, and default QoS value configured based on Speed Tier and RAT type). Exit and execute default processing (Roaming zone =From RMS table, and default QoS value configured based on Speed Tier and RAT type). No From the Qos Mapping Table select the first entry that matches Roaming Group, RAT, TAI or RAI, Billing Plan, SSTI
  • 63. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 63 Decision Logic (cont.) is QoS_Ref equal to “mirror”? Yes Exit and mirror back received QoS values Exit and mirror back received QoS values No is QoS_Ref equal to 0? Yes Exit and execute default processing (Roaming zone =From RMS table, and default QoS value configured based on Speed Tier and RAT Type) Exit and execute default processing (Roaming zone =From RMS table, and default QoS value configured based on Speed Tier and RAT Type) No • From the QoS Profiles Table (QoSProfiles) using the QoSRef as key select QoS values • PCRF replies with CCA-I with the selected QoS values, either AMBR or AMBR/QCI/ARP • From the QoS Profiles Table (QoSProfiles) using the QoSRef as key select QoS values • PCRF replies with CCA-I with the selected QoS values, either AMBR or AMBR/QCI/ARP
  • 64. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 64 Implementation  Initial creation of Location Mapping Table and QoS Mapping Table  Done as part of the Implementation Guide  Following slides will cover the addition of a visited PLMN for customized QoS assignment to roaming ATT subscribers
  • 65. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 65 PCRF Log in  Log in to PCRF, click Cisco logo  Select Decision Tables
  • 66. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 66 Decision Tables
  • 67. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 67 Location Mapping Table  Select Location Mapping Table  Use green down arrow key to add a row and green minus sign to remove a row under Actions  Enter new PLMN_ID, APN and ROAMING_GROUP  At a minimum, LOCMapping table should have the catch-all entry (*ANY*,*ANY*,0) Add Remove
  • 68. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 68 Import table from CSV file  In place of manual entry, a CSV file is imported
  • 69. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 69 Select CSV file to import
  • 70. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 70 QoS Mapping Table  Select QoS Mapping Table  Use green down arrow key to add a row and green minus sign to remove a row under Actions  At a minimum, QOSMapping table should have the catch-all entry Add Remove
  • 71. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 71 Import table from CSV file  In place of manual entry, a CSV file is imported
  • 72. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 72 Select CSV file to import
  • 73. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 73 QoS Defintion  Two types of QoS definitions  APN Aggregate: To set only APN-AMBR DL/UL  Extended Default EPS Bearer: To set APN-AMBR DL/UL, QCI and ARP  QoS Definitions are named and an appropriate naming scheme is required, e.g.: AGG_LOR_01 AGG_LOR_EXT_01
  • 74. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 74 APN Aggregate Definition  Log in to PCRF and select PCRF  Go to Configuration->QOS -> QOS Information  Click “+” to add new QOS. Select APN Aggregate for QOS Level  Populate the necessary fields.
  • 75. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 75 APN Aggregate Definition (cont.)
  • 76. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 76 Extended Default EPS Bearer  Log in to PCRF and select PCRF  Go to Configuration->QOS -> QOS Information  Click “+” to add new QOS. Select Extended Default EPS Bearer for QoS Level  Populate the necessary fields.
  • 77. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 77 Extended Default EPS Bearer
  • 78. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 78 Import CSV files
  • 79. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 79 Lab Session
  • 80. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 80 Q&A
  • 81. © 2010 Cisco and/or its affiliates. All rights reserved. Cisco PublicBRKSPG-2022 81 Thank You

Editor's Notes

  1. This scenario depicts a case where SGSN has Gp interface towards PGW and SGW has S8 interface towards PGW. In this scenario, Inter-RAT handover is anchored at PGW. HPMN may also have GGSN for internal use, but that is not used for roaming in this case.
  2. This scenario depicts a case where SGSN has Gp interface towards PGW and GGSN, and SGW has S8 interface towards PGW. In this scenario, 2G/3G data access will be provided over Gp interface, and Inter-RAT handover is anchored at PGW. The SGSN can select between using GGSN and PGW if the HPMN uses different APNs for GGSN compared to PGW. If the HPMN uses the same APNs on both GGSN and PGW, then VPMN SGSN must use UE-capability as follows: If UE is LTE capable, then PGW must be selected, and if the UE is only 2G/3G capable, GGSN must be selected.
  3. This scenario depicts a case where SGSN has S4 interface towards SGW, and SGW has S8 interface towards PGW. In this scenario, Inter-RAT handover is anchored at SGW if SGW doesn't change or PGW if SGW changes. HPMN may also have GGSN for internal use, but that is not used for roaming in this case.
  4. This scenario depicts a case where SGSN has S4 interface towards SGW and also Gp interface towards GGSN, and SGW has S8 interface towards PGW. In this scenario, Inter- RAT handover is anchored at SGW if SGW doesn't change, or PGW if SGW changes. The SGSN can select between using GGSN and SGW/PGW if the HPMN uses different APNs for GGSN compared to PGW. If the HPMN uses the same APNs on both GGSN and PGW, then VPMN SGSN must use UE-capability as follows: If UE is LTE capable, then SGW/PGW must be selected, and if the UE is only 2G/3G capable, GGSN must be selected.
  5. SMS over SGs is a means to provide C-Plane based SMS over LTE access without forcing UE to fall back to overlay 2G/3G accesses. SMS over SGs is defined in 3GPP TS 23.272 [25]. If a VPMN operates a network comprising LTE plus GSM and/or UMTS access(es) and if this VPMN provides a non-IMS SMS service as well as an LTE data service to visiting subscribers, then it must support SMS over SGs. When SMS over SGs is provided for roaming, existing roaming interfaces for SMS services (E interface) will be used without any changes. Therefore, there are no new guidelines required for SMS over SGs.
  6. In some initial deployments, there will be no support of voice services on LTE. However, operators still want users on LTE to access the voice calls. This can be achieved by providing CSFB procedures. CSFB is defined in 3GPP TS 23.272 [25], in 3GPP TS 23.018 [27], and is introduced as an interim solution before VoLTE is deployed. Release 10 compliant CSFB implementation is recommended for voice fallback as some of Release 8 implementations are not deemed to be efficient enough. If a VPMN operates a network comprising LTE plus GSM and/or UMTS access(es) and if this VPMN provides a non-IMS voice service as well as an LTE data service to visiting subscribers, then it must support CSFB for voice. During the CSFB procedure, UE camping in LTE will be handed over to overlay 2G/3G access right after the call request is made. CSFB can be used for voice, Location Services (LCS) and call-independent supplementary services such as USSD. When CSFB is provided for roaming, either the Roaming Retry procedure or the Roaming Forwarding one can be implemented in the VPMN and the HPMN; it may impact the roaming interfaces. It is highly recommended to implement one or the other procedure since it increases the Mobile Terminating Call (MTC) success rate. If the Roaming Retry procedure or the Roaming Forwarding one is not implemented then the existing roaming interfaces for circuit switched services will remain unchanged.
  7. The IPX Network was originally conceived as an inter-Service Provider IP backbone created to carry GTP-tunnels (GPRS Tunnelling Protocol) via the Gp interface between the GPRS Support Nodes (GSNs) in different GSM Operators that is, data roaming. The Gp interface allowed mobile end-users to make use of the GPRS/3G services of their home network while roaming in a visited network. Later, Multimedia Messaging Service (MMS) interworking and Wireless Local Area Network (WLAN) authentication data roaming were added as supported services. This original inter-Service Provider IP backbone is in fact an Inter-PLMN (Public Land Mobile Network) IP Backbone and was termed the GRX. The GRX model is used to interconnect in excess of 300 networks and has proven highly successful.
  8. With the development of IP-based services, interworking of such services has become an industry wide challenge. The GRX model is applicable as an IP interworking solution; however the GRX specification does not meet all the requirements. It has been recognised that by adding interworking specific functionality to the GRX model and offering it to the industry, a common interconnect platform could be established for IP interworking. The enhanced GRX is called an IPX and is designed to support a variety of types of Service Providers in a secure and business sustainable way. The core enhancements to the GRX are end-to-end Quality of Service and the introduction of the IPX Proxy which facilitates interconnect cascade billing and multi-lateral interconnect agreements.
  9. The IPX introduces the requirement to support Quality of Service features end-to-end. That is, the parties involved in the transport of a service (up to the terminating Service Provider BG/firewall) are bound by end-to-end Service Level Agreements. The GRX service is an exception as this service is offered on IPX on best-effort basis. A common DNS root database supports domain name resolution. This root database may be used by all IPX parties. The IPX also introduces IPX Proxy elements. These Proxies may support interworking of specified IP services and make it possible to use cascading interconnect billing and a multilateral interconnect model. To assist with the translation of Telephone Numbers to URI the common DNS root database of the IPX will support E.164 NUmber Mapping (ENUM) capability. In the IPX, all user traffic, (that is, User Equipment (UE)-to-UE and UE-to-Server), is separated from Server-to-Server traffic. This is to fulfil the requirement of end users not being able to reach or "explore" the IPX network. The IPX is isolated from the public Internet and security rules are defined to prevent unintended access to/from it.
  10. IPX Providers should:  Support connections from Service Providers in various ways (Layers 1, 2 and 3).  Comply with IP addressing guidelines for Inter-Service Provider IP Backbone in IR.40.  Comply with DNS guidelines as specified in IR.67.  Offer DNS root service for contracted Service Providers.  Have BGP-4 routing capability.  Per Service Community: distribute all (valid) known routes to Service Providers.  Control which routes a Service Provider can advertise to a Service Community.  Offer interconnectivity to other IPXs (IPX peering).  Comply with Service Level Agreements.  Conform with security requirements laid out in IR.77.  Maintain user traffic separation. Furthermore, but with the exception of the GRX service, an IPX Provider shall:  Support end-to-end QoS requirements, described in the end-to-end quality SLA and in this document.  Create the agreements required with other IPX Providers to fulfil the end-to-end SLA. If Diameter Edge Agent is supported in the IPX network, then the IPX Provider must follow IR.88. Separation of Service Communities on IPX Networks IPX Provider shall maintain isolation between Service Communities on their IPX Network. This isolation can be logical (for example by VPNs on an IPX Network) or physical (that is, when the Service Provider connects to separate IPX Network, for example for GRX and an IPX Service).
  11. Syniverse and Aicent will deploy a pair of premise routers that will connect via GE to the IXC routers in the IXC zone. It is anticipated that there will be growth in the number of roaming specific services, especially when LBO is implemented. These service platforms will be connected to the IXC zone. The IPS signature-matching inspection will be specific to DNS application attacks and exploits.
  12. The Priority-Level AVP (AVP code 1046) is of type Unsigned 32. The AVP is used for deciding whether a bearer establishment or modification request can be accepted or needs to be rejected in case of resource limitations (typically used for admission control of GBR traffic). The AVP can also be used to decide which existing bearers to pre-empt during resource limitations. The priority level defines the relative importance of a resource request. Values 1 to 15 are defined, with value 1 as the highest level of priority. Values 1 to 8 should only be assigned for services that are authorized to receive prioritized treatment within an operator domain. Values 9 to 15 may be assigned to resources that are authorized by the home network and thus applicable when a UE is roaming. The Pre-emption-Capability AVP (AVP code 1047) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. If it is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can get resources that were already assigned to another bearer with a lower priority level. The following values are defined: PRE-EMPTION_CAPABILITY_ENABLED (0) This value indicates that the service data flow or bearer is allowed to get resources that were already assigned to another service data flow or bearer with a lower priority level. PRE-EMPTION_CAPABILITY_DISABLED (1) This value indicates that the service data flow or bearer is not allowed to get resources that were already assigned to another service data flow or bearer with a lower priority level. This is the default value applicable if this AVP is not supplied. The Default-EPS-Bearer-QoS AVP (AVP code 1049) is of type Grouped, and it defines the QoS information for the EPS default bearer. When this AVP is sent from the PCEF to the PCRF, it indicates the subscribed QoS for the default EPS bearer and/or the retained QoS for the default EPS bearer in the PCEF. When this AVP is sent from the PCRF to the PCEF, it indicates the authorized QoS for the default EPS bearer. The QoS class identifier identifies a set of IP-CAN specific QoS parameters that define QoS, excluding the applicable bitrates and ARP. When included in the Default-EPS-Bearer-QoS AVP, it shall include only non-GBR values. The Allocation-Retention-Priority AVP is an indicator of the priority of allocation and retention for the default bearer. AVP Format: Default-EPS-Bearer-QoS::= < AVP Header: 1049 > [ QoS-Class-Identifier ] [ Allocation-Retention-Priority] * [ AVP ] The Pre-emption Vulnerability AVP (AVP code 1048) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level. If it is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can lose the resources assigned to it in order to admit a pre-emption capable bearer with a higher priority level. The following values are defined: PRE-EMPTION_VULNERABILITY_ENABLED (0) This value indicates that the resources assigned to the service data flow or bearer can be pre-empted and allocated to a service data flow or bearer with a higher priority level. This is the default value applicable if this AVP is not supplied. PRE-EMPTION_VULNERABILITY_DISABLED (1) This value indicates that the resources assigned to the service data flow or bearer shall not be pre-empted and allocated to a service data flow or bearer with a higher priority level.
  13. The goal of standardizing a QCI with corresponding characteristics is to ensure that applications / services mapped to that QCI receive the same minimum level of QoS in multi-vendor network deployments and in case of roaming.
  14. The ARP priority levels 1-8 should only be assigned to resources for services that are authorized to receive prioritized treatment within an operator domain (i.e. that are authorized by the serving network). The ARP priority levels 9-15 may be assigned to resources that are authorized by the home network and thus applicable when a UE is roaming. NOTE:This ensures that future releases may use ARP priority level 1-8 to indicate e.g. emergency and other priority services within an operator domain in a backward compatible manner. This does not prevent the use of ARP priority level 1-8 in roaming situation in case appropriate roaming agreements exist that ensure a compatible use of these priority levels. The APR dictates whether a bearer establishment/modification request can be accepted or rejected in the event of conflicts in demand for network resources. At the time of exceptional network resources limitations, such as handover, ARP can be used by the eNodeB to drop a flow with a lower ARP to free up capacity. ARP, however, has no effect on the network treatment received by the flow once the flow is successfully established.