Packet Data Architecture Enhancement

1
Packet Data Architecture Enhancement

• Minneapolis PSAWG Working Session
• Frédéric ROSIN - 10/10/1116

2
Outline

• Reminder of the agreed architecture
• Enhancement
• Impact Analysis

3
Reminder of the agreed architecture

• Need for overlapping addressing space leads us to
  define APN
• An APN enables external data servers (FES) and
  mobiles (SU or MDP) to have their own IP
  addressing space.
• Addressing space of different APN can overlap
• IP endpoints of an APN can not communicate with
  IP endpoints of another APN

4
Mobile IP and APN
APN 2 Network
APN 1 Network
FES
FES
10.1.10.5
10.1.10.5
Home Agent
Home Agent
111.1.1.3 (ISSI)
111.1.1.2 (ISSI)
Home RFSS
ISSI
MIP Home Address 10.1.1.2
MIP Home Address 10.1.1.2
111.1.10.1 (ISSI)
Foreign Agent
Serving RFSS
SU A
SU B
10.1.1.2
10.1.1.2
5
Mobile IP and APN (Cont)

• Routing/Forwarding at the Home Agent
• When the Home Agent of a given APN gets a packet
  from its ISSI interface, it uses an IP routing
  table in order to determine that
• The destination IP address is MIP tunnel and
  forward
• The destination IP address is a FES forwarding
  to the APN physical interface
• The destination IP address is for an SU of
  another Home RFSS
• Tunnels to the destination SUs Home RFSS

6
Enhancement of the current architecture

• Enhancement is proposed to provide the following
  benefits
• Simplifying the Home agent configuration
• Use of widely used COTS for Home Agent
• Suggest to introduce a non-overlapping ISSI IP
  addressing scheme to enable endpoints of an APN
  to communicate accross a P25 network.
• SU/MDP/FES still use APN IP addressing scheme
• A second IP address of the non-overlapping ISSI
  IP addressing scheme is assigned to each endpoint
• IP within IP encapsulation is used between the
  SNDCP FNEs and gateways (RFG)

7
Use of the ISSI IP addressing FES ?? Mobile
FES
FES
10.1.10.5
10.1.10.5
10.1.1.2 (SU A) ?? 111.10.1.1 10.1.10.5(FES) ??
111.9.1.1
RFG
RFG
10.1.1.2 (SU B) ?? 111.11.1.1 10.1.10.5(FES) ??
111.9.1.2
Home Agent
Home RFSS
MIP Home Address 111.11.1.1
MIP Home Address 111.10.1.1
Local SU 10.1.1.2(SU A), APN 1??111.10.1.1 10.1.1
.2(SU B), APN 2??111.11.1.1 Forwarding
table 10.1.10.5(FES), APN 1 ??
111.9.1.1 10.1.10.5(FES), APN 2 ?? 111.9.1.2
Foreign Agent
Serving RFSS
SU A
SU B
10.1.1.2
10.1.1.2
8
Use of the ISSI IP addressing Mobile ?? Mobile
Home Agent
Home Agent
Home RFSS
Home RFSS
MIP Home Address 111.10.1.1
MIP Home Address 111.12.1.23
Foreign Agent
Foreign Agent
Serving RFSS
Serving RFSS
Local SU 10.1.1.23(SU C), APN 1??111.12.1.23 Forw
arding table 10.1.1.2(SU A), APN 1 ?? 111.10.1.1
Local SU 10.1.1.2(SU A), APN 1??111.10.1.1 Forwar
ding table 10.1.1.23(SU C), APN 1 ?? 111.12.1.23
SU A
SU C
10.1.1.2
10.1.1.23
9
Impact Analysis on the ISSI

• No change for the mobility management SAP
• Change for Packet Data SAP
• Upon SN Context registration, retrieval of both
  APN IP address and ISSI IP address from the SU
  profile
• APN IP address of the SU is sent out to the SU
• ISSI IP address of the SU is used by the serving
  RFSS to open the Mobile IP tunnel
• No specific SAP for Home-Home forwarding
  standard IP routing is used.
• ? We recommend this enhancement to simplify the
  IP network configuration and to allow the use of
  widely used COTS for the Home Agent function