ROUTE PROTOCOL

• US 20080291868A1
• Filed: 04/21/2008
• Published: 11/27/2008
• Est. Priority Date: 04/25/2007
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Mazik, David R., Patwardhan, Ravindra, Sinnarajah, Ragulan, Agashe, Parag Arun, Ulupinar, Fatih, Prakash, Rajat
• Granted Patent: US 8,254,364 B2
• Time in Patent Office: Days
• US Class Current: 370/328
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 76/15 Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/18 Management of setup rejection or failure

Abstract

A route protocol is established whereby a mobile device can communicate to a multitude of (receiving) base stations though a tunnel created through a serving base station. A message that includes a Route Creation Header can be transmitted by the mobile device to create the tunnel. The Route Creation Header is reviewed by the receiving base station while the mobile device is in a Waiting-To-Open State. Various errors might occur with respect to the Route Creation Header. These errors can be conveyed to the mobile device by base station by setting one or more error code fields. Once the errors are resolved, another attempt to create a tunnel with base station can be made, if desired.

Claims

1. A method for creating a tunnel relationship between a mobile device and a base station, comprising:

selecting at least one base station for establishment of communication through a tunnel;

transmitting a message that includes a Route Creation Header to the at least one base station, the Route Creation Header comprises one or more parameters associated with defining the tunnel;

waiting for a confirmation of the Route Creation Header; and

transitioning out of a Waiting-To-Open state if the confirmation is received, wherein the confirmation indicates creation of the tunnel relationship.

2. The method of claim 1, further comprising:

re-transmitting the message that includes the Route Creation Header to the at least one base station if the confirmation is not received.

3. The method of claim 1, wherein the confirmation includes receiving a packet from the at least one base station.

4. The method of claim 1, wherein transmitting a message that includes a Route Creation Header to the at least one base station further comprises:

determining that two or more Packet Consolidation Protocol Packets will be carried in a single MAC packet, each Packet Consolidation Protocol Packet includes a Header Element record; and

omitting the Header Element record from all but one of the Packet Consolidation Packets, wherein omitting the Header Element records saves resources and improves efficiency.

5. The method of claim 1, wherein transmitting the message that includes the Route Creation Header to the at least one base station, further comprises:

selecting an identifier for the tunnel to the at least one base station; and

choosing a personality for the tunnel.

6. The method of claim 5, wherein the personality comprises one or more protocol types and one or more attribute values.

7. The method of claim 1, wherein transmitting the message that includes the Route Creation Header to the at least one base station, further comprises:

indicating whether an existing route should be deleted.

8. The method of claim 1, further comprising:

receiving a packet from the at least one base station, the packet includes a personality error code;

reviewing a list of ranked personalities received with the packet;

selecting a personality from the list of ranked personalities;

modifying the Route Creation Header Packet to include the selected personality; and

transmitting the modified Route Creation Header Packet to the at least one base station.

9. The method of claim 1, further comprising:

receiving a packet from the at least one base station, the packet includes a route already established error code and a route identification of the established route; and

deciding that the tunnel relationship is not needed.

10. The method of claim 1, further comprising:

receiving a packet from the at least one base station, the packet includes a session close error code and a CRCErrorDetectPattern; and

re-authenticating with a network that includes that at least one base station if the CRCErrorDetectPattern indicates the session close error code is not due to a link error.

11. The method of claim 1, further comprising:

including an access terminal identifier (ATI) in the Route Creation Header if the ATI has recently changed.

12. The method of claim 1, further comprising:

including a RouteID header in the message;

receiving a request for a current route map, if the RouteID header is not recognized by a serving base station; and

transmitting the current route map in response to the request.

13. A wireless communications apparatus, comprising:

a memory that retains instructions related to selecting at least one base station for establishment of communication through a tunnel, transmitting a message that includes a Route Creation Header to the at least one base station, waiting for a confirmation of the Route Creation Header, and transitioning out of a Waiting-To-Open state if the confirmation is received, wherein the Route Creation Header comprises one or more parameters associated with defining the tunnel; and

a processor, coupled to the memory, configured to execute the instructions retained in the memory.

14. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to re-transmitting the message that includes the Route Creation Header to the at least one base station if the confirmation is not received.

15. The wireless communications apparatus of claim 13, wherein the confirmation includes receiving a packet from the at least one base station.

16. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to determining that two or more Packet Consolidation Protocol Packets are to be carried in a single MAC packet, each Packet Consolidation Protocol Packet includes a Header Element record, and omitting the Header Element record from all but one of the Packet Consolidation Packets, wherein omitting the Header Element records saves resources and improves efficiency.

17. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to selecting an identifier for the tunnel to the at least one base station and choosing a personality for the tunnel.

18. The method of claim 17, wherein the personality comprises at least one protocol type and at least one attribute value.

19. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to indicating whether an existing route should be deleted.

20. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to receiving a packet from the at least one base station, the packet includes a personality error code, reviewing a list of ranked personalities received with the packet, selecting a personality from the list of ranked personalities, modifying the Route Creation Header Packet to include the selected personality, and transmitting the modified Route Creation Header Packet to the at least one base station.

21. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to receiving a packet from the at least one base station and deciding that the tunnel relationship is not needed, wherein the packet includes a route already established error code and a route identification of the established route.

22. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to receiving a packet from the at least one base station, wherein the packet includes a session close error code and a CRCErrorDetectPattern, and re-authenticating with a network that includes that at least one base station if the CRCErrorDetectPattern indicates the session close error code is not due to a link error.

23. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to including an access terminal identifier (ATI) in the Route Creation Header if the ATI has recently changed.

24. The wireless communications apparatus of claim 13, wherein the memory further retains instructions related to including a RouteID header in the message, receiving a request for a current route map, if the RouteID header is not recognized by a serving base station, and transmitting the current route map in response to the request.

25. A computer program product, comprising:

a computer-readable medium comprising;

a first set of codes for causing a computer to select at least one base station for establishment of communication through a tunnel;

a second set of codes for causing the computer to transmit a message that includes a Route Creation Header to the at least one base station, wherein the Route Creation Header comprises one or more parameters associated with defining the tunnel;

a third set of codes for causing the computer to wait for a confirmation of the Route Creation Header, wherein the confirmation includes receiving a packet from the at least one base station; and

a fourth set of codes for causing the computer to transition out of a Waiting-To-Open state if the confirmation is received.

26. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to re-transmit the message that includes the Route Creation Header to the at least one base station if the confirmation is not received.

27. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to determine that two or more Packet Consolidation Protocol Packets will be carried in a single MAC packet, each Packet Consolidation Protocol Packet includes a Header Element record; and

a sixth set of codes for causing the computer to omit the Header Element record from all but one of the Packet Consolidation Packets, wherein omitting the Header Element records saves resources and improves efficiency.

28. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to select an identifier for the tunnel to the at least one base station; and

a sixth set of codes for causing the computer to choose a personality for the tunnel, wherein the personality comprises one or more protocol types and one or more attribute values.

29. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to indicate whether an existing route should be deleted.

30. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to receive a packet from the at least one base station, the packet includes a personality error code;

a sixth set of codes for causing the computer to review a list of ranked personalities received with the packet.

a seventh set of codes for causing the computer to select a personality from the list of ranked personalities;

a eighth set of codes for causing the computer to modify the Route Creation Header Packet to include the selected personality; and

a ninth set of codes for causing the computer to transmit the modified Route Creation Header Packet to the at least one base station.

31. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to receive a packet from the at least one base station, the packet includes a route already established error code and a route identification of the established route; and

a sixth set of codes for causing the computer to decide that the tunnel relationship is not needed.

32. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to receive a packet from the at least one base station, the packet includes a session close error code and a CRCErrorDetectPattern; and

a sixth set of codes for causing the computer to re-authenticate with a network that includes that at least one base station if the CRCErrorDetectPattern indicates the session close error code is not due to a link error.

33. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to include an access terminal identifier (ATI) in the Route Creation Header if the ATI has recently changed.

34. The computer program product of claim 25, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to include a RouteID header in the message;

a sixth set of codes for causing the computer to receive a request for a current route map, if the RouteID header is not recognized by a serving base station; and

