Patent Grant
9918000
The present disclosure generally relates to the field of photography. In particular, the present disclosure is directed to a wireless photographic communication system and method.
Previously, a user of a camera body that desired to add wireless communication capabilities to a camera would have to use either an external or internal module to modify the camera so as to provide such capabilities. An internal wireless module may be mounted inside the body of the camera, thus providing wireless capabilities with as little as an antenna visible from on the outside of the camera body. However, an internal wireless communication module may require some disassembly of the camera body itself for installation. Typical external wireless communication devices generally include a transmitter, receiver, and/or a transceiver in a body that requires some form of connectivity to the controls of the camera body to provide the camera body with the wireless communication functionality. Typically, an external wireless communication device remains separate from the camera body and uses wires to connect to a port of a camera. This type of external wireless communication device may require physical attachment to some part of the camera or its surroundings. This may be accomplished by tape, Velcro, or other aesthetically and physically unappealing techniques. Existing external wireless communication devices also have their own power supplies. The power supplies typically add to the size and mass of the module. The wires add to the complication and external bulk of using the external module. Another example of an external wireless communication device may be mounted in the hotshoe of a camera. The hotshoe only provides access to shutter synchronization. The hotshoe is typically reserved for a flash module, thus, when a wireless communication module is inserted therein, the hotshoe is unavailable for a flash or other device. Additionally, the hotshoe does not provide access to a power supply of the camera body. Thus, a hotshoe connected wireless communication module still requires its own power supply. It would be desirable to have a more compact, elegant, and directly connected module for providing wireless communication capability to a camera. It is also desirable to have a wireless communication module that leaves the hotshoe of the camera free to receive other devices, such as a flash.
In one implementation, a method of synchronizing a remote lighting device to image acquisition by a camera body is provided. The method includes detecting a predictor signal of the camera body via an external port of the camera body, the predictor signal occurring at a known time prior to a shutter of the camera body opening; determining a synchronization time for synchronizing a remote lighting device, the determining including use of the predictor signal and an amount of time between the predictor signal and the shutter opening; wirelessly communicating a synchronization information to the remote lighting device after the detecting a predictor signal; and synchronizing the remote lighting device to image acquisition at the synchronization time, wherein (a) the determining occurs before the wirelessly communicating and the synchronization information includes a synchronization signal or (b) the determining occurs after the wirelessly communicating and the synchronization information includes information based on the predictor signal for use in the determining.
In another implementation, a system for synchronizing a remote lighting device to image acquisition by a camera body, the system comprising: a means for detecting a predictor signal of the camera body via an external port of the camera body, the predictor signal occurring at a known time prior to a shutter of the camera body opening; a means for determining a synchronization time for synchronizing a remote lighting device, the determining including use of the predictor signal and an amount of time between the predictor signal and the shutter opening; a means for wirelessly communicating a synchronization information to the remote lighting device after the detecting a predictor signal; and a means for synchronizing the remote lighting device to image acquisition at the synchronization time, wherein (a) the determining occurs before the wirelessly communicating and the synchronization information includes a synchronization signal or (b) the determining occurs after the wirelessly communicating and the synchronization information includes information based on the predictor signal for use in the determining.
For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:
It is often desirable to provide wireless communication capability to a camera. A wireless communication module is provided for enabling a camera to wirelessly communicate with a remote device. In one example, a camera body may communicate wirelessly with a remote device for many purposes, such as controlling the remote device, sending information to the remote device, receiving information from the remote device, being controlled by the remote device, and any combinations thereof. Wireless communication may occur over any of a variety of well known communication techniques. Examples of wireless communication techniques include, but are not limited to, radio frequency (RF), optical, and any combinations thereof. Various aspects of wireless communication techniques, including encoding of wireless signals, are discussed in U.S. Pat. No. 5,359,375 to Clark, issued on Oct. 25, 1994, which is incorporated herein by reference in its entirety. Examples of remote devices include, but are not limited to, a light source, such as a flash or continuous light source; a camera; a light meter, such as a light intensity or light color spectrum meter; a general computing device, such as a personal computer or handheld computing device; and any combinations thereof.
In one embodiment, a wireless communication module includes a transmitter, a receiver, and/or a transceiver for providing wireless communication with a remote device. A wireless communication module also includes one or more pressure connectors directly on the body of the module for connecting the module to one or more ports of a camera body. In one example, the one or more pressure connectors are integral with the shape of the module body. The one or more pressure connectors may be integral with the shape of the module body in many ways including, but not limited to, by molding one or more pressure connectors uniformly with the body itself, by attaching one or more pressure connectors directly to a surface of the module body, and any combinations thereof. In another example, the one or more pressure connectors include a male portion that protrudes directly from a surface of the module body. The male portion is sized and configured for direct insertion into a port of a camera body. In yet another example, the one or more pressure connectors include a female portion designed to mate with a male port element of a camera body. In one aspect, pressure can be applied to the module body to cause the one or more pressure connectors to connect with one or more ports of a camera body. Wires between the wireless communication module and the camera are unnecessary and use of the camera hotshoe is not required. This allows for compact and elegant designs that conform directly to a camera body in a manner not previously available.
A module body (or parts of a module body) may be constructed of any material. Examples of materials include, but are not limited to, a rigid plastic, a flexible plastic, a metal, glass filled nylon, and any combinations thereof. In yet another example, a module body may include a flexible and/or articulateable portion (e.g., for allowing movement of one pressure connector with respect to another and/or to allow one or more pressure connectors of a module body to engage one or more ports of a camera body). In still yet another example, a module body is shaped and configured to not obstruct access to external controls of the camera body when the module body is connected to the camera. In a further example, discussed in further detail below with respect to
Each of first and second pressure connectors 420 and 430 are on a side of module body 410. In this example, two pressure connectors are shown. However, it is contemplated that any number of one or more pressure connectors may be present in a wireless communication module, such as wireless communication module 400. In one example, one or more pressure connectors are present on the same side/surface of a module body. In another example, two or more pressure connectors are present on a plurality of sides/surfaces of a module body. A pressure connector may include male, female, and/or a combination of male and female components. In one example, as shown in
Module 400 also includes a transmitter 440 therein for communicating wirelessly with a remote object. In an alternate example, module 400 may include any known wireless communication circuit in place of transmitter 440 that may allow wireless communication to and/or from a remote device. Example wireless communication circuits may include, but are not limited to, a transmitter, a receiver, a transceiver, and any combinations thereof. In one example, a wireless communication module includes a receiver for receiving information from a remote device and communicating the information to a camera body to which the module is connected. In another example, a wireless communication module includes a receiver for receiving information from a remote device and a transmitter for transmitting information to a remote device. In yet another example, a wireless communication module includes a transmitter for transmitting information to a remote device. In still yet another example, a wireless communication module may include a transceiver for receiving information from a remote device and transmitting information to a remote device. Several examples discussed herein cover a module having a transmitter. It should be understood that various combinations exist, including, but not limited to, the transmitter in these examples being accompanied with a receiver, replaced by a receiver, or replaced by a transceiver. It is contemplated that the transmitter element of any of the various embodiments covered herein may actually be satisfied by the use of a transceiver element that includes both a transmitter and receiver component. One example of a transceiver includes a ADF7020-1 model transceiver available from Analog Devices of Norwood, Mass. Other examples of a transmitter, a receiver, and/or a transceiver may be utilized with a wireless communication module.
Transmitter 440 may be in direct or indirect electrical communication with first and second connectors 420 and 430. Transmitter 440 is also in electrical communication with an antenna 445 for providing wireless communication to a camera with a remote device.
An antenna, such as antenna 445, may be internal or external to a module body, such as module body 410. In one example, an antenna is integrally molded with the module body. In another example, an antenna is moveable with respect to the module body. Movement may be in any direction and be achieved by a variety of ways that are known for moveably connecting two pieces. In one example, an antenna may collapse into a module body. In another example, an antenna may fold into a module body. In yet another example, an antenna may be removable from a module body (e.g., via a screw mounting, a snap mounting, and/or other connector). In a further example, where an optical wireless technique is used, an antenna may include an optical sensor and/or an optical emitter. Example optical sensors include, but are not limited to, an infrared (IR) sensor. Example optical emitters include, but are not limited to, an IR light emitting device (LED).
Example ports of a camera body to which a wireless communication module may be connected include, but are not limited to, a synchronization port, such as a PC port; a motor-drive port, such as a 10-pin or 3-pin motor-drive port; a video input and/or output port; a Firewire port; a serial port, such as a USB port; an external power port, such as an external power port of a camera battery; and any combinations thereof. An example motor-drive port may have multiple pins and/or female pin receptors that each provide access to one or more internal functions and/or controls of a camera body. Internal functions and/or controls that may be accessed from a port of a camera body include, but are not limited to, access to direct power that is available even when the camera body is turned off, access to electrical ground, access to switched power, access to regulated power, access to serial communication with camera controls (such as RS-232 communication and universal serial bus “USB” communication), access to data input functionality, communication with “half-press” pre-release trigger control (in some examples referred to as “wakeup”), communication with “full-press” release trigger control (also known as “shutter release”), access to shutter synchronization information, access to internal memory of the camera body; access to an internal processor of the camera body; access to various other controls of the camera body; and any combinations thereof. In one example, when a port provides a pressure connector (and corresponding wireless communication module) access to an internal power supply of a camera, the wireless communication module may utilize the internal power supply as a power supply for the functioning of the module including, but not limited to, powering reception/transmission. In one example, a single port of a camera body may provide access to one internal function/control. In another example, a single port of a camera body may provide access to a plurality of internal function/controls. Throughout this disclosure, where a port is enumerated to give access to a particular one or more of an internal function/control, it should be understood that additional internal functions/controls may be also accessed by that same port. Camera body 470 in
In one example, first port 450 may be a port of camera body 470 that provides access to a shutter synchronization signal of camera body 470. An example of a camera port that provides access to a shutter synchronization signal of a camera includes, but is not limited to, a synch port (also known as a PC port). In another example, second port 460 is a port of camera body 470 that provides access to an internal power supply of camera body 470. Example camera ports that provide access to an internal power supply of a camera include, but are not limited to, a motor-drive port, an IEEE 1394 (Firewire) port, a universal serial bus port, an external power port of a removable camera battery, accessory port, and any combinations thereof.
A pressure connector, such as pressure connector 420 and/or pressure connector 430, may provide direct connection of a module body to a port of a camera body in a variety of ways. In one example, a pressure connector is sized and configured to fit snugly within, and/or around, a port of a camera body so that friction of the snug fit maintains the connection. The size and configuration of a pressure connector will depend on the size and configuration of a port of a camera body to which the pressure connector is designed to mate. In another example, one or more pressure connectors of a module body, when connected to one or more ports of a camera body, provide a portion or all of the structural support to hold the module in direct connection with the camera body (e.g., friction between one or more pressure connectors and the one or more ports of the camera body and a level of rigidity of the materials selected for construct of the one or more pressure connectors and/or the module body of the wireless communication module may provide the only structural support necessary to hold the module in place in direct connection with a camera body). In yet another example, a pressure connector may include a screw connect element that can provide a screw connection to a port of a camera body. In still yet another example, a pressure connector includes a button or other element to release the connection with a port of a camera body. In a further example, a pressure connector includes a snap-type connect element that allows the pressure connector to snap into a port of a camera body. Various friction fit, screw connection, and snap connection elements will be understood by those of ordinary skill in light of the present disclosure.
In another embodiment, a wireless communication module may be permanently attached to a camera body. In one example, an outer covering of a camera body (e.g., a rubber grip component of a camera body) may be removed and a wireless communication module connected to one or more ports of the camera in an area proximate the removed outer covering. The module body of the wireless communication module may be sized shaped and configured to replace the removed outer covering. An adhesive, one or more screws, or other permanent or releasable attachment techniques may be used to adhere the module body to the camera body. In one example, a module body may be contoured to provide a grip to the camera body. In another example, a module body may be configured to conform to the general shape of the camera body and to not obscure access to camera controls.
645 of camera body 650. In one example, first port 640 provides access to a shutter synchronization signal of camera body 650 to wireless communication module 600. In another example, second port 645 provides access to an internal power supply of camera body 650 to wireless communication module 600. First and second pressure connectors 620 and 625 are in communication with a transmitter 660. First pressure connector 620 may be in communication with a shutter synchronization signal module 665 for receiving a shutter synchronization signal. A shutter synchronization signal module (synchronization signal module) may include any necessary circuitry to receive and/or deliver information from/to a port of a camera body to a transmitter and/or processor of a wireless communication module. In one example, a synchronization signal module may include minimal circuitry (e.g., as little as a wired connection) sufficient to provide an electrical communication between a pressure connector and a transmitter and/or processor of a wireless communication module. In another example, a shutter synchronization signal module, such as shutter synchronization signal module 665, may include more detailed circuitry for communicating data to and/or from a port of a camera body to which a corresponding pressure connector is directly engaged (e.g., routing circuitry, a memory element, internal processing capabilities, machine readable instruction, etc.). Second pressure connector 625 may be in communication with a power management module 670 for receiving power from a power supply internal to camera body 650 and providing the power to module body 610. In one example, a power management module may include any necessary circuitry to provide electrical communication between a pressure connector and a transmitter and/or processor of a wireless communication module (e.g., as little as a wired connection). In another example, a power management module may include more detailed circuitry to provide power management to a wireless communication module (e.g., routing circuitry, a memory element, internal processing capabilities, machine readable instruction, etc.) Power management module 670 may be in communication with transmitter 660 for providing power to transmitter 660. Shutter synchronization signal module 665 may also be in communication with transmitter 660 for providing information to transmitter 660.
Optionally, module body 610 may include a processor 675 for processing information received and/or transmitted by communication module 600. Power management module 670 and shutter synchronization signal module 665 may be in communication with optional processor 675. Processor 675 may be in communication with transmitter 660. Transmitter 660 is in communication with antenna 680 for wirelessly communicating with a remote device. In one example, a processor, such as processor 675, may be used to encode transmissions from a wireless communication module and to decode transmissions received by a wireless communication module. In another example, a processor may manage information received wirelessly by a wireless communication module, received from a camera body to which the module is connected, and any combinations thereof. Example processors include, but are not limited to, a microcontroller, a digital signal processor, a field programmable gate array, a programmable logic device (PLD), and any combinations thereof. A processor, such as processor 675 may utilize information, such as settings, algorithms, and/or software instructions (e.g. machine readable instructions), present in an optional memory element that is separate from and/or integrated with the processor. One example of a processor includes a ATMega168 model processor available from Atmel of San Jose, Calif.
Power for a wireless communication module, such as wireless communication module 600, may be provided in a variety of ways. In one example, a wireless communication module, such as module 600, may receive power solely through one or more pressure connectors from a power supply of a camera to which the module is attached.
Wireless communication module 700 may include an optional capacitor 785 or similar module for storing power. Capacitor 785 may be a part of, or a separate circuit from, power management module 770. In one example, capacitor 785 may store power received from a camera power supply. This may be useful in an example where the camera power supply accessed by the module is below what is required to operate a wireless communication module on a full-time basis. An example of such a power supply having a current of about 2.5 mA power may be accessed via a Firewire port of a camera body. Capacitor 785 may store power and use it at select intervals, such as when transmission is required or reception is desired.
In another embodiment, internal power supply 705 may be removable. Module body 710 may include an optional door or compartment 790 for receiving a removable internal power supply. A module body may also include an optional external connector 795 for connecting an external power supply, such as a standard 110 V A/C outlet or low voltage A/C adapter, to the internal power supply for recharging the internal power supply and/or providing alternate power to module 700. In one example, wireless communication module 700 may access power internal to a camera body via a pressure connector, such as pressure connector 725, to a port of the camera body and also have its own internal/external power supply (e.g., internal power supply 705 and/or external power via external connector 795. In this example, the wireless communication module may utilize the power supply of the camera, especially if the camera power supply is a low current power supply, to maintain the general functioning of the module and also utilize its own internal/external power supply during transmission from the module to a remote device. This example, may utilize smaller current from the camera without the use of a capacitor. However, a capacitor in combination with this example is also contemplated.
A wireless communication module may also obtain power through a pressure connector from a dedicated port of a camera body for providing power and/or an external port of a battery pack associated with a camera body.
A pressure connector for connecting a wireless communication module to a camera may be moveable with respect to each other and/or a module body.
A wireless communication module may also include one or more external visual indicators for providing information about an internal status of the module. Example visual indicators include, but are not limited to, a video screen, an LCD, an LED, a light, plasma display element, and any combinations thereof.
A wireless communication module may also include one or more pass through ports in communication with a connector, as discussed above, for allowing a user to connect another device to the connector while the wireless communication module is connected to the camera.
First pass-through connector 1365 is sized, shaped, and configured to match the first port of the camera body for providing an ability to utilize the first port of the camera body when wireless communication module 1300 is connected to the camera body. Second pass-through connector 1370 is sized, shaped, and configured to match the second port of the camera body for providing an ability to utilize the second port of the camera body when wireless communication module 1300 is connected to the camera body.
In still another embodiment, a wireless communication module may include an audio element for providing an audio signal indicative of a state of the module. Examples of audio elements include, but are not limited to, a speaker, piezo buzzer, and any combinations thereof. A wireless communication module may also include one or more external controls for changing/controlling an internal state of the module. External controls include, but are not limited to, a button, a trigger, a toggle, knob, joystick, and any combinations thereof. Examples of the internal states that may need changing and/or indication include, but are not limited to, channel of operation, frequency of operation, device address, receive or transmit mode, type of camera that it will communicate with, and any combinations thereof. A visual and/or audio indication may be provided in a variety of ways including, but not limited to, quantity of indications, spoken word, a displayed image, a displayed character, and any combinations thereof. In another example, an internal state may be modified using wireless communication to a wireless communication module via the wireless communication capability of the module.
In another example, second module side 1420 may include an audio element 1470 in communication with processor 1460 for providing an audible indication of a status and/or change of an internal state of wireless communication module 1400. In one example, processor 1460 may provide instructions and/or an electrical signal to audio element 1470 for producing an audible indication representing a current status (e.g., a certain number and/or quality of audible indication may provide specific information about the state of the module). In another example, processor 1460 may provide instructions and/or an electrical signal to audio element 1470 for producing an audible indication representing a change in status (e.g., an audible indication may be provided when a user modifies a status with an external control, such as external control 1465).
In still another example, second module side 1420 may include a visual indicator 1475 in communication with processor 1460 for providing a visual indication of a status and/or change of an internal state of wireless communication module 1400. Any number and/or combination of visual indicators may be included in wireless communication module 1400. Example visual indicators are discussed above.
In a further embodiment, an external control (e.g., external control 1465) on a wireless communication module may be configured to be used alone to communicate with an internal state of the module and/or be configured to be used in combination with one or more controls of a camera body to which it is attached. In one example, wireless communication module 1400 may have access to a camera control (e.g. trigger control) of a camera body via one or more of pressure connectors 1425, 1430 and a port of the camera body (e.g., a motor-drive port). In such an example, external control 1465 may be configured (e.g., via machine readable instruction associated with processor 1460, such as in a memory) to activate at the same time as (or in a predetermined sequence with) the camera control (e.g., when a full and/or partial trigger signal is received via a pressure connector). In one aspect, this may allow a user to control a state, such as channel of operation, of the wireless communication module so that the state does not erroneously change by a single inadvertent button activation. In another example, an external control of a wireless communication module may work in conjunction with a visual indicator. In yet another example, an external control includes a visual indicator integrated therewith (e.g., a pressure sensitive display element, such as a pressure sensitive LED or LCD).
A wireless communication module (e.g., wireless communication module 1400) may utilize an external control to power on and/or off the wireless communication module or one or more aspects of the wireless communication module. In still another example, a wireless communication module may power on by sensing connection to a port of a camera body. In such an example, a processor, such as processor 1460 may have associated therewith instructions for detecting an information and/or power provided via one or more pressure connectors in direct communication with one or more ports of the camera body. In still yet another example, a wireless communication module may be configured to have an internal state modified and/or controlled by one or more camera controls of a camera body to which the module is connected (e.g., a processor, such as processor 1460 may include instructions for detecting a signal provided via one or more pressure connectors in direct communication with one or more ports of the camera body and to set and/or alter a state of the wireless communication module based on the signal). In a further example, an internal state of a wireless communication module may be indicated by a visual indicator of a camera body to which the wireless communication module is connected. In such an example, a processor, such as processor 1460, may provide information to a processor of the camera body via one or more pressure connectors in direct communication with one or more ports of the camera body. The processor of the camera body may utilize a visual display element of the camera body (e.g., an LED and/or LCD display) to display an indication of the wireless communication module status.
As discussed above, wireless communication can be used for a variety of purposes. Examples of uses for a wireless communication module include, but are not limited to, wirelessly controlling the function and/or triggering of a remote flash, wirelessly controlling the function and/or triggering of a remote camera, wirelessly controlling the camera to which the module is connected from a remote device, wirelessly communicating information to and/or from a remote device, wirelessly receiving information from and/or transmitting information to a remote light meter and/or color spectrum meter, and any combinations thereof. Any of the embodiments discussed herein may utilize direct connection to a camera body and access to appropriate internal functions/controls through a pressure connector to port connection to accomplish any of these and other uses.
In one example, wireless communication module 1710 may receive from camera body 1715, and wirelessly communicate to remote camera 1720, an information from one or more external ports of camera body 1715. Camera body 1715 may utilize wireless communication module 1710 to communicate a variety of information to a remote camera, such as camera 1720. Example information for wireless communication to a remote camera includes, but is not limited to, a synchronization signal for synching an image acquisition parameter (e.g., shutter/light synchronization) of the remote camera, a trigger release signal, a control signal for controlling the remote camera, another image acquisition parameter (e.g., ISO, aperture, shutter speed, desired light exposure value, etc.), a confirmation signal (e.g., response to a previous communication, such as a synch signal, and any combinations thereof. In another example, wireless communication module 1710 may wirelessly receive from remote camera 1720, and communicate to camera body 1715, an information related to the operation of remote camera 1720. Example information for wireless communication from a remote camera includes, but is not limited to, a synchronization signal for synching an image acquisition parameter (e.g., shutter/light synchronization) of the remote camera, a trigger release signal, a control signal for controlling the remote camera, another image acquisition parameter (e.g., ISO, aperture, shutter speed, desired light exposure value, etc.), a confirmation signal (e.g., response to a previous communication, such as a synch signal, and any combinations thereof. Remote camera 1720 also includes a lens 1725 attached thereto.
In another example, wireless communication module 1710 may receive from camera body 1715, and wirelessly communicate to remote light source 1725, an information from one or more external ports of camera body 1715. Example information for wireless communication to a remote light source includes, but is not limited to a synchronization signal, a trigger signal, an image acquisition parameter, a desired light exposure value, a color temperature value, raw color spectrum information collected from a color spectrum detector, ISO, aperture, shutter speed, a control signal for operating a remote light source, a power adjustment, and any combinations thereof. Remote light source 1725 may include a flash light and/or a continuous light. In yet another example, wireless communication module 1710 may wirelessly receive from a remote light source, such as remote light source 1725, an information (e.g., a confirmation of light trigger) and communicate the information to camera body 1715.
In still another example, wireless communication module 1710 may receive from camera body 1715, and wirelessly communicate to remote general computing device 1730 (here shown as an exemplary handheld general computer device), information from one or more external ports of camera body 1715. Example information for wireless communication to a remote general computing device includes, but is not limited to, an image acquisition parameter, a color temperature value, an exposure value, and any combinations thereof. In still yet another example, wireless communication module 1710 may wirelessly receive from remote general computing device 1730, and communicate to camera body 1715, an information related to the operation of remote general computing device 1730.
In a further example, communication module 1710 may receive from camera body 1715, and wirelessly communicate to remote light and/or color spectrum meter 1735, information from one or more external ports of camera body 1715. Example information for wireless communication to a remote light and/or color spectrum meter includes, but is not limited to, an image acquisition parameter, a desired color temperature value, a desired exposure value, and any combinations thereof. In still yet another example, wireless communication module 1710 may wirelessly receive from remote light and/or color spectrum meter 1735, and communicate to camera body 1715, an information (e.g., a color temperature value, an exposure value, and any combination thereof) related to the operation of remote light and/or color spectrum meter 1735.
As discussed above in relation to various embodiments, a wireless communication module, such as wireless communication module 1710 may obtain information via one or more pressure connectors connected to the camera to which the module is attached for synchronizing a remote device with camera 1715. The information may be used to synchronize a remote device, such as a remote lighting device, a remote camera, or remote meter, to the shutter of the camera to which the module is attached. In one example, a wireless communication module, such as wireless communication module 1710 may receive a shutter synchronization information via a synchronization port (e.g., a PC connector) of a camera body to which the module is connected. In one example, the shutter synchronization information may be wirelessly communicated to a remote device (e.g., remote camera 1720, remote light source 1725, etc.) for synchronizing the remote device with image capture. In an alternate embodiment, a wireless communication module may use trigger information or voltage change information (e.g. a voltage change of a camera internal power source) from a camera port, such as a motor-drive port, and a known time between a trigger signal event and a shutter opening for a given camera (and/or camera setting) to synchronize the remote device via wireless communication. In such an embodiment, a memory may be utilized in the wireless communication device and/or at the remote device to store a known time between trigger signal and a shutter opening. In one example, a processor in a wireless communication module may utilize trigger information and voltage change information in conjunction with known timing information stored in a memory to determine an appropriate time to wirelessly transmit a synchronization signal to a remote device. In another example, a wireless communication module may wirelessly communicate received trigger information and voltage change information to a remote device, which may utilize stored timing information and a local processor to determine appropriate synchronization with the image acquisition. In another example, it may be necessary to factor time for the actual wireless transmission of information between a wireless communication module and a remote device.
In another alternative embodiment, a wireless communication module may monitor the voltage of an internal camera power supply to which it is connected via one or more pressure connector. Inclusion of monitoring circuitry as part of processing circuitry in a wireless communication module allows monitoring for changes indicative of certain internal events in the camera body.
In another example, a voltage output change from a camera body may be uniquely related to internal activity of a camera body. Internal activity, such as the start of a mirror opening, the stop of a mirror opening, first shutter movement, and/or subsequent shutter movement may cause signature voltage spikes that may be reliably used to predict a shutter opening. Thus, the predicted shutter opening could be used to synchronize a remote device via wireless communication using a wireless communication module, such as wireless communication module 1710. Voltage activity from the internal power supply may be compared by proper circuitry within a wireless communication module to one or more stored voltage signatures (possibly in a memory of the wireless communication module) to determine an internal event indicative of a shutter opening.
In another example, a voltage output change from the camera body may be used to gain extra time prior to the shutter opening for sending redundant signals that contain time stamps as to when the shutter will be open in the very near future. This extra time can enable a zero delay remote shutter synchronization. For example, if a specific voltage event indicates that the shutter will be open in exactly 28 milliseconds, the wireless communication module may send a signal to the remote flash device to activate in 28 milliseconds less the amount of time it took for wireless communications to complete. This zero delay system is unique and is not used by any current wireless system.
In a further example, a wireless communication module may include an audio reception device, (e.g., a microphone), to receive audio signals from within a camera body. A camera body may produce signature audio waves that are a function of particular events that occur within the camera body. For example, a mirror slapping open (or other internal event) may produce unique audio of a predictable wavelength and/or amplitude that can be monitored by an audio reception device of a wireless communication module. The measured audio may be compared to one or more stored audio signatures (possibly in a memory of the wireless communication module) to determine an internal event indicative of a shutter opening. Because of the time required for audio to travel from a camera body to an audio reception device, it may be important to maintain a fixed known distance between the camera body and the audio reception device.
As discussed above, known times between certain internal events and shutter activity may be used in conjunction with voltage and audio activity to predict shutter activity timing.
A wireless communication module according to the various embodiments discussed herein may include a memory in order to facilitate the storage of information, such as information related to known times between trigger and shutter activity, voltage signatures for one or more cameras, signal encryption, channel settings, processing instructions, and any combinations thereof.
Information and/or power may be provided to a wireless communication module and/or information may be provided to a camera from a wireless communication module according to any of the above discussed examples. Wireless communication module 2110 also illustrates an example shape and configuration that does not interfere with utilization of external camera controls, including the ability to change a lens without removing wireless communication module 2110.
In another embodiment, a method of modifying a camera to allow the camera to wirelessly communicate with a remote device is provided. A wireless communication module having one or more pressure connectors according to the various embodiments discussed herein may be connected to one or more ports of the camera.
In yet another embodiment, a method of communicating between a camera and a remote device is provided. A wireless communication module having one or more pressure connectors according to the various embodiments discussed herein may be connected to one or more ports of the camera. The wireless communication module may utilize a transmitter, receiver, and/or transceiver within the module body and connections made between the one or more pressure connectors and the one or more ports to communicate information to or from the remote device. Communication of information may include controlling the remote device and/or controlling the camera from the remote device.
Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention.
This application is a continuation application of U.S. patent application Ser. No. 15/237,390, filed Aug. 15, 2016, and titled “Wireless Photographic Communication System and Method,” which is a continuation of U.S. patent application Ser. No. 14/456,691, filed Aug. 11, 2014, and titled “Zero Delay Photographic Synchronization System and Method,” which is a continuation application of U.S. patent application Ser. No. 13/016,345, filed Jan. 28, 2011, and titled “Zero Delay Photographic Synchronization System and Method,” which is a continuation application of U.S. patent application Ser. No. 11/490,322, filed Jul. 20, 2006, and titled “Wireless Photographic Communication System and Method,” each of which is incorporated by reference herein in its entirety. This application also claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 60/701,451, filed Jul. 20, 2005, and titled “Wireless Photographic Communication System and Method”, which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3039375 | Umbach | Jun 1962 | A |
| 3185056 | Gold et al. | May 1965 | A |
| 3205803 | Burgarella et al. | Sep 1965 | A |
| 3259042 | Kagan | Jul 1966 | A |
| RE26627 | Burgarella et al. | Jul 1969 | E |
| 3547017 | Harvey | Dec 1970 | A |
| 3659509 | Burgarella | May 1972 | A |
| 3706266 | Uno et al. | Dec 1972 | A |
| 3728947 | Harnden et al. | Apr 1973 | A |
| 3782258 | Boekkooi et al. | Jan 1974 | A |
| 3810214 | Malone et al. | May 1974 | A |
| 4047191 | Coppa et al. | Sep 1977 | A |
| 4067030 | Kuramoto et al. | Jan 1978 | A |
| 4194818 | Matteson et al. | Mar 1980 | A |
| 4201434 | Tureck | May 1980 | A |
| 4209244 | Sahara et al. | Jun 1980 | A |
| 4329624 | Kamon et al. | May 1982 | A |
| 4333719 | Takami et al. | Jun 1982 | A |
| 4344680 | Ishida et al. | Aug 1982 | A |
| 4351594 | Ishida et al. | Sep 1982 | A |
| 4355309 | Hughey et al. | Oct 1982 | A |
| 4368966 | Hagyuda | Jan 1983 | A |
| 4410250 | Curran | Oct 1983 | A |
| 4465353 | Yoshida et al. | Aug 1984 | A |
| 4482895 | Weinberg | Nov 1984 | A |
| 4509845 | Mizokami | Apr 1985 | A |
| 4571049 | Tsunefuji et al. | Feb 1986 | A |
| 4573786 | Taniguchi et al. | Mar 1986 | A |
| 4603954 | Egawa et al. | Aug 1986 | A |
| 4636052 | Bowsher | Jan 1987 | A |
| 4643551 | Ohmori | Feb 1987 | A |
| 4693582 | Kawamura et al. | Sep 1987 | A |
| 4705373 | Ohmori | Nov 1987 | A |
| 4707127 | Goedken | Nov 1987 | A |
| 4712902 | Hosomizu et al. | Dec 1987 | A |
| 4740804 | Shands | Apr 1988 | A |
| 4816850 | Philipeaux et al. | Mar 1989 | A |
| 4816855 | Kitaura et al. | Mar 1989 | A |
| 4881013 | Kataoka et al. | Nov 1989 | A |
| 4884094 | Kitaura et al. | Nov 1989 | A |
| 4988584 | Shaper | Jan 1991 | A |
| 5016037 | Taniguchi et al. | May 1991 | A |
| 5034769 | Takami et al. | Jul 1991 | A |
| 5159375 | Taniguchi et al. | Oct 1992 | A |
| 5218397 | Takagi | Jun 1993 | A |
| 5283610 | Sasaki | Feb 1994 | A |
| 5299012 | Tsuruta et al. | Mar 1994 | A |
| 5359375 | Clark | Oct 1994 | A |
| 5384611 | Tsuji et al. | Jan 1995 | A |
| 5422543 | Weinberg | Jun 1995 | A |
| 5436531 | Weinberg | Jul 1995 | A |
| 5521708 | Beretta | May 1996 | A |
| 5640623 | Sasaki | Jun 1997 | A |
| 5692223 | Ichikawa et al. | Nov 1997 | A |
| 5708833 | Kinney et al. | Jan 1998 | A |
| 5713050 | Ozawa | Jan 1998 | A |
| 5721971 | Sasaki | Feb 1998 | A |
| 5734934 | Horinishi et al. | Mar 1998 | A |
| 5754898 | Nakano | May 1998 | A |
| 5848306 | Shono | Dec 1998 | A |
| 6006039 | Steinberg et al. | Dec 1999 | A |
| 6029013 | Larkin et al. | Feb 2000 | A |
| 6052539 | Latorre | Apr 2000 | A |
| 6088542 | Yanai et al. | Jul 2000 | A |
| 6127940 | Weinberg | Oct 2000 | A |
| 6167199 | Fukui | Dec 2000 | A |
| 6188431 | Oie | Feb 2001 | B1 |
| 6278481 | Schmidt | Aug 2001 | B1 |
| 6351610 | Numako et al. | Feb 2002 | B1 |
| 6353711 | Numako et al. | Mar 2002 | B1 |
| 6366737 | Numako et al. | Apr 2002 | B1 |
| 6400907 | Izukawa | Jun 2002 | B1 |
| 6404987 | Fukui | Jun 2002 | B1 |
| 6430369 | Lee et al. | Aug 2002 | B2 |
| 6453154 | Haber et al. | Sep 2002 | B1 |
| 6524237 | McGowan | Feb 2003 | B1 |
| 6618557 | Ziemkowski | Sep 2003 | B1 |
| 6625399 | Davis | Sep 2003 | B1 |
| 6683654 | Haijima | Jan 2004 | B1 |
| 6718135 | Kawasaki et al. | Apr 2004 | B2 |
| 6731952 | Schaeffer et al. | May 2004 | B2 |
| 6748165 | Ogasawara | Jun 2004 | B2 |
| 6778764 | Barghini et al. | Aug 2004 | B2 |
| 6798986 | Hagiuda | Sep 2004 | B2 |
| 6863417 | Hill | Mar 2005 | B2 |
| 6941067 | Muramatsu | Sep 2005 | B2 |
| 7016603 | Clark | Mar 2006 | B2 |
| 7035534 | Shih et al. | Apr 2006 | B2 |
| 7133607 | Clark | Nov 2006 | B2 |
| 7136709 | Arling et al. | Nov 2006 | B2 |
| 7184658 | Squillace | Feb 2007 | B2 |
| 7362965 | Clark | Apr 2008 | B2 |
| 7437063 | Clark | Oct 2008 | B2 |
| 7446800 | Holmes | Nov 2008 | B2 |
| 7463304 | Murray | Dec 2008 | B2 |
| 7702228 | Clark | Apr 2010 | B2 |
| 7714908 | Holmes | May 2010 | B2 |
| 7764875 | Clark | Jul 2010 | B2 |
| 7775575 | Clark | Aug 2010 | B2 |
| 7783188 | Clark | Aug 2010 | B2 |
| 7880761 | Clark | Feb 2011 | B2 |
| 7885533 | Clark | Feb 2011 | B2 |
| 7970267 | Clark | Jun 2011 | B1 |
| 8121468 | Clark | Feb 2012 | B2 |
| 8130276 | Holmes | Mar 2012 | B2 |
| 8180210 | Clark | May 2012 | B2 |
| 8326136 | Clark | Dec 2012 | B1 |
| 8326140 | Clark | Dec 2012 | B2 |
| 8326141 | Clark | Dec 2012 | B1 |
| 8331776 | Clark | Dec 2012 | B2 |
| 8351774 | Clark | Jan 2013 | B2 |
| 8526808 | Clark | Sep 2013 | B2 |
| 8532476 | Clark | Sep 2013 | B2 |
| 8538250 | Clark | Sep 2013 | B2 |
| 8559804 | Clark | Oct 2013 | B1 |
| 8571401 | Clark | Oct 2013 | B2 |
| 8571406 | Clark | Oct 2013 | B2 |
| 8600224 | Clark | Dec 2013 | B2 |
| 8614766 | Clark | Dec 2013 | B1 |
| 8705950 | Clark | Apr 2014 | B2 |
| 8718461 | Clark | May 2014 | B2 |
| 8803989 | Clark | Aug 2014 | B2 |
| 8824882 | Clark | Sep 2014 | B2 |
| 8917350 | Clark | Dec 2014 | B2 |
| 9250499 | Clark | Feb 2016 | B2 |
| 9354491 | Clark | May 2016 | B2 |
| 9420157 | Clark | Aug 2016 | B2 |
| 9602707 | Clark | Mar 2017 | B2 |
| 9635233 | Clark | Apr 2017 | B2 |
| 9690169 | Clark | Jun 2017 | B2 |
| 20010042149 | Ito et al. | Nov 2001 | A1 |
| 20020009296 | Shaper et al. | Jan 2002 | A1 |
| 20020013161 | Schaeffer et al. | Jan 2002 | A1 |
| 20020061192 | Kawasaki et al. | May 2002 | A1 |
| 20020067425 | Iverson | Jun 2002 | A1 |
| 20020067923 | Fujimura | Jun 2002 | A1 |
| 20020127019 | Ogasawara | Sep 2002 | A1 |
| 20020191389 | Hill | Dec 2002 | A1 |
| 20030128272 | Clough et al. | Jul 2003 | A1 |
| 20030133018 | Ziemkowski | Jul 2003 | A1 |
| 20030161621 | Takaiwa | Aug 2003 | A1 |
| 20030165335 | Hagiuda | Sep 2003 | A1 |
| 20030193588 | Yuen et al. | Oct 2003 | A1 |
| 20040036774 | Nichols et al. | Feb 2004 | A1 |
| 20040066455 | Holmes | Apr 2004 | A1 |
| 20040101295 | Clark | May 2004 | A1 |
| 20040136702 | Barghini et al. | Jul 2004 | A1 |
| 20040145114 | Ippolito et al. | Jul 2004 | A1 |
| 20040234259 | Muramatsu | Nov 2004 | A1 |
| 20050006484 | Ito | Jan 2005 | A1 |
| 20050096753 | Arling et al. | May 2005 | A1 |
| 20050174434 | Chang et al. | Aug 2005 | A1 |
| 20050249486 | Murray | Nov 2005 | A1 |
| 20050281549 | Shih et al. | Dec 2005 | A1 |
| 20060014563 | Cheng | Jan 2006 | A1 |
| 20060093341 | Clark | May 2006 | A1 |
| 20060093348 | Squillace | May 2006 | A1 |
| 20060216009 | Kawamura | Sep 2006 | A1 |
| 20060257130 | Lee et al. | Nov 2006 | A1 |
| 20060275024 | McNary | Dec 2006 | A1 |
| 20060291016 | Ishigami et al. | Dec 2006 | A1 |
| 20070014553 | Endo | Jan 2007 | A1 |
| 20070058959 | Clark | Mar 2007 | A1 |
| 20070070206 | Clark | Mar 2007 | A1 |
| 20070229250 | Recker et al. | Oct 2007 | A1 |
| 20070237510 | Clark | Oct 2007 | A1 |
| 20070273774 | Holmes | Nov 2007 | A1 |
| 20080193114 | Clark | Aug 2008 | A1 |
| 20080298792 | Clark | Dec 2008 | A1 |
| 20080298793 | Clark | Dec 2008 | A1 |
| 20090034952 | Clark | Feb 2009 | A1 |
| 20090066810 | Holmes | Mar 2009 | A1 |
| 20090097835 | Kunishige | Apr 2009 | A1 |
| 20100177212 | Holmes | Jul 2010 | A1 |
| 20100290771 | Clark | Nov 2010 | A1 |
| 20100316364 | Clark | Dec 2010 | A1 |
| 20110123185 | Clark | May 2011 | A1 |
| 20110128390 | Clark | Jun 2011 | A1 |
| 20110268432 | Clark | Nov 2011 | A1 |
| 20120027395 | Clark | Feb 2012 | A1 |
| 20120099847 | Clark | Apr 2012 | A1 |
| 20120127340 | Holmes | May 2012 | A1 |
| 20120127361 | Clark | May 2012 | A1 |
| 20120140088 | Clark | Jun 2012 | A1 |
| 20120148221 | Clark | Jun 2012 | A1 |
| 20120181948 | Clark | Jul 2012 | A1 |
| 20120194699 | Kouno | Aug 2012 | A1 |
| 20120207459 | Clark | Aug 2012 | A1 |
| 20120207460 | Clark | Aug 2012 | A1 |
| 20120230663 | Ogasawara | Sep 2012 | A1 |
| 20120243859 | Clark | Sep 2012 | A1 |
| 20130089313 | Clark | Apr 2013 | A1 |
| 20130094845 | Clark | Apr 2013 | A1 |
| 20130100340 | Clark | Apr 2013 | A1 |
| 20130121674 | Clark | May 2013 | A1 |
| 20130343742 | Clark | Dec 2013 | A1 |
| 20140241710 | Clark | Aug 2014 | A1 |
| 20140347508 | Clark | Nov 2014 | A1 |
| 20140369673 | Clark | Dec 2014 | A1 |
| 20150124427 | Clark | May 2015 | A1 |
| 20160119524 | Clark | Apr 2016 | A1 |
| 20160353002 | Clark | Dec 2016 | A1 |
| 20170021666 | Clark | Jan 2017 | A1 |
| 20170223253 | Clark | Aug 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2616030 | Jul 2013 | CA |
| 2648798 | Sep 2013 | CA |
| 2007-80020420.4 | Jun 2010 | CN |
| 2010-10600736.4 | Feb 2012 | CN |
| 2010-10600736.4 | Dec 2012 | CN |
| 0984320 | Mar 2000 | EP |
| 07760263.9 | Jan 2011 | EP |
| 07760263.9 | Jul 2011 | EP |
| 8756458.9 | Jul 2011 | EP |
| 11177995.5 | Dec 2011 | EP |
| 11177995.5 | Jul 2012 | EP |
| 10741797 | Aug 2012 | EP |
| 11177995.5 | Aug 2012 | EP |
| 11177997.1 | Dec 2012 | EP |
| 56-143422 | Nov 1981 | JP |
| 59-064821 | Apr 1984 | JP |
| 59-170822 | Sep 1984 | JP |
| 63-018874 | Jan 1988 | JP |
| 04-021834 | Jan 1992 | JP |
| 05-093948 | Apr 1993 | JP |
| 07-159844 | Jan 1995 | JP |
| 07-159866 | Jun 1995 | JP |
| 2002-244193 | Aug 2002 | JP |
| 2002-318413 | Oct 2002 | JP |
| 2003-172970 | Jun 2003 | JP |
| 2003-215672 | Jul 2003 | JP |
| 2003-325451 | Nov 2003 | JP |
| 2004-072230 | Mar 2004 | JP |
| 2005-236532 | Sep 2005 | JP |
| 2006-149935 | Jun 2006 | JP |
| 2007-067870 | Mar 2007 | JP |
| 2010-510491 | Aug 2012 | JP |
| 10-0728117 | Jun 2007 | KR |
| 2003037271 | May 2004 | WO |
| 2007066162 | Nov 2007 | WO |
| 2006028229 | Feb 2008 | WO |
| 2008065137 | Sep 2008 | WO |
| 2008065139 | Sep 2008 | WO |
| 2010024088 | Jul 2010 | WO |
| 2010024108 | Sep 2010 | WO |
| 2010024195 | Sep 2010 | WO |
| 2011044008 | Nov 2011 | WO |
| 2012025915 | Jun 2012 | WO |
| Entry |
|---|
| Affadavit of James E. Clark: FlashWizard II Synchronizer, signed Mar. 20, 2008; previously submitted in U.S. Appl. No. 11/697,241. |
| Analog Devices Technical Data Sheet for ADF7020-1 Transceiver IC, Analog Devices, Inc., 2005, pp. 1-44. |
| Ash Transceiver Impedance Matching; Document Created on Dec. 10, 2001; pp. 1 to 10; http://www.rfm.com/products/apnotes/antennamatch.pdf; last viewd on Dec. 15, 2005. |
| Declaration of James E. Clark filed on Feb. 18, 2005 in U.S. Appl. No. 10/306,759. |
| Ken Rockwell: Nikon SU-800 Remote Commander; Nov. 1, 2005, http://www.kenrockwell.com/nikon/su800.htm; last viewed on Jul. 18, 2012. |
| Ken Rockwell; How to Use Nikon Strobes Wirelessly, for Free!; Dec. 17, 2005; http://web.archive.org/web/20051217091704/http://www.kenrockwell.com/nikon/ittlslave.htm; last viewed at Internet archive on Apr. 1, 2010. |
| Nikon D2x; Sep., 2004; pp. 1 to 12; Nikon Corporation. |
| Nikon WT-1 Transmitter User's Manual; around Dec. 2003; Nikon Corporation. |
| Phil Askey, Nikon D2H Review: 15. Wireless: Digital Photography Review, Wireless (Review of WT-1 Transmitter); Dec. 2003; http://www.dpreview.com/reviews/NikonD2H/page15.asp; last viewed on Mar. 18, 2008. |
| Phil Askey, Nikon D2H Review: 1. Introduction: Digital Photography Review, Nikon D2H Review, Dec. 2003; http://www.dpreview.com/reviews/NikonD2H/; last viewed on Mar. 18, 2008. |
| Phil Askey, Nikon D2Hs Preview: 1. Introduction: Digital Photography Review (includes Review of WT-2 Transmitter); Feb. 2005; http://www.dpreview.com/articles/nikond2hs/; last viewed Mar. 14, 2008. |
| PocketWizard MultiMAX Transceiver New Trigger Control Software Features, by LPA Design, Feb. 10, 2001; pp. 1 to 6, United States. |
| PocketWizard MultiMAX Transceiver Owner's Manual, by LPA Design, May 2001, pp. 1-55 and “Relay Mode” on p. 40, United States. |
| Quantum FreeWire Transceiver; Jul. 17, 2005; pp. 1 to 7; http://web.archive.org/web/20050717015832/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008. |
| Quantum FreeWire Transceiver; Nov. 15, 2004; pp. 1 to 7; http://web.archive.org/web/20041115093657/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008. |
| Quantum FreeWire Transceiver; Oct. 7, 2001; pp. 1 to 6; http://web.archive.org/web/20011007140624/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008. |
| Robert Hanashiro; Equipment Corner—News & Notes for all Those Gear-Heads; Nov. 26, 2001; pp. 1 to 3; http://www.sportsshooter.com/news_story.html?id=594; last viewed on Sep., 17, 2002. |
| XE-200 RF Shutter Release for Rebel 2000; http://zenopuseelectronix.com/XE-200.html; last viewed on Sep. 9, 2002. |
| Profoto Pro-B2 User's Manual, dated Jan., 2005. |
| U.S. Appl. No. 10/306,759, dated Aug. 29, 2003, Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Dec. 18, 2003, Response to Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Dec. 24, 2003, Examiner Interview Summary, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Mar. 27, 2004, Final Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Apr. 15, 2004, Examiner Interview Summary, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Apr. 20, 2004, Response to Final Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Aug. 24, 2004, Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Feb. 18, 2005, Request for Continued Examination, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Mar. 29, 2005, Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Apr. 14, 2005, Response to Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Jun. 29, 2005, Final Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Aug. 25, 2005, Response to Final Office Action, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Sep. 16, 2005, Notice of Allowance, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Oct. 18, 2005, 312 Amendment, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Dec. 20, 2005, Response to 312 Amendment, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Jan. 4, 2006, Response to 312 Amendment, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 10/306,759, dated Nov. 18, 2006, Certificate of Correction, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 11/305,668, dated Mar. 8, 2006, Office Action, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/305,668, dated Jun. 8, 2006, Response to Office Action, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/305,668, dated Jun. 13, 2006, Supplemental Response to Request for Clarification by the Examiner, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/305,668, dated Jun. 30, 2006, Notice of Allowance, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/305,668, dated Mar. 29, 2007, Request for Correction of Letters Patent, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/488/491, dated Oct. 16, 2007, Office Action. |
| U.S. Appl. No. 11/490,322, dated Apr. 20, 2010, Office Action, U.S. Pat. No. 7,880,761. |
| U.S. Appl. No. 11/490,322, dated Jul. 12, 2010, Response to Office Action, U.S. Pat. No. 7,880,761. |
| U.S. Appl. No. 11/490,322, dated Sep. 15, 2010, Notice of Allowance, U.S. Pat. No. 7,880,761. |
| U.S. Appl. No. 11/529,203, dated Aug. 14, 2007, Office Action, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/529,203, dated Oct. 16, 2007, Terminal Disclaimer, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/529,203, dated Oct. 16, 2007, Response to Office Action, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/529,203, dated Oct. 25, 2007, Terminal Disclaimer, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/529,203, dated Dec. 14, 2007, Notice of Allowance, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/697,241, dated Nov. 8, 2007, Office Action, U.S. Pat. No. 7,437,063. |
| U.S. Appl. No. 11/697,241, dated Mar. 10, 2008, Response to Office Action, U.S. Pat. No. 7,437,063. |
| U.S. Appl. No. 11/697,241, dated Mar. 24, 2008, Examiner Interview Summary, U.S. Pat. No. 7,437,063. |
| U.S. Appl. No. 11/697,241, dated Jun. 9, 2008, Notice of Allowance, U.S. Pat. No. 7,437,063. |
| U.S. Appl. No. 12/104,950, dated Dec. 31, 2009, Office Action, U.S. Pat. No. 7,764,875. |
| U.S. Appl. No. 12/104,950, dated Feb. 1, 2010, Response to Office Action, U.S. Pat. No. 7,764,875. |
| U.S. Appl. No. 12/104,950, dated Mar. 23, 2010, Notice of Allowance, U.S. Pat. No. 7,764,875. |
| U.S. Appl. No. 12/129,402, dated Apr. 19, 2010, Notice of Allowance, U.S. Pat. No. 7,783,188. |
| U.S. Appl. No. 12/129,447, dated Apr. 12, 2010, Notice of Allowance, U.S. Pat. No. 7,775,575. |
| U.S. Appl. No. 12/129,447, dated Apr. 12, 2010, Examiner Amendment, U.S. Pat. No. 7,775,575. |
| U.S. Appl. No. 12/250,914, dated Jun. 12, 2009, Office Action, U.S. Pat. No. 7,702,228. |
| U.S. Appl. No. 12/250,914, dated Jun. 29, 2009, Response to Office Action and Terminal Disclaimer, U.S. Pat. No. 7,702,228. |
| U.S. Appl. No. 12/250,914, dated Oct. 28, 2009, Terminal Disclaimer, U.S. Pat. No. 7,702,228. |
| U.S. Appl. No. 12/250,914, dated Dec. 3, 2009, Notice of Allowance, U.S. Pat. No. 7,702,228. |
| U.S. Appl. No. 12/705,052, dated Mar. 27, 2012, Office Action, U.S. Pat. No. 8,326,141. |
| U.S. Appl. No. 12/705,052, dated Jun. 27, 2012, Response to Office Action, U.S. Pat. No. 8,326,141. |
| 12/705,052 Sep. 5, 2012 Notice of Allowance 8,326,141. |
| U.S. Appl. No. 12/705,096, dated Mar. 12, 2012, Office Action, U.S. Pat. No. 8,326,136. |
| U.S. Appl. No. 12/705,096, dated Jun. 12, 2012, Response to Office Action, U.S. Pat. No. 8,326,136. |
| U.S. Appl. No. 12/705,096, dated Aug. 8, 2012, Notice of Allowance, U.S. Pat. No. 8,326,136. |
| U.S. Appl. No. 12/705,164, dated Mar. 29, 2012, Office Action, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Jun. 29, 2012, Response to Office Action, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Sep. 7, 2012, Office Action, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Nov. 8, 2012, Response to Office Action, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Nov. 21, 2012, Advisory Action and Applicant Initiated Interview Summary, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Nov. 29, 2012, RCE, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/705,164, dated Aug. 14, 2013, Notice of Allowance, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/762,811, dated Dec. 28, 2010, Office Action, U.S. Pat. No. 7,970,267. |
| U.S. Appl. No. 12/762,811, dated Mar. 28, 2011, Response to Office Action, U.S. Pat. No. 7,970,267. |
| U.S. Appl. No. 12/762,811, dated Mar. 28, 2011, Terminal Disclaimer, U.S. Pat. No. 7,970,267. |
| U.S. Appl. No. 12/762,811, dated Apr. 20, 2011, Notice of Allowance, U.S. Pat. No. 7,970,267. |
| U.S. Appl. No. 12/843,254, dated Jul. 27, 2010, Preliminary Remarks, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/843,254, dated Aug. 25, 2011, Office Action, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/843,254, dated Aug. 25, 2011, Response to Office Action, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/843,254, dated Aug. 25, 2011, Terminal Disclaimer, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/843,254, dated Nov. 28, 2011, Notice of Allowance, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/861,445, dated Sep. 30, 2010, Notice of Allowance, U.S. Pat. No. 7,885,533. |
| U.S. Appl. No. 13/016,345, dated Apr. 26, 2013, Restriction Requirement, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/016,345, dated May 28, 2013, Response to Restriction Requirement, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/016,345, dated Sep. 17, 2013, Office Action, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/016,345, dated Mar. 17, 2014, Response to Office Action, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/016,345, dated Apr. 10, 2014, Notice of Allowance, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/016,345, dated Jul. 23, 2014, Issue Notification, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/021,951, dated Nov. 25, 2011, Notice of Allowance, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/021,951, dated Feb. 13, 2012, Withdrawal of Notice of Allowance, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/021,951, dated Feb. 22, 2012, Office Action, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/021,951, dated Jul. 20, 2012, Response to Office Action, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/021,951, dated Oct. 5, 2012, Notice of Allowance, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/169,413, dated Dec. 20, 2011, Office Action, U.S. Pat. No. 8,180,210. |
| U.S. Appl. No. 13/169,413, dated Jan. 16, 2012, Response to Office Action, U.S. Pat. No. 8,180,210. |
| U.S. Appl. No. 13/169,413, dated Jan. 16, 2012, Terminal Disclaimers, U.S. Appl. No. 8,180,210. |
| U.S. Appl. No. 13/169,413, dated Mar. 22, 2012, Notice of Allowance, U.S. Pat. No. 8,180,210. |
| U.S. Appl. No. 13/183,046, dated Feb. 13, 2013, Office Action, U.S. Pat. No. 8,600,224. |
| U.S. Appl. No. 13/183,046, dated Apr. 29, 2013, Response to Office Action, U.S. Pat. No. 8,600,224. |
| U.S. Appl. No. 13/183,046, dated Jul. 31, 2013, Notice of Allowance, U.S. Pat. No. 8,600,224. |
| U.S. Appl. No. 13/201,182, dated May 24, 2013, Restriction Requirement. |
| U.S. Appl. No. 13/201,182, dated Aug. 26, 2013, Response to Restriction Requirement. |
| U.S. Appl. No. 13/201,182, dated Nov. 18, 2013, Office Action. |
| U.S. Appl. No. 13/201,185, dated Nov. 22, 2013, Office Action/Restriction Requirement. |
| U.S. Appl. No. 13/201,281, dated Sep. 25, 2013, Office Action, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/201,281, dated Mar. 24, 2014, Response to Office Action, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/201,281, dated Mar. 24, 2014, Terminal Disclaimer, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/201,281, dated Apr. 21, 2014, Notice of Allowance, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/201,281, dated Dec. 3, 2014, Issue Notification, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/208,686, dated Feb. 6, 2013, Office Action, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,686, dated May 6, 2013, Response to Office Action, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,686, dated Jul. 15, 2013, Final Office Action, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,686, dated Aug. 16, 2013, Applicant Initiated Interview Summary, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,686, dated Sep. 16, 2013, Response to Office Action, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,686, dated Sep. 30, 2013, Notice of Allowance, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,706, dated Dec. 26, 2012, Office Action, U.S. Pat. No. 8,571,406. |
| U.S. Appl. No. 13/208,706, dated Mar. 26, 2013, Response to Office Action, U.S. Pat. No. 8,571,406. |
| U.S. Appl. No. 13/208,706, dated Jul. 2, 2013, Notice of Allowance, U.S. Pat. No. 8,571,406. |
| U.S. Appl. No. 13/253,596, dated Nov. 30, 2011, Office Action, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated Feb. 29, 2012, Response to Office Action, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated Feb. 29, 2012, Terminal Disclaimer, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated May 9, 2012, Final Office Action, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated Jul. 18, 2012, Request for Continued Examination, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated Jul. 18, 2012, Response to Office Action, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/253,596, dated Aug. 9, 2012, Notice of Allowance, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/399,333, dated Jun. 14, 2012, Office Action, U.S. Pat. No. 8,351,774. |
| U.S. Appl. No. 13/399,333, dated Sep. 14, 2012, Response to Office Action, U.S. Pat. No. 8,351,774. |
| U.S. Appl. No. 13/399,333, dated Sep. 14, 2012, Terminal Disclaimers, U.S. Pat. No. 8,351,774. |
| U.S. Appl. No. 13/399,333, dated Sep. 28, 2012, Notice of Allowance, U.S. Pat. No. 8,351,774. |
| U.S. Appl. No. 13/401,175, dated May 6, 2013, Office Action, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Aug. 6, 2013, Response to Office Action, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Sep. 20, 2013, Notice of Allowance, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Dec. 16, 2013, Notice to File Corrected Application Papers, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Jan. 13, 2014, Corrected Notice of Allowability, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Mar. 20, 2014, Reponse to Notice to File Corrected Application Papers, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Mar. 20, 2014, Petition to Revive, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Apr. 1, 2014, Petition Decision to Revive, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/401,175, dated Apr. 16, 2015, Issue Notification, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/438,500, dated Jun. 18, 2012, Office Action, U.S. Pat. No. 8,559,804. |
| U.S. Appl. No. 13/438,500, dated Sep. 14, 2012, Response to Office Action, U.S. Pat. No. 8,559,804. |
| U.S. Appl. No. 13/438,500, dated Sep. 14, 2012, Terminal Disclaimers, U.S. Pat. No. 8,559,804. |
| U.S. Appl. No. 13/438,500, dated Jun. 12, 2013, Notice of Allowance, U.S. Pat. No. 8,559,804. |
| U.S. Appl. No. 13/692,515, dated Jun. 24, 2013, Notice of Allowance, U.S. Pat. No. 8,571,401. |
| U.S. Appl. No. 13/692,550, dated May 16, 2013, Notice of Allowance, U.S. Pat. No. 8,538,250. |
| U.S. Appl. No. 13/692,550, dated Jul. 2, 2013, Supplemental Notice of Allowance, U.S. Pat. No. 8,538,250. |
| U.S. Appl. No. 13/708,326, dated Mar. 26, 2013, Notice of Allowance, U.S. Pat. No. 8,526,808. |
| U.S. Appl. No. 13/735,325, dated Mar. 15, 2013, Office Action, U.S. Pat. No. 8,532,476. |
| U.S. Appl. No. 13/735,325, dated Mar. 21, 2013, Response to Office Action w/Terminal Disclaimers, U.S. Pat. No. 8,532,476. |
| U.S. Appl. No. 13/735,325, dated May 14, 2013, Notice of Allowance, U.S. Pat. No. 8,532,476. |
| U.S. Appl. No. 14/015,336, dated Nov. 8, 2013, Office Action, U.S. Pat. No. 8,824,882. |
| U.S. Appl. No. 14/015,336, dated Apr. 7, 2014, Response to Office Action, U.S. Pat. No. 8,824,882. |
| U.S. Appl. No. 14/015,336, dated Apr. 7, 2014, Terminal Disclaimers, U.S. Pat. No. 8,824,882. |
| U.S. Appl. No. 14/015,336, dated May 2, 2014, Notice of Allowance, U.S. Pat. No. 8,824,882. |
| U.S. Appl. No. 14/021,200, dated Oct. 8, 2013, Office Action. |
| U.S. Appl. No. 14/270,107, dated Jun. 3, 2014, Office Action, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Dec. 3, 2014, Response to Office Action, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Dec. 3, 2014, Terminal Disclaimer, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Mar. 6, 2015, Final Office Action, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Jun. 6, 2015, Response to Office Action, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Jun. 15, 2015, Notice of Allowance, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Sep. 2, 2015, RCE, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Oct. 30, 2015, Notice of Allowance, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Jan. 4, 2016, RCE, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/270,107, dated Jan. 29, 2016, Notice of Allowance, U.S. Pat. No. 9,354,491. |
| U.S. Appl. No. 14/456,691, dated Oct. 23, 2015, Restriction Requirement, U.S. Pat. No. 9,420,157. |
| U.S. Appl. No. 14/456,691, dated Nov. 4, 2015, Response to Restriction Requirement, U.S. Pat. No. 9,420,157. |
| U.S. Appl. No. 14/456,691, dated Dec. 18, 2015, Office Action, U.S. Pat. No. 9,420,157. |
| U.S. Appl. No. 14/456,691, dated Mar. 17, 2016, Response to Office Action, U.S. Pat. No. 9,420,157. |
| U.S. Appl. No. 14/456,691, dated Mar. 17, 2016, Terminal Disclaimer, U.S. Pat. No. 9,420,157. |
| U.S. Appl. No. 14/472,320, dated Apr. 27, 2015, Office Action, U.S. Pat. No. 9,250,499. |
| U.S. Appl. No. 14/472,320, dated Jul. 30, 2015, Response to Office Action, U.S. Pat. No. 9,250,499. |
| U.S. Appl. No. 14/472,320, dated Jul. 30, 2015, Terminal Disclaimers, U.S. Pat. No. 9,250,499. |
| U.S. Appl. No. 14/472,320, dated Sep. 22, 2015, Notice of Allowance, U.S. Pat. No. 9,250,499. |
| U.S. Appl. No. 15/237,390, dated Dec. 19, 2016, Notice of Allowance, U.S. Pat. No. 9,635,233. |
| U.S. Appl. No. 15/237,390, dated Apr. 5, 2017, Issue Notification, U.S. Pat. No. 9,635,233. |
| U.S. Appl. No. 10/306,759, filing date Nov. 26, 2002, U.S. Pat. No. 7,016,603. |
| U.S. Appl. No. 11/305,668, filing date Dec. 16, 2005, U.S. Pat. No. 7,133,607. |
| U.S. Appl. No. 11/490,322, filing date Jul. 20, 2006, U.S. Pat. No. 7,880,761. |
| U.S. Appl. No. 11/529,203, filing date Sep. 27, 2006, U.S. Pat. No. 7,362,965. |
| U.S. Appl. No. 11/697,241, filing date Apr. 5, 2007, U.S. Pat. No. 7,437,063. |
| U.S. Appl. No. 12/104,950, filing date Apr. 17, 2008, U.S. Pat. No. 7,764,875. |
| U.S. Appl. No. 12/129,402, filing date May 29, 2008, U.S. Pat. No. 7,783,188. |
| U.S. Appl. No. 12/129,447, filing date May 29, 2008, U.S. Pat. No. 7,775,575. |
| U.S. Appl. No. 12/250,914, filing date Oct. 14, 2008, U.S. Pat. No. 7,702,228. |
| U.S. Appl. No. 12/705,052, filing date Feb. 12, 2010, U.S. Pat. No. 8,326,141. |
| U.S. Appl. No. 12/705,096, filing date Feb. 12, 2010, U.S. Pat. No. 8,326,136. |
| U.S. Appl. No. 12/705,164, filing date Feb. 12, 2010, U.S. Pat. No. 8,614,766. |
| U.S. Appl. No. 12/762,811, filing date Apr. 19, 2010, U.S. Pat. No. 7,970,267. |
| U.S. Appl. No. 12/843,254, filing date Jul. 26, 2010, U.S. Pat. No. 8,121,468. |
| U.S. Appl. No. 12/861,445, filing date Aug. 23, 2010, U.S. Pat. No. 7,885,533. |
| U.S. Appl. No. 13/016,345, filing date Jan. 28, 2011, U.S. Pat. No. 8,803,989. |
| U.S. Appl. No. 13/021,951, filing date Feb. 7, 2011, U.S. Pat. No. 8,331,776. |
| U.S. Appl. No. 13/169,413, filing date Jun. 27, 2011, U.S. Pat. No. 8,180,210. |
| U.S. Appl. No. 13/183,046, filing date Jul. 14, 2011, U.S. Pat. No. 8,600,224. |
| U.S. Appl. No. 13/201,182, filing date Aug. 11, 2011. |
| U.S. Appl. No. 13/201,185, filing date Aug. 11, 2011. |
| U.S. Appl. No. 13/201,281, filing date Aug. 12, 2011, U.S. Pat. No. 8,917,350. |
| U.S. Appl. No. 13/208,686, filing date Aug. 12, 2011, U.S. Pat. No. 8,705,950. |
| U.S. Appl. No. 13/208,706, filing date Aug. 12, 2011, U.S. Pat. No. 8,571,406. |
| U.S. Appl. No. 13/253,596, filing date Oct. 5, 2011, U.S. Pat. No. 8,326,140. |
| U.S. Appl. No. 13/399,333, filing date Feb. 17, 2012, U.S. Pat. No. 8,351,774. |
| U.S. Appl. No. 13/401,175, filing date Feb. 21, 2012, U.S. Pat. No. 8,718,461. |
| U.S. Appl. No. 13/438,500, filing date Apr. 3, 2012, U.S. Pat. No. 8,559,804. |
| U.S. Appl. No. 13/692,515, filing date Dec. 3, 2012, U.S. Pat. No. 8,571,401. |
| U.S. Appl. No. 13/692,550, filing date Dec. 3, 2012, U.S. Pat. No. 8,538,250. |
| U.S. Appl. No. 13/708,326, filing date Dec. 7, 2012, U.S. Pat. No. 8,526,808. |
| U.S. Appl. No. 13/735,325, filing date Jan. 7, 2013, U.S. Pat. No. 8,532,476. |
| U.S. Appl. No. 14/015,336, filing date Aug. 30, 2013, U.S. Pat. No. 8,824,882. |
| U.S. Appl. No. 14/201,200, filing date Sep. 9, 2013. |
| U.S. Appl. No. 14/270,107, filing date May 5, 2014. |
| U.S. Appl. No. 14/456,691, filing date Aug. 11, 2014. |
| U.S. Appl. No. 14/472,320, filing date Aug. 28, 2014, U.S. Pat. No. 9,250,499. |
| U.S. Appl. No. 14/533,067, filing date Nov. 4, 2014. |
| U.S. Appl. No. 14/987,589, filing date Jan. 4, 2016. |
| U.S. Appl. No. 14/987,589, filing date Apr. 8, 2016, Office Action. |
| U.S. Appl. No. 14/533,067, filing date Apr. 15, 2016, Office Action (Ex parte Quayle). |
| U.S. Appl. No. 14/987,589, filing date Sep. 8, 2016, Response to Office Action. |
| U.S. Appl. No. 14/987,589, filing date Nov. 7, 2016, Notice of Allowance. |
| U.S. Appl. No. 14/987,589, filing date Mar. 1, 2017, Issue Notification. |
| U.S. Appl. No. 14/270,107, filing date May 11, 2016, Issue Notification. |
| U.S. Appl. No. 14/533,067, filing date Jul. 26, 2016, Notice of Allowance. |
| U.S. Appl. No. 14/533,067, filing date Oct. 25, 2016, RCE. |
| U.S. Appl. No. 14/533,067, filing date Nov. 7, 2016, Office Action (Ex parte Quayle). |
| U.S. Appl. No. 14/533,067, filing date Jan. 8, 2017, Response to Office Action. |
| U.S. Appl. No. 14/533,067, filing date Jul. 15, 2016, Response to Office Action. |
| U.S. Appl. No. 14/533,067, filing date Feb. 28, 2017, Notice of Allowance. |
| U.S. Appl. No. 14/533,067, filing date Jun. 7, 2017, Issue Notification. |
| U.S. Appl. No. 15/237,390, filing date Aug. 15, 2016. |
| U.S. Appl. No. 15/492.635, filing date Apr. 20, 2017. |
| U.S. Appl. No. 15/464,293, filing date Mar. 20, 2017. |
| U.S. Appl. No. 15/169,638, filing date May 31, 2016. |
| U.S. Appl. No. 15/633,216, filing date Jun. 26, 2017. |
| Number | Date | Country | |
|---|---|---|---|
| 20170223253 A1 | Aug 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60701451 | Jul 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15237390 | Aug 2016 | US |
| Child | 15492635 | US | |
| Parent | 14456691 | Aug 2014 | US |
| Child | 15237390 | US | |
| Parent | 13016345 | Jan 2011 | US |
| Child | 14456691 | US | |
| Parent | 11490322 | Jul 2006 | US |
| Child | 13016345 | US |
