Patent Description:
Traffic flow information and pattern regulation are useful tools for informing motorists of congestion, hazards, accidents, police or highway safety personnel activity, and the like.

Some traffic flow and pattern control apparatus may be deployed in construction zones, for example, or in areas such as freeway interchanges or toll plazas where traffic congestion is regular or frequent, or in areas requiring temporary rerouting of vehicular traffic. In that regard, many such traffic flow and pattern control apparatus are designed to be portable, or at least moveable (i.e., they may not be permanently affixed to or integrated into the roadway or other immovable infrastructure).

Additionally, some traffic monitoring systems (such as those provided by Signalisation Ver-Mac™ Inc. ) acquire and transmit traffic flow data to a remote system which processes data for use in connection with one or more applications. A typical traffic flow monitoring and regulation system may, for example, update road-side or overhead signage with information concerning traffic patterns that a motorist may expect to encounter some distance ahead. Additionally or alternatively, such traffic data may be provided to third party mapping and navigation tools, providing a user of such a tool with real-time or near real-time information concerning traffic conditions where they are being monitored. In connection with these and other systems, it may be useful to identify the location of each traffic flow and pattern control apparatus placed on or near the route being monitored or controlled.

Installation of permanent or long-term traffic sensors is a relatively complicated task, involving wiring, installation of communications equipment, and providing solid anchorage or a permanent support structure. On the other hand, since the equipment is permanent or deployed for an extended period, power consumption is usually not a limiting factor for the equipment utilized, as the powered sensor components are either connected to a local utility power grid or accompanied by a government or commercial generator.

The challenges associated with providing temporary or portable traffic sensors and other flow and pattern control apparatus are very different from those associated with deploying permanent or long term fixtures. Applications for these portable apparatus include construction sites, warning of speed limit changes, lane or road closures, and temporary flagging or road hazards such as rock slides, bridge damage, lighting failures, traffic collisions, law enforcement activity, and the like. It is often desirable that a portable traffic apparatus be light-weight but sturdy, easily moveable to a suitable location, visible to motorists to prevent damage or destruction, and self-powered, since a portable device may not always be positioned such that it may readily be wired to electric utility services. Portability may be desirable for many applications, as investment in a permanent physical infrastructure is not required and because a traffic apparatus may quickly and selectively be deployed only where it is needed. As noted above, however, portable structures may be moved, and so it may be useful in many applications to acquire and to maintain accurate location information for each such apparatus that is deployed.

Therefore, there is a need for an improved system and method of acquiring and maintaining location information associated with such apparatus in connection with a traffic flow monitoring or regulation system. <CIT> discloses a signage unit which transmits a key to a mobile device. A road works operative can upload GPS information within an input text section on the mobile device. <CIT> discloses a roadside marker which can transmit a signal to a remote location. <CIT> discloses a device, a system, and a method for monitoring a road sign.

A method of acquiring and maintaining location information associated with a traffic apparatus is defined in the claims.

Optionally, the beacon system is operative to broadcast the apparatus data periodically at a frequency.

Optionally, the capturing is responsive to a peak signal strength.

Optionally, the deriving comprises utilizing the apparatus data.

Optionally, the beacon system is operative to broadcast the apparatus data responsive to a proximity of the remote device.

Optionally, the deriving comprises utilizing positioning data resident on the remote device.

The apparatus data may include a unique apparatus identifier.

The method further comprises transmitting the apparatus data from the remote device to a computer processing system.

Optionally, the deriving may comprise utilizing the computer processing system.

Additionally or alternatively, the recording may comprise utilizing the computer processing system.

The method may optionally further comprise transmitting the location data from the computer processing system to a third party platform.

In accordance with another aspect of the invention, a traffic apparatus location system is defined in the claims.

Optionally, the location data are included in the apparatus data broadcast by the beacon system.

The beacon system may optionally be operative to broadcast the apparatus data periodically at a frequency.

Additionally or alternatively, the beacon system may be operative to broadcast the apparatus data responsive to a proximity of the remote device.

Optionally, the location data may be derived based on a location of the remote device.

The location data may be derived by the remote device, or the location data may be derived by the computer processing system.

Optionally, the apparatus data include a unique apparatus identifier.

Optionally, the remote device is a wireless telephone and in others, the remote device is a tablet computer.

Optionally, the beacon system comprises a wireless transceiver and is configured and operative to initiate the broadcast responsive to a signal from the remote device.

