Transcript Document

3GPP-3GPP2 Workshop
Puerto Vallarta, MEXICO, 24th – 25th January 2008
Source:
Motorola
Title:
Comparison of 3GPP2 SBBC and 3GPP PCC
Agenda item:
3
Document for:
DISCUSSION
CIMS-080019
Comparison of 3GPP2
SBBC and 3GPP PCC
Lew Milton
[email protected]
+1 847 632 4393
3GPP2 SBBC Architecture (X.S0013-012-B)
Application Function (AF)
(e.g., P-CSCF)
Tx
Home
Policy & Charging Rules Function (PCRF)
Charging Rules
Function
(CRF)
Policy Decision
Point
(PDP)
Home Network
Ty
Visited PCRF
CRF
Proxy
PDP
Proxy
Ty
Access Gateway (AGW)
Traffic Plane
Function
(TPF)
Policy
Enforcement Point
(PEP)
Visited Network
3GPP PCC Release 7 Architecture (TS 23.203
v8.0.0)
Subscription Profile
Repository
(SPR)
AF
Rx
Sp
Online Charging System (OCS)
CAMEL
SCP
Service Data Flow
Based
Credit Control
Policy and Charging
Rules Function
(PCRF)
Gx
Gy
PCEF
GW
Gz
Offline
Charging
System
(OFCS)
3GPP Release 8 TS 23.401 v8.0.0
Non-roaming Architecture
UTRAN
SGSN
HSS
GERAN
S3
S1-MME
S6a
MME
S12
PCRF
S4
S7
S11
LTE -Uu ”
UE
Rx+
S10
Serving S5
Gateway
E-UTRAN
S1-U
PDN
Gateway
SGi
Operator’s IP Services
(e.g. IMS, PSS etc.)
3GPP Release 8 TS 23.401 v8.0.0 Roaming
Architecture
HSS
PCRF
S7
Rx+
S6a
PDN
Gateway
HPLMN
VPLMN
S8a
UTRAN
SGSN
GERAN
S12
S3
S1-MME
S4
MME
S11
S10
“LTE -Uu”
UE
Serving
Gateway
E-UTRAN
S1-U
SGi
Operator’s IP
Services
(e.g. IMS, PSS etc.)
3GPP Release 8 TS 23.402
v8.0.0 Non-roaming Architecture
HSS
Wx*
S6a
PCRF
S7c
Rx+
S7
SGi
3GPP
Access
Serving
Gateway
PDN
Gateway
Operator's IP
Services
(e.g. IMS, PSS
etc.)
S5
S6c
S2b
S7b
3GPP AAA
Server
ePDG
S2a
Wn*
HPLMN
Non-3GPP
Networks
Wm*
S7a
Trusted
Non-3GPP IP
Access
Wu*
Untrusted
Non-3GPP IP
Access
UE
Wa*
Ta*
3GPP Release 8 TS 23.402
v8.0.0 Roaming Architecture
HSS
Wx*
Rx+
hPCRF
S7
S6a
SGi
PDN
Gateway
HPLMN
Operator's IP
Services
(e.g. IMS, PSS
etc.)
3GPP AAA
Server
S6c
S9
S2b
S8a/b
3GPP
Access
Serving
Gateway
Wd*
vPCRF
S7c
S7b
3GPP AAA
Proxy
Wm*
S2a
ePDG
VPLMN
NonNetworks
S7a
Trusted
Non-3GPP IP
Access
Wn*
Untrusted
Non-3GPP IP
Access
Wa*
Ta*
3GPP2 Flows vs. 3GPP Bearers
•
•
3GPP2 Flows (HRPD, UMB) - MMD Rev. B
– All flows are UE initiated for HRPD, and UMB supports both UE and NW initiated flows
– Flow binding done at the Access Gateway (AGW)
– Tx sessions to Ty session are one-to-many
– TFTs sent by UE to AGW; AGW validates QoS via Ty with PCRF
– AGW does per flow charging
3GPP Bearers (GPRS, UMTS) – Rel. 7
– Both UE and NW initiated bearers supported
• Binding done at the PCEF for NW initiated bearers
• Binding done at the PCRF for UE initiated bearers
•
– Rx sessions to Gx sessions are one-to-one
– GGSN sends TFTs to PCRF
3GPP Bearers (EPS) – Rel. 8
– Both UE initiated and Network initiated bearers supported
– TS 23.401 has bearer binding in P-GW (none at S-GW)
• P-GW validates TFTs with PCRF via S7
– TS 23.402 has bearer binding in both the S-GW & P-GW
• Both S-GW and P-GW validate TFTs with PCRF via S7c/S7
– S-GW does aggregate charging for same QoS bearer, or per flow charging
– P-GW does per flow charging
3GPP/3GPP2 Policy Interfaces Differences
• 3GPP2 MMD SBBC Rev. B Tx vs. 3GPP PCC Rel. 7 Rx
– Tx uses the same Application ID as Rx
– Tx has optional AVP differences with Rx
• 3GPP2 MMD SBBC Rev. Ty vs. 3GPP PCC Rel. 7 Gx
– Ty has several detailed AVP differences
– Ty includes policy peering support
Recommendations
• 3GPP PCC interfaces S7, S7x and S9 should be access
independent
– 3GPP S7, S7a and S7c should support the policy, QoS
control and charging functionality of 3GPP2 Ty
– 3GPP S9 should support the policy peering functionality of
3GPP2 Ty
– 3GPP Rx+ should support the functionality of 3GPP2 Tx
• 3GPP2 access specific information should be added as
cdma2000 access specific Release 8 annex(es).
• 3GPP2 will take action to bring CRs into 3GPP SA2 and
CT3