1 / 11

Comparison of 3GPP2 SBBC and 3GPP PCC

3GPP-3GPP2 Workshop CIMS-080019 Puerto Vallarta, MEXICO, 24th – 25th January 2008 Source: Motorola Title: Comparison of 3GPP2 SBBC and 3GPP PCC Agenda item: 3 Document for: DISCUSSION.

thyra
Télécharger la présentation

Comparison of 3GPP2 SBBC and 3GPP PCC

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3GPP-3GPP2 Workshop CIMS-080019 Puerto Vallarta, MEXICO, 24th – 25th January 2008 Source: Motorola Title: Comparison of 3GPP2 SBBC and 3GPP PCC Agenda item: 3 Document for: DISCUSSION

  2. Comparison of 3GPP2 SBBC and 3GPP PCC Lew MiltonLewis.Milton@motorola.com+1 847 632 4393

  3. Visited PCRF PDP Proxy CRF Proxy Access Gateway (AGW) Traffic Plane Function (TPF) Policy Enforcement Point (PEP) 3GPP2 SBBC Architecture (X.S0013-012-B) Application Function (AF) (e.g., P-CSCF) Tx Home Policy & Charging Rules Function (PCRF) Policy Decision Point (PDP) Charging Rules Function (CRF) Home Network Ty Visited Network Ty

  4. 3GPP PCC Release 7 Architecture (TS 23.203) Subscription Profile Repository (SPR) AF Rx Policy and Charging Rules Function (PCRF) Sp Online Charging System (OCS) Service Data Flow Based Credit Control CAMEL SCP Gx Gy PCEF GW Gz Offline Charging System (OFCS)

  5. PDN Gateway Serving Gateway 3GPP Release 8 TS 23.401Non-roaming Architecture UTRAN SGSN HSS GERAN S3 S6a S 1 - MME S12 MME PCRF S4 S7 Rx+ S11 S10 ” LTE - Uu S5 SGi Operator’s IP Services (e.g. IMS, PSS etc.) UE E - UTRAN S1 - U

  6. 3GPP Release 8 TS 23.401 Roaming Architecture HSS PCRF S7 Rx+ S6a Operator’s IP SGi PDN Services Gateway (e.g. IMS, PSS etc.) HPLMN VPLMN S8a UTRAN SGSN GERAN S12 S3 S4 S1 - MME MME S11 S10 “ LTE - Uu ” Serving Gateway UE E - UTRAN S 1 - U

  7. 3GPP Release 8 TS 23.402Non-roaming Architecture HSS Wx* S6a PCRF S 7c Rx+ S7 Operator ' s IP SGi Services Serving PDN (e.g. IMS, PSS 3GPP Gateway Gateway etc.) Access S5 S6c S2b S7b Wm* 3GPP AAA ePDG S2a Server Wn* HPLMN S7a Non - 3GPP Networks Wu* Untrusted Trusted Non - 3GPP IP Non - 3GPP IP Access Wa* Access Ta* UE

  8. HSS Wx* Rx+ Operator's IP hPCRF S7 Services S6a (e.g. IMS, PSS SGi PDN etc.) 3GPP AAA Gateway Server HPLMN S6c S 9 S2b Wd* S8a/b vPCRF Serving 3GPP Gateway Access S7c S7b 3GPP AAA Proxy Wm* S2a ePDG VPLMN Non - Wn* Networks S7a Trusted Untrusted Non - 3GPP IP Non - 3GPP IP Access Access Wa* Ta* 3GPP Release 8 TS 23.402Roaming Architecture

  9. 3GPP/3GPP2 Policy Interfaces

  10. 3GPP2 vs. 3GPP Bearers • 3GPP2 Bearers (HRPD, UMB) - MMD Rev. B • All bearers are UE initiated • Binding done at the Access Gateway (AGW) • 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 • 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

  11. Recommendations • 3GPP2 AGW-to-PCRF Ty interface evolves to 3GPP S7a • 3GPP2 PCRF-to-PCRF Ty interface evolves to 3GPP S9 • 3GPP2 PCRF-to-AF Tx interface evolves to 3GPP Rx+ • S7c and S7a should be closely aligned • 3GPP2 access specific information should be added as a cdma2000 access specific annex to Rel. 8 TS 23.203

More Related