What is Simple IP and Mobile IP?
The 1xEV-DO system supports packet data connections to a public or private data network using either mobile IP or simple IP protocol. Only a brief definitions for the simple IP and mobile IP protocols are provided here. For details, see
3GPP2 P.S0001-B Version 2.0
standard.
-
For simple IP protocol, moving from the coverage area of one PDSN to another PDSN constitutes a change in packet data session. A wireless device must obtain a new IP address (and lose existing connections) every time it changes its point of attachment (such as PDSN). A packet data session and a PPP session are concurrent in simple IP, that is, the existence of the packet data session is dependent upon a PPP session.
-
For mobile IP protocol, a packet data session can span several PDSNs as long as the user continuously maintains mobility bindings at the Home Agent (the IP address is persistent). A wireless device is allowed to maintain the same IP address as it moves across PDSNs and preserve existing packet data session during moves. The packet data session can exist through several changes of the PPP session. The mobile IP allows the PPP session to be terminated and re-established without the termination of the packet data session.
-
PPP session: A PPP session describes the time during which a particular PPP connection is maintained between the wireless device and the PDSN. The PPP session is maintained during periods when the wireless device is dormant. If a user hands off from one Radio Network (RN) to another RN but is still connected to the same PDSN, the PPP session remains. If a user changes PDSN, a new PPP session is created at the new PDSN.
-
Packet Data Session: Describes continuous use of packet data service by the user. A packet data session begins when the user invokes packet data service. A packet data session ends when the user or the network terminates packet data service. (A packet data service indicates any packet switched data service offered by the cdma2000 wireless network (for example, 1xEV-DO AN) to a user through the AT.
How Does Test Set Support Simple IP Packet Data Connection?
The
Session Application Type
can be set to
Default Packet Application
or
M-Flow Packet Application
or
Enhanced M-Flow Pkt
App before an access terminal (AT) initiates a packet data connection.
The test set supports packet data connection using simple IP protocol via it's internal PDSN simulation (see
Packet Data Network Emulation in the Test Set
). To use the test set's internal PDSN simulation, the
External PDSN State
must be set to
Off
(see
Data Channel Parameters
). In this case, the AT's PPP connection is terminated by the test set, propagating the encapsulated IP packets directly to the ethernet interface (LAN port).
An example procedure for packet data connection using simple IP is described in
Packet Data Service Example Procedure (via Simple IP)
.
How Does Test Set Support Mobile IP Packet Data Connection?
The test set provides two ways to support mobile IP protocol tests required to ensure compliance with the TIA/EIA-IS-835 standard. One way is by working together with an external PDSN (MOB-IP-SIM) provided by the Software Concepts, Inc. The other way is a simple way just to use Mobile IP Support in the test set.
Mobile IP Simulator
A typical connection diagram between the test set and the MOB-IP-SIM is shown in the figure below.
Test Set's Mobile IP Solution Setup
Both the simple IP and mobile IP protocols are implemented in the MOB-IP-SIM. For details on the MOB-IP-SIM functionality and configurations, see the MOB-IP-SIM technical manual available on the web:
http://www.softwareconceptsinc.net/mip-5850.php
If the external MOB-IP-SIM is providing PDSN simulation, the test set will forward the PPP octets delivered by RLP data to the external MOB-IP-SIM. The MOB-IP-SIM is responsible for actual termination of the PPP link and interpreting all protocol layers necessary to pass the end-to-end encapsulated IP packets directly onto the network (IP, UDP, MIP).
The
Session Application Type
can be set to
Default Packet Application
or
M-Flow Packet Application
or
Enhanced M-Flow Pkt App
before an AT initiates a packet data connection. To work with the External MOB-IP-SIM, the test set must be properly configured (see
Data Channel Parameters
). An example procedure for packet data connection using mobile IP is described in
Packet Data Service Example Procedure (via Mobile IP)
.
As the external MOB-IP-SIM only includes the logging of higher layer protocols (such as IP, UDP, MIP), it cannot display those messages of the lower protocols (for example, SLP, RLP, etc.). These air interface messages can be logged using the Wireless Protocol Adviser (WPA) (see
Protocol Logging
).
Mobile IP Support in Test Set
The test set also provides Mobile IP support without any external devices. Its work model can be described as follows. The test set processes the reverse Mobile IP related messages (MIP Agent Solicitation, MIP Registration Request) from Mobile Station and generate corresponding forward Mobile IP messages (MIP Agent Advertisement, MIP Registration Reply) to Mobile Station in order to pass the Mobile IP negotiation. After the Mobile IP negotiation, the DUT IP Address is assigned as Home Address to the DUT and the DUT use this IP address to do IP packet data transferring. For most of the Mobile IP related parameters in the forward Mobile IP messages, the test set uses either the fixed settings in the test set or the related parameter values gotten from the corresponding reverse Mobile IP messages.
Here the packet data service means DPA/MFPA/EMPA call.
When
External PDSN State
is
Off
,
Internal Mobile IP State
has effect. Switch the
Internal Mobile IP State
to
On
, the test set works in Mobile IP mode, in which
Home Agent Shared Secret (Hex)
must be consistent with the value configured in the DUT, otherwise, Mobile IP negotiation will fail. Switch the
Internal Mobile IP State
to Off, the test set works in Simple IP mode.
When
External PDSN State
is
On
,
Internal Mobile IP State
has no effect. In this case, the simulation of data network is provided by MOB-IP-SIM instead of the test set.
Compared with a DUT working with MOB-IP-SIM, the performance of data throughput between the test set and a DUT configured using Mobile IP can be greatly improved. This difference can be observable in Data Throughput Monitor measurement.