The invention relates to providing interactive action figures or action figure accessories that have corresponding virtual counterparts in a virtual environment, and more particularly to a system and method of providing secured wireless communication with an action figure or action figure accessory.
In recent years, a number of video game/toy hybrid systems have emerged where figurines of movie, comic, or story characters can “come to life” in a video game. As an example, typical video game/toy hybrid systems enable a player to “import” a character represented by a figurine into the video game by placing the figurine on a portal device attached to a game console. Each game session may require the player to import the character (via the placement of the figurine) to utilize the character to accomplish various tasks in the game during the session. From the perspective of the player, the figurine and the character may become “synonymous” with one another as the player continues to use the figurine to access the character in the video game. As the character grows in-game (e.g., levels up) and obtains new abilities and special powers, the value of the figurine to the player may also increase—further adding to the collectability value of the figurine.
Due to the popularity of hybrid video game/toy systems, counterfeit figurines or other products for such systems are manufactured and sold to take advantage of the superior value of the imitated products, which, in turn, negatively affects the reputation of the imitated products, and reduces profits for companies that design, manufacture, and sell the imitated products. Although some systems may associate unique identifiers with their figurines (or other components) to alleviate counterfeiting issues, the unique identifiers may still be compromised and utilized to create counterfeit versions. These and other drawbacks exist.
The invention addressing these and other drawbacks relates to methods, apparatuses, or systems for providing secured wireless communication with an action figure or action figure accessory. As used herein, an action figure may comprise a figurine, made of plastic or other materials, having one or more moveable parts (e.g., moveable appendages or other moveable parts) that allow the action figure to exhibit various poses. An action figure accessory may comprise one or more physical objects that modify or supplement the functionality or appearance of an action figure (e.g., to make the action figure more useful, versatile, or attractive, to change the appearance of the action figure, etc.). A virtual environment may comprise a virtual space, a game space, a virtual universe, or other virtual environment.
In accordance with one aspect of the invention, validation of action figures or accessories and encryption of information transmitted from the action figure or accessories may be performed to ensure that the action figures or accessories are valid action figures or accessories. As an example, during a validation process, an action figure may provide one or more of its unique identifier, unique identifiers associated with its accessories, unique identifiers associated with other action figures or accessories, etc., so that the identifiers may be checked against known valid identifiers. To prevent the identifiers from being stolen, the action figure may encrypt the identifiers via one or more techniques described herein, and provide the encrypted versions of the identifiers to validate the action figure, its accessories, other action figures or accessories, etc.
In an implementation, identifiers may be pre-manufactured on silicon components, and the silicon components may be embedded into action figures or accessories with which the identifiers are to be associated. Each silicon component may, for example, carry its own unique fingerprint within its physical structure, e.g., a resulting byproduct of small fabrication errors, which can be used for identification. The unique fingerprint may be read via a contact point and transmitted to a processor of the action figure or accessory (in which the silicon component is embedded) for further processing to validate the action figure or accessory (e.g., encrypting a representation of the unique fingerprint to generate an encrypted version of the identifier that can be provided to validate the action figure or accessory).
In an implementation, an action figure or accessory and another component with which the action figure or accessory is communicating may each generate one or more shared secrets via one or more key exchanges (e.g., public key exchanges, such as Diffie-Hellman key exchange, or other key exchange), and the shared secrets may be utilized to encrypt and decrypt their sent and received information. As an example, an action figure or accessory may encrypt its identifier based on a shared secret generated via a Diffie-Hellman or other key exchange, and provide the encrypted version of the identifier to a validation component to validate the action figure or accessory.
In an implementation, a component (e.g., a validation component or other component communicating with an action figure or accessory) may provide a public key that the action figure or accessory can use to securely send information (e.g., its identifier or other information for validation or other purposes) to the component (e.g., by using the public key to encrypt the information prior to sending). As an example, the public key provided by the component may comprise a RSA-based encryption key. As such, even though the public key may be utilized as an encryption key to encrypt information to be sent to the component (e.g., a validation component), the public key cannot be used by another party to decrypt the encrypted information. On the other hand, the component (which provided the public key) may decrypt the encrypted information because of its knowledge of the prime numbers used to generate the public encryption key. In another implementation, the action figure or accessory may provide a public key that other components can use to securely send information to the action figure or accessory. As an example, the public key provided by the action figure or accessory may comprise a RSA-based encryption key that can be used to encrypt information, but cannot be used as a decryption key to decrypt to the encrypted information. However, because of its knowledge of the prime numbers used to generate the public encryption key, the action figure or accessory can decrypt encrypted information that was encrypted using the public encryption key.
In an implementation, an action figure or accessory may utilize a private key from a set of private keys stored at the action figure or accessory to encrypt information or to provide as an additional level of validation. The set of private keys may comprise one or more shared secrets (generated via a Diffie-Hellman or other key exchange) or other private keys. A host of a virtual environment (in which a virtual counterpart of the action figure or accessory exists) may, for example, provide or update the set of private keys to/for the action figure or accessory. A virtual environment host may comprise one or more virtual universe servers, game servers, or other components that host the virtual environment (e.g., a virtual space, a game space, a virtual universe, or other virtual environment).
In one implementation, a private key from the set of private keys (stored at the action figure or accessory) may be provided along with the identifier associated with the action figure or accessory for validation. Upon receipt of the private key and the identifier, a validation component may, for example, check both the identifier and the private key against a database that contains valid identifiers and the set of private keys to determine whether the action figure or accessory is a valid action figure or accessory. In this way, the use of the private key as a validation check may provide an additional level of validation. As an example, even if the action figure or accessory's identifier is compromised, a given action figure or accessory may not be validated without going through the additional validation check based on the set of private keys (e.g., which can be provided and updated by a component performing such validation checks).
In another implementation, a private key from the set of private keys (stored at the action figure or accessory) may be utilized to encrypt the identifier associated with the action figure or accessory. As an example, the action figure or accessory may utilize a shared secret (generated via a Diffie-Hellman or other key exchange) and the private key to encrypt the identifier, and the shared secret to encrypt the private key. Upon receipt of the encrypted versions of the identifier and the private key, a validation component may decrypt the encrypted version of the identifier using the shared secret and the private key, and decrypt the encrypted version of the private key using the shared secret. The validation component may then check the identifier and the private key against a database that contains valid identifiers and the set of private keys to determine whether the action figure or accessory is a valid action figure or accessory.
As another example, the action figure or accessory may utilize a RSA-based public encryption key and the private key to encrypt the identifier, and the RSA-based public encryption key to encrypt the private key. Upon receipt of the encrypted versions of the identifier and the private key, a validation component may decrypt the encrypted version of the identifier using a RSA-based decryption key (corresponding to RSA-based public encryption key) and the private key, and decrypt the encrypted version of the private key using the RSA-based decryption key. The validation component may then check the identifier and the private key against a database that contains valid identifiers and the set of private keys to determine whether the action figure or accessory is a valid action figure or accessory.
It should be noted that, although implementations described herein are with respect to action figures and action figure accessories, it is understood that (to the extent possible) other objects may be used in place of action figures and/or action figure accessories. As an example, in an implementation, a host of a virtual environment (in which a virtual counterpart of a real-world object exists) may participate in a Diffie-Hellman or other key exchange with the real-world object so that the virtual environment host (or a key management or validation component thereof) and the real-world object may each have a copy of the shared secret generated based on the key exchange that can be utilized to encrypt information, to validate the real-world object, or for other purposes.
Various other aspects, features, and advantages of the invention will be apparent through the detailed description of the invention and the drawings attached hereto. It is also to be understood that both the foregoing general description and the following detailed description are exemplary and not restrictive of the scope of the invention. As used in the specification and in the claims, the singular forms of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise. In addition, as used in the specification and the claims, the term “or” means “and/or” unless the context clearly dictates otherwise.
In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the implementations of the invention. It will be appreciated, however, by those having skill in the art that the implementations of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the implementations of the invention.
Exemplary System Description
System 100 may further comprise a user device 104 (or multiple user devices 104). User device 104 may comprise any type of mobile terminal, fixed terminal, or other device. By way of example, user device 104 may comprise a desktop computer, a notebook computer, a netbook computer, a tablet computer, a smartphone, a navigation device, an electronic book device, a gaming device, or other user device. Users may, for instance, utilize one or more user devices 104 to interact with server 102, other user devices 104, action
User device 104 may comprise interface communication subsystem 130, virtual interface subsystem 132, or other components. It should be noted that while one or more operations are described herein as being performed by components of one of server 102 or user device 104, those operations may, in some implementations, be performed by components of the other one of service 102 or user device 104.
Action
In some implementations, user device 104 may act as an intermediary between server 102, action
In some implementations, the various computers and subsystems illustrated in
The electronic storages may comprise non-transitory storage media that electronically stores information. The electronic storage media of the electronic storages may include one or both of system storage that is provided integrally (e.g., substantially non-removable) with the servers or removable storage that is removably connectable to the servers via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). The electronic storages may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storages may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). The electronic storage may store software algorithms, information determined by the processors, information received from the servers, information received from client computing platforms, or other information that enables the servers to function as described herein.
The processors may be programmed to provide information processing capabilities in the servers. As such, the processors may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. In some implementations, the processors may include a plurality of processing units. These processing units may be physically located within the same device, or the processors may represent processing functionality of a plurality of devices operating in coordination. The processors may be programmed to execute computer program instructions to perform functions described herein of subsystems 110-154 or other subsystems. The processors may be programmed to execute computer program instructions by software; hardware; firmware; some combination of software, hardware, or firmware; and/or other mechanisms for configuring processing capabilities on the processors.
It should be appreciated that the description of the functionality provided by the different subsystems 110-154 described herein is for illustrative purposes, and is not intended to be limiting, as any of subsystems 110-154 may provide more or less functionality than is described. For example, one or more of subsystems 110-154 may be eliminated, and some or all of its functionality may be provided by other ones of subsystems 110-154. As another example, additional subsystems may be programmed to perform some or all of the functionality attributed herein to one of subsystems 110-154.
Attention will now be turned to a more detailed description of various implementations comprising one or more features related to providing interactive action figures and/or action figure accessories that have corresponding virtual counterparts in a virtual environment. It should be noted that features described herein may be implemented separately or in combination with one another.
Virtual Counterpart Presentation Based on Action Figure or Accessory Information
In an implementation, action figure information obtained from an action figure may be utilized to present a virtual counterpart of the action figure in a virtual environment in which virtual counterparts of action figures interact with one another or with the virtual environment. In an implementation, action figure or accessory information may be obtained from one or more action figures or accessories. The action figure or accessory information may then be utilized to present virtual counterparts of the action figures or accessories in the virtual environment. In some implementations, presentation of virtual counterparts based on action figure or accessory information may be provided in accordance with implementations described in related co-pending U.S. patent application Ser. No. 14/622,287, entitled “SYSTEM AND METHOD FOR PRESENTING A VIRTUAL COUNTERPART OF AN ACTION FIGURE BASED ON ACTION FIGURE STATE INFORMATION,” which is hereby incorporated by reference in its entirety.
In an implementation, interface communication subsystem 130 may detect action
As an example, if interface communication subsystem 130 enables wireless communication between user device 104 and the other object (e.g., action
In one scenario, as shown in
In another scenario, accessory 108 may provide information to user device 104 (or to a host of an associated virtual environment) by transmitting the information to action
In yet another scenario, one or more action
In a further scenario, with respect to
It should be noted that, although some implementations described herein are with respect to wireless communications between one or more components of system 100, it is understood that (to the extent possible) communications between the components of system 100 may be performed via one or more wired means. For example, server 102, user device 104, action
In an implementation, virtual interface subsystem 132 may provide action figure or accessory information (received from one or more action figures or accessories) to virtual environment subsystem 112. Virtual environment subsystem 112 may generate a presentation of one or more virtual counterparts of the action figures or accessories in a virtual environment, and provide the presentation of the virtual counterparts and the virtual environment to virtual interface subsystem 132. Responsive to receiving the presentation, virtual interface subsystem 132 may provide the presentation of the virtual counterparts and the virtual environment to a user of user device 104 (e.g., via a display electronically coupled to user device 104, via a speaker electronically coupled to user device 104, or other output device).
Secured Communication With Action Figures/Accessories
In an implementation, action figures or accessories may utilize one or more keys (e.g., a private key, a public key, a shared secret, etc.) to encrypt information so that the information can be securely provided to one another, a server, or other device. As an example, action figures or accessories may be validated from time to time to ensure that a valid action figure or accessory is being used without tampering. Validation of the action figures or accessories may comprise validation of identifiers associated with the action figures or accessories. During a validation process, for example, an action figure may provide one or more of its identifier, identifiers associated with its accessories, identifiers associated with other action figures or accessories, etc., so that the identifiers may be checked against known valid identifiers. To prevent the identifiers from being stolen, the action figure may encrypt the identifiers via one or more techniques described herein, and provide the encrypted versions of the identifiers to validate the action figure, its accessories, other action figures or accessories, etc.
In an implementation, identifiers may be pre-manufactured on silicon components, and the silicon components may be embedded into action figures or accessories with which the identifiers are to be associated. As an example, rather than having an identifier stored in traditional memory, each silicon component may carry its own unique fingerprint within its physical structure, e.g., a resulting byproduct of small fabrication errors, which can be used for identification. The unique fingerprint may, for instance, be read via a contact point and transmitted to a processor of the action figure or accessory (in which the silicon component is embedded) for further processing to validate the action figure or accessory (e.g., encrypting a representation of the unique fingerprint to generate an encrypted version of the identifier that can be provided to validate the action figure or accessory). In another implementation, an identifier associated with an action figure or accessory may be stored in a non-volatile memory of the action figure or accessory (e.g., flash memory or other non-volatile memory), and the stored identifier may be retrieved when needed for validation or other purposes.
In an implementation, action
It should be noted that while one or more operations are described herein as being performed by components of server 102, those operations may, in some implementations, be performed by components of user device 104. It should also be noted that while one or more operations are described herein as being performed by components of action
In an implementation, action
In an implementation, action
In an implementation, action
In an implementation, a private key from a set of private keys (stored at action
In an implementation, server 102 (e.g., key management subsystem 114 thereof) may update a set of private keys stored at action
As another example, server 102 may update the set of private keys stored at action
In an implementation, the private keys of a set of private keys used for encryption, validation, or other purposes may be updated based on one or more time intervals, one or more usage intervals, or other intervals (e.g., without regard to whether one or more private keys have been compromised). As an example, the set of private keys stored at action
Exemplary Data Flow
Server 102 may obtain a set of private keys that is to be used by action
In operations 316 and 318, action
It should be noted that, while operations 302-318 are described with respect to use of a shared secret generated via a Diffie-Hellman or other key exchange, other cryptographic techniques may be utilized. As an example, action
As another example, server 102 may generate a public encryption key (e.g., a RSA-based public encryption key or other public encryption key) that can be used by others to encrypt information, but cannot be used by others as a decryption key to decrypt information encrypted using the public encryption key. Server 102 may provide the public encryption key to action
In operation 320, server 102 may decrypt the encrypted versions of the identifier and/or the private key, and utilize the identifier and/or the private key to validate action
It should be noted that, while one or more operations are described herein (e.g., operations 302-320 or other operations) as being performed by server 102, those operations may, in some implementations, be performed by user device 104. It should also be noted that while one or more operations are described herein as being performed by action
Exemplary Flowcharts
In some implementations, the methods may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of the methods in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of the methods.
In an operation 402, a device may be detected within a short wireless communication range of an action figure or action figure accessory. Operation 402 may be performed by a communication subsystem that is the same as or similar to action figure communication subsystem 140 or accessory communication subsystem 150, in accordance with one or more implementations.
In an operation 404, a wireless connection between the action figure or action figure accessory and the device may be established based on the detection. Operation 404 may be performed by a communication subsystem that is the same as or similar to action figure communication subsystem 140 or accessory communication subsystem 150, in accordance with one or more implementations.
In an operation 406, a first key stored at the action figure or action figure accessory may be obtained. As an example, the first key may comprise a first private key. As another example, the first private key may comprise a shared secret generated via a Diffie-Hellman or other key exchange, a private decryption key (e.g., generated via RSA-based techniques), or a private key obtained via another technique. Operation 406 may be performed by a key subsystem that is the same as or similar to action figure key subsystem 142 or accessory key subsystem 152, in accordance with one or more implementations.
In an operation 408, first encrypted information may be received from the device via the wireless connection. As an example, the first encrypted information may comprise an encrypted version of a second key that is to be used by the action figure or action figure accessory for encryption, validation, or other purposes. Operation 408 may be performed by a key subsystem that is the same as or similar to action figure key subsystem 142 or accessory key subsystem 152, in accordance with one or more implementations.
In an operation 410, the first encrypted information may be processed based on the first key (e.g., a shared secret or other key) to determine the second key. As an example, the second key may comprise a second private key. Operation 410 may be performed by a key subsystem that is the same as or similar to action figure key subsystem 142 or accessory key subsystem 152, in accordance with one or more implementations.
In an operation 412, an identifier associated with the action figure or action figure accessory may be obtained. Operation 412 may be performed by a validation subsystem that is the same as or similar to action figure validation subsystem 144 or accessory validation subsystem 154, in accordance with one or more implementations.
In an operation 414, second encrypted information may be generated based on the second key and the identifier. As an example, the second encrypted information may comprise an encrypted version of the identifier. Operation 414 may be performed by a key subsystem that is the same as or similar to action figure key subsystem 142 or accessory key subsystem 152, in accordance with one or more implementations.
In an operation 416, the second encrypted information may be provided to the device via the wireless connection. Operation 416 may be performed by a validation subsystem that is the same as or similar to action figure validation subsystem 144 or accessory validation subsystem 154, in accordance with one or more implementations.
In an operation 502, a first public key associated with a first private key may be provided to an action figure or action figure accessory. As an example, the first public key may comprise (i) a public key to be used to generate a shared secret, (ii) a public encryption key (e.g., a RSA-based public encryption key or other public encryption key) to be used by others to encrypt (but not decrypt) information, or (iii) other public key. Operation 502 may be performed by a key subsystem that is the same as or similar to key management subsystem 114, in accordance with one or more implementations.
In an operation 504, first encrypted information comprising an encrypted version of a second key may be generated. As an example, the second key may comprise a second private key. The second private key may be encrypted via one or more techniques described here to generate the first encrypted information. Operation 504 may be performed by a key subsystem that is the same as or similar to key management subsystem 114, in accordance with one or more implementations.
In an operation 506, the first encrypted information may be provided to the action figure or action figure accessory. Operation 506 may be performed by a key subsystem that is the same as or similar to key management subsystem 114, in accordance with one or more implementations.
In an operation 508, second encrypted information may be received from the action figure or action figure accessory. As an example, the second encrypted information may be generated at the action figure or action figure accessory based on the first public key, the second key, and an identifier associated with the action figure or action figure accessory. Upon generation, the second encrypted information may comprise an encrypted version of the identifier. The generated second encrypted information may be received from the action figure or action figure accessory. Operation 508 may be performed by a validation subsystem that is the same as or similar to validation management subsystem 116, in accordance with one or more implementations.
In an operation 510, the second encrypted information may be processed based on the first private key and the second key to obtain the identifier. Operation 510 may be performed by a validation subsystem that is the same as or similar to validation management subsystem 116, in accordance with one or more implementations.
In an operation 512, a virtual counterpart of the action figure or action figure accessory in a virtual environment may be presented based on the identifier. Operation 512 may be performed by a virtual environment subsystem that is the same as or similar to virtual environment subsystem 112, in accordance with one or more implementations.
Although the present invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.
This application is a continuation of U.S. patent application Ser. No. 14/636,115, filed Mar. 2, 2015 (which issued as U.S. Pat. No. 9,205,336 on Dec. 8, 2015), the content of which is hereby incorporated by reference herein in its entirety. This application is also related to following, co-pending U.S. utility patent applications, filed on Feb. 13, 2015: (1) U.S. patent application Ser. No. 14/622,287, entitled “SYSTEM AND METHOD FOR PRESENTING A VIRTUAL COUNTERPART OF AN ACTION FIGURE BASED ON ACTION FIGURE STATE INFORMATION,” (2) U.S. patent application Ser. No. 14/622,321, entitled “SYSTEM AND METHOD FOR PROVIDING STATE INFORMATION OF AN ACTION FIGURE,” (3) U.S. patent application Ser. No. 14/622,354, entitled “SYSTEM AND METHOD FOR PROVIDING AN ENHANCED MARKETING, SALE, OR ORDER FULFILLMENT EXPERIENCE RELATED TO ACTION FIGURES OR ACTION FIGURE ACCESSORIES HAVING CORRESPONDING VIRTUAL COUNTERPARTS,” and (4) U.S. patent application Ser. No. 14/622,386, entitled “SYSTEM AND METHOD FOR PROVIDING RELEVANT NOTIFICATIONS VIA AN ACTION FIGURE,” each of which is hereby incorporated by reference herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5766077 | Hongo | Jun 1998 | A |
6012961 | Sharpe, III et al. | Jan 2000 | A |
6159101 | Simpson | Dec 2000 | A |
6290565 | Galyean III et al. | Sep 2001 | B1 |
6354947 | Dobrusskin et al. | Mar 2002 | B1 |
6773325 | Mawle et al. | Aug 2004 | B1 |
6773344 | Gabai | Aug 2004 | B1 |
7066781 | Weston | Jun 2006 | B2 |
7502759 | Hannigan et al. | Mar 2009 | B2 |
7610233 | Leong et al. | Oct 2009 | B1 |
7828295 | Matsumoto et al. | Nov 2010 | B2 |
7843471 | Doan et al. | Nov 2010 | B2 |
7862428 | Borge | Jan 2011 | B2 |
8257157 | Polchin | Sep 2012 | B2 |
8287372 | Hong et al. | Oct 2012 | B2 |
8585497 | Borge | Nov 2013 | B2 |
8595811 | Johnson et al. | Nov 2013 | B2 |
8602857 | Morichau-Beauchant et al. | Dec 2013 | B2 |
8636588 | Borge | Jan 2014 | B2 |
8734242 | Borge | May 2014 | B2 |
8858339 | Reiche et al. | Oct 2014 | B2 |
9205336 | Yano | Dec 2015 | B1 |
9259651 | Yano | Feb 2016 | B1 |
9266027 | Yano | Feb 2016 | B1 |
9361067 | Yano | Jun 2016 | B1 |
20030027636 | Covannon et al. | Feb 2003 | A1 |
20050059483 | Borge | Mar 2005 | A1 |
20050266920 | Kaku et al. | Dec 2005 | A1 |
20060070029 | Laborczfalvi et al. | Mar 2006 | A1 |
20060084362 | Ghaly | Apr 2006 | A1 |
20060273909 | Heiman et al. | Dec 2006 | A1 |
20070015588 | Matsumoto | Jan 2007 | A1 |
20070097832 | Koivisto et al. | May 2007 | A1 |
20070197297 | Witchey | Aug 2007 | A1 |
20080081694 | Hong et al. | Apr 2008 | A1 |
20090053970 | Borge | Feb 2009 | A1 |
20090054155 | Borge | Feb 2009 | A1 |
20090098792 | Cheng et al. | Apr 2009 | A1 |
20090117819 | Nakamura | May 2009 | A1 |
20090158210 | Cheng | Jun 2009 | A1 |
20100088650 | Kaltenbach et al. | Apr 2010 | A1 |
20100151940 | Borge | Jun 2010 | A1 |
20110014984 | Penman et al. | Jan 2011 | A1 |
20110021109 | Le et al. | Jan 2011 | A1 |
20110047600 | Johnson et al. | Feb 2011 | A1 |
20110124264 | Garbos | May 2011 | A1 |
20120191880 | Gandhi et al. | Jul 2012 | A1 |
20120295703 | Reiche et al. | Nov 2012 | A1 |
20130044570 | Mkrtchyan | Feb 2013 | A1 |
20130288563 | Zheng et al. | Oct 2013 | A1 |
20130296058 | Leyland et al. | Nov 2013 | A1 |
20130307848 | Tena et al. | Nov 2013 | A1 |
20140030955 | Smetanin et al. | Jan 2014 | A1 |
20140057527 | Fessenmaier | Feb 2014 | A1 |
20140088750 | Sharma et al. | Mar 2014 | A1 |
20140114630 | Brave | Apr 2014 | A1 |
20140121008 | Canessa | May 2014 | A1 |
20140162785 | Reiche et al. | Jun 2014 | A1 |
20140227676 | Noshadi et al. | Aug 2014 | A1 |
20140273717 | Judkins et al. | Sep 2014 | A1 |
20140273721 | Katan et al. | Sep 2014 | A1 |
20140274313 | Bala et al. | Sep 2014 | A1 |
20140357373 | Barney et al. | Dec 2014 | A1 |
20150038229 | Reiche et al. | Feb 2015 | A1 |
20150080121 | Garlington et al. | Mar 2015 | A1 |
20150174479 | Reiche et al. | Jun 2015 | A1 |
20150375128 | Villar et al. | Dec 2015 | A1 |
Number | Date | Country |
---|---|---|
2014055924 | Apr 2014 | WO |
Entry |
---|
U.S. Appl. No. 14/645,228, a non-Final Office Action, mailed May 22, 2015, 45 pages. |
U.S. Appl. No. 14/622,354, a non-Final Office Action, mailed Jun. 5, 2015, 12 pages. |
U.S. Appl. No. 14/622,287, a non-Final Office Action, mailed Jun. 24, 2015, 20 pages. |
U.S. Appl. No. 14/622,386, a non-Final Office Action, mailed Jul. 6, 2015, 14 pages. |
U.S. Appl. No. 14/622,321, a non-Final Office Action, mailed Jul. 24, 2015, 10 pages. |
U.S. Appl. No. 14/645,228, a Final Office Action, mailed Sep. 15, 2015, 28 pages. |
U.S. Appl. No. 14/636,115, a Notice of Allowance, mailed Oct. 7, 2015, 9 pages. |
U.S. Appl. No. 14/622,386, a Notice of Allowance, mailed Nov. 30, 2015, 9 pages. |
U.S. Appl. No. 14/622,354, a Notice of Allowance, mailed Dec. 22, 2015, 10 pages. |
U.S. Appl. No. 14/622,321, a non-final Office Action, mailed Jan. 6, 2016, 12 pages. |
U.S. Appl. No. 14/622,287, a Final Office Action, mailed Jan. 7, 2016, 18 pages. |
U.S. Appl. No. 14/645,228, a Notice of Allowance, mailed Apr. 11, 2016, 20 pages. |
U.S. Appl. No. 14/622,287, a non-final Office Action issued, mailed Jun. 20, 2016, 19 pages. |
International Patent Application No. PCT/US2016/016303, an International Search Report and Written Opinion mailed Jun. 16, 2016, 16 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 14636115 | Mar 2015 | US |
Child | 14961040 | US |