The beacon system may optionally comprise one of a global positioning system sensor, a gyroscope, an altimeter, a compass, and an accelerometer.

Optionally, the computer processing system is operative to transmit the location data to a third party platform.

The foregoing and other aspects of various disclosed embodiments will be apparent through examination of the following detailed description thereof in conjunction with the accompanying drawing figures, in which like reference numerals are used to represent like components throughout, unless otherwise noted.

Certain aspects and features of the disclosed subject matter may be further understood with reference to the following description and the appended drawing figures. In operation, a system and method of acquiring and maintaining traffic apparatus location information in connection with a traffic flow monitoring and regulation system may transmit information regarding the purpose and location of a traffic apparatus to a remote server or computer system. Specifically, the present disclosure provides for a power efficient traffic apparatus data collecting system which acquires and maintains location and functionality data associated with traffic apparatus employed in the field, and transmits those data to a remote or distant computer server or computing platform such as, for instance, those associated with smart work or construction zones or other traffic management systems or platforms.

Those of skill in the art will appreciate that, to accommodate or to maximize portability, a traffic flow data collection strategy such as described below may effectuate communications with a remote computer system via any of various wireless technologies such as wireless fidelity (WiFi) protocols, satellite or cellular communications standards, and the like. The present disclosure is not intended to be limited by the nature or functional characteristics of the communications hardware or signaling methodologies used to enable the disclosed traffic apparatus to communicate apparatus data to a remote computer system, nor is it intended to be limited by the purpose or operation of the remote computer system itself.

Turning now to the drawing figures, <FIG> illustrates a variety of traffic flow and pattern control apparatus to which the disclosed subject matter pertains, and <FIG> is an elevation view of a traffic flow and pattern control apparatus modified for use in connection with the disclosed subject matter. <FIG> depicts various types of traffic apparatus <NUM> that are familiar to most motorists: drums; delineators; cones; flashers; fixed signs or placards (such as "Road Work," "Merge Left Ahead," "Road Closed," "Detour," and "Traffic Signal Ahead" signs); and variable or selectively programmable lighted signs. It will be appreciated that numerous other signs and structures are used in the art or may be developed that may have utility in connection with traffic control applications, and that the present disclosure is not intended to be limited to any particular subset of traffic signage or traffic flow devices. In that regard, in the context of the present disclosure, the terms "traffic flow and pattern control apparatus" and "traffic apparatus" are intended to encompass each of the traffic apparatus <NUM> illustrated in <FIG> as well as other signs, devices, structures, and informative instruments used to signal or to alert vehicular traffic to road conditions, speed limits or hazards, or to provide other information, as is generally known in the art. Examples of such traffic apparatus for use in Canada and the United States may be found, for example, in the Manual on Uniform Traffic Control Devices (the "MUTCD") or in other analogous or counterpart publications in other jurisdictions.

For example, traffic apparatus <NUM> may be implemented as a barricade or other freestanding road-side structure that is light-weight, readily portable, and crash-certified. In that regard, it is noted that many governmental bodies or highway safety organizations require a safety or crash certification before a traffic apparatus <NUM> may be deployed road-side or near traffic patterns, even in emergency scenarios. Accordingly, those of skill in the art will appreciate that design aspects of commercial embodiments of traffic apparatus <NUM> may be implemented as a function of local, state, or federal statutes or applicable regulations. The present disclosure is not intended to be limited to any particular implementation of the hardware components, materials, or communications protocols illustrated and described with reference to the drawing figures to the extent that any of these elements may be influenced or directed by statute or regulation or other design considerations.

Traffic apparatus <NUM>, in any of its various embodiments, may be constructed of a variety of materials generally known in the art having suitable strength, weight, weather durability, and ultraviolet (UV) light resistant characteristics. Examples include plastics, polyvinyl chloride (PVC), painted, coated, or weather-treated metals such as stainless steel, aluminum, and suitably weather-resistant alloys, ceramics, and other moldable or formable materials that have utility in outdoor and inclement weather applications. The present disclosure is not intended to be limited by the materials or structural configuration of traffic apparatus <NUM>, though an intended functionality of a particular traffic apparatus <NUM> may influence the instant system and method as set forth below. By way of example only, and not by way of limitation, a signage embodiment of traffic apparatus <NUM> is depicted in <FIG> (i.e., "Merge Left").

