EP2798863B1 - Wireless networks for sharing road information - Google Patents
Wireless networks for sharing road information Download PDFInfo
- Publication number
- EP2798863B1 EP2798863B1 EP11878801.7A EP11878801A EP2798863B1 EP 2798863 B1 EP2798863 B1 EP 2798863B1 EP 11878801 A EP11878801 A EP 11878801A EP 2798863 B1 EP2798863 B1 EP 2798863B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- vehicles
- road
- node
- wireless network
- road information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 description 23
- 230000005540 biological transmission Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 239000004065 semiconductor Substances 0.000 description 4
- 238000001514 detection method Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010338 mechanical breakdown Methods 0.000 description 1
- 239000003305 oil spill Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G01—MEASURING; TESTING
- G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
- G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
- G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
- G01C21/34—Route searching; Route guidance
- G01C21/3453—Special cost functions, i.e. other than distance or default speed limit of road segments
- G01C21/3492—Special cost functions, i.e. other than distance or default speed limit of road segments employing speed data or traffic data, e.g. real-time or historical
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096708—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control
- G08G1/096716—Systems involving transmission of highway information, e.g. weather, speed limits where the received information might be used to generate an automatic action on the vehicle control where the received information does not generate an automatic action on the vehicle control
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096733—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place
- G08G1/096741—Systems involving transmission of highway information, e.g. weather, speed limits where a selection of the information might take place where the source of the transmitted information selects which information to transmit to each vehicle
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0967—Systems involving transmission of highway information, e.g. weather, speed limits
- G08G1/096766—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission
- G08G1/096791—Systems involving transmission of highway information, e.g. weather, speed limits where the system is characterised by the origin of the information transmission where the origin of the information is another vehicle
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/09—Arrangements for giving variable traffic instructions
- G08G1/0962—Arrangements for giving variable traffic instructions having an indicator mounted inside the vehicle, e.g. giving voice messages
- G08G1/0968—Systems involving transmission of navigation instructions to the vehicle
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G1/00—Traffic control systems for road vehicles
- G08G1/16—Anti-collision systems
- G08G1/161—Decentralised systems, e.g. inter-vehicle communication
- G08G1/162—Decentralised systems, e.g. inter-vehicle communication event-triggered
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/025—Services making use of location information using location based information parameters
- H04W4/027—Services making use of location information using location based information parameters using movement velocity, acceleration information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- This relates generally to wireless networks for mobile devices.
- a mobile device can use a wireless communication technology to establish a network connection to another mobile device.
- the wireless network connection enables the mobile devices to communicate with each other.
- US2010194592 discloses a method and an apparatus for broadcasting information related to a vehicular environment using an broadcast network of nodes including a source node and a plurality of relay nodes.
- US2005002347 discloses a traffic information service apparatus using an ad-hoc network and a method for controlling the same.
- US2005201316 discloses a wireless network system which relays a broadcast signal in multi-ple stages and distributes data to terminals there around. The present invention provides a method, a computer readable medium and a device according respectively to claim 1, claim 6 and claim 11.
- a temporary network may be established between vehicles (“nodes") using wireless connections. Such temporary networks established between nodes may be referred to as “ad hoc wireless networks.”
- an ad hoc wireless network may be used for sending and receiving information about road conditions. Such road information may include an average speed for a particular portion of road, a location and configuration of a road obstruction (e.g., a disabled vehicle), images of an accident scene, a traffic flow plan to route vehicles around a road obstruction, etc. In this manner, vehicles may avoid or reduce delays due to road congestion or obstruction.
- the ad hoc wireless network may enable emergency response vehicles to assess an accident before arriving at the accident scene.
- Emergency response personnel may also use the ad hoc wireless network to send instructions to vehicles at or near the accident scene. In this manner, embodiments may enable faster and more effective responses to accidents.
- an ad hoc wireless network 10 may include any number of nodes 160 (e.g., nodes 160A, 160B) connected by a wireless connection 165.
- the nodes 160 may be any vehicles including wireless communications interfaces.
- a node 160 may be an automobile including a built-in computer and transceiver, a truck including a portable communication device (e.g., a cellular telephone, a laptop computer or a handheld computer), etc.
- each node 160 may include a transceiver 152, a processor 154, a memory device 156, a road information module 158, and sensor(s) 159. Further, each node 160 may have a transmission range, meaning a physical distance over which the included transceiver 152 can effectively send or receive radio transmissions to another device. Generally, a node 160 may establish a wireless connection 165 to another node 160 if the two nodes 160 are within each other's transmission ranges.
- first and second nodes may instead connect to each other through one or more intervening nodes (not shown).
- the intervening nodes may each act as a relay station or repeater, thus enabling the first node to connect to the second node indirectly.
- the wireless connections 165 may be based on any radio communications technologies and/or standards.
- the wireless connection 165 may be a Wi-Fi connection conforming to the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard, IEEE 802.11-2007, published June 12, 2007.
- the road information module 158 may include functionality to discover other nodes 160 with which to establish an ad hoc wireless network. Such functionality may include broadcasting a beacon to invite other nodes 160 to join or establish an ad hoc wireless network. In addition, such functionality may include accepting a beacon received from another node 160.
- the road information module 158 may also include functionality to determine whether to establish an ad hoc wireless network (or join an existing network) based on an estimated time duration of a wireless connection (i.e., how long the node 160 is expected to maintain the wireless connection 165 to the other node(s) 160).
- the time duration may be estimated by determining the amount of time that will elapse before one node 160 physically moves out of the transmission range of the other node 160. This determination may involve predicting the future movements of each node based on the current speed, direction, planned path, and/or destination location of each node 160.
- the predicted movements may then be used to estimate a point in time (if any) when at least one node 160 moves out of the transmission range of another node 160.
- the ad hoc wireless network may be established (or is joined) if the estimated time duration exceeds some predefined minimum time of connection (e.g., ten minutes, one hour, etc.).
- the road information module 158 may interact with the sensor(s) 159.
- the sensor(s) 159 may be any device to collect information about the node 160 or its surroundings.
- the information about the node 160 may include the speed, direction, destination, and planned path of the node 160.
- the sensor(s) 159 may include a Global Positioning System (GPS) device, an onboard trip computer, a speedometer, a compass, etc.
- GPS Global Positioning System
- the information about the node 160 may also include a transmission range and signal strength for the node 160.
- the sensor(s) 159 may also include a radio signal analysis device, a network bandwidth analysis device, etc.
- the information about the surroundings of node 160 may include information about the physical configuration of the space around the node 160.
- Such spatial information may include the number and layout of lanes of the road, the positions and/or speeds of any neighboring vehicles, the position and geometry of a road obstruction (e.g., a fallen tree, a vehicle accident, a construction site), etc.
- the senor(s) 159 may also include a camera to capture images of the surroundings (e.g., video camera, still camera, stereoscopic camera), a light-based object-detection system (e.g., a laser, infrared, or ultraviolet emitter and/or detector), a radio-based object-detection system (e.g., active and/or passive radar), a sound-based object-detection system (e.g., active and/or passive sonar), etc.
- a camera to capture images of the surroundings e.g., video camera, still camera, stereoscopic camera
- a light-based object-detection system e.g., a laser, infrared, or ultraviolet emitter and/or detector
- a radio-based object-detection system e.g., active and/or passive radar
- a sound-based object-detection system e.g., active and/or passive sonar
- the information about the surroundings of node 160 may relate to the road surface and/or traction characteristics.
- the sensor(s) 159 may include a tire traction sensor, a road ice sensor, etc. Further, it is contemplated that the sensor(s) 159 may be any other device or combination of devices configured to capture any other information about the node 160 or its surroundings.
- the road information module 158 may include functionality to analyze and/or summarize information derived from the sensor(s) 159. For example, the road information module 158 may use information about vehicle speed and road configuration to determine that a particular lane is obstructed at a specific location. The road information module 158 may also include functionality to present the information and/or an analysis thereof to a user of the node 160. For example, the road information module 158 may interact with a display device or user interface (not shown) to present a summary of the information to a user. Further, in one or more embodiments, the road information module 158 may include functionality to send such information and/or an analysis thereof to other nodes 160 using the ad hoc wireless network.
- the road information module 158 of a first node 160A may include functionality to receive inbound road information from a second node 160B, and to present the received inbound road information to a user of the first node 160A.
- the road information module 158 may also include functionality to determine an alternate route based on road condition information received from another node, and to present the alternate route to a user of the receiving node (e.g., a driver of a vehicle).
- the road information module 158 of node 160A may receive information from node 160B via the transceiver 152, and may then interact with a display device or user interface (not shown) to present the information to a user of node 160A.
- the road information module 158 of a node 160 may include functionality to send information about an accident to an emergency response vehicle using an ad hoc wireless network. For example, in the event of an accident, an emergency response vehicle may be travelling to the scene of the accident. In such a situation, receiving information about the accident from a node may enable personnel of the emergency response vehicle to assess the accident and to prepare before arriving at the accident scene.
- the road information module 158 of a node 160 may also include functionality to receive instructions from the emergency response vehicle, and to present the received instructions to a user of the node 160. For example, the road information module 158 of node 160 may receive instructions from the emergency response vehicle via the transceiver 152, and may then interact with a display device or user interface (not shown) to present the instructions to a user of node 160A.
- the road information module 158 of a node 160 may include functionality to determine a traffic flow plan, and to present the traffic flow plan to a user of the node 160.
- the traffic flow plan may specify how vehicles are to move around an obstruction in a road.
- the road information module 158 may automatically determine a traffic flow plan based on predefined algorithms to improve flow through a bottleneck (e.g., merging one vehicle at a time, merging groups of a specified size, merging each lane for a specified period of time, etc.).
- the traffic flow plan may be determined by a single node 160 (e.g., by the first node 160 to detect the obstruction, by a randomly chosen node 160, etc.), or may be determined cooperatively among multiple nodes 160 (e.g., by automatic voting of each node 160, by user-specified voting in a user interface, etc.).
- the road information module 158 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device.
- nodes 230, 240, 250, 260, 270, and 280 are travelling on a highway 205, and are connected by an ad hoc wireless network (indicated by arrows).
- the nodes shown in Figure 2A are equivalent to the nodes 160 shown in Figure 1 , and include the same components and functionality described above with reference to nodes 160.
- the highway 205 may have two lanes, a right lane 203 and a left lane 204, both for travel in the same direction.
- an obstruction 210 is present at a particular location or portion of the highway 205.
- the obstruction 210 may represent anything affecting the flow of traffic, such as a group of slow and/or stopped vehicles, an oil spill, an ice patch, a fallen tree, a construction site, a vehicle suffering a mechanical breakdown, etc.
- one or more sensors 159 of node 230 may detect the obstruction 210 as node 230 approaches the obstruction 210.
- the sensor(s) 159 may detect a vehicle or object blocking the right lane 203, a drop in average speed of vehicles at the particular location, a loss in traction, etc.
- node 230 may send information about the obstruction 210 to the other nodes using the ad hoc wireless network. Such information may include, e.g., location, speed, video or still images, a text description, or any other indication of the obstruction 210.
- each receiving node e.g., node 250
- the drivers of the receiving nodes may then adjust their driving based on the received information. For example, a driver may change lanes to avoid the obstruction 210.
- a driver may slow a driving speed before reaching an ice patch.
- the driver of node 270 may avoid the obstruction 210 by detouring off the highway 205 onto a side road 207.
- one or more nodes shown in Figure 2A may determine a traffic flow plan to move around the obstruction 210.
- node 230 may generate a traffic flow plan specifying that groups of vehicles from the two lanes are to use a single unobstructed lane in alternating turns.
- Such a traffic control plan may be based on quantities of vehicles (e.g., ten vehicles from left lane 204, then ten vehicles from right lane 203, etc.), periods of time (e.g., fifty seconds allocated to left lane 204, then forty seconds allocated to right lane 203, etc.), any combination of quantities and time periods, and/or any other parameters.
- the traffic control plan may be based on one or more predefined algorithms for traffic control.
- the traffic control plan may be sent to each vehicle affected by the obstruction 210 (e.g., nodes 240, 250, 260, etc.).
- the traffic control plan may be generated cooperatively by the nodes included in the ad hoc wireless network.
- the driver of each vehicle may be presented with the traffic control plan (or information derived from the traffic control plan) in order to move around the obstruction.
- each driver may receive an indication on a display device (e.g., a green light and red light display, a text message, an auditory signal, etc.) to determine whether to stop or go into an available lane around the obstruction 210.
- a display device e.g., a green light and red light display, a text message, an auditory signal, etc.
- the flow around the obstruction may be controlled in a manner similar to that provided by a traffic policeman, and may thereby reduce the delay to each vehicle.
- nodes 221, 231, 241, 251, 261, 271, and 281 are travelling on highway 205, and are connected by an ad hoc wireless network (indicated by arrows).
- the nodes shown in Figure 2B are equivalent to the nodes 160 shown in Figure 1 , and include the same components and functionality described above with reference to nodes 160.
- an accident 211 e.g., a multi-vehicle collision, a vehicle-pedestrian collision, etc.
- an emergency response vehicle 291 e.g., an ambulance, a fire truck, a police car, etc.
- the emergency response vehicle 291 may receive information related to the accident 211 from any nodes in the vicinity of the accident 211.
- the emergency response vehicle 291 may receive images of the accident 211 from node 231. Such images may have been captured by a sensor 159 (e.g., a camera) of node 231, and may have been sent by node 231 using the ad hoc wireless network.
- the information received by the emergency response vehicle 291 may also include, e.g., location, speed, video, a text description, or any other indication of the accident 211. Such information may enable personnel of the emergency response vehicle 291 to assess the accident 211 and to prepare before arriving at the site of the accident 211.
- personnel in the emergency response vehicle 291 may use the ad hoc wireless network to send instructions to the nodes.
- such instructions may include a request to keep a particular lane clear for the emergency response vehicle 291, a request for additional information about the accident (e.g., request an image of a particular location or from a particular perspective), a request to administer first aid to an injured person, etc.
- embodiments of the invention may include any number and arrangement of nodes.
- ad hoc wireless networks may be established using any number of intermediate nodes, and may also connect to external communications networks.
- any of the nodes may also connect to an access point (not shown) to access another network (e.g., the Internet).
- the nodes may act as network relays for each other, thereby enabling a node to access an external network without being directly connected to an access point.
- Figure 3A shows a sequence 300 for obtaining road information in accordance with one or more embodiments.
- the sequence 300 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device.
- the sequence 300 may be part of the road information module 158 shown in Figure 1 .
- the sequence 300 may be implemented by any other component of a node 160.
- speed and location information may be obtained by a node.
- node 230 may obtain the average speed of traffic at a particular location on highway 205.
- speed and location information may be provided by sensor(s) 159 (e.g., a GPS device, an onboard trip computer, a speedometer, etc.) included in the node 230.
- a determination may be made about whether there is an obstruction in a road.
- node 230 may use sensor(s) 159 to detect the obstruction 210 in highway 205. If it is determined that there is no obstruction, then at step 330, the road information about speed and location (obtained at step 310) is sent to other vehicles using the ad hoc wireless network. For example, referring to Figure 2A , node 230 may send information about average speed of traffic at a particular location on highway 205 to node 250.
- the physical configuration of the obstruction may be determined.
- node 230 may use on-board sensors 159 to determine the physical configuration (e.g., size, shape, location, etc.) of the obstruction 210 and the surrounding area.
- a traffic flow plan may be determined.
- node 230 may determine a traffic flow plan specifying that three vehicles in the left lane 204 (e.g., nodes 240, 260, and 280) are to pass around the obstruction 210 first, followed by three vehicles in the right lane 203 (e.g., nodes 230, 250, and 270).
- the traffic flow plan may be determined by a vote of a group of nodes.
- the road information about speed and location (obtained at step 310) and the traffic flow plan (determined at step 325) may be sent to other vehicles using the ad hoc wireless network.
- node 230 may send road information and a traffic flow plan to nodes 240, 250, 260, 270, and 280.
- the sequence 300 ends.
- Figure 3B shows a sequence 340 for receiving and using road information in accordance with one or more embodiments.
- the sequence 340 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device.
- the sequence 340 may be part of the road information module 158 shown in Figure 1 .
- the sequence 340 may be implemented by any other component of a node 160.
- road information may be received from other vehicles in an ad hoc wireless network.
- node 250 may receive road information (e.g., average speed at a given location, information about an obstruction, etc.) from node 230.
- an estimated time delay may be determined using the received road information.
- the estimated time delay may be presented to a driver of the vehicle.
- node 270 may use information received from node 230 to determine an estimated time delay due to current road conditions, and may present the estimated time delay to a user of node 270.
- node 270 may use sensor(s) 159 (e.g., an navigational computer, a GPS device, etc.) to determine that side road 207 is an alternate route to the highway 205. Thus, the node 270 may interact with a display device to present the alternate route to the driver of node 270.
- an alternate route may be optionally presented based on the estimated time delay (determined at step 355).
- Figure 4 shows a sequence 400 for sharing information in emergency situations in accordance with one or more embodiments.
- the sequence 400 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device.
- the sequence 400 may be part of the road information module 158 shown in Figure 1 .
- the sequence 400 may be implemented by any other component of a node 160.
- information about an accident may be obtained by a node.
- node 230 may obtain information about accident 211.
- the information about the accident 211 may include, e.g., location, position, vehicle condition, number of people involved, type and severity of injuries, etc.
- such accident information may be obtained using sensor(s) 159 (e.g., a video camera, a radar sensor, an infrared sensor, etc.) included in the node 230.
- the accident information may also be entered by a user using an interface of node 230 (e.g., a keyboard, voice interface, graphic interface, mouse, joystick, etc.)
- the accident information may be sent to other vehicles using the ad hoc wireless network.
- the accident information may be received by an emergency response vehicle.
- information about the accident 211 (obtained at step 410) is sent by node 230 using the ad hoc wireless network, and is received by the emergency response vehicle 291.
- the accident information may be presented to emergency responders.
- the emergency responders may use the accident information to assess the accident, and to prepare to respond to the accident.
- personnel of the emergency response vehicle 291 may be presented with information about the accident 211, and may use such information to prepare to respond to the accident 211.
- Such preparation may include, e.g., gathering required medical supplies, retrieving information about a particular type of vehicle, etc.
- the emergency responders send instructions to other vehicles using the ad hoc wireless network.
- personnel of the emergency response vehicle 291 may send instructions to nodes 221, 231, 241, 251, 261, 271, and 281. Examples of such instructions may include a request to keep a particular lane clear for the emergency response vehicle 291, requests for images or descriptions of the accident, instructions for administering first aid to an injured person at the accident site, etc.
- FIG. 5 depicts a computer system 130, which may be the nodes 160 shown in Figure 1 .
- the computer system 130 may include a hard drive 134 and a removable medium 136, coupled by a bus 104 to a chipset core logic 110.
- a keyboard and mouse 120, or other conventional components, may be coupled to the chipset core logic via bus 108.
- the core logic may couple to the graphics processor 112 via a bus 105, and the applications processor 100 in one embodiment.
- the graphics processor 112 may also be coupled by a bus 106 to a frame buffer 114.
- the frame buffer 114 may be coupled by a bus 107 to a display screen 118, such as a liquid crystal display (LCD) touch screen.
- a graphics processor 112 may be a multi-threaded, multi-core parallel processor using single instruction multiple data (SIMD) architecture.
- SIMD single instruction multiple data
- the chipset logic 110 may include a non-volatile memory port to couple the main memory 132. Also coupled to the logic 110 may be a radio transceiver and antenna(s) 121, 122. Speakers 124 may also be coupled through logic 110.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Radar, Positioning & Navigation (AREA)
- Remote Sensing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Life Sciences & Earth Sciences (AREA)
- Atmospheric Sciences (AREA)
- Automation & Control Theory (AREA)
- Traffic Control Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Description
- This relates generally to wireless networks for mobile devices.
- A mobile device can use a wireless communication technology to establish a network connection to another mobile device. The wireless network connection enables the mobile devices to communicate with each other.
US2010194592 discloses a method and an apparatus for broadcasting information related to a vehicular environment using an broadcast network of nodes including a source node and a plurality of relay nodes.
US2005002347 discloses a traffic information service apparatus using an ad-hoc network and a method for controlling the same.
US2005201316 discloses a wireless network system which relays a broadcast signal in multi-ple stages and distributes data to terminals there around.
The present invention provides a method, a computer readable medium and a device according respectively to claim 1, claim 6 and claim 11. - Some embodiments are described with respect to the following figures:
-
Figure 1 is a depiction of a portion of an ad hoc wireless network in accordance with one embodiment of the present invention; -
Figures 2A-2B are examples of an ad hoc wireless network in accordance with one embodiment of the present invention; -
Figures 3A-3B are flow charts in accordance with one embodiment of the present invention; -
Figure 4 is a flow chart in accordance with one embodiment of the present invention; and -
Figure 5 is a schematic depiction of a node in accordance with one embodiment of the present invention. - In accordance with some embodiments, a temporary network may be established between vehicles ("nodes") using wireless connections. Such temporary networks established between nodes may be referred to as "ad hoc wireless networks." In one or more embodiments, an ad hoc wireless network may be used for sending and receiving information about road conditions. Such road information may include an average speed for a particular portion of road, a location and configuration of a road obstruction (e.g., a disabled vehicle), images of an accident scene, a traffic flow plan to route vehicles around a road obstruction, etc. In this manner, vehicles may avoid or reduce delays due to road congestion or obstruction.
- Further, in one or more embodiments, the ad hoc wireless network may enable emergency response vehicles to assess an accident before arriving at the accident scene. Emergency response personnel may also use the ad hoc wireless network to send instructions to vehicles at or near the accident scene. In this manner, embodiments may enable faster and more effective responses to accidents.
- Referring to
Figure 1 , an ad hocwireless network 10 may include any number of nodes 160 (e.g.,nodes wireless connection 165. The nodes 160 may be any vehicles including wireless communications interfaces. For example, a node 160 may be an automobile including a built-in computer and transceiver, a truck including a portable communication device (e.g., a cellular telephone, a laptop computer or a handheld computer), etc. - In one or more embodiments, each node 160 may include a
transceiver 152, aprocessor 154, amemory device 156, aroad information module 158, and sensor(s) 159. Further, each node 160 may have a transmission range, meaning a physical distance over which the includedtransceiver 152 can effectively send or receive radio transmissions to another device. Generally, a node 160 may establish awireless connection 165 to another node 160 if the two nodes 160 are within each other's transmission ranges. - Further, in one or more embodiments, if a first node (e.g.,
node 160A) is out of transmission range of a second node (e.g.,node 160B), the first and second nodes may instead connect to each other through one or more intervening nodes (not shown). The intervening nodes may each act as a relay station or repeater, thus enabling the first node to connect to the second node indirectly. - The
wireless connections 165 may be based on any radio communications technologies and/or standards. For example, thewireless connection 165 may be a Wi-Fi connection conforming to the IEEE (Institute of Electrical and Electronics Engineers) 802.11 standard, IEEE 802.11-2007, published June 12, 2007. - In one or more embodiments, the
road information module 158 may include functionality to discover other nodes 160 with which to establish an ad hoc wireless network. Such functionality may include broadcasting a beacon to invite other nodes 160 to join or establish an ad hoc wireless network. In addition, such functionality may include accepting a beacon received from another node 160. - In one or more embodiments, the
road information module 158 may also include functionality to determine whether to establish an ad hoc wireless network (or join an existing network) based on an estimated time duration of a wireless connection (i.e., how long the node 160 is expected to maintain thewireless connection 165 to the other node(s) 160). For example, the time duration may be estimated by determining the amount of time that will elapse before one node 160 physically moves out of the transmission range of the other node 160. This determination may involve predicting the future movements of each node based on the current speed, direction, planned path, and/or destination location of each node 160. The predicted movements may then be used to estimate a point in time (if any) when at least one node 160 moves out of the transmission range of another node 160. In one or more embodiments, the ad hoc wireless network may be established (or is joined) if the estimated time duration exceeds some predefined minimum time of connection (e.g., ten minutes, one hour, etc.). - In one or more embodiments, the
road information module 158 may interact with the sensor(s) 159. The sensor(s) 159 may be any device to collect information about the node 160 or its surroundings. The information about the node 160 may include the speed, direction, destination, and planned path of the node 160. For example, the sensor(s) 159 may include a Global Positioning System (GPS) device, an onboard trip computer, a speedometer, a compass, etc. The information about the node 160 may also include a transmission range and signal strength for the node 160. For example, the sensor(s) 159 may also include a radio signal analysis device, a network bandwidth analysis device, etc. - The information about the surroundings of node 160 may include information about the physical configuration of the space around the node 160. Such spatial information may include the number and layout of lanes of the road, the positions and/or speeds of any neighboring vehicles, the position and geometry of a road obstruction (e.g., a fallen tree, a vehicle accident, a construction site), etc. For example, the sensor(s) 159 may also include a camera to capture images of the surroundings (e.g., video camera, still camera, stereoscopic camera), a light-based object-detection system (e.g., a laser, infrared, or ultraviolet emitter and/or detector), a radio-based object-detection system (e.g., active and/or passive radar), a sound-based object-detection system (e.g., active and/or passive sonar), etc.
- In one or more embodiments, the information about the surroundings of node 160 may relate to the road surface and/or traction characteristics. For example, the sensor(s) 159 may include a tire traction sensor, a road ice sensor, etc. Further, it is contemplated that the sensor(s) 159 may be any other device or combination of devices configured to capture any other information about the node 160 or its surroundings.
- In one or more embodiments, the
road information module 158 may include functionality to analyze and/or summarize information derived from the sensor(s) 159. For example, theroad information module 158 may use information about vehicle speed and road configuration to determine that a particular lane is obstructed at a specific location. Theroad information module 158 may also include functionality to present the information and/or an analysis thereof to a user of the node 160. For example, theroad information module 158 may interact with a display device or user interface (not shown) to present a summary of the information to a user. Further, in one or more embodiments, theroad information module 158 may include functionality to send such information and/or an analysis thereof to other nodes 160 using the ad hoc wireless network. - In one or more embodiments, the
road information module 158 of afirst node 160A may include functionality to receive inbound road information from asecond node 160B, and to present the received inbound road information to a user of thefirst node 160A. Theroad information module 158 may also include functionality to determine an alternate route based on road condition information received from another node, and to present the alternate route to a user of the receiving node (e.g., a driver of a vehicle). For example, theroad information module 158 ofnode 160A may receive information fromnode 160B via thetransceiver 152, and may then interact with a display device or user interface (not shown) to present the information to a user ofnode 160A. - In one or more embodiments, the
road information module 158 of a node 160 may include functionality to send information about an accident to an emergency response vehicle using an ad hoc wireless network. For example, in the event of an accident, an emergency response vehicle may be travelling to the scene of the accident. In such a situation, receiving information about the accident from a node may enable personnel of the emergency response vehicle to assess the accident and to prepare before arriving at the accident scene. Theroad information module 158 of a node 160 may also include functionality to receive instructions from the emergency response vehicle, and to present the received instructions to a user of the node 160. For example, theroad information module 158 of node 160 may receive instructions from the emergency response vehicle via thetransceiver 152, and may then interact with a display device or user interface (not shown) to present the instructions to a user ofnode 160A. - In one or more embodiments, the
road information module 158 of a node 160 may include functionality to determine a traffic flow plan, and to present the traffic flow plan to a user of the node 160. The traffic flow plan may specify how vehicles are to move around an obstruction in a road. In one or more embodiments, theroad information module 158 may automatically determine a traffic flow plan based on predefined algorithms to improve flow through a bottleneck (e.g., merging one vehicle at a time, merging groups of a specified size, merging each lane for a specified period of time, etc.). The traffic flow plan may be determined by a single node 160 (e.g., by the first node 160 to detect the obstruction, by a randomly chosen node 160, etc.), or may be determined cooperatively among multiple nodes 160 (e.g., by automatic voting of each node 160, by user-specified voting in a user interface, etc.). - The
road information module 158 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device. - Referring now to
Figure 2A , an example 20 of using an ad hoc wireless network for sharing road information is depicted in accordance with one or more embodiments. In this example,nodes highway 205, and are connected by an ad hoc wireless network (indicated by arrows). Assume that the nodes shown inFigure 2A are equivalent to the nodes 160 shown inFigure 1 , and include the same components and functionality described above with reference to nodes 160. - As shown in
Figure 2A , thehighway 205 may have two lanes, aright lane 203 and aleft lane 204, both for travel in the same direction. In this example, anobstruction 210 is present at a particular location or portion of thehighway 205. Theobstruction 210 may represent anything affecting the flow of traffic, such as a group of slow and/or stopped vehicles, an oil spill, an ice patch, a fallen tree, a construction site, a vehicle suffering a mechanical breakdown, etc. In one or more embodiments, asnode 230 approaches theobstruction 210, one ormore sensors 159 ofnode 230 may detect theobstruction 210. For example, the sensor(s) 159 may detect a vehicle or object blocking theright lane 203, a drop in average speed of vehicles at the particular location, a loss in traction, etc. - In response to detecting the
obstruction 210,node 230 may send information about theobstruction 210 to the other nodes using the ad hoc wireless network. Such information may include, e.g., location, speed, video or still images, a text description, or any other indication of theobstruction 210. Upon receiving the information fromnode 230, each receiving node (e.g., node 250) may present the information (or an indication based on the information) to a user of the receiving node (e.g., a driver). The drivers of the receiving nodes may then adjust their driving based on the received information. For example, a driver may change lanes to avoid theobstruction 210. In another example, a driver may slow a driving speed before reaching an ice patch. In yet another example, the driver ofnode 270 may avoid theobstruction 210 by detouring off thehighway 205 onto aside road 207. - In one or more embodiments, one or more nodes shown in
Figure 2A may determine a traffic flow plan to move around theobstruction 210. For example,node 230 may generate a traffic flow plan specifying that groups of vehicles from the two lanes are to use a single unobstructed lane in alternating turns. Such a traffic control plan may be based on quantities of vehicles (e.g., ten vehicles fromleft lane 204, then ten vehicles fromright lane 203, etc.), periods of time (e.g., fifty seconds allocated to leftlane 204, then forty seconds allocated toright lane 203, etc.), any combination of quantities and time periods, and/or any other parameters. The traffic control plan may be based on one or more predefined algorithms for traffic control. The traffic control plan may be sent to each vehicle affected by the obstruction 210 (e.g.,nodes - Further, in one or more embodiments, the driver of each vehicle may be presented with the traffic control plan (or information derived from the traffic control plan) in order to move around the obstruction. For example, each driver may receive an indication on a display device (e.g., a green light and red light display, a text message, an auditory signal, etc.) to determine whether to stop or go into an available lane around the
obstruction 210. In this manner, the flow around the obstruction may be controlled in a manner similar to that provided by a traffic policeman, and may thereby reduce the delay to each vehicle. - Referring now to
Figure 2B , an example 21 of using an ad hoc wireless network in emergency response situations is depicted in accordance with one or more embodiments. In this example,nodes highway 205, and are connected by an ad hoc wireless network (indicated by arrows). Assume that the nodes shown inFigure 2B are equivalent to the nodes 160 shown inFigure 1 , and include the same components and functionality described above with reference to nodes 160. - As shown in
Figure 2B , an accident 211 (e.g., a multi-vehicle collision, a vehicle-pedestrian collision, etc.) has occurred at a particular location on thehighway 205. Assume that an emergency service has been called in response to theaccident 211, and therefore an emergency response vehicle 291 (e.g., an ambulance, a fire truck, a police car, etc.) is travelling toward the site of theaccident 211. - In one or more embodiments, the
emergency response vehicle 291 may receive information related to theaccident 211 from any nodes in the vicinity of theaccident 211. For example, theemergency response vehicle 291 may receive images of theaccident 211 fromnode 231. Such images may have been captured by a sensor 159 (e.g., a camera) ofnode 231, and may have been sent bynode 231 using the ad hoc wireless network. The information received by theemergency response vehicle 291 may also include, e.g., location, speed, video, a text description, or any other indication of theaccident 211. Such information may enable personnel of theemergency response vehicle 291 to assess theaccident 211 and to prepare before arriving at the site of theaccident 211. - In one or more embodiments, personnel in the
emergency response vehicle 291 may use the ad hoc wireless network to send instructions to the nodes. For example, such instructions may include a request to keep a particular lane clear for theemergency response vehicle 291, a request for additional information about the accident (e.g., request an image of a particular location or from a particular perspective), a request to administer first aid to an injured person, etc. - Note that the examples shown in
Figures 1 and2A-2B are provided for the sake of illustration, and are not intended to limit embodiments of the invention. For example, embodiments of the invention may include any number and arrangement of nodes. Further, it is contemplated that ad hoc wireless networks may be established using any number of intermediate nodes, and may also connect to external communications networks. For example, any of the nodes may also connect to an access point (not shown) to access another network (e.g., the Internet). It is also contemplated that the nodes may act as network relays for each other, thereby enabling a node to access an external network without being directly connected to an access point. -
Figure 3A shows asequence 300 for obtaining road information in accordance with one or more embodiments. Thesequence 300 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device. In one embodiment, thesequence 300 may be part of theroad information module 158 shown inFigure 1 . In another embodiment, thesequence 300 may be implemented by any other component of a node 160. - At
step 310, speed and location information may be obtained by a node. For example, referring toFigures 1 and2A ,node 230 may obtain the average speed of traffic at a particular location onhighway 205. In one or more embodiments, such speed and location information may be provided by sensor(s) 159 (e.g., a GPS device, an onboard trip computer, a speedometer, etc.) included in thenode 230. - At
step 315, a determination may be made about whether there is an obstruction in a road. For example, referring toFigure 2A ,node 230 may use sensor(s) 159 to detect theobstruction 210 inhighway 205. If it is determined that there is no obstruction, then atstep 330, the road information about speed and location (obtained at step 310) is sent to other vehicles using the ad hoc wireless network. For example, referring toFigure 2A ,node 230 may send information about average speed of traffic at a particular location onhighway 205 tonode 250. - However, if it is determined at
step 315 that there is an obstruction, then atstep 320, the physical configuration of the obstruction may be determined. For example, referring toFigure 2A ,node 230 may use on-board sensors 159 to determine the physical configuration (e.g., size, shape, location, etc.) of theobstruction 210 and the surrounding area. - At
step 325, a traffic flow plan may be determined. For example, referring toFigure 2A ,node 230 may determine a traffic flow plan specifying that three vehicles in the left lane 204 (e.g.,nodes obstruction 210 first, followed by three vehicles in the right lane 203 (e.g.,nodes - Next, at
step 330, the road information about speed and location (obtained at step 310) and the traffic flow plan (determined at step 325) may be sent to other vehicles using the ad hoc wireless network. For example, referring toFigure 2A ,node 230 may send road information and a traffic flow plan tonodes step 330, thesequence 300 ends. -
Figure 3B shows asequence 340 for receiving and using road information in accordance with one or more embodiments. Thesequence 340 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device. In one embodiment, thesequence 340 may be part of theroad information module 158 shown inFigure 1 . In another embodiment, thesequence 340 may be implemented by any other component of a node 160. - At
step 350, road information may be received from other vehicles in an ad hoc wireless network. For example, referring toFigure 2A ,node 250 may receive road information (e.g., average speed at a given location, information about an obstruction, etc.) fromnode 230. - At
step 355, an estimated time delay may be determined using the received road information. Atstep 360, the estimated time delay may be presented to a driver of the vehicle. For example, referring toFigure 2A ,node 270 may use information received fromnode 230 to determine an estimated time delay due to current road conditions, and may present the estimated time delay to a user ofnode 270. - At
step 370, a determination may be made about whether there any alternate routes available. If not, then thesequence 340 continues at step 380 (described below). However, if it is determined atstep 370 that there are alternate routes available, then atstep 375, the alternate routes may be presented to a driver. For example, referring toFigures 1 and2A ,node 270 may use sensor(s) 159 (e.g., an navigational computer, a GPS device, etc.) to determine thatside road 207 is an alternate route to thehighway 205. Thus, thenode 270 may interact with a display device to present the alternate route to the driver ofnode 270. In one or more embodiments, an alternate route may be optionally presented based on the estimated time delay (determined at step 355). - At
step 380, a determination may be made about whether a traffic flow plan has been received. If not, then thesequence 340 ends. However, if it is determined atstep 380 that a traffic flow plan has been received, then atstep 385, the traffic flow plan may be presented to a driver. For example, referring toFigure 2A ,node 270 may determine that a traffic flow plan forobstruction 211 has been received fromnode 230. Thus, thenode 270 may interact with a display device to present the traffic flow plan to the driver ofnode 270. Afterstep 385, thesequence 340 ends. -
Figure 4 shows asequence 400 for sharing information in emergency situations in accordance with one or more embodiments. Thesequence 400 may be implemented in hardware, software, and/or firmware. In firmware and software embodiments it may be implemented by computer executed instructions stored in a non-transitory computer readable medium, such as an optical, semiconductor, or magnetic storage device. In one embodiment, thesequence 400 may be part of theroad information module 158 shown inFigure 1 . In another embodiment, thesequence 400 may be implemented by any other component of a node 160. - At
step 410, information about an accident may be obtained by a node. For example, referring toFigures 1 and2B ,node 230 may obtain information aboutaccident 211. The information about theaccident 211 may include, e.g., location, position, vehicle condition, number of people involved, type and severity of injuries, etc. In one or more embodiments, such accident information may be obtained using sensor(s) 159 (e.g., a video camera, a radar sensor, an infrared sensor, etc.) included in thenode 230. Optionally, the accident information may also be entered by a user using an interface of node 230 (e.g., a keyboard, voice interface, graphic interface, mouse, joystick, etc.) - At
step 420, the accident information may be sent to other vehicles using the ad hoc wireless network. Atstep 430, the accident information may be received by an emergency response vehicle. For example, referring toFigure 2B , information about the accident 211 (obtained at step 410) is sent bynode 230 using the ad hoc wireless network, and is received by theemergency response vehicle 291. - At
step 440, the accident information may be presented to emergency responders. Atstep 450, the emergency responders may use the accident information to assess the accident, and to prepare to respond to the accident. For example, referring toFigure 2B , personnel of theemergency response vehicle 291 may be presented with information about theaccident 211, and may use such information to prepare to respond to theaccident 211. Such preparation may include, e.g., gathering required medical supplies, retrieving information about a particular type of vehicle, etc. - At
step 460, the emergency responders send instructions to other vehicles using the ad hoc wireless network. For example, referring toFigure 2B , personnel of theemergency response vehicle 291 may send instructions tonodes emergency response vehicle 291, requests for images or descriptions of the accident, instructions for administering first aid to an injured person at the accident site, etc. Afterstep 460, thesequence 400 ends. -
Figure 5 depicts acomputer system 130, which may be the nodes 160 shown inFigure 1 . Thecomputer system 130 may include ahard drive 134 and aremovable medium 136, coupled by abus 104 to achipset core logic 110. A keyboard andmouse 120, or other conventional components, may be coupled to the chipset core logic viabus 108. The core logic may couple to thegraphics processor 112 via abus 105, and theapplications processor 100 in one embodiment. Thegraphics processor 112 may also be coupled by abus 106 to aframe buffer 114. Theframe buffer 114 may be coupled by abus 107 to adisplay screen 118, such as a liquid crystal display (LCD) touch screen. In one embodiment, agraphics processor 112 may be a multi-threaded, multi-core parallel processor using single instruction multiple data (SIMD) architecture. - The
chipset logic 110 may include a non-volatile memory port to couple themain memory 132. Also coupled to thelogic 110 may be a radio transceiver and antenna(s) 121, 122.Speakers 124 may also be coupled throughlogic 110.
Claims (15)
- A method comprising:determining whether to establish an ad hoc wireless network based on an estimated time duration of a wireless connection;establishing the ad hoc wireless network comprising a plurality of vehicles, if the estimated time duration exceeds a predefined minimum time of connection;obtaining road information using sensors of a first vehicle of the plurality of vehicles; andsending the road information to other vehicles of the plurality of vehicles using the ad hoc wireless network.
- The method of claim 1 wherein obtaining the road information comprises determining an average speed for a particular portion of a road.
- The method of claim 1 wherein obtaining the road information comprises determining a location of an obstruction in a road.
- The method of claim 3 wherein obtaining the road information further comprises determining a physical configuration of the obstruction.
- The method of claim 1 wherein obtaining the road information comprises capturing at least one image of an accident.
- A non-transitory computer readable medium storing instructions to cause a computer to:determine whether to establish an ad hoc wireless network based on an estimated time duration of a wireless connection;establish the ad hoc wireless network comprising a plurality of vehicles, if the estimated time duration exceeds a predefined minimum time of connection;obtain road information using sensors of a first vehicle of the plurality of vehicles; andsend the road information to other vehicles of the plurality of vehicles using the ad hoc wireless network.
- The medium of claim 6 further storing instructions to establish the ad hoc wireless network based on speed and direction information for the plurality of vehicles.
- The medium of claim 6 further storing instructions to send an average speed for a particular portion of a road to a second vehicle of the plurality of vehicles.
- The medium of claim 6 further storing instructions to send a location of an obstruction in a road to a second vehicle of the plurality of vehicles.
- The medium of claim 6 further storing instructions to determine a traffic flow plan for an obstruction in a road in cooperation with at least one of the plurality of vehicles.
- A mobile device comprising:at least one sensor;a wireless transceiver; anda controller coupled to the wireless transceiver, the controller is adapted to:determine whether to establish an ad hoc wireless network based on an estimated time duration of a wireless connection;establish the ad hoc wireless network, if the estimated time duration exceeds a predefined minimum time of connection;obtain road information using the at least one sensor; andsend the road information to a plurality of vehicles using an ad hoc wireless network.
- The mobile device of claim 11 wherein the controller is also to connect to the ad hoc wireless network.
- The mobile device of claim 11 wherein the controller is also to determine a traffic flow plan for an obstruction in a road.
- The mobile device of claim 11 wherein the controller is also to receive inbound road information from a second vehicle of the plurality of vehicles.
- The mobile device of claim 14 wherein the controller is also to present a user of the mobile device with the inbound road condition information received from the second vehicle.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2011/068102 WO2013101183A1 (en) | 2011-12-30 | 2011-12-30 | Wireless networks for sharing road information |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2798863A1 EP2798863A1 (en) | 2014-11-05 |
EP2798863A4 EP2798863A4 (en) | 2015-09-16 |
EP2798863B1 true EP2798863B1 (en) | 2017-02-01 |
Family
ID=48698417
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP11878801.7A Active EP2798863B1 (en) | 2011-12-30 | 2011-12-30 | Wireless networks for sharing road information |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2798863B1 (en) |
CN (2) | CN110617833B (en) |
WO (1) | WO2013101183A1 (en) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8825265B1 (en) * | 2012-03-16 | 2014-09-02 | Google Inc. | Approach for consolidating observed vehicle trajectories into a single representative trajectory |
US9791282B2 (en) | 2014-09-27 | 2017-10-17 | Intel Corporation | Technologies for route navigation sharing in a community cloud |
CN107438085B (en) * | 2016-05-25 | 2021-12-28 | 西安中兴新软件有限责任公司 | Ad hoc network method based on vehicle-mounted terminal and vehicle-mounted terminal |
CN106408980B (en) * | 2016-09-23 | 2019-06-21 | 盯盯拍(深圳)技术股份有限公司 | Road conditions live broadcasting method and road conditions live broadcast device |
US10703386B2 (en) | 2018-10-22 | 2020-07-07 | Ebay Inc. | Intervehicle communication and notification |
CN110708668A (en) * | 2019-09-29 | 2020-01-17 | 潘丽 | Vehicle-mounted fusion detector and autonomous vehicle networking system |
CN111337043B (en) * | 2020-03-17 | 2022-08-02 | 北京嘀嘀无限科技发展有限公司 | Path planning method and device, storage medium and electronic equipment |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7421334B2 (en) * | 2003-04-07 | 2008-09-02 | Zoom Information Systems | Centralized facility and intelligent on-board vehicle platform for collecting, analyzing and distributing information relating to transportation infrastructure and conditions |
KR100520157B1 (en) * | 2003-06-18 | 2005-10-10 | 삼성전자주식회사 | A System and Method For Providing Traffic Information based on Ad Hoc Network |
JP4128149B2 (en) * | 2004-02-27 | 2008-07-30 | Kddi株式会社 | Wireless network system, relay terminal and program in the same system |
US7362711B2 (en) * | 2004-12-16 | 2008-04-22 | Palo Alto Research Center Incorporated | Method and apparatus for detecting and correcting malicious data in an ad-hoc network |
US20080140287A1 (en) * | 2006-12-06 | 2008-06-12 | Man Seok Yang | System and method for informing vehicle accident using telematics device |
KR100835385B1 (en) * | 2006-12-06 | 2008-06-04 | 한국전자통신연구원 | The system and method for informing automobile accident using telematics device |
CN100561540C (en) * | 2008-05-14 | 2009-11-18 | 西安交通大学 | A kind of method for processing traffic road condition information based on vehicle mounted wireless sensor network |
CN101448338B (en) * | 2008-11-27 | 2010-08-11 | 北京理工大学 | Mobile three-dimensional spatial wireless testing network system |
EP2203004B1 (en) * | 2008-12-29 | 2011-12-21 | Hitachi, Ltd. | Method and apparatus for determining a distribution of neighbour nodes around a first node in a communication network |
US20100194592A1 (en) * | 2009-02-04 | 2010-08-05 | Raymond Yim | Method and System for Disseminating Vehicle and Road Related Information in Multi-Hop Broadcast Networks |
CN101727747A (en) * | 2009-12-16 | 2010-06-09 | 南京信息工程大学 | Abnormal road jam alarming method based on flow detection |
CN101951659B (en) * | 2010-08-13 | 2013-09-25 | 华南理工大学 | Self-organization method of sensor network and mobile terminal system based on same |
-
2011
- 2011-12-30 CN CN201910993786.4A patent/CN110617833B/en active Active
- 2011-12-30 EP EP11878801.7A patent/EP2798863B1/en active Active
- 2011-12-30 CN CN201180075953.9A patent/CN104012123A/en active Pending
- 2011-12-30 WO PCT/US2011/068102 patent/WO2013101183A1/en active Application Filing
Non-Patent Citations (1)
Title |
---|
None * |
Also Published As
Publication number | Publication date |
---|---|
WO2013101183A1 (en) | 2013-07-04 |
CN110617833A (en) | 2019-12-27 |
CN110617833B (en) | 2023-11-03 |
EP2798863A4 (en) | 2015-09-16 |
EP2798863A1 (en) | 2014-11-05 |
CN104012123A (en) | 2014-08-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20140091949A1 (en) | Wireless Networks for Sharing Road Information | |
CN108738021B (en) | Communication system, in-vehicle device, and recording medium on which program is recorded | |
EP2798863B1 (en) | Wireless networks for sharing road information | |
US20230018419A1 (en) | Autonomous vehicle control system with roadside unit (rsu) network's global sensing | |
US10019898B2 (en) | Systems and methods to detect vehicle queue lengths of vehicles stopped at a traffic light signal | |
US8954205B2 (en) | System and method for road side equipment of interest selection for active safety applications | |
US20210132604A1 (en) | Autonomous passenger vehicle system | |
US11568741B2 (en) | Communication device, control method thereof, and communication system including the same | |
KR100986279B1 (en) | Method for control intelligent traffic signal and system thereof | |
WO2018132378A2 (en) | Connected automated vehicle highway systems and methods | |
US11842631B2 (en) | Communication device, control method thereof and communication system including the same | |
JP2018077652A (en) | Vehicle driving support system and collective housing | |
US20220408307A1 (en) | Roadside apparatus and communication congestion control method | |
KR20190104477A (en) | Method for charging battery of autonomous vehicle and apparatus therefor | |
AU2018208404B2 (en) | Connected automated vehicle highway systems and methods | |
KR20190104476A (en) | Method for controlling vehicle in autonomous driving system and apparatus thereof | |
KR101477523B1 (en) | A corporative image recording system using vehicle-to-vehicle communications and the method thereof | |
CN113593224B (en) | Road condition sharing method and device, vehicle-mounted terminal and storage medium | |
KR20200068776A (en) | Telecommunication service providing method and system for connected & autonomous vehicles | |
KR20210123903A (en) | Apparatus for supporting vehicle to everything communication, system having the same and method thereof | |
KR20200036071A (en) | Intelligent Platforms and Systems of Automated Parking and Calling Car by Smart and Integrated Autonomous Driving Car Control System | |
CN104680838A (en) | Safety assisting method and system for automobile | |
CN112583872B (en) | Communication method and device | |
US20210110708A1 (en) | Hierarchical integrated traffic management system for managing vehicles | |
KR20240000596A (en) | passenger assistance system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20140613 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
RA4 | Supplementary search report drawn up and despatched (corrected) |
Effective date: 20150814 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: G01C 21/34 20060101ALI20150810BHEP Ipc: G08G 1/0967 20060101ALI20150810BHEP Ipc: G08G 1/0968 20060101ALI20150810BHEP Ipc: G08G 1/16 20060101ALI20150810BHEP Ipc: H04W 4/02 20090101AFI20150810BHEP Ipc: H04W 4/04 20090101ALI20150810BHEP Ipc: H04W 4/22 20090101ALI20150810BHEP Ipc: H04W 84/18 20090101ALI20150810BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20160901 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 866396 Country of ref document: AT Kind code of ref document: T Effective date: 20170215 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602011034875 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 866396 Country of ref document: AT Kind code of ref document: T Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170502 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170601 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170501 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: RS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170501 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170601 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602011034875 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SM Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20171103 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171230 Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171230 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20180831 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20171231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171230 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180102 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171231 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171231 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20171231 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20111230 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20201001 Year of fee payment: 10 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20211230 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20211230 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230518 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20230925 Year of fee payment: 13 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230919 Year of fee payment: 13 |