The 3 GPP 2 Architecture Sridhar Machiraju CS

  • Slides: 24
Download presentation
The 3 GPP 2 Architecture Sridhar Machiraju CS 294 -3, Spring 2002, University of

The 3 GPP 2 Architecture Sridhar Machiraju CS 294 -3, Spring 2002, University of California at Berkeley

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

Introduction We saw that the 3 GPP architecture evolved from the already-existing GPRS network.

Introduction We saw that the 3 GPP architecture evolved from the already-existing GPRS network. It can be viewed as IP-based multimedia enhancements to 2 G networks. However, 3 GPP 2 has created a new architecture (there was no existing packet data service) for the 2 G and 3 G CDMA air interfaces.

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

Basic Design Philosophy of 3 GPP 2 • Leverage existing globally-accepted IETF protocols whenever

Basic Design Philosophy of 3 GPP 2 • Leverage existing globally-accepted IETF protocols whenever possible e. g. , mobile IP (for mobility), IPSec (for e 2 e security), AAA (authentication, authorization and accounting for network access). • Some advantages are – – Interoperability/roaming with existing IP networks. – Easy deployment of new services. – Well understood standards.

The Official Reference Model!

The Official Reference Model!

A Simpler Version! Control of Services IP SCP SN Base Station BTS BSC Internet

A Simpler Version! Control of Services IP SCP SN Base Station BTS BSC Internet Traditional MSC “Switching Point” SMS Packet data functions PDSN AAA PSTN HLR VLR OTAF PDN

Much More Simpler! • • • BTS – Base • Transceiver Station BSC –

Much More Simpler! • • • BTS – Base • Transceiver Station BSC – Base Station • Controller • MSC – Mobile Switching Center PDSN - Packet Data Serving Node HA – Home Agent IWF – Inter-Working Function

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

A Mobility Perspective • • • Note that, for simple IP, the HA is

A Mobility Perspective • • • Note that, for simple IP, the HA is not used. AAA is used for data service authentication. The PPP tunnel from the MS terminates at the PSDN which acts as the Foreign Agent (FA). The PSDN is the first hop IP router and performs Diffserv shaping, ingress filtering, handoff between PCFs. The PDSN is also responsible forwarding accounting information to the appropriate AAA entity. The PCF maintains a layer 2 connection with the PSDN for sending/receiving packets for MSs under its control.

The Ultimate Goal – An All-IP Network

The Ultimate Goal – An All-IP Network

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

Security and Mobility Management • 3 GPP uses GGSN, • 3 GPP 2 uses

Security and Mobility Management • 3 GPP uses GGSN, • 3 GPP 2 uses mobile IP SGSN nodes. and PSDN as FA/HA. • 3 GPP does not allow • It allows heterogeneous access. • The HLR is likely to • The PDSN uses an be used by the SGSN AAA infrastructure to for authenticating data authenticate data users. Thus, access and Access and data network authentication are separate. integrated.

Services etc. • The 3 GPP model has a • Though the specification is

Services etc. • The 3 GPP model has a • Though the specification is yet to be published, SIP-like functionality 3 GPP 2 has decided to use in the 3 types of Call SIP. State Control • In the 3 GPP 2 model, Functions (CSCF). location service is more of a database i. e. , access • Location service in the independent. 3 GPP model is tied • Link layer mobility in the closely to the access. 3 GPP 2 world is viewed as • GTP is used to provide a direct extension of link-layer mobility. mobile IP.

Note that, • Due to the lack of standards for SIP with all potential

Note that, • Due to the lack of standards for SIP with all potential applications like Vo. IP, there is a danger of 3 GPP and 3 GPP 2 coming up with incompatible extensions to SIP which would have to be harmonized sometime later. • The 3 GPP 2 specification is not as complete as the 3 GPP specification. • In the 3 GPP specification, there is an option to place a mobile IP-based Foreign Agent in the GGSN. Still, this would introduce a lot of tunneling overhead in the GGSNSGSN path (Mobile IP over GTP over IP).

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

3 GPP All-IP Network Architecture Model Applications & Services IP Multimedia Subsystem SCP CSCF

