The present disclosure relates to a first device controlling operation of a second device, and, more particularly, to a first device controlling operation of a second device based on a read request. Some embodiments may be applied to aerosol delivery devices, such as smoking articles, and more particularly to a system and elated methods and computer program products for controlling an aerosol delivery device by a read request. The smoking articles may be configured to heat a material, which may be made or derived from tobacco or otherwise incorporate tobacco, to form an inhalable substance for human consumption.
Many smoking devices have been proposed through the years as improvements upon, or alternatives to, smoking products that require combusting tobacco for use. Many of those devices purportedly have been designed to provide the sensations associated with cigarette, cigar, or pipe smoking, but without delivering considerable quantities of incomplete combustion and pyrolysis products that result from the burning of tobacco. To this end, there have been proposed numerous smoking products, flavor generators, and medicinal inhalers that utilize electrical energy to vaporize or heat a volatile material, or attempt to provide the sensations of cigarette, cigar, or pipe smoking without burning tobacco to a significant degree. See, for example, the various alternative smoking articles, aerosol delivery devices and heat generating sources set forth in the background art described in U.S. Pat. No. 7,726,320 to Robinson et al., U.S. Pat. App. Pub. No. 2013/0255702 to Griffith Jr. et al., U.S. Pat. App. Pub. No. 2014/0000638 to Sebastian et al., U.S. Pat. App. Pub. No. 2014/0060554 to Collett et al., U.S. patent application Ser. No. 13/647,000 to Sears et al., filed Oct. 8, 2012, U.S. patent application Ser. No. 13/826,929 to Ampolini et al., filed Mar. 14, 2013, and U.S. patent application Ser. No. 14/011,992 to Davis et al., filed Aug. 28, 2013, which are incorporated herein by reference in their entirety.
Ongoing developments in the field of aerosol delivery devices have resulted in increasingly sophisticated aerosol delivery devices. However, due to factors such as form factor, many aerosol delivery devices have relatively limited user interface mechanisms via which operations of the device may be invoked by a user.
The present disclosure relates to a system and related methods, apparatuses, and computer program products for controlling operation of a device based on a read request. For example, various embodiments disclosed herein provide a system whereby a first computing device may invoke performance of an operation by a second computing device by sending a request to read a value corresponding to the operation to the second computing device via a communication link between the first computing device and the second computing device. In this regard, each of a plurality of readable values that may be maintained by the second computing device may correspond to a respective operation, and the second computing device may be configured to perform the operation corresponding to the value that the first computing device requested to read in response to the request. Such example embodiments may be particularly beneficial for devices, such as aerosol delivery devices, that may have relatively limited user interface mechanisms. For example, some such example embodiments may be applied to enable a device such as a mobile communication device having a full featured user interface to invoke performance of an operation by an aerosol delivery device by sending a request to read a value corresponding to the operation to the aerosol delivery device.
For example, in one aspect, a method for performing an operation in response to a read request is provided. The method may include a first computing device receiving a request to read a value. The request may be received from a second computing device via a wireless communication link between the first computing device and the second computing device. The first computing device may, for example, comprise an aerosol delivery device. The second computing device may, for example, comprise a mobile communication device. The method may further include the first computing device determining an operation corresponding to the value. In this regard, each of a plurality of values that may be read from the first computing device may correspond to a different respective operation. The method may additionally include the first computing device performing the operation corresponding to the value in response to the request.
In another aspect, an apparatus is provided, which may include processing circuitry. The apparatus may be implemented on a first computing device, such as an aerosol delivery device. The processing circuitry may be configured to cause the first computing device to receive a request to read a value. The request may be received from a second computing device, such as a mobile communication device, via a wireless communication link between the first computing device and the second computing device. The processing circuitry may be further configured to cause the first computing device to determine an operation corresponding to the value. In this regard, each of a plurality of values that may be read from the first computing device may correspond to a different respective operation. The processing circuitry may be additionally configured to cause the first computing device to perform the operation corresponding to the value in response to the request.
In a further aspect, a computer program product is provided, which may include at least one non-transitory computer-readable storage medium having program instructions stored thereon. The stored program instructions may include program code for receiving, to a first computing device, a request to read a value. The request may be received from a second computing device via a wireless communication link between the first computing device and the second computing device. The first computing device may, for example, comprise an aerosol delivery device. The second computing device may, for example, comprise a mobile communication device. The stored program instructions may further include program code for determining an operation corresponding to the value. In this regard, each of a plurality of values that may be read from the first computing device may correspond to a different respective operation. The stored program instructions may additionally include program code for controlling the first computing device to perform the operation corresponding to the value in response to the request.
In an additional aspect, a method for causing a computing device to perform an operation in response to a read request is provided. The method may include a first computing device determining an operation for performance by a second computing device. The first computing device may, for example, comprise a mobile communication device. The second computing device may, for example, comprise an aerosol delivery device. The method may further include the first computing device determining a value corresponding to the operation. In this regard, each of a plurality of values that may be read from the second computing device may correspond to a different respective operation. The method may additionally include the first computing device formatting a request to read the value corresponding to the operation and sending the request to the second computing device via a wireless communication link between the first computing device and the second computing device to cause the second computing device to perform the operation.
In still a further aspect, an apparatus is provided, which may include processing circuitry. The apparatus may be implemented on a first computing device, such as a mobile communication device. The processing circuitry may be configured to cause the first computing device to determine an operation for performance by a second computing device. The second computing device may, for example, comprise an aerosol delivery device. The processing circuitry may be further configured to cause the first computing device to determine a value corresponding to the operation. In this regard, each of a plurality of values that may be read from the second computing device may correspond to a different respective operation. The processing circuitry may be additionally configured to cause the first computing device to format a request to read the value corresponding to the operation and to send the request to the second computing device via a wireless communication link between the first computing device and the second computing device to cause the second computing device to perform the operation.
In another aspect, a computer program product is provided, which may include at least one non-transitory computer-readable storage medium having program instructions stored thereon. The stored program instructions may include program code for determining, at a first computing device, an operation for performance by a second computing device. The first computing device may, for example, comprise a mobile communication device. The second computing device may, for example, comprise an aerosol delivery device. The stored program instructions may further include program code for determining, at the first computing device, a value corresponding to the operation. In this regard, each of a plurality of values that may be read from the second computing device may correspond to a different respective operation. The stored program instructions may additionally include program code for formatting a request to read the value corresponding to the operation and sending the request to the second computing device via a wireless communication link between the first computing device and the second computing device to cause the second computing device to perform the operation.
This Summary is provided merely for purposes of summarizing some example embodiments so as to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above described example embodiments are merely examples and should not be construed to narrow the scope or spirit of the disclosure in any way. In this regard, these and other features, aspects, and advantages of the disclosure will be apparent from a reading of the following detailed description together with the accompanying drawings, which are briefly described below. The invention includes any combination of two, three, four, or more of the above-noted embodiments as well as combinations of any two, three, four, or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined in a specific embodiment description herein. This disclosure is intended to be read holistically such that any separable features or elements of the disclosed invention, in any of its various aspects and embodiments, should be viewed as intended to be combinable unless the context clearly dictates otherwise.
Having thus described the disclosure in the foregoing general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
The present disclosure will now be described more fully hereinafter with reference to exemplary embodiments thereof. These exemplary embodiments are described so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Indeed, the disclosure may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. As used in the specification, and in the appended claims, the singular forms “a”, “an”, “the”, include plural referents unless the context clearly dictates otherwise.
Some example embodiments of the present disclosure relate to a system and related methods, apparatuses, and computer program products for controlling operation of a device based on a read request. These example embodiments may provide several advantages over prior techniques. For example, some embodiments provide a finer level of control over devices offering a more limited user interface. As a further example, in some embodiments in which a protocol, such as Bluetooth, may be used to support a read request that may be used to invoke performance of an operation, the protocol's write handlers may not have to be implemented, thereby reducing programming complexity and saving memory space on devices with relatively limited memory space (e.g., limited random access memory space and/or limited program memory), such as some aerosol delivery devices. Further, whereas a command to write a value may have to be sanitized (e.g., checked for out of bounds errors), a read request that may be used to toggle or otherwise modify a value in accordance with various example embodiments may not need to be sanitized. Additionally, using a read request to invoke performance of an operation may allow remote control of a device that may prohibit a remote device from writing to the device due to security concerns. Further, read requests may be simpler and require less time to format and transmit than a write request, which may provide a faster response time to user commands and may reduce power consumption in the device generating and sending the read request compared to power that may be required to send a write request or other explicit command for performing an operation.
Moreover, use of a read request to invoke performance of an operation by a device in accordance with various embodiments disclosed herein may be used without transferring a program instruction(s) or other instruction for storage/installation on a device, thereby offering an additional level of control over devices having limited memory space. Accordingly, in some example embodiments, a first device may invoke performance of an operation by a second device based on a read request without the second device downloading or storing any program or information from the first device.
Some example embodiments relate to invoking performance of an operation by an aerosol delivery device by sending a read request to the aerosol delivery device and to an aerosol delivery device configured to perform an operation in response to receiving such a read request. It will be appreciated, however, that embodiments described with respect to application to an aerosol delivery device are provided by way of example, and not by way of limitation. In this regard, embodiments disclosed herein may be applied mutatis mutandis to devices other than aerosol delivery devices within the scope of the disclosure.
Aerosol delivery devices according to the present disclosure may use electrical energy to heat a material (preferably without combusting the material to any significant degree) to form an inhalable substance; such articles most preferably being sufficiently compact to be considered “hand-held” devices. An aerosol delivery device may provide some or all of the sensations (e.g., inhalation and exhalation rituals, types of tastes or flavors, organoleptic effects, physical feel, use rituals, visual cues such as those provided by visible aerosol, and the like) of smoking a cigarette, cigar, or pipe, without any substantial degree of combustion of any component of that article or device. The aerosol delivery device may not produce smoke in the sense of the aerosol resulting from by-products of combustion or pyrolysis of tobacco, but rather, that the article or device most preferably yields vapors (including vapors within aerosols that can be considered to be visible aerosols that might be considered to be described as smoke-like) resulting from volatilization or vaporization of certain components of the article or device. In highly preferred embodiments, aerosol delivery devices may incorporate tobacco and/or components derived from tobacco. As such, the aerosol delivery device can be characterized as an electronic smoking article such as an electronic cigarette.
Aerosol delivery devices of the present disclosure also can be characterized as being vapor-producing articles or medicament delivery articles. Thus, such articles or devices can be adapted so as to provide one or more substances (e.g., flavors and/or pharmaceutical active ingredients) in an inhalable form or state. For example, inhalable substances can be substantially in the form of a vapor (i.e., a substance that is in the gas phase at a temperature lower than its critical point). Alternatively, inhalable substances can be in the form of an aerosol (i.e., a suspension of fine solid particles or liquid droplets in a gas). For purposes of simplicity, the term “aerosol” as used herein is meant to include vapors, gases and aerosols of a form or type suitable for human inhalation, whether or not visible, and whether or not of a form that might be considered to be smoke-like.
In use, aerosol delivery devices of the present disclosure may be subjected to many of the physical actions employed by an individual in using a traditional type of smoking article (e.g., a cigarette, cigar or pipe that is employed by lighting and inhaling tobacco). For example, the user of an aerosol delivery device of the present disclosure can hold that article much like a traditional type of smoking article, draw on one end of that article for inhalation of aerosol produced by that article, take puffs at selected intervals of time, etc.
Smoking articles of the present disclosure generally include a number of components provided within an outer shell or body. The overall design of the outer shell or body can vary, and the format or configuration of the outer body that can define the overall size and shape of the smoking article can vary. Typically, an elongated body resembling the shape of a cigarette or cigar can be a formed from a single, unitary shell; or the elongated body can be formed of two or more separable pieces. For example, a smoking article may comprise an elongated shell or body that can be substantially tubular in shape and, as such, resemble the shape of a conventional cigarette or cigar. In one embodiment, all of the components of the smoking article are contained within one outer body or shell. Alternatively, a smoking article may comprise two or more shells that are joined and are separable. For example, a smoking article may possess at one end a control body comprising a shell containing one or more reusable components (e.g., a rechargeable battery and various electronics for controlling the operation of that article), and at the other end and removably attached thereto a shell containing a disposable portion (e.g., a disposable flavor-containing cartridge). More specific formats, configurations and arrangements of components within the single shell type of unit or within a multi-piece separable shell type of unit will be evident in light of the further disclosure provided herein. Additionally, various smoking article designs and component arrangements can be appreciated upon consideration of the commercially available electronic smoking articles, such as those representative products listed in the background art section of the present disclosure.
Aerosol delivery devices of the present disclosure most preferably comprise some combination of a power source (i.e., an electrical power source), at least one control component (e.g., means for actuating, controlling, regulating and/or ceasing power for heat generation, such as by controlling electrical current flow from the power source to other components of the aerosol delivery device), a heater or heat generation component (e.g., an electrical resistance heating element or component commonly referred to as part of an “atomizer”), and an aerosol precursor composition (e.g., commonly a liquid capable of yielding an aerosol upon application of sufficient heat, such as ingredients commonly referred to as “smoke juice,” “e-liquid” and “e-juice”), and a mouthend region or tip for allowing draw upon the aerosol delivery device for aerosol inhalation (e.g., a defined air flow path through the article such that aerosol generated can be withdrawn therefrom upon draw). Exemplary formulations for aerosol precursor materials that may be used according to the present disclosure are described in U.S. Pat. Pub. No. 2013/0008457 to Zheng et al. and U.S. Pat. Pub. No. 2013/0213417 to Chong et al., the disclosures of which are incorporated herein by reference in their entirety. Representative types of aerosol precursor components and formulations also are set forth and characterized in U.S. Pat. No. 7,217,320 to Robinson et al. and U.S. Pat. Pub. Nos. 2013/0008457 to Zheng et al.; 2013/0213417 to Chong et al. and 2014/0060554 to Collett et al., the disclosures of which are incorporated herein by reference. Other aerosol precursors that may be employed include the aerosol precursors that have been incorporated in the VUSE® product by R. J. Reynolds Vapor Company, the BLU™ product by Lorillard Technologies, the MISTIC MENTHOL product by Mistic Ecigs, and the VYPE product by CN Creative Ltd. Also desirable are the so-called “smoke juices” for electronic cigarettes that have been available from Johnson Creek Enterprises LLC.
More specific formats, configurations and arrangements of components within the aerosol delivery device of the present disclosure will be evident in light of the further disclosure provided hereinafter. Additionally, the selection of various aerosol delivery device components can be appreciated upon consideration of the commercially available electronic aerosol delivery devices, such as those representative products listed in the background art section of the present disclosure. Further, the arrangement of the components within the aerosol delivery device can also be appreciated upon consideration of the commercially available electronic aerosol delivery devices, such as those representative products listed in the background art section of the present disclosure.
One example embodiment of an aerosol delivery device 100 according to the present disclosure is illustrated in
As illustrated in
It will be appreciated that
Having described several example embodiments of aerosol delivery devices that may be used with various example embodiments, several embodiments of a system and related methods, apparatuses, and computer program products for controlling operation of a device based on a read request will now be described. Such example embodiments enable a greater degree of control over devices, such as the aerosol delivery devices described above, that may have a more limited user interface compared to computing devices having fully featured user interfaces.
Device A 402 and Device B 404 may each be embodied as any computing device that may be configured to communicate with another computing device. In accordance with some example embodiments, Device A 402 may be embodied as a computing device offering a user interface with input/output mechanisms enabling a user to input commands for controlling operation of Device B 404. By way of non-limiting example, Device A 402 may be embodied as a mobile communication device, such as a smart phone, personal digital assistant (PDA), tablet computing device, a portable media device, some combination thereof, or the like. It will be appreciated, however, that Device A 402 may be embodied as a computing device other than a mobile communication device within the scope of the disclosure, including, for example, a personal computer, such as a laptop computer, desktop computer, or the like.
In accordance with some example embodiments, Device B 404 may be embodied as a computing device having relatively reduced user interface features, or that may not have any user interface features, and thus that may only provide users with course-grained control of Device B 404 through direct interaction with Device B 404. Accordingly, use of Device A 402 to provide control inputs for the Device B 404 that may be propagated to the Device B 404 in the form of corresponding read requests in accordance with various embodiments may provide users with finer-grained control of Device B 404. For example, in some embodiments, Device B 404 may be embodied as an aerosol delivery device, such as the various embodiments of aerosol delivery devices described above with respect to
Device A and Device B may be configured to establish a communication link with each other to enable Device A 402 to send a read request in accordance with various embodiments to Device B 404. The communication link may be implemented using any wireless or wireline technology configured to enable communication between two computing devices.
For example, in some embodiments, a Bluetooth technology, such as Bluetooth, Bluetooth Low Energy (also known as Bluetooth Smart and Wibree), and/or the like may be used to implement a wireless communication link between Device A 402 and Device B 404. Further examples of wireless communication technologies that may be supported by Device A 402 and/or Device B 404 and used to implement a wireless communication link between Device A 402 and Device B in accordance with some embodiments may include various wireless personal area network (WPAN) networking technologies, such as Zigbee, wireless Universal Serial Bus (USB), various Institute of Electrical and Electronics Engineers (IEEE) 802.15 technologies, and/or the like; various wireless local area network (WLAN) technologies, such as Wi-Fi direct, various IEEE 802.11 technologies, and/or the like; an Infrared Data Association (IrDA) and/or other infrared (IR) technology; near field communication (NFC); and/or other wireless communication technology that may be used to convey a read request and/or other information between computing devices.
It will be appreciated, however, that embodiments described with respect to use of Bluetooth and other types of wireless communication links between Device A 402 and Device B 404 are described by way of example, and not by way of limitation. In this regard, a wireline communication link, such as a USB link, Firewire link, Thunderbolt link, various serial communication links, and/or the like may be substituted mutatis mutandis for a wireless communication link within the scope of the disclosure.
Device B 404 may be configured to provide one or more readable values that Device A 402 may request to read (e.g., by sending a read request referencing a value to Device B 404). For example, in some embodiments, a readable value may be a value that Device A 402 may request to read, and Device B 404 may respond to the request with the requested value. In this regard, the read request may comprise a query for the readable value to which Device B 404 may respond, and in accordance with some embodiments does not include any transfer of a value or other information to Device B 404 for storage on Device B 404. Three such readable values, Value X 406, Value Y 408, and Value Z 410, are illustrated in
A readable value provided by Device B 404 may be mapped to a corresponding operation, which Device B 404 may be configured to perform in response to receiving a request to read the value from Device A 402. The operation may be any operation other than reading/returning the value. In the example of
Device B 404 may be configured to maintain mappings between the readable values and corresponding operations so that the appropriate operation may be performed in response to a read request that may be received from Device A 402. For example, in some embodiments, Device B 404 may be configured to implement a hook procedure that may be configured to intercept a request to read a value and invoke the operation corresponding to the value. Thus, for example, given a request to read Value Z 410 that may be received from Device A 402, a hook procedure may be configured to intercept the request to read Value Z 410 and to invoke performance of Other Operation Z 416 in response to the request. In some embodiments using one or more hook procedures, a hook procedure may be implemented within a function that may be used to handle a read request. Thus, for example, a function that may be used to respond to a read request by providing the requested value to Device A 402 may include a hook procedure configured to invoke an operation corresponding to the requested value in parallel to or in lieu of reading and returning the requested value.
As a further example of a mapping that may be maintained by Device B 404, in some embodiments, a readable value may be mapped to a memory location storing a reference to the operation corresponding to the value. For example, in some such embodiments, the memory location may contain a pointer to a memory location of the operation and/or a reference to a function call for invoking the operation. As such, when a request to read a value is received, the reference to the corresponding operation that may be maintained in the memory location mapped to the value may be read and used to invoke performance of the corresponding operation.
In order to invoke performance of a particular operation by Device B 404, Device A 402 may accordingly format and send a request to read the value corresponding to the operation to Device B 404. For example, Device A 402 may request to read Value X 406 to invoke performance of Other Operation X 412, may request to read Value Y 408 to invoke performance of Other Operation Y 414, and/or may request to read Value Z 410 to invoke performance of Other Operation Z 416.
In some example embodiments, a request to read a value may reference a variable that may contain or otherwise reference the value. Thus, for example, a request to read Value X 406 may reference the variable (e.g., “X”) referencing Value X 406. In some such embodiments, such as some embodiments in which Bluetooth Low Energy is used to support communication between Device A 102 and Device B 104, readable characteristics may be used by Device B 404 to reference readable values in such a manner. Thus, for example, Device A 402 may request to read Value X 406 in some example embodiments by sending an appropriate Bluetooth protocol request for reading characteristic “X.” A request to read a variable in such a manner may be interpreted by Device B 404 and used to perform the corresponding operation.
Additionally or alternatively, in some embodiments, Device A 402 may have knowledge of a memory location (e.g., a memory address) at which a value may be stored by Device B 404. In such embodiments, a request to read a value from Device B 404 may reference the memory location of the value.
Device A 402 of some example embodiments may maintain and/or have access to a mapping that may define a correspondence between operations that may be performed by Device B 404 and respective values and/or variables (e.g., characteristics or the like) referencing the values that may be read to invoke performance of those operations. As such, given an operation that Device A 402 (and/or a user thereof) wants Device B 404 to perform, Device A 402 may use the mapping to determine the value corresponding to the operation and format an appropriate request to read the value corresponding to the operation and send the request to Device B 404 to invoke performance of the operation by Device B 404.
Given an example in which Device A 402 (or a user thereof) wants to invoke performance of Other Operation X 412 by Device B 404, Device A 402 may format a request to read Value X 406 and send the request to Device B 404, as illustrated by operation 420. The request may include a reference a variable (e.g., a characteristic) referencing Value X 406, a reference to a memory location storing Value X 406, and/or other reference to Value 406.
Device B 404 may receive the request and determine that the request is a request to read Value X 406 (e.g., based on a reference to Value X 406 that may be included in the request as described above). Device B 404 may further determine that Other Operation X 412 corresponds to Value X 406 and may perform Other Operation X 412 in response to the request to read Value X 406, as illustrated by operation 430. Device B 404 may use any of the previously described techniques to determine and perform the operation (e.g., Other Operation X 412) that corresponds to Value X 406, including, for example, implementation of a hook procedure configured to intercept a request to read Value X 406 and invoke Other Operation X 412 in response thereto, reading a reference to Other Operation X 412 that may be stored in a memory location mapped to Value X 406, and/or the like.
In some example embodiments Device B 404 may be configured to send a response to the request to read Value X 406 to Device A 402, as illustrated by operation 440. For example, in some embodiments, the response may include the value (e.g., Value X 406) requested to be read by Device A 402 in operation 420. In this regard, Device B 404 may be configured to perform a read procedure for reading and providing Value X 406 in addition to (e.g., in parallel) to Other Operation X 412 in response to a request to read Value X 406 in accordance with some example embodiments, and thus may provide Value X 406 to Device A 402 in response to the request. A response to a read request including the requested value may be handled in accordance with a protocol that may be used for reading a value, such as a response to a request to read a characteristic value in accordance with various Bluetooth protocols. Additionally or alternatively, in some example embodiments, Device B 404 may be configured to respond to the request to read Value X 406 with confirmation that Other Operation X 412 was performed in response to the request.
It will be appreciated that Device B 404 may perform any of a variety of operations in response to a read request. Moreover, the set of operations that may be performed in response to a read request may vary depending on the embodiment of Device B 404, as one type of computing device may be capable of a different set of operations than another computing device (e.g., depending on device capabilities and functional purpose). As such, it will be appreciated that each of Other Operation X 412, Other Operation Y 414, and Other Operation Z 416 may comprise any respective operation that may be performed other than or in addition to read procedure that may be used to respond to a read request by providing the requested value.
In some example embodiments, a read request may be used by Device A 402 to alter a power state of Device B 404. For example, in accordance with some such embodiments, a read request may be used to turn Device B 404 off, turn Device B 404 on, place Device B 404 in a standby or low power mode of operation, switch Device B 404 from a low power or standby mode of operation to a normal power consumption mode, and/or the like.
Additionally or alternatively, in some example embodiments, a read request may be used by Device A 402 to modify a configuration setting of Device B 404. A configuration setting modification that may be modified via a read request in accordance with various embodiments may comprise a modification to any adjustable operating parameter that may relate to operation of Device B 404 and, thus, may vary depending on the embodiment of Device B 404.
As a particular example of a configuration setting that may be modified in some embodiments in which Device B 404 is embodied as an aerosol delivery device, a configuration setting for an element of a user interface of the aerosol delivery device, such as the functionality of an LED and/or other indicator(s) (e.g., the indicator 218) that may be implemented on an aerosol delivery device may be modified. Further non-limiting examples of configuration settings that may be modified via a read request in some embodiments in which Device B 404 is embodied as an aerosol delivery device may include modification of a heating profile configuration, modification of an aerosol precursor composition vaporization setting, modification of a puff control setting, modification of a battery management setting, modification of a haptic feedback configuration, modification of a flavor setting, and/or the like. For example, modification of an aerosol precursor composition vaporization setting may include modification of a configuration defining an amount of aerosol precursor composition that is vaporized per puff, and/or other configuration setting that may relate to the vaporization of aerosol precursor composition. Modification of a puff control setting may, for example, include modification of a number of puffs that are allowed within a period of time and/or for a single smoking session, modification of a minimum interval of time that must elapse between puffs, and/or modification of another setting that may govern device behavior with respect to user puffs. Modification of a battery management setting may, for example, include modification of a configuration relating to charging of a battery or other electrical power source (e.g., electrical power source 216) that may be implemented on an aerosol delivery device and/or a configuration that may regulate consumption of the battery. Modification of a haptic feedback configuration may, for example, include modification of a vibration strength of haptic feedback, activating/deactivating haptic feedback, and/or the like. Modification of a flavor setting may, for example, include modification of the type and/or concentration of a flavor that is vaporized separately or in combination with other aerosol precursor components.
In some example embodiments in which a configuration setting may be modified in response to a request to read a value, the value may specify the configuration setting. For example, a readable value may define a value within a range of possible setting values for a configuration. In accordance with some such embodiments, Device A 402 may be configured to request to read a value defining a configuration setting in order to modify the configuration setting, and Device B 404 may be configured to modify the value (e.g., by overwriting the value with a new value and/or otherwise modifying the stored value) in response to the request so as to modify the configuration setting.
In some example embodiments in which a value may be modified in response to a read request, multiple variables, such as multiple characteristics, may reference the same value. Each respective variable referencing the value may correspond to a different operation that may be performed on the value. For example, a request to read a first variable referencing the value may result in Device B 404 performing a first operation to modify the value (e.g., incrementing the value by 1) and a request to read a second variable referencing the value may result in Device B 404 performing a second operation to modify the value (e.g., decrementing the value by 1).
In some example embodiments, Device A 402 may provide a user interface enabling a user to select an operation to be performed by Device B 404 and/or to control at least some functionality of Device B 404. For example, Device A 402 may be configured to display a graphical user interface that may be provided by an application, such as a mobile app, that may be implemented on Device A 402 in accordance with some example embodiments. The graphical user interface may provide access to a plurality of selectable commands for controlling Device B 404. A user may select a command, such as by touching an appropriate region of a touch screen display, providing a voice command, and/or actuating an appropriate key, button, or other input mechanism that may be provided by Device A 402. Device A 402 may receive an indication of a command selected by the user, and may determine the operation(s) corresponding to the command. Device A 402 may format and send one or more read requests to Device B 404 to invoke performance of one or more commanded operations by Device B 404 in response to the user command.
In some example embodiments, a command that may be selected by a user of Device A 402 may be abstracted at a higher level of granularity than operations that may be performed by Device B 404 to carry out the command. Thus, for example, Device A 402 may resolve a user command into a set of operations that may need to be performed by Device B 404 in order to carry out the command, and may format and send the appropriate read requests to invoke performance of the appropriate set of operations by Device B 404.
In some example embodiments, the apparatus 500 may include processing circuitry 510 that is configurable to perform functions in accordance with one or more example embodiments disclosed herein. In this regard, the processing circuitry 510 may be configured to perform and/or control performance of one or more functionalities of apparatus 500 (e.g., functionalities of Device A 402) in accordance with various example embodiments. Thus, the processing circuitry 510 may be configured to perform data processing, application execution and/or other processing and management services according to one or more example embodiments.
In some embodiments, the apparatus 500 or a portion(s) or component(s) thereof, such as the processing circuitry 510, may be implemented via one or more integrated circuits, which may each include one or more chips. The processing circuitry 510 and/or one or more further components of the apparatus 500 may therefore, in some instances, be configured to implement an embodiment on a system on a chip.
In some example embodiments, the processing circuitry 510 may include a processor 512 and, in some embodiments, such as that illustrated in
The processor 512 may be embodied in a variety of forms. For example, the processor 512 may be embodied as various hardware processing means, such as a microprocessor, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), some combination thereof, or the like. Although illustrated as a single processor, it will be appreciated that the processor 512 may comprise a plurality of processors. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of a computing device, such as Device A 402, on which the apparatus 500 may be implemented. In some example embodiments, the processor 512 may be configured to execute instructions that may be stored in the memory 514 and/or that may be otherwise accessible to the processor 512. As such, whether configured by hardware or by a combination of hardware and software, the processor 512 may be capable of performing operations according to various embodiments while being configured accordingly.
In some example embodiments, the memory 514 may include one or more memory devices. Memory 514 may include fixed and/or removable memory devices. In some embodiments, the memory 514 may provide a non-transitory computer-readable storage medium that may store computer program instructions that may be executed by the processor 512. In this regard, the memory 514 may be configured to store information, data, applications, instructions and/or the like for enabling the apparatus 500 to carry out various functions in accordance with one or more example embodiments. In some embodiments, the memory 514 may be in communication with one or more of the processor 512, communication interface 516, user interface 518, and read control module 520 via one or more buses for passing information among components of the apparatus 500.
The apparatus 500 may further include a communication interface 516. The communication interface 516 may be configured to enable a computing device, such as Device A 402, on which the apparatus 500 may be implemented to communicate with one or more further computing devices, such as Device B 404 and/or other device that may be controlled to perform an operation by sending a read request to the device. In this regard, the communication interface 516 may include one or more interface mechanisms for enabling communication with other devices and/or networks. As such, the communication interface 516 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network (e.g., a cellular network, Wi-Fi, WLAN, and/or the like) and/or for supporting a wireless communication link with a second computing device. Thus, for example, the communication interface 516 may be configured to support various wireless communication technologies, such as by way of non-limiting example, various Bluetooth technologies (e.g., including Bluetooth Low Energy and/or regular Bluetooth technologies), Zigbee, wireless USB, various IEEE 802.15 technologies, various IEEE 802.11 technologies, IrDA and/or other IR technology, NFC, and/or other communication technologies that may be used to support wireless communication between two or more computing devices, such as between Device A 402 and Device B 404 as described above. The communication interface 516 may additionally or alternatively include a communication modem, a physical port (e.g., a serial port) for receiving a wireline communication cable, and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), USB, FireWire, Thunderbolt, Ethernet, one or more optical transmission technologies, and/or other wireline communication technology that may be used to implement a communication link between two or more computing devices, such as between Device A 402 and Device B 404 as described above.
In some example embodiments, the apparatus 500 may include the user interface 518. The user interface 518 may be in communication with the processing circuitry 510 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface 518 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, one or more biometric input devices (e.g., a visual or sensorial tracing device that may track body part or eye movements), an accelerometer, a gyroscope, and/or other input/output mechanisms. In embodiments wherein the user interface 518 comprises a touch screen display, the user interface 518 may additionally be configured to detect and/or receive an indication of a touch and/or other movement gesture or other input to the display. The user interface 518 may, for example, be configured to display a graphical user interface that may display one or more selectable commands for controlling a second computing device, such as Device B 404 as described above. The user interface 518 may further provide an input mechanism(s) for enabling the user to select the command, which may accordingly be received by the apparatus 500 via the user interface 518.
The apparatus 500 may further include read control module 520. The read control module 520 may be embodied as various means, such as circuitry, hardware, a computer program product comprising computer readable medium (for example, the memory 514) storing computer readable program instructions executable by a processing device (for example, the processor 512), or some combination thereof. In some embodiments, the processor 512 (or the processing circuitry 510) may include, or otherwise control, the read control module 520. The read control module 520 may be configured to format a request to read a value corresponding to an operation from a second device, such as Device B 404, and send the request to the second device to invoke performance of the operation by the second device, as described above. In some example embodiments in which a user may select a command via the user interface 518, the read control module 520 may be configured to resolve the command into one or more operations for performance by the second device to carry out the command, and may be configured to format and send the appropriate read requests to invoke performance of the one or more operations by the second device.
It will be appreciated that the components, devices or elements illustrated in and described with respect to
In some example embodiments, the apparatus 600 may include processing circuitry 610 that is configurable to perform and/or control performance of functions of a computing device, such as Device B 404, on which the apparatus 600 may be implemented in accordance with one or more example embodiments disclosed herein. Thus, the processing circuitry 610 may be configured to perform data processing, application execution and/or other processing and management services that may be implemented to perform functionality of the aerosol delivery device according to one or more example embodiments.
In some embodiments, the apparatus 600 or a portion(s) or component(s) thereof, such as the processing circuitry 610, may be implemented via one or more integrated circuits, which may each include one or more chips. The processing circuitry 610 and/or one or more further components of the apparatus 600 may therefore, in some instances, be configured to implement an embodiment on a system on a chip.
In some example embodiments, the processing circuitry 610 may include a processor 612 and, in some embodiments, such as that illustrated in
The processor 612 may be embodied in a variety of forms. For example, the processor 612 may be embodied as various hardware processing means, such as a microprocessor, a coprocessor, a controller or various other computing or processing devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), some combination thereof, or the like. Although illustrated as a single processor, it will be appreciated that the processor 612 may comprise a plurality of processors. The plurality of processors may be in operative communication with each other and may be collectively configured to perform one or more functionalities of a computing device, such as Device B 404, on which the apparatus 600 may be implemented. In some example embodiments, the processor 612 may be configured to execute instructions that may be stored in the memory 614 and/or that may be otherwise accessible to the processor 612. As such, whether configured by hardware or by a combination of hardware and software, the processor 612 may be capable of performing operations according to various embodiments while being configured accordingly.
In some example embodiments, the memory 614 may include one or more memory devices. Memory 614 may include fixed and/or removable memory devices. In some embodiments, the memory 614 may provide a non-transitory computer-readable storage medium that may store computer program instructions that may be executed by the processor 612. In this regard, the memory 614 may be configured to store information, data, applications, instructions and/or the like for enabling the apparatus 600 to carry out various functions in accordance with one or more example embodiments. In some embodiments, the memory 614 may be in communication with one or more of the processor 612, communication interface 616, user interface 618, and read execution module 620 via one or more buses for passing information among components of the apparatus 600.
The apparatus 600 may further include a communication interface 616. The communication interface 616 may be configured to enable a computing device, such as Device B 404, on which the apparatus 600 may be implemented to communicate with one or more further computing devices, such as Device A 402 and/or other device that may be controlled to perform an operation by sending a read request to the device. In this regard, the communication interface 616 may include one or more interface mechanisms for enabling communication with other devices and/or networks. As such, the communication interface 616 may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network (e.g., a cellular network, Wi-Fi, WLAN, and/or the like) and/or for supporting a wireless communication link with a second computing device. Thus, for example, the communication interface 616 may be configured to support various wireless communication technologies, such as by way of non-limiting example, various Bluetooth technologies (e.g., including Bluetooth Low Energy and/or regular Bluetooth technologies), Zigbee, wireless USB, various IEEE 802.15 technologies, various IEEE 802.11 technologies, IrDA and/or other IR technology, NFC, and/or other communication technologies that may be used to support wireless communication between two or more computing devices, such as between Device A 402 and Device B 404 as described above. The communication interface 616 may additionally or alternatively include a communication modem, a physical port (e.g., a serial port) for receiving a wireline communication cable, and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), USB, FireWire, Thunderbolt, Ethernet, one or more optical transmission technologies, and/or other wireline communication technology that may be used to implement a communication link between two or more computing devices, such as between Device A 402 and Device B 404 as described above.
In some example embodiments, the apparatus 600 may include the user interface 618. However, in some embodiments, one or more aspects of the user interface 618 may not be present, or the user interface 618 may be eliminated entirely. The user interface 618 may be in communication with the processing circuitry 610 to receive an indication of a user input and/or to provide an audible, visual, mechanical, or other output to a user. As such, the user interface 618 may include, for example, a keyboard, a mouse, a joystick, a display, a touch screen display, a microphone, a speaker, one or more biometric input devices (e.g., a visual or sensorial tracing device that may track body part or eye movements), an accelerometer, a gyroscope, and/or other input/output mechanisms. In embodiments wherein the user interface 618 comprises a touch screen display, the user interface 618 may additionally be configured to detect and/or receive an indication of a touch and/or other movement gesture or other input to the display.
In embodiments in which the apparatus 600 may be implemented on an aerosol delivery device, the user interface 618 may, for example, include an input mechanism(s) to enable a user to power the aerosol delivery device on/off, to activate a heating element to generate a vapor or aerosol for inhalation, and/or to otherwise actuate and/or control at least some functionality of an aerosol delivery device. For example, the user interface 618 may include a mouthpiece (e.g., mouthpiece 316), and/or associated puff sensing components (e.g., flow sensor 210), which may enable a user to provide a puff input to an aerosol delivery device. As a further example, the user interface 618 may provide one or more indicators (e.g., indicator 218), such one or more LEDs (e.g., LED 212) that may be used to indicate an operating status of an aerosol delivery device, a charge level of a battery, an amount of aerosol precursor composition remaining in a cartridge, and/or to provide other status information that may be related to operation of an aerosol delivery device to a user. In some example embodiments, the user interface 618 may include a vibrator and/or other haptic feedback device, which may impart a vibration and/or other motion on the aerosol delivery device.
The apparatus 600 may further include read execution module 620. The read execution module 620 may be embodied as various means, such as circuitry, hardware, a computer program product comprising computer readable medium (for example, the memory 614) storing computer readable program instructions executable by a processing device (for example, the processor 612), or some combination thereof. In some embodiments, the processor 612 (or the processing circuitry 610) may include, or otherwise control, the read execution module 620. The read execution module 620 may be configured to perform an operation corresponding to a value referenced in a read request that may be received by a computing device, such as Device B 404, on which the apparatus 600 may be implemented in accordance with various example embodiments disclosed herein.
Operation 700 may include determining an operation for performance by a second computing device, such as Device B 404. For example, a computing device, such as Device A 402, performing the method of
Operation 710 may include determining a value corresponding to the operation. For example, in some embodiments, operation 710 may comprise accessing a mapping between operations and references to the corresponding values, such as variables (e.g., characteristics and/or other variables that may reference a value), memory locations storing the values on the second computing device, and/or other indication that may be used to reference the corresponding value. The value corresponding to the operation (e.g., a reference thereto) may accordingly be determined by looking up the operation determined in operation 700 in the mapping to determine the corresponding value reference.
Operation 720 may include formatting a request to read the value corresponding to the operation. The request may include a reference to the value (e.g., the reference that may be determined in operation 710), such as a characteristic and/or other type of variable referencing the value, a reference to a memory location storing the value, and/or other indication that may enable the second device to determine the value requested to be read. For example, the reference to the value may be included as a parameter to the request.
Operation 730 may include sending the request to the second computing device. The request may be sent via a communication link with the second computing device. In some example embodiments, the communication link may be a wireless communication link, such as may be implemented via a Bluetooth technology. In some example embodiments, the value may also be received from the second computing device in response to the request.
Operation 800 may include receiving a request to read a value. The request may be received from a second computing device, such as Device A 402, via a communication link with the second computing device. In some example embodiments, the communication link may be a wireless communication link, such as may be implemented via a Bluetooth technology.
Operation 810 may include determining an operation corresponding to the value. For example, in some embodiments, a hook procedure may be configured to intercept the read request and invoke the operation corresponding to the value. In this regard, in some such embodiments, a request to read the value may trigger a read procedure for reading the value and the hook procedure may be implemented within the read procedure and executed in response to the read procedure such that the corresponding operation may be invoked in response to the read request. As another example, in some embodiments, the value may be mapped to (e.g., stored in) a memory location, which may store a reference to the operation corresponding to the value such that when the value is read, the corresponding operation may be determined
Operation 820 may include performing the operation corresponding to the value in response to the request. In some example embodiments, the value may also be returned to the second computing device in response to the request.
It will be understood that each block of the flowcharts in
Moreover, it will be appreciated that the ordering of blocks and corresponding method operations within the flowchart is provided by way of non-limiting example in order to describe operations that may be performed in accordance some example embodiments. In this regard, it will be appreciated that the ordering of blocks and corresponding method operations illustrated in the flowchart is non-limiting, such that the ordering of two or more block illustrated in and described with respect to the flowchart may be changed and/or method operations associated with two or more blocks may be at least partially performed in parallel in accordance with some example embodiments. Further, in some embodiments, one or more blocks and corresponding method operations illustrated in and described with respect to the flowchart may be optional, and may be omitted.
Many modifications and other embodiments of the disclosure will come to mind to one skilled in the art to which this disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed herein and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Number | Name | Date | Kind |
---|---|---|---|
1771366 | Wyss et al. | Jul 1930 | A |
2057353 | Whittemore, Jr. | Oct 1936 | A |
2104266 | McCormick | Jan 1938 | A |
2805669 | Meriro | Sep 1957 | A |
3200819 | Gilbert | Aug 1965 | A |
3316919 | Green et al. | May 1967 | A |
3398754 | Tughan | Aug 1968 | A |
3419015 | Wochnowski | Dec 1968 | A |
3424171 | Rooker | Jan 1969 | A |
3476118 | Luttich | Nov 1969 | A |
4054145 | Berndt et al. | Oct 1977 | A |
4131117 | Kite et al. | Dec 1978 | A |
4150677 | Osborne | Apr 1979 | A |
4190046 | Virag | Feb 1980 | A |
4219032 | Tabatznik et al. | Aug 1980 | A |
4259970 | Green, Jr. | Apr 1981 | A |
4284089 | Ray | Aug 1981 | A |
4303083 | Burruss, Jr. | Dec 1981 | A |
4449541 | Mays et al. | May 1984 | A |
4506682 | Muller | Mar 1985 | A |
4635651 | Jacobs | Jan 1987 | A |
4674519 | Keritsis et al. | Jun 1987 | A |
4708151 | Shelar | Nov 1987 | A |
4714082 | Banerjee et al. | Dec 1987 | A |
4735217 | Gerth et al. | Apr 1988 | A |
4756318 | Clearman et al. | Jul 1988 | A |
4771795 | White et al. | Sep 1988 | A |
4776353 | Lilja et al. | Oct 1988 | A |
4793365 | Sensabaugh, Jr. et al. | Dec 1988 | A |
4800903 | Ray et al. | Jan 1989 | A |
4819665 | Roberts et al. | Apr 1989 | A |
4821749 | Toft et al. | Apr 1989 | A |
4830028 | Lawson et al. | May 1989 | A |
4836224 | Lawson et al. | Jun 1989 | A |
4836225 | Sudoh | Jun 1989 | A |
4848374 | Chard et al. | Jul 1989 | A |
4848376 | Lilja et al. | Jul 1989 | A |
4874000 | Tamol et al. | Oct 1989 | A |
4880018 | Graves, Jr. et al. | Nov 1989 | A |
4887619 | Burcham, Jr. et al. | Dec 1989 | A |
4907606 | Lilja et al. | Mar 1990 | A |
4913168 | Potter et al. | Apr 1990 | A |
4917119 | Potter et al. | Apr 1990 | A |
4917128 | Clearman et al. | Apr 1990 | A |
4922901 | Brooks et al. | May 1990 | A |
4924888 | Perfetti et al. | May 1990 | A |
4928714 | Shannon | May 1990 | A |
4938236 | Banerjee et al. | Jul 1990 | A |
4941483 | Ridings et al. | Jul 1990 | A |
4941484 | Clapp et al. | Jul 1990 | A |
4945931 | Gori | Aug 1990 | A |
4947874 | Brooks et al. | Aug 1990 | A |
4947875 | Brooks et al. | Aug 1990 | A |
4972854 | Kiernan et al. | Nov 1990 | A |
4972855 | Kuriyama et al. | Nov 1990 | A |
4986286 | Roberts et al. | Jan 1991 | A |
4987906 | Young et al. | Jan 1991 | A |
5005593 | Fagg | Apr 1991 | A |
5019122 | Clearman et al. | May 1991 | A |
5022416 | Watson | Jun 1991 | A |
5042510 | Curtiss et al. | Aug 1991 | A |
5056537 | Brown et al. | Oct 1991 | A |
5060669 | White et al. | Oct 1991 | A |
5060671 | Counts et al. | Oct 1991 | A |
5065775 | Fagg | Nov 1991 | A |
5072744 | Luke et al. | Dec 1991 | A |
5074319 | White et al. | Dec 1991 | A |
5076296 | Nystrom et al. | Dec 1991 | A |
5093894 | Deevi et al. | Mar 1992 | A |
5095921 | Losee et al. | Mar 1992 | A |
5097850 | Braunshteyn et al. | Mar 1992 | A |
5099862 | White et al. | Mar 1992 | A |
5099864 | Young et al. | Mar 1992 | A |
5103842 | Strang et al. | Apr 1992 | A |
5121757 | White et al. | Jun 1992 | A |
5129409 | White et al. | Jul 1992 | A |
5131415 | Munoz et al. | Jul 1992 | A |
5144962 | Counts et al. | Aug 1992 | A |
5143097 | Sohn et al. | Sep 1992 | A |
5146934 | Deevi et al. | Sep 1992 | A |
5159940 | Hayward et al. | Nov 1992 | A |
5159942 | Brinkley et al. | Nov 1992 | A |
5179966 | Losee et al. | Jan 1993 | A |
5211684 | Shannon et al. | May 1993 | A |
5220930 | Gentry | Jun 1993 | A |
5224498 | Deevi et al. | Jul 1993 | A |
5228460 | Sprinkel, Jr. et al. | Jul 1993 | A |
5230354 | Smith et al. | Jul 1993 | A |
5235992 | Sensabaugh | Aug 1993 | A |
5243999 | Smith | Sep 1993 | A |
5246018 | Deevi et al. | Sep 1993 | A |
5249586 | Morgan et al. | Oct 1993 | A |
5261424 | Sprinkel, Jr. | Nov 1993 | A |
5269327 | Counts et al. | Dec 1993 | A |
5285798 | Banerjee et al. | Feb 1994 | A |
5293883 | Edwards | Mar 1994 | A |
5301694 | Raymond | Apr 1994 | A |
5303720 | Banerjee et al. | Apr 1994 | A |
5318050 | Gonzalez-Parra et al. | Jun 1994 | A |
5322075 | Deevi et al. | Jun 1994 | A |
5322076 | Brinkley et al. | Jun 1994 | A |
5339838 | Young et al. | Aug 1994 | A |
5345951 | Serrano et al. | Sep 1994 | A |
5353813 | Deevi et al. | Oct 1994 | A |
5357984 | Farrier et al. | Oct 1994 | A |
5360023 | Blakley et al. | Nov 1994 | A |
5369723 | Counts et al. | Nov 1994 | A |
5372148 | McCafferty et al. | Dec 1994 | A |
5377698 | Litzinger et al. | Jan 1995 | A |
5388574 | Ingebrethsen et al. | Feb 1995 | A |
5388594 | Counts et al. | Feb 1995 | A |
5408574 | Deevi et al. | Apr 1995 | A |
5435325 | Clapp et al. | Jul 1995 | A |
5445169 | Brinkley et al. | Aug 1995 | A |
5468266 | Bensalem et al. | Nov 1995 | A |
5468936 | Deevi et al. | Nov 1995 | A |
5479948 | Counts et al. | Jan 1996 | A |
5498850 | Das | Mar 1996 | A |
5498855 | Deevi et al. | Mar 1996 | A |
5499636 | Baggett, Jr. et al. | Mar 1996 | A |
5501237 | Young et al. | Mar 1996 | A |
5505214 | Collins et al. | Apr 1996 | A |
5515842 | Ramseyer et al. | May 1996 | A |
5530225 | Hajaligol | Jun 1996 | A |
5551450 | Hemsley | Sep 1996 | A |
5551451 | Riggs et al. | Sep 1996 | A |
5564442 | MacDonald et al. | Oct 1996 | A |
5573692 | Das et al. | Nov 1996 | A |
5591368 | Fleischhauer et al. | Jan 1997 | A |
5593792 | Farrier et al. | Jan 1997 | A |
5595577 | Bensalem et al. | Jan 1997 | A |
5596706 | Sikk et al. | Jan 1997 | A |
5611360 | Tang | Mar 1997 | A |
5613504 | Collins et al. | Mar 1997 | A |
5613505 | Campbell et al. | Mar 1997 | A |
5649552 | Cho et al. | Jul 1997 | A |
5649554 | Sprinkel et al. | Jul 1997 | A |
5659656 | Das | Aug 1997 | A |
5665262 | Hajaligol et al. | Sep 1997 | A |
5666976 | Adams et al. | Sep 1997 | A |
5666977 | Higgins et al. | Sep 1997 | A |
5666978 | Counts et al. | Sep 1997 | A |
5687746 | Rose et al. | Nov 1997 | A |
5692525 | Counts et al. | Dec 1997 | A |
5692526 | Adams et al. | Dec 1997 | A |
5708258 | Counts et al. | Jan 1998 | A |
5711320 | Martin | Jan 1998 | A |
5726421 | Fleischhauer et al. | Mar 1998 | A |
5727571 | Meiring et al. | Mar 1998 | A |
5730158 | Collins et al. | Mar 1998 | A |
5750964 | Counts et al. | May 1998 | A |
5799663 | Gross et al. | Sep 1998 | A |
5816263 | Counts et al. | Oct 1998 | A |
5819756 | Mielordt | Oct 1998 | A |
5829453 | White et al. | Nov 1998 | A |
5865185 | Collins et al. | Feb 1999 | A |
5865186 | Volsey, II | Feb 1999 | A |
5878752 | Adams et al. | Mar 1999 | A |
5880439 | Deevi et al. | Mar 1999 | A |
5894841 | Voges | Apr 1999 | A |
5915387 | Baggett, Jr. et al. | Jul 1999 | A |
5934289 | Watkins et al. | Aug 1999 | A |
5954979 | Counts et al. | Sep 1999 | A |
5967148 | Harris et al. | Oct 1999 | A |
6026820 | Baggett, Jr. et al. | Feb 2000 | A |
6033623 | Deevi et al. | Mar 2000 | A |
6040560 | Fleischhauer et al. | Mar 2000 | A |
6053176 | Adams et al. | Apr 2000 | A |
6089857 | Matsuura et al. | Jul 2000 | A |
6095153 | Kessler et al. | Aug 2000 | A |
6116247 | Banyasz et al. | Sep 2000 | A |
6119700 | Fleischhauer et al. | Sep 2000 | A |
6125853 | Susa et al. | Oct 2000 | A |
6125855 | Nevett et al. | Oct 2000 | A |
6125866 | Nichols et al. | Oct 2000 | A |
6155268 | Takeuchi | Dec 2000 | A |
6164287 | White | Dec 2000 | A |
6182670 | White | Feb 2001 | B1 |
6196218 | Voges | Mar 2001 | B1 |
6196219 | Hess et al. | Mar 2001 | B1 |
6216706 | Kumar et al. | Apr 2001 | B1 |
6289898 | Fournier et al. | Sep 2001 | B1 |
6349729 | Pham | Feb 2002 | B1 |
6357671 | Cewers | Mar 2002 | B1 |
6418938 | Fleischhauer et al. | Jul 2002 | B1 |
6446426 | Sweeney et al. | Aug 2002 | B1 |
6532965 | Abhulimen et al. | Mar 2003 | B1 |
6598607 | Adiga et al. | Jul 2003 | B2 |
6601776 | Oljaca et al. | Aug 2003 | B1 |
6615840 | Fournier et al. | Sep 2003 | B1 |
6688313 | Wrenn et al. | Feb 2004 | B2 |
6701936 | Shafer et al. | Mar 2004 | B2 |
6715494 | McCoy | Apr 2004 | B1 |
6730832 | Dominguez et al. | May 2004 | B1 |
6772756 | Shayan | Aug 2004 | B2 |
6803545 | Blake et al. | Oct 2004 | B2 |
6803550 | Sharpe et al. | Oct 2004 | B2 |
6810883 | Felter et al. | Nov 2004 | B2 |
6854461 | Nichols | Feb 2005 | B2 |
6854470 | Pu | Feb 2005 | B1 |
6994096 | Rostami et al. | Feb 2006 | B2 |
7011096 | Li et al. | Mar 2006 | B2 |
7017585 | Li et al. | Mar 2006 | B2 |
7025066 | Lawson et al. | Apr 2006 | B2 |
7117867 | Cox et al. | Oct 2006 | B2 |
7163015 | Moffitt | Jan 2007 | B2 |
7173322 | Cox et al. | Feb 2007 | B2 |
7185659 | Sharpe et al. | Mar 2007 | B2 |
7234470 | Yang | Jun 2007 | B2 |
7290549 | Banerjee et al. | Nov 2007 | B2 |
7293565 | Griffin et al. | Nov 2007 | B2 |
7392809 | Larson et al. | Jul 2008 | B2 |
7513253 | Kobayashi et al. | Apr 2009 | B2 |
7647932 | Cantrell et al. | Jan 2010 | B2 |
7690385 | Moffitt | Apr 2010 | B2 |
7692123 | Baba et al. | Apr 2010 | B2 |
7726320 | Robinson et al. | Jun 2010 | B2 |
7775459 | Martens, III et al. | Aug 2010 | B2 |
7810505 | Yang | Oct 2010 | B2 |
7832410 | Hon | Nov 2010 | B2 |
7845359 | Montaser | Dec 2010 | B2 |
7878209 | Newbery et al. | Feb 2011 | B2 |
7896006 | Hamano et al. | Mar 2011 | B2 |
8066010 | Newbery et al. | Nov 2011 | B2 |
8079371 | Robinson et al. | Dec 2011 | B2 |
8127772 | Montaser | Mar 2012 | B2 |
8156944 | Han | Apr 2012 | B2 |
8314591 | Terry et al. | Nov 2012 | B2 |
8365742 | Hon | Feb 2013 | B2 |
8375957 | Hon | Feb 2013 | B2 |
8393331 | Hon | Mar 2013 | B2 |
8402976 | Fernando et al. | Mar 2013 | B2 |
8499766 | Newton | Aug 2013 | B1 |
8528569 | Newton | Sep 2013 | B1 |
8550069 | Alelov | Oct 2013 | B2 |
8851081 | Fernando | Oct 2014 | B2 |
20020146242 | Vieira | Oct 2002 | A1 |
20030131859 | Li et al. | Jul 2003 | A1 |
20030226837 | Blake et al. | Dec 2003 | A1 |
20040020500 | Wrenn et al. | Feb 2004 | A1 |
20040050383 | Cox et al. | Mar 2004 | A1 |
20040118401 | Smith et al. | Jun 2004 | A1 |
20040129280 | Woodson et al. | Jul 2004 | A1 |
20040149296 | Rostami et al. | Aug 2004 | A1 |
20040200488 | Felter et al. | Oct 2004 | A1 |
20040226568 | Takeuchi et al. | Nov 2004 | A1 |
20040255965 | Perfetti et al. | Dec 2004 | A1 |
20050016549 | Banerjee et al. | Jan 2005 | A1 |
20050016550 | Katase | Jan 2005 | A1 |
20050066986 | Nestor et al. | Mar 2005 | A1 |
20050172976 | Newman et al. | Aug 2005 | A1 |
20050274390 | Banerjee et al. | Dec 2005 | A1 |
20060016453 | Kim | Jan 2006 | A1 |
20060070633 | Rostami et al. | Apr 2006 | A1 |
20060162733 | McGrath et al. | Jul 2006 | A1 |
20060185687 | Hearn et al. | Aug 2006 | A1 |
20060196518 | Hon | Sep 2006 | A1 |
20070074734 | Braunshteyn et al. | Apr 2007 | A1 |
20070102013 | Adams et al. | May 2007 | A1 |
20070215167 | Crooks et al. | Sep 2007 | A1 |
20070283972 | Monsees et al. | Dec 2007 | A1 |
20080085103 | Beland et al. | Apr 2008 | A1 |
20080092912 | Robinson et al. | Apr 2008 | A1 |
20080149118 | Oglesby et al. | Jun 2008 | A1 |
20080245377 | Marshall et al. | Oct 2008 | A1 |
20080257367 | Paterno et al. | Oct 2008 | A1 |
20080276947 | Martzel | Nov 2008 | A1 |
20080302374 | Wengert et al. | Dec 2008 | A1 |
20090065010 | Shands | Mar 2009 | A1 |
20090095311 | Han | Apr 2009 | A1 |
20090095312 | Herbrich et al. | Apr 2009 | A1 |
20090126745 | Hon | May 2009 | A1 |
20090128301 | Park et al. | May 2009 | A1 |
20090188490 | Han | Jul 2009 | A1 |
20090230117 | Fernando et al. | Sep 2009 | A1 |
20090260641 | Monsees et al. | Oct 2009 | A1 |
20090260642 | Monsees et al. | Oct 2009 | A1 |
20090272379 | Thorens et al. | Nov 2009 | A1 |
20090283103 | Nielsen et al. | Nov 2009 | A1 |
20090293892 | Williams et al. | Dec 2009 | A1 |
20090324206 | Young et al. | Dec 2009 | A1 |
20100006113 | Urtsev et al. | Jan 2010 | A1 |
20100023582 | Pedersen et al. | Jan 2010 | A1 |
20100024834 | Oglesby et al. | Feb 2010 | A1 |
20100043809 | Magnon | Feb 2010 | A1 |
20100059070 | Potter et al. | Mar 2010 | A1 |
20100059073 | Hoffmann et al. | Mar 2010 | A1 |
20100065075 | Banerjee et al. | Mar 2010 | A1 |
20100083959 | Siller | Apr 2010 | A1 |
20100163063 | Fernando et al. | Jul 2010 | A1 |
20100200006 | Robinson et al. | Aug 2010 | A1 |
20100229881 | Hearn | Sep 2010 | A1 |
20100242974 | Pan | Sep 2010 | A1 |
20100242976 | Katayama et al. | Sep 2010 | A1 |
20100258139 | Onishi et al. | Oct 2010 | A1 |
20100300467 | Kuistilla et al. | Dec 2010 | A1 |
20100307518 | Wang | Dec 2010 | A1 |
20100313901 | Fernando et al. | Dec 2010 | A1 |
20110005535 | Xiu | Jan 2011 | A1 |
20110011396 | Fang | Jan 2011 | A1 |
20110036363 | Urtsev et al. | Feb 2011 | A1 |
20110036365 | Chong et al. | Feb 2011 | A1 |
20110073121 | Levin et al. | Mar 2011 | A1 |
20110088707 | Hajaligol | Apr 2011 | A1 |
20110094523 | Thorens et al. | Apr 2011 | A1 |
20110120480 | Brenneise | May 2011 | A1 |
20110126847 | Zuber et al. | Jun 2011 | A1 |
20110126848 | Zuber et al. | Jun 2011 | A1 |
20110155153 | Thorens et al. | Jun 2011 | A1 |
20110155718 | Greim et al. | Jun 2011 | A1 |
20110162663 | Bryman | Jul 2011 | A1 |
20110168194 | Hon | Jul 2011 | A1 |
20110180082 | Banerjee et al. | Jul 2011 | A1 |
20110265806 | Alarcon et al. | Nov 2011 | A1 |
20110309157 | Yang et al. | Dec 2011 | A1 |
20120042885 | Stone et al. | Feb 2012 | A1 |
20120060853 | Robinson et al. | Mar 2012 | A1 |
20120111347 | Hon | May 2012 | A1 |
20120132643 | Choi et al. | May 2012 | A1 |
20120227752 | Alelov | Sep 2012 | A1 |
20120231464 | Yu et al. | Sep 2012 | A1 |
20120260927 | Liu | Oct 2012 | A1 |
20120279512 | Hon | Nov 2012 | A1 |
20120318882 | Abehasera | Dec 2012 | A1 |
20130037041 | Worm et al. | Feb 2013 | A1 |
20130056013 | Terry et al. | Mar 2013 | A1 |
20130081625 | Rustad et al. | Apr 2013 | A1 |
20130081642 | Safari | Apr 2013 | A1 |
20130192619 | Tucker et al. | Aug 2013 | A1 |
20130206154 | Fernando et al. | Aug 2013 | A1 |
20130306084 | Flick | Nov 2013 | A1 |
20130319439 | Gorelick et al. | Dec 2013 | A1 |
20130340750 | Thorens et al. | Dec 2013 | A1 |
20130340775 | Juster et al. | Dec 2013 | A1 |
20140060554 | Collett et al. | Mar 2014 | A1 |
20140060555 | Chang et al. | Mar 2014 | A1 |
20140096781 | Sears et al. | Apr 2014 | A1 |
20140096782 | Ampolini et al. | Apr 2014 | A1 |
20140202477 | Qi et al. | Jul 2014 | A1 |
20140278139 | Hong | Sep 2014 | A1 |
20150007838 | Fernando et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
276250 | Jul 1965 | AU |
2 641 869 | May 2010 | CA |
2 752 255 | Aug 2010 | CA |
1541577 | Nov 2004 | CN |
2719043 | Aug 2005 | CN |
200997909 | Jan 2008 | CN |
101116542 | Feb 2008 | CN |
101176805 | May 2008 | CN |
201379072 | Jan 2010 | CN |
103914013 | Jul 2014 | CN |
10 2006 004 484 | Aug 2007 | DE |
102006041042 | Mar 2008 | DE |
20 2009 010 400 | Nov 2009 | DE |
0 295 122 | Dec 1988 | EP |
0 430 566 | Jun 1991 | EP |
0 845 220 | Jun 1998 | EP |
1 618 803 | Jan 2006 | EP |
2 110 034 | Oct 2009 | EP |
2 316 286 | May 2011 | EP |
2 468 116 | Jun 2012 | EP |
1444461 | Jul 1976 | GB |
2469850 | Nov 2010 | GB |
2002-362730 | Dec 2002 | JP |
2006-217227 | Aug 2006 | JP |
2008-311958 | Dec 2008 | JP |
2011-517567 | Jun 2011 | JP |
20060042716 | May 2006 | KR |
WO 198602528 | May 1986 | WO |
WO 199748293 | Dec 1997 | WO |
WO 0237990 | May 2002 | WO |
WO 2004043175 | May 2004 | WO |
WO 2005099494 | Oct 2005 | WO |
WO 2007078273 | Jul 2007 | WO |
WO 2007131449 | Nov 2007 | WO |
WO 2009105919 | Sep 2009 | WO |
WO 2009155734 | Dec 2009 | WO |
WO 2010003480 | Jan 2010 | WO |
WO 2010045670 | Apr 2010 | WO |
WO 2010073122 | Jul 2010 | WO |
WO 2010091593 | Aug 2010 | WO |
WO 2010118644 | Oct 2010 | WO |
2010133342 | Nov 2010 | WO |
WO 2010140937 | Dec 2010 | WO |
WO 2011010334 | Jan 2011 | WO |
WO 2011081558 | Jul 2011 | WO |
WO 2012072762 | Jun 2012 | WO |
2012094400 | Jul 2012 | WO |
WO 2012100523 | Aug 2012 | WO |
WO 2013089551 | Jun 2013 | WO |
2013158352 | Oct 2013 | WO |
Entry |
---|
International Search Report and Written Opinion of the International Searching Authority for corresponding International Application No. PCT/US2015/038846 dated Sep. 28, 2015. |
Number | Date | Country | |
---|---|---|---|
20160007651 A1 | Jan 2016 | US |