1 presentation to all tsgs e-utran hrpd interworking e-utran hrpd interworking cisco,...
DESCRIPTION
3 Presenter: Architecture – Parviz Yegani (Cisco) Functionalities and Interfaces – Mike Dolan (Alcatel-Lucent) Call Flows – Barnaba Barnowski (Nortel) Radio Configuration – George Cherian (Motorola) Supporting Company: AgendaTRANSCRIPT
1
Presentation to all TSGs E-UTRAN – HRPD Interworking
E-UTRAN – HRPD InterworkingCisco, Alcatel-Lucent, Nortel, Motorola
3GPP2 Super MeetingHollywood, CA
January 14-18, 2008
2
COPYRIGHT STATEMENT:
The contributors grant 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. The 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. The contributors specifically reserves 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.
3
Presenter: Architecture – Parviz Yegani (Cisco) Functionalities and Interfaces – Mike Dolan (Alcatel-Lucent) Call Flows – Barnaba Barnowski (Nortel) Radio Configuration – George Cherian (Motorola)
Supporting Company:
Agenda
5
EPC Objectives: Interworking of multiple access networks under the
same packet-switched core network (EPC) • 3GPP Accesses: E-UTRAN (EPS), UTRAN/GERAN.• Non 3GPP Accesses: E-UTRAN/HRPD & 1xRTT etc.
Note – Interworking between E-UTRAN and HRPD systems is the main focus of this presentation.
6
.Non-Roaming Architecture (Using S2a)
SGi
PCRF
S7
HSS
Operator’s IP Services (e.g. IMS, PSS etc.)
Wx*
HPLMN
Non-3GPP Networks
S6c
Rx+
PDN Gateway
3GPP AAA ServerS2a
S7a
Trusted non-3GPP
AccessTa*
S7c
S5
S6a
3GPPAccess
ServingGateway
7
EUTRAN–HRPD Interworking Architecture (Non-Roaming)
EUTRAN-HRPD IWK is mainly supported via interfaces S101, Sx-U(S103) and S2a.
8
EUTRAN-HRPD Interworking Architecture (Roaming I)
hPCRF
HSS
HPLMN
Wd*
eHRPD
VPLMN
vPCRF
3GPP AAA Proxy
Ta*
3GPP AAA Server
S2a
S7a
S9
SGiS7
S6c
Operator's IP Services (e.g. IMS, PSS etc.)
Rx+ Wx*
S7c
S8b
S6a
MME
Case 1: Non 3GPP anchor (PGW) is in the HPLMN
PDNGateway(PGW)
HRPD SGW
Sx-U (S103)S101
A10’/A11’
S11
3GPP2 AAA Pi
eAN/PCF
eNB
S1-MME
3GPP2 AN AAA A12
A13/A16
ServingGateway
(SGW)
S1-U
HRPD BTS
9
E-UTRAN – HRPD Interworking Architecture (Roaming II)
hPCRF
HSS
HPLMN
Wd*
S6d
vPCRF
PDNGateway(PGW)
3GPP AAA Proxy
3GPP AAA Server
S7a
S9
S7
Rx+
SGi
Wx*
Ta*
Visited network IP services or proxies to home network
services or PDN
Rx+
S5
S7c
S6a Operator's IP Services (e.g. IMS, PSS etc.)
Case 2: Non-3GPP anchor (PGW) is in the VPLMN
MME
eHRPD
VPLMN
3GPP2 AAA Pi
3GPP2 AN AAA
A12
S2a
HRPD SGW
Sx-U(S103)
A10’/A11’
eAN/PCF
A13/A16
S101
eNB
ServingGateway
(SGW)
S11
S1-MME
S1-U
HRPD BTS
11
Functionalities: HSGW (HRPD Serving Gateway)– Mobility Anchoring for inter-eAN handoff– Mobility anchoring for intra-3GPP2 mobility. (This is TBD.)– Packet routing and forwarding.– Transport level packet marking in the uplink and the downlink.– Accounting on user and service class granularity. – Uplink and downlink charging per AT, PDN, and service class
(e.g. for roaming with home routed traffic). – Event reporting to the PCRF.– Downlink Flow Mapping.– Uplink bearer binding verification with packet dropping of
“misbehaving UL traffic”.– MAG functions for S2a mobility
(i.e., Network-based mobility based on PMIPv6). – Support for Simple IPv6 and IPv4 addressing
(i.e., Simple IPv6 and Simple IPv4 with PMIPv6). (This is TBD.)– Authenticator or NAS (similar to the NAS function in X.S0011-D).– Provides the functions defined for the S7a interface.
(Whether charging rule function (CRF) is carried over this interface is TBD.)– Support for ROHC. (This is TBD.)
12
Functionalities: eAN/PCF (enhanced Access Network/Packet Control Function)(aka: RNC)
– All functionality for existing (legacy) HRPD support.
– Ability to differentiate Access Terminals (ATs) that are enhanced (eAT) and connect them to a HSGW. Legacy ATs are connected to a PDSN.
– Enhancements to the A11 signaling interface to connect to a HSGW.
– Support for the S101 interface for tunneling HRPD messages to the MME.
– Support for exchanging IP addresses and GRE keys between the HSGW and the MME to allow connection of the HSGW to existing P-GWs (Packet Data Network Gateways) currently serving the mobile.
– Support for communicating IP addresses and GRE keys from the HSGW to the MME for the creation of Sx-U interfaces for data packet forwarding at handoff.
13
Functionalities: eAT (enhanced Access Terminal)– All functionality for existing (legacy) HRPD support.
– Ability to differentiate itself to the eAN/PCF as an “enhanced” AT.
– Ability to support the IP service context being defined for eHRPD.
– Ability to support the authentication mechanism being defined for eHRPD.
– Ability to support one or multiple Simple IP addresses (IPv4 or IPv6).
14
Functionalities: PGW (Packet Data Network Serving Gateway)– Per-user based packet filtering (by e.g. deep packet inspection)
– Lawful Interception
– IP address allocation (to the UE)
– Transport level packet marking in the uplink and downlink, e.g. setting the DiffServ Code Point.
– UL and DL service level charging as defined in 3GPP TS 23.203 [6](e.g. based on deep packet inspection defined by local policy)
– UL and DL service level gating control as defined in 3GPP TS 23.203 [6]
– UL and DL service level rate enforcement as defined in 3GPP TS 23.203 [6] (e.g. by rate policing/shaping)
– DL rate enforcement based on AMBR (aggregate maximum bit rate)(e.g. by rate policing/shaping)
– DL rate enforcement based on the accumulated maximum bit rates (e.g. by rate policing/shaping)
– DHCPv4 and DHCPv6 functions (client, relay and server)
– User plane anchor for mobility between 3GPP access and non-3GPP access
– Includes the function of a PMIP LMA
15
Interfaces:
A11’/A10 (eAN/PCF to HSGW) Enhancements to the existing A11/A10 to support the enhanced functionalities and handoff with LTE.
S2a (HSGW to PGW) PMIP-based bearer path providing mobility between HSGWs, and between an LTE SGW and a HSGW.
S101 (eAN/PCF to MME) Carries encapsulated HRPD or LTE signaling to support single transmitter devices during pre-registration and handoff.
Sx-U (SGW to HSGW) Provides a bearer path for downlink data packets during handoff after the UE has broken radio contact with the source system. (Will be called S103-U.)
S7a (HSGW to PCRF) Provides policy information to the HSGW and updates to the PCRF.
Ta* (3GPP2 AAA to 3GPP AAA) Provides support for AAA functionality between 3GPP and 3GPP2 systems.
17
Active Mode Call Flows: E-UTRAN HRPD
– Pre-registration (in advance)– Preparation and Execution
HRPD E-UTRAN– Pre-registration, Preparation, and Execution
18Handover Pre-registration (A40-20080114-xxxr0 A S0022-0 – Section 3.15.2.1)(Consistent with 23.402 8.0.0 – expanded to show HRPD Pre-registration Details)
UE E-UTRAN S-GW eAN/PCF HSGW PCRF P-GW
0. UE registered in MME or an ongoing data session
1. E-UTRAN indicates to the UE that it should pre-register.
2. E-UTRAN Tunnel establishment between the UE and the E-UTRAN occurs. An S101 tunneling session is created between E-UTRAN and the eAN/PCF.
3. UATI-Request/Response (optional)
4. Session Configuration
5a. Device Level Authentication
7a. Authenticate and establish IP service contextbetween UE and HSGW over default signaling flow.
8. HRPD Session Maintenance
9. IP Environment session maintenance with HSGW.
7c. Obtain policy
information
7b. Authentication.
5b. A12 Access-Request
5c. A12 Access-Accept6a. A11
Registration-Request6b. A11
Registration-Reply
MME AAA
10. Update policy
information
E-UTRAN HRPD
19Handover Preparation & Execution (Part 1) (S2-080475)
1. CDMA measurements
3. Relocation indication
7. A11 Signalling
11. Data Forwarding
0. UE connected via E-UTRAN
2. Handoverdecision
6. Direct Transfer (S101 Session ID, SectorID, PDN GW Address, GRE keys, HRPD ConnRequest)
9a. Create forwarding tunnels Request
9b. Create forwarding tunnels Response
10. Relocation Command (Forwarding address, HRPD TCA)
11. Message X (HRPD TCA)
4. Message X (HRPD ConnRequest)
5. Message Y (HRPD ConnRequest, SectorID, Relocation Started indication)
8. S101 HO Command (S101 Session ID, Forwarding address, HRPD TCA message)
UE MMEHRPD Access
Network AAAHSGWE-UTRAN PCRFS-GWPDN GW
E-UTRAN HRPD
20Handover Preparation & Execution (Part 2) (S2-080475)
13. HRPD TCC
16. E-UTRAN Bearer Release
15a. HO Complete (S101 Session ID)
17a. Delete Bearer Request
17b. Delete Bearer Response
UE MMEHRPD Access
Network AAAHSGWE-UTRAN PCRFS-GWPDN GW
14b. Proxy Binding Update14a. A11 Signalling (PDN GW Address, GRE keys)
14d. Modification of IP-CAN Session
14c. Proxy Binding Acknowledge
14e. Ack. of IP-CAN Session Modification
15b. HO Complete (S101 Session ID)
12. HRPD AN acquires UE
E-UTRAN HRPD
21Handover Pre-registration, Preparation & Execution (Part 1) (S2-080576)
HRPD E-UTRAN
eNB MME S-GWHSGWHRPD AN P-GW
2. Decision to handover to E-UTRAN
7. Create default bearer Req
3. Message X (Attach Request)
1. HRPD Radio on
HSS PCRFUE
5. Authentication
6. Location update & Subscriber data retrieval
8. Create default bearer req or PMIP Binding Update
9. Create default bearer res or PMIP Binding accept 10. Create default bearer Res
5. Direct Transfer (S101 Session ID, Authentication)
5. Message X (Authentication)
4. Direct Transfer (S101 Session ID,Attach Request, UE Capabilities)
11. Direct Transfer (S101 Session ID, Attach Accept)12. Message X (
Attach Accept)
13. Message X (Attach Complete) 14. Direct Transfer (S101 Session ID,
Attach Complete)
22Handover Pre-registration, Preparation & Execution (Part 2) (S2-080576)
HRPD E-UTRAN
23. Release of HRPD resources
eNBMME
S-GWHSGWHRPD AN P-GW HSS PCRF
18. RRC RB establishment
17. S1 Initial UE context setup Req
16. RRC connection request / Service request
UE
15. LTE radio ON
19. S1 Initial UE context setup Complete
20. Update bearer Request
21. Update bearer Response22. HO Complete
24
Mobility from E-UTRAN to HRPD HRPD System Information
– To enable mobility from E-UTRAN to HRPD, the following HRPD parameters may be sent over E-UTRAN1
• HRPD Pre-registration allowed: This field indicates if the AT is required to perform HRPD-pre-registration while on E-UTRAN
• HRPD Pre-registration zone: This field is set to the pre-registration zone. When the AT moves from one pre-registration zone to another it will pre-register again if it was already pre-registered.
• HRPD Neighbor cell information: These fields are set to the HRPD neighbor cell information, which may include fields such as band-class, frequency, pilot-pn and other associated information
• HRPD Timing Reference: This field is set to the cdma2000 system time at the boundary of an E-UTRAN frame, to assist AT synchronization
HRPD measurements1
– To enable handoff from E-UTRAN to HRPD network, the access terminal sends radio measurements of the HRPD neighbor cells to E-UTRAN network for eNB to evaluate and decide whether a handoff from E-UTRAN to HRPD is needed
AT capabilities1
– The capabilities of the multi-mode access terminal the E-UTRAN network uses to allow E-UTRAN to HRPD mobility. One such capability information is whether access terminal supports dual receiver
1 The parameters are identified in 3GPP TR 36.938 V1.0.0
25
Mobility from E-UTRAN to cdma2000 1x cdma2000 1x System Information
– To enable mobility from E-UTRAN to cdma2000 1x, the following cdma20001x parameters may be sent over E-UTRAN1
• cdma2000 1x Neighbor cell information: These fields are set to the HRPD neighbor cell information, which may include parameters such as band-class, channel, pilot-pn and other associated information
• cdma2000 1x Timing Reference: This field is set to the cdma2000 system time at the boundary of an E-UTRAN frame, to assist AT synchronization
cdma2000 1x measurements• To enable handoff from E-UTRAN to cdma2000 1x, the radio measurements of the cdma2000 1x
neighbor cells are sent to E-UTRAN network for eNB to evaluate and decide whether a handoff from E-UTRAN to cdma2000 1x network is needed
AT capabilities• The capabilities of the multi-mode access terminal the E-UTRAN network uses to allow E-UTRAN to
HRPD mobility. One such capability information is whether AT supports dual receiver
1 The parameters are identified in 3GPP TR 36.938 V1.0.0
26
References: TS23.401v8.0.0 (as of Dec.-2007)
• GTP-based Mobility• Link: http://www.3gpp.org/ftp/Specs/html-info/23401.htm
TS23.402v8.0.0 (as of Dec.-2007)• IETF-based Mobility• Link: http://www.3gpp.org/ftp/Specs/html-info/23402.htm