Graphical user interface and data transfer methods in a controlling device
Summary by NHIP
Pop-up Remote Widget System
The system superimposes a pop-up remote control widget over a smart device display in response to user input. This widget presents a selectable subset of icons controlling specific functional operations of a target device without requiring a switch to the main application.
Claim Score by NHIP
Abstract
A smart device is provided with a main remote control application that may be configured using information obtained from a QR code. The main remote control application may present images of original remote controls corresponding to devices which are controllable by the configured main remote control application. In connection with a presented image of an original remote control, the display may present icons that are representative of a subset of the buttons of the original remote control. The user interface also allows a user to select amongst the images of the original remote controls to change which appliances are to be controlled via the user interface. A pop-up remote control widget may also be provided which may be invoked without switching to the main remote control application provisioned on the smart device.

Term
6.1 yearsleft in the term
Expires 5 November 2032, including 322 days of term adjustment.
- Priority
- Filed
- Granted
- Today
- Expires
18 claims: 2 independent, 16 dependent
- 1Broadest claimClaim Score 36, narrow(NHIP)A non-transitory, computer-readable media having stored thereon instructions which, when executed by a processing device, perform steps comprising:responding to predetermined first user input provided to a smart device to cause a pop-up remote control widget associated with a main remote control application provisioned on the smart device to be superimposed in a display of the smart device over a current smart device display data;wherein the pop-up remote control widget presents in the display of the smart device a first plurality of icons, wherein each of the first plurality of icons of the pop-up remote control widget is selectable to cause a command to be issued from the smart device to control a one of a first plurality of functional operations of an intended target controllable device, wherein the first plurality of functional operations of the intended target controllable device that are controllable via selections of the first plurality of icons of the pop-up remote control widget is a subset of a second plurality of functional operations of the intended target controllable device that are controllable via use of the main remote control application, and wherein the pop-up remote control widget is capable of being invoked at any point without switching to the main remote control application provisioned on the smart device.
- 8A non-transitory, computer-readable media having stored thereon instructions which, when executed by a processing device, perform steps comprising:responding to predetermined first user input provided to a smart device to cause a pop-up remote control widget associated with a main remote control application provisioned on the smart device to be superimposed in a display of the smart device over a current smart device display data;wherein the pop-up remote control widget presents in the display of the smart device a first plurality of icons, wherein each of the first plurality of icons of the pop-up remote control widget is selectable to cause a command to be issued from the smart device to control a one of a first plurality of functional operations of respective one of a first intended target controllable device and a second intended target device, wherein the first plurality of functional operations of the first and second intended target controllable devices that are controllable via selections of the first plurality of icons of the pop-up remote control widget is a subset of a second plurality of functional operations of the first and second intended target controllable devices that are controllable via use of the main remote control application, and wherein the pop-up remote control widget is capable of being invoked at any point without switching to the main remote control application provisioned on the smart device.
Independent claims2
27 paragraphs in 5 sections, as filed
RELATED APPLICATION INFORMATION
0001This application claims the benefit of and is continuation of U.S. application Ser. No. 13/329,940, filed on December 19, 2011, which application claims the benefit of U.S. Provisional Patent Application No. 61/442,488, filed Feb. 11, 2011, the disclosures of which are incorporated herein by reference in its entirety.
BACKGROUND
0002Personal communication, productivity, and entertainment devices such as tablet computers, smart phones, portable email devices, e-books, hand-held games and/or game controllers, portable media players, etc. (all referred to hereafter as “smart devices”) are known to include features such as graphical user interfaces on color touch screens, wireless Internet capability, and support for ancillary applications (sometimes referred to as “apps”) such as, for example, calendars, email, maps and navigation, etc. Such ancillary applications may be pre-installed in a smart device or may be made available for download by a user. Certain such apps may comprise an ability to issue commands to entertainment and other appliances, for example to offer the features and functionality of a universal remote control, to operate in conjunction with a TV guide display to enable channel selection, etc. Typically such remote control apps may be provisioned with a library of command data and protocols suitable for controlling a plurality of appliances of different type and/or manufacture (a so-called “universal remote”). Such a command library and the hardware necessary to transmit operational commands to appliances may be incorporated into or made available to the smart device itself, or may take the form of a separate external device which is placed in communication with the smart device (i.e., a relay device or so-called “blaster”). After initial installation and configuration of such a smart device app, a GUI may be provided by means of which a user may be enabled to issue operational commands to the configured appliances. Disclosed herein are user-friendly and convenient GUI methods for facilitating command input and for transferring configuration data between smart devices.
SUMMARY
0003The following relates generally to remote control systems and, more particularly, to methods for presenting a GUI on a portable device, e.g., a smart device which may incorporate universal remote control functionality to command operation of one or more types of remotely controllable appliances of one or more manufacturers. Exemplary smart devices include but are not limited to Apple's “iPhone” and “iPad,” Google's “Android” platform, Nintendo's “Wii U” controller, Blackberry's “Torch” or “PlayBook,” and various other tablet computers and/or smart phones. Exemplary types of appliances include, but are not limited to televisions, digital video disc players (DVDs), cable or satellite set top boxes (STBs), digital video recorders (DVRs), audio video (AV) receivers, thermostats, game consoles, lighting systems, etc.
0004In one described aspect, a smart device remote control application may be furnished with a touch screen GUI the activatable icons of which approximate the layout of the target appliances original equipment remote control. Since differences in keypad size, form factor, or GUI aesthetics may necessitate that only a portion of the replicated keypad can be displayed at any one time, a user may be provided with a means to scroll within the GUI display. Separately or in conjunction with this feature, user selection of a particular target device to control, e.g. TV, DVD, STB, etc., may be made using a slide-out or pull-down menu comprising images representative of original equipment remote controls.
0005In another described aspect, provision may be made in a smart device remote control app for a quick loading mini control panel comprising frequently used control functions, such as for example those associated with volume control, which may be invoked by a user without necessitating a loading of the full remote control GUI or interruption of other currently running apps.
0006In a yet further described aspect, a remote control app, once installed and configured in a first smart device, may be enabled to display a matrix barcode, such as for example a so-called Quick Response Code or “QR code” containing the remote control apps current configuration data. This displayed matrix barcode may then be photographed, optically recognized, or otherwise captured by a second smart device in order to rapidly and conveniently configure a remote control app resident in said second smart device to match the configuration of the remote control app of the first smart device.
0007A better understanding of the objects, advantages, features, properties and relationships of the various aspects described hereinafter will be obtained from the following detailed description and accompanying drawings which set forth illustrative embodiments and which are indicative of the various ways in which the principles of the invention claimed hereinafter may be employed.
BRIEF DESCRIPTION OF THE DRAWINGS
For a better understanding of the claimed invention, reference may be had to preferred embodiments shown in the attached drawings in which:
<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system in which a smart device equipped with a remote control app constructed according to the description that follows may be used;
<figref idref="DRAWINGS">FIG. 2</figref> illustrates in block diagram form the major components of the exemplary smart device of <figref idref="DRAWINGS">FIG. 1</figref>;
<figref idref="DRAWINGS">FIG. 3</figref> illustrates an exemplary smart device GUI for use in issuing commands to controlled appliances;
<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary smart device GUI for use in selecting an appliance to be controlled;
<figref idref="DRAWINGS">FIG. 5</figref> illustrates an exemplary pop up mini remote control GUI;
<figref idref="DRAWINGS">FIG. 6</figref> illustrates exemplary matrix barcodes which may encode configuration information for use by a remote control app of a smart device; and
<figref idref="DRAWINGS">FIG. 7</figref> illustrates exemplary situations in which matrix barcodes such as those of <figref idref="DRAWINGS">FIG. 6</figref> may be utilized to transfer information to a remote control app of a smart device.
DETAILED DESCRIPTION
0016By way of example, <figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary system wherein a smart device <b>100</b> may be adapted to issue commands to controllable appliances such as a TV <b>102</b>, a set top box (STB) <b>104</b>, an audio/video receiver (AVR) <b>106</b>, a DVD player <b>108</b>, etc. While illustrated in the context of a home entertainment system comprising a TV, STB, AVR and DVD player, it is to be understood that controllable appliances may include, but need not be limited to, televisions, VCRs, DVRs, DVD players, cable or satellite converter set-top boxes (“STBs”), amplifiers, AV receivers, CD players, game consoles, home lighting, drapery, fans, HVAC systems, thermostats, personal computers, etc. In the illustrative example of <figref idref="DRAWINGS">FIG. 1</figref>, a smart device <b>100</b> may include both a universal remote control app and the necessary hardware to enable direct transmission of commands to appliances <b>102</b> through <b>108</b>, for example without limitation the technology described in co-pending U.S. patent application Ser. No. 13/043,915 which is incorporated herein by reference in its entirety. Appliance commands may be issued in the form of infrared signals <b>110</b> as illustrated, or in any other suitable format, e.g., via an RF signal such as contemplated by RF4CE, Zwave, Bluetooth, etc.; ultrasonic signal; visible light; etc. as appropriate for the control of each particular appliance. In alternative embodiments appliance commands may be issued indirectly via a proxy, or relay device, which is responsive to wireless communications received from the universal remote control app resident in smart device <b>100</b>, for example as described in co-pending U.S. patent applications Ser. Nos. 13/071,661 or 13/328,416, which are also incorporated herein by reference in their entirety. Since the techniques and methods described herein are equally applicable to either embodiment, these will be described hereafter with reference to the system of <figref idref="DRAWINGS">FIG. 1</figref>, it being understood that these may be applied mutatis mutandis to other embodiments which may utilize a relay device for issuance of appliance commands.
0017With reference to <figref idref="DRAWINGS">FIG. 2</figref>, as is known in the art, a smart phone device <b>100</b> may include as needed for a particular application, processing means <b>200</b> which may comprise both an application processing section <b>202</b> and an RF/DSP processing section <b>204</b>; an LCD display <b>206</b>; a keypad <b>208</b> which may comprise physical keys, touch keys overlaying LCD <b>206</b>, or a combination thereof; a subscriber identification module (SIM) card <b>210</b>; memory means <b>212</b> which may comprise ROM, RAM, Flash, or any combination thereof; WiFi and/or Bluetooth wireless interface(s) <b>214</b>; a wireless telephony interface <b>216</b>; power management circuitry <b>218</b> with associated battery <b>220</b>; a USB interface <b>222</b> and connector <b>224</b>; an audio management system <b>226</b> with associated microphone <b>228</b>, speaker <b>230</b>, and headphone jack <b>232</b>; optional IR communication means comprising a transmitter and/or receiver <b>236</b> with associated IR output diode(s) <b>234</b>; and various optional accessory features <b>238</b> such as a digital camera, GPS, accelerometer, etc.
0018A remote control app resident in such a smart device may draw on a library of codes and data suitable for commanding the functional operations of various types of appliances of multiple manufactures and/or models, i.e., a library of remote control codesets for a so-called “universal” controller, as well known in the art. Upon initial installation, the remote control app may be provisioned with the specific command data and protocol (“codeset”) to which each of the to-be-controlled appliances is responsive. As is known in the art, this may take the form of a pointer or index into a library of codesets pre-stored locally in the memory <b>212</b> of smart device <b>100</b> or of a relay device; individual codesets downloaded to those devices during a configuration process; an item-by-item download of individual commands from a codeset on an as-required basis from a library stored locally on a PC or on an appliance such as STB <b>104</b> or TV <b>102</b>, or stored remotely at a headend or internet accessible server; etc. Since methods to accomplish the identification of suitable commands and/or codesets for controlled appliances are well known in the art, for the sake of brevity these will not be further described herein. Nevertheless, for more information in this regard the interested reader may turn to, for example, co-pending U.S. patent application Ser. Nos. 13/198,072, 13/198,172, or 13/240,604, all of common ownership and all incorporated herein by reference in their entirety.
0019In keeping with the objectives of subject disclosure, identification and provisioning of appliance command codesets may include a provisioning of appropriate image elements and data for use in presenting the GUI displays described herein. As will become apparent, such image elements and data may include pictures, simulacrums, graphics, layout information, key position maps, etc. as necessary to create graphical representations of each appliance's original equipment remote control. Such data may be retrieved together with the command codesets, or may be available from an independent source such as a Web service which may be separately accessed by the smart device remote control app once an exact appliance identity has been established, as appropriate for a particular embodiment.
0020With reference to <figref idref="DRAWINGS">FIG. 3</figref>, when a smart device remote control app in accordance with the invention described herein is invoked, it may display a GUI <b>300</b> which may be representative of the original equipment remote control corresponding to the currently selected appliance. As illustrated, GUI <b>300</b> may comprise an area <b>302</b> containing touch-activated icons arranged in a layout which approximates a portion of the OEM remote control keypad. A second area <b>304</b> may contain an image <b>306</b> representative of the entire OEM remote control which may serve to identify to the user of the app both which appliance is currently under control (STB <b>104</b> in the example presented) and, for example by means of a highlighted area <b>308</b>, which section of the OEM remote control keypad is currently being displayed in area <b>302</b>. In order to access other functional areas of the remote control GUI, for example an upper section <b>310</b> or lower section <b>312</b> of the simulated OEM keypad, the remote control app may be enabled to recognize vertical sliding motions <b>314</b> of a user's finger as requests to scroll back and forth within the interface. In some embodiments this input may be recognized only if performed within area <b>304</b>, while in other embodiments it may recognized when performed anywhere on the touch sensitive surface of smart device <b>100</b> (i.e., both areas <b>302</b> and <b>304</b> of the illustrated example). In yet further embodiments, a finger tap on the desired area of remote control image <b>306</b> may be used to select the keys to be presented in area <b>302</b>, either in place of as an alternate to the sliding motions described above. As the interface scrolls, the highlight area <b>308</b> of OEM remote control image <b>306</b> may adjust accordingly so as to correspond with the OEM remote control section displayed in area <b>302</b>.
0021With reference to <figref idref="DRAWINGS">FIG. 4</figref>, in order to permit user selection of different target appliances to be controlled a smart device remote control app may be enabled to recognize a generally horizontal sliding motion <b>408</b> of a user's finger commencing within area <b>304</b> as a request to change controlled appliance. In response to such a gesture, the remote control app may cause display area <b>304</b> to expand horizontally as illustrated at <b>304</b>′ in illustrative display <b>400</b>. The expanded display in area <b>304</b>′ may comprise representations of the OEM remote controls of the appliances currently configured to be controlled by the remote control app. In the illustrative example these may include image <b>402</b> representative of remote control provided with TV <b>102</b>, image <b>404</b> representative of remote control provided with AVR <b>106</b>, image <b>406</b> representative of remote control provided with DVD player <b>108</b>, and image <b>306</b>′ representative of a remote control provided with STB <b>104</b>. Selection of the appliance to be controlled may now be conveniently accomplished by way of a finger tap on the image representing a remote control for controlling the desired appliance. Upon selection of an image, the remote control app may automatically return to a state such as illustrated in <figref idref="DRAWINGS">FIG. 3</figref> with the newly selected remote control device being displayed. Selection of an area of the display screen (or provision of other input that is not recognized as a selection of an image) can also be used to manually return the remote control app to a state such as illustrated in <figref idref="DRAWINGS">FIG. 3</figref> with the remote control that was displayed upon receiving the generally horizontal input <b>408</b> again being displayed. Alternatively, the images presented for selection can be representations of the appliances that are to be controlled via the current configuration of the remote control app in lieu of or together with the images of the remote controls provided with such appliances.
0022In some embodiments, a smart device remote control app may support a user convenience feature in the form of a pop-up remote control widget, for example as illustrated in <figref idref="DRAWINGS">FIG. 5</figref>. Exemplary widget pop-up GUI <b>502</b> may comprise a limited set of pre-determined, frequently used appliance command functions, for example providing a user direct access to the five basic functions Home, Volume Up, Volume down, Mute and Play/pause as illustrated. As will be appreciated, a user of the remote control app may be required to configure these pop-up key assignments during the smart device remote control app initial installation process, e.g., by specifying the particular appliance to which each of the basic commands is to be directed, for example TV or AVR for volume functions and STB or DVD for play/pause in the illustrative system of <figref idref="DRAWINGS">FIG. 1</figref>. Once configured, widget GUI <b>502</b> may be invoked at any point without switching to the main remote control application, for example by activating an icon provided for that purpose, by a gesture, by motion of the smart device such as shaking or flipping, etc., as appropriate for a particular embodiment. When invoked, the widget GUI <b>502</b> may be temporarily superimposed over the current smart device display data <b>500</b>, for example using a smart device OS feature such the Android operating system “PopupWindow” class. Once the desired appliance adjustments have been made, widget GUI <b>502</b> may be returned to the idle state (e.g., a non-displayed state) by repeating the action which invoked it, by touching smart device screen <b>500</b> in an area outside of widget display <b>502</b>, etc., as appropriate. In a further embodiment, the command buttons presented with the widget GUI <b>502</b> may be dynamically changed or updated by the remote control app to present only those command buttons that the remote control app determines are most often selected by a user or a known user. To this end, the remote control app would then include a monitoring and counting feature to keep track of command selection by a user or known user (to the extent the widget GUI <b>502</b> is to be personalized). A displayed matrix barcode may also be utilized to conveniently transfer remote control app configuration information from an appliance or computer to a smart device, or to transfer configurations between smart devices. In an illustrative embodiment a standardized matrix barcode such as the Denso Wave “Quick Response” or QR code may be utilized. The QR code format is appropriate for this application since it is scaleable up to a maximum data content of 2,953 bytes and is widely supported by built-in smart device operating systems and image recognition software, both on-board and cloud-based. Since the encoding and decoding techniques utilized in conjunction with QR matrix codes are standardized and widely known, these will not be described in further detail herein. Nevertheless, for additional information on this subject the interested reader may turn to published standards such as for example ISO/IEC publication 18004: “<i>Information technology—Automatic identification and data capture technique—QR Code </i>2005 <i>bar code symbology specification.”</i>
0023By way of example without limitation, QR codes suitable for use in configuring a smart device remote control app are illustrated in <figref idref="DRAWINGS">FIGS. 6 and 7</figref>, along with a human-readable representation of the data encoded therein. QR code <b>602</b>, representative of a matrix barcode which may be used to identify a specific controllable appliance to an app resident in smart device <b>100</b>′ as illustrated in example <b>702</b> of <figref idref="DRAWINGS">FIG. 7</figref>, may comprise a brand, type, model number, and serial field <b>604</b>; a command code set identifier <b>606</b> (where this is known, if this is not present the applicable command code set may be inferred from the brand model information <b>604</b> as is known in the art, for example by reference to a database); territory identification <b>608</b> corresponding the geographic area in which this appliance is marketed (when present, this may be used for example to select a language for icon key captions); and in some embodiments, information regarding available appliance input ports <b>610</b>.
0024QR code <b>620</b>, representative of a larger matrix which may be used to transfer an entire equipment configuration between apps resident in smart devices <b>100</b> and <b>100</b>′ as illustrated in example <b>704</b> of <figref idref="DRAWINGS">FIG. 7</figref>, or from a PC based setup program to a smart device, may comprise a list of controllable appliances <b>622</b> which includes type, brand, and codeset identifiers for each appliance; an activity definition field <b>624</b> comprising the identities of the devices which are to participate in various user-defined activity macros; and a favorite channel field <b>626</b> which may comprise a listing of broadcast channel identifiers and corresponding channel numbers.
0025While various concepts have been described in detail, it will be appreciated by those skilled in the art that various modifications and alternatives to those concepts could be developed in light of the overall teachings of the disclosure. For example, in an alternate embodiment, actual photographic images of OEM remote controls may be used in place of the graphic representations depicted herein. In such instances, it will be appreciated that some or all of said photographic images may be captured by a user of the smart device, for example using a built-in camera. In other embodiments, images representative of the appliance themselves may be used in place of OEM remote images when selecting an appliance to be controlled. Furthermore, it will be appreciated that optical transfer of setup and configuration information to and between smart device remote control apps or other controlling devices may be accomplished via any convenient standard or proprietary optical image encoding system, for example without limitation the EIA Data Matrix code, Aztec Code, Siemens Data Matrix, etc.
0026Further, while described in the context of functional modules and illustrated using block diagram format, it is to be understood that, unless otherwise stated to the contrary, one or more of the described functions and/or features may be integrated in a single physical device and/or a software module, or one or more functions and/or features may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary for an enabling understanding of the invention. Rather, the actual implementation of such modules would be well within the routine skill of an engineer, given the disclosure herein of the attributes, functionality, and inter-relationship of the various functional modules in the system. Therefore, a person skilled in the art, applying ordinary skill, will be able to practice the invention set forth in the claims without undue experimentation. It will be additionally appreciated that the particular concepts disclosed are meant to be illustrative only and not limiting as to the scope of the invention which is to be given the full breadth of the appended claims and any equivalents thereof.
0027All patents cited within this document are hereby incorporated by reference in their entirety.
Contents5
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2003169231A1 | Cites | United States of America | Applicant |
| US2003234737A1 | Cites | United States of America | Applicant |
| US2004056789A1 | Cites | United States of America | Applicant |
| US2004257259A1 | Cites | United States of America | Applicant |
| US2006050142A1 | Cites | United States of America | Applicant |
| US2006259864A1 | Cites | United States of America | Applicant |
| WO2007024271A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2007271267A1 | Cites | United States of America | Applicant |
| US2008168367A1 | Cites | United States of America | Applicant |
| US2009239587A1 | Cites | United States of America | Applicant |
| US2009298535A1 | Cites | United States of America | Applicant |
| US2009320070A1 | Cites | United States of America | Applicant |
| US2010017736A1 | Cites | United States of America | Applicant |
| US2010053461A1 | Cites | United States of America | Applicant |
| US2010223553A1 | Cites | United States of America | Search report |
| US2010275135A1 | Cites | United States of America | Applicant |
| US2010332979A1 | Cites | United States of America | Applicant |
| US2011007018A1 | Cites | United States of America | Applicant |
| WO2011008387A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US7627825B2 | Cites | United States of America | Applicant |
| US8640031B2 | Cites | United States of America | Applicant |
| US20030169231A1 | Cites | United States of America | Applicant |
| US20030234737A1 | Cites | United States of America | Applicant |
| US20040056789A1 | Cites | United States of America | Applicant |
| US20040257259A1 | Cites | United States of America | Applicant |
| US20060050142A1 | Cites | United States of America | Applicant |
| US20060259864A1 | Cites | United States of America | Applicant |
| US20070271267A1 | Cites | United States of America | Applicant |
| US20080168367A1 | Cites | United States of America | Applicant |
| US20090239587A1 | Cites | United States of America | Applicant |
| US20090298535A1 | Cites | United States of America | Applicant |
| US20090320070A1 | Cites | United States of America | Applicant |
| US20100017736A1 | Cites | United States of America | Applicant |
| US20100053461A1 | Cites | United States of America | Applicant |
| US20100223553A1 | Cites | United States of America | Search report |
| US20100275135A1 | Cites | United States of America | Applicant |
| US20100332979A1 | Cites | United States of America | Applicant |
| US20110007018A1 | Cites | United States of America | Applicant |
| WO2007024271 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO2011008387 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| European Patent Office, Extended Search Report on PCT/US2011/066371, dated Apr. 3, 2014, 8 pgs. | Non-patent | – | Applicant |
| The Intl. Bureau of WIPO, International Preliminary Report , Written Opinion on Patentability and Search Report issued on PCT/US11/066371, issued Oct. 10, 2013, completed/mailed Jun. 12, 2012, 9 pgs. | Non-patent | – | Applicant |
| European Patent Office, Extended Search Report on PCT/US2011/066371, dated Apr. 3, 2014, 8 pgs. | Non-patent | – | Applicant |
| The Intl. Bureau of WIPO, International Preliminary Report , Written Opinion on Patentability and Search Report issued on PCT/US11/066371, issued Oct. 10, 2013, completed/mailed Jun. 12, 2012, 9 pgs. | Non-patent | – | Applicant |
23 members in 3 offices
Priority claims10
| Document | Office | Kind | Date |
|---|---|---|---|
| 201161442488 | United States of America | P | |
| 201161442488 | United States of America | P | |
| 201113329940 | United States of America | A | |
| 201113329940 | United States of America | A | |
| 201414535984 | United States of America | A | |
| 13329940 | – | – | – |
| 61442488 | – | – | – |
| US201113329940 | – | – | – |
| US201161442488P | – | – | – |
| US201414535984 | – | – | – |
Members23
| Document | Office | Kind | |
|---|---|---|---|
| US2012210268A1 | United States of America | A1 | |
| WO2012112216A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012112216A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP2676436A2 | European Patent Office (EPO) | A2 | |
| EP2676436A4 | European Patent Office (EPO) | A4 | |
| US2014224868A1 | United States of America | A1 | |
| US2014229889A1 | United States of America | A1 | |
| US8918719B2 | United States of America | B2 | |
| US2015066166A1 | United States of America | A1 | |
| US2015067595A1 | United States of America | A1 | |
| US8997002B2 | United States of America | B2 | |
| US2015169201A1 | United States of America | A1 | |
| US9405447B2 | United States of America | B2 | |
| US9720580B2This record | United States of America | B2 | |
| US9804757B2 | United States of America | B2 | |
| US9851879B2 | United States of America | B2 | |
| US2018039396A1 | United States of America | A1 | |
| US2018088780A1 | United States of America | A1 | |
| US2018095642A1 | United States of America | A1 | |
| US10254937B2 | United States of America | B2 | |
| EP2676436B1 | European Patent Office (EPO) | B1 | |
| US2023019304A1 | United States of America | A1 | |
| US2023047899A1 | United States of America | A1 |
66 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Payment of Maintenance Fee, 4th Year, Large EntityM1551 | M1551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Response to 312 Amendment (PTO-271)MN271 | MN271 | |
| Response to Amendment under Rule 312N271 | N271 | |
| Amendment after Notice of Allowance (Rule 312)AllowedA.NA | A.NA | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail PUB other miscellaneous communication to applicantMM327-D | MM327-D | |
| PUB Other miscellaneous communication to applicantM327-D | M327-D | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Terminal Disclaimer FiledDIST | DIST | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Application Is Now CompleteCOMP | COMP | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Application Dispatched from OIPEOIPE | OIPE | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Initial Exam Team nnIEXX | IEXX |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 09720580
- Publication, DOCDB
- 9720580
- Publication, EPODOC
- US9720580
- Application
- 14535984
- Application, DOCDB
- 201414535984
- Application, EPODOC
- US201414535984
Titles
- English
- Graphical user interface and data transfer methods in a controlling device
Patent term adjustment
- A delay
- +329 daysthe office missed an examination deadline
- Applicant delay
- −7 days
- Net adjustment
- 322 days
Classification
- CPC, 15
- G06F3/04842
- H04N21/41265
- G06F3/0484
- G05B15/02
- G06F3/04886
- G06F3/0482
- H04N21/42204
- H04N21/4223
- H04N21/485
- G06F3/0485
- H04N21/8173
- G06F3/04817
- G06F16/00
- G06F17/30
- H04N21/4126
- IPC, 13
- G06F3 00
- G06F3 0484
- G06F3 0488
- H04N21 41
- H04N21 422
- H04N21 4223
- H04N21 485
- H04N21 81
- G06F17 30
- G06F3 0481
- G06F3 0485
- G05B15 02
- G06F3 0482
- USPC, 1
- 001001000