Communication of emergency messages with road markers
Claim Score by NHIP
Abstract
Disclosed is an apparatus, system, and method to communicate emergency messages utilizing road markers. The road marker may include: a light emitter to emit different light colors; a transmitter; and a receiver to receive an emergency message from an emergency vehicle, a road marker gateway, or another road marker. Further, the road marker may include a processor to: to command the light emitter to emit a light color based upon the emergency message received by the receiver; and command the transmitter to transmit the received emergency message to at least one other road marker.

Term
Projected expiry 30 March 2031.
- Priority and filed
- Published
- Today
- Projected expiry
51 claims: 6 independent, 45 dependent
- 1A road marker to communicate emergency messages with other road markers comprising:a light emitter to emit different light colors;a transmitter;a receiver to receive an emergency message from an emergency vehicle, a road marker gateway, or another road marker;and a processor to: command the light emitter to emit a light color based upon the emergency message received by the receiver;and command the transmitter to transmit the received emergency message to at least one other road marker.
- 11A method to communicate emergency messages between road markers comprising:receiving an emergency message at a road marker from an emergency vehicle, a road marker gateway, or another road marker;commanding a light emitter to emit a light color based upon the emergency message received;and transmitting the received emergency message to at least one other road marker.
- 20A road marker to communicate emergency messages with other road markers comprising:mean for receiving an emergency message at a road marker from an emergency vehicle, a road marker gateway, or another road marker means for emitting a light color based upon the emergency message received;and means for transmitting the received emergency message to at least one other road marker.
- 29A computer program product comprising:a computer-readable medium comprising code for: receiving an emergency message at a road marker from an emergency vehicle, a road marker gateway, or another road marker emitting a light color based upon the emergency message received;and transmitting the received emergency message to at least one other road marker.
- 38A road marker gateway to communicate emergency messages to and from road markers comprising:a transmitter;a receiver to receive an emergency message from a traffic management station;and a processor to command the transmitter to transmit the emergency message to a road marker, wherein the road marker emits a light color based upon the received emergency message and transmits the received emergency message to at least one other road marker.
- 45Broadest claimClaim Score 81, broad(NHIP)A computer program product comprising:a computer-readable medium comprising code for: receiving an emergency message from a traffic management station;and transmitting the emergency message to a road marker, wherein the road marker emits a light color based upon the received emergency message and transmits the received emergency message to at least one other road marker.
Independent claims6
74 paragraphs in 4 sections, as filed
BACKGROUND
00011. Field
0002The present invention relates generally to an apparatus, system, and method to communicate emergency messages utilizing road markers.
00032. Relevant Background
0004Today, worldwide highway and road traffic flow control is typically done independently and visually on an intersection-by-intersection basis using age-old magnetometer vehicle detection coupled with timed signal lights. Government agencies are aware of the increased safety and resulting cost saving potentials associated with making highways more intelligent. More informed and aware drivers will result in fewer traffic accidents which in turn results in less emergency response calls, less insurance claims, and great cost savings.
0005Thousands of people die or are seriously injured from traffic accidents when they could have been saved or had better outcomes if emergency services had arrived just a few minutes earlier. In addition, multiple vehicle accidents often occur because of the lack of warning of impending danger ahead from accidents or stopped traffic.
0006One approach that has been utilized is the use of portable and fixed programmable signs that are placed along the roadside. Although, a portable sign can sometimes be quickly dispatched to an accident scene, doing so nevertheless takes a significant amount of time. Fixed signs, on the other hand, are usable only on the location where they are erected. In addition, both portable and fixed signs must be programmed at the time needed with a message to display. Further, pavement markers have been proposed that can indicate to drivers to merge in case of traffic. However, none of these systems communicate emergency messages utilizing road markers to drivers.
SUMMARY
0007Embodiments of the invention may relate to an apparatus, system, and method to communicate emergency messages utilizing road markers. In one embodiment, a road marker may include: a light emitter to emit different light colors; a transmitter; and a receiver to receive an emergency message from an emergency vehicle, a road marker gateway, or another road marker. Further, the road marker may include a processor to: to command the light emitter to emit a light color based upon the emergency message received by the receiver; and command the transmitter to transmit the received emergency message to at least one other road marker.
BRIEF DESCRIPTION OF THE DRAWINGS
<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating a system to communicate emergency messages utilizing road markers for a highway having a plurality of lanes in which a plurality of cars, trucks, and other vehicles drive on.
<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of a WIRM.
<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram illustrating the components of a WIRM gateway and a traffic management station.
<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram that illustrates a process to implement the lighting of WIRMS.
<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram showing the traffic emergency system.
DETAILED DESCRIPTION
0013The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” or “example” is not necessarily to be construed as preferred or advantageous over other embodiments.
0014With reference to <figref idref="DRAWINGS">FIG. 1</figref>, <figref idref="DRAWINGS">FIG. 1</figref> is a system diagram in which embodiments of the invention may be practiced. In particular, in one embodiment, a wireless emergency system <b>100</b> having a plurality of wireless intelligent road markers (WIRMS) <b>102</b> that communicate emergency messages with one another in combination with a plurality of WIRM gateways <b>110</b> and a traffic management station <b>120</b> is illustrated. As will be described in more detail, the WIRMS <b>102</b> may be used to emit light of different colors, flashes, etc., to warn drivers of emergency situations such as a vehicle accident <b>140</b>, bad weather, road/lane problems, traffic congestion, closed lane, etc. Further, by the WIRMS <b>102</b> communicating with each other, the WIRMS <b>102</b> can transmit these emergency messages down the road to oncoming traffic.
0015As can be seen in <figref idref="DRAWINGS">FIG. 1</figref>, a highway is illustrated having a plurality of lanes <b>109</b> in which a plurality of cars <b>130</b>, trucks <b>132</b>, buses, etc., and other vehicles are driving. As can be further seen on <figref idref="DRAWINGS">FIG. 1</figref>, each of the lanes <b>109</b> may have a corresponding group of WIRMS <b>104</b>, <b>106</b>, <b>108</b>, and <b>110</b> that may be utilized to emit light and flashes to warn drivers about vehicle accidents <b>140</b>, bad weather, road/lane problems, traffic congestion, closed lane, etc.
0016The WIRMS <b>102</b> may communicate with one another, along with a plurality of WIRM gateways <b>110</b>, and through link <b>112</b> with a traffic management station <b>120</b>. Traffic management station <b>120</b> may further be connected to the Internet <b>122</b>, the public switch telephone network (PSTN) <b>124</b>, along with other data sources.
0017As one particular example, a WIRM <b>106</b> may receive an instruction from an emergency vehicle <b>136</b> that a traffic accident <b>140</b> has occurred such that WIRMS <b>104</b> and <b>106</b> associated with that lane <b>109</b> are commanded to emit a red color indicating to drivers <b>130</b> to merge into another lane and that the lane is closed such that vehicles will avoid the upcoming car accident <b>140</b> and will free the lane for the emergency vehicle <b>136</b>. This emergency message may be transmitted from the emergency vehicle <b>136</b> to the nearest WIRM <b>104</b> and thereafter on to the other WIRMS <b>104</b> and <b>106</b>, on WIRM by WIRM basis, as well as to a WIRM gateway <b>110</b>. From the WIRM gateway <b>100</b> this emergency message may be transmitted via a link <b>112</b> to the traffic management station <b>120</b> to indicate to the traffic management station <b>120</b> that a traffic accident <b>140</b> has occurred, the specific location of the traffic accident, as well as what portions of the lanes have been closed to allow for the emergency vehicle <b>136</b> to attend to the traffic accident <b>140</b>.
0018Thus, in one embodiment, a WIRM <b>102</b> receives an emergency message from an emergency vehicle <b>136</b> and transmits this message to the surrounding WIRMS <b>104</b> and <b>106</b> to warn drivers of the emergency and these WIRMS may indicate the emergency by turning to a red color or flashing a red color. It should be appreciated that one or both sides of the lane WIRMS <b>104</b> and/or <b>106</b> may be turned red or flash red to indicate to drivers to exit the lane to avoid further traffic collisions and to aid the approach of emergency vehicle <b>136</b>. Thus, an accident <b>140</b>, in the distance may be indicated to drivers by WIRMS <b>104</b> and <b>106</b> sending a message to oncoming traffic. Accordingly, as one example, WIRMS <b>104</b> and <b>106</b> may communicate with each other and further this emergency data may be transmitted to a WIRM gateway <b>110</b> and further via link <b>112</b> to the traffic management station <b>120</b>.
0019With additional reference to <figref idref="DRAWINGS">FIG. 2</figref>, a block diagram of a WIRM <b>102</b>, according to one embodiment, is illustrated. A WIRM <b>102</b> that is used to communicate emergency messages with other WIRMS <b>102</b> (as well as to a WIRM gateway <b>110</b>) may comprise: a light emitter <b>208</b> (e.g., an LED) to emit different light colors (e.g. red <b>220</b>, yellow <b>240</b>, green <b>250</b>); a transmitter <b>204</b> to transmit an emergency message <b>209</b>; a receiver <b>206</b> to receive an emergency message <b>209</b> from an emergency vehicle <b>136</b>, a road marker gateway <b>110</b>, or another WIRM <b>102</b>; and a processor <b>202</b>. The processor <b>202</b> may be used to: command the light emitter <b>208</b> to emit a light color based upon the emergency message <b>209</b> received by the receiver <b>206</b>; and command the transmitter <b>204</b> to transmit the received emergency message <b>209</b> to nearby WIRMS (e.g., all WIRMS within range, lane specific WIRMS, and/or specifically identified WIRMS). The WIRMS communicated to may be designated based upon the type of emergency and locations, such as, vehicle accidents, bad weather conditions, road/lane problems, traffic congestion, closed lane, etc.
0020Further, the wireless emergency system <b>100</b> includes many different types of ways that emergency messages can be transmitted to WIRMS <b>102</b>. For example, an emergency message <b>209</b> may be transmitted from an emergency vehicle <b>136</b> to a WIRM <b>102</b>, a WIRM gateway <b>110</b>, and to the traffic management station <b>120</b>. As an example, the emergency vehicle <b>136</b> may have been notified about the accident (e.g., from the fire or police department based upon a x911 call) but was uncertain as to the location of the accident. As soon as the emergency vehicle <b>136</b> locates the accident <b>140</b>, it sends an emergency message to the nearest WIRM <b>102</b>. That WIRM <b>102</b> transmits the emergency message to its next adjacent WIRM and each WIRM passes on the message to the other WIRMS, such as WIRMS <b>104</b> and WIRMS <b>106</b>, such that they turn to or flash red to indicate to drivers that the lane is closed and that an emergency vehicle is approaching. This emergency message <b>209</b> may also be transmitted from the emergency vehicle <b>136</b> or by a WIRM <b>102</b> to the nearest WIRM gateway <b>110</b> and by the WIRM gateway <b>110</b> through wireless link <b>112</b> to the traffic management station <b>120</b> in order to identify the accident, the accident location, as well as the type of accident.
0021As another example, a random vehicle <b>130</b> may see an accident <b>140</b> and either directly call the traffic management station <b>120</b> or the traffic management station may be notified by a vehicle's call to x911 and the traffic management station <b>120</b> via link <b>112</b> may transmit the accident information to a WIRM gateway <b>110</b> and the WIRM gateway <b>110</b> may then transmit the emergency message to a WIRM <b>102</b>. The WIRM <b>102</b> may then in conjunction with all of the other appropriate WIRMS (e.g., WIRMS <b>104</b> and <b>106</b>) communicate emergency messages <b>209</b> to one another to display or flash a red light for a certain pre-defined area to indicate to drivers that they clear the lane because of a traffic accident <b>140</b> and that an emergency vehicle <b>136</b> is approaching. Thus, an emergency message may be transmitted from the traffic management station <b>120</b> via link <b>112</b> to a WIRM gateway <b>110</b> and to the WIRMS <b>102</b>.
0022Turning briefly to <figref idref="DRAWINGS">FIG. 3</figref>, <figref idref="DRAWINGS">FIG. 3</figref> is a block diagram illustrating the components of the WIRM gateway <b>110</b> and the traffic management station <b>120</b> that may be utilized by the wireless emergency system <b>100</b>, according to one embodiment. In one embodiment, WIRM gateway <b>110</b> may include a processor <b>302</b>, memory <b>303</b>, transmitter <b>309</b>, receiver <b>310</b>, and power source <b>312</b>. Transmitter <b>309</b> may transmit emergency messages <b>209</b> via transmitter <b>309</b> to WIRMS <b>102</b>, emergency vehicles <b>136</b>, and to traffic management station <b>120</b> via link <b>112</b>; and may receive emergency messages <b>209</b> via receiver <b>310</b> from WIRMS <b>102</b>, emergency vehicles <b>136</b>, and from the traffic management station <b>120</b> via link <b>112</b>.
0023Further, the traffic management station <b>120</b> may include a server <b>320</b>, a transmitter <b>329</b>, and a receiver <b>330</b>. Traffic management station <b>120</b> may be connected to the Internet <b>122</b> and the public switch telephone network (PSTN) <b>124</b>. The traffic management station <b>120</b> may receive emergency data from callers, vehicles, emergency vehicles, the Internet, or a wide variety of different sources, and may transmit these emergency messages via link <b>112</b> to a WIRM gateway <b>110</b> such that WIRM gateway <b>110</b> can pass on this emergency message data to the WIRMS <b>102</b> regarding such things as vehicle accidents, bad weather, road/lane problems, traffic congestion, closed lane, etc. Additionally, as previously described, traffic management station via receiver <b>330</b> may receive via link <b>112</b> emergency messages from WIRM gateways <b>110</b>.
0024Particular examples will now be described. As one example, the emergency message <b>209</b> may be a “traffic collision” or “closed lane” message. In this instance, the processor <b>202</b> of a WIRM <b>102</b> commands the light emitter to emit a red color <b>220</b> to communicate the “closed lane” message to drivers and the processor <b>202</b> commands the transmitter <b>204</b> to transmit the received “closed lane” emergency message <b>209</b> to the other WIRMS <b>102</b>.
0025A particular previously-described example of this may be a lane <b>109</b> in which a vehicle collision <b>140</b> occurred and some of the WIRMS <b>104</b> and <b>106</b> for a particular pre-defined distance are commanded to emit the red light such that vehicles <b>130</b> are told switch lanes to avoid the vehicle collision <b>140</b> and to allow an emergency vehicle <b>136</b> to obtain quick access to the vehicle collision <b>140</b>. In this instance the emergency message may also be referred to as a “traffic collision” message. Of course other “closed lane” messages may be related to a rock-slide associated with a lane, another type of accident that has occurred in a lane, a dropped item in a lane, etc.
0026As another example, the emergency message <b>209</b> may be a “bad weather” message. In this instance, the processor <b>202</b> of a WIRM <b>102</b> commands the light emitter to emit a yellow color <b>240</b> to communicate the “bad weather” message to drivers and the processor <b>202</b> commands the transmitter <b>204</b> to transmit the received “bad weather” emergency message <b>209</b> to the other WIRMS <b>102</b>. Thus, bad weather conditions such as snow, ice, hail, rain, etc., can be communicated with yellow lights to alert drivers to slow down.
0027As yet another example, the emergency message <b>209</b> may be a “traffic congested” message. In this instance, the processor <b>202</b> of a WIRM <b>102</b> commands the light emitter to emit a yellow color <b>240</b> to communicate the “traffic congested” message to drivers and the processor <b>202</b> commands the transmitter <b>204</b> to transmit the received “traffic congested” emergency message <b>209</b> to the other WIRMS <b>102</b>. Thus, traffic congestion conditions can be communicated with yellow lights to alert drivers to slow down.
0028Therefore, as can be seen in <figref idref="DRAWINGS">FIG. 1</figref>, each of the lanes <b>109</b> may have a corresponding group of WIRMS <b>104</b>, <b>106</b>, <b>108</b>, and <b>110</b> that may be utilized to emit light and flashes (of red and yellow) to warn drivers about vehicle accidents <b>140</b>, bad weather, road/lane problems, traffic congestion, closed lane, etc. Of course, green lights can indicate to drivers that there are no problems currently associated with the lane <b>109</b>.
0029With brief reference to <figref idref="DRAWINGS">FIG. 4</figref>, a flow diagram that illustrates a process <b>400</b> to implement the lighting of WIRMS, as previously described, according to one embodiment, will be described. At block <b>402</b>, an emergency message from an emergency vehicle or a WIRM gateway is received at a WIRM. Next, at block <b>404</b>, the light emitter of a WIRM is commanded to emit a light color (e.g., red, yellow, flashing, etc.) based upon the emergency message received. Further, a transmitter of the WIRM is commanded to transmit the received emergency message to other nearby WIRMS (block <b>406</b>).
0030In particular, if the emergency message is a “close the lane” message (decision block <b>408</b>) then the light emitter emits red (block <b>410</b>). If not, if the emergency message is a “traffic collision” message (decision block <b>412</b>) then the light emitter also emits red (block <b>414</b>). If not, and the emergency message is determined to be a “bad weather” message (decision block <b>420</b>), then the light emitter emits yellow (block <b>422</b>). If not, it is next determined whether the emergency message is a “traffic congested” message (decision block <b>424</b>) and if so, the light emitter emits yellow also (block <b>426</b>). If not, process <b>400</b> ends (block <b>430</b>). Of course, green lights can indicate to drivers that there are no problems currently associated with the lane <b>109</b>.
0031Again, with particular reference to <figref idref="DRAWINGS">FIG. 2</figref>, a WIRM <b>102</b> may include a solar panel <b>212</b> to provide power to the WIRM <b>102</b>. Also, WIRM <b>102</b> may include a sensor <b>210</b>, such as, an optical sensor or a motion vibration sensor, to monitor vehicle traffic such that the processor <b>202</b> may determine whether vehicle traffic is congested, and if so, command the light emitter <b>208</b> to emit a yellow <b>240</b> color, or, if not congested, command the light emitter <b>208</b> to emit a green <b>250</b> color. Further, processor <b>202</b> can command the transmitter <b>204</b> to transmit the monitored vehicle traffic congestion message <b>209</b> to other WIRMS <b>102</b> (such that they can likewise emit yellow to warn drivers of traffic congestion), as well as, through a WIRM gateway <b>110</b> to the traffic management station <b>120</b>. In this way, the traffic management station <b>120</b> can pass the traffic congestion data onto Internet websites and to vehicles themselves such that the traffic congestion is automatically and widely distributed.
0032With reference to <figref idref="DRAWINGS">FIG. 5</figref>, a block diagram showing the complete traffic emergency system <b>500</b>, according to one embodiment, is shown. As can be seen in <figref idref="DRAWINGS">FIG. 5</figref> in addition to <figref idref="DRAWINGS">FIG. 1</figref> and the other figures, emergency vehicles <b>136</b> can correspond via wireless link <b>209</b> to WIRMS <b>102</b> and through wireless link <b>502</b> to WIRM gateways <b>110</b> and the traffic management station <b>120</b>. Further, regular vehicles <b>132</b> may communicate via a wireless link <b>504</b> to the traffic management station <b>120</b>. Additionally, other users, vehicles, etc., can communicate with the traffic management station via the Internet <b>120</b>, the PSTN <b>124</b>, or by other means. For example, a x911 call to a police or fire station (or the information from a call) may be passed on to the traffic management station <b>120</b>. It should be appreciated that vehicles that communicate information not only include on-the-road vehicles but may also include off-the-road vehicles such as helicopters, planes, etc.
0033Additionally, as previously described, WIRMS <b>102</b> may communicate emergency messages <b>209</b> with each other and to the WIRM gateways <b>110</b> and the WIRM gateways <b>110</b> may further communicate with the traffic management station <b>120</b>. Conversely, the traffic management station <b>120</b> may communicate emergency messages via link <b>112</b> to the WIRM gateways <b>110</b> and WIRMS <b>102</b>.
0034Thus, as one example, to implement the WIRM system <b>500</b>, three main components may be utilized: the WIRMS <b>102</b>, WIRM gateways <b>110</b>, and the traffic management station <b>120</b>. As an example, the WIRMS <b>102</b> may communicate with each other utilizing low-power wireless network technology via wireless emergency messages <b>209</b>. The WIRMS <b>102</b> may be self-powering (using solar energy), and this energy may be sufficient to power the LED lights highlighting the location of the WIRMS <b>102</b> to drivers. As previously discussed, the WIRMS <b>102</b> may be remotely instructed to provide a variety of lighting colors, flashes, and/or patterns. Also, as previously described, a WIRM <b>102</b> may have additional capabilities enabling the WIRM <b>102</b> to provide traffic monitoring information to the traffic management station <b>120</b>.
0035Further, the WIRM gateways <b>110</b> may be installed beside the highway. The WIRM gateways <b>110</b> may communicate with the WIRMS <b>102</b> and may communicate with the traffic management station <b>120</b> via WWAN (or other similar technologies). In essence, these devices facilitate communication between the WIRMS <b>102</b> and the traffic management station <b>120</b>. The WIRM gateways <b>110</b> may require more power than a small solar-cell provides such that WIRM gateways, in one embodiment, may utilize a large solar panel such as those used by road-side emergency phones.
0036The traffic management station <b>120</b> may include an appropriate system that includes sufficient hardware and software (e.g. servers, computers, phone lines, etc.) to provide an operations and service center. The traffic management station <b>120</b> in conjunction with the WIRM gateways <b>110</b> may provide instructions to the WIRMS <b>102</b> and also receive data observed by the WIRMS <b>102</b>. The traffic management station <b>120</b> also may provide services to external systems. Examples of such services include providing traffic recommendations to vehicle GPS navigation units or supporting a traffic-monitoring web-site via the Internet <b>122</b>.
0037The WIRMS <b>102</b> provide visual clues to drivers to enhance safety. In order to accomplish this, as previously described, the WIRMS <b>102</b> use lights illuminating in a variety of colors, flashes, and/or patterns. Examples of this may include: green—normal; yellow and/or flashing—slow down or prepare to stop/merge (traffic congestion, accident ahead, bad weather); red—lane closed (e.g. emergency vehicle approaching, bad accident, vehicle collision, road problems). In one example, WIRMS <b>102</b> may be generally placed 20 meters apart and with an appropriate radio range, such as, 75 meters. WIRMS <b>102</b> may communicate with a number of surrounding WIRMS ensuring that the failure of multiple adjacent WIRMS would not affect the entire system.
0038Thus, for traffic conditions affected by accidents, bad weather, road problems (e.g., rock slides), and traffic congestion, the emergency system <b>500</b> utilizing WIRMS <b>102</b> may warn oncoming drivers to slow down or change lanes. Further, emergency vehicles can close lanes to gain access to accident sites. Additionally, by controlling the WIRM system centrally (e.g. utilizing traffic management station <b>120</b>), it may be used for deterring traffic and/or highlighting bad weather conditions. During peak traffic times, special/stadium events, a WIRM system may be used to reconfigure lane direction and divert traffic. Integration with traffic signals could intelligently aid flow. Such a system would be more configurable than current manual approaches. Safety zones including train and pedestrian, school zones, and bike paths may be illuminated when crossing traffic is present. By having the road surface look different when there is a pedestrian/bike/train present, the intersecting traffic will be more noticeable.
0039Additionally, as previously described, when the WIRMS <b>102</b> utilize an optical or motion vibration sensor to monitor vehicle traffic, the WIRM system <b>500</b> may be used more accurately than existing traffic analysis systems and may be used for GOOGLE MAPS and/or an Internet-based government style traffic congestion reporting system. The accurate flow information may be fed into car systems as well to dynamically update the fastest route to a destination. In another embodiment, drivers may be able get automated road conditions (weather, traffic flow), accident alerts, alternate routes, emergency vehicles nearby, pedestrians and crosswalks, bikes and bike lanes, etc. There are further features that could be implemented utilizing WIRMS <b>102</b>. For example, WIRMS <b>102</b> could have capabilities (sensors) for feeding traffic, road, and weather conditions back to the traffic management station <b>120</b> via the WIRM gateway <b>110</b> or a direct link <b>502</b>. Also, in another embodiment, WIRMS <b>102</b> could transmit messages to vehicles and systems in the vehicles to act on such as signals that automatically brake the vehicle due to an upcoming close accident or automatically display to the user a warning that a traffic accident, bad weather, a rock slide etc., is very close (e.g., in one-half mile a bad traffic accident occurred).
0040The WIRM based system <b>500</b> may also be used to monitor traffic congestion, oncoming traffic speed, and warn traffic to break in slow or spotted traffic conditions such as accidents, bad weather, and congestion. Emergency vehicles <b>136</b> could be used to close lanes to gain access. By controlling the WIRM system centrally such as via a traffic management station <b>120</b>, the WIRM system could be used for deterring traffic and highlighting bad weather conditions. During peak traffic times, special/stadium events, a WIRM system could be used to reconfigure lane direction and divert traffic. Integration with traffic signals could intelligently aid flow. Such a system may be more configurable than current manual approaches. Further, safety zones including train and pedestrian, school zones and bike paths may likewise be illuminated utilizing WIRMS <b>102</b> when crossing traffic is present. By having the road surface look different when there is a pedestrian/bike/train present, the intersecting traffic may be more noticeable. Further, the WIRM system could be used to monitor erratic driving, speeding and also could be combined with cameras to identify potential perpetrators. Such systems could also be used to track stolen vehicles and missing people. For example, WIRMS <b>102</b> could include cameras and these cameras could be utilized to identify cars by photographing license plates and employing optical character recognition algorithms.
0041Thus, the WIRM based system <b>500</b> may implement huge improvements in maximizing freeway safety and control. For example, the WIRM based system <b>500</b> utilizing the WIRMS <b>102</b> coloring may implement traffic control flow in terms of regular lane traffic and transit lane traffic during peak times. As an example, a 4×4 lane highway could be reconfigured for 1 incoming, and 7 outgoing lanes. Additionally, the WIRMS <b>102</b> can monitor traffic in lanes, in case of emergencies, e.g., a vehicle accidently gets in the wrong lane. Further, as previously described, the WIRM based system <b>500</b> can configure lanes for stadiums and special events and can be integrated with traffic lights to allow for more intelligent traffic flow. The WIRM based system <b>500</b> can establish safety zones such the WIRMs <b>102</b> can illuminate surrounding lanes and roads when there is a situation that warrants attention, such as, when there is a pedestrian/bike/train present. For example, bike lanes could illuminate behind a cyclist to inform approaching traffic. Also, school zones could be highlighted during school hours. Additionally, the WIRMS <b>102</b>, much like accident warning, could determine car speed and be integrated with traffic lights/crossings to indicate braking required, especially where intersection is around a blind corner.
0042Further, the WIRM based system <b>500</b> utilizing WIRMS <b>102</b> may implement traffic monitoring and diversion, such as: re-routing traffic in an emergency situation by closing lanes and changing lane direction and highlighting detours for emergency and roadwork including weather issues such as flooded or icy roads. WIRM based system <b>500</b> may be useful in accident analysis, such as, the WIRMS <b>102</b> monitoring speed and braking activities to help determine accident fault. Additionally, WIRM based system <b>500</b> may provide very accurate traffic monitoring that can be performed with sensors in the WIRMS <b>102</b> rather than the current very low-resolution system of sensors on freeway exists. This information can then be transmitted back to the traffic management station <b>120</b> for implementation with systems such as GOOGLE MAPS TRAFFIC and Internet-based government systems. Additionally, displays could be integrated into side-of-the-road displays to indicate traffic conditions including items such as “Time to LAX: 22 minutes”. These would be far more accurate than existing systems. In-car navigation systems could utilize the live traffic monitoring information from the WIRMS <b>102</b> to map the fastest route to a destination. In-car systems could display time-to-destination information retrieved from the WIRM based system <b>500</b> via a web interface, or directly from the WIRMS <b>102</b>.
0043Moreover, the WIRM based system <b>500</b> utilizing WIRMS <b>102</b> may implement vehicle monitoring by cameras in the WIRMS <b>102</b> and WIRM gateway <b>110</b> to monitor for speeding and erratic drivers; drunk drivers; drivers veering within lanes. Additionally, the WIRM based system <b>500</b> may be integrated with stolen vehicle tracking systems and can be used in child abduction and missing person tracking. Vehicles may also interact with the WIRM based system. For example, autonomous cruise control systems could interact with the WIRMS to determine upcoming conditions and act accordingly. As an example, a vehicle could be commanded to brake to a complete halt in ½ mile due to a rock slide. These types of information could be displayed in a vehicle's heads-up-display. This could be particularly useful in low visibility situations such as fog, snow and heavy rain.
0044The WIRM system may also allow for more advanced functionality including autonomous cruise control systems that interact with road surface and automatically control the car. Another advanced system would be in-car heads-up display on the road surface. This could be useful in low visibility situations.
0045Additionally, an embodiment is presented that provides a procedure to determine the location coordinates for WIRMS <b>102</b> and WIRM gateways <b>110</b>. Hereinafter the term “node” refers to WIRM. In particular, the hereinafter described procedure relates to determining location coordinates for the self-organizing WIRM system using short-range wireless transfer.
0046This procedure explains how to calculate absolute location coordinates for nodes in a mesh network using short-range wireless transfer. Here, the location coordinates are tuples (X, Y, Z) representing GPS positions (latitude, longitude, altitude).
0047A node represents an intelligent WIRM, a device that uses short-range wireless transfer to communicate with other nodes. A gateway node is more powerful and can communicate over larger distances. It also contains a wired-link to a network and knows its own GPS position.
0048A local node of n<sub>i </sub>is a node that is within range of wireless communication. A node n<sub>i </sub>uses short-range wireless transfer to discover the distance to each local node. The information gathered by each node is relayed back to a gateway node for processing.
0049The gateway node builds a multivariate quadratic system of equations using the information received. This system of equations can generally be solved using standard algorithms to find a unique solution, provided there are a sufficient number of equations in comparison to the number of variables. Solving these types of systems becomes less complex if the system is over-defined (number of equations>number of variables).
0050Two Dimensions
0051Assumption 1: Each node is local to at least 2 other nodes.
0052Assumption 2: Each gateway-node is local to at least 2 other nodes.
0053Let (X<sub>i</sub>, Y<sub>i</sub>) denote the absolute coordinates of node n<sub>i</sub>. The distance d<sub>ij </sub>between two nodes n<sub>i </sub>and n<sub>j </sub>can be expressed as:
0000<br />(<i>X</i><sub>i</sub><i>−X</i><sub>j</sub>)<sup>2</sup>+(<i>Y</i><sub>i</sub><i>−Y</i><sub>j</sub>)<sup>2</sup><i>=d</i><sub>ij</sub><sup>2</sup>.
0054For each node, there are 2 unknown variables (X<sub>i</sub>, Y<sub>i</sub>). For a system of n nodes, this gives 2n variables. For each node-node distance discovered, there is 1 equation in 4 variables. For each node-gateway distance discovered, there is 1 equation in 2 variables (since the gateway coordinates are known).
0055If assumption 1 holds, the number of node-node equations is at least 2n−3 in 2n variables. Each gateway-node introduces at least 2 more equations with no additional variables. For a system including 4 gateway-nodes, there are at least 2n+5 equations in 2n variables.
0056Three Dimensions
0057Assumption 1: Each node is local to at least 3 other nodes.
0058Assumption 2: Each gateway-node is local to at least 3 other nodes.
0059Let (X<sub>i</sub>, Y<sub>i</sub>, Z<sub>i</sub>) denote the absolute coordinates of node n<sub>i</sub>. The distance d<sub>ij </sub>between two nodes n<sub>i </sub>and n<sub>j </sub>can be expressed as:
0000<br />(<i>X</i><sub>i</sub><i>−X</i><sub>j</sub>)<sup>2</sup>+(<i>Y</i><sub>i</sub><i>−Y</i><sub>j</sub>)<sup>2</sup>+(<i>Z</i><sub>i</sub><i>−Z</i><sub>j</sub>)=<i>d</i><sub>ij</sub><sup>2</sup>.
0060For each node, there are 3 unknown variables (X<sub>i</sub>, Y<sub>i</sub>, Z<sub>i</sub>). For a system of n nodes, this gives 3n variables. For each node-node distance discovered, there is 1 equation in 6 variables. For each node-gateway distance discovered, there is 1 equation in 3 variables (since the gateway coordinates are known).
0061If assumption 1 holds, the number of node-node equations is at least 3n−3 in 3n variables. Each gateway-node introduces at least 3 more equations with no additional variables. For a system including 4 gateway-nodes, there are at least 3n+9 equations in 3n variables.
0062It should be appreciated that embodiments of the invention previously described may be implemented in conjunction with the execution of instructions by processors (e.g., processors of the WIRMs <b>102</b>, WIRM gateways <b>110</b>, and the traffic management station <b>120</b>) and/or other circuitry and/or other devices. Particularly, this circuitry, including but not limited to processors, may operate under the control of a program, routine, or the execution of instructions to execute methods or processes in accordance with embodiments of the invention. For example, such a program may be implemented in firmware or software (e.g. stored in memory and/or other locations) and may be implemented by processors and/or other circuitry. Further, it should be appreciated that the terms processor, microprocessor, circuitry, controller, etc., refer to any type of logic or circuitry capable of executing logic, commands, instructions, software, firmware, functionality, etc.
0063Further, the WIRMs <b>102</b>, WIRM gateways <b>110</b>, and the traffic management station <b>120</b> may communicate via one or more wireless communication links that are based on or otherwise support any suitable wireless communication technology. For example, in some aspects a wireless device may associate with a network. In some aspects the network may comprise a body area network or a personal area network (e.g., an ultra-wideband network). In some aspects the network may comprise a local area network or a wide area network. A wireless device may support or otherwise use one or more of a variety of wireless communication technologies, protocols, or standards such as, for example, CDMA, TDMA, OFDM, OFDMA, WiMAX, and Wi-Fi. Similarly, a wireless device may support or otherwise use one or more of a variety of corresponding modulation or multiplexing schemes. A wireless device may thus include appropriate components (e.g., air interfaces) to establish and communicate via one or more wireless communication links using the above or other wireless communication technologies. For example, a device may comprise a wireless transceiver with associated transmitter and receiver components (e.g., a transmitter and a receiver) that may include various components (e.g., signal generators and signal processors) that facilitate communication over a wireless medium. As is well known, a wireless devices may therefore wirelessly communicate with other mobile devices, cell phones, other wired and wireless computers, Internet web-sites, etc.
0064The teachings herein may be incorporated into (e.g., implemented within or performed by) a variety of apparatuses (e.g., devices). For example, one or more aspects taught herein may be incorporated into a phone (e.g., a cellular phone), a personal data assistant (“PDA”), an entertainment device (e.g., a music or video device), a headset (e.g., headphones, an earpiece, etc.), a microphone, a medical device (e.g., a biometric sensor, a heart rate monitor, a pedometer, an EKG device, etc.), a user I/O device (e.g., a watch, a remote control, a light switch, a keyboard, a mouse, etc.), a tire pressure monitor, a computer, a point-of-sale device, an entertainment device, a hearing aid, a set-top box, or any other suitable device.
0065These devices may have different power and data requirements. In some aspects, the teachings herein may be adapted for use in low power applications (e.g., through the use of an impulse-based signaling scheme and low duty cycle modes) and may support a variety of data rates including relatively high data rates (e.g., through the use of high-bandwidth pulses).
0066In some aspects a wireless device may comprise an access device (e.g., a Wi-Fi access point) for a communication system. Such an access device (also referred to as a base station) may provide, for example, connectivity to another network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Accordingly, the access device may enable another device (e.g., a Wi-Fi station) to access the other network or some other functionality. In addition, it should be appreciated that one or both of the devices may be portable or, in some cases, relatively non-portable.
0067Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
0068Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
0069The various illustrative logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
0070The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
0071In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software as a computer program product, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
0072The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Contents4
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9976265B2 | Cited by | United States of America | Applicant |
| WO2021142397A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2018181094A1 | Cited by | United States of America | Search report |
| US12013944B2 | Cited by | United States of America | Applicant |
| US11698186B2 | Cited by | United States of America | Applicant |
| US10623162B2 | Cited by | United States of America | Applicant |
| WO2020074919A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US12277845B2 | Cited by | United States of America | Applicant |
| US9776632B2 | Cited by | United States of America | Applicant |
| US8704676B2 | Cited by | United States of America | Applicant |
| US10235880B2 | Cited by | United States of America | Search report |
| US2018181091A1 | Cited by | United States of America | Search report |
| US11769418B2 | Cited by | United States of America | Applicant |
| US11075894B2 | Cited by | United States of America | Applicant |
| US10838383B2 | Cited by | United States of America | Applicant |
| US10911544B2 | Cited by | United States of America | Applicant |
| US11725785B2 | Cited by | United States of America | Applicant |
| US2012146812A1 | Cited by | United States of America | Pre-grant |
| US10627794B2 | Cited by | United States of America | Applicant |
| US11941120B2 | Cited by | United States of America | Applicant |
| US10749275B2 | Cited by | United States of America | Applicant |
| US2024135810A1 | Cited by | United States of America | Search report |
| US2016366543A1 | Cited by | United States of America | Pre-grant |
| US11014575B2 | Cited by | United States of America | Search report |
| US10281914B2 | Cited by | United States of America | Applicant |
| US11706861B2 | Cited by | United States of America | Applicant |
| US2018357895A1 | Cited by | United States of America | Search report |
| US11794789B2 | Cited by | United States of America | Applicant |
| CN108431879A | Cited by | China | Search report |
| US10412172B2 | Cited by | United States of America | Applicant |
| US10919523B2 | Cited by | United States of America | Applicant |
| US9598078B2 | Cited by | United States of America | Applicant |
| US11295625B2 | Cited by | United States of America | Applicant |
| US10700411B2 | Cited by | United States of America | Applicant |
| US10629980B2 | Cited by | United States of America | Applicant |
| US10959158B2 | Cited by | United States of America | Search report |
| US10637683B2 | Cited by | United States of America | Search report |
| FR3059132A1 | Cited by | France | Search report |
| US10426358B2 | Cited by | United States of America | Applicant |
| JP2017530462A | Cited by | Japan | Search report |
| US10972543B2 | Cited by | United States of America | Applicant |
| US12385196B2 | Cited by | United States of America | Applicant |
| US11755012B2 | Cited by | United States of America | Applicant |
| US10276921B2 | Cited by | United States of America | Applicant |
| US8855900B2 | Cited by | United States of America | Search report |
| US10249103B2 | Cited by | United States of America | Applicant |
| US11658953B2 | Cited by | United States of America | Applicant |
| US2014070962A1 | Cited by | United States of America | Pre-grant |
| US2019197892A1 | Cited by | United States of America | Search report |
| US11249483B2 | Cited by | United States of America | Search report |
| US9807850B1 | Cited by | United States of America | Search report |
| US10735220B2 | Cited by | United States of America | Applicant |
| US11138879B2 | Cited by | United States of America | Search report |
| US2017169706A1 | Cited by | United States of America | Pre-grant |
| US2013013179A1 | Cited by | United States of America | Pre-grant |
| US10892543B2 | Cited by | United States of America | Applicant |
| US10651883B2 | Cited by | United States of America | Applicant |
| US10607482B2 | Cited by | United States of America | Search report |
| US10375172B2 | Cited by | United States of America | Applicant |
| WO2016039913A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2016321923A1 | Cited by | United States of America | Pre-grant |
| US2016366543A1 | Cited by | United States of America | Search report |
| CN106575472A | Cited by | China | Search report |
| US9349293B2 | Cited by | United States of America | Search report |
| US9111447B2 | Cited by | United States of America | Search report |
| US2018181091A1 | Cited by | United States of America | Search report |
| US12203637B2 | Cited by | United States of America | Applicant |
| JP2017530462A | Cited by | Japan | Search report |
| WO2019161437A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8595037B1 | Cited by | United States of America | Search report |
| US11991158B2 | Cited by | United States of America | Applicant |
| WO2023023825A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11232203B2 | Cited by | United States of America | Applicant |
| US10832665B2 | Cited by | United States of America | Applicant |
| US9076339B2 | Cited by | United States of America | Applicant |
| US10687377B2 | Cited by | United States of America | Applicant |
| US2021394776A1 | Cited by | United States of America | Search report |
| US9953526B2 | Cited by | United States of America | Search report |
| EP3398182A1 | Cited by | European Patent Office (EPO) | Examiner |
| US10222773B2 | Cited by | United States of America | Applicant |
| US11989295B2 | Cited by | United States of America | Applicant |
| US11128987B2 | Cited by | United States of America | Applicant |
| WO2025153546A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2020152059A1 | Cited by | United States of America | Search report |
| US2003063015A1 | Cites | United States of America | Pre-grant |
| US2004127231A1 | Cites | United States of America | Pre-grant |
| US2005270175A1 | Cites | United States of America | Pre-grant |
| US2006193691A1 | Cites | United States of America | Pre-grant |
| US2007124306A1 | Cites | United States of America | Pre-grant |
| US2007211463A1 | Cites | United States of America | Pre-grant |
| US2007213088A1 | Cites | United States of America | Pre-grant |
| US2009009089A1 | Cites | United States of America | Pre-grant |
| US2010156668A1 | Cites | United States of America | Pre-grant |
| US2010201267A1 | Cites | United States of America | Pre-grant |
| US2011006912A1 | Cites | United States of America | Pre-grant |
| US2011068950A1 | Cites | United States of America | Pre-grant |
| US2011084854A1 | Cites | United States of America | Pre-grant |
| US2011153742A1 | Cites | United States of America | Pre-grant |
| US2011199231A1 | Cites | United States of America | Pre-grant |
| US2012194353A1 | Cites | United States of America | Pre-grant |
2 members in 2 offices; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 201113076227 | United States of America | A | |
| US201113076227 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2012249341A1 | United States of America | A1 | |
| WO2012135687A1 | World Intellectual Property Organization (WIPO) | A1 |
66 transactions on the USPTO file
Abandoned after 2 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Mail Abandonment for Failure to Pay Issue FeeAbandonedMABN6 | MABN6 | |
| Abandonment for Failure to Pay Issue FeeAbandonedABN6 | ABN6 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Rule 47 / 48 Correction of Inventorship Papers FiledRU47 | RU47 | |
| Affidavit(s) (Rule 131 or 132) or Exhibit(s) ReceivedAF/D | AF/D | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Sent to Classification ContractorPGPC | PGPC | |
| Cleared by L&R (LARS)L128 | L128 | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
3 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO PAY ISSUE FEESTCB | STCB | |
| Information on status: application discontinuationABANDONED -- FAILURE TO PAY ISSUE FEESTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication
- 20120249341
- Publication, DOCDB
- 2012249341
- Publication, EPODOC
- US2012249341
- Application
- 13076227
- Application, DOCDB
- 201113076227
- Application, EPODOC
- US201113076227
Titles
- English
- Communication of emergency messages with road markers
Classification
- CPC, 6
- G08G1/0104
- G08G1/095
- G08G1/096716
- G08G1/096758
- G08G1/096775
- E01F9/559
- IPC, 1
- G08G1 00
- USPC, 1
- 340902000