Cisco ASR 5000 Series Administration Manual page 229

Mobile-IP and Proxy-MIP Timer Considerations
•
Use the following example to set absolute and idle timeout for the APN template in 3GPP network:
•
The following example can be used to set FA agent reg-lifetime in the FA service:
5. The system prepares the Agent advertisement. To select the value of the registration lifetime the system
compares the configured agent registration lifetime in the FA service to the idle and absolute timeouts that
were available in step (2). If the lifetime is lower, this value is used in the agent advertisement. If the idle
timeout or absolute timeout is lower, the system sends the registration lifetime as 5 seconds less than the
configured idle or absolute timeout. Note that if there is no idle or absolute timeout configured it defaults to
off, and the registration lifetime is always sent.
6. After the system sends the agent advertisement, the mobile sends a registration request. The requested lifetime in
the mobile request should be the lower of the values between the configured lifetime and the lifetime sent in
the agent advertisement.
7. When the FA receives the MIP RRQ, it authenticates the user. The values received in FA authentication
overwrite the values received during PDIF service authentication. This also includes timer values. If the AAA
returns a value for the subscriber idle timeout that is less than the lifetime in the MIP RRQ, sends a lifetime too
long error code (Code: 0x45, Requested Lifetime Too Long). The system sends back a lifetime value equal to
the configured subscriber idle timeout.
8. When the FA receives the MIP RRQ, it authenticates the user. The values received in FA authentication
overwrites the values received during PDIF service authentication. This includes timer values. If the AAA
returns a value for the subscriber idle timeout that is less than the lifetime in the MIP RRQ, sends a lifetime too
long error code (Code: 0x45, Requested Lifetime Too Long). The system sends back a lifetime value equal to
the configured subscriber idle timeout.
9. Assuming that the mobile can handle this error code, it should adjust the lifetime value to that sent by the system
and send a new RRQ.
The new RRQ is accepted by the FA and sent to the HA. The HA authenticates the user and compares the
requested lifetime to the configured MIP lifetime in the HA-service and the subscriber idle and absolute
timeouts. If the MIP lifetime is lower it is be sent back to the mobile; if the MIP lifetime is higher the system
OL-22944-02
Cisco ASR 5000 Series Gateway GPRS Support Node Administration Guide ▄
Call Flow Summary ▀