SYSTEM AND METHOD FOR ROUTING, MOBILITY, APPLICATION SERVICES, DISCOVERY, AND SENSING IN A VEHICULAR NETWORK ENVIRONMENT

• US 20150264554A1
• Filed: 03/20/2015
• Published: 09/17/2015
• Est. Priority Date: 01/14/2011
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Addepalli, Sateesh K., Sudhaakar, Raghuram S., Dai, Lillian Lei, Ermagan, Vina, Natarajan, Preethi, Lee, Kevin C., Monclus, Pere, Somers, Robert Edward
• Granted Patent: US 9,654,937 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B60R 16/023 for transmission of signals between vehicle parts or subsystems
• CPC Class Codes: B60W 50/10 Interpretation of driver requests or demands
• CPC Class Codes: G06F 21/45 Structures or tools for the administration of authentication
• CPC Class Codes: G06F 3/017 Gesture based interaction, e.g. based on a set of recognized hand gestures interaction based on gestures traced on a digitiser G06F3/04883
• CPC Class Codes: G06F 3/167 Audio in a user interface, e.g. using voice commands for navigating, audio feedback
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 1/008 where the control data relates to payload of a different packet
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: H04L 43/0858 One way delays
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 45/12 Shortest path evaluation
• CPC Class Codes: H04L 51/02 using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages
• CPC Class Codes: H04L 61/2592 using tunnelling or encapsulation
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04Q 9/00 Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
• CPC Class Codes: H04W 12/03 Protecting confidentiality, e.g. by encryption
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/06 : Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• CPC Class Codes: H04W 36/0009 : for a plurality of users or terminals, e.g. group communication or moving wireless networks user group management H04W4/08; processing of subscriber group data H04W8/186
• CPC Class Codes: H04W 36/08 : Reselecting an access point
• CPC Class Codes: H04W 4/00 : Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 4/10 : Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 4/40 : for vehicles, e.g. vehicle-to-pedestrians [V2P]
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/20 : based on geographic position or location
• CPC Class Codes: H04W 48/02 : Access restriction performed under specific conditions
• CPC Class Codes: H04W 48/06 : based on traffic conditions
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 52/0206 : in access points, e.g. base stations access point devices per se H04W88/08
• CPC Class Codes: H04W 52/0219 : where the power saving management affects multiple terminals
• CPC Class Codes: H04W 52/0264 : by selectively disabling software applications
• CPC Class Codes: H04W 52/12 : Outer and inner loops
• CPC Class Codes: H04W 52/143 : Downlink power control
• CPC Class Codes: H04W 52/225 : Calculation of statistics, e.g. average, variance
• CPC Class Codes: H04W 52/241 : taking into account channel quality metrics, e.g. SIR, SNR, CIR, Eb/lo
• CPC Class Codes: H04W 52/346 : distributing total power among users or channels
• CPC Class Codes: H04W 72/20 : Control channels or signalling for resource management
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/53 : based on regulatory allocation policies
• CPC Class Codes: H04W 76/45 : for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 8/06 : Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 8/08 : Mobility data transfer
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/02 : Data link layer protocols
• CPC Class Codes: H04W 84/005 : Moving wireless networks
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 92/18 : between terminal devices
• CPC Class Codes: Y02A 30/60 : Planning or developing urban green infrastructure
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

A method includes selecting a path for routing a data packet from a source node to a destination node in a vehicular ad hoc network, storing the data packet if the selected path is identified as a dead end, and establishing a communication link with a first node. The method also includes forwarding the data packet to the first node if a first distance between the first node and the destination node is less than a second distance between the source node and the destination node. More specific embodiments include sending a query for location information of the destination node, receiving the location information including two or more available paths from the source node to the destination node, and determining the path for routing the data packet is an optimal path of the two or more available paths.

Claims

1-31. -31. (canceled)

32. A method, comprising:

receiving, by a processor of a mobile access point, network traffic from an endpoint device;

inspecting the network traffic;

determining the endpoint device has a mobility scheme based on the inspecting;

inferring a type of mobility scheme on the endpoint device; and

adapting mobility services to accommodate the mobility scheme of the endpoint device.

33. The method of claim 32, further comprising:

