Abstract:
A Packet Core Function (PCF) (55) and a method of automatic Packet Data Service Node (PDSN) Discovery, Monitoring, and Failure Handover in a packet-switched network that includes a plurality of PDSNs (57). The PDSNs multicast PDSN profile information that includes their ID, status, congestion level, and routing table information. The PCF automatically builds and updates a PDSN database (61) from the profile information it receives. If the PCF fails to receive a predefined number of multicast messages, or fails to receive responses to polling messages from a particular PDSN, the PCF concludes that the PDSN has failed. If a failure is detected, the PCF selects one or more new PDSNs to handle the packet data sessions that were being handled by the failed PDSN. The PCF then hands over the active sessions to the selected PDSN(s).
Abstract:
A Packet Core Function (PCF) (55) and a method of automatic Packet Data Service Node (PDSN) Discovery, Monitoring, and Failure Handover in a packet-switched network that includes a plurality of PDSNs (57). The PDSNs multicast PDSN profile information that includes their ID, status, congestion level, and routing table information. The PCF automatically builds and updates a PDSN database (61) from the profile information it receives. If the PCF fails to receive a predefined number of multicast messages, or fails to receive responses to polling messages from a particular PDSN, the PCF concludes that the PDSN has failed. If a failure is detected, the PCF selects one or more new PDSNs to handle the packet data sessions that were being handled by the failed PDSN. The PCF then hands over the active sessions to the selected PDSN(s).
Abstract:
Point-to-point protocol (PPP) negotiation in a wireless communication system between e.g. a mobile station (MS) and a packet data service node (PDSN). The MS sends to the PDSN a link control protocol option designated option X that identifies a user profile including at least one pre-negotiated PPP parameter. If the PDSN supports the user profile and the at least one parameter, it acknowledges this. In response, the MS acknowledges its acceptance. Then each node sets a state machine in accordance with the user profile. If the PDSN supports the user profile but not one or more of the at least one parameter, it sends a negative-acknowledgment identifying a second, acceptable user profile. If the PDSN does not support the user profile, it rejects the first user profile and a full PPP negotiation is performed without reference to any of the pre-stored user profiles.