The following generally relates to an electronic tracking device and charging apparatus.
Tracking objects in a physical space can be difficult, as people and things move freely and sometimes unexpectedly. Electronic tracking devices can be put on people and things. These tracking devices require an apparatus to provide an electrical charge.
Embodiments will now be described by way of example only with reference to the appended drawings wherein:
It will be appreciated that for simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the example embodiments described herein. However, it will be understood by those of ordinary skill in the art that the example embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the example embodiments described herein. Also, the description is not to be considered as limiting the scope of the example embodiments described herein.
It will be appreciated that one beacon can be attached to one or more light sources.
The beacon controls the blinking pattern of each light emitting tracking device. The beacon includes, for example, a controller that controls one or more blinking patterns and a power source (e.g. a battery) to power the lights in the light emitting tracking device. The beacon, for example, also includes a wireless transceiver to wirelessly transmit and receive data.
In an example aspect the light source 121 emits light that is detected by one or more optical sensors 102a, 102b, 102c (e.g. cameras). Preferably, there are two or more optical sensors to track a light source in multiple dimensions (e.g. X, Y, Z dimensions). For example, the optical sensors 102a, 102b, 102c are positioned overhead and capture images of the light emitted from a given light source 120. The optical sensors transmit the captured video data and time code information via a data network 101. A tracking server 103, which is also connected to the data network 101, receives the captured video data from the optical sensors then processes the images using image recognition to identify the position of the light sources in the images. The position information from the different optical sensors are then compared (e.g. using triangulation) by the tracking server 103 to determine the location of a given beacon in three-dimensional space.
In an example aspect, the light sources emit infrared light and the optical sensors 102a, 102b, 102c detect the infrared light. In other words, the optical sensors are infrared cameras. In an alternative embodiment, a light in a different range of the light spectrum is emitted and is detected by the optical sensors 102a, 102b, 102c.
In an example aspect, a light source is an infrared light emitting diode (LED). The infrared light is not visible to people's eyes, but can be detected by the optical sensors.
In an example embodiment, each of the light sources 121a, 121b, 121c, 121d, 121e emit light at a different blinking pattern or blinking frequency. The blinking pattern or the blinking frequency represents an identifier (ID) that is specific to each light source, and is mapped to a specific beacon. In other words, the light source 121a has a first ID and accordingly blinks according to a first blinking pattern or blinking frequency that is associated with the first ID, and the light source 121b has a second ID and accordingly blinks according to a second blinking pattern or blinking frequency that is associated with the second ID. These blinking patterns or blinking frequencies are controlled by the beacon 120a to which the light emitting tracking device is connected.
In other words, over a series of images, the tracking server 103 can detect the blinking pattern of a given light source to identify its associated ID. In this way, the tracking server can track the position and movement of multiple light sources simultaneously.
Furthermore, the beacon 120a also includes an inertial measurement unit (IMU) and other sensors that measure the relative position and orientation of the beacon 120a. This inertial information is sent to the tracking server 103, and this inertial information combined with the optical positioning information provides a robust and accurate tracking system for position or orientation, or both. It will be appreciated that different computations can be used to merge the sensor data from the IMU of the beacon and the sensor data from the optical sensors.
In an example embodiment, the data network 101 is a network switch. In a further example embodiment, the data network 101 is an Ethernet network.
In an example aspect, a time keeper device 104 is connected to the data network 101 to synchronize other devices that are connected to the data network, such as the optical sensors 102a, 102b, 102c, the tracking server 103 and one or more charging stations 110a, 110n, 110o, 110p. Other devices in the system 100 may have their own time keeping devices.
One or more charging stations 110a, 110n, 110o, 110p have charge ports that hold beacons 120c, 120d, 120e and more for providing electrical charging as well as beacon setting management.
In an example embodiment, a given charging station 110n is connected to the data network 101 via wired connection, and one or more other charging stations 110o and 110p are connected to the given charging station 110n in a daisy chain manner. For example, the charging station 110o is connected via a wire to the charging station 110n, and the charging station 110p is connected via a wire to the charging station 110o. In this way, these daisy chained charging stations 110o and 110p are also in data communication with the data network 101.
In an example embodiment, data from the beacons 120a, 120b, etc. are transmitted to the one or more charging stations 110a, 110n, etc. so that current data from the beacons can be displayed by one or more of the charging stations. For example, battery data about a given beacon is wirelessly transmitted to a given charging station, and a display device on the charging station displays this battery data.
In another example embodiment, data from a given charging station is transmitted to one or more beacons. This data can be used to affect the operation of the beacon (e.g. modify blinking settings for the light source, display a message, display an indicator, change a sensor mode, etc.). For example, a charging station wirelessly transmits data to a beacon and, after receiving this data, the beacon is triggered to display a message or an indicator to return the beacon to the charging station. In another example, a charging station wirelessly transmits data to a beacon and, after receiving this data, the beacon is triggered to activate a blinking light source at a higher brightness level or a lower brightness level.
More generally, according to an example embodiment, data is communicated between one or more beacons and one or more charging stations over the data network 101.
In an example embodiment, the system of devices and components shown in
In an example embodiment, the display screen 201 is an electronic paper display (EPD), which uses electronic ink to display images or text, or both. This type of display consumes very little energy. For example, little or no electrical energy is used to hold a static image or text on the display screen. It will be appreciated that other types of currently known and future known display screens can be incorporated into the beacon.
The data from the sensors is transmitted from the beacon to the tracking server 103 using the wireless communication subsystem, and the tracking server 103 uses this information to compute the position or orientation, or both, of the beacon. Information about the battery use, including remaining charge information (e.g. as a percentage or as time remaining, or both), is also transmitted using the wireless communication subsystem to one or more charging stations 110, so that the one or more charging stations can display remaining battery charge information for the given beacon.
The beacon ID or other settings, or both, can be configured on the beacon itself using the display screen and one or more buttons, and this information is also transmitted to the tracking server 103 or to the one or more charging stations 110, or to both.
The beacon also detects when a working light source is connected to a given port 215a, 215b, 215c, etc., and this information is displayed on the display screen 201. In this way, a user can visually discern if a light source connected to a port in the beacon is emitting light or not. It will be appreciated that when using an infrared light source (e.g. infrared LED), a user cannot see whether the light source is working by looking at the infrared light source. An indicator that is visible to the user, such as on the display screen 201, informs the user.
In another example embodiment, the visual indicator corresponding to each activated port (e.g. ports 215a, 215b, 215c, etc.) can also be positioned as a dedicated light indicator device on the beacon body. In another example embodiment, a light indicator device is integrated into the wire (e.g. positioned on the plug of the wire) of the light source (e.g. the infrared light sources 121s, 121r, etc.), and the light indicator device is activated when the attached given infrared light source is activated to pulse by the beacon.
The visual indicator device for indicating that a given port 215a, 215b, 215c, etc. is being activated to pulse a light source 121s, 121r, etc. can be integrated into the beacon in different ways or integrated into a corresponding wire in different ways. The visual indicator device is also herein referred to as a working indicator.
In another example aspect, the wired communication subsystem 213 allows the option for the beacon to connect to an external device 220. The external device 220 connects to the beacon to, for example, do one or more of the following: provide additional data to the beacon, to provide commands to the beacon, to provide additional power to the beacon, to obtain data from the beacon, to obtain power from the beacon, etc. In an example aspect, the external device 220 increases the operational capacity of the beacon, such as by sensing additional data and providing the additional data to the beacon. In another example, the external device 220 is an external mobile battery that provides further power to the beacon. In another example, the external device 220 includes long range wireless communication systems that increases the distance at which the beacon can receive or transmit, or both, data with the tracking server 103.
In another example embodiment, shown in
Also shown in
It will also be appreciated that data from the beacon can be read or written, or both, using the wired communication subsystem 213 when the beacon is physically connected to a charging station.
The surface 301d has positioned thereon the one or more ports 215a, 215b, 215c for respectively connecting to the one or more wires with the light sources. For example, the light source 121s is connected to a wire 304 that connects to a plug 303. The plug 303 is received by a receptacle that is the port 215c. The plug and receptacle include together form a quick-connect and quick-disconnect mechanism. For example, this mechanism is a spring-loaded locking and unlocking mechanism. For example, in use, a user pushes the plug to unlock the plug from the receptacle, and pulls the plug in an opposite direction to lock the plug into the receptacle.
The surface 301c has positioned thereon a physical port 302 that connects to the wired communication subsystem 213 and to the battery 211. For example, the port 302 is a female connector according to a USB format. In an example implementation, the port 302 is a female USB-C connector. It will be appreciated that alternative types of data ports and power connectors can be used. The surface 301c also has positioned thereon another button 205c.
The number of buttons and positions of the buttons can vary from the embodiment shown.
The front surface 301e of the housing 301 has positioned thereon the display screen 201.
The rear surface 301f of the housing 301 includes one or more physical features 303 (e.g. indents or protrusions, or both) that allow for other mechanical devices to be connected to the rear surface 301f. For example, a clip can be connected to the rear surface 301f. In another example, a mounting pad is connected to the rear surface, so that the beacon is mountable onto another object.
Turning to
In an example aspect, pressing one of the buttons 205a, 205b, 205c momentarily illuminates the display. In dark or low-light environments, this helps a user to see the GUIs displayed on the display.
From the home screen, a user can press one of the buttons to navigate to the menu screen 410 shown in
After the status option is selected, the status screen is displayed. An example embodiment of a status screen 420 is shown in
After the configuration option is selected, one or more configuration options are provided to change a setting of the beacon, or to change an ID of the beacon, or both.
Changes to the beacon ID or changes to one or more other settings of the beacon, or both, that are made via the GUI on the beacon, are transmitted to the data network 101 and propagated to a tracking server 103 or to one or more charging stations 110a, 110n, or to both.
Turning to
The communication module 506 connects to the data network 101 preferably using a wired communication subsystem 507. The wired communication subsystem 507 also facilitates daisy chaining of multiple charging stations. The communication module can include a wireless communication subsystem 508 for connection to the data network 101, either in alternative or in addition to the wired communication subsystem. The memory 509 includes device manager software 510 to monitor, modify and control parameters and settings of the beacons, as well as the charging station itself.
Each of the charging ports 515a, 515b, etc. include one or more connectors that mates with a given beacon to provide power to the given beacon as well as to facilitate data communication with the given beacon.
Turning to
In
Using the touch screen display 501 and the device manager software, beacon settings can be monitored and changed.
In an example aspect, the touch screen display 501 is a lighted display (e.g. emits light) so that the GUIs presented on the touch screen display are visible in dark or low-light environments.
In the top-down view of
The general status GUI 604 on the screen 501 displays status information associated with each charging port. For example, status information 603a about the charging port 515a is positioned next to the charging port 515a and it includes the battery status of the associated beacon (e.g. beacon 120b in the charging port 515a), the associated name, and the beacon ID. Similar status information 603e is shown in relation to the charging port 515e for the beacon 120a.
Status information 603h is also displayed for a given beacon that is not currently positioned in the charging port 515h. In other words, the charging port 515h is associated with or assigned to a given beacon (e.g. for Captain Marvel having ID 170). The battery information and other status information is wirelessly transmitted from the Captain Marvel beacon to the data network 101 and to the charging station, and this information is used to update the status information 603h.
In another example aspect, the charging port 515d is not assigned to any beacon and the status information 603d shows the same.
When the screen 501 detects a touch input over the status information 60e, more information and settings are shown as per the GUI 605 shown in
In particular, the GUI 605 shows detailed settings about the beacon associated with Captain America. In an example aspect, an indicator 606 indicates the position of the associated charging port. These settings can be modified using the touch screen display 501. Values, options buttons, numbers, and text can be inputted using various graphical controls. The graphical controls can include a virtual touch-screen keyboard that appears as appropriate (e.g. selecting a text field).
The settings include the beacon name, the product information (e.g. zone information), preset conditions and processes, beacon ID, wireless channel, subnet and light source brightness. These settings are modifiable on the charging station GUI. By modifying one or more of these settings in the GUI, these one or more modified settings are transmitted from the charging station to the beacon, via the charging port. It will be appreciated that these settings are just for example. Other settings can be used in alternative or in addition. The serial number of the beacon is also shown.
Turning to
After the insertion and update of information about the beacon 120c, in this example, the beacon 120c has low power (e.g. 30% battery charge) and is currently assigned to Hulk and has beacon ID 145. For example, an actor for the Hulk however, desires a beacon with full battery charge immediately, while an actor for Captain America is okay to use a beacon with a low battery charge or has time to wait for a battery to charge to full capacity.
The screen 501 detects a user input that includes a touch, drag, and release gesture that starts at the position of the status information 603d (by the charging port 515d) and ends at the position of the status information 603e (by the charging port 515e). After detecting this gesture, the charging station automatically switches the beacon ID and associated settings between the beacons 120c and 120a. The subsequent GUI 604b after the gesture is shown in
In particular, in
The actor for the Hulk can now take the beacon 120a. This allows for a very quick swap of beacons, as well as beacon settings.
It is appreciated that any updates and actions that take place at the charging station can be propagated throughout the system. For example, updated beacon IDs and settings, where applicable, are transmitted from the charging station to one or more of: the tracking server 103; one or more other charging stations; and the relevant beacon(s).
In an example embodiment, the device manager software on the charging station is used to remotely modify a setting of one or more beacons, even if the one or more beacons are not positioned in a charging port on the charging station.
Turning to
Block 701: The charging station receives user input via the touch screen to set a beacon ID, or to modify another beacon setting, in association with a given charging port (also referred to as “CP” in
Block 702: The charging station maps the beacon ID or setting(s), or both, to the given charging port and displays the beacon settings next to the given charging port.
Block 703: The charging station determines if a beacon is currently inserted into the given charging port. If so, the process continues to block 704. If not, the process continues to block 706.
Block 704: The charging station transmits a write command from the given charging port to the beacon with the updated beacon ID or updated setting(s), or both.
Block 705: Following block 704, after the beacon in the given charging port receives the write command, the beacon updates its local memory with the updated information.
Block 706: Following block 703, the charging station determines if there is a beacon in the system 100 that currently uses the subject beacon ID. If so, the process continues to block 707. If not, the process continues to block 709.
Block 707: The charging station obtains the status information about the beacon with the beacon ID. This status information is obtained from the data network 101 (e.g. from another charging station, from the beacon itself, from the tracking server, etc.).
Block 708: Following block 707, the charging station displays the beacon's status information having the beacon ID next to the given charging port.
Block 709: If there is no beacon that currently is assigned to the beacon ID (e.g. for a new beacon ID), then the new beacon ID and associated settings are displayed next to the given charging port. The charging station also displays an indicator that the no beacon is currently mapped to the new beacon ID and the related settings.
Action 710: Following block 709, a beacon is inserted into the given charging port.
Following action 710, block 704 and 705 are executed.
Below are general example embodiments.
In an example embodiment, a tracking beacon comprises: an electronic display; a processor; one or more buttons; one or more ports for connecting to and powering one or more infrared light sources; a communication module; a battery; and memory that stores thereon a beacon ID and a corresponding blinking pattern for the one or more infrared lights, and further storing thereon a GUI that is displayed on the electronic display. The GUI displays the beacon ID assigned to the tracking beacon.
In an example aspect, the memory stores multiple beacon IDs that respectively correspond to multiple blinking patterns for controlling the one or more infrared lights, and selection and activation of a given beacon ID and a corresponding given blinking pattern is navigated through the GUI using the one or more buttons.
In another example aspect, the electronic display is an electronic paper display.
In another example aspect, the GUI comprises one or more working indicators positioned on the electronic display in relation to the one or more ports, and wherein a given working indicator indicates if a given infrared light source is connected to a given port and is emitting infrared light.
In another example aspect, the GUI includes a graphical control, which are activated using the one or more buttons, to modify a setting of the tracking beacon.
In another example aspect, the graphical control changes the beacon ID currently associated with the tracking beacon to a new beacon ID, which automatically modifies the blinking pattern to a new blinking pattern of the one or more light infrared light sources.
In another example aspect, after detecting a given one of the one or more buttons is activated, momentarily illuminating the electronic display.
In another example aspect, the tracking beacon further comprises one or more working indicators positioned in corresponding relation to the one or more ports, and, activating a given working indicator corresponding to a given port when the tracking beacon activates a given infrared light source connected to the given port.
In another example aspect, the tracking beacon further comprises a wired communication port that receives power to charge the battery and data from an external device. In another example aspect, via the wired communication port, the tracking beacon receives and stores a new beacon ID and a corresponding new blinking pattern for the one or more infrared light sources.
In another example aspect, the tracking beacon further comprises a barometer, and data from the barometer is transmitted along with a beacon ID using the communication module.
In another example aspect, the tracking beacon further comprises a wired communication port configured to receive power and exchange data; and the wired communication port is connected to an external device that comprises one or more additional infrared light sources that are controllable by the tracking beacon via the wired communication port.
In another example embodiment, a system is provided for charging and interacting with tracking beacons. The system comprises a charging station for charging one or more tracking beacons, and the charging station comprising a housing, a display, one or more charging ports that are configured to each receive a tracking beacon. Each of the one or more tracking beacons comprises a housing, an electronic display, one or more buttons, one or more ports for connecting to and powering one or more infrared lights, a processor, a communication module, memory, a battery, and a wired communication port for connecting to a given charging port of the charging station. A given tracking beacon is connected to the given charging port of the charging station receives power from the charging station, and at least one of sends and receives data to and from the charging station. The data comprises a beacon ID and a corresponding blinking pattern for the one or more infrared lights.
In an example aspect, the given tracking beacon receives time synchronization data from the charging station via the wired communication port.
In another example aspect, the charging station comprises multiple charging ports that are positioned at one or more edges of the display, and the display shows beacon IDs positioned beside and corresponding to each of the charging ports.
In another example aspect, after the given tracking beacon is removed from the given charging port, the given tracking beacon wirelessly transmits status data to the charging station, and the status data is shown on the display of the charging station.
In another example aspect, after the given tracking beacon is removed from the given charging port, the charging station receives an input to change a setting of the given tracking beacon, the charging station wirelessly transmits settings data to the given tracking beacon, and the given tracking beacon changes the setting using the settings data. In another example aspect, the input is user input received via a graphical user interface shown by the display of the charging station.
In another example aspect, the beacon ID is stored and displayed on the tracking beacon, and after it is connected to the given charging port, the beacon ID is automatically transmitted to the charging station and displayed on the display of the charging station.
In another example embodiment, a charging station for charging tracking beacons is provided. The charging station comprises: a housing that comprises a touch screen display and charging ports that are configured to each receive a tracking beacon; a processor; a power supply; a communication module; and memory comprising device manager software, the device manager software including a GUI that is displayed on the touch screen display. The charging station receives user inputs via the GUI configured to update one or more settings of a given tracking beacon.
In an example aspect, each of the charging ports are positioned close to any edge of the touch screen display.
In another example aspect, a beacon setting update is made via the GUI in relation to an empty charging port and, after the given tracking beacon is inserted into the empty charging port, the given tracking beacon is automatically updated with the beacon setting update.
In another example aspect, the charging station further comprises a time keeping device, and the charging station transmits time synchronization data from the time keeping device via one or more of the charging ports.
In another example aspect, a first beacon ID is displayed beside a first charging slot and a second beacon ID is displayed beside a second charging slot, and responsive to receiving a touch gesture to switch positions between the first beacon ID with the second beacon ID, the charging station updates the touch screen display to show the first beacon ID beside the second slot and the second beacon ID beside the first slot.
In another example embodiment, a tracking beacon includes: an electronic paper display; a processor; one or more buttons; one or more ports for connecting to and powering one more light sources; a communication module; a battery; and memory that comprises a GUI that is displayed on the electronic paper display, and the GUI is navigated using the one or more buttons.
In an example aspect, the GUI comprises one or more working indicators positioned in relation to the one or more ports, and wherein a given working indicator indicates if a given light source is connected to a given port and is emitting light.
In another example aspect, the GUI includes a graphical control, which are activated using the one or more buttons, to modify a setting of the beacon.
In another example embodiment, a tracking beacon includes: a housing that comprises a display, one or more buttons, and ports for connecting to and powering one more light sources, each of the ports positioned close to any edge of the display; a processor; a communication module; a battery; and memory that comprises a GUI that is displayed on the display. The GUI is navigated using the one or more buttons, and wherein the GUI comprises one or more working indicators positioned on the display in relation to positions of the ports. A given working indicator indicates if a given light source is connected to a given port and is emitting light.
It will be appreciated that any module or component exemplified herein that executes instructions may include or otherwise have access to computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, EEPROM, flash memory or other memory technology, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the servers or computing devices or nodes, or accessible or connectable thereto. Any application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media.
It will be appreciated that different features of the example embodiments of the system, the devices, and the components as described herein, may be combined with each other in different ways. In other words, different devices, modules, operations, functionality and components may be used together according to other example embodiments, although not specifically stated.
It will also be appreciated that the examples and corresponding system diagrams used herein are for illustrative purposes only. Different configurations and terminology can be used without departing from the principles expressed herein. For instance, components and modules can be added, deleted, modified, or arranged with differing connections without departing from these principles.
Although the above has been described with reference to certain specific embodiments, various modifications thereof will be apparent to those skilled in the art without departing from the scope of the claims appended hereto.
This patent application is a continuation of U.S. patent application Ser. No. 17/095,311 filed on Nov. 11, 2020 and titled “Electronic Tracking Device and Charging Apparatus”, which claims priority to United States Patent Application No. 62/934,215 filed on Nov. 12, 2019 and titled “Electronic Tracking Device And Charging Apparatus”, the entire contents of which are herein incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4542291 | Zimmerman | Sep 1985 | A |
4631676 | Pugh | Dec 1986 | A |
4665928 | Linial | May 1987 | A |
4988981 | Zimmerman | Jan 1991 | A |
5229756 | Kosugi | Jul 1993 | A |
5347387 | Rice | Sep 1994 | A |
5372365 | McTeigue | Dec 1994 | A |
5429140 | Burdea | Jul 1995 | A |
5513854 | Daver | May 1996 | A |
5524637 | Erickson | Jun 1996 | A |
5583478 | Renzi | Dec 1996 | A |
5638300 | Johnson | Jun 1997 | A |
5641288 | Zaenglein, Jr. | Jun 1997 | A |
5790076 | Sypniewski | Aug 1998 | A |
5826578 | Curchod | Oct 1998 | A |
5844824 | Newman | Dec 1998 | A |
5846086 | Bizzi | Dec 1998 | A |
5913727 | Ahdoot | Jun 1999 | A |
5914701 | Gersheneld | Jun 1999 | A |
5930741 | Kramer | Jul 1999 | A |
5963891 | Walker | Oct 1999 | A |
6005548 | Latypov | Dec 1999 | A |
6097369 | Wambach | Aug 2000 | A |
6353932 | Stembridge | Mar 2002 | B2 |
6512947 | Bartholome | Jan 2003 | B2 |
6597443 | Boman | Jul 2003 | B2 |
6691074 | Moriya | Feb 2004 | B1 |
6701296 | Kramer | Mar 2004 | B1 |
6710713 | Russo | Mar 2004 | B1 |
6757068 | Foxlin | Jun 2004 | B2 |
6909420 | Nicolas | Jun 2005 | B1 |
6984208 | Zheng | Jan 2006 | B2 |
7046151 | Dundon | May 2006 | B2 |
7292151 | Ferguson | Nov 2007 | B2 |
7331871 | Lopez | Feb 2008 | B2 |
7602301 | Stirling | Oct 2009 | B1 |
7698830 | Townsend | Apr 2010 | B2 |
7705736 | Kedziora | Apr 2010 | B1 |
7712365 | James | May 2010 | B1 |
7725279 | Luinge | May 2010 | B2 |
7755602 | Tremblay | Jul 2010 | B2 |
7774155 | Sato | Aug 2010 | B2 |
7821407 | Shears | Oct 2010 | B2 |
7980141 | Connor | Jul 2011 | B2 |
8019121 | Marks | Sep 2011 | B2 |
8089458 | Barney | Jan 2012 | B2 |
8231506 | Molyneux | Jul 2012 | B2 |
8313379 | Ikeda | Nov 2012 | B2 |
8323106 | Zalewski | Dec 2012 | B2 |
8328691 | Lanfermann | Dec 2012 | B2 |
8636605 | Rose | Jan 2014 | B2 |
8639666 | Densham et al. | Jan 2014 | B2 |
8854594 | Densham | Oct 2014 | B2 |
8938431 | Densham et al. | Jan 2015 | B2 |
9055226 | Densham | Jun 2015 | B2 |
9104373 | Lechman | Aug 2015 | B1 |
9177387 | Marks | Nov 2015 | B2 |
9350923 | Densham | May 2016 | B2 |
9538156 | Densham et al. | Jan 2017 | B2 |
9573056 | Marks | Feb 2017 | B2 |
9582072 | Connor | Feb 2017 | B2 |
9747697 | Densham et al. | Aug 2017 | B2 |
9822956 | Eichel | Nov 2017 | B2 |
9823634 | Densham et al. | Nov 2017 | B2 |
10279254 | Mikhailov | May 2019 | B2 |
10437658 | Alonso | Oct 2019 | B2 |
10455874 | Okumiya | Oct 2019 | B2 |
11287505 | Densham | Mar 2022 | B2 |
11342799 | Yang | May 2022 | B2 |
11599257 | Densham et al. | Mar 2023 | B2 |
20020036617 | Pryor | Mar 2002 | A1 |
20020114076 | Dickson et al. | Aug 2002 | A1 |
20020158131 | Dickson et al. | Oct 2002 | A1 |
20030014212 | Ralston | Jan 2003 | A1 |
20040016812 | Schmidt et al. | Jan 2004 | A1 |
20040143176 | Foxlin | Jul 2004 | A1 |
20040219498 | Davidson | Nov 2004 | A1 |
20050127185 | Wilz et al. | Jun 2005 | A1 |
20070021208 | Mao | Jan 2007 | A1 |
20070192910 | Vu et al. | Aug 2007 | A1 |
20070250286 | Duncan | Oct 2007 | A1 |
20100105475 | Mikhailov et al. | Apr 2010 | A1 |
20100164862 | Sullivan | Jul 2010 | A1 |
20120025945 | Yazadi | Feb 2012 | A1 |
20120050535 | Densham | Mar 2012 | A1 |
20120143093 | Stirling | Jun 2012 | A1 |
20120235579 | Chemel et al. | Sep 2012 | A1 |
20140274309 | Nguyen | Sep 2014 | A1 |
20140320667 | Densham et al. | Oct 2014 | A1 |
20150097946 | Stout et al. | Apr 2015 | A1 |
20150130801 | Wooley | May 2015 | A1 |
20160113581 | Amir | Apr 2016 | A1 |
20160196667 | Densham et al. | Jul 2016 | A1 |
20170140617 | Klein | May 2017 | A1 |
20170363741 | Send et al. | Dec 2017 | A1 |
20180005430 | Griffith | Jan 2018 | A1 |
20180196585 | Densham | Jul 2018 | A1 |
20190138107 | Nietfeld | May 2019 | A1 |
20190280535 | Tu | Sep 2019 | A1 |
20200363490 | Densham | Nov 2020 | A1 |
20210042019 | Densham | Feb 2021 | A1 |
20210141520 | Densham | May 2021 | A1 |
Entry |
---|
“BlackTrax Unveils Version 2.2,” Lighting and Sounds America, Published Oct. 16, 2017, [Retrieved on Aug. 5, 2021]. Retrieved from the Internet <URL: http://www.lightingandsoundamerica.com/news/story.asp?ID=4UP6S>, 1 page. |
“BlackTrax Wiki—History:BTBeacon—Preview of version 9,” CAST Group of Companies Inc., Published on Feb. 24, 2016, [Retrieved on Aug. 5, 2021]. Retrieved from the Internet: <URL: https://wiki.blacktrax.ca/tiki-pagehistory.php?page=BTBeacon&preview=9>, 5 pages. |
“BlackTrax Wiki—History:BTSmart Charger—Preview of version 12,” CAST group of Companies Inc., Published on Apr. 15, 2019, [Retrieved on Aug. 5, 2021], Retrieved from the Internet: <URL: https://wiki.blacktrax.ca/tiki-pagehistory.php?page=BTSmart+Charger&preview=12.>, 3 pages. |
Number | Date | Country | |
---|---|---|---|
20230195297 A1 | Jun 2023 | US |
Number | Date | Country | |
---|---|---|---|
62934215 | Nov 2019 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17095311 | Nov 2020 | US |
Child | 18110696 | US |