Download X30-20060522-007 CDMA2000 Packet Data Network

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Intelligent maintenance system wikipedia , lookup

Transcript
CDMA2000 Packet Data Network Evolution
2006.5.17
Zhong Xin: [email protected]
Wang Jie: [email protected]
Leo Anderson: [email protected]
Huawei Technologies Co., Ltd. grants a free, irrevocable license to 3GPP2 and its Organizational 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 all or portions of this contribution; and at the Organizational
Partner's sole discretion to permit others to reproduce in whole or in part such contribution or the resulting
Organizational Partner's standards publication. Huawei Technologies Co., Ltd. is 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 Huawei Technologies Co., Ltd. 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 Huawei Technologies Co., Ltd.. Huawei Technologies Co., Ltd.. specifically reserves the right to amend or
modify the material contained herein and to any intellectual property of Huawei Technologies Co., Ltd.. other than
provided in the copyright statement above.
Outline

Network Architecture

Mobility Management

Security

Service Based Bearer Control

Cross-technology Interworking

Appendix: Optional Network Architectures
2
Network Architecture
HA
WiMAX
Backbone IP Network
AAA
WLAN
LMHA
LMHA
DHCP
Server
1x/HRPD
AGW
S4
S3
U2
AGW Pool
AGW
LMHA: Local Mobility Home Agent
AGW: Access Gateway
RRM
RRM
RRM: Radio Resource Management
S2
Control Plane Interface
BTS
BTS
BTS
BTS
User Data Plane Interface
Air Interface
Air Interface
AT
AT
3
Entity Functions (1)
Access Gateway (AGW) Functions
 First-Hop Router for the MS/AT
 Mobility Management
 Session Management
 DHCP Relay/Server
 Authentication Functions
 Accounting Functions
 RADIUS Client (for authentication and accounting)
 TFT
 Policy enforcement function (flow based…)
 RLP
 Header Compression (mandatory if RLP is located in AGW, optional if RLP is
located in BTS)
 Security (Ciphering / Integrity Protection) (if RLP is located in AGW)
4
Entity Functions (2)
Local Mobility Home Agent (LMHA) Functions

Controlling/ Delegating IP address to the MS/AT

Mobility Management
Radio Resource Management (RRM) Functions

Radio Resource Management (Admission Control, Load Control and so on)

Radio Session Management

Session Transfer

Radio Link Management:

Handoff control
Base Transceiver System (BTS) Functions

Radio Signal Transceiver

Base Band Processing

Radio Resource Dynamic Scheduling
5
Key Concepts

MIP is used to support handover between different access networks.

AGWs in a specific area consist of a pool for load balancing and high reliability.

Since RRM is only responsible for control plane processing, the path of control
plane between AT and AGW remains three hops, while the user data plane is
reduced to two hops.

The location of RLP termination is in AGW.
6
Interfaces
Interface between AGW and LMHA

Use IETF Standard Protocol (e.g. MIP)
Interface between RRM and RRM (S4)

Control plane interface (3GPP2 specific)

Control plane interface for handoff
Interface between RRM and AGW (S3):

Control plane interface (3GPP2 specific)

Flexible interface (multiple to multiple relationship)
Interface between AGW and BTS (U2):

User data plane interface

Flexible interface (multiple to multiple relationship)
Interface between RRM and BTS (S2):

Control plane interface (3GPP2 specific)