As set forth below, traffic apparatus <NUM> may generally include a beacon system <NUM>, which may be mounted, affixed, or otherwise attached to or integrated into a structural element of traffic apparatus <NUM>, which as noted above, may be embodied in or comprise a barrel or impact absorbing cylinder, a sign (as in <FIG>), a cone, a barricade, a flasher, or other device. In some embodiments, some powered components of traffic apparatus <NUM> (such as a flasher or lighted elements) may receive electrical power from a solar panel, a small windmill deployed on traffic apparatus <NUM> or proximate thereto, a battery source, or a combination of these and other power sources. Standard, wired electrical service may be appropriate in some instances; for example, a nearby truck or trailer supporting an electric generator may be employed to power electrical components of traffic apparatus <NUM>, though to maximize portability, wireless or fully integrated power sources (such as photovoltaic (PV) panels or battery packs) may be used. As set forth below, traffic apparatus <NUM> may be so constructed and dimensioned as to render it sufficiently light-weight to be easily movable by a single person. Irrespective of power supplies to other components of traffic apparatus <NUM>, in some embodiments, beacon system <NUM> may be battery powered and so configured to conserve power as set forth in more detail below.

<FIG> is a high-level functional schematic diagram of an embodiment of a beacon system to be used in connection with a traffic flow and pattern control apparatus. As noted above, traffic apparatus <NUM> may generally comprise a beacon system <NUM> integrated with or attached to a suitable structural element as a function of the overall design and structural configuration of traffic apparatus <NUM>. In that regard, it will be appreciated that any of various mechanical fastening elements (such as rivets, nuts and bolts, screws, clips or clamps, hook and loop fasteners, etc.), adhesives, welding or brazing techniques, and other coupling techniques or structures may be employed to affix beacon system <NUM> to a structural element or portion of traffic apparatus <NUM>.

In an implementation, beacon system <NUM> generally comprises a wireless transmitter <NUM>, such as a transmitter operative in accordance with Bluetooth™, WiFi, or a suitable near field communication (NFC) telecommunications standard. In operation, beacon system <NUM>, via transmitter <NUM>, may transmit certain information (such as GPS or other location data as well as identification data associated with the nature or operational characteristics of traffic apparatus <NUM>) to a remote device (depicted in <FIG> as a wireless telephone identified by reference numeral <NUM>). In that regard, beacon system <NUM> may also comprise a memory <NUM> that may store data associated with the functionality or intended purpose of traffic apparatus <NUM>. In certain implementations in which memory <NUM> may be selectively reprogrammable, beacon system <NUM> may also include a wireless transceiver or suitable wired hardware interface (not shown), such as a universal serial bus (USB), DockPort jack, or other suitable data interface to allow data transfer to memory <NUM>, enabling definition of the operability and functional characteristics of beacon system <NUM>, and thereby, of traffic apparatus <NUM>.

By way of example, memory <NUM> may maintain data associated with the specific traffic apparatus <NUM> ("apparatus data") to which beacon system <NUM> is affixed or attached. Such apparatus data may include a serial number, apparatus code, or other identifier that may have utility in enabling a system operator or administrator to identify or to distinguish a unique traffic apparatus <NUM> from a plurality of same that are deployed in a particular traffic control application. Additionally or alternatively, such apparatus data may include a code, a series of bits or data words, or other indicator sufficient to identify the type or operational characteristics of traffic apparatus <NUM> in a particular application. In particular, such a code or identifier stored in memory <NUM> may identify the traffic apparatus <NUM> to which beacon system <NUM> is attached as a cone, a barrel, a barricade, or a sign (<FIG>); more particularly, such a code or identifier may further classify traffic apparatus <NUM> in accordance with the information, if any, provided to nearby motorists. For example, apparatus data may be used to characterize a sign as conveying particular information, such as "<NUM> MPH Zone," "Merge Left Ahead" (<FIG>), "Yield," "Detour Left," and the like. In that regard, each of the various traffic apparatus <NUM> illustrated in <FIG> may have a unique code or identifier to specify its function and to distinguish that function from others. Additionally, as noted above, another code or identifier may distinguish each individual traffic apparatus <NUM> from others having like functionality.