3 GPP All-IP Network Architecture Model Applications & Services IP Multimedia Subsystem SCP CSCF MGCF CSCF Legacy mobile signalling Network Multimedia IP Networks T-SGW BGCF MRF UMS R-SGW PSTN/ Legacy/External MGW HSS CS Domain 3 G-HLR G-MSC Server 3 G-SGSN 3 G-HLR Emergency Services Network 3 G-GGSN PS Domain MSC Server GMLC RAN BSS/ GERAN UTRAN MT Signaling only User Data and Signaling TE Application Service Control Transport Multimedia IP Networks

3 GPP NAM - Discussion • 3 GPP is divided into 4 planes –

3 GPP NAM - Discussion • 3 GPP is divided into 4 planes – IP Multimedia, Packet-Switched, Data. Switched and Radio Access. • At each plane, there exist data and control functions. • The picture is very disorganized especially from traditional networking perspective. – Legacy transport gateways are on the same plane as applications. – HLR and Unified Messaging Service are in limbo. – As mentioned earlier, the location service is access dependent because of its presence in the lowest layer. – The CSCF has all the functionality; there is not much modularity. • Transport and Control reside in the same functional node often. • Applications have to talk to either of CSCF, HSS, SGSN. • Qo. S is implemented in CSCF and GGSN.

3 GPP 2 All-IP Network Architecture Model Application Databases EIR DSI Sub Service Control

3 GPP 2 All-IP Network Architecture Model Application Databases EIR DSI Sub Service Control Service Application Poli Subscription Qo. S Manager Position Server AAA Transport Position Determining Entity Signaling-Control Bearer Radio Access Gateway Access Net. BTS BSC + PCF MM Other Access Networks MS FA/ Attendant Network Capability Gateway Session Control Manager Roaming Signaling Gateway MAP 41 & GSM Trunk Signaling Gateway Core Qo. S Manager Media Gateway Control Media Resource Function Media Gateway Mobile IP Home Agent PSTN Border Router Legacy MS Domain Support IP Network

3 GPP 2 NAM - Discussion • 3 GPP 2 fits into the Transport,

3 GPP 2 NAM - Discussion • 3 GPP 2 fits into the Transport, Control, Service, Application Plane model much better. • The PSDN will have only the HA/FA functionality unlike the GSN nodes. • Applications talk to only the NCG. • The modularity of this model over the 3 GPP model is seen in the case of the Qo. S manager. • The HLR, ESI, location information etc are captured as services available by querying databases.

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3

Contents • • • Introduction The 3 GPP 2 Architecture Mobility Management in 3 GPP 2 Functional comparison of 3 GPP and 3 GPP 2. Architectural comparison of 3 GPP and 3 GPP 2 • The MWIF Architecture.

The Mobile Wireless Internet Forum (MWIF) • MWIF is a non-profit association of wireless

The Mobile Wireless Internet Forum (MWIF) • MWIF is a non-profit association of wireless companies whose objective is to define a single mobile wireless and Internet architecture independent of the access technology. • They have a network reference model to achieve this. Backwards compatibility is still a problem. • Notice the service discovery server in the MWIF architecture. • The CSCF functionality is in the CSM and Session Proxy.

MWIF All-IP Network Architecture Model Resource Directory Services Application Location Server Global Name Server

MWIF All-IP Network Architecture Model Resource Directory Services Application Location Server Global Name Server Geographic Location Manager Application Functional Entities Policy Repository Transport Core Network Application(s) Service Discovery Server Authentication Server Multimedia Resource Controller Session Proxy Home IP Address Manager Accounting Server Resource Manager Session Anchor Multimedia Resource Function Mobile Attendant Access Gateway i Authorization Server Communications Session Manager (CSM) Home Mobility Manager Bearer Signaling-Control 3 rd Party Application(s) AAA Functional Entities Service Control Profile Server l IP Address Manager Access Transport Gateway Media Gateway Controller Transport Gateway Functional Entities IP Gateway Signaling Gateway Media Gateway Access Network Terminal UIM Intranet INTERNET Enterprise PSTN MAP 41 & GSM

Summary • Though the 3 GPP and 3 GPP 2 NAM differ, active harmonization

Summary • Though the 3 GPP and 3 GPP 2 NAM differ, active harmonization initiatives such as MWIF are cause for optimism. • Remember that harmonization on the access is also being tried for (or else dual mode devices would be necessary). • SIP seems to be the choice for session initiation over H. 323 and other protocols. • There are strong reasons for using IPv 6 in 3 G networks. But, all commercial 3 G networks till date use IPv 4 (since it is easier to deploy).