One to multiple relationship
7
Local route optimization intra LMHA
Plain data
LMHA
LMHA
AGW 1
AGW 2
AT1
AT2
User traffic without optimization
Tunneling data
AGW 1
AGW 2
AT1
AT2
User traffic with optimization
Note: if communication peers are under the same LMHA area, route optimization
may be desirable for efficiency.
8
Inter-AGW Dormant Handoff
AT
Target
RRM
Source
RRM
Target
AGW
Source
AGW
1. User Data
LMHA
User Data
2. AT goes to
dormant and roams
3. Session Transfer
4. Selects
Target AGW
5. HO Request
6. Context Transfer
7. HO Response
8. Binding Update (binding AT’s
IP addr to Target AGW’s IP addr)
9
User Data
Inter-AGW Active Handoff
AT
Target
RRM
Source
RRM
Target
AGW
Source
AGW
1. User Data
LMHA
User Data
User Data
2. Pilot Reporting
3. Session Transfer
4. Handoff
5. Selects
Target AGW
6. HO Request
7. Context Transfer
8. HO Response
9. Binding Update (binding AT’s
IP addr to Target AGW’s IP addr)
10. User Data
User Data
10
User Data
Inter-LMHA Dormant Handoff (MIP)
AT
Target
RRM
Source
RRM
Target
AGW
Source
AGW
1. User Data
Target
LMHA
User Data
2. AT goes
to dormant
and roams
3. Session Transfer
4. Selects
Target AGW
5. HO Request
6. Context Transfer
7. HO Response
8. Binding Update (binding AT’s
IP addr to Target AGW’s IP addr)
9. Mobile IP Registration with HA
11
Source
LMHA
HA
User Data
User Data
Inter-LMHA Active Handoff (MIP)
AT
Target
RRM
Source
RRM
Target
AGW
Source
AGW
1. User Data
Target
LMHA
User Data
Source
LMHA
HA
User Data
User Data
2. Pilot Reporting
3. Session Transfer
4. Handoff
5. Selects
Target AGW
6. HO Request
7. Context Transfer
8. HO Response
9. Binding Update (binding AT’s
IP addr to Target AGW’s IP addr)
10. Mobile IP Registration with HA
11. User Data
User Data
12
User Data
User Data
Inter-LMHA Active Handoff (SIP) - option 1
AT
Target
RRM
Source
RRM
Target
AGW
Source
AGW
1. User Data
Target
LMHA
Source
LMHA
User Data
User Data
User Data
User Data
2. Pilot Reporting
3. Session Transfer
4. Handoff
5. Selects
Target AGW
6. HO Request
7. Establish
Bidirectional Tunnel
8. HO Response
9. User Data
User Data
13
Inter-LMHA Active Handoff (SIP) - option 2
AT
Source
RRM
Target
RRM
Source
LMHA
Target
LMHA
Source
AGW
Target
AGW
User Data
1. User Data
User Data
2. Pilot Reporting
3. Session Transfer
4. Handoff
5. Selects
Target AGW
6. HO Request
7. Context Transfer
8. HO Response
9. Binding Update (binding AT’s
IP addr to Target AGW’s IP addr)
10. Establish
Bidirectional
Tunnel
11. User Data
User Data
14
User Data
User Data
Security Architecture Overview
HA
Backbone IP Network
AAA
LMHA
LMHA
AGW
(RLP)
AGW
(RLP)
AGW Pool
Network access authentication and
authorization
RRM
RRM
BTS
BTS
AT
BTS
U-plane ciphering and optional
integrity protection. C-plane
integrity protection and optionally
ciphering.
C-plane integrity protection and
optionally ciphering between AT
and RRM
BTS
AT
C-plane security associations
between AGW and RRM
15
Security Association in network
Each AT has a SA with AGW

protect User plane traffic of AT

protect signaling between AT and AGW

AGW can assign encrypted temporary ID to AT for preventing AT tracking
Each RRM has a SA with AGW

encrypt and integrity protect signaling between RRM and AGW

protect key( between AT and RRM ) transfer from AGW to RRM
Each AT has a shared key with specific RRM

Against fake RRM attack

integrity and optional encrypt protect signaling between RRM and AT
16
Key Hierarchy
MSK
[KAT_RRMa KAT_RRMb]
KAT_RRMa

AT and AGW have the MSK (Master Session
Key).

MSK is a result of authentication between AT and
AAA-server (EAP-AKA etc.). AAA server
transfers the MSK to AGW.

AGW derives RRM specific key (i.e. KAT_RRM)
form MSK, RRM identity is involved in derivation.
AGW can send multiple RRM identity to AT to
enable AT computing multiple KAT_RRM
simultaneously.

AGW sends KAT_RRM to RRM using SA between
them.

Session key is shared between AT and AGW, and
is derived from MSK also.
Session key
AGW
(RLP)
RRM b
RRM a
BTS
BTS
AT
MSK
KAT_RRMa KAT_RRMb
Session key
17
SBBC Architecture (non roaming)
Data
Signaling
AF
HPLMN
Tx
LMHA
PCRF
PCRF
AF:
Application Function
AGW:
Access Gateway
LMHA:
Local Mobility Home Agent
PCEF:
Policy and Charging Enforcement Function
PCRF:
Policy and Charging Rule Function
H-PCRF:
Home Policy and Charging Rule Function
V-PCRF:
Visited Policy and Charging Rule Function
Ty
Ty
AGW(PCEF)
AGW(PCEF)