In some implementations, memory <NUM> may be pre-coded for a particular purpose such that apparatus data for beacon system <NUM> is predetermined when memory <NUM> is initialized with data. In such situations, however, care must be taken by a system operator or administrator to ensure that a beacon system <NUM> pre-configured to operate in connection with a particular type of traffic apparatus <NUM> is properly affixed to a respective cone, barricade, sign, or placard, for instance, or the system in which that traffic apparatus <NUM> is deployed may record and maintain inaccurate data regarding the deployed arrangement of traffic apparatus <NUM>. Additionally or alternatively, memory <NUM> may be selectively reprogrammed or rewritten such that beacon system <NUM> may be selectively programmable, for example, as a function of the type and nature of the traffic apparatus <NUM> to which it is affixed or attached. In this flexible embodiment, as noted above, memory <NUM> may be programmed wirelessly, for example, or via a USB, DockPort, or other wired communication interface such that apparatus data stored in memory <NUM> accurately reflect the nature and operational characteristics of the traffic apparatus <NUM> to which beacon system <NUM> is affixed. In another embodiment, memory <NUM> may be selectively programmed via a rocker panel, switch, or dial (not illustrated), for instance, such that beacon system <NUM> may be programmed to one of several functionalities in accordance with switch or dial position. For example, placing a rocker panel or toggle switch in the left position may program memory <NUM> to characterize beacon system <NUM> as a "Merge Left" indicator, while placing the rocker panel or toggle switch in the right position may program memory <NUM> to characterize beacon system <NUM> as a "Merge Right" indicator. Those of skill in the art will appreciate that memory <NUM> may be programmed or selectively reprogrammed in any of various ways that are generally known in the art or developed in accordance with known principles and operational characteristics of memory <NUM>, enabling flexibility and efficiency for traffic administrator work flow when employing beacon system <NUM> in connection with a desired type of traffic apparatus <NUM>.

It will be appreciated that memory <NUM> may be embodied in or comprise read only memory (ROM), electrically erasable programmable read-only memory (EEPROM) or other types of "flash" memory, any of various types of random access memory (RAM), or other solid-state memory device as a design choice, and generally selected as a function of power consumption, reliability, memory capacity, mean read/write cycles to failure, or a combination of these and other factors. The present disclosure is not intended to be limited by the specific implementation or technologies employed in connection with memory <NUM>.

As indicated in <FIG>, beacon system <NUM> may also comprise any of a number of different types of sensors <NUM>. Sensors <NUM> may include gyroscopes, altimeters, compasses, accelerometers, GPS or other motion or positioning sensors, for example, having utility in locating and discovering the orientation of apparatus <NUM> in two- or three-dimensional space. In some implementations, it may be useful to communicate signals from sensors <NUM>, via transmitter <NUM>, to a remote system or processing platform such as device <NUM>. In some embodiments, particularly those transmitting apparatus data in real-time or near real-time, data from sensors <NUM> may identify positioning, for instance, as well as acceleration or motion that may be indicative of a traffic apparatus <NUM> that has been moved since a previous data transmission. Comparison of successive compass data points, for example, may indicate expected, or unexpected (and therefore, undesirable), rotation of a traffic apparatus <NUM>.

In the <FIG> implementation, data acquired by sensors <NUM> and data from memory <NUM> may be combined, concatenated, multiplexed, or otherwise aggregated for transmission by transmitter <NUM> (as indicated by aggregate data stream <NUM>), though it may also be desirable that memory <NUM> or one or more sensors <NUM> provide apparatus data for transmission by transmitter <NUM> individually (i.e., in discrete or separate data streams). Accordingly, the present disclosure is not intended to be limited by the particular data flow illustrated in <FIG>, and it is noted that the data structure and the manner in which apparatus data are provided to transmitter <NUM> for transmission are susceptible of numerous variations and modifications depending, for example, on the bandwidth of transmitter <NUM>, the type and amount of apparatus data to be provided, power consumption limitations or requirements, or a combination of these and other factors. For example, it will be appreciated that a microprocessor, a microcontroller, a programmable logic controller (PLC), or other suitable data processing element may facilitate combination, aggregation, multiplexing, or other processing or pre-processing of data at beacon system <NUM>, as illustrated at reference numeral <NUM>, though alternatives may readily be implemented within the scope and contemplation of the disclosed subject matter.

In operation, one or more battery cells (reference numeral <NUM>) may be used to provide operational power to the components of beacon system <NUM>, and in particular, when and if required. As is generally known, such battery cells may employ nickel cadmium, nickel metal hydride, lithium ion, or other rechargeable or single-use battery cell chemistries or technologies that are generally known or developed according to known principals. In some embodiments, power control circuitry may be used to monitor and to regulate charge and discharge cycles for such battery cells, and to minimize or reduce battery consumption; power control circuitry may comprise or incorporate a microcontroller, a PLC, or other data processing element as is generally known.

