3GPP2 Network Evolution: Inter-working Across Technologies

January 08, 2007QUALCOMM Inc

NoticeContributors grant a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any Organizational Partner’s standards publication even though it may include portions of the contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication. Contributors are also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an Organizational Partner’s standard which incorporates this contribution. This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. Contributors specifically reserve the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement above.

2

Introduction and Scope

• AT may have multiple RF links that attach to different access technologies

• AT may attach to UMB and DO or LTE alternately using a single-RF transceiver

• Technologies to be considered for interworking:

– WLAN

– WiMAX

– 3GPP

– Any other future access network

• Scope of this discussion

– Simultaneous access through multiple interfaces

– Inter-technology handoffs

– Multi-RF and Single-RF AT considerations

3

Motivation

• Support for multi-mode single-RF and multi-RF ATs

– UMB-HRPD interworking handled in a separate slide set• UMB and HRPD interfaces may be the same or different from an IP

perspective (same or different IP address respectively)

– This set focuses on interworking across UMB and other technologies

• HRPD elements shown in the architecture for completeness

• Support for seamless mobility across technologies

• Simultaneous use of multiple interfaces for multi-mode, multi-RF ATs

– E.g., use of WLAN for high bandwidth flows, use of UMB for long-lived sessions, etc.

4

Multi-RF AT – Logical Architecture

UMB WiMAX WLAN

eBS AP eNB

IP Core Network

HA

AAA

PCRF

LTE

WiMAX BS

Prefix1ASN GW(Prefix2)

HRPD

HRPD AN

AG

PDIF(Prefix3)

SAE GW(Prefix4)PDSN

ATDual-mode Single RF

Note: Figure only shows the case where the HRPD and UMB are handled by a single RF and appear as a single IP interface on the AT

5

Multi-RF AT – Potential Physical Architecture

UMB WiMAX WLAN

eBS AP eNB

IP Core Network

HA

AAA

PCRF

LTE

WiMAX BS

Prefix1Prefix2

(ASN GW)

HRPD

HRPD AN

AG

Prefix3 (PDIF)

Prefix4 (SAE GW)PDSN

ATDual-mode Single RF

Note: Figure only shows the case where the HRPD and UMB are handled by a single RF and appear as a single IP interface on the AT

6

UMB-WLAN Interworking with Legacy PDIF

• UMB can perform interworking with legacy PDIF without any changes

• No interface needed between PDIF and AAG

• X.P0028 can be reused

• IS-835-D MIPv6 used as an example

7

WLAN Operation

UMB Operation (Bootstrapping in UMB)

UMB-WLAN Interworking (Legacy PDIF)AT PDIF AAAAAGeBS1 HA

EAP Authentication EAP Authentication

DHCP Info Exchange

Router Solicitation PMIP BU

PMIP BARouter Advertisement

MIP BU/BA

IPsec/IKEv2/EAP EAP Authentication

MIP BU/BA

IP1

HA

HoA

IP2

HoA::IP1

IP1::eBS1

Data (HoA/IP1)

Data (HoA/IP2))

HoA::IP2

UMB to WLAN Switch

8

UMB-WLAN Interworking with Enhanced PDIF

• EAP-ER can be done over WLAN

– Full EAP exchange done over UMB can be leveraged

– No need to repeat full EAP exchange

• Possible to use both interfaces simultaneously

– Multiple CoAs registered at the HA• One CoA registered as default (priority = 255)• Specific flows can be registered on a second interface

– E.g., video over WLAN, all other traffic over UMB

– Or, voice over UMB, all other traffic over WLAN

• X.P0047 Enhanced MIPv6 used as an example

9

WLAN Operation

UMB Operation (Bootstrapping in UMB)

UMB-WLAN Interworking (Enhanced PDIF)AT PDIF AAAAAGeBS1 HA

EAP Authentication EAP Authentication

DHCP Info Exchange

Router Solicitation PMIP BU

PMIP BARouter Advertisement

MIP BU/BA (Priority = 255)

IPsec/IKEv2/EAP-ER EAP-ER Authentication

MIP BU/BA (Priority < 255; Flow1)

IP1

HA

IKEv2

HoA

IP2

HoA::IP1 (Default)

IP1::eBS1

HoA:: IP1 (Default) IP2 (Flow1)

Data (HoA/IP1)

Data (HoA/IP2) (Flow 1)

10

WiMAX Operation

UMB Operation (Bootstrapping in UMB)

UMB-WiMAX InterworkingAT ASN GW AAAAAGeBS1 HA

EAP Authentication EAP Authentication

DHCP Info Exchange

Router Solicitation PMIP BU

PMIP BARouter Advertisement

MIP BU/BA (Priority = 255)

EAP-ER Authentication EAP-ER Authentication

MIP BU/BA (Priority < 255; Flow2)

IP1

HA

IKEv2

HoA

IP3

HoA::IP1 (Default)

IP1::eBS1

HoA:: IP1 (Default) IP3 (Flow2)

Data (HoA/IP1)

Data (HoA/IP3) (Flow 2)

IP Address Acquisition

11

3GPP LTE Operation

UMB Operation (Bootstrapping in UMB)

UMB-3GPP LTE InterworkingAT

SAE GW/MME AAAAAGeBS1 HA

EAP Authentication EAP Authentication

DHCP Info Exchange

Router Solicitation PMIP BU

PMIP BARouter Advertisement

MIP BU/BA (Priority = 255)

Authentication

MIP BU/BA (Priority X)

IP1

HA

IKEv2

HoA

IP4

HoA::IP1 (Default)

IP1::eBS1

HoA:: IP1 (Default) IP4 (Alternate)

Data (HoA/IP1)

Data (HoA/IP4)

IP Address Acquisition

12

Inter-Technology Handoffs• Inter-technology handoffs are no different from connecting simultaneously to

multiple technologies with different RF links– For a single-RF AT, all inter-technology transitions will be true “handoffs” (no

simultaneously active interfaces)• In this case, it is not necessary to do multiple CoA binding for CMIP

• With technologies like WLAN and WiMAX, the PDIF and BS may connect to the same AAG

– PMIP may be used between each BS/PDIF and the AAG

– PDIF may alternately directly attach to IP core; PDIF-assigned IP address may serve directly as MIP CoA

• Inter-technology intra-AAG handoffs will cause a PMIP binding at the AAG for new IP address of AT

– AT uses CMIP to register it’s IP address with the HA

– Same IP address can be preserved for single-RF AT if needed• No CMIP update needed in this case• Not ideal, since it complicates design

– Interface between different technologies needed (e.g., AAG-PDIF interface)– Some technology independent AT ID needs to be transferred across such boxes

» L2 IDs cannot be used to identify the AT any more

– Does not allow the same design for single and multi-RF ATs