Different AGWs may connect different PCRFs

PCEF locates in AGW

Inter-AGW handoff may need PCEF relocation
18
SBBC Architecture (roaming)
HPLMN
AF
Tx
Data
H-PCRF
Signaling
Ty
When AF is in HPLMN
VPLMN
 AF
connects with H-PCRF
LMHA

V-PCRF
Ty
AGW(PCEF)
V-PCRF acts as a proxy or a relay agent
between AGW and H-PCRF
AGW(PCEF)
19
SBBC Architecture for roaming 2
HPLMN
Data
H-PCRF
Signaling
When AF is not in HPLMN
Tx
AF
Options 1
 AF
Ty

Tx
VPLMN
connects with H-PCRF
V-PCRF acts as a proxy or a relay agent
between AGW and H-PCRF
Option 2:
LMHA
V-PCRF
 AF
Ty
AGW(PCEF)
connects with V-PCRF directly
 AF-related
AGW(PCEF)
information needn’t to be passed
between the visited PCRF and the home PCRF

V-PCRF gets home-related information from
H-PCRF via Ty.
20
Cross-technology Inter-working
Case 1: Interworking with other access network within the same LHMA,
access network controlled by one operator
CDMA Home service
network
AAA
HA
IWU: Inter-Working Unit
It served as gateway for user to
access CDMA PS service via WALN
/WIMAX
internet
LMHA
IWU
AGW
AT access Internet via
WLAN/WIMAX
CDMA based Access control
and Authentication
Other access network
(WLAN/WIMAX)
CDMA Access network
Access CDMA PS service
network via WLAN/WIMAX
Access CDMA PS service
network via CDMA AN
AT
Note: In case of AT only Supporting SIP,IWU should act as a 21
proxy MIP.
Cross-technology Inter-working
Case 2: Interworking with other access network within the HA , access
network controlled by same or different operator
CDMA Home service
network
AAA
HA
internet
IWU: Inter-Working Unit
It served as gateway for user to
access CDMA PS service via WALN
/WIMAX
LMHA
IWU
AT access Internet via
WLAN/WIMAX
AGW
Other access network
(WLAN/WIMAX)
CDMA Access network
CDMA based Access control
and Authentication
Access CDMA PS service
network via WLAN/WIMAX
Access CDMA PS service
network via CDMA AN
AT
22
Requirement of Cross-technology Inter-working
Inter-working unit (IWU) function

support access to cdma2000 packet Data service via the WLAN/WIMAX system.

act as proxy MIP function when AT only support SIP.

MIP is the Interface between IWU and HA(LMHA)
Network selection

Terminal should provide the auto and manual network selection according to network
capability、service characteristics and cost.

User shall may have the capability to prioritize the selection of access system.

Home Operator may have the capability
to define preferred
or forbidden
WLAN/WIMAX access network

Network may direct user to the appropriate access technology according to service and
current network capability in order to manage network loading.
Service continuity while switching across different access network
23
Appendix: Optional Network Architecture 1
HA
AAA
Backbone IP Network
LMHA: Local Mobility Home Agent
LMHA
LMHA
DHCP
Server
AGW: Access Gateway
RRM: Radio Resource Management
Control Plane Interface
AGW
AGW Pool
AGW
User Data Plane Interface
S2
Air Interface
U2
BTS
(RRM)
BTS
(RRM)
BTS
(RRM)
RRM Combined with
BTS as one entity
BTS
(RRM)
Air Interface
AT
AT
24
Appendix: Optional Network Architecture 2
HA
AAA
Backbone IP Network
LMHA: Local Mobility Home Agent
LMHA
LMHA
DHCP
Server
AGW: Access Gateway
RRM: Radio Resource Management
AGW
(RRM)
Control Plane Interface
AGW
(RRM)
User Data Plane Interface
S2
Air Interface
U2
BTS
BTS
BTS
RRM Combined with
BTS as one entity
BTS
Air Interface
AT
AT
25
Considerations about Optional Architectures
Optional Architecture 1

Faster session setup and activation/deactivation, faster intra-BTS handoff

More complex inter-BTS handoff
Optional Architecture 2

Less 3GPP2 specific entities than other options

Difficult to support AGW pool because RRM is coupled with AGW

Hard to define S2 & U2 as an open interface
26