Though not specifically illustrated in <FIG>, it is noted that beacon system <NUM> may generally employ a housing or other structure that is suitably weather and element resistant to protect components <NUM>, <NUM>, and <NUM> from environmental damage, and that the materials, shock-proofing, ultraviolet resistance, and other characteristics of such a housing may be selected as a function of the sensitivities of those components, including memory <NUM>. For example, the housing may be suitably water, weather, and ultraviolet resistant to protect beacon system <NUM> components from the elements, dust and road debris, salt, and the like, such as are frequently encountered in road-side, all-weather traffic monitoring and control applications.

In use, beacon system <NUM> may generally transmit apparatus data associated with traffic apparatus <NUM> to a remote processing platform such as remote device <NUM>. As noted above, remote device <NUM> in the <FIG> embodiment is depicted as a wireless telephone, but remote device <NUM> may be embodied in or comprise any of various other devices such as general purpose or specifically designed tablet computers, laptop computers, personal digital assistants (PDAs), or similar portable devices having appropriate communications capabilities to receive apparatus data from transmitter <NUM> and to transmit those data (either in raw or processed form) to another system or computing platform as set forth below. In some implementations, for instance, apparatus data received from transmitter <NUM> may be processed, pre-processed, aggregated, or otherwise organized by suitable processing elements and software components at remote device <NUM>; additionally or alternatively, it may be desirable that remote device <NUM> simply act as a relay to provide apparatus data from transmitter <NUM>, unmodified, to an additional device or system.

It will be appreciated that remote device <NUM> may comprise one or more processing components, such as a microprocessor, microcontroller, PLC, application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other data processing component having sufficient resources to receive the data transmission from beacon system <NUM>, to execute any processing that is desirable locally (i.e., at remote device <NUM>), and to transmit the raw apparatus data or processed data to another system. These hardware elements may be operative in accordance with software modules, operating systems, program applications, and other instruction sets (or a combination of these) as is generally known in the art.

Typically, remote device <NUM>, when implemented as a wireless telephone or tablet computer, may have a display (such as a touch screen display) and one or more input mechanisms (such as the same touch screen display and one or more physical buttons or switches) enabling interaction with remote device <NUM>, ordinarily via a user interface or graphical user interface (GUI). These implementations may have particular utility in applications in which remote device <NUM> may be employed, for example, to do some degree of processing or pre-processing of apparatus data received from beacon system <NUM> under control of, or influenced by, input from a user (which may be, for example, a road crew member installing or placing traffic apparatus <NUM>). In some situations, on the other hand, it may be desirable that remote device <NUM> comprise or embody a simple wireless relay strategy that requires no (or minimal) user interface mechanism. In these situations, remote device <NUM> may be implemented as a small, light-weight, wearable electronic component (such as a smart watch, a bi-directional pager device, or other communication component) with a transceiver and sufficient telecommunications capabilities to receive apparatus data and to transmit same without any interaction with a user. For example, remote device <NUM> in accordance with some embodiments may be removably or fixedly attached to, or integrated into the structure of, a garment such as a vest or hard hat worn by a member of a road crew or traffic control staff member. In these embodiments, the work flow of a road crew is minimally impacted by the beacon system <NUM> technology deployed in connection with the traffic apparatus <NUM> used in a particular traffic flow control application, since user interaction with remote device <NUM> is not required.

Turning now to an example of one implementation, <FIG> is a high-level functional schematic diagram of an embodiment of a system of acquiring and maintaining traffic apparatus location information. As illustrated at the left side of <FIG>, system <NUM> may generally comprise an array or arrangement (reference numeral <NUM>) of traffic apparatus <NUM>, each of which may comprise a respective beacon system <NUM> substantially as described above with reference to <FIG>. As noted above, each respective beacon system <NUM> may transmit apparatus data (such as via a respective transmitter <NUM>) to a remote device <NUM> deployed in proximity to the arrangement <NUM>.

It will be appreciated that arrangement <NUM> may comprise more or fewer traffic apparatus <NUM> than illustrated in <FIG>, and that each respective traffic apparatus <NUM> may serve a particular function within arrangement <NUM>. For example, where the right-most travel lane is closed (e.g., due to construction, a collision or hazard, law enforcement activity, etc.), one or more "Merge Left" signs may be deployed upstream of a series of cones, delineators, or barricades that urge motorists to the left lane. Similarly, one or more "Detour" signs may be deployed upstream of a barricade, a "Road Closed" sign, and a "Right" arrow sign urging motorists to turn right. Those of skill in the art will appreciate that the number and type of traffic apparatus <NUM> deployed may be application-specific and depend upon prevailing or typical traffic conditions, the nature and threat of a particular hazard, the size or length of an area affected by the traffic flow control desired, or a combination of these and a variety of other factors. In this context, the term "arrangement" is intended to encompass the various traffic apparatus <NUM> and their relative positions that, collectively, are expected to effectuate a particular traffic control goal (e.g., closing a lane of traffic, causing traffic to turn off of a road, controlling the speed of vehicular traffic, warning of a hazard, and the like).

