EP3279882A1 - Module d'actionnement de bouton de commande à distance, système et procédé de références croisées pour des applications connexes - Google Patents

Module d'actionnement de bouton de commande à distance, système et procédé de références croisées pour des applications connexes Download PDF

Info

Publication number
EP3279882A1
EP3279882A1 EP17183600.0A EP17183600A EP3279882A1 EP 3279882 A1 EP3279882 A1 EP 3279882A1 EP 17183600 A EP17183600 A EP 17183600A EP 3279882 A1 EP3279882 A1 EP 3279882A1
Authority
EP
European Patent Office
Prior art keywords
remote control
button
actuation system
controller
actuation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP17183600.0A
Other languages
German (de)
English (en)
Other versions
EP3279882B1 (fr
Inventor
Craig Arnold Tieman
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tieman Vehicle Technologies LLC
Original Assignee
Tieman Vehicle Technologies LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US15/228,166 external-priority patent/US9576414B2/en
Application filed by Tieman Vehicle Technologies LLC filed Critical Tieman Vehicle Technologies LLC
Publication of EP3279882A1 publication Critical patent/EP3279882A1/fr
Application granted granted Critical
Publication of EP3279882B1 publication Critical patent/EP3279882B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
    • G08C17/00—Arrangements for transmitting signals characterised by the use of a wireless electrical link
    • G08C17/02—Arrangements for transmitting signals characterised by the use of a wireless electrical link using a radio link

Definitions

  • Electronic systems in automotive vehicles and other devices may utilize handheld remote controls with finger-pressable buttons. These devices can be utilized to remotely actuate vehicle or device functions by hand, where such functions may be difficult to access otherwise by a vehicle operator.
  • the remote controls of these electronic systems generally permit secure remote actuation of unlocking, locking, power door and trunk opening, remote engine starting, activation of horns, lights and panic features as well as other types of vehicle or device functions.
  • Directed Electronics offers aftermarket systems that control more functions and provide longer-range of connectivity, including the addition of telematics communications for control from any location with a smartphone application.
  • One primary limitation of these systems includes the need for extensive custom engineering efforts to enable the electronics to interface to and work with the electronics of the vehicles.
  • consumers may be required to employ a professional technician for all installation efforts due to the technical complexity of the different vehicle installations. Consequently, these installations are generally expensive for consumers to consider.
  • the main limitation of a data bus control technique is the extensive effort to reverse-engineer data bus commands for each vehicle. Additionally, many vehicles cannot be controlled via this connector at some or all of the time, such as when an owner is away from their vehicle due and/or due to a lack of available data bus commands.
  • a remote control button actuation system that includes a button actuator tip mounted configurable to actuate the buttons on a remote control for vehicle or device.
  • the button actuator tip can be moved to any position over the surface of the remote control by actuating first and second servo motors operably linked to the boom to control boom rotation angle and boom extension distance.
  • first and second servo motors operably linked to the boom to control boom rotation angle and boom extension distance.
  • the button actuator tip operably linked to a third servo motor, may be lowered to press a remote control button.
  • the servo motors may be controlled by a programmable controller that receives signals from either a mobile device via short or medium-range wireless signals or from a separate telematics gateway device which extends the range of control to the mobile device.
  • the various embodiments of the controller may include configurable nonvolatile memory that can provide storage of data, such as data representative of the proper servo positions for all buttons on an installed vehicle or device remote control.
  • the data may be loaded into the memory of the controller at manufacture, programmed after sale by using a one-time calibration process performed by a user, selectable or generated upon the entrance of a code, down loadable, etc.
  • the system may be powered by an internal power supply using either internal or external batteries, or may be powered by interfacing to another power source such as a 12-volt source available in the vehicle.
  • the machine and/or controller may be operated by remote control and thus this disclosure includes a method to calibrate and operate the remote control machine and controller by RF means or any form of wireless transmission including but not limited to the unlicensed spectrum, BLUETOOTH, WIFI, etc.
  • Another embodiment includes a method of remotely actuating the buttons of a remote control by mounting a remote control with actuatable buttons in proximity to a machine to actuate buttons of the remote control.
  • An exemplary machine may include a rotatable pivot secured to a base and a boom comprising a first end and second end. The boom is mounted, e.g., rotatably mounted on the rotatable pivot at the first end and reversibly extendable from the pivot. An actuator is fixedly mounted on the second end. The pivot, the boom and the actuator are configurable to raise and lower a tip to actuate the buttons of the remote control.
  • Another embodiment includes a computer program product that includes a computer readable medium having computer readable code embodied therein.
  • the computer readable program code is adapted to be executed by a processor to implement a method of remotely actuating the buttons of a remote control.
  • the computer readable code causes the computer and/or devices interfaced thereto to actuate buttons, switches or actuators of a remote control mounted to a holder and proximate to a actuation machine.
  • the machine in another contemplated embodiment, includes a rotatable pivot secured to a base and a boom comprising a first end and second end.
  • the boom is rotatably mounted on the rotatable pivot at the first end and reversibly extendable from the pivot.
  • An actuator is fixedly mounted on the second end, and wherein the pivot, the boom and the actuator are configurable to raise and lower a tip to engage the buttons of the remote control.
  • an exemplary machine may include a boom mounted on a rotatable pivot, which rotatable pivot is secured to a base, and a button actuator assembly slidable along the boom.
  • the pivot, the boom and the button actuator assembly are configurable to raise and lower a tip to actuate the buttons of the remote control.
  • the actuation system includes an isolation enclosure that is designed to prevent radio frequency (RF) signals from entering into or leaving an open interior of the isolation enclosure.
  • the isolation enclosure is preferably formed from a metallic material to prevent the transmission of the RF signals.
  • the isolation enclosure completely surrounds a key fob that is located on a remote control support within the open interior of the isolation enclosure. The remote control support securely receives and retains the key fob in a known location within the open interior.
  • a controller also located within the open interior, is configured to receive command signals from a mobile device. Based upon the command signals received from the mobile device, the controller converts the command signals into position commands used to move the button actuator. Since the controller is positioned within the isolation enclosure, the controller is coupled to a receiving antenna that is generally aligned with a first opening in the isolation enclosure to receive the wireless command signals from the mobile device. The controller is in further communication with a transmitting antenna, which is also aligned with the same opening or another opening in the isolation enclosure. The transmitting antenna is able to transmit vehicle command signals out of the isolation enclosure for receipt by the operating systems within the vehicle.
  • a key fob antenna is positioned within the isolation enclosure to receive the control signals from the key fob and communicate these signals to the controller. Based upon the received signals from the key fob, the controller retransmits the control signals received from the key fob as the vehicle command signals. In this manner, the actuation system is able to isolate the key fob and controller from outside RF signals while still allowing the key fob and controller to transmit vehicle command signals to the vehicle.
  • the button actuator includes three separate servo motors that are each operable to move the plunger in one of three transverse directions.
  • the three servo motors are independently operable by the controller and are each used to move the plunger in one of the three transverse directions.
  • a force translating device is positioned within the open interior of the isolation enclosure.
  • the force translating device is able to convert the movement of the plunger in a third direction into movement in a direction that is either transverse to the third direction or opposite to the third direction. In this manner, the force translating device is able to depress a button on either a side surface of the key fob or on a back surface of the key fob.
  • content may also include files having executable content, such as: object code, scripts, byte code, markup language files, and patches.
  • content as referred to herein, may also include files that are not executable in nature, such as documents that may need to be opened or other data files that need to be accessed.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computing device and the computing device may be a component.
  • One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between two or more computers.
  • these components may execute from various computer readable media having various data structures stored thereon.
  • the components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal).
  • wireless device wireless telephone
  • wireless communication device wireless handset
  • 3G third generation
  • 4G fourth generation
  • a “processing component” or “thermal energy generating component” may be, but is not limited to, a central processing unit, a graphical processing unit, a core, a main core, a sub-core, a processing area, a hardware engine, etc. or any component residing within, or external to, an integrated circuit within a portable computing device.
  • FIG. 1 shows a mechanization diagram of the remote control button actuation system in accordance with the description.
  • the controlling system 100 may be a wireless mobile device, which operates to send user commands via wireless RF or other wireless technology, including optical and audible technology, directly to the controller and power supply 8. It will be appreciated that throughout this description, the term RF or RF wireless are used but, in all such instances unless specifically mentioned otherwise, any wireless or wired technology could also be utilized in such situations.
  • the controlling system 100 may be a gateway device located within the vehicle or nearby the device under control and, which connects wirelessly via RF or via wires to the controller and power supply 8. The controller and power supply 8 receives an actuation command from the controlling system 100.
  • the actuation command may include a variety of information and one such example is to include the identity of a particular remote control button that is to be actuated and a specific duration of time to actuate the button.
  • the commands may include a variety of other information such as, time of day to actuate the button, a sequence of buttons to be actuated, a request for multiple presses of a single button, etc.
  • the controller and power supply 8 converts these commands into specific servo motor commands that cause the provision of actuating power to the 3-axis button actuation system 51, which presses the selected remote control 101 button for the required duration and then releases the button, or otherwise performs the requested command.
  • the pivot arm may include multiple tips and a further servo could be used to control the relative location of the multiple tips. For instance, if a certain function requires two buttons to be pressed simultaneously, the server could operate to position the tips relative to each other at a certain distance to ensure actuation of both buttons. When only a single button needs to be actuated, the servo can move the additional tip out of the way or, bring all the tips in to close proximity such that they operate as a single tip.
  • FIG. 2 is a right-side isometric view of an exemplary 3-axis button actuation system 51.
  • a button actuator tip 1 is attached to a z-axis rack gear 2, which is held in position by a motor support bracket 28 and attached to a sliding boom 4. The tip 1 can be moved vertically when the z-axis pinion gear 3 rotates.
  • Z-axis pinion gear 3 is attached to one end of a z-axis driveshaft 5, which extends longitudinally through the entire length of sliding boom 4.
  • Sliding boom 4 is held by boom support 10, which enables the sliding boom to move horizontally to reposition button actuator tip 1.
  • Boom support 10 rotates about the vertical axis on boom support pivot pin 47, which is attached to the mounting enclosure 50 shown in FIG. 5 .
  • Angle-axis driven gear 6 is also mounted to the boom support pivot pin 47 and the enclosure 50.
  • Angle-axis servo motor 9 is attached to boom support 10 and rotates angle-axis drive gear 7, which is engaged with angle-axis driven
  • Remote control clamp pad 30 is mounted on clamp pad pivot pin 31, which is attached to one end of clamp pad support 38.
  • Clamp pad 36 and clamp pad pivot 37 are mounted to the opposite end of clamp pad support 38.
  • Clamp pad support 38 is mounted to clamp pad support pivot pin 40, which rotates on spring bracket 42.
  • Clamp pad 32 is mounted on clamp pad pivot pin 33 and which is attached to one end of clamp pad support 39.
  • Clamp pad 34 and clamp pad pivot 35 are mounted to the opposite end of clamp pad support 39.
  • Clamp pad support 39 is mounted to clamp pad support pivot pin 41, which rotates on spring bracket 43.
  • Clamp pad tension spring 44 mounts to one end of spring bracket 42 and spring bracket 43.
  • Clamp pad tension spring 45 mounts to the opposite ends of spring bracket 42 and spring bracket 43.
  • Clamp pad tension release control arm and cam 46 is mounted to the enclosure 50 and rotates about the vertical axis to rotate the cam against the spring brackets 42 and 43.
  • the clamp pad support pivot pins 40 and 41 move in the clamp pad support slide holes 57 and 58 of FIG. 5a in the enclosure 50.
  • FIG. 3a is a left-side isometric view of the 3-axis button actuation system 51 constructed in accordance with one embodiment.
  • Z-axis driven gear 24 is attached to the opposite end of z-axis driveshaft 5 from the z-axis pinion gear 3.
  • Z-axis servo motor 22 rotates z-axis drive gear 23 which is engaged with z-axis driven gear 24.
  • R-axis rack gear 25 is attached longitudinally to the top of boom support 10.
  • R-axis pinion gear 26 engages with r-axis rack gear 25 and is rotated by r-axis servo motor 20.
  • FIG. 3b is a left-side view of FIG. 3a with z-axis servomotor 22 and z-axis drive gear 23 removed.
  • Sliding boom anti-rotation pin 29 is attached to boom support 10 and slides in a slot in motor support bracket 28 to prevent rotation of sliding boom 4 when it is moving longitudinally within the boom support 10.
  • FIG. 4 is a bottom-side isometric view of the 3-axis button actuation system 51 constructed in accordance with one embodiment.
  • FIG. 5 is a top-side isometric view of the controller and power supply 8 and 3-axis button actuation system 51 mounted with the housing 50 and constructed in accordance with one embodiment.
  • Remote control 101 is shown mounted within the 3-axis button actuation system 51 and held firmly in place by clamp pads 30, 32, 34 and 36 by clamp pad tension springs 44 and 45.
  • Calibration guide alignment pins 52, 53, 54 and 55 are shown protruding from the inside bottom surface of housing 50.
  • FIG. 6 shows transparent calibration guide 56 used in one embodiment.
  • FIG. 7 shows calibration guide 56 mounted on calibration guide alignment pins 52, 53, 54 and 55 using holes at each corner of calibration guide 56.
  • the installed remote control 101 is located just below the calibration guide 56.
  • FIG. 8 is a flowchart describing the calibration process for the 3-axis button actuation system 51 according to one embodiment.
  • FIG. 9 is a flowchart describing the operation process for the 3-axis button actuation system 51 according to one embodiment.
  • servo gears, pinions and racks could be replaced with link arms and linkages to transfer rotational forces and cause rotational and linear motions of the 3-axis button actuation system 51.
  • the z-axis servo and gears could be replaced by a two-position solenoid to move the button actuator tip 1 vertically.
  • the fixed-length sliding boom 4 and z-axis driveshaft 5 could be replaced by telescoping elements as a means to conserve enclosure 50 space.
  • An alternative method of moving the button actuation tip 1 over the remote control 101 button area could be constructed using x-axis and y-axis servo motors with an x-y sliding table.
  • FIG. 13 , FIG. 14 , FIG. 15 , FIG. 16 and FIG. 17 show an alternative embodiment, i.e., machine 400 comprising boom 402 that is mounted to fixed shaft 408 proximate to pivot end 404.
  • Fixed shaft 408, fixedly mounted on box 600 passes through an opening (not shown) in boom 402.
  • One or more bushings (not shown) positioned between boom 402 and fixed shaft 408 allow the boom to rotate about fixed shaft 408 such that boom distant end 406 moves along arcuate path 412.
  • Servo motor 414 is linked to drive gear 416A that engages pivot gear 416B to move boom 402 about axis 410.
  • Button actuator 418 is slidable along boom 402.
  • Lever 422 is mechanically coupled to the actuator by arm 424.
  • Remote control 500 is held proximate to machine 400 by pads 432, 434, 438, and 440.
  • Pads 432 and 434 are resiliently biased against remote control 400 by member 436.
  • Pads 438 and 440 are resilient biased against an opposite side of remote control 500 by member 444.
  • Members 442 and 444 are anchored to box 600, e.g., to walls 602 and 604, respectively.
  • the remote control button actuator system utilizes a 3-axis servo-controlled actuator to permit universal remote control actuation with a plurality of buttons to be actuated.
  • the embodiments present the use of a spring-loaded, adjustable remote control holder so as to facilitate the adjustment of any type of remote control.
  • the remote control actuation system alleviates, and in some instances, eliminates the problem encountered by other systems which attempt to take control of devices (e.g. automotive keyless entry) via hard-wired or RF methods and which require extensive reverse engineering on a vehicle-by-vehicle basis or sacrificing of expensive remote controls which are used for code harvesting.
  • the described embodiments of the actuation system do not require the use of dedicated solenoids for each remote button on the remote controller. Further, the various embodiments do not require special brackets or tooling to hold different types of remotes.
  • a user connects the controlling system 100 to the controller and power supply 8 either using a wireless RF or wired connection.
  • Software applications running within the user's mobile device and controlling system 100 operate to provide remote control of the controller and power supply 8.
  • the first-time setup process would involve preparing the controller and power supply 8 and 3-axis button actuation system 51 for remote control 101 installation by the user.
  • the button actuator tip 1 would be retracted and moved out of the way to permit remote control 101 installation.
  • the user would move the clamp pad tension release control arm and cam 46, causing the cam to act against the spring brackets 42 and 43 to move the clamp pads 30, 32, 34 and 36 outward.
  • the remote control 101 can then be placed between the clamp pads and the clamp pad tension release control arm and cam 46 would be moved back to place the remote control 101 under tension from clamp pad tension springs 44 and 45.
  • specific holders that are designed to receive specific remote control models may be utilized rather than the clamp.
  • the system may include an interface for receiving one of a plurality of specific holders such that a specific holder can be installed for a specific application.
  • the transparent calibration guide 56 would be placed and aligned over the calibration guide alignment pins 52, 53, 54 and 55. The user would make a mark with a fine-tipped marker on the calibration guide over the center of every remote control 101 button. The calibration guide would be removed and the numbered intersecting lines closest to each mark identified for the angle-axis and r-axis settings for each button.
  • FIG. 8 shows the calibration procedure 200 which would be performed by the user in conjunction with a software application running on a mobile device, beginning with step 201.
  • Step 202 initiates a button counter for the first button.
  • Step 203 uses the angle-axis calibration value from the calibration guide 56 for the current button to drive the angle-axis servomotor 9 to that value.
  • Step 204 uses the r-axis calibration value from the calibration guide 56 for the current button to drive the r-axis servo motor 20 to that value.
  • Step 205 has the user activating the z-axis servo motor 22 to lower the button actuator tip 1 until it just contacts the current remote control 101 button.
  • step 206 shows how the user would use the application to make minor adjustments in angle-axis and/or r-axis servo values to center the button actuator tip 1.
  • step 207 would have the user save the current servo settings, with an additional depress value being added to the current z-axis servo value, into nonvolatile controller and power supply 8 memory.
  • step 208 shows the button counter being incremented for the next button and step 209 checks if the final button has been calibrated. If not, steps 203 through 208 will be repeated for the next button. If this is the final button, step 210 completes the calibration process.
  • Step 301 begins with the command from the controlling system 100 identifying the button number and duration of press.
  • Step 302 shows retrieving the saved servo values from the controller and power supply 8 nonvolatile memory for the angle-axis servo motor 9, r-axis servo motor 20 and z-axis servo motor 22.
  • Step 303 shows sending the correct angle-axis value to the angle-axis servo motor 9 to rotate the boom support 10 to the correct angle.
  • Step 304 shows sending the correct r-axis value to the r-axis servo motor 20 to extend the sliding boom to the correct length.
  • Step 305 shows sending the correct z-axis servo value to the z-axis servo motor 22 to lower the button actuator tip 1, thus pressing the remote control button, and initiating a duration timer.
  • Step 306 checks if the button press duration has been exceeded. If not, the timer is incremented in step 309 and step 306 checks the timer again. Steps 306 and 309 are repeated until the timer duration is exceeded.
  • step 307 sends the uppermost button actuator tip 1 position value to z-axis servo motor 22 to return the button actuator tip 1 to the uppermost position.
  • Step 308 shows the end of the operate button actuator process 300.
  • FIG. 10 illustrated is a high level functional block diagram of an exemplary architecture of a system 10 for remote actuation.
  • a vehicle having an actuation package 800, controlled by a user carrying a portable computing device 100, such as a Smartphone, on his person would be one embodiment of the actuation component 100 and the mobile component 850 of such architecture.
  • FIG. 10 illustration depicts an actuation package 800 and a mobile component 850
  • a mobile component 850 and a actuation package 800 may be within a proximate to a user. That is, it is envisioned that certain functionality in an embodiment may be implemented via a remote computing device such as a server 105.
  • the actuation package 800 may communicate with the server 105 via a communications network 191 without need to communicate 190A with a mobile component 850.
  • an actuation package 800 may communicate with either or both of the server 105 and the mobile component 850.
  • the mobile component 850 may transmit data to and/or from the server 105 via link 190B which is implemented over communications network 191.
  • FIG. 12 is a functional block diagram illustrating an exemplary, non-limiting aspect of a portable computing device ("PCD"), such as a mobile component 850 and/or a actuation package 800, for implementing the disclosed methods and systems.
  • the PCD may be in the form of a wireless telephone in some embodiments.
  • the PCD 100, 125 includes an on-chip system 102 that includes a multi-core central processing unit (“CPU") 110 and an analog signal processor 126 that are coupled together.
  • the CPU 110 may comprise a zeroth core 222, a first core 224, and an Nth core 230 as understood by one of ordinary skill in the art.
  • a digital signal processor may also be employed as understood by one of ordinary skill in the art.
  • a display controller 128 and a touch screen controller 130 are coupled to the digital signal processor 110.
  • a touch screen display 132 external to the on-chip system 102 is coupled to the display controller 128 and the touch screen controller 130.
  • PCD 100, 125 may further include a video encoder 134, e.g., a phase-alternating line (“PAL") encoder, a sequential educational memoire (“SECAM”) encoder, a national television system(s) committee (“NTSC”) encoder or any other type of video encoder 134.
  • the video encoder 134 is coupled to the multi-core CPU 110.
  • a video amplifier 136 is coupled to the video encoder 134 and the touch screen display 132.
  • a video port 138 is coupled to the video amplifier 136.
  • a universal serial bus (“USB”) controller 140 is coupled to the CPU 110. Also, a USB port 142 is coupled to the USB controller 140.
  • a memory 112 which may include a PoP memory, a cache 116, a mask ROM/Boot ROM, a boot OTP memory, a DDR memory 115 may also be coupled to the CPU 110.
  • a subscriber identity module (“SIM”) card 146 may also be coupled to the CPU 110.
  • a digital camera 148 may be coupled to the CPU 110. In an exemplary aspect, the digital camera 148 is a charge-coupled device (“CCD”) camera or a complementary metal-oxide semiconductor (“CMOS”) camera.
  • CCD charge-coupled device
  • CMOS complementary metal-oxide semiconductor
  • a stereo audio CODEC 150 may be coupled to the analog signal processor 126.
  • an audio amplifier 152 may be coupled to the stereo audio CODEC 150.
  • a first stereo speaker 154 and a second stereo speaker 156 are coupled to the audio amplifier 152.
  • FIG. 6 shows that a microphone amplifier 158 may be also coupled to the stereo audio CODEC 150.
  • a microphone 160 may be coupled to the microphone amplifier 158.
  • a frequency modulation ("FM") radio tuner 162 may be coupled to the stereo audio CODEC 150.
  • an FM antenna 164 is coupled to the FM radio tuner 162.
  • stereo headphones 166 may be coupled to the stereo audio CODEC 150.
  • FM frequency modulation
  • FIG. 11 further indicates that a radio frequency (“RF") transceiver 168 may be coupled to the analog signal processor 126.
  • An RF switch 170 may be coupled to the RF transceiver 168 and an RF antenna 172.
  • a keypad 174 may be coupled to the analog signal processor 126.
  • a mono headset with a microphone 176 may be coupled to the analog signal processor 126.
  • a vibrator device 178 may be coupled to the analog signal processor 126.
  • FIG. 6 also shows that a power supply 188, for example a battery, is coupled to the on-chip system 102 through a power management integrated circuit ("PMIC”) 180.
  • PMIC power management integrated circuit
  • the power supply 188 includes a rechargeable DC battery or a DC power supply that is derived from an alternating current ("AC") to DC transformer that is connected to an AC power source.
  • the power supply 188 includes a kinetically rechargeable DC battery.
  • FIG. 12 is a schematic diagram illustrating an exemplary software architecture 700 for the disclosed embodiments.
  • the CPU or digital signal processor 110 is coupled to the memory 112 via main bus 211.
  • the memory 112 may reside within a mobile component 850, a actuation package 800 or a combination thereof.
  • the actuation module 101 and the CPU 110 may reside within a mobile component 850, a actuation package 800 or a combination thereof.
  • the CPU 110 is a multiple-core processor having N core processors. That is, the CPU 110 includes a first core 222, a second core 224, and an Nth core 230. As is known to one of ordinary skill in the art, each of the first core 222, the second core 224 and the Nth core 230 are available for supporting a dedicated application or program. Alternatively, one or more applications or programs may be distributed for processing across two or more of the available cores.
  • the CPU 110 may receive commands from the actuation module(s) 101 that may comprise software and/or hardware. If embodied as software, the module(s) 101 comprise instructions that are executed by the CPU 110 that issues commands to other application programs being executed by the CPU 110 and other processors.
  • Bus 211 may include multiple communication paths via one or more wired or wireless connections, as is known in the art and described above in the definitions.
  • the bus 211 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications. Further, the bus 211 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
  • actuation component/mobile component 800/850 When the logic used by the PCD (e.g., actuation component/mobile component) 800/850 is implemented in software, as is shown in FIG. 12 , it should be noted that one or more of startup logic 250, management logic 260, actuation interface logic 270, applications in application store 280 and portions of the file system 290 may be stored on any computer-readable medium for use by, or in connection with, any computer-related system or method.
  • a computer-readable medium is an electronic, magnetic, optical, or other physical device or means that can contain or store a computer program and data for use by or in connection with a computer-related system or method.
  • the computer-readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random-access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM, EEPROM, or Flash memory) (electronic), an optical fiber (optical), Flash, and a portable compact disc read-only memory (CDROM) (optical).
  • the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, for instance via optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
  • Disk and disc includes compact disc ("CD”), laser disc, optical disc, digital versatile disc (“DVD”), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • the various logic may be implemented with any or a combination of the following technologies, which are each well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array
  • the memory 112 is a non-volatile data storage device such as a flash memory or a solid-state memory device. Although depicted as a single device, the memory 112 may be a distributed memory device with separate data stores coupled to the digital signal processor 110 (or additional processor cores).
  • the management logic 260 includes one or more executable instructions for terminating a program on one or more of the respective processor cores, as well as selectively identifying, loading, and executing a more suitable replacement program.
  • the management logic 260 is arranged to perform these functions at run time or while the PCD 100 is powered and in use by an operator of the device.
  • a replacement program which may be customized by a user in some embodiments, may be found in the program store 296 of the embedded file system 290.
  • the interface logic 270 includes one or more executable instructions for presenting, managing and interacting with external inputs to observe, configure, or otherwise update information stored in the embedded file system 290.
  • the interface logic 270 may operate in conjunction with manufacturer inputs received via the USB port 142.
  • These inputs may include one or more programs to be deleted from or added to the program store 296.
  • the inputs may include edits or changes to one or more of the programs in the program store 296.
  • the inputs may identify one or more changes to, or entire replacements of one or both of the startup logic 250 and the management logic 260.
  • the embedded file system 290 includes a hierarchically arranged actuation store 292.
  • the file system 290 may include a reserved section of its total file system capacity for the storage of information for the configuration and management of the various algorithms used by the PCD 800/850.
  • one of ordinary skill in programming is able to write computer code or identify appropriate hardware and/or circuits to implement the disclosed description without difficulty based on the flow charts and associated description in this specification, for example.
  • the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted as one or more instructions or code on a computer-readable medium.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that may be accessed by a computer.
  • such computer-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to carry or store desired program code in the form of instructions or data structures and that may be accessed by a computer.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line ("DSL"), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc includes compact disc (“CD”), laser disc, optical disc, digital versatile disc (“DVD”), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
  • FIG. 18 illustrates a mechanization diagram of the remote control button actuation system 1000 in accordance with another contemplated embodiment of the present disclosure.
  • the controlling system 1001 may again be a mobile device which operates to send user commands via wireless RF through antenna 1002 or other wireless technology, including optical and audible technology, to the controller 1003.
  • the controlling system 1001 could communicate to the controller 1003 through a wired connection, such as shown by reference numeral 1004.
  • the controller 1003 converts commands received from the mobile device 1001 into specific servo motor commands that cause the provision of actuating power to the three-axis button actuator 1005, which then presses the selected remote control button on a remote control device, such as a key fob 1006.
  • the remote control device could be any other type of RF remote, such as a home security remote, a garage door remote or other types of remote control devices.
  • the controller 1003, actuator 1005 and key fob 1006 are all contained within an isolation enclosure 1008.
  • the isolation enclosure 1008 is contemplated as being constructed of metal or a metalized material that will completely block RF transmissions into and out of the isolation enclosure 1008.
  • the isolation enclosure 1008 will be designed as a Faraday cage to limit the RF communications into and out of the isolation enclosure 1008.
  • a receiving antenna 1010 receives control commands from the controlling system 1001.
  • the receiving antenna 1010 is aligned with an opening or other area of the isolation enclosure 1008 that allows RF signals to be received from within the isolation enclosure 1008.
  • the receiving antenna 1010 could be located outside of the isolation enclosure 1008 and connected by a wire to the controller 1003.
  • the receiving antenna 1010 is used by the controller 1003 to receive wireless commands from the controlling system 1001. It is contemplated that the receiving antenna 1010 could be a Bluetooth or other short-range antenna that is able to communicate with the controlling system 1001, such as a mobile device.
  • the controller 1003 When the controller 1003 receives the command from the controlling system 1001, the controller 1003 generates motor commands which are relayed to the actuator 1005.
  • the actuator 1005 converts the commands to actuate a series of servo motors, which cause an actuator tip of the actuator 1005 to press one or more buttons on the key fob 1006.
  • the key fob When the key fob button is pressed, the key fob generates an RF vehicle command signal from the internal key fob antenna 1012 in a conventional manner. Since the key fob 1006 is contained within the enclosure 1008, the command signal sent from the key fob antenna 1012 is isolated and is not directly received by the operating components within the vehicle.
  • the transmitting antenna 1016 is positioned such that the controller is able to transmit RF vehicle command signals out of the enclosure 1008 for receipt by the vehicle's keyless entry and/or keyless ignition system.
  • the use of the receiving antenna 1010 and transmitting antenna 1016 allows the controller 1003 to communicate outside of the enclosure 1008. Since the enclosure 1008 is designed to block RF transmissions, the use of the two antennas 1010 and 1016 allows the actuation system 1000 to isolate the key fob 1006.
  • the controller 1003 is powered by an internal battery 1018. However, it is contemplated that the controller 1003 could also receive power from a 12-volt DC power source 1020, such as a vehicle battery.
  • the actuation system 1000 could be located at various different locations within a vehicle as long as the transmissions from the transmitting antenna 1016 are strong enough to reach the vehicle's keyless entry and keyless starting systems.
  • the actuator 1005 shown in FIG. 18 could be either the embodiment shown previously in the present application or could be one of the two alternate embodiments to be shown in FIGS. 19-30 . In each case, the actuator 1005 is contained within the enclosure 1008 and used to press the required and desired button on the remote control key fob 1006. Although the present disclosure contemplates the remote control as being a key fob 1006, it should be understood other types of remote control systems could be utilized while operating within the scope of the present disclosure.
  • FIG. 19 illustrates one embodiment of the remote control actuation system 1000.
  • the enclosure 1008 includes a top cover 1022, a pair of side walls 1024, a pair of end walls 1026 and a bottom wall 1028.
  • the enclosure 1008 is preferably formed from a metal or metalized material that completely blocks RF transmissions.
  • a key fob 1006 is shown positioned within the enclosure.
  • the key fob shown in FIG. 19 includes five separate buttons 1030A - 1030E each located on the top face 1032 of the key fob 1006. Each of the buttons 1030A - 1030E performs a different function.
  • the actuator 1005 is shown in isolation and removed from the enclosure.
  • the actuator 1005 receives commands from the controller 1003 to move the plunger 1036 into a desired location.
  • the actuator 1005 is able to move the plunger 1036 in three different axes, defined as the x, y and z axes in FIG. 23 .
  • the actuator 1005 includes an outer frame 1038 that encases the entire robotic system.
  • the outer frame 1038 supports a first servo motor 1040.
  • the first servo motor 1040 operates to drive a pinion gear 1042 that engages a long rack gear 1044 supported along a support rail 1046.
  • a second servo motor 1048 is supported on the inner frame 1056 that is movable within the outer frame 1038.
  • the second servo motor 1048 is operable to rotate a first bevel gear 1050 which in turn meshes with a second bevel gear 1052.
  • the second bevel gear 1052 includes a series of teeth that mesh with a second rack gear 1054.
  • the second servo motor 1048 can be activated to move the inner frame 1056 along the pair of spaced support rails 1058.
  • the second servo motor 1048 is operable to move the plunger 1036 along the x-axis.
  • a third servo motor 1060 is connected to a pinion gear 1062 that engages a rack gear 1064 that is movable along a support guide 1065.
  • the rack gear 1064 includes an actuation tip 1066 that combines with the rack gear 1064 to form an actuation plunger 1036.
  • the third servo motor 1060 rotates, the interaction between the pinion gear 1062 and rack gear 1064 moves the plunger 1036 along the z-axis.
  • the lowermost portion of the rack gear 1064 of the plunger 1036 includes the actuation tip 1066.
  • the actuation tip 1066 is designed of a specific size such that the actuation tip 1066 can depress any one of the buttons 1030 formed on the key fob.
  • the battery 1018 is positioned within the enclosure 1008 to power the controller 1003. It is contemplated that a battery access panel (not shown) would be formed in the bottom wall 1028 of the enclosure 1008 to provide access for the batteries 1018 for initial installation and removal when discharged.
  • the enclosure 1008 includes four optical reference posts 1068 that protrude from the bottom wall 1028 at locations surrounding the key fob 1006.
  • the reference posts 1068 will be used for calibrating the location of the key fob 1006 and the individual buttons 1030 within the enclosure 1008.
  • the correct z-axis location of each button is determined by automatically lowering the actuation tip until the key fob begins transmitting an RF signal, which is detected by the controller 1003.
  • the key fob 1006 includes buttons 1030 only on the top face 1032. However, it is contemplated that the key fob could have buttons on either the side or bottom face.
  • the embodiment of the key fob 1070 shown in FIG. 22 includes additional actuating components that allow the actuator 1005 to depress buttons on either the side or back face of the key fob 1070.
  • actuation buttons 1030 are on the front face 1072.
  • the key fob 1070 includes an additional side button 1074 as shown in FIG. 26 and a rear panic button 1077, as shown in FIG. 30 .
  • the actuator 1005 includes a translation frame 1076 mounted within the enclosure 1008.
  • the translation frame 1076 includes a pair of spaced side frames 1078 that are positioned on opposite sides of the key fob 1072.
  • one of the side frames 1078 includes a contact pad 1080 that is formed as part of a pivot arm 1082.
  • the pivot arm 1082 is pivotally connected to the vertical wall 1084 such that downward force on the contact pad 1080 causes the pivot arm to rotate, resulting in movement of a second contact pad 1086 in a perpendicular direction.
  • the downward movement of the contact pad 1080 causes the horizontal movement of the contact pad 1086 into contact with the button 1074 formed on the side 1075 of the key fob 1072.
  • FIGS. 28 and 30 illustrate another type of key fob 1090 that includes the bottom button 1077 mounted on the bottom face 1092.
  • the contact pad 1080 is mounted to a support block 1094, which in turn engages a lower contact pad 1096.
  • the lower contact pad 1096 is formed as part of a spring steel contact arm 1100.
  • the contact arm 1100 includes another mounting block 1102 having a contact pad 1104.
  • the contact pad 1104 engages the bottom button 1077, as illustrated in FIG. 30 . In this manner, the downward, vertical movement created by the plunger is translated to an upward vertical movement of the contact pad 1104 to depress the bottom button 1077.
  • the translation frame 1076 can include a pair of locking fingers 1108 that help to further hold the key fob in place against the upward force created during depression of the bottom button 1077.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Selective Calling Equipment (AREA)
EP17183600.0A 2016-08-04 2017-07-27 Module d'actionnement de bouton de commande à distance, système et procédé de références croisées pour des applications connexes Active EP3279882B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/228,166 US9576414B2 (en) 2013-12-24 2016-08-04 Remote control button actuation module, system, and method

Publications (2)

Publication Number Publication Date
EP3279882A1 true EP3279882A1 (fr) 2018-02-07
EP3279882B1 EP3279882B1 (fr) 2020-09-23

Family

ID=59649460

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17183600.0A Active EP3279882B1 (fr) 2016-08-04 2017-07-27 Module d'actionnement de bouton de commande à distance, système et procédé de références croisées pour des applications connexes

Country Status (2)

Country Link
EP (1) EP3279882B1 (fr)
CA (1) CA2975024C (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3611703A1 (fr) * 2018-08-14 2020-02-19 Blue Eclipse, LLC Actionneur de bouton de commande à distance pourvu d'un plateau amovible
EP3693933A3 (fr) * 2019-02-07 2020-11-11 Blue Eclipse, LLC Actionneur pour commande à distance à deux boutons
US11859407B1 (en) 2020-06-09 2024-01-02 Allstate Insurance Company Remotely accessible secure enclosure

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11180114B1 (en) 2020-05-07 2021-11-23 Toyota Motor North America, Inc. Systems and methods for key fob communication disconnection

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020084694A1 (en) * 2001-01-03 2002-07-04 Quesnel Gary E. Smart car starter
WO2006084330A1 (fr) * 2005-02-11 2006-08-17 Keyless Lifestyles Pty Ltd Dispositif d'acces personnel pour vehicule
US20130181822A1 (en) * 2012-01-16 2013-07-18 Richard Warren Leavitt Method and timer apparatus for fob remote

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8996166B2 (en) * 2010-12-09 2015-03-31 T-Mobile Usa, Inc. Touch screen testing platform

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020084694A1 (en) * 2001-01-03 2002-07-04 Quesnel Gary E. Smart car starter
WO2006084330A1 (fr) * 2005-02-11 2006-08-17 Keyless Lifestyles Pty Ltd Dispositif d'acces personnel pour vehicule
US20090108989A1 (en) 2005-02-11 2009-04-30 Keyless Lifestyles Pty Ltd Personal access arrangement for a vehicle
US20130181822A1 (en) * 2012-01-16 2013-07-18 Richard Warren Leavitt Method and timer apparatus for fob remote

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3611703A1 (fr) * 2018-08-14 2020-02-19 Blue Eclipse, LLC Actionneur de bouton de commande à distance pourvu d'un plateau amovible
US10960849B2 (en) 2018-08-14 2021-03-30 Blue Eclipse, Llc Remote control button actuator with removable tray
EP3693933A3 (fr) * 2019-02-07 2020-11-11 Blue Eclipse, LLC Actionneur pour commande à distance à deux boutons
US11340649B2 (en) 2019-02-07 2022-05-24 Blue Eclipse, Llc Two button remote control actuator
US11859407B1 (en) 2020-06-09 2024-01-02 Allstate Insurance Company Remotely accessible secure enclosure
US12497803B2 (en) 2020-06-09 2025-12-16 Allstate Insurance Company Remotely accessible secure enclosure

Also Published As

Publication number Publication date
CA2975024A1 (fr) 2018-02-04
EP3279882B1 (fr) 2020-09-23
CA2975024C (fr) 2026-05-05

Similar Documents

Publication Publication Date Title
US9576414B2 (en) Remote control button actuation module, system, and method
US9409297B2 (en) Remote control button actuation module, system, and method
EP3279882B1 (fr) Module d'actionnement de bouton de commande à distance, système et procédé de références croisées pour des applications connexes
US11340649B2 (en) Two button remote control actuator
EP2126869B1 (fr) Système et procédé de commande à distance
DE102012203535B4 (de) Tastenloser Fahrzeugschlüssel mit Gestikerkennung
EP3678103B1 (fr) Système d'actionnement de bouton de commande à distance avec proxy à distance
EP3611703B1 (fr) Actionneur de bouton de commande à distance pourvu d'un plateau amovible
US20090210110A1 (en) Method of operating a vehicle accessory
US20180158294A1 (en) Building security and automation system having user-defined screens and associated method
CN105339991B (zh) 遥控交通工具的功能的方法和装置
DE102016121706A1 (de) Verfahren und Systeme zum Aktivieren der Gestensteuerung für ein Fahrzeugmerkmal
CN109466391A (zh) 用于车辆座椅的具有人机界面的扶手模块
US10233675B2 (en) System for physically securing an electronic device
KR20170097943A (ko) 차키 버튼 누름장치를 활용한 차량 관리 시스템
CN106761128B (zh) 电动尾门的控制方法及控制系统
DE102013207094B4 (de) System zur Implementierung von Funktionen im Fahrzeug unter Verwendung von Kurzstreckenkommunikation
CN108657118A (zh) 一种将汽车遥控钥匙改造成无钥匙进入系统的装置及方法
US10896554B2 (en) Apparatus and method for providing vehicle user interface
EP3687281B1 (fr) Système de commande, procédé et programme informatique pour machine de traite automatique
EP3668762A1 (fr) Système d'identification et procédé d'actionnement d'émetteur à distance
KR20150108594A (ko) 도어 제어시스템
AU2018208777A1 (en) Automated hard lid for trayback vehicle
CN209297375U (zh) 一种行车记录仪
KR20230131994A (ko) 차량 및 그 제어 방법

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180801

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20190529

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20200506

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017024019

Country of ref document: DE

Ref country code: AT

Ref legal event code: REF

Ref document number: 1317173

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201015

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201223

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20201224

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1317173

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200923

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200923

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210125

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210123

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017024019

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

26N No opposition filed

Effective date: 20210624

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210727

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210727

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20210731

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20170727

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200923

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20250731

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20250731

Year of fee payment: 9

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20200923

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20260115

Year of fee payment: 9