NAMED-DATA NETWORKS FOR VEHICLE-TO-INFRASTRUCTURE COMMUNICATION

• US 20200137191A1
• Filed: 10/26/2018
• Published: 04/30/2020
• Est. Priority Date: 10/26/2018
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: Neishaboori, Azin
• Granted Patent: US 11,159,644 B2
• Time in Patent Office: Days
• 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/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04W 4/06 Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
• CPC Class Codes: H04W 4/44 for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
• CPC Class Codes: H04W 4/46 for vehicle-to-vehicle communication [V2V]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 72/12 Wireless traffic scheduling
• CPC Class Codes: H04W 72/30 Resource management for broadcast services

Abstract

Method and apparatus are disclosed for named-data networks for vehicle-to-infrastructure communication. An example roadside unit includes roadside unit for vehicle-to-infrastructure communication via a named-data network includes a transceiver configured to broadcast an RSU interest packet based on a broadcast schedule and receive a vehicle data packet of a vehicle that corresponds with the RSU interest packet. The example roadside unit also includes a controller configured to dynamically adjust the broadcast schedule based on the vehicle data packet.

Claims

1. A vehicle-to-infrastructure (V2I) system utilizing a named-data network, the system comprising:

a vehicle configured for V2I communication; and

a roadside unit configured for the V2I communication, wherein, to communicate, the roadside unit is configured to;

broadcast an RSU interest packet based on a broadcast schedule;

receive a vehicle data packet of the vehicle that corresponds with the RSU interest packet; and

dynamically adjust the broadcast schedule based on the vehicle data packet.

2. The system of claim 1, wherein the vehicle is configured to broadcast the vehicle data packet responsive to:

receiving the RSU interest packet; and

identifying data stored in memory of the vehicle that corresponds with the RSU interest packet.

3. The system of claim 1, wherein the roadside unit is configured to receive a vehicle interest packet of the vehicle.

4. The system of claim 3, wherein the vehicle interest packet broadcasted by the vehicle corresponds with a subject-of-interest of the vehicle.

5. The system of claim 3, wherein the roadside unit is configured to dynamically adjust the broadcast schedule further based on the vehicle interest packet.

6. A method for vehicle-to-infrastructure communication via a named-data network, the method comprising:

broadcasting, via a transceiver of a roadside unit, an RSU interest packet based on a broadcast schedule; and

receiving, via the transceiver, a vehicle data packet of a vehicle that corresponds with the RSU interest packet; and

dynamically adjusting, via a processor of the roadside unit, the broadcast schedule based on the vehicle data packet.

7. The method of claim 6, wherein dynamically adjusting the broadcast schedule based on the vehicle data packet includes adjusting how often the RSU interest packet is broadcasted upon identifying a change in demand for information corresponding with the RSU interest packet.

8. The method of claim 6, further including a manifest in the RSU interest packet, the manifest identifies topics of information that the roadside unit is storing to facilitate the vehicle in identifying a vehicle interest packet to broadcast.

9. A roadside unit for vehicle-to-infrastructure communication via a named-data network, the roadside unit comprising:

a transceiver configured to;

broadcast an RSU interest packet based on a broadcast schedule; and

receive a vehicle data packet of a vehicle that corresponds with the RSU interest packet; and

a controller configured to dynamically adjust the broadcast schedule based on the vehicle data packet.

10. The roadside unit of claim 9, wherein the transceiver is configured to receive a vehicle interest packet of the vehicle.

11. The roadside unit of claim 10, wherein, upon the transceiver receiving the vehicle interest packet:

the controller is to identify data is stored in memory of the roadside unit that corresponds with the vehicle interest packet; and

the transceiver is to broadcast a corresponding RSU data packet responsive to the controller identifying the data.

12. The roadside unit of claim 10, wherein the controller is configured to dynamically adjust the broadcast schedule further based on the vehicle interest packet.

13. The roadside unit of claim 10, wherein the controller is configured to process the RSU interest packet and the vehicle interest packet in parallel.

14. The roadside unit of claim 9, wherein the roadside unit is coupled to infrastructure.

15. The roadside unit of claim 9, wherein, based on the broadcast schedule, the transceiver is to broadcast interest packets at a predefined interval.

16. The roadside unit of claim 9, wherein the controller is configured to cache the vehicle data packet responsive to receiving the vehicle data packet.

17. The roadside unit of claim 9, wherein the RSU interest packet and the vehicle data packet relate to at least one of vehicle software updates and map updates.

18. The roadside unit of claim 9, wherein the controller includes:

a wait state during which the controller waits to receive at least one of the vehicle data packet and a vehicle interest packet;

a send-interest state during which the controller broadcasts the RSU interest packet via the transceiver;

a search-for-data state during which the controller searches for data stored in memory that corresponds with the vehicle interest packet; and

a send-data state during which the controller broadcasts an RSU data packet via the transceiver.

19. The roadside unit of claim 9, wherein, to adjust the broadcast schedule, the controller is configured to adjust how often the RSU interest packet is to be broadcasted responsive to identifying a change in demand for information corresponding with the RSU interest packet.

20. The roadside unit of claim 9, wherein the controller includes a manifest in the RSU interest packet, the manifest identifies topics of information stored in memory of the roadside unit to facilitate the vehicle in identifying a vehicle interest packet to broadcast.