In an embodiment, remote device <NUM> may be configured and operative to receive apparatus data from each respective beacon system <NUM> while in close enough proximity to be in communication with a respective transmitter <NUM>; this may be effectuated, for example, as a traffic apparatus <NUM> is being placed in arrangement <NUM>, or it may be effectuated after all traffic apparatus <NUM> have been set up in desired locations. As remote device <NUM> is moved through arrangement <NUM>, signal strength from each transmitter <NUM> may rise (e.g., as remote device <NUM> approaches the associated traffic apparatus <NUM>) and fall (e.g., as remote device <NUM> recedes from the associated traffic apparatus <NUM>). When signal strength is lost for a particular beacon system <NUM> (or if such signal strength falls below a predetermined threshold, for example), then remote device <NUM> may record (or transmit) a location of that particular beacon system <NUM> (and thus, a location of the traffic apparatus <NUM> to which it is affixed) when its signal strength was at or near a maximum. In the foregoing manner, either during deployment or after, a position ("location data") for each traffic apparatus <NUM> in arrangement <NUM> may be ascertained from acquired apparatus data, recorded, and/or transmitted by remote device <NUM>.

Location data based upon apparatus data may be forwarded from remote device <NUM> to another data processing system or platform, illustrated on the right side of <FIG> as central system <NUM>. As noted above, remote device <NUM> may, additionally or alternatively, transmit raw apparatus data to central system <NUM> for processing; in such an embodiment, location data for each traffic apparatus <NUM> in an arrangement <NUM> may be derived at central system <NUM>, for example, where processing resources and power consumption parameters may be less restricted than at remote device <NUM>. In that regard, it is worth noting again that derivation of location data from raw, or unprocessed, apparatus data may be implemented at remote device <NUM>, at central system <NUM>, or at both, operating either individually or in cooperation; these various data processing strategies may be selected in accordance with the processing capabilities and telecommunications bandwidth of remote device <NUM> or a variety of other factors.

It is noted that central system <NUM> may be embodied in or comprise a computer server or series of servers, workstations, desktop or laptop computers, or other similar data processing components useful for providing the functionality described herein. The various components of central system <NUM> (such as bus architectures, memory controllers, data storage, input/output devices, network interface cards or other telecommunications interfaces, and the like) are generally known in the art and have been omitted from <FIG> for clarity.

In operation of system <NUM>, proprietary software instruction sets may be executed, such as by central system <NUM>, remote device <NUM>, or a combination of both, to analyze acquired apparatus data transmitted by beacon system <NUM> and to write those data and the results of any computations to memory (not shown) at central system <NUM>. In the foregoing manner, central system <NUM> may acquire and maintain a detailed map recording a location of each traffic apparatus <NUM> deployed in a particular arrangement <NUM>.

In some implementations, location data may be aggregated with map data (available from a variety of third party navigation software providers, for instance) such that a map of a particular arrangement <NUM> and its constituent traffic apparatus <NUM> may be superimposed upon or otherwise integrated with road map data, satellite imagery data, or both. In one such embodiment, for instance, location data may be integrated with road map or satellite data at central system <NUM>, which may serve or transmit aggregated data to various third party platforms <NUM>. In another embodiment, additionally or alternatively, central system <NUM> may serve or transmit location data to third party platforms <NUM>, which may then integrate or aggregate such location data with their own proprietary data or software applications. In that regard, third party platforms <NUM> may include those owned or operated by, for example, federal, state, or local departments of transportation (DOT) or law enforcement, the National Transportation Safety Board (NTSB) or other regulatory authority, automobile manufacturers (for use in connection with onboard navigation aids or mapping software applications), suppliers of navigation software applications or solutions, and the like.

The connection between central system <NUM> and third party platforms <NUM> may be via the Internet, for example, or some other wide area network, and may be wired or wireless. The present disclosure is not intended to be limited by the type of telecommunications technologies used by any of the parties illustrated in <FIG>, nor is it intended to be limited by which of the parties integrates location data with map or satellite data. Those of skill in the art will recognize that the architectural arrangement of <FIG> is susceptible of various alternatives and modifications.