a seventh set of codes for causing the computer to transmit the current route map in response to the request.

35. An apparatus, comprising:

means for selecting at least one base station for establishment of communication through a tunnel;

means for transmitting a message that includes a Route Creation Header to the at least one base station, wherein the Route Creation Header comprises one or more parameters associated with defining the tunnel;

means for waiting for a confirmation of the Route Creation Header, wherein the confirmation includes receiving a packet from the at least one base station, the means for transmitting the message re-transmits the message that includes the Route Creation Header to the at least one base station until the confirmation is received; and

means for transitioning out of a Waiting-To-Open state when the confirmation is received.

36. The apparatus of claim 35, further comprising:

means for determining that two or more Packet Consolidation Protocol Packets will be carried in a single MAC packet, each Packet Consolidation Protocol Packet includes a Header Element record; and

means for omitting the Header Element record from all but one of the Packet Consolidation Packets.

37. The apparatus of claim 35, further comprising:

means for receiving a packet from the at least one base station, the packet includes a personality error code;

means for reviewing a list of ranked personalities received with the packet;

means for selecting a personality from the list of ranked personalities;

means for modifying the Route Creation Header Packet to include the selected personality; and

means for transmitting the modified Route Creation Header Packet to the at least one base station.

38. The apparatus of claim 35, further comprising:

means for receiving a packet from the at least one base station, the packet includes a route already established error code and a route identification of the established route; and

means for deciding that the tunnel relationship is not needed.

39. The apparatus of claim 35, further comprising:

means for receiving a packet from the at least one base station, the packet includes a session close error code and a CRCErrorDetectPattern; and

means for re-authenticating with a network that includes that at least one base station if the CRCErrorDetectPattern indicates the session close error code is not due to a link error.

40. At least one processor for route protocol, comprising:

a first module operable to choose at least one base station for establishment of communication through a tunnel;

a second module operable to transmit a message that includes a Route Creation Header to the at least one base station, wherein the Route Creation Header comprises one or more parameters associated with defining the tunnel;

a third module operable to wait for a confirmation of the Route Creation Header, wherein the confirmation includes receiving a packet from the at least one base station;

a fourth module operable to re-transmit the message that includes the Route Creation Header to the at least one base station until the confirmation is received; and

a fifth module operable to transition out of a Waiting-To-Open state when the confirmation is received.

41. The at least one processor of claim 40, further comprising:

a sixth module operable to determine that two or more Packet Consolidation Protocol Packets should be carried in a single MAC packet, each Packet Consolidation Protocol Packet includes a Header Element record; and

a seventh module operable to omit the Header Element record from all but one of the Packet Consolidation Packets.

42. The at least one processor of claim 40, further comprising:

a sixth module operable to receive a packet from the at least one base station, the packet includes a personality error code;

a seventh module operable to review a list of ranked personalities received with the packet;

an eighth module operable to select a personality from the list of ranked personalities;

a ninth module operable to modify the Route Creation Header Packet to include the selected personality; and

a ninth module operable to transmit the modified Route Creation Header Packet to the at least one base station.

43. The at least one processor of claim 40, further comprising:

a sixth module operable to receive a packet from the at least one base station, the packet includes a route already established error code and a route identification of the established route; and

a seventh module operable to decide that the tunnel relationship is not needed.

44. The at least one processor of claim 40, further comprising:

a sixth module operable to receive a packet from the at least one base station, the packet includes a session close error code and a CRCErrorDetectPattern; and

a seventh module operable to re-authenticate with a network that includes that at least one base station if the CRCErrorDetectPattern indicates the session close error code is not due to a link error.

45. A method for creating a tunnel relationship between a mobile device and a base station, comprising:

receiving a message that includes a Route Creation Header from a mobile device, wherein the Route Creation Header comprises one or more parameters associated with defining a tunnel;

determining if the mobile device is in a Waiting-To-Open state;

reviewing the Route Creation Header for at least one error, if the device is in the Waiting-To-Open state;

creating a Route Protocol Message in response to the received message; and

transmitting the created Route Protocol Message to the mobile device.

46. The method of claim 45, further comprising:

ignoring the Route Creation Header from a mobile device if the device is not in the Waiting-To-Open state and the Route Creation Header does not include a delete all routes flag.

47. The method of claim 45, wherein reviewing the Route Creation Header for at least one error further comprises:

determining that a personality requested in the received Route Creation Header is not supported, the personality comprises one or more protocol types and one or more attribute values;

wherein determining that the personality requested is not supported includes accessing a Session Reference Network Controller to determine an interpretation of personality identifiers received in the Route Creation Header;

ranking the supported personalities in an order of preference; and

including the ranked supported personalities in the Route Protocol Message.

48. The method of claim 45, wherein reviewing the Route Creation Header for at least one error, further comprises:

determining if a route is already established with the mobile device; and

including a route identification of an established route in the Route Protocol Message if it is determined that a route is already established.

49. The method of claim 45, wherein reviewing the Route Creation Header for at least one error, further comprises:

receiving instructions that a session with the mobile device should be closed, wherein the instructions are received from a Session Reference Network Controller; and

including a CRCErrorDetectPattern in the Route Protocol Message.

50. The method of claim 45, wherein reviewing the Route Creation Header for at least one error, further comprises:

determining that a route has not been established with the mobile device based on a receiving a packet that does not include the Route Creation Header and no route exists; and

including an error code in the created Route Protocol Message that indicates the route does not exist, if it is determined that the route has not been established.

51. The method of claim 45, wherein reviewing the Route Creation Header for at least one error, further comprises:

determining there is a failure in the identification of the mobile device; and

including an error code in the Route Protocol Message to indicate the mobile device identification failure.

52. The method of claim 51, wherein the identification failure is received from a Session Reference Network Controller.

53. The method of claim 45, further comprising:

receiving a RouteID header in the message; and

transmitting a request for a current route map, if the RouteID header is not recognized.

54. A wireless communications apparatus, comprising:

a memory that retains instructions for receiving a message that includes a Route Creation Header from a mobile device, wherein the Route Creation Header comprises one or more parameters associated with defining a tunnel, determining if the mobile device is in a Waiting-To-Open state, reviewing the Route Creation Header for at least one error if the device is in the Waiting-To-Open state, creating a Route Protocol Message in response to the received message, and transmitting the created Route Protocol Message to the mobile device; and

a processor, coupled to the memory, configured to execute the instructions retained in the memory.

55. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to ignoring the Route Creation Header from a mobile device if the device is not in the Waiting-To-Open state and the Route Creation Header does not include a delete all routes flag.

56. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to determining if a personality requested in the received Route Creation Header is not supported, accessing a Session Reference Network Controller to determine an interpretation of personality identifiers received in the Route Creation Header, ranking the supported personalities in an order of preference, and including the ranked supported personalities in the Route Protocol Message, wherein the personality comprises one or more protocol types and one or more attribute values.

57. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to determining if a route is already established with the mobile device and including a route identification of an established route in the Route Protocol Message, if it is determined that a route is already established.

58. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to receiving instructions from a Session Reference Network Controller that a session with the mobile device should be closed and including a CRCErrorDetectPattern in the Route Protocol Message.

59. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to determining that a route has not been established with the mobile device based on a receiving a packet that does not include the Route Creation Header and no route exists and including an error code in the created Route Protocol Message that indicates the route does not exist, if it is determined that the route has not been established.

60. The wireless communications apparatus of claim 54, wherein the memory further retains instructions relating to determining there is a failure in the identification of the mobile device and including an error code in the Route Protocol Message to indicate the mobile device identification failure.

61. The wireless communications apparatus of claim 60, wherein the identification failure is received from a Session Reference Network Controller.

62. The wireless communications apparatus of claim 54, wherein the memory further retains instructions related to receiving a RouteID header in the message and transmitting a request for a current route map, if the RouteID header is not recognized.

63. A computer program product, comprising:

a computer-readable medium comprising;

a first set of codes for causing a computer to receive a message that includes a Route Creation Header from a mobile device, wherein the Route Creation Header comprises one or more parameters associated with defining a tunnel;

a second set of codes for causing the computer to determine if the mobile device is in a Waiting-To-Open state;

a third set of codes for causing the computer to review the Route Creation Header for at least one error if the device is in the Waiting-To-Open state;

a fourth set of codes for causing the computer to create a Route Protocol Message in response to the received message; and

a fifth set of codes for causing the computer to transmit the created Route Protocol Message to the mobile device.

64. The computer program product of claim 63, the computer-readable medium further comprising:

a sixth set of codes for causing the computer to ignore the Route Creation Header from a mobile device if the device is not in the Waiting-To-Open state and the Route Creation Header does not include a delete all routes flag.

65. The computer program product of claim 63, the computer-readable medium further comprising:

a sixth set of codes for causing the computer to determine if a personality requested in the received Route Creation Header is not supported, wherein the personality comprises at least one protocol type and at least one attribute value;

a seventh set of codes for causing the computer to access a Session Reference Network Controller to determine an interpretation of personality identifiers received in the Route Creation Header;

a eighth set of codes for causing the computer to rank the supported personalities in an order of preference; and

a ninth set of codes for causing the computer to include the ranked supported personalities in the Route Protocol Message.

66. The computer program product of claim 63, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to determine if a route is already established with the mobile device; and

a sixth set of codes for causing the computer to include a route identification of an established route in the Route Protocol Message, if it is determined that a route is already established.

67. The computer program product of claim 63, the computer-readable medium further comprising

a fifth set of codes for causing the computer to receive instructions from a Session Reference Network Controller that a session with the mobile device should be closed;

and

a sixth set of codes for causing the computer to include a CRCErrorDetectPattern in the Route Protocol Message.

68. The computer program product of claim 63, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to determine that a route has not been established with the mobile device based on a receiving a packet that does not include the Route Creation Header and no route exists; and

a sixth set of codes for causing the computer to include an error code in the created Route Protocol Message that indicates the route does not exist, if it is determined that the route has not been established.

69. The computer program product of claim 63, the computer-readable medium further comprising:

a fifth set of codes for causing the computer to determine there is a failure in the identification of the mobile device; and

a sixth set of codes for causing the computer to include an error code in the Route Protocol Message to indicate the mobile device identification failure.

70. The computer program product of claim 69, wherein the identification failure is received from a Session Reference Network Controller.

71. The computer program product of claim 63, the computer-readable medium further comprising

a fifth set of codes for receiving a RouteID header in the message;

and

a sixth set of code for transmitting a request for a current route map, if the RouteID header is not recognized.

72. An apparatus, comprising:

means for receiving a message that includes a Route Creation Header from a mobile device, wherein the Route Creation Header comprises one or more parameters associated with defining a tunnel;

means for determining if the mobile device is in a Waiting-To-Open state;

means for reviewing the Route Creation Header for at least one error, if the device is in the Waiting-To-Open state;

means for creating a Route Protocol Message in response to the received message; and

means for transmitting the created Route Protocol Message to the mobile device.

73. The apparatus of claim 72, further comprising:

means for ignoring the Route Creation Header from a mobile device if the mobile device is not in the Waiting-To-Open state and the Route Creation Header does not include a delete all routes flag.

74. The apparatus of claim 72, further comprising

means for determining if a personality requested in the received Route Creation Header is not supported;

means for accessing a Session Reference Network Controller to determine an interpretation of personality identifiers received in the Route Creation Header;

means for ranking the supported personalities in an order of preference; and

means for including the ranked supported personalities in the Route Protocol Message.

75. At least one processor for route protocol, comprising:

a first module operable to receive a message that includes a Route Creation Header from a mobile device, wherein the Route Creation Header comprises one or more parameters associated with defining a tunnel;

a second module operable to determine if the mobile device is in a Waiting-To-Open state;

a third module operable to review the Route Creation Header for at least one error, if the device is in the Waiting-To-Open state, wherein the Route Creation Header is ignored if the device is not in the Waiting-To-Open state;

a fourth module operable to create a Route Protocol Message in response to the received message; and

a fifth module operable to transmit the created Route Protocol Message to the mobile device.

76. The at least one processor of claim 75, wherein the at least one error is one of a supported personality error, a route already established error, a session close error, a route has not been established error, an error in the identification of the mobile device, or combinations thereof.