8.3. PMIP Tunnel Operation with Multiple Binding
Error! Reference source not found. through xx-4 illustrates an example call flow for
PMIPv4 tunneling operation with multiple binding.
8.3.1 PMIP Tunnel Operation for Initial Power Up
Figure 1 shows PMIP multiple binding updates for initial power up.
AT
eBS1
eBS2
SRNC
AGW
VAAA
(Proxy)
1. Successful Access Authentication and Authorization
1'. SRNC
Receives PMNAN-RK1
2. IOS Signaling
(eBS1 receives PMN-AN-HA1 Key
and seq 1 from SRNC)
3. Link ID
4. AT Presents
Link ID to Upper
Layer
5. DAP Move Req
6. PMIP RRQ [NAI , GRE Extension (set to all zero),
eBS 1 IP address, MN-HA Authentication,
Binding Type Extension (RL+ Primary Binding)]
7. PMIP RRP (GRE Key, MN-HA
Authentication)
8. DAP
Assignment
9. IOS Signaling
10. IP Address Assignment
Figure 1
PMIP Tunnel Operation with Initial Power Up
The steps in Figure 1 are described below.
1.
The AT, SRNC, AGW, and AAA perform successful access authentication and
authorization as same as step 1 specified in section 8.2.
8.3 PMIP Tunnel Operation with Multiple Binding
1
Error! No text of specified style in document.
Error! No text of specified style in document.
HAAA
2.
The eBS and SRNC performs IOS signaling exchanges in which the SRNC sends
AGW IP Address, User Name, AAA-Session-ID, and PMN-AN-HA1 key derived
from PMN-AN-RK1 to the eBS1. The sequence number (Seq1)is also sent from the
SRNC to eBS1 (used for calculating PMN-AN-HA1 key in AGW.) (See Error!
Reference source not found. for the details.)
3.
The eBS1 presents link ID to the AT. The link ID represents the IP interface that the
AT creates to talk to IP layer.
4.
The AT presents the link ID to the upper IP layer. The upper IP layer compares the
link ID with its current link ID. If it is different, it triggers IP Address assignment.
5.
This step is optional. For AT assisted DAP move, the AT sends DAP Move Request
to the eBS1.
6.
Since the eBS1 doesn’t have GRE key, the eBS1 sends PMIP RRQ (see RFC
PMIPv4 draft) to the AGW which includes GRE extension (set to all zero), eBS1 IP
address, NAI (formatted as AAA-Session-ID@Realm, where AAA-Session-ID is
received from SRNC at step 2, and Realm is the Realm portion of User Name
received from SRNC at step 2), and MN-HA authentication extension calculated by
using PMN-AN-HA1 key received from step 2. In the MN-HA Authentication
extension, the SPI field contains the sequence number as specified in [4].. In the
PMIP RRQ, Binding Type Extension is also included to indicate this PMIP Binding
is for RL + Primary binding.
7.
The AGW verifies MN-HA Auth extension by using PMN-AN-HA1 key (PMN-ANHA1 Key = HMAC-SHA-256(PMN-AN-RK1, “Derived PMIP Key”, Seq1, eBS1 IP
Address, AGW IP Address). If authentication passes, the AGW selects a GRE key
associated with this NAI and includes it through GRE extension (see RFC GRE
Extension draft) in the PMIP RRP sent to the eBS1. Since PMIP RRQ includes
Binding Type Extension with RL and Primary indication, the AGW can send and
receive packets to and from the eBS1.
8.
This step is optional. It occurs if the step 5 is performed. The eBS1 sends DAP
Assignment to the AT.
9.
The eBS1 sends DAP notification to SRNC and other eBSes in the route set through
IOS signaling (see Error! Reference source not found. for the details.)
10. The AGW and AT performs IP address assignment if AT request for it. (See IP
address assignment call flow.)
8.3.2 PMIP Tunnel Operation for Subsequent Route Adding or Connection
Setup (Scenario 1)
Figure 2 shows PMIP multiple binding updates for subsequent route adding and DAP move.
The same call flow also applies when the AT comes from idle state and setup a connection
with the eBS2. This call flow shows RL binding and Primary binding in different steps.
Error! No text of specified style in document.
Error! No text of specified style in document.
2
8.3 PMIP Tunnel Operation with Multiple Binding
AT
eBS1
eBS2
SRNC
AGW
VAAA
(Proxy)
HAAA
1. Route Open Request
2. IOS Signaling
(eBS2 receives GRE,
PMN-AN-HA1 Key and
seq 2 from SRNC)
3. PMIP RRQ [NAI, eBS2 IP address, GRE Key, MN-HA
Authentication, Binding Type Extension (RL)]
4. PMIP RRP (GRE Key, MN-HA Authentication)
5. Route Open Accept
(Link ID)
6. DAP Move Req
7. PMIP RRQ [NAI, eBS2 IP address, GRE Key, MNHA Authentication]
9. DAP Assignment
8. PMIP RRP (GRE Key, MNHA Authentication)
10. IOS Signlaing
Figure 2
PMIP Tunnel Operation with Connection Setup or Route Adding (Scenario 1)
The steps in Figure 2 are described below.
1.
The AT sends Route Open Request to the eBS2.
2.
During IOS procedure, the eBS2 receives AGW IP address, User Name, AAASession-ID, GRE key, and PMN-AN-HA1 key and sequence (seq 2) from the SRNC.
(See Error! Reference source not found. for the details.)
3.
The eBS2 sends PMIP RRQ to the AGW including Binding Type Extension
indicating RL only in addition to BS2 IP address, NAI (formatted as AAA-SessionID@Realm, where AAA-Session-ID is received from SRNC at step 2, and Realm is
the Realm portion of User Name received from SRNC at step 2), GRE extension,
and MN-HA authentication extension. In the MN-HA Authentication extension, the
SPI field contains the sequence number as specified in [4].
4.
The AGW verifies MN-HA Auth extension by using PMN-AN-HA1 key (PMN-ANHA1 Key = HMAC-SHA-256(PMN-AN-R1, “Derived PMIP Key”, Seq2, eBS2 IP
Address, AGW IP Address). If authentication passes, the AGW sends the PMIP RRP
to the eBS2. Since PMIP RRQ includes RL Only Extension, the AGW can only
receive packets from the eBS2.
8.3 PMIP Tunnel Operation with Multiple Binding
3
Error! No text of specified style in document.
Error! No text of specified style in document.
5.
The eBS2 sends Route Open Accept to the AT. The link ID represents the IP
interface that the AT creates to talk to IP layer. It is assumed Link ID is unchanged
in this call flow.
6.
Sometimes later, the AT sends DAP Move Request to eBS2 requesting DAP
handoff. This step is optional and only is performed for AT assisted DAP move.
7.
The eBS2 sends PMIP RRQ to the AGW including NAI, GRE Key and eBS2 IP
address, and MN-HA authentication extension. In the MN-HA Authentication
extension, SPI field contains the sequence number as specified in [4].
8.
The AGW verifies MN-HA Auth extension by using PMN-AN-HA1 key (PMN-ANHA1 Key = HMAC-SHA-256(PMN-AN-RK1, “Derived PMIP Key”, Seq2, eBS2 IP
Address, AGW IP Address). If authentication passes, the AGW sends PMIP RRP to
the eBS2. Since PMIP RRQ in previous step doesn’t include Binding Type
Extension, the AGW treats it as primary binding and it can receive and send packets
from and to the eBS2. Please note if the other eBS(es) in the Route Set has
performed RL binding or RL+ Primary binding, the AGW treats other eBS(es) to be
RL binding only at this time.
9.
The eBS2 sends DAP Assignment to the AT. This step is optional and only is
performed for AT assisted DAP move.
10. The eBS2 sends DAP notification to SRNC and other eBSes in the Route Set
through IOS signaling (see Error! Reference source not found. for the details.)
8.3.3
PMIP Tunnel Operation for Subsequent Route Adding or Connection
Setup (Scenario 2)
Figure 3 shows PMIP multiple binding updates for subsequent route adding and DAP move.
The same call flow also applies when the AT comes from idle state and setup a connection
with the eBS2. This call flow shows RL binding and Primary binding in the same step for the
network initiated DAP move.
Error! No text of specified style in document.
Error! No text of specified style in document.
4
8.3 PMIP Tunnel Operation with Multiple Binding
AT
eBS1
eBS2
AGW
SRNC
VAAA
(Proxy)
HAAA
1. Route Open Request
2. IOS Signaling
(eBS2 receives session:
GRE Key, PMN-AN-HA
Key and seq from SRNC
etc)
3. Route Open Accept (Link ID)
4. PMIP RRQ [NAI , GRE Key, eBS2 IP Address,
MN-HA Authentication,
Binding Type Extension (RL+DAP)]
5. PMIP RRP (MN-HA
Authentication)
6. IOS Signaling
Figure 3
PMIP Tunnel Operation with Connection Setup or Route Adding (Scenario 2)
The steps in Figure 3 are described below.
1.
The AT sends a Route Open message to the eBS2.
2.
The eBS2 and SRNC performs IOS signaling exchanges in which the SRNC sends
session info including AGW IP address, User Name, AAA-Session-ID, GRE Key,
and PMN-AN-HA1 key derived from PMN-AN-RK1 to the eBS2. The sequence
number is also sent from the SRNC to eBS2 (used for calculating PMN-AN-HA1
key in AGW.) (See Error! Reference source not found. for the details.)
3.
The eBS2 sends Route Open Accept including link ID to the AT. The link ID
represents the IP interface that the AT creates to talk to IP layer. It is assumed Link
ID is unchanged in this call flow.
4.
The eBS2 sends PMIP RRQ (see RFC PMIPv4 draft) to the AGW which includes
eBS2 IP address, NAI (formatted as AAA-Session-ID@Realm, where AAA-SessionID is received from SRNC at step 2, and Realm is the Realm portion of User Name
received from SRNC at step 2), GRE extension received from step 2, and MN-HA
authentication extension calculated by using PMN-AN-HA1 key received from step
2. In the MN-HA Authentication extension, the SPI field contains the sequence
8.3 PMIP Tunnel Operation with Multiple Binding
5
Error! No text of specified style in document.
Error! No text of specified style in document.
number as specified in [4]. In the PMIP RRQ, Binding Type Extension is also
included to indicate this PMIP Binding is for both RL and Primary PMIP binding.
5.
The AGW verifies MN-HA Auth extension by using PMN-AN-HA1 key (PMN-ANHA1 Key = HMAC-SHA-256(PMN-AN-RK1, “Derived PMIP Key”, Seq2, eBS2 IP
Address, AGW IP Address). If authentication passes, the AGW sends the PMIP RRP
to the eBS2. Since PMIP RRQ includes RL Extension with RL and DAP indication,
the AGW can send and receive packets to and from the eBS2.
6.
The eBS2 sends DAP notification to SRNC and other eBSes in the route set through
IOS signaling (see Error! Reference source not found. for the details.)
8.3.4 PMIP Tunnel RL Deregistration
Figure 4 shows RL PMIP binding deregistration.
AT
eBS1
eBS2/
DAP
AGW
SRNC
VAAA
(Proxy)
HAAA
1. Both eBS1 and eBS2 is in Route
Set
2. AT Decides to
remove eBS1 from
the Route Set
3. Route Close
4. PMIP RRQ [NAI , GRE Key, eBS1 IP Address,
MN-HA Authentication,
Binding Type Extension (RL), Lifetime=0]
5. PMIP RRP (MN-HA
Authentication)
Figure 4
RL PMIP Deregistration
The steps in Figure 4 are described below.
1.
The eBS1 and eBS2 in the AT’s Route Set.
2.
The AT decides to remove the eBS1 from the Route Set.
3.
The AT sends Route Close to the eBS1.
4.
The eBS1 sends PMIP RRQ (see Error! Reference source not found.) with PMIP
lifetime set to 0 and Binding Type extension to the AGW to indicate this PMIP
Binding is for RL binding deregistration.
Error! No text of specified style in document.
Error! No text of specified style in document.
6
8.3 PMIP Tunnel Operation with Multiple Binding
5.
The AGW verifies MN-HA Auth extension. If authentication passes, the AGW sends
the PMIP RRP to the eBS1. Since PMIP RRQ includes RL Extension lifetime equal
to 0, the AGW stop receiving the packets from the eBS1.
8.3.6 U6-PMIP Deregistration
Figure 5 shows U6-PMIP binding deregistration. The U6-PMIP binding deregistration is
performed autonomously by the AGW, and is triggered when a U6-PMIP binding exists at
the AGW for an AT, and a new U1 PMIP or U6-PMIP registration request is accepted for that
AT.
AT
eBS1
eBS2
AGW
SRNC
VAAA
(Proxy)
HAAA
1. AT is in Idle state
2. U6-PMIP Binding
(Signaling Only)
3. AT Decides to
open a route
4. Route Open Request
5. IOS Signaling
(eBS2 receives session: GRE Key,
PMN-AN-HA1 Key and seq from
SRNC etc)
6. Route Open Accept (Link ID)
7. PMIP RRQ [Binding Type
Extension(RL+Primary)]
8. PMIP RRP (MN-HA Authentication)
9. U1 PMIP Binding (RL+Primary)
Figure 5
U6-PMIP Deregistration
The steps in Figure 5 are described below.
1.
AT is in the Idle state.
2.
A U6PMIP binding exists between the SRNC and AGW.
3.
The AT decides to open a route to eBS2.
8.3 PMIP Tunnel Operation with Multiple Binding
7
Error! No text of specified style in document.
Error! No text of specified style in document.
4.
The AT sends a Route Open Request to the eBS2.
5.
The eBS2 and SRNC exchange IOS signaling to establish a session for the AT.
6.
The eBS2 accepts the route open request and sends Link ID to AT.
7.
The eBS2 sends U1 PMIP RRQ with RL+Primary Binding Type extension to the
AGW.
8.
The AGW verifies MN-HA Auth extension. If authentication passes, the AGW sends
the successful PMIP RRP to the eBS2. Since PMIP RRP was successful, the AGW
autonomously revokes the U6-PMIP binding which existed in step 2.
9.
A U1 PMIP binding exists between AGW and eBS2.
Error! No text of specified style in document.
Error! No text of specified style in document.
8
8.3 PMIP Tunnel Operation with Multiple Binding