Touchscreen device for controlling a security system
Claim Score by NHIP
Abstract
The present invention is a hand held portable remote such as a key fob that allows a user to interact with the security system using a flat panel touch-pad. The touch-pad input allows a user to rapidly select and control a large number of security functions, such as Arm, Disarm, Panic, garage door open, lamp on/off, and lamp dimming control, etc. The security device comprises a housing, a wireless communication port for interface with the security system, a touch-pad input device, and processing circuitry. In order to operate the security device, the user generates a user input by creating a contact motion on the touch-pad input device with a fingertip. The contact motion may consist of a swiping motion, a tapping, or a circular motion. In order to distinguish the contact motion clearly, when the fingertip contact comprises a wider than normal contact, it causes the processing circuitry to not generate an output signal. The security device also comprises an LCD display for displaying alpha numeric control options to a user and LED indicators for indicating the modes of the processing circuitry.

Term
Term ended
Projected expiry passed 2 June 2026, 0.3 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
20 claims: 2 independent, 18 dependent
- 1Broadest claimClaim Score 73, broad(NHIP)A security device for use with a security system comprising:a. a housing, b. a wireless communication port for interface with said security system, c. a touch-pad input device for inputting a user input from a user and providing a control signal related to said user input, and d. processing circuitry to accept said control signal and generating an output signal to be transmitted by said wireless communication port to said security system.
- 16A method of accepting a user input into a security device and controlling a security system, wherein said security device comprises a wireless communication port, a touch-pad input device and processing circuitry, comprising the steps of:a. inputting a user input into said touch-pad, b. converting said user input into a control signal related to said user input, and c. transmitting an output signal to said security system as a function of said control signal.
Independent claims2
23 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001This invention relates to security systems, and in particular to a control device with a touch-screen or touch-pad that is used to control a security system.
BACKGROUND ART
0002Nearly all security systems of today utilize sophisticated control devices to perform the functions of programming the security system, arming or disarming the security system, providing a panic alert, controlling lighting, and controlling garage doors, etc. Many security systems employ multiple control devices to allow a user more flexibility in controlling the security system. The control devices may be wired or wireless wall-mounted control panels located at different entrances to the protected area or wireless portable handheld devices that can control the security system from outside the protected area.
0003A convenient embodiment of a wireless handheld device is a key fob that is small enough to be placed on a key chain. Key fobs are customarily used for locking and unlocking automobiles. They have room for only a few buttons to allow convenient placement of the device on a key chain which can be held in a pants pocket. The small number of buttons is a problem for security system control devices because it limits the amount of controllable functions the device can perform. It is therefore desirable for a homeowner to have a control device that performs the multiple function of a wall mounted control panel while having the size and convenience of a key fob.
0004An additional concern of a wireless handheld device is that the buttons on the device are subject to inadvertent activation when something rubs against the device. When a key fob is placed in a pants pocket, the buttons may be depressed when the person bends or sits down or the buttons come in contact with keys or coins. This may cause the security system to be put in an undesirable mode. For proper operation of the security system, the key fob must be designed to safeguard against this problem.
0005It is therefore an object of the present invention to provide a small portable handheld control device that can control the many functions of a security system.
0006It is a further object of the present invention to provide a method for quickly selecting and controlling the many functions of a security system.
0007It is a further object of the present invention to provide a control device that is not inadvertently activated by contact with keys, clothing, coins, etc.
0008Finally, it is a further object of the present invention to provide a display to the user to inform the user of the security devices transmissions and operations.
DISCLOSURE OF THE INVENTION
0009The present invention is a touch-screen security device that is able to remotely control functions of a security system. The security device is generally a hand held portable remote device such as a key fob that allows a user to interact with the security system using a flat panel touch-pad input instead of push buttons. The touch-pad input allows a user to rapidly select and control many security and house-control functions, such as Arm, Disarm, Panic, garage door open, lamp on/off, and lamp dimming control, etc. The security system procedures for performing these and other functions are well known to one skilled in the art and will not be described.
0010The security device comprises a housing, a wireless communication port for interfacing with the security system, a touch-pad input device, and processing circuitry. The touch-pad input device allows a user to provide user inputs, as described below, and provides a control signal to the processing circuitry that is related to the selected user input. The processing circuitry accepts the control signal and generates output signals based on it. The processing circuitry generates output signals that control the security device, as described below, and output signals that are transmitted to the security system via an antenna.
0011In order to operate the security device, the user generates a user input by creating a contact motion on the touch-pad input device with a fingertip. The contact motion may be for example a tapping motion, a clockwise circular motion, a counterclockwise circular motion, a swiping motion from top to bottom, a swiping motion from bottom to top, a swiping motion from left to right, or a swiping motion from right to left of the touch pad. In order to distinguish the contact motion clearly, when the fingertip contact comprises a wider than normal contact, it causes the processing circuitry to not generate an output signal.
0012The security device also comprises a display such as an LCD display for displaying alpha numeric control options to be selected by a user and LED indicators for indicating the modes of the processing circuitry. In an alternative embodiment the LCD display may contain graphics that indicate the modes of the processing circuitry. The user views the control options displayed on the LCD and uses the contact motions on the touch-pad as described above to either (1) select the current control option displayed, (2) scroll to a different control option, or (3) go into a programming mode. In order to perform these operations, the security device processing circuitry uses a micro-computer to input the control signals from the touch-pad device and, depending on the control signal, the micro-computer outputs signals to the LCD display, the LED indicators, and/or the RF transmitter. In order to provide flexibility to the user, the control options are programmed into the security device by an installer (or the user) when the security device is put into the programming mode.
0013The present invention is also a method of accepting a user input into the security device described above and controlling a security system comprising the steps of inputting a user input into a touch-pad, converting the user input into a control signal related to the user input, and transmitting an output signal to the security system as a function of the control signal. The user input is the same contact motions described above. The present invention also comprises the steps of displaying a control option to be selected by the user and programming the control option into the security device by the user.
0014The method of operation of the present invention is as follows. The user views the control option on the security device display and performs a contact motion on the touch-pad. The touch-pad provides a control signal to the processing circuitry that corresponds to the contact motion, and the processing circuitry determines the processing state based on the control signal. If the processing state is a first level processing state, then the processing circuitry transmits to the security system an output signal which is a function of the control signal. An example of a first level processing state would be an execute input which may be a left to right finger swipe contact motion. This indicates acceptance of the currently displayed control option. A first level processing state requires no further input from the user. If the processing state is a second level processing state, then the processing circuitry revises the control option displayed to the user, accepts a subsequent user input into the touch-pad, and converts the subsequent user input into a control signal related to the subsequent user input. These steps may be repeated. An example of a second level processing state would be a mode select input which may be a right to left finger swipe contact motion. A second level processing state requires an additional input from the user. The present invention also comprises the step of indicating the mode of the processing circuitry by illuminating LEDs, which helps the user to know if the security device is executing a command or waiting for an input. In an alternative embodiment, the step of indicating the mode of the processing circuitry is performed by the LCD display which contains graphics that indicate the modes of the processing circuitry.
BRIEF DESCRIPTION OF THE DRAWING
0015<figref idref="DRAWINGS">FIG. 1</figref> is a diagram of the security device of the present invention.
0016<figref idref="DRAWINGS">FIG. 2</figref> is a circuit diagram of the present invention.
0017<figref idref="DRAWINGS">FIG. 3</figref> is a mode of operation flowchart of the present invention.
BEST MODE FOR CARRYING OUT THE INVENTION
0018The preferred embodiments of the present invention will now be described with respect to the Figures. <figref idref="DRAWINGS">FIG. 1</figref> illustrates the security device <b>5</b> as a key fob. Shown are front and side views of the key fob housing <b>10</b>. The key fob housing <b>10</b> has an antenna <b>50</b> and a keychain loop <b>100</b> attached to it. The antenna <b>50</b> provides a large transmission range, while the keychain loop <b>100</b> allows the security device <b>5</b> to be easily attached to a keychain. The antenna <b>50</b> may be extendable, fully retractable, or built-in (totally internal). The key fob housing <b>10</b> contains a recessed power on button <b>40</b>, an LCD display <b>20</b>, a touch pad <b>30</b>, and four LEDs <b>60</b>, <b>70</b>, <b>80</b>, and <b>90</b>. The power button is pushed to turn the security device <b>5</b> on. If it is turned on accidentally, it will turn itself off after a short time of inactivity because it will interpret inactivity as no valid user input on the touch pad <b>30</b>. Once the security device <b>5</b> is turned on, the LCD display <b>20</b> will be lit by the backlight LED <b>110</b> and a control option will be displayed. The LCD display <b>20</b> presently shows the control option “14. PORCH LIGHT”. A predefined number of control options will be available in a list form, and the user will either select the currently displayed control option or scroll through the list until a desired control option is displayed (only one control option is displayed for selection at a given time). In the example given, the number “14” is the object number of the control option. Once the user reads the current control option, he uses the touch-pad <b>30</b> to select that control option or to scroll to a different control option. The touch-pad senses a tapping or swiping motion from the users finger tip. If the contact is larger than a finger tip then the security device <b>5</b> ignores the input. For example, if the touch-pad <b>30</b> is pressed against the user's leg the security device <b>5</b> will ignore the input. This is to safeguard against inadvertent selections. The LEDs <b>60</b>, <b>70</b>, <b>80</b>, and <b>90</b> provide feedback to the user as to what action the security device <b>5</b> is performing. The SELECT LED <b>70</b> is lit when the user needs to select a control option. The EXECUTE LED <b>80</b> is lit when a command has been executed. The CHOOSE LED <b>60</b> is lit when the security device's <b>5</b> mode is being selected, and the PROG LED <b>90</b> is lit when the security device <b>5</b> is in a program mode.
0019<figref idref="DRAWINGS">FIG. 2</figref> shows a circuit diagram of the security device <b>5</b>. The security device's <b>5</b> processor is a single chip microcomputer <b>150</b> with a clock input from crystal <b>170</b>. The microcomputer <b>150</b> is normally in a sleep mode or hibernation state, drawing very little battery power from the battery <b>160</b>. When the power on button <b>40</b> is pushed, the microcomputer <b>150</b> wakes up and places a message on the LCD display <b>20</b>. The microcomputer <b>150</b> contains a built in LCD driver that directly controls the LCD display <b>20</b>. The microcomputer <b>150</b> also sends output signals to the LED driver <b>120</b> that cause the LEDs <b>60</b>, <b>70</b>, <b>80</b>, and <b>90</b> to be illuminated when the microcomputer <b>150</b> is performing the functions described above. An additional LED driver <b>130</b> controls the backlight LED <b>110</b> that lights the LCD display <b>20</b> when a control option is displayed to allow the user to see it. The microcomputer <b>150</b> communicates with the security system via RF transmitter <b>140</b>. The RF transmitter <b>140</b> accepts message data from the microcomputer <b>150</b> and when commanded by the microcomputer <b>150</b> converts the data to an RF message and transmits it to the security system through antenna <b>50</b>. The message structure and the transmit protocols are compatible with home security control panels as known in the art. The signals transmitted may also be compatible with receiver devices that are interface with X-10 type Line Voltage control modules or equivalent AC power control devices or wireless control units, all as well known in the art.
0020The touch-pad <b>30</b> is a key feature in the design of the security device <b>5</b>. It provides quick access to all of the security system functions, thus allowing the key fob <b>10</b> to operate like a sophisticated control device. In the preferred embodiment, The touch-pad <b>30</b> and its PSoC (programmable systems-on-chips) controller <b>180</b> are manufactured by Cypress Semiconductor Corporation. The PSoC controller <b>180</b> is programmed to read and process inputs from the touch-pad <b>30</b> by Cypress and generally works as follows. The touch-pad <b>30</b> has an underlying grid work of conductors and the PSoC controller <b>180</b> capacitively senses the presence of a finger on the touch pad <b>30</b> by generating a series of pulses on one part of the touch-pad <b>30</b> gridwork and measures the return signal to another part of the gridwork. It isolates the physical location of where the user's fingertip touched the touch-pad <b>30</b> by determining the location of the capacitance change. The location information is then processed by the PSoC controller <b>180</b> to provide output signals to the micro-computer <b>150</b> that are correlated to the location of the fingertip touch. The PSoC controller <b>180</b> also provides signals that are correlated to the direction of the movement of the fingertip touch. The microcomputer <b>150</b> decodes the signals from the PSoC controller <b>180</b> to determine which finger stroke, or user input, was performed. Thus, the microcomputer can determine, based on inputs from the PSoC controller, if the user performed a single tap, a left to right stroke, a circular stroke, etc.
0021<figref idref="DRAWINGS">FIG. 3</figref> shows a top level flow diagram of the microcomputer <b>150</b> operation. When the power button <b>40</b> is depressed the Select LED <b>70</b> is lit and a control option is displayed on the LCD. The microcomputer <b>150</b> waits for a user input to the touch-pad <b>30</b>. If no input is received after an amount of time, the microcomputer <b>150</b> goes into a sleep mode until the power button <b>40</b> is depressed again. If the touch-pad <b>30</b> input is a down finger stroke, the microcomputer <b>150</b> displays the next control option on the LCD <b>20</b> and waits for another touch-pad <b>30</b> input. If the touch-pad <b>30</b> input is an up finger stroke, then the previous control option is displayed on the LCD <b>20</b>. The list of control options may have any number of entries, and the list scrolls and then wraps around from the last to the first and/or from the first to the last. If the touch-pad <b>30</b> input is a left to right finger stroke, this indicates acceptance of the current control option and the microcomputer <b>150</b> executes the control option that is displayed on the LCD <b>20</b>. The microcomputer <b>150</b> performs this command by composing a message consisting of the object number of the control option, the serial number of the keypad of the security system and other housekeeping data. The microcomputer <b>150</b> then sends the message to the RF transmitter <b>140</b> and commands the transmitter <b>140</b> to transmit the message to the security system. Finally the Execute LED <b>80</b> is flashed on and the microprocessor <b>150</b> waits a timeout period and then goes to sleep.
0022If the touch-pad <b>30</b> input is a right to left finger stroke, then the microcomputer <b>150</b> lights the Choose LED <b>60</b> and goes into the choose mode. If the next touch-pad <b>30</b> input is a down finger stroke then the microcomputer <b>150</b> goes into the program mode. This two step process is used to prevent the user from inadvertently programming spurious data into the security device <b>5</b>. The Program LED <b>90</b> is lit and the microcomputer <b>150</b> performs the program routine. The programming mode may be used for initial installation of the security device <b>5</b> or reprogramming of the security device <b>5</b>. When the security device <b>5</b> is initially manufactured it does not have the various control options programmed into it. The user (or installer) enters the programming mode to program each object number (0-31) with a control option (arm, disarm, lamp on/off, etc.) that describe each security system function. During this procedure, the user is prompted with messages on the LCD <b>20</b> to guide the user to select the object number, the type of object, and the alphanumeric descriptor that describes the object (the control option). Also during the installation process, the security system's alarm panel is programmed to accept data from the security device <b>5</b> by recognizing a unique serial number associated with the security device <b>5</b> (programmed during manufacture) that is sent as part of the transmitted message. The object numbers programmed to be associated with a particular object by the user or installer in the security device <b>5</b> must also be programmed into the security system's alarm panel to correspond to the appropriate security system function.
0023It will be apparent to those skilled in the art that modifications to the specific embodiment described herein may be made while still being within the spirit and scope of the present invention. For example, programming of the security device <b>5</b> may also be accomplished by coupling the security device <b>5</b> to a laptop computer to have all of the control data and nomenclature downloaded from a computer program directly to the security device <b>5</b>. Lastly, an alternative embodiment of fitting the security device <b>5</b> with a “Bluetooth” interface (a wireless interface protocol) to allow long distance control of a security system using a cell phone may be implemented. In this application, the Bluetooth interface is a communication channel used by the security device <b>5</b> to request a cell phone carried by the user to transmit a message to the home security system as well known in the art.
Contents5
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2018198788A1 | Cited by | United States of America | Search report |
| US11750414B2 | Cited by | United States of America | Applicant |
| US11824675B2 | Cited by | United States of America | Applicant |
| US10747216B2 | Cited by | United States of America | Applicant |
| US10523689B2 | Cited by | United States of America | Applicant |
| US11582065B2 | Cited by | United States of America | Applicant |
| US11341840B2 | Cited by | United States of America | Applicant |
| US11625161B2 | Cited by | United States of America | Applicant |
| US11641391B2 | Cited by | United States of America | Applicant |
| US11398147B2 | Cited by | United States of America | Applicant |
| US2016274759A1 | Cited by | United States of America | Applicant |
| US10666523B2 | Cited by | United States of America | Applicant |
| US11082395B2 | Cited by | United States of America | Applicant |
| US10616075B2 | Cited by | United States of America | Search report |
| US11418572B2 | Cited by | United States of America | Applicant |
| US11611568B2 | Cited by | United States of America | Applicant |
| US10382452B1 | Cited by | United States of America | Applicant |
| US10692356B2 | Cited by | United States of America | Applicant |
| US11223998B2 | Cited by | United States of America | Applicant |
| US10142394B2 | Cited by | United States of America | Applicant |
| US10078958B2 | Cited by | United States of America | Applicant |
| US10389736B2 | Cited by | United States of America | Applicant |
| US11792036B2 | Cited by | United States of America | Applicant |
| US11316753B2 | Cited by | United States of America | Applicant |
| US10522026B2 | Cited by | United States of America | Applicant |
| US10223903B2 | Cited by | United States of America | Applicant |
| US11537186B2 | Cited by | United States of America | Applicant |
| US10225314B2 | Cited by | United States of America | Applicant |
| US2018198788A1 | Cited by | United States of America | Search report |
| US11894986B2 | Cited by | United States of America | Applicant |
| US11809174B2 | Cited by | United States of America | Applicant |
| US10721087B2 | Cited by | United States of America | Applicant |
| US11424980B2 | Cited by | United States of America | Applicant |
| US10079839B1 | Cited by | United States of America | Applicant |
| US10332363B2 | Cited by | United States of America | Applicant |
| US11551263B2 | Cited by | United States of America | Applicant |
| US10992784B2 | Cited by | United States of America | Applicant |
| US10051078B2 | Cited by | United States of America | Applicant |
| US2011316786A1 | Cited by | United States of America | Pre-grant |
| US2015312991A1 | Cited by | United States of America | Pre-grant |
| US11601810B2 | Cited by | United States of America | Applicant |
| US11792330B2 | Cited by | United States of America | Applicant |
| US11201755B2 | Cited by | United States of America | Applicant |
| US10382452B1 | Cited by | United States of America | Applicant |
| US10498830B2 | Cited by | United States of America | Applicant |
| US10142392B2 | Cited by | United States of America | Applicant |
| US11175793B2 | Cited by | United States of America | Applicant |
| US11665617B2 | Cited by | United States of America | Applicant |
| US11153266B2 | Cited by | United States of America | Applicant |
| US8830173B2 | Cited by | United States of America | Search report |
| US11810445B2 | Cited by | United States of America | Applicant |
| US10447491B2 | Cited by | United States of America | Applicant |
| US10142166B2 | Cited by | United States of America | Applicant |
| US11616659B2 | Cited by | United States of America | Applicant |
| US10841381B2 | Cited by | United States of America | Applicant |
| US11412027B2 | Cited by | United States of America | Applicant |
| US11706045B2 | Cited by | United States of America | Applicant |
| US10200504B2 | Cited by | United States of America | Applicant |
| US10365810B2 | Cited by | United States of America | Applicant |
| US11296950B2 | Cited by | United States of America | Applicant |
| US10140840B2 | Cited by | United States of America | Applicant |
| US2011134517A1 | Cited by | United States of America | Pre-grant |
| US11237714B2 | Cited by | United States of America | Applicant |
| US10444964B2 | Cited by | United States of America | Applicant |
| US11258625B2 | Cited by | United States of America | Applicant |
| US10559193B2 | Cited by | United States of America | Applicant |
| US10530839B2 | Cited by | United States of America | Applicant |
| US10813034B2 | Cited by | United States of America | Applicant |
| US12063220B2 | Cited by | United States of America | Applicant |
| US11316958B2 | Cited by | United States of America | Applicant |
| US10313303B2 | Cited by | United States of America | Applicant |
| US10896442B2 | Cited by | United States of America | Applicant |
| US10754304B2 | Cited by | United States of America | Applicant |
| US10510097B2 | Cited by | United States of America | Applicant |
| US10735249B2 | Cited by | United States of America | Applicant |
| US11378922B2 | Cited by | United States of America | Applicant |
| US10380871B2 | Cited by | United States of America | Applicant |
| US9351377B2 | Cited by | United States of America | Search report |
| US11489812B2 | Cited by | United States of America | Applicant |
| US11962672B2 | Cited by | United States of America | Applicant |
| US11277465B2 | Cited by | United States of America | Applicant |
| US11656667B2 | Cited by | United States of America | Applicant |
| US11184322B2 | Cited by | United States of America | Applicant |
| US10672254B2 | Cited by | United States of America | Applicant |
| US11113950B2 | Cited by | United States of America | Applicant |
| US10930136B2 | Cited by | United States of America | Applicant |
| US10127802B2 | Cited by | United States of America | Applicant |
| US11418518B2 | Cited by | United States of America | Applicant |
| US11367340B2 | Cited by | United States of America | Applicant |
| US11356926B2 | Cited by | United States of America | Applicant |
| US11423756B2 | Cited by | United States of America | Applicant |
| US11240059B2 | Cited by | United States of America | Applicant |
| US10339791B2 | Cited by | United States of America | Applicant |
| US11129084B2 | Cited by | United States of America | Applicant |
| US10741057B2 | Cited by | United States of America | Applicant |
| US11410531B2 | Cited by | United States of America | Applicant |
| US10616244B2 | Cited by | United States of America | Applicant |
| US10999254B2 | Cited by | United States of America | Applicant |
| US10890881B2 | Cited by | United States of America | Applicant |
| US12277853B2 | Cited by | United States of America | Applicant |
4 members in 2 offices; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 27008205 | United States of America | A | |
| US20050270082 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2007103433A1 | United States of America | A1 | |
| WO2007055907A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2007055907A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US7362221B2 | United States of America | B2 |
34 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, 12th Year, Large EntityM1553 | M1553 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Oath or Declaration Filed (Including Supplemental)C602 | C602 | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 20070103433
- Publication, DOCDB
- 2007103433
- Publication, EPODOC
- US2007103433
- Application
- 11270082
- Application, DOCDB
- 27008205
- Application, EPODOC
- US20050270082
Titles
- English
- Touchscreen device for controlling a security system
Patent term adjustment
- A delay
- +205 daysthe office missed an examination deadline
- Net adjustment
- 205 days
Classification
- CPC, 2
- G08B25/016
- G08B25/008
- IPC, 3
- G09G5 00
- G06F13 42
- G08B23 00
- USPC, 3
- 345156000
- 340005800
- 340500000