By way of example, it is noted that many smart work zone, commercial vehicle fleet management, and navigation systems employ real-time and historical traffic flow data for a variety of purposes. One such system promulgated by Signalisation Ver-Mac, for instance, is referred to as Jam Logic™, and uses traffic flow data to update road-side or overhead signage or network accessible navigational tools responsive to changes in traffic speed or flow patterns. Additionally, a number of commercially available mapping and navigational aids that are available via the Internet or proprietary telecommunications networks can provide visualizations of traffic congestion or locations of wrecks, road closures, or other hazards using data acquired from road-side traffic apparatus <NUM> such as those described above. It may be desirable in connection with these and other systems, however, to know where particular traffic apparatus <NUM> are along a route and to provide a motorist with an advanced alert (i.e., prior to the motorist's arrival within visual range), regarding what information a particular traffic apparatus <NUM> may be intended to convey. In particular, the road crew or a traffic control entity responsible for setting up individual traffic apparatus <NUM> may want to ensure, via data maintained at central system <NUM>, for example, that a particular arrangement <NUM> is deployed properly, as well as when and if a traffic apparatus <NUM> has been moved, e.g., by wind, rain, collision, vandalism, etc. By periodically moving remote device <NUM> in and around arrangement <NUM>, location data maintained at central system <NUM> may provide information that is useful for road crews or traffic control administrators to determine whether adjustments or relocation of one or more traffic apparatus <NUM> may be necessary or desirable.

Employing electronics to determine when apparatus data are to be transmitted, and how much apparatus data are to be transmitted, may allow the powered components of beacon system <NUM> (particularly sensors <NUM> and transmitter <NUM>) to conserve power. Since apparatus data need not be continuously processed and transmitted, and may be transmitted only periodically, only when remote device <NUM> is in close proximity, or (for example) only when an accelerometer or other motion detection device determines that traffic apparatus <NUM> has been moved, beacon system <NUM> may save on power such that a small photovoltaic panel or small chemical battery cell may be capable of providing sufficient power for most use cases.

<FIG> is a flow diagram illustrating aspects of a method of acquiring and maintaining traffic apparatus location information.

As indicated at block <NUM>, a beacon (such as beacon system <NUM>) may be affixed to a traffic apparatus <NUM> such as set forth above with reference to <FIG>. The term "affixed" in this context is intended to be construed broadly enough to encompass embodiments in which beacon system <NUM> is integrated with a structural component of traffic apparatus <NUM>, and may not require mechanical fasteners, adhesives, or other coupling elements.

As indicated at block <NUM>, a beacon may broadcast (such as via transmitter <NUM>, for instance) apparatus data associated with the traffic apparatus <NUM> to which it is affixed. As noted above, this may be accomplished utilizing data provided by one or more sensors <NUM> disposed on or attached to beacon system <NUM> as well as data provided by memory <NUM>. Apparatus data from these sources may be combined, multiplexed, or otherwise integrated for transmission by transmitter <NUM>, or they may be broadcast in discrete or separate data streams. In particular, memory <NUM> may store an apparatus identifier (apparatus ID) that distinguishes a traffic apparatus <NUM> from others that are deployed in proximity as well as a functional identifier (functional ID) that is associated with or defines the functionality of the traffic apparatus <NUM>. Positioning, orientation, and movement or acceleration data may also be provided for real-time or near real-time system applications.

In some embodiments, apparatus data may be transmitted only periodically or intermittently, such as at a frequency of once every five seconds, once every ten seconds, once per minute, etc. Additionally or alternatively, beacon system <NUM> may comprise a transceiver device that is configured and operative to be responsive to signals from remote device <NUM>; in such embodiments, apparatus data may be transmitted by transmitter <NUM>, for example, responsive to requests from, or a detected proximity of, remote device <NUM>. These embodiments may prolong battery life or minimize amperage draw by components of beacon system <NUM>, for example, and may have particular utility in applications which favor low power consumption.

Broadcast apparatus data may be captured, for example, by a remote device or instrument such as remote device <NUM>. As indicated at block <NUM>, apparatus data sufficient to identify a location of traffic apparatus <NUM> may be captured when a signal from transmitter <NUM> is at peak signal strength, as measured by remote device <NUM> (i.e., generally, when remote device <NUM> is closest to beacon system <NUM>). As noted above, this may be effectuated by moving remote device <NUM> in and around an arrangement <NUM> of traffic apparatus <NUM>; typically, it is expect that signal strength identified by remote device <NUM> will increase as remote device <NUM> approaches a location of traffic apparatus <NUM> and decrease as remote device <NUM> is moved away. In some embodiments, it may be desirable to use GPS or other mapping or location functionality resident at remote device <NUM> to acquire or to validate location data associated with a particular traffic apparatus <NUM>.

Signal strength and sampling of apparatus data may continue periodically or repeatedly until a threshold low signal strength is reached, as indicated at decision block <NUM>. As noted above, if remote device <NUM> is within a particular range of a particular traffic apparatus <NUM>, signal strength may be above a predetermined or desired threshold, and sampling may continue; when signal strength drops below a threshold, however, remote device <NUM> may acknowledge loss of signal and record apparatus data at the point when signal strength was at a peak. In the foregoing manner, remote device <NUM> may ascertain a location of each traffic apparatus <NUM>, along with apparatus ID and function ID, by moving relative to the traffic apparatus <NUM> deployed in a particular arrangement <NUM>; these data may be recorded (e.g., by remote device <NUM> for later transmission) or simply transmitted by remote device <NUM> (e.g., to central system <NUM>) for recordation or further processing as indicated at block <NUM>. As noted above, in instances where apparatus data do not include GPS or other specific data to locate a particular traffic apparatus <NUM> in two- or three-dimensional space, location data may be derived from or informed by cellular, navigational, GPS, or other location information resident on remote device <NUM> and measured or computed at the time that a threshold signal strength is reached for that particular traffic apparatus <NUM>.

The arrangement of the blocks and the order of operations depicted in <FIG> are not intended to exclude other alternatives or options. For example, the operations depicted at blocks <NUM> and <NUM> may occur substantially simultaneously in some implementations. Further, a different type of threshold and iterative loop may be employed, and the thresholds may vary as function of the type of processing expected or desired to be carried out by remote device <NUM>. For example, rather than a low signal strength threshold to exit the loop of block <NUM> and decision block <NUM>, a high signal strength threshold may be used instead, such that the loop is exited when signal strength begins to drop (e.g., as remote device <NUM> begins to recede from traffic apparatus <NUM>).

In accordance with the foregoing, a traffic control agency or other governmental or regulatory authority may ascertain and maintain the location of a portable (i.e., non-permanent) traffic apparatus <NUM>, and may review and validate the integrity of an arrangement <NUM> of same, without incurring the deleterious effects of additional or onerous workflow changes. The foregoing system and method introduce no additional recurring fees (such as subscriptions, for example) and may be implemented at low cost (since the beacon system <NUM> components may be implemented simply and cheaply, with low power requirements). The suppliers or lessors of traffic apparatus <NUM> may be enabled to access location information for every traffic apparatus <NUM> deployed in the field, and may uniquely identify every asset's purpose and location; this may have utility in marketing, business development, and other contexts. Those responsible for road conditions and traveler safety (such as DOTs, law enforcement officials, or local transportation boards) may be enabled to access information sufficient to assess road conditions and to identify road closures and local hazards. Autonomous vehicle developers may benefit from available aggregated data by integrating apparatus data and location data into their automated control systems, increasing safety with advanced warnings of road conditions or hazard zones.

Claim 1:
A traffic apparatus location system comprising:
a traffic apparatus (<NUM>);
a beacon system (<NUM>) affixed to said traffic apparatus (<NUM>), said beacon system (<NUM>) configured to broadcast apparatus data including a functional identifier associated with a function of said traffic apparatus (<NUM>);
a remote device (<NUM>) configured to receive the apparatus data broadcast by said beacon system (<NUM>), responsive to a measure of a signal strength of the beacon system (<NUM>) identified by the remote device (<NUM>); and
a computer processing system (<NUM>) configured to receive information associated with the apparatus data from said remote device (<NUM>), the information including the functional identifier associated with the function of said traffic apparatus (<NUM>);
wherein at least one of the remote device (<NUM>) and the computer processing system (<NUM>) is configured to use the information to derive location data associated with a location in space at which said traffic apparatus (<NUM>) is deployed; and
wherein at least one of the remote device (<NUM>) and the computer processing system (<NUM>) is configured to record the function of said traffic apparatus (<NUM>), and record the location in space at which said traffic apparatus (<NUM>) was deployed when the signal strength was at or near a maximum.