Patent Application
20250185139
As early as humans began dwelling in cities, efficient infrastructure became vital to the city's growth and prosperity. Modern cities' infrastructure includes below grade, above grade, and in the air infrastructure. The advent of I.O.T sensing technologies, fast computing speed, and real time ability to communicate across wide network array, expanded the “air” element to the cloud. This leap invites a reexamination of legacy urban infrastructure against current technologies for the benefit of improving infrastructure efficiency, reducing operating cost, and improving the quality of urban living. Urban planners tasked with cutting operational costs while improving the quality of urban living are constrained by budgetary limitations and typically resort to incremental changes. These changes often complicate the urban infrastructure by adding equipment with increased bureaucracies. A realistic assessment of the city's infrastructure and the actors associated with supporting the system shows:
With the above noted constraints, the challenge facing a planner today is how to optimize the cities' infrastructure and support staff efficiency while minimizing expenditures. In looking for an answer, among the test questions raised is what equipment is here to stay? Another question that follows is of the equipment that is here to stay, what specific equipment can easily be adapted to state-of-the-art technology?
An analysis shows that street light poles and traffic poles are ideal candidates for such integration. The streetlights by municipal ordinances are set apart at repeated intervals throughout the city and traffic poles are set at major intersections. Both streetlights and traffic lights are permanent vertical real estate structures with power input. The investment cost was paid for in years past.
Current systems and methods for a networked system of smart light pole devices are limited in both their ability to gather data relating to its local environment as well as their ability to communicate data relating to its local environment to additional smart light pole devices in the network. For example, current smart light pole devices do not have the capability of transmitting and/or receiving information and/or instructions from a first smart light pole device directly to a plurality of additional smart light pole devices. In these cases, a centralized server/node must be implemented to relay information and/or instructions from a first smart light pole device to a plurality of additional smart light pole devices. This method of information and/or instruction transmission is slowed and can be prone to outside security risks. Furthermore, using a relay system may negatively affect the real-time transmission of information and/or data, reducing the effectiveness of the overall system.
Street poles dot our modern landscape, from city parks to parking lots and from pedestrian walkways to commuter roadways, just to name a few. Some of these street poles are also illumination poles. Illumination poles serve to illuminate their respective surroundings to provide visibility in darkly lit environments and/or during the night hours when there is a natural absence of light. By supplying visibility in environments otherwise low on light, these illumination poles provide value to a community through an added measure of safety, security, and convenience.
With reference to roadways, illumination poles can be set up at intersections to assist both vehicle and pedestrian traffic in safely navigating the intersection in low-light settings. In addition, thereto, illumination poles can be set up along roadways at predetermined intervals, depending on the illumination capabilities of the luminaire attached to the pole and the light intensity desired by the municipality, to assist both vehicle and pedestrian traffic along the roadway. City parks, parking lots, garages, walking paths, and other common areas also utilize illumination poles in a similar fashion.
But with the advent of the technological revolution, including advances in power generation, power distribution, and power and data connectivity as well as a variety of electronic devices having increasingly better processing capabilities and connectivity, municipalities are beginning to use these advances to transform their respective landscapes into “smarter” landscapes. For example, conventional traffic lights and conventional illumination poles, and their accompanying structures, are becoming increasingly populated with additional lighting and non-lighting related devices that improve the lights' and poles' collective utility to the community. Cameras are sometimes mounted on traffic lights to monitor traffic flow. Photocells are sometimes mounted on illumination poles to automate the activation of light from the luminaire in low-light conditions.
However, this transformation of the traffic light or the illumination pole to include additional lighting and/or non-lighting related devices is not without problems. Consider, for example, that adding, removing, or somehow altering components of the illumination pole may compromise the structural integrity of the pole itself. Changes to the illumination pole may create structural weaknesses or introduce susceptibility to corrosion. Also, changes to the illumination pole may not only diminish the aesthetic architectural appeal originally intended by the designer but also degrade the uniformity and beauty of the illumination poles chosen by the municipality. Mounting after-market cameras and/or additional products to an illumination pole may diminish the original aesthetic appeal by creating unsightly structural configurations and wiring and by introducing unpleasant disparity between poles.
In addition, changes to the illumination pole may prevent the proliferation of additional improvements and/or components due to inadequate space allocation on the pole. For example, a device manufacturer's interest in the illumination pole is limited to its respective discipline. If, therefore, one device is added to the pole that monopolizes space allocation, then it could be possible that other device manufacturers may be dissuaded from pursuing future improvements to the pole due to the lack of space. In other words, the first discipline to occupy the pole could do so at the expense of other disciplines to follow. Such inefficiency is not beneficial to the municipality or the citizens thereof.
The lighting industry is transforming from electromagnetic to electronic technology. Similarly, electronic technology is developing electronic devices with increasingly better processing capabilities and connectivity. Yet, despite the lighting industry becoming more and more interested on incorporating intelligent systems or “smart” systems to provide a variety of lighting system functions, few advances have been made in developing efficient, economical, and aesthetically pleasing smart illumination poles, due at least in part to historical legacy, complexity, and cost. Each individual developer of design improvements carries with it costs associated with research and development, upfront equipment purchase, installation, operation, and maintenance.
In view of the foregoing, there is thus a need in the lighting industry for an apparatus that can establish standards and methods for device cohabitation on illumination poles, as these poles are increasingly included in the smart grid revolution. The present disclosure addresses these concerns.
Managing the urban flow of vehicular traffic is rather complex. In the past, traffic engineers obtained data on average daily/annually street traffic and then synchronized the traffic lights to respond to a predictable forecast. This method could not predict variables such as accidents, major municipal events, emergency vehicular traffic, or impact of weather patterns on local streets. A ground-sensing device commonly used helps alleviate intersection congestion; however, it lacks the ability to synchronize the traffic lights based on the number of waiting vehicles. The present innovation, the IDS is a scout member of city-wide scouts that in real time counts and communicates to neighboring devices the number of vehicles approaching an intersection. The IDS is placed on street light poles and any other suitable energized vertical structure equipped with sensing devices that recognize a moving object and its trajectory. The sensing device may include a camera, radar, interactive vehicle/pole identifier, or other devices, and a combination of them thereof. As the sensing devices sense the moving object and its trajectory, they pass the information to the next IDS system at the same trajectory path and/or directly to the traffic light controller. Aside from counting vehicles, the IDS can pick up anomalies and disturbances in common traffic patterns. For example, an emergency vehicle has the right-of-way. When an IDS senses an emergency vehicle approaching, it communicates to its downstream member network that the intersection in the anticipated path of the emergency vehicle must be clear. When the IDS senses that an accident occurs within its scouting zone, it communicates to its member upstream letting it know that traffic diversion is needed. The IDS can also act as a parking slot locater and relay parking related information to metering/towing companies and/or municipal planners. Current car technology comes with a dashboard screen and means of external communication. Using an app, the car's dashboard can signify all vacant parking slot locations along the path the driver takes. The IDS is the reporting real time device communicating the information. Older model cars can use a handheld device to activate and deactivate the metering of a car whereas the IDS can associate the car, the car location and the handheld device.
Managing an intersection with human and vehicular traffic efficiently is complex. The IDS placed on vertical structure/s at an intersection operating in conjunction with other roadway IDS network members provides real time information to the intersection's traffic signal controller to operate safely and efficiently without any human interaction. The IDS provide the controller with sensed information from all leading roads into the intersection and all pedestrian traffic sensed in and in proximity of the intersection. The controller's program typically also includes a fallback routine when critical input is not received, and/or it senses a failure.
The above narrative represents a fraction of the IDS's sensing, processing, and communicating device capabilities for managing human and vehicular traffic. The very same devices perform additional tasks that relate to other services. The task may include services performed for the benefit of a plurality of municipal departments, product/service contractor/s and citizenry at large. These shared device capabilities coupled with processing power and communication techniques are re-charting future cities' infrastructure design logic. Economically, consolidating multi-party needs on as few as possible devices while processing the devices' inputs in real time transmitting its processed input to a plurality of clients significantly reduces cost and improves efficiency. Furthermore, standardization of all network aspects including the device size and connectivity electrical and mechanical connectivity, the internal communication protocol and the IDS network communication protocol with external clients, reduces each device cost and servicing staff. The IDS embodiment energy consumption is significantly less than conventional municipal HID lighting luminaires. Replacing an existing HID streetlight luminaire with an IDS with an LED lighting device leaves extra electrical capacity for a myriad of auxiliary devices.
Various embodiments of the present technology may comprise a network of intermediate device systems configured to be detachably coupled to an illumination pole electrically connected to a power source. The intermediate device system may comprise a housing with an exterior surface and an interior cavity configured to receive at least one electrical component. The intermediate device system may comprise a control unit disposed within the interior cavity of the housing and communicatively coupled to a processor. The control unit may be configured to receive and process substantially real time information from at least one of the electronic devices and create a data set based on the received real time information. In some embodiments, the data set may comprise at least one of: a parameter of the surrounding environment and an instruction set configured to operate at least one of the electrical devices within the intermediate device system and/or a second intermediate device system within the network of intermediate device systems. The intermediate device system may also comprise a communication module disposed within the interior cavity of the housing and communicatively coupled to the control unit. The communication module may form a bidirectional communication channel to facilitate transfer of the data set between the control unit of the intermediate device system and a second communication module of the second intermediate device system and receive an incoming data set from the second communication module.
A more complete appreciation of the disclosure and many of the attendant advantages thereof will be readily obtained as the same becomes better understood by reference to the following detailed description when considered in connection with the accompanying drawings, wherein:
As used herein, an element or step recited in the singular and proceeded with the word “a” or “an” should be understood as not excluding plural elements or steps, unless such exclusion is explicitly recited. Furthermore, references to “one embodiment” of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features.
Before addressing each figure individually, a brief overview of an Intermediate Device Structure (IDS) network is provided. The IDS network is an urban infrastructure device solution comprising a community of like members configured to make living in the city safer, healthier, and friendlier. The IDS members are communicatively coupled and distributed throughout the public domain of a city. The IDS community members can also be communicatively coupled to at least one remote client. The IDS members can communicate with at least one: an individual and/or his or her mobile device, a stationary or moving vehicle, a municipal department, a banking/credit institution, and cloud computing resources, as will be discussed. Examples of IDS members used in a network are found in the patent documents cited in the Cross-Reference Section, for example U.S. Pat. No. 11,071,204. However, the IDS member described herein has modified functionality to provide the functions and services as discussed herein.
The IDS member is coupled to an elevated structure that has or can have access to electricity. The elevated structures can include roadway lighting poles, traffic light poles, walls, power poles, and building exteriors. Coupling the IDS member to vertical structures well above grade enables greater area coverage to coupled sensing and communication devices, as well as providing a better vantage point to capture images with an image sensor which are used in black ice detection. Also, mounting IDS members well above the ground reduces risk of damage, tampering or theft.
Roadways constitute the majority of the city's public domain. Therefore, the IDS members can be primarily placed on roadway lighting and traffic lighting poles. These poles are electrified and the spacing between the poles is regulated, leaving no gaps that would otherwise require installing vertical structures to support the IDS members. The IDS member can incorporate the utility of the device/s originally coupled to the pole or can operate independently.
The IDS member's electronic devices can include at least one of: a processor/controller with resident memory and code, a sensing device, a communication device, a back-up power storage device, and an output device. Each of the IDS' networked members is tasked to gather in real time environmental inputs around the vicinity of the IDS member. Using sensing devices (e.g., image sensors, ground and air temperature sensors, humidity sensors, light sensors and the like) the information is received by the IDS' processor/controller. The sensing devices can be coupled to at least one of: the IDS' member housing, the pole/arm, and to a surface in the vicinity of the pole.
The sensing devices can include: a camera (which at least includes an image sensor and optics, and which can be a still camera or a video camera), a photocell, a temperature probe, a barometric pressure probe, a vibration sensor, a speaker/microphone, a light source, a wind velocity probe, an air quality probe, a radiation sensor, radar, a sound meter and any other sensing device that, operating alone and/or with other coupled sensing devices, enhances the utility derived from the IDS member. The sensing devices may also be hosted on the UAV 85 as will be discussed.
The processor/controller of the IDS member is configured to receive and process a plurality of inputs in real time. The inputs are received from sensory devices associated with the IDS member, neighboring like IDS members and other remote clients. The IDS member can have a unique address and the associated sensing, communicating, output, and power back-up storage devices can be associated by a sub-address. Similarly, other remote IDS members, their devices, as well as remote clients have their own unique addresses and sub-addresses. Unique addresses of IDS member devices enable geographic mapping of the IDS' member community.
The code operating the processor/controller of the IDS member is configured to operate alone and/or in unison with another networked member. The code can employ at least one artificial intelligence (AI) algorithm embodied as a trained AI engine, as will be discussed in more detail with reference to
The inputs received by the devices associated with the IDS member coupled with inputs received from like IDS neighboring members and other remote clients is compiled by the code's pre-programmed parameters to generate accurate and consistent outputs based on the same sets of inputs. The outputs can be preemptive or reactive. The IDS community of networked members' prime responsibility is to protect life. Applicant's prior U.S. Pat. Nos. 9,829,185; 9,885,451; 10,215,351; 10,653,014; and 11,071,204, each of which is incorporated herein by reference in its entirety, articulate several utility use cases.
A detailed description of the hereinafter described embodiments of the disclosed apparatus and method are presented herein by way of exemplification and not limitation with reference to the Figures listed above. Although certain embodiments are shown and described in detail, it should be understood that various changes and modifications may be made without departing from the scope of the appended claims. The scope of the present disclosure will in no way be limited to the number of constituting components, the materials thereof, the shapes thereof, the relative arrangement thereof, etc., and are disclosed simply as an example of embodiments of the present disclosure.
As a preface to the detailed description, it should be noted that, as used in this specification and the appended claims, the singular forms “a”, “an” and “the” include plural referents, unless the context clearly dictates otherwise.
The conventional street pole or public utility pole is a largely untapped vertical real estate asset that communities, municipalities, and device manufacturers alike can begin to develop to increase economic value to both the government and private sector as well as improve quality of life for ordinary citizens, and particularly those in urban settings.
As shown in
As a result of the preconfigured electric grid and each conventional illumination pole's established electric connectivity thereto, each conventional illumination pole 2 is currently underutilized as an electrified vertical real estate asset of the community. In other words, the full value of illumination pole 2 as housing for smart devices and as an integral component of an overall smart grid of any particular community is not yet realized. However, the intermediate device structure (IDS) of the present disclosure for use with illumination poles 2 can standardize the means and methods of maximizing this largely-dormant electrified vertical resource.
Referring to the drawings,
With reference to
Embodiments of IDS 10 may comprise base member 30. Base member 30 may comprise a generally rectangular shape having a length defined between a first end 32 and a second end 34. Base member 30 may have a through bore 36 running from first end 32 to second end 34. Base member 30 may define an outer width W, as depicted in
Embodiments of IDS 10 may further comprise base member 30 being configured to be functionally and/or structurally coupled to coupling arm 20, and second end 24 of coupling arm 20 may be coupled to first end 32 of base member 30 such that coupling arm 20 and base member 30 are structurally and functionally secured to one another thereby. Embodiments of IDS 10 may further comprise coupling arm 20 and base member 30 being assembled by joining casted and non-casted elements together. Alternatively, coupling arm 20 and base member 30 may be monolithically casted or printed in a unitary or single piece. Coupling arm 20 and base member 30 may be manufactured from a heat dissipating, non-corrosive material and may be painted or otherwise treated to suit architectural needs. The configuration of IDS 10 provides a rigid design suitable in adverse environments.
Embodiments of IDS 10 may comprise coupling arm 20 being configured to receive and retain thereon luminaire 8 and base member 30 being configured to receive and retain therein mast arm 6. In other words, embodiments of IDS 10 may comprise coupling arm 20 and base member 30 being configured to be inserted between and oriented in line with mast arm 6 and luminaire 8 of illumination pole 2. Conventional illumination poles 2 used on roadways are typically configured to have mast arm 6 extend over the street and sidewalk such that luminaire 8 is deployed over vehicle and pedestrian traffic. Industry standards have harmonized the arm tip dimensions of mast arm 6 so manufacturers of luminaires 8 may build luminaires 8 to fit the standard mast arm 6. The tip of mast arm 6 is therefore dimensionally common to most roadway luminaires 8. As a result, first end 22 of coupling arm 20 may be physically and functionally shaped and sized to functionally engage luminaire 8. Once assembled in this way, coupling arm 20 and luminaire 8 may thereafter be retained on one another by fastening means, such as screws, bolts, mechanical clasps, friction fit, and the like. In like manner, through bore 36 of base member 30 may be physically and functionally shaped and sized to functionally engage the tip end of mast arm 6 of conventional illumination pole 2. Base member 30 may therefore be configured to receive mast arm 6 within through bore 36. In particular, second end 34 of base member 30 may be inserted onto mast arm 6 and base member 30 and mast arm 6 may thereby be coupled to one another by fastening means, such as screws, bolts, mechanical clasps, friction fit, and the like. Any of the fastening means described herein may further comprise sealing members, such as neoprene-like washers, that may function together with the fastener and/or the bores 36 to seal the junction between component parts against moisture ingress.
With reference to
With reference to
With reference to
With reference to
With reference to
With reference to
Embodiments of IDS 10 may further comprise a mechanical eye 60, such as a camera (optical and infrared) or other optical instrument. Mechanical eye 60 may comprise any auxiliary device that may be communicatively coupled to IDS 10 to provide optical image input to IDS 10 and other auxiliary devices coupled thereto. Mechanical eye 60 may be configured to be physically coupled to housing 40 at a lower region of housing 40 or on a bottom surface of housing 40. As depicted, mechanical eye 60 may be configured to be physically coupled to base member 30 on a bottom surface of base member 30. Mechanical eye 60 may be configured to be releasably and repeatedly coupled to housing 40, as needed. Mechanical eye 60 may be configured to couple to dock 57 to facilitate quick and easy connection to power and data connectivity provided through IDS 10.
With reference to
With reference to
In one embodiment, the control unit 80 may be configured to create a data set based on the received real time information from components of the IDS 10, remote clients, remote devices, and/or any other system capable of sending information. The data set may comprise information related to a parameter of the surrounding environment. For example, the data set created by the control unit 80 of one IDS 10 may comprise substantially real time audiovisual information captured by the camera 60 of that IDS 10. The parameter of the surrounding environment may comprise any suitable parameter captured by any component of the IDS 10 such as an electronic eye (i.e., camera 60), an electronic car 86, an illumination source, an auxiliary device 70, a remote client (e.g., a first responder), a remote device (e.g., a cell phone or RFID tag), and/or the like.
The data set may further comprise an instruction set configured to operate the plurality of electronic devices on the IDS 10. For example, the instruction set may comprise instructions for the control unit 80 to operate the illumination source of the IDS 10, to operate the camera 60 of the IDS 10, to send information from one IDS 10 to a plurality of additional IDSs 10, to operate an electronic device located on a different IDS, and/or the like.
The communication module 126 may be configured to form a bidirectional communication channel between the IDS 10 and one or additional IDSs 10. The communication module may further be configured to form a bidirectional communication channel between the IDS 10 and one or more additional electronic devices, remote clients, and/or remote devices. The bidirectional communication channel may be configured to facilitate the transfer of the data set between the control unit of the first IDS 10 and a second communication module 126 of a second IDS 10. The bidirectional communication channel may be configured to allow information and/or data to be sent back and forth between a first IDS 10 to a second IDS 20, between a first IDS 10 and a remote client and/or remote device, and/or between a first IDS 10 and any other system suitably configured to receive information. The bidirectional communication channel may facilitate transfer of information and/or data via hard-wire connections, wireless connections, WIFI, infrared, cellular, and/or the like.
In one embodiment, the bidirectional communication channel may be configured to receive a second incoming data set from a remote client, a remote device, and/or another IDS 10. The second incoming data set may comprise a new set of data/information related to the parameter of the surrounding area as well as a new instruction set configured to operate a plurality of electronic devices on either the IDS receiving the second data set, the remote device, and/or the remote client. For example, the incoming data set may comprise an instruction set instructing the receiving IDS 10 to activate its illumination device.
For example, a first IDS 10 in the network may capture data related to a parameter of the surrounding environment (e.g., traffic conditions). Based on the captured data, the control unit 80 may generate a data set with an instruction set for a second IDS 10 to turn its illumination device on. The data set may be sent from the first IDS 10 to the second IDS 10 via the bidirectional communication channel. Once received by the second IDS (via its own communication module), the control unit 80 of the second IDS 10 may be configured to execute the instructions included in the instruction set of the data set. The second IDS 10 may use the bidirectional communication channel to send a confirmation back to the first IDS 10. Communication via the bidirectional communication channel between a first IDS 10 and an additional IDS 10, remote client, and/or remote device may be done via radio frequency, WIFI, cellular, hard-wired communication lines, infrared, fiber optics, and/or any other suitable system configured to facilitate the transmission of data/information.
Using the same example above, instead of sending the data set to a second IDS 10, the first IDS 10 may be configured to send the data set to a plurality of additional remote clients and/or remote devices. For example, if the captured parameter of the surrounding environment relates to traffic conditions, the data set may be sent to a remote client such as a first responder with instructions to perform a task. Similarly, the data set may be sent to a cell phone provider with instructions to send alert messages to its customers in the area to avoid a certain location. The data set my also by configured to be sent to a plurality of remote devices located on the pole structure and/or away from the pole structure. A remote device may comprise any device suitably configured to receive information from an IDS 10 such as a cell phone, computer, tablet, GPS unit, and/or the like.
The control unit 80 may be suitably configured to accept and operate a variety of auxiliary devices 70 independently or in unison, wherein each auxiliary device 70 may be configured to sense a parameter of the surrounding environment. For example, mechanical eye 60 may be considered one of several auxiliary devices 70 that control unit 80 can control, manipulate, operate, direct, activate, manage, run, administer, oversee, work, maneuver, or otherwise govern to the benefit of the operational functions of IDS 10 according to programmed parameters, hardware and software capabilities, and sensory input. Mechanical eye 60 may operate to effectively provide an eye into the community, and in particular to the surrounding environments around IDS 10. Mechanical eye 60 may observe, survey, study, and/or monitor surrounding environments and provide a means for remote clients, such as first responders, police, fire and rescue, EMTs, etc., to view, watch, or otherwise see the happenings and conditions around IDS 10 in real-time. Mechanical eye 60 may be configured to redirect its line-of-sight in 360-degree orientation, such that mechanical eye 60 may provide. 360-degree views of the surrounding environment. Mechanical eye 60 may operate by client-directed input received remotely from IDS 10 (i.e., mechanical eye 60 can be operated by users remote from IDS 10), or mechanical eye 60 may operate automatically by pre-programmed instructions that are based on sensory input of other auxiliary devices 70.
Further in example, and not by way of limitation, auxiliary devices 70 may further comprise a metering device 82, a drone launch and/or charging pad 84, an electronic car 86 (such as a microphone or any system configured to receive audible data and/or information from its surrounding area), a barometric sensor 88, an air quality sensor 90, electrified signage 92, a communication device 94, a structural integrity sensor 96, a wind velocity sensor 98, a photovoltaic cell 100, an RFID reader 102, radar 104, broadband communication hardware 106 (such as WIFI/WiMAX transponders, transceivers, and other communication gear; 3G, 4G and 5G communication gear), a speaker 108, a corrosion monitor 110, a vibration monitor 112 (such as a piezoelectric sensor), GPS technology 114, power storage unit 116 (such as a battery or backup power unit), and a radiation sensor 118 (such as a high-energy particle detector). RFID reader. 102 may further comprise any other signal reader that is capable of reading and/or receiving a signal being broadcast by a RFID tag within the sensing range of the RFID reader 102. These auxiliary devices 70 listed herein may not be considered to be all inclusive. That is, the auxiliary devices 70 listed herein may additionally include other community system and monitoring devices and circuits not listed herein. For example, auxiliary devices 70 may further comprise seasonal lighting displays, long-term and short-term electrified signage, astronomical clock for keeping and tracking time, a thermometer of any variety for measuring one or more temperatures, one or more photocells, and one or more infrared sensors (such as motion sensors), each of these being configured to be electrically coupled to IDS 10 and configured to be controlled thereby. Control unit 80 may be housed in housing 40, such as within cavity 58. Auxiliary devices 70 may be housed in housing 40, such as in cavity 58, and may alternatively be coupled housing 40 on an exterior portion thereof, as described herein.
In one embodiment, the auxiliary devices 70 may be suitably configured with any system configured to allow a first auxiliary device 70 to communicate with a second auxiliary device 70. The auxiliary device 70 of a first IDS 10 may be configured to communicate with one or more auxiliary devices 70 of one or more additional IDS 10. For example, the electronic eye (i.e., camera 60) of one IDS 10 may receive sensed information of its surrounding area and may associate this information with the specific IDS 10 on which the camera 60 is mounted/housed. The first IDS 10 may send the sensed information from the camera 60 of the first IDS 10 to any number of additional IDS 10 such that the additional IDS 10 also has access to the same sensed information as the first IDS 10. For example, the control unit 80 of the first IDS 10 may transmit/send the sensed information from the camera 60 of the first IDS 10 via the communication module 126 to the communication module 126 of the second IDS 10, wherein the information is passed to the control unit 80 for further processing. This cycle may be repeated at each of the individual IDSs 10 receiving the sensed data/information from the camera 60 of the first IDS 10.
Embodiments of drone launch and charging pad 84 may comprise a drone (86 in
Auxiliary devices 70 may be optimized to provide a broader platform for a larger number of auxiliary devices 70 with greater interactive capabilities. Thus, in a general sense, control unit 80 may be considered the heart and mind of IDS 10, the structural components, such as coupling arm 20, base member 30, and housing 40 may be considered the skeletal support of IDS 10, and auxiliary devices 70 may be considered the muscle and sensory input of IDS 10. For example, coupling arm 20, base member 30, and housing 40 may provide a physical platform in conjunction with pole 4, and in particular mast arm 6, on which IDS 10 may be positioned for optimal benefit to the community in the performance of its intended functions. Further, auxiliary devices 70 for example, may gather information of the surrounding environment around IDS 10 and relay this information to control unit 80 for processing. Control unit 80 may then provide directives, instructions, or commands to IDS 10 for further sensory gathering operations, to the surrounding environment in the form of direct and immediate audible or visible alerts, or to remote devices or clients positioned at a short or great distance from IDS 10. Each IDS 10 may also form part of a larger network of IDSs 10. Taken together, the network of IDSs 10 may be configured to operate in unison to provide a larger-scale view of conditions in a community or along a roadway in real time. Communications hardware and wiring may comprise electrical wiring, broadband communication cable, fiber optic cable, category 5 cable, network cable, twisted pair cable, or other similar wiring and cable that is configured to carry, transmit, and otherwise support electricity, power, data exchange, and/or the like.
In one embodiment, the network of IDSs 10 may be autonomous and decentralized. The IDS 10 may be autonomous in that the IDS 10 may be configured to operate independently from human control based on a parameter of a local environment, received information from other IDSs 10, remote devices, and/or remote clients, and the like. For example, based on the light levels captured by a camera 60, the IDS 10 may be configured to automatically operate the illumination device. The network of IDSs 10 may also be configured to operate in a decentralized fashion. For example, a single IDS 10 may be configured to relay and/or transmit information from itself to one or more additional IDSs 10, remote clients, and/or remote devices without first transmitting that information to a centralized server. In this configuration, the network of IDSs may be configured to operate more efficiently and provide information at a higher speed than if the information needs to be routed through a centralized server first.
Now referring to
In one embodiment, the upper section 1801 and the lower section 1802 may be detachably coupled together with any suitable fastener such as a hinge 41. For example, the upper section 1801 may comprise a first hinge portion 1810 for receiving a second hinge portion 1815 of the hinge 41, wherein the second hinge portion 1815 is disposed on the lower section 1802. The first hinge portion 1810 and the second hinge portion 1815 may joined by automatically lock in place or may be manually locked in place. When the first hinge portion 1810 and the second hinge portion 1815 are couple together, the interior of the IDS 10 may be accessed by dissociation of the lower section and engagement of the hinge 41, as described below.
Now referring to
Referring to
In one embodiment, sidewalls 1820 of the attachment system 1803 may be configured to suitably fit around an existing light pole. For example, the sidewalls 1820 may be curved to fit a rounded light pole mast, or the sidewalls 1820 may be substantially straight to fit around a square or other suitably shaped light pole mast. A pair of opposing sidewalls 1820 of the attachment system 1803 may comprise a mast track 9 configured to fit around an existing light pole mast as shown in
Referring to
In one embodiment, the attachment system 1803 may comprise a power entry port 1808. The power entry port 1808 may be configured to receive a power source from an existing structure such as a light pole (conductors of the power source may be a power bus). The power entry port 1808 may comprise two substantially equally sized holes on the attachment system 1803 as well as the housing body 50 as shown in
In one embodiment, the upper surface of the attachment system 1803 may be suitably configured to receive a landing pad 84 for the drone. The landing pad 84 may be configured to receive, hold, and/or recharge the drone. For example, the landing pad 84 may be communicatively coupled to the control unit 80 of the IDS 10 as well as the power module of the IDS 10. The landing pad 84 may comprise electrical contacts to interact with the charging port of an UAV such that when the UAV 85 (
In one embodiment, the landing pad 84 may comprise the same structure as the attachment system 1803, or the landing pad 84 may comprise a separate component that is coupled to the attachment system 1803 at a later time. The landing pad 84 may be detachably coupled to the attachment system 1803 using any suitable method such as screws, bolts, adhesives, magnets, and/or the like. The size of the landing pad 84 may vary depending on the size of the UAV for which the landing pad 84 is configured for.
Now referring to
Now referring back to
The upper section 1801 may further be configured with a plurality of access ports configured to grant access to the interior of the housing body 50. The access ports may comprise an electrical wiring port 5 and antenna port 46. The electrical wiring port 5 ports may be configured to receive electrical power lines from an exterior source. The antenna port 46 may be configured to receive auxiliary devices such as antennas, and/or receive additional components of the IDS. The access ports may vary in size depending on the type of component being passed through and/or attached.
Now referring to
In one embodiment, the lower section 1802 may be configured with an access button configured to grant access to the cavity 58 of the housing body 50. For example, an access button 42 may be disposed on the lower section 1802 and suitably configured to open an access door 40 utilizing the hinge system 41. The access button 42 may be configured to release the hinge system 41 such that access to the interior of the housing body 50 is granted.
In one embodiment, the lower section 1802 may comprise a dedicated access port 56 and/or a power and data port 57. The dedicated access port 56 and/or the power and data port 57 may be configured to receive electrical power from the power supply of the IDS 10 and pass that power to one of the IDS's 10 electrical components. For example, camera 60 may be coupled to the dedicated access port 56 to receive electrical power to operate the camera 60. The power and data port 57 may be configured to provide electrical power and/or data lines for the camera 60 as well as any additional auxiliary devices 70 as discussed above.
The lower section 1802 may further comprise a light source 1809. The light source may comprise any suitable system or device configured to provide illumination to its surrounding area. The light source 1809 may receive electrical power from the IDS 10. For example, the light source 1809 may be electrically coupled to the power supply of the IDS such that electrical power may be transmitted to the light source 1809. The light source 1809 may further be communicatively coupled to the control unit 80 of the IDS. The light source 1809 may be configured to receive information, data, and/or instructions from the control unit to operate the light source 1809. For example, the control unit may send instructions to the light source 1809 to turn on and off depending on the received information from one of the electrical components of the IDS 10.
Control unit 80 may further comprise operating components within cavity 58 of housing 40 of IDS 10; the operating components may include one or more power supply modules 120, one or more processors 124 with associated memory 125, and one or more communication modules 126 that direct I/O operations of IDS 10. Power supply module 120 may include a power converter and distribution module. Control unit 80 may further comprise long-term data storage 128, such as a hard drive, solid state drive, or other data storage device. Each of the individual components of control unit 80, including for example, power supply module 120, processor 124, RAM memory 125, communication module 126, data storage 128, and auxiliary devices 80, may each be suitably connected via a power bus 87 and a data bus 89 (represented as solid lines). Control unit 80 and its associated component parts and wiring may be referred to as an electronic assembly.
Embodiments of IDS 10 may comprise power supply 120 being a power supply and distribution module. In one embodiment, the distribution module may be incorporated into the power supply or as a stand-alone component communicatively coupled to the power supply. As such, power supply 120 may be configured to receive line power 130 via wiring 5 from the existing power grid of the municipality. Wiring 5 may run from the ground and up through pole 4, through mast arm 6, and into cavity 58 of housing 40 by way of openings 35/54 in base member 30 and internal ridge 52, respectively. In this way, line power 130 may arrive at power supply 120 and may be electrically coupled to power supply 120. As a power converter and distribution module, power supply 120 may be configured to take the received line power 130 and convert line power 130 into various degrees of low-voltage power needed to operate any one or more of the various auxiliary devices 70, as needed and required by each device 70. Power supply 120 may be configured to systematically and automatically recognize auxiliary devices 70 coupled to IDS 10 and determine the power requirements of each device 70 and may thereafter convert line power 130 into the specific power required by device 70 and then distribute or route this converted power to device 70. In the alternative, the specific power requirements of each device 70 may be input into IDS 10 via programming and updating control code 81 to do so. Yet, regardless of how IDS 10, control unit 80, processor 124, or control code 81 determines what power to send to each individual device 70, power supply 120, as a power converter and distribution module, may be configured to perform this line power reception, low-voltage conversion, and distribution for each auxiliary device 70 coupled to IDS 10, whether device 70 is positioned within housing 40 or external to housing 40. In like manner, luminaire 8 may be electrically coupled to power supply 120. As such, IDS 10 may be configured to control, convert, and distribute electric power to luminaire 8 according to the functions of IDS 10 described herein. In other words, as a power converter and distribution module, power supply 120 may be configured to perform this line power reception, low-voltage conversion, and distribution for the luminaire 8 in addition to each of the devices 70. The IDS 10 may be configured to take an existing source of line power 130 and convert this electric power to the individual power requirement needs of any and all electronic devices coupled to or related to the operations of IDS 10 and distributes this converted/required power according to the operational directives of IDS 10 as determined by sensory input from devices 70 or programmed directives of IDS 10. The IDS 10 may be configured to be retrofitted on existing poles 2 and with a single electrical connection to line power 130 become a facilitator of smart technology, with each IDS 10 being customizable with devices 70 to the needs of communities, municipalities, and citizenry as determined on a case-by-case basis or a pole-by-pole basis. The power supply 120 may be further configured to provide power to a remote device coupled to the pole structure that may or may not be directly coupled to the IDS 10. For example, the pole structure 4 may comprise a plurality of auxiliary devices 70 that interact with the IDS 10, but do not reside within the IDS 10 itself.
In another embodiment, as a power converter and distributor, power supply 120 may be configured to convert line power 130 to the low-voltage power needed to operate the various devices 70 of IDS 10 and control unit 80, as described above, but may leave untouched the electrical connections of luminaire 8. Thus, despite IDS 10 being coupled to line power 130 through power supply 120, luminaire 8 may be directly coupled to line power 130 as it was prior to installation of IDS 10. Or, through software and/or control code 81, IDS 10 may be configured to control some portion of the functions of luminaire 8 while luminaire 8 continues to receive its power from line power 130.
Power supply 120 may be modular and scalable having one or more input power channels 121 and output power channels 123. Input and output power channels 121, 123 may be programmable with flexibility to change the power format supplied and device specific power operational parameters as needed. For example, some devices of the IDS may require a higher voltage/current than a different device of the IDS 10. Power supply 120 may have an optional dedicated processor 127, governing the power from power supply 120 while maintaining real-time communication with processor 124 of control unit 80. In some embodiments, power supply 120 may also have direct communication capability with an external network (not shown). Power supply 120 may also be configured to receive and utilize photovoltaic power, such as from photovoltaic cell 100.
Embodiments of IDS 10 may further comprise a backup emergency battery, e.g., UPS 122, whose power may be selectively distributed to all essential services and devices during an emergency. UPS 122 may be also connected to photovoltaic cell 100 to receive power therefrom. UPS 122 may be networked with other input/output onboard environmental data collection, assessment, and operational devices, and have remote communication capability.
Embodiments of IDS 10 may further comprise low-voltage auxiliary devices 70 being housed within housing 40, on exterior surfaces of housing 40, on pole 4, in communication with pole 4 but below the ground surface (i.e., below grade), and in and on pole 4 in various locations, as desired and determined by intended use and configuration of IDS 10. As discussed above, luminaire 8 may be configured to operate on power and controls that have limited connectivity to IDS 10, wherein housing 40 of IDS 10 is merely a pass through for luminaire 8 power and control. Luminaire 8 may be configured to operate on power and controls that is directly connected to IDS 10 and controlled by IDS 10 operations, wherein IDS 10 governs operations and control of luminaire 8 and luminaire 8 is comprised merely of lamps and optical encasements. In other words, while luminaire 8 may contain hardware for dispensing light in low-light settings, control and operational aspects of luminaire 8 may be controlled and governed by IDS 10, such as hours of operation and illumination intensity just to name a few.
Data output from power supply 120 may include reporting on the quality of the input power from wiring 5 and/or input power channels 121, the operational temperature of power supply 120, the power consumption of power supply 120 including client devices such as communication module 126, processor 124, and auxiliary devices 70, time of usage broken down by device, and operational anomalies. Power supply 120 may process the highest electrical load of control unit 180 and may therefore be located proximate the interior surface 44 of housing cover 42 to exchange heat therewith to effectively cool power supply 120. Circuit boards (not shown) for power supply 120 may be wired by a conventional method or engaged by plug-in connectors. Additionally, the circuit boards may be encased or open and may be secured within cavity 58.
Embodiments of IDS 10 may further comprise control unit 80 including control code 81 that may be multi-device relational suite of software configured to operate, control, and otherwise govern auxiliary devices 70 independently or in unison. The suite of software may be configured to analyze a data set received by the control unit 80. The data set may be augmented with additional data captured and/or received from any of the electronic devices or auxiliary devices of the IDS 10, a remote client (e.g., first responder), and/or a remote device (e.g., a cell phone, RFID, or device located on the pole structure 4). Based on the augmented data set, the IDS 10 and/or the network of IDSs 10 may be configured to perform a task. The IDS 10 may be configured to perform the task on a single IDS 10 device and/or a plurality of IDSs 10, electronic devices, and/or remote clients either independently or in conjunction with other IDSs 10, remote clients, and/or remote devices. In addition, processor 124 may be configured to execute control code 81 and thereby receive local device sensory input from one or more auxiliary devices 70 and then compile this information in accordance with pre-programmed instructions. Processed information may then be converted to actionable output to auxiliary devices 70. In addition, processor 124 may be configured to communicate with neighboring IDSs 10 or with other devices remotely located from IDS 10. Processor 124 may direct the communication of sensed information or pre-programmed instructions and/or directives based on sensed information to remote devices or remote clients, such as first responders, police departments, fire and rescue teams, etc. For example, in the case of an ongoing public emergency, the control unit 80, processor 124, and/or communication module 126 may be configured to gather, analyze, and report data and/or information back to the IDS 10. The received information may be transmitted to a remote client such as a first responder and/or the received information may be transmitted to a remote device, such as all cellular phones within a certain vicinity to prompt people to stay away from the area.
Embodiments of IDS 10 may further comprise processor 124 containing resident memory 125 that may be programmed with control code 81 prior to installation in IDS 10 or on mast arm 6, during operational use, or at any time thereafter. For example, programming may be performed by a wired connection to a port, e.g., data line dock 57 connected to port 46 or wirelessly via antenna 47. Likewise, updates to IDS 10 in general, to control code 81, to operational instructions, or to device specific updates may occasionally be performed with occasional device upgrades. Indeed, because housing body 50 is configured with one or more receptacles on its bottom exterior surface, devices 70 may be updated, exchanged, interchanged, or replaced as needed according to device life expectancy, device configuration, or desired capabilities of IDS 10 for the location within the municipality. Embodiments of IDS 10 may further comprise docks 57 and any other similar input ports to IDS 10 being keyed to accept only approved network devices. With docks 57 being keyed to accept only authorized auxiliary devices 70, only those clients, customers, manufacturers that have been approved for working with IDS 10 may be permitted to couple their respective devices 70 thereto. Such keys may be digital access codes or may be programmed into IDS 10 control code 81 or into the software of individual auxiliary devices 70. In the alternative, such keys may be specifically required hardware (i.e., protectable shaped and sized connectors) for use in electrically coupling to IDS 10.
In one embodiment, the IDS 10 may be configured with any suitable system to easily and efficiently access, change out, replace, repair, exchange, or interchange component parts, including auxiliary devices 70. For example, the IDS 10 may be configured with an access door 40 on the lower section 1802 of the housing body 50. One IDS 10 may include some or all of auxiliary devices 70, whereas another IDS 10 may not include some or all of auxiliary devices 70. Many auxiliary devices 70 may be coupled to the underside surfaces of housing 40, whereas other primary components, such as power supply 120, processor 124, and communication module 126 may be accessed simply by removing housing cover 42 from housing body 50. And, because some or all of these devices are equipped with quick connect configurations, each of these devices may be easily removed, installed, or replaced, as needed.
Embodiments of IDS 10 may further comprise control code 81 being scalable by modules, where each module relates to the functionality of an associated device and its relation to other onboard devices and the entire network's devices. Control code 81 may be provided with input tables such as schedules and set points, as well as alert parameters and operational reports. In addition, control code 81 can be customized for specific applications and may include self-learning modules. Processor 124 may have sufficient memory 125 associated therewith to access and act on pertinent information in substantially real time. Substantially real time may comprise near-instantaneous transmission and receiving of information, or instantaneous/simultaneous transmission and/or receiving of information. It is understood that the transmission of information over a large distance may not be in real-time based on the method of transmission, and substantially real time here leaves open the possibility that transmission/receiving is done with a slight delay. For example, if a first IDS 10 captures information related to a parameter of its surrounding environment, that information may be processed by the processor in substantially real time. Additionally, control code 81 may be provided with a self-reporting module associated with each auxiliary device 70 to report the device's operational condition and provide alerts when the device 70 performs outside its optimal performance range.
Embodiments of IDS 10 may further comprise each IDS 10 being assigned a unique address that is associated with the identification information of the pole 2 to which IDS 10 is connected. For example, each pole 2 or IDS 10 may be assigned a unique alphanumeric ID, or the pole 2 may be identified by its location according to GPS coordinates. Based on this unique ID, IDS 10 may be capable of assigning a sub-address to all devices 70 coupled or functionally connected to IDS 10. In this manner, the operational integrity of the various elements of auxiliary devices 70 may be monitored and any anomalies with onboard devices may be alerted, identifying the nature of the anomaly and possible recommendations for action. Information specific to each auxiliary device 70 may be recorded and stored for retrieval upon status inquiry. Information may include device manufacturer, device serial number, date of installation, license renewal alerts, warranty control, device reliability and life expectancy, event records, and maintenance schedules. Moreover, under the condition that an IDS 10 senses an environmental input that triggers a local and/or remote client response, the unique address of the IDS 10 may be communicated to the client(s) to allow the client(s) to arrive at the correct destination to address and/or resolve the situation or problem.
Embodiments of IDS 10 may further comprise IDS 10 functioning as a local environment area manager. For example, control unit 80 and control code 81 may work hand-in-hand to facilitate direct, or via processor 124, communication with onboard auxiliary devices 80. Additionally, communication module 126 may be configured to facilitate communication between onboard auxiliary devices 80, as well as between a plurality of IDSs 10, as well as between local and remote municipality management systems, as well as between local and remote clients, such as first responders, police, fire and rescue, EMTs, and others that may need real time input about a specific location in a part of the community. Communication module 126 may employ radio frequency (RF) communication via antenna 47 to facilitate remote communication with other electronic devices and systems. For example, electronic car 86 may pick up an auditory input or signal from the surrounding environment that is consistent with a preprogrammed auditory input that triggers further action from IDS 10, such auditory input being, for example, the sound of a vehicle collision on or near the roadway. IDS 10, in response to the auditory input and preprogrammed instructions associated therewith, may activate mechanical eye 60 to provide a real time view of the scene. Moreover, IDS 10, in response to the auditory input and preprogrammed instructions, may communicate with remote clients to direct first responders to the scene and may communicate with neighboring IDSs 10 and possibly traffic lights to regulate and direct traffic flow away from or around the scene, as needed. Such capability of IDS 10 to respond to environmental input and perform necessary operations, such as directing IDS 10 operations and communicating with remote clients and devices, may be especially important if the vehicle occupant is disabled by the vehicle collision and cannot perform these functions himself/herself.
IDS 10 may be programmed in similar fashion to respond accordingly to any number of environmental conditions measurable by any of auxiliary devices 70 on IDS 10. As such, auxiliary devices 70 may be utilized in connection with lighting control, traffic control, life safety, loss prevention, asset management functions, and/or operational. optimization.
Lighting control may entail IDS 10 being configured to govern time of use or lighting intensity of luminaire 8. Lighting control may also entail one or more IDSs 10 cooperating with one another to turn on or off or dim as vehicle or pedestrian traffic passes thereunder or thereby. IDS 10 may be programmed to turn luminaire 8 off if IDS 10 does not sense movement thereunder, thus preserving energy consumption and prolonging life expectancy of luminaire 8.
Traffic control may entail IDS 10 being configured to provide local and remote monitoring of traffic patterns, traffic backups, traffic accidents, and roadway obstructions. Traffic control may entail IDS 10 being configured to govern traffic light operations and recommend alternative traffic routes based upon traffic flow and accident reports discovered by one or more IDSs 10 in the community and along roadways. Traffic control may entail IDS 10 being configured to govern traffic light operations to allow first responders to arrive at the scene of an accident or emergency in as little time as possible. Traffic control may entail IDS 10 being configured to govern traffic light operations to allow funeral processions to proceed along roadways with as little interference or traffic flow disruption as possible. Traffic control may entail IDS 10 being configured to monitor crowd control at large public events, such as concerts, swap meets, sporting events, and the like. Audible and/or visible commands may be given by IDS 10 to local and remote devices/client in response to sensed input of crowd density, crowd noise, crowd movement, and the like.
Life safety may entail IDS 10 being configured to provide local and remote monitoring of air quality, including discovering airborne contaminants and threats. As one IDS 10 senses an airborne contaminant, the one IDS 10 may relay this information to neighboring IDSs 10 and other remote devices or remote clients. As such, the network of IDSs 10 may coordinate information and communicate with one another to provide a “safety net” of helpful information over communities and roadways. Life safety may entail IDS 10 being configured to audibly and/or visibly warn surrounding communities and vehicle and pedestrian traffic on roadways of impending danger up along the roadway or approaching danger from behind on the roadway, such as a high-speed chase. Life safety may entail IDS 10 being configured to provide local and remote monitoring of weather patterns and temperature patterns, such as deep freezes, humid conditions, extreme heat, or high winds. Audible and/or visible commands may be given by IDS 10 to local and remote devices/client in response to sensed input of weather conditions, temperature, and the like. Life safety may entail IDS 10 being configured to analyze traffic patterns and traffic flow in and around traffic accidents, traffic emergencies, or other localized non-traffic emergencies, such as fires and the like, to reroute traffic to prioritize optimal routes for first responders. IDS 10 may be configured to locate first responders and, based on their respective positions, anticipate quickest routes by calculating time from current location to arrival on scene, and configure traffic patterns and traffic flow to permit first responders to arrive on scene in as little time as possible. IDS 10 may be configured to divert non-essential traffic to a different route to optimize first responder response.
Loss prevention may entail IDS 10 being configured to monitor public environments for suspicious activity of local and remote clients to prevent theft, crime, or disorderly conduct, or the like via sensory input from auxiliary devices 70 and behavioral software analysis of sensed input. Loss prevention may entail one or more IDSs 10 being configured to monitor location of stolen vehicles or vehicles identified in an AMBER alert operation. One or more IDSs 10 may be configured to have a mechanical eye 60 that may be configured to read vehicle license plate numbers and/or faces and features of pedestrians that pass thereby. Control unit 80 may thereafter process this visual information and communicate the identification and location of the identified vehicle or person in question once discovered. Loss prevention may entail IDS 10 being configured to sound an audible and/or visual alarm for sensed abnormalities, such as unauthorized entry into a vehicle where IDS 10 has been informed the vehicle is not to be entered or unauthorized removal of a vehicle from a parking stall where IDS 10 has been informed the vehicle is not to be moved.
Asset management may entail IDS 10 being configured to visually monitor roadway conditions and markings, such as the presence of potholes in the roadway or the deterioration of paint stripes and pedestrian walkways. Asset management may entail IDS 10 being configured to visually monitor case of vehicle and pedestrian traffic flow to determine if redesign of roadways or walkways or space reallocation is needed.
Operational optimization may entail IDs 10 being configured to monitor energy being used thereby, to monitor and track maintenance history, to record events and keep an event history, and perform device and system performance evaluations, and so forth.
With reference to
With reference to
A feature of IDS 10 is the capability to operate one or several onboard devices from among auxiliary devices 70, such as mechanical eye 60, backup battery 119, metering device 82, drone launch and charging pad 84, electronic car 86 (such as a microphone or other auditory instrument), barometric sensor 88, air quality sensor 90, electrified signage 92, communication device 94, structural integrity sensor 96, wind velocity sensor 98, photovoltaic cell 100, RFID reader 102, radar 104, broadband communication hardware 106 (such as WIFI/WiMAX transponders, transceivers, and other communication gear; 3G, 4G and 5G communication gear), speaker 108, corrosion monitor 110, vibration monitor 112 (such as a piezoelectric sensor), GPS technology 114, power storage unit 116 (such as a battery or backup power unit), radiation sensor 118, seasonal lighting displays, long-term and short-term electrified signage, astronomical clock for keeping and tracking time, thermometer of any variety for measuring one or more temperatures, one or more photocells, and one or more infrared sensors (such as motion sensors) in unison, based on real-time information sensed by these devices 70 and according to processing and directives coordinated by control unit 80 and programmed instructions in control code 81.
A feature of IDS 10 is the capability to perform auto-commissioning of a network of IDSs 10. For example, as mentioned, each IDS 10 may include a discrete address, and sub-addresses for component parts, that may form part of an electronic map showing each IDS 10 by its associated discrete address and its relative location to the entire network of IDSs 10. Auto-commissioning may commence following installation and implementation of IDS 10 on pole 2 to create smart pole 140, wherein IDS 10 marks its place on the electronic map by GPS coordinates.
In one embodiment, the IDS 10 may comprise GPS technology 114. The GPS technology 114 may comprise a global positioning system module configured to receive and/or report information related to the geographical location of the pole structure on which the GPS technology 114 is mounted. The GPS technology 114 may send information to the control unit 80 related to the geographical location of the pole so that repairs may be made. The GPS technology 114 may further be configured to report information to remote clients and/or remote devices.
In one embodiment, the IDS 10 may comprise an accelerometer disposed on/in a portion of the pole structure 4. The accelerometer may comprise any suitable device and/or system configured to measure acceleration, vibration, and/or other related parameters. The accelerometer may be configured to report on the current structural integrity of the pole structure. For example, a pole structure may experience vibrations during an earthquake and/or severe wind conditions which may exceed the structural limitations of the pole structure. The accelerometer may determine using the data set comprising the parameters of the surrounding environment to determine whether the structural limitations of the IDS 10 are exceeded. The accelerometer may be configured to report information related to the structural integrity of the pole structure to a plurality of additional IDSs 10, remote clients, remote devices, electronic devices, and/or auxiliary devices 70.
A related feature of IDS 10 is the capability to function as part of a larger scale mashed wireless network 150. As depicted in
A feature of IDS 10 is the capability to control light from its respective luminaire 8 at its local location. As discussed above, IDS 10 may include mechanical eye 60, communication module 126, processor 124 and/or remote processors. Processor 124 and/or the remote processors may maintain a pre-determined light level by dimming or turning luminaire 8 on or off through processing in real time local zone illumination conditions data obtained by mechanical eye 60 and preprogrammed local or remote controller instructions. Motion detectors may also be utilized to monitor or sense movement to trigger operation of luminaire 8 by IDS 10.
With reference to
A feature of IDS 10 is the capability to optimize local and entire space environmental conditions. Optimization methodology may utilize data from mechanical eye 60, motion detectors, as well as other onboard sensor devices such as processor 124, mechanical car 86, communication module 126, and/or remote processors to process data and act in real time (or substantially real time) on changing conditions while operating within programmatic instruction guidelines.
For example, as depicted in
A feature of IDS 10 is the capability to collect environmental conditions data via mechanical eye 60 and relay the data to local processor 124 and/or remote processors. The data collected by mechanical eye 60 may include, but is not limited to, parking stall occupancy, a traffic count, vehicle load density analysis, time of day activity loads, and photographic and thermal imagery. The processed data obtained by mechanical eye 60 with or without additional information processed from other non-camera devices within IDS 10 facilitate optimal operation of IDS 10. Another feature of IDS 10 is to function as a public announcement, sound, and alarming system through the provision of audio input/output via mechanical car 86 and speaker 108 (mechanical voice). Additionally, mechanical car 86 and speaker 108 (mechanical voice) may be networked with other input/output onboard environment data collection, assessment, and operational devices, and have remote communication capability.
In addition, to optimize the flow of traffic, the IDS can recognize emergency vehicles by sight and/or by signal and can prioritize the vehicular trajectory over all other vehicles including vacating the intersection at the time the emergency vehicle 7 arrives there. The ability to discern speed and direction coupled with the IDS's artificial logic programming results in giving the IDS predictability and self-learning capabilities. That in turn enables the IDS to make decisions including diverting traffic when an event observed puts humans and vehicles in harm's way. In addition to visual capacity, the IDS 10 may include an array of other sensing 61 devices, expanding its capability of sensing activities and anomalies occurring within its assigned zone.
For example, as depicted in
In summary, embodiments described above address a number of the mechanical, thermal, electrical, airborne, and architectural challenges that are commonly associated with community roadways, intersections, walkways, and publicly accessible paths. Furthermore, the mechanical arrangement and electronics assembly of IDS 10 may assume partial or full control over the ambient environment in the vicinity of the IDS, integrating operational logic traditionally associated with isolated disciplines' networks of traffic flow, first response, crowd control, parking monitoring, public safety, air quality monitoring devices, input/output audio devices, temperature and humidity devices, security and normal operation monitoring cameras, occupancy sensors, lighting controls, and so forth. Consequently, the IDS 10 including the mechanical arrangement and the electronics assembly yields significant improvements in terms of the integration of a variety of disciplines associated with community roadways, intersections, walkways, and publicly accessible paths. Moreover, IDS 10 accomplishes all of these without compromising the structural integrity of existing structures (i.e., illumination poles 2) already owned by the community, municipality, and/or citizenry.
The computer readable storage medium may be a tangible device that can store instructions for use by an instruction execution device (processor). The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any appropriate combination of these devices. A non-exhaustive list of more specific examples of the computer readable storage medium includes each of the following (and appropriate combinations): flexible disk, hard disk, solid-state drive (SSD), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash), static random access memory (SRAM), compact disc (CD or CD-ROM), digital versatile disk (DVD) and memory card or stick. A computer readable storage medium, as used in this disclosure, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described in this disclosure can be downloaded to an appropriate computing or processing device (circuitry that is configured to perform operations by execution of code retrieved from memory) from a computer readable storage medium or to an external computer or external storage device via a global network (i.e., the Internet), a local area network, a wide area network and/or a wireless network. The network may include copper transmission wires, optical communication fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing or processing device may receive computer readable program instructions from the network and forward the computer readable program instructions for storage in a computer readable storage medium within the computing or processing device.
Computer readable program instructions for carrying out operations of the present disclosure may include machine language instructions and/or microcode, which may be compiled or interpreted from source code written in any combination of one or more programming languages, including assembly language, Basic, Fortran, Java, Python, R, C, C++, C # or similar programming languages. The computer readable program instructions may execute entirely on a user's personal computer, notebook computer, tablet, or smartphone, entirely on a remote computer or computer server, or any combination of these computing devices. The remote computer or computer server may be connected to the user's device or devices through a computer network, including a local area network or a wide area network, or a global network (i.e., the Internet). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by using information from the computer readable program instructions to configure or customize the electronic circuitry, in order to perform aspects of the present disclosure.
Aspects of the present disclosure are described herein with reference to flow diagrams and block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood by those skilled in the art that each block of the flow diagrams and block diagrams, and combinations of blocks in the flow diagrams and block diagrams, can be implemented by computer readable program instructions.
The computer readable program instructions that may implement the systems and methods described in this disclosure may be provided to one or more processors (and/or one or more cores within a processor) of a general purpose computer, special purpose computer, or other programmable apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable apparatus, create a system for implementing the functions specified in the flow diagrams and block diagrams in the present disclosure. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having stored instructions is an article of manufacture including instructions which implement aspects of the functions specified in the flow diagrams and block diagrams in the present disclosure.
The computer readable program instructions may also be loaded onto a computer, other programmable apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions specified in the flow diagrams and block diagrams in the present disclosure.
Referring to
Additional detail of computer 805 is shown in
Computer 805 may be an embedded processor, a personal computer (PC), a desktop computer, laptop computer, tablet computer, netbook computer, a personal digital assistant (PDA), a smart phone, or any other programmable electronic device capable of communicating with other devices on network 810.
Computer 805 may include processor 835, bus 837, memory 840, non-volatile storage 845, network interface 850, peripheral interface 855 and display interface 865. Each of these functions may be implemented, in some embodiments, as individual electronic subsystems (integrated circuit chip or combination of chips and associated devices), or, in other embodiments, some combination of functions may be implemented on a single chip (sometimes called a system on chip or SoC).
Processor 835 may be one or more single or multi-chip microprocessors, such as those designed and/or manufactured by Intel Corporation, Advanced Micro Devices, Inc. (AMD), Arm Holdings (Arm), Apple Computer, etc. Examples of microprocessors include Celeron, Pentium, Core i3, Core i5 and Core i7 from Intel Corporation; Opteron, Phenom, Athlon, Turion and Ryzen from AMD; and Cortex-A, Cortex-R and Cortex-M from Arm.
Bus 837 may be a proprietary or industry standard high-speed parallel or serial peripheral interconnect bus, such as ISA, PCI, PCI Express (PCI-e), AGP, and the like.
Memory 840 and non-volatile storage 845 may be computer-readable storage media. Memory 840 may include any suitable volatile storage devices such as Dynamic Random Access Memory (DRAM) and Static Random Access Memory (SRAM). Non-volatile storage 845 may include one or more of the following: flexible disk, hard disk, solid-state drive (SSD), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash), compact disc (CD or CD-ROM), digital versatile disk (DVD) and memory card or stick.
Program 848 may be a collection of machine readable instructions and/or data that is stored in non-volatile storage 845 and is used to create, manage and control certain software functions that are discussed in detail elsewhere in the present disclosure and illustrated in the drawings. In some embodiments, memory 840 may be considerably faster than non-volatile storage 845. In such embodiments, program 848 may be transferred from non-volatile storage 845 to memory 840 prior to execution by processor 835.
Computer 805 may be capable of communicating and interacting with other computers via network 810 through network interface 850. Network 810 may be, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, or a combination of the two, and may include wired, wireless, or fiber optic connections. In general, network 810 can be any combination of connections and protocols that support communications between two or more computers and related devices.
Peripheral interface 855 may allow for input and output of data with other devices that may be connected locally with computer 805. For example, peripheral interface 855 may provide a connection to external devices 860. External devices 860 may include devices such as a keyboard, a mouse, a keypad, a touch screen, and/or other suitable input devices. External devices 860 may also include portable computer-readable storage media such as, for example, thumb drives, portable optical or magnetic disks, and memory cards. Software and data used to practice embodiments of the present disclosure, for example, program 848, may be stored on such portable computer-readable storage media. In such embodiments, software may be loaded onto non-volatile storage 845 or, alternatively, directly into memory 840 via peripheral interface 855. Peripheral interface 855 may use an industry standard connection, such as RS-232 or Universal Serial Bus (USB), to connect with external devices 860.
Display interface 865 may connect computer 805 to display 870. Display 870 may be used, in some embodiments, to present a command line or graphical user interface to a user of computer 805. Display interface 865 may connect to display 870 using one or more proprietary or industry standard connections, such as VGA, DVI, DisplayPort and HDMI.
As described above, network interface 850, provides for communications with other computing and storage systems or devices external to computer 805. Software programs and data discussed herein may be downloaded from, for example, remote computer 815, web server 820, cloud storage server 825 and computer server 830 to non-volatile storage 845 through network interface 850 and network 810. Furthermore, the systems and methods described in this disclosure may be executed by one or more computers connected to computer 805 through network interface 850 and network 810. For example, in some embodiments the systems and methods described in this disclosure may be executed by remote computer 815, computer server 830, or a combination of the interconnected computers on network 810.
Data, datasets and/or databases employed in embodiments of the systems and methods described in this disclosure may be stored and or downloaded from remote computer 815, web server 820, cloud storage server 825 and computer server 830.
Circuitry as used in the present application can be defined as one or more of the following: an electronic component (such as a semiconductor device), multiple electronic components that are directly connected to one another or interconnected via electronic communications, a computer, a network of computer devices, a remote computer, a web server, a cloud storage server, a computer server. For example, each of the one or more of the computer, the remote computer, the web server, the cloud storage server, and the computer server can be encompassed by or may include the circuitry as a component(s) thereof. In some embodiments, multiple instances of one or more of these components may be employed, wherein each of the multiple instances of the one or more of these components are also encompassed by or include circuitry. In some embodiments, the circuitry represented by the networked system may include a serverless computing system corresponding to a virtualized set of hardware resources. The circuitry represented by the computer may be a personal computer (PC), a desktop computer, a laptop computer, a tablet computer, a netbook computer, a personal digital assistant (PDA), a smart phone, or any other programmable electronic device capable of communicating with other devices on the network. The circuitry may be a general purpose computer, special purpose computer, or other programmable apparatus as described herein that includes one or more processors. Each processor may be one or more single or multi-chip microprocessors. Processors are considered processing circuitry or circuitry as they include transistors and other circuitry therein. The circuitry may implement the systems and methods described in this disclosure based on computer-readable program instructions provided to the one or more processors (and/or one or more cores within a processor) of one or more of the general purpose computer, special purpose computer, or other programmable apparatus described herein to produce a machine, such that the instructions, which execute via the one or more processors of the programmable apparatus that is encompassed by or includes the circuitry, create a system for implementing the functions specified in the flow diagrams and block diagrams in the present disclosure. Alternatively, the circuitry may be a preprogrammed structure, such as a programmable logic device, application specific integrated circuit, or the like, and is/are considered circuitry regardless if used in isolation or in combination with other circuitry that is programmable, or preprogrammed.
As an example, The IDS member may employ a trained AI engine to assist in detecting an “event”, such as black ice formation, and assist in predicting when the event (e.g., ice formation) will become present based on emerging environmental factors. Although black ice detection (which is discussed in more detail in U.S. patent application Ser. No. 18/084,589, incorporated herein by reference) is an exemplary “event”, other events such as fire, flood, traffic issue (crash), person or pet with certain characteristics, pet, fallen limb, snow, license plate of missing car, potentially dangerous animal (e.g., rapid fox, Javelina, Bear, etc.) may be other events that the AI engine is trained to detect. As shown in
First, the computing device 1000 is trained on images and sensor information provided to it by the sensors and camera(s) of the IDS member. After a subject image is acquired, in order to generate a source vector to be inputted to the data analysis network 3000, the computing device 1000 may instruct the data extraction network 2000 to generate the source vector including (i) a reflectivity of the roadway's surface (shown as “Opt Issue” in
In order to generate the source vector, the computing device 1000 may instruct at least part of the data extraction network 2000 to detect reflectivity (or more generally “optical issue”) and black ice presence (or more generally “event presence”) from the image data from the IDS member. In addition to black ice as an event that the UAV may capture with its imaging camera(s), the data collected by the UAV can be also can be used by a learned AI engine to identify other optically detectable events such as fire, flood, traffic issue (crash), person or pet with certain characteristics, pet, fallen limb, snow, license plate of missing car, potentially dangerous animal (e.g., rapid fox, Javelina, Bear, etc.). Thus, the UAV optionally includes multiple sensors such as cameras, thermal imaging, heat sensors, vibration, barometric, light level, etc. In addition, data from other sensors (e.g., thermometer) may be fused with the optical information to help detect the presence/absence of the event. In the case of black ice detection, a condition of near freezing or below may be used by the AI engine as a weighted factor in determining the presence/absence of black ice. Similarly, IR camera information in addition to optical camera information may be used as weighted input in determining the presence absence of a fire, or a living person or animal. Similarly, microphone data may be fused with the optical data in the AI engine to determine the presence/absence of a car crash, or a limb falling on a road. Furthermore, the receipt of a message from an authority that contains data of a missing person, a missing animal, a license plate number, etc. may be used fused with the optical information from the camera to determine a presence or absence of the missing person, missing animal or license plate number.
Specifically, the computing device 1000 may instruct the first feature extracting layer 210 to apply at least one first convolutional operation to the subject image and sensor data, to thereby generate at least one subject feature map. Thereafter, the computing device 1000 may instruct the ROI pooling layer 220 to generate one or more ROI-Pooled feature maps by pooling regions on the subject feature map and/or sensor data, corresponding to ROIs on the subject image, and/or senor data file which have been acquired from a Region Proposal Network (RPN) interworking with the data extraction network 2000. And, the computing device 1000 may instruct the first outputting layer 230 to generate at least one estimated reflectivity. That is, the first outputting layer 230 may perform a classification and a regression on the subject image and sensor file, by applying at least one first Fully-Connected (FC) operation to the ROI-Pooled feature maps, to generate each of reflectivity and black ice formation detection (in this example), including information on coordinates of each of bounding boxes on a specific area within a predetermined area patrolled by the UAV. Moreover the predetermined area is an area within communication coverage range of the UAV to a first IDS (first pole structure) or another IDS (or second pole structure). Generally, the IDS's are arranged so that the communication range from any of the IDSs to the UAV covers the geographic reason of interest. For example, the IDSs may be arranged linearly along a roadway, if the UAV's patrol area is a neighborhood street. The IDSs may always be arranged in a 2-dimentional geographic pattern (e.g., circular layout) so the predetermined area is more of a circular area of interest. The UAV may be controlled by the computer 805 to self-direct a route of the UAV within the patrol area. The self-directed route based on a likelihood of a predicted event occurring at a particular destination within the area based on input from an on-board sensor and an assigned priority weight.
After such detecting processes are completed, by using the estimated reflectivity and black ice formation detection, the computing device 1000 may instruct the data vectorizing layer 240 to subtract a y-axis coordinate of an upper bound of the ground from a y-axis coordinate of the lower boundary of the region surrounding probe to generate the apparent reflectivity and ice detection associated with the content sensor file from region of the roadway, and multiply the detected value with an estimated area to generate the apparent reflectivity and black ice presence for that area.
After the apparent reflectivity and black ice formation for the area is acquired, the computing device 1000 may instruct the data vectorizing layer 240 to generate at least one source vector including the reflectivity and estimated ice presence as its at least part of components.
Then, the computing device 1000 may instruct the data analysis network 3000 to calculate an estimated ice presence by using the source vector. Herein, the second feature extracting layer 310 of the data analysis network 3000 may apply second convolutional operation to the source vector to generate at least one source feature map, and the second outputting layer 320 of the data analysis network 3000 may perform a regression, by applying at least one FC operation to the source feature map, to thereby calculate the estimated ice presence.
As shown above, the computing device 1000 may include two neural networks, i.e., the data extraction network 2000 and the data analysis network 3000. The two neural networks should be trained to perform said processes properly. Below, how to train the two neural networks will be explained by referring to
First, by referring to
Herein, the data vectorizing layer 240 may have been implemented by using a rule-based algorithm, not a neural network algorithm. In this case, the data vectorizing layer 240 may not need to be trained, and may just be able to perform properly by using its settings inputted by a manager.
As an example, the first feature extracting layer 210, the ROI pooling layer 220 and the first outputting layer 230 may be acquired by applying a transfer learning, which is a well-known prior art, to an existing object detection network such as VGG or ResNet, etc.
Second, by referring to
After performing such training processes, the computing device 1000 can properly calculate the estimated ice presence detection level by using the subject image including the scene photographed from the IDS member and from sensor levels.
Once a determination of the event's presence or absence is determined, the UAV and/or the IDS that communicates with the UAV, or a remote device, generates an electronic message that is transmitted to a predetermined audience (e.g., email, SMS, web-page, etc.) that informs the interested parties (e.g., neighborhood members) of the event status (e.g., presence, absence, or on-watch).
Obviously, numerous modifications and variations of the present disclosure are possible in light of the above teachings. It is therefore to be understood that within the scope of the appended claims, the disclosure may be practiced otherwise than as specifically described herein.
While the principles of the disclosed subject matter have been described in connection with specific apparatus configurations described above, it is to be clearly understood that this description is made only by way of example and not as a limitation on the scope of the disclosed subject matter. For example, embodiments may be implemented in systems having other architectures as well. The various functions or processing blocks discussed herein and illustrated in the Figures may be implemented in hardware, firmware, software or any combination thereof. Further, the phraseology or terminology employed herein is for the purpose of description and not of limitation.
While this disclosure has been described in conjunction with the specific embodiments outlined above, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, the preferred embodiments of the present disclosure as set forth above are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the present disclosure, as required by the following claims. The claims provide the scope of the coverage of the present disclosure and should not be limited to the specific examples provided herein.
The particular implementations shown and described are illustrative of the invention and its best mode and are not intended to otherwise limit the scope of the present invention in any way. Indeed, for the sake of brevity, conventional manufacturing, connection, preparation, another functional aspects of the system may not be described in detail.
Furthermore, the connecting lines shown in the various figures are intended to represent exemplary functional relationships and/or steps between the various elements. Many alternative or additional functional relationships or physical connections may be present in a practical system.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments. Various modifications and changes may be made, however, without departing from the scope of the present invention as set forth in the claims. The specification and figures are illustrative, rather than restrictive, and modifications are intended to be included within the scope of the present invention. Accordingly, the scope of the invention should be determined by the claims and their legal equivalents rather than by merely the examples described.
For example, the steps recited in any method or process claims may be executed in any order and are not limited to the specific order presented in the claims. Additionally, the components and/or elements recited in any apparatus claims may be assembled or otherwise operationally configured in a variety of permutations and are accordingly not limited to the specific configuration recited in the claims.
Benefits, other advantages and solutions to problems have been described above with regard to particular embodiments; however, any benefit, advantage, solution to problem or any element that may cause any particular benefit, advantage or solution to occur or to become more pronounced are not to be construed as critical, required or essential features or components of any or all the claims.
As used herein, the terms “comprise”, “comprises”, “comprising”, “having”, “including”, “includes” or any variation thereof, are intended to reference a non-exclusive inclusion, such that a process, method, article, composition or apparatus that comprises a list of elements does not include only those elements recited, but may also include other elements not expressly listed or inherent to such process, method, article, composition or apparatus. Other combinations and/or modifications of the above-described structures, arrangements, applications, proportions, elements, materials or components used in the practice of the present invention, in addition to those not specifically recited, may be varied or otherwise particularly adapted to specific environments, manufacturing specifications, design parameters or other operating requirements without departing from the general principles of the same.
The present application is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 18/084,589, filed Dec. 20, 2022, which is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 17/334,722, filed May 29, 2021, which is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 16/841,399, filed Apr. 6, 2020 (now U.S. Pat. No. 11,071,204); which is a continuation-in-part of and claims priority to U.S. patent application Ser. No. 16/242,666, filed Jan. 8, 2019 (now U.S. Pat. No. 10,653,014); which is a continuation application of and claims priority to U.S. patent application Ser. No. 15/884,107, filed Jan. 30, 2018 (now U.S. Pat. No. 10,215,351); which is a continuation application of U.S. patent application Ser. No. 14/757,923, filed Dec. 28, 2015 (now U.S. Pat. No. 9,885,451); which is a continuation-in-part application of and claims priority to U.S. patent application Ser. No. 14/166,056, filed Jan. 28, 2014 (now U.S. Pat. No. 9,829,185); which in turn claims the benefit of the earlier filing date of U.S. Provisional Application No. 61/767,035, filed Feb. 20, 2013, and incorporates by reference each of the above applications/patents in their entireties. To the extent any amendments, characterizations, or other assertions previously made (in this or in any of the above-cited patent applications and/or patents) with respect to any art, prior or otherwise, could be construed as a disclaimer of any subject matter supported by the present disclosure of this application, Applicant hereby rescinds and retracts such disclaimer. Applicant also respectfully submits that any prior art previously considered in any related patent applications or patents, including any parent, sibling, or child, is expected to be revisited by the Office as part of the examination of the subject application.
| Number | Date | Country | |
|---|---|---|---|
| 61767035 | Feb 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15884107 | Jan 2018 | US |
| Child | 16242666 | US | |
| Parent | 14757923 | Dec 2015 | US |
| Child | 15884107 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 18084589 | Dec 2022 | US |
| Child | 19037566 | US | |
| Parent | 17334722 | May 2021 | US |
| Child | 18084589 | US | |
| Parent | 16841399 | Apr 2020 | US |
| Child | 17334722 | US | |
| Parent | 16242666 | Jan 2019 | US |
| Child | 16841399 | US | |
| Parent | 14166056 | Jan 2014 | US |
| Child | 14757923 | US |
