Method and apparatus to resynchronize ppp on um interface without affecting ppp on a rm interface and to resynchronize ppp on a rm interface without affecting ppp on a um interface
Abstract
A method, within a wireless communication system, and a wireless MT2 device which provide for the resynchronization of a PPP link on each one of a U m and R m interface without affecting the other of the U m and R m interface. When a handoff is performed, such that the communications of the mobile MT2 device is handed off to a new BS/MSC, the U m interface will undergo PPP configuration renegotiation without causing the R m interface also to undergo PPP configuration renegotiation. Similarly, when the R m interface undergoes PPP configuration renegotiation, the U m interface will not undergo PPP configuration renegotiation.
Claims
exact text as granted — not AI-modifiedWe claim as our invention:
1. A method of resynchronizing a first Point-to-Point Protocol link on a U m interface without resynchronizing a second Point-to-Point Protocol link on a R m interface, comprising:
checking all packets being received by a MT 2 device over said U m interface to determine whether a received packet is a PPP packet for requesting option negotiating;
negotiating option values of said U m interface, after said checking determines that said received packet is said PPP packet for requesting option negotiating.
2. The method according to claim 1 , wherein a Point-to-Point Protocol on said MT 2 device enters a state for data transfer after said negotiating of said option values is successfully completed.
3. The method according to claim 2 , wherein said checking is performed when said Point-to-Point Protocol is in said state for data transfer.
4. The method according to claim 1 , wherein said negotiating comprises negotiating LCP option values.
5. The method according to claim 1 , wherein said negotiating comprises negotiating IPCP option values.
6. The method according to claim 1 , wherein said negotiating comprises negotiating LCP option values and IPCP option values.
7. A method of resynchronizing a first Point-to-Point Protocol link without resynchronizing a second Point-to-Point Protocol link, comprising:
checking all packets being received by a MT 2 device over one of a U m interface and a R m interface to determine whether a received packet is a PPP packet for requesting option negotiating;
negotiating option values of said one of said U m interface and said R m interface, after said checking determines that said received packet is said PPP packet for requesting option negotiating.
8. The method according to claim 7 , wherein a Point-to-Point Protocol on said MT 2 device enters a state for data transfer after said negotiating of said option values is successfully completed.
9. The method according to claim 8 , wherein said checking is performed when said Point-to-Point Protocol is in said state for data transfer.
10. The method according to claim 7 , wherein said negotiating comprises negotiating LCP option values.
11. The method according to claim 7 , wherein said negotiating comprises negotiating IPCP option values.
12. The method according to claim 7 , wherein said negotiating comprises negotiating LCP option values and IPCP option values.
13. A MT 2 device capable of resynchronizing a first Point-to-Point Protocol link on a U m interface without resynchronizing a second Point-to-Point Protocol link on a R m interface, comprising:
means for checking all packets being received over said U m interface to determine whether a received packet is a PPP packet for requesting option negotiation;
means for negotiating option values of said U m interface, after said checking means determines that said received packet is said PPP packet for requesting option negotiation.
14. The MT 2 device according to claim 13 , wherein a Point-to-Point Protocol on said MT 2 device enters a state for data transfer after said negotiating means successfully negotiates said PPP options.
15. The MT 2 device according to claim 14 , wherein said checking means performs checking of all of said packets when said Point-to-Point Protocol is in said state for data transfer.
16. The MT 2 device according to claim 13 , wherein said option values negotiated by said negotiating means comprises LCP option values.
17. The MT 2 device according to claim 13 , wherein said option values negotiated by said negotiating means comprises IPCP option values.
18. The MT 2 device according to claim 13 , wherein said option values negotiated by said negotiating means comprises LCP option values and IPCP option values.
19. A MT 2 device capable of resynchronizing a first Point-to-Point Protocol link without resynchronizing a second Point-to-Point Protocol link, comprising:
means for checking all packets being received by a MT 2 device over one of a U m interface and a R m interface to determine whether a received packet is a PPP packet for requesting option negotiating;
means for negotiating option values of said one of said U m interface and said R m interface, after said checking means determines that said received packet is said PPP packet for requesting option negotiating.
20. The MT 2 device according to claim 19 , wherein a Point-to-Point Protocol on said MT 2 device enters a state for data transfer after said negotiating means successfully negotiates PPP options.
21. The MT 2 device according to claim 20 , wherein said checking means performs checking when said Point-to-Point Protocol is in said state for data transfer.
22. The MT 2 device according to claim 19 , wherein said option values negotiated by said negotiating means comprises LCP option values.
23. The MT 2 device according to claim 19 , wherein said option values negotiated by said negotiating means comprises IPCP option values.
24. The MT 2 device according to claim 19 , said option values negotiated by said negotiating means comprises LCP option values and IPCP option values.Join the waitlist — get patent alerts
Track US6377556B1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.