reflecting mobility events to the endpoint device.

34. The method of claim 33, wherein the mobility events include at least one of forcing a new registration or changing a leased address.

35. The method of claim 32, wherein the inspecting includes detecting a destination port of the network traffic.

36. The method of claim 32, further comprising:

enabling the endpoint device to get a layer 3 (L3) address from a service provider if the service provider allows multiple dynamic host configuration protocol (DHCP) requests.

37. The method of claim 32, further comprising:

provisioning the endpoint device with a layer 3 (L3) address.

38. The method of claim 32, further comprising:

receiving other network traffic from a second endpoint device;

inspecting the other network traffic;

determining the second endpoint device does not have an available mobility scheme based on the inspecting the other network traffic; and

providing other mobility services to the second endpoint device.

39. The method of claim 38, further comprising:

hiding other mobility events from the second endpoint device.

40. At least one non-transitory computer readable media including code for execution that, when executed by at least one processor, is operable to perform operations comprising:

receiving network traffic from an endpoint device;

inspecting the network traffic;

determining the endpoint device has a mobility scheme based on the inspecting;

inferring a type of mobility scheme on the endpoint device; and

adapting mobility services to accommodate the mobility scheme of the endpoint device.

41. The at least one non-transitory computer readable media of claim 40, wherein the code for execution, when executed by the at least one processor, is operable to perform further operations comprising:

reflecting mobility events to the endpoint device.

42. The at least one non-transitory computer readable media of claim 40, wherein the inspecting includes detecting one or more protocol specific properties of the network traffic.

43. The at least one non-transitory computer readable media of claim 40, wherein the code for execution, when executed by the at least one processor, is operable to perform further operations comprising:

enabling the endpoint device to get a layer 3 (L3) address from a service provider if the service provider allows multiple dynamic host configuration protocol (DHCP) requests.

44. The at least one non-transitory computer readable media of claim 40, wherein the code for execution, when executed by the at least one processor, is operable to perform further operations comprising:

provisioning the endpoint device with a layer 3 (L3) address.

45. The at least one non-transitory computer readable media of claim 40, wherein the code for execution, when executed by the at least one processor, is operable to perform further operations comprising:

receiving other network traffic from a second endpoint device;

inspecting the other network traffic;

determining the second endpoint device does not have an available mobility scheme based on the inspecting the other network traffic; and

providing other mobility services to the second endpoint device.

46. The at least one non-transitory computer readable media of claim 45, wherein the code for execution, when executed by the at least one processor, is operable to perform further operations comprising:

hiding other mobility events from the second endpoint device.

47. An apparatus, comprising:

a mobility manager; and

at least one processor operable to execute instructions associated with the mobility manager to perform operations to;

receive network traffic from an endpoint device;

inspect the network traffic;

determine the endpoint device has a mobility scheme based on the inspecting;

infer a type of mobility scheme on the endpoint device; and

adapt mobility services to accommodate the mobility scheme of the endpoint device.

48. The apparatus of claim 47, wherein the at least one processor is operable to execute the instructions to perform further operations to:

reflect mobility events to the endpoint device.

49. The apparatus of claim 47, wherein the inspecting includes detecting a destination port of the network traffic.

50. The apparatus of claim 47, wherein the at least one processor is operable to execute the instructions to perform further operations to:

receive other network traffic from a second endpoint device;

inspect the other network traffic;

determine the second endpoint device does not have an available mobility scheme based on the inspecting the other network traffic; and

provide other mobility services to the second endpoint device.

51. A method, comprising:

receiving, in a source node, a data packet to be routed to a destination node in a vehicular network;

querying a location server in another network for location information associated with the destination node;

receiving the location information of the destination node including two or more available paths from the source node to the destination node;

selecting an optimal path from the two or more available paths;

establishing a communication link with a first node in the optimal path;

forwarding the data packet to the first node if a first distance between the first node and the destination node is less than a second distance between the source node and the destination node;

receiving in the source node a request for sensor data;

obtaining the sensor data;

generating a tag for the sensor data;

encapsulating the sensor data with the tag; and

sending the encapsulated sensor data to a data collector, wherein the obtaining, the generating, the encapsulating, and the sending occur in response to the request in real time.