EP3433699B1 - Controlling a mode of communication between a host computer and a detachable peripheral device - Google Patents

Controlling a mode of communication between a host computer and a detachable peripheral device Download PDF

Info

Publication number
EP3433699B1
EP3433699B1 EP16910719.0A EP16910719A EP3433699B1 EP 3433699 B1 EP3433699 B1 EP 3433699B1 EP 16910719 A EP16910719 A EP 16910719A EP 3433699 B1 EP3433699 B1 EP 3433699B1
Authority
EP
European Patent Office
Prior art keywords
peripheral device
computer
communication
host computer
keyboard
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.)
Active
Application number
EP16910719.0A
Other languages
German (de)
French (fr)
Other versions
EP3433699A1 (en
EP3433699A4 (en
Inventor
Ricky T. BURKS
Shang-Te CHIANG
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.)
Hewlett Packard Development Co LP
Original Assignee
Hewlett Packard Development Co LP
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
Application filed by Hewlett Packard Development Co LP filed Critical Hewlett Packard Development Co LP
Publication of EP3433699A1 publication Critical patent/EP3433699A1/en
Publication of EP3433699A4 publication Critical patent/EP3433699A4/en
Application granted granted Critical
Publication of EP3433699B1 publication Critical patent/EP3433699B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/40Bus structure
    • G06F13/4063Device-to-bus coupling
    • G06F13/4068Electrical coupling
    • G06F13/4081Live connection to bus, e.g. hot-plugging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/1632External expansion units, e.g. docking stations
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/02Input arrangements using manually operated switches, e.g. using keyboards or dials
    • G06F3/023Arrangements for converting discrete items of information into a coded form, e.g. arrangements for interpreting keyboard generated codes as alphanumeric codes, operand codes or instruction codes
    • G06F3/0231Cordless keyboards
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/12Arrangements for remote connection or disconnection of substations or of equipment thereof
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/50Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • a portable computing device such as a tablet computer, may have an associated Bluetooth keyboard that is wirelessly paired to the computing device.
  • a radio of the keyboard may communicate with a radio of the computing device for purposes of communicating input from the keyboard, such as key strokes, trackpad movements, and so forth.
  • US 2009/0058707 A1 discloses a remote control system including a plurality of devices located in a plurality of zones in an operational area.
  • US 2002/0038400 A1 discloses a personal computer system comprising a notebook type personal computer and an expansion device to which the personal computer is removably docked.
  • a host computer may have a detachable keyboard (a Bluetooth keyboard, for example) that wirelessly communicates input data (data representing keystrokes, trackpad movements, mouse button actuations, and so forth) to the computer.
  • a detachable keyboard a Bluetooth keyboard, for example
  • input data data representing keystrokes, trackpad movements, mouse button actuations, and so forth
  • a process called "pairing" may be used.
  • the host computer may have a docking connector that mates with a docking connector of the keyboard to physically attach the keyboard to the computer. Although physically attached together, the keyboard and the host computer may rely on a paired wireless connection for purposes of communicating the input data from the keyboard to the computer. Although a user may expect the keyboard to function when the user docks, or physically attaches, the keyboard to the host computer, the keyboard may not function unless the keyboard is wirelessly paired with the computer. As such, using a detachable keyboard with a host computer may be confusing and burdensome for the user.
  • the mode of communication between a detachable peripheral device (a keyboard, a mouse, and so forth) and a host computer is automatically regulated, depending on whether the peripheral device is attached, or docked, to the host computer or detached, or undocked, from the host computer.
  • the "automatic" regulation refers to the host computer and/or the peripheral device taking actions to control the mode of communication in response to the peripheral device being attached to or detached from the host computer.
  • the peripheral device and the host computer may communicate using either a wired mode of communication or a wireless mode of communication.
  • a connection management engine of the host computer sets up a wired mode of communication between the host computer and the peripheral.
  • the connection management engine sets ups a wireless mode of communication between the host computer and the peripheral.
  • a "wired mode of communication” refers to the host computer and the peripheral device communicating using signaling on at least one wired connection between the host computer and the peripheral device.
  • the wired connection may include the connection of one or multiple physical terminals of a docking connector of the host computer with one or multiple physical terminals of a mating docking connector of the keyboard.
  • the physical terminal(s) may be associated with a serial bus, and the host computer and the peripheral device may be agents of the serial bus.
  • the wired mode of communication may involve a serial bus interface of the host computer communicating, via the connected physical terminal connections, with a serial bus interface of the peripheral device.
  • the wired mode of communication includes using signaling that complies with the Universal Serial Bus (USB) or Inter-Integrated Circuit (I 2 C) specification.
  • the wired mode of communication may involve using a serial bus other than a USB or I 2 C bus, and the wired mode of communication may involve the use of a bus other than a serial bus.
  • the "wireless mode of communication" refers to the host computer and the peripheral device communicating using wirelessly signaling.
  • a radio of the host computer may communicate with a radio of the peripheral device using wireless communication that complies with the Bluetooth standard promulgated by the Bluetooth Special Interest Group.
  • the host computer may be a Bluetooth master device
  • the peripheral device may be a Bluetooth slave device.
  • the host computer and the peripheral device perform a process called "pairing.”
  • the keyboard and the host computer authenticate each other to become bonded, or paired.
  • the peripheral device and the host computer may transition from the wired mode of communication to the wireless mode of communication, as described herein, without undergoing the pairing process.
  • the wireless mode of communication may involve the use of wireless signaling other than Bluetooth-based communication.
  • the wireless mode of communication may involve the use of signaling that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (commonly called "WiFi”), near field communication (NFC), and so forth.
  • IEEE Institute of Electrical and Electronics Engineers 802.11 standards
  • NFC near field communication
  • the peripheral device may be used with the host computer by merely attaching the device to the computer.
  • a keyboard may be newly purchased and used for the first time (i.e., the keyboard may have just been taken "out of the box").
  • the keyboard may be docked to a computer and used to supply input to the computer without a user first taking actions to wirelessly pair the keyboard to the computer.
  • the user may therefore have a seamless keyboard experience, as the keyboard works as intuitively expected by the user.
  • a computer system 100 may include a tablet computer 104 (an example of a host computer) and a detachable keyboard 150 (an example of a peripheral).
  • the keyboard 150 may communicate with the tablet computer 104 using one of two modes of communication: 1. a wired mode of communication in which a bus interface 164 (a serial bus interface, such as a USB or I 2 C bus interface, for example) of the keyboard 150 communicates input data (data representing key strokes, trackpad movements, mouse button "clicks," and so forth) with a serial bus interface 118 (a USB or I 2 C bus interface, for example) of the tablet computer 104 when the keyboard 150 is docked to the tablet computer104; and 2. a wireless mode of communication in which a radio 160 (a Bluetooth radio, for example) of the keyboard 150 wirelessly communicates input data with a radio 114 (a Bluetooth radio, for example) of the tablet computer 104.
  • a radio 160 a Bluetooth radio, for example
  • Fig. 1 depicts the keyboard 150 for a state of the computer system 100 in which the keyboard 150 is detached, or undocked, from the tablet computer 104.
  • a docking connector 155 of the keyboard 150 is detached, or undocked, from a mating docking connector 130 of the tablet computer 104.
  • electrical contacts, or terminals, of the docking connector 130 mate with electrical contacts of the docking connector 155 of the keyboard to form corresponding wired connections between the keyboard 150 and the tablet computer 104 to communicate, for example, signals and power.
  • One or multiple wired connections formed by the docking of the keyboard 150 and the tablet computer 104 may communicate one or multiple signals associated with a serial bus, such as the USB or I 2 C bus.
  • One of multiple wired connections formed by the docking of the keyboard 150 to the tablet computer 104 may be used to alert the tablet computer 150 to an undocking event (the occurrence of the keyboard 150 being detached, or undocked, from, the tablet computer 104) or a docking event (the occurrence of the keyboard 150 being attached, or docked to, the tablet computer 104).
  • circuitry of the tablet computer 104 may generate interrupts in response to voltage transitions on a docking sense contact of the docking connector 130, which occur due to the docking or undocking of the docking connector 155.
  • the tablet computer 104 includes a connection management engine 108, which may be a processor-based engine (as depicted by a processor 110 of the engine 108 in Fig. 1 ).
  • the connection management engine 108 automatically transitions between wired and wireless modes of communication the keyboard 150 and the tablet computer 104 in response to docking and undocking events.
  • the connection management engine 108 in response to a docking event, automatically sets up a wired connection between the keyboard 150 and the tablet computer 104 so that keyboard input data is communicated to the tablet computer 104 using the bus interfaces 118 and 164. Moreover, in accordance with example implementations, in response to an undocking event, the connection management engine 108 automatically sets up a wireless connection between the keyboard 150 and the tablet computer 104 so that keyboard input data is communicated to the tablet computer 104 using wireless transmissions via the radios 114 and 160.
  • connection management engine 108 may communicate with a connection management engine 154 of the keyboard 150 to set up the keyboard 150 for the wireless and wired modes of communication.
  • the connection management engine 154 in accordance with example implementations, may be a processor-based engine 154 (as depicted by a processor 156) in Fig. 1 .
  • connection management engine 108 of the tablet computer 104 may be a master, which controls the connection management engine 154 of the keyboard 150 as a slave for purposes of instructing the engine 154 to set up the keyboard 150 for wired or wireless communication with the tablet computer 104; or the connection management engine 154 of the keyboard 150 may operate autonomously to detect the docking status of the keyboard 150 and control whether the keyboard 150 is set up for wired or wireless communications.
  • the connection management engine 154 of the keyboard 150 may be a master, which controls the connection management engine 108 of the tablet computer 104 as a slave for purposes of instructing the engine 108 to set up the tablet computer 104 for wired or wireless communication with the keyboard 150.
  • the keyboard 150 and the tablet computer 104 are first wirelessly bonded, or paired.
  • the wireless pairing of the radios 116 and 160 may occur many different ways, depending on the particular implementation.
  • the wireless pairing may be initiated in response to a human user depressing a designated pairing key or button on the keyboard 150.
  • the connection management engine 108 may use a Simple Secure Pairing (SSP) protocol in a process that does not involve the user entering a pass key via the keyboard 150.
  • SSP Simple Secure Pairing
  • the initial wireless pairing may involve the connection management engine 108 causing a display 120 of the tablet computer 140 to display a numeric code for the user to enter via keys 151 of the keyboard 150.
  • the tablet computer 104 and the keyboard 150 may be pre-paired by the manufacturer or seller of the tablet computer 104 and keyboard 150.
  • the keyboard 150 and the tablet computer 104 remain bonded, or paired, independently from the communication mode (wireless or wired) being used, unless the user undertakes action(s) on the tablet computer 104 to remove the pairing.
  • the mode of communication between the tablet computer 104 and the keyboard 150 may transition between the wired and wireless modes, with the pairing remaining intact.
  • the tablet computer 104 may, in general, include a housing 106 in which the connection management engine 108, radio 114 and bus interface 118 are disposed.
  • the housing 106 includes that includes a region for a display 120; openings for power buttons, camera(s), speaker(s), control buttons; and an opening through which the docking connector 130 extends.
  • the tablet computer 104 may include various other software and/or hardware components, as further described herein.
  • the keyboard 150 may include various other features, such as, for example, keys 151 and a trackpad 153 with associated mouse buttons.
  • a technique 200 includes communicating (block 204) data between a host computer and a peripheral device, where the peripheral device is docked to the host computer and the communication involves using a wired mode of communication.
  • the technique 200 includes detecting (block 206) undocking of the peripheral device from the host computer; and in response to the detection of the undocking, automatically transitioning from using the wired mode of communication to using the wireless mode of communication to communicate data between the host computer and the peripheral device.
  • a technique 300 includes a host computer communicating (block 304) with a peripheral device using a paired wireless connection between the peripheral device and a radio of the host computer in response to the peripheral device being disconnected from a docking connector.
  • the technique includes the host computer determining (decision block 308) whether the peripheral device has engaged with docking connector of the host computer, and if not, communication continues using the paired wireless connection, pursuant to block 304.
  • the technique 300 includes the host computer bypassing (block 312) using the paired wireless connection and using a wired connection to communicate data with the peripheral device.
  • the mode is changed to a wired mode of communication when the peripheral device is attached, or docked. to the host computer.
  • a wired mode of communication between the peripheral device and the host computer may be beneficial for certain operations of the host computer. For example, a user may use an attached keyboard to perform a lower level basic input/output system (BIOS) operation on the host computer, and this BIOS operation may not support the wireless mode of communication.
  • BIOS basic input/output system
  • the host computer may transition to a power conservation state (transition from a fully powered up state to a hibernation or sleep state, for example).
  • the host computer may be able to wake up in response to a key stroke or trackpad input from a keyboard that communicates with the host computer using a wired mode of communication, but the host computer may be unable to wake up in response to keyboard input if the keyboard communicates with the host computer using a wireless mode of communication.
  • the connection management engine 108 may perform a technique 400 that is depicted in Fig. 4 .
  • the technique 400 assumes that a keyboard (the example peripheral device) is "out of the box," batteries have been installed in the keyboard, and the keyboard is wirelessly discoverable by the host computer.
  • the technique 400 includes the connection management engine 108 determining (decision block 404) whether a docking event has occurred. If not, the connection management engine 108 determines (decision block 408) whether the host computer has been wirelessly paired with the keyboard.
  • connection management engine 108 determines (decision block 412) whether the host computer is operating in a BIOS mode of operation, which does not support wireless communication. If so, then the connection management engine 108 may not take further action. In accordance with further example implementations, in response to determining the host computer is operating in a BIOS mode of operation, the connection management engine 108 may set up the wired mode of communication so that the keyboard may be used if attached to the host computer.
  • connection management engine 108 determines that the host computer is not operating in a BIOS mode operation, then the connection management engine 108 wirelessly pairs the keyboard and host computer, pursuant to block 420. If the pairing is unsuccessful, then one or multiple attempts may be performed (as depicted in decision blocks 424 and 428).
  • connection management engine 108 sets up the wireless mode of communication so that data is communicated using a wireless connection, pursuant to block 432.
  • connection management engine 108 may transition the keyboard to the wired mode of operation in response to the host computer entering into a power conservation mode. Therefore, in accordance with some implementations, in response to the connection management engine 108 determining (decision block 436) that host computer is about to transition to a power conservation mode, the connection management engine 108 removes the wireless connection (block 444) and sets up a wired connection with the keyboard (block 454). Therefore, the user may dock the keyboard with the host computer and use input from the keyboard for purposes of thereafter waking up the computer from the power conservation mode, as described herein.
  • the connection management engine 108 may remove the wireless connection (block 444) and set up the wired connection with the keyboard, pursuant to block 454.
  • connection management engine 108 determines (decision block 462) that an undocking event has occurred. When this occurs, control transitions to decision block 408, as described above.
  • the tablet computer 104 may include hardware 510 and software 560.
  • the hardware 510 may include one or multiple processors 110, the radio 114, and one or multiple bus interfaces 118.
  • the memory 514 contains a non-transitory storage medium that is formed from semiconductor storage devices, memristors, phase change devices, volatile memory devices, non-volatile memory devices, and so forth.
  • the tablet computer 104 includes instructions 564, which when executed by one or multiple processor(s) 110 cause the processor(s) 110 to form the connection management engine 108.
  • the software 560 may include sets 572 of machine executable instructions that when executed by the processor(s) 110 cause the processor(s) 110 to form one or multiple device drivers and sets 576 of machine executable instruction that when executed by the processor(s) 110 cause the processor(s) 110 to form one or multiple applications.
  • the tablet computer 104 may include various other sets of machine executable instructions, such as instructions 568, which when executed by the processor(s) 110 cause the processor(s) 110 to form an operating system.
  • the machine executable instructions described herein may be stored in a non-transitory computer readable storage medium, such as the memory 514.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Human Computer Interaction (AREA)
  • Input From Keyboards Or The Like (AREA)

Description

    Background
  • A portable computing device, such as a tablet computer, may have an associated Bluetooth keyboard that is wirelessly paired to the computing device. In this manner, a radio of the keyboard may communicate with a radio of the computing device for purposes of communicating input from the keyboard, such as key strokes, trackpad movements, and so forth. For example, US 2009/0058707 A1 discloses a remote control system including a plurality of devices located in a plurality of zones in an operational area. US 2002/0038400 A1 discloses a personal computer system comprising a notebook type personal computer and an expansion device to which the personal computer is removably docked.
  • Brief Description of the Drawings
    • Fig. 1 is a schematic diagram of a system that includes a tablet computer and a detachable keyboard according to an example implementation.
    • Fig. 2 is a flow diagram depicting a technique to transition from a wired mode of communication between a peripheral device and a host computer to a wireless mode of communication between the peripheral device and the host computer in response to the undocking of the peripheral device from the host computer.
    • Fig. 3 is a flow diagram depicting a technique to transition from a wireless mode of communication between the peripheral device and the host computer to a wired mode of communication between the peripheral device and the host computer in response to the peripheral device being docked to the host computer.
    • Fig. 4 is a flow diagram depicting a technique to control wireless and wired connections between a host computer and a keyboard according to an example implementation.
    • Fig. 5 is a schematic diagram of a host computer according to an example implementation.
    Detailed Description
  • A host computer (a tablet computer, a smartphone, a notebook computer, and so forth) may have a detachable keyboard (a Bluetooth keyboard, for example) that wirelessly communicates input data (data representing keystrokes, trackpad movements, mouse button actuations, and so forth) to the computer. For purposes of setting up the wireless connection between the host computer and the keyboard, a process called "pairing" may be used.
  • The host computer may have a docking connector that mates with a docking connector of the keyboard to physically attach the keyboard to the computer. Although physically attached together, the keyboard and the host computer may rely on a paired wireless connection for purposes of communicating the input data from the keyboard to the computer. Although a user may expect the keyboard to function when the user docks, or physically attaches, the keyboard to the host computer, the keyboard may not function unless the keyboard is wirelessly paired with the computer. As such, using a detachable keyboard with a host computer may be confusing and burdensome for the user.
  • In accordance with example implementations that are described herein, the mode of communication between a detachable peripheral device (a keyboard, a mouse, and so forth) and a host computer is automatically regulated, depending on whether the peripheral device is attached, or docked, to the host computer or detached, or undocked, from the host computer. In this context, the "automatic" regulation refers to the host computer and/or the peripheral device taking actions to control the mode of communication in response to the peripheral device being attached to or detached from the host computer.
  • More specifically, in accordance with example implementations, the peripheral device and the host computer may communicate using either a wired mode of communication or a wireless mode of communication. In accordance with example implementations, when the peripheral s attached, or docked, to the host computer, a connection management engine of the host computer sets up a wired mode of communication between the host computer and the peripheral. Moreover, in accordance with example implementations, when the peripheral is detached, or undocked, from the host computer, the connection management engine sets ups a wireless mode of communication between the host computer and the peripheral.
  • In this context, a "wired mode of communication" refers to the host computer and the peripheral device communicating using signaling on at least one wired connection between the host computer and the peripheral device. For example, the wired connection may include the connection of one or multiple physical terminals of a docking connector of the host computer with one or multiple physical terminals of a mating docking connector of the keyboard. In accordance with example implementations, the physical terminal(s) may be associated with a serial bus, and the host computer and the peripheral device may be agents of the serial bus. As such, in accordance with example implementations, the wired mode of communication may involve a serial bus interface of the host computer communicating, via the connected physical terminal connections, with a serial bus interface of the peripheral device. In accordance with example implementations, the wired mode of communication includes using signaling that complies with the Universal Serial Bus (USB) or Inter-Integrated Circuit (I2C) specification. In accordance with further implementations, the wired mode of communication may involve using a serial bus other than a USB or I2C bus, and the wired mode of communication may involve the use of a bus other than a serial bus.
  • In accordance with example implementations, the "wireless mode of communication" refers to the host computer and the peripheral device communicating using wirelessly signaling. For example, in accordance with example implementations, a radio of the host computer may communicate with a radio of the peripheral device using wireless communication that complies with the Bluetooth standard promulgated by the Bluetooth Special Interest Group. In this manner, the host computer may be a Bluetooth master device, and the peripheral device may be a Bluetooth slave device. For purposes of initially setting up a Bluetooth-based wireless connection, the host computer and the peripheral device perform a process called "pairing." In the pairing process, the keyboard and the host computer authenticate each other to become bonded, or paired. After being paired, the peripheral device and the host computer may transition from the wired mode of communication to the wireless mode of communication, as described herein, without undergoing the pairing process.
  • In accordance with further implementations, the wireless mode of communication may involve the use of wireless signaling other than Bluetooth-based communication. For example, in accordance with further implementations, the wireless mode of communication may involve the use of signaling that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (commonly called "WiFi"), near field communication (NFC), and so forth.
  • In accordance with example implementations, regardless of whether the peripheral device is wirelessly paired with the host computer or not, the peripheral device may be used with the host computer by merely attaching the device to the computer. For example, a keyboard may be newly purchased and used for the first time (i.e., the keyboard may have just been taken "out of the box"). The keyboard may be docked to a computer and used to supply input to the computer without a user first taking actions to wirelessly pair the keyboard to the computer. The user may therefore have a seamless keyboard experience, as the keyboard works as intuitively expected by the user.
  • Referring to Fig. 1, in accordance with example implementations, a computer system 100 may include a tablet computer 104 (an example of a host computer) and a detachable keyboard 150 (an example of a peripheral). The keyboard 150 may communicate with the tablet computer 104 using one of two modes of communication: 1. a wired mode of communication in which a bus interface 164 (a serial bus interface, such as a USB or I2C bus interface, for example) of the keyboard 150 communicates input data (data representing key strokes, trackpad movements, mouse button "clicks," and so forth) with a serial bus interface 118 (a USB or I2C bus interface, for example) of the tablet computer 104 when the keyboard 150 is docked to the tablet computer104; and 2. a wireless mode of communication in which a radio 160 (a Bluetooth radio, for example) of the keyboard 150 wirelessly communicates input data with a radio 114 (a Bluetooth radio, for example) of the tablet computer 104.
  • Fig. 1 depicts the keyboard 150 for a state of the computer system 100 in which the keyboard 150 is detached, or undocked, from the tablet computer 104. In other words, a docking connector 155 of the keyboard 150 is detached, or undocked, from a mating docking connector 130 of the tablet computer 104. In accordance with example implementations, electrical contacts, or terminals, of the docking connector 130 mate with electrical contacts of the docking connector 155 of the keyboard to form corresponding wired connections between the keyboard 150 and the tablet computer 104 to communicate, for example, signals and power. One or multiple wired connections formed by the docking of the keyboard 150 and the tablet computer 104 may communicate one or multiple signals associated with a serial bus, such as the USB or I2C bus.
  • One of multiple wired connections formed by the docking of the keyboard 150 to the tablet computer 104 may be used to alert the tablet computer 150 to an undocking event (the occurrence of the keyboard 150 being detached, or undocked, from, the tablet computer 104) or a docking event (the occurrence of the keyboard 150 being attached, or docked to, the tablet computer 104). For example, in accordance with example implementations, circuitry of the tablet computer 104 may generate interrupts in response to voltage transitions on a docking sense contact of the docking connector 130, which occur due to the docking or undocking of the docking connector 155.
  • In accordance with example implementations, the tablet computer 104 includes a connection management engine 108, which may be a processor-based engine (as depicted by a processor 110 of the engine 108 in Fig. 1). The connection management engine 108 automatically transitions between wired and wireless modes of communication the keyboard 150 and the tablet computer 104 in response to docking and undocking events.
  • More specifically, in accordance with example implementations, in response to a docking event, the connection management engine 108 automatically sets up a wired connection between the keyboard 150 and the tablet computer 104 so that keyboard input data is communicated to the tablet computer 104 using the bus interfaces 118 and 164. Moreover, in accordance with example implementations, in response to an undocking event, the connection management engine 108 automatically sets up a wireless connection between the keyboard 150 and the tablet computer 104 so that keyboard input data is communicated to the tablet computer 104 using wireless transmissions via the radios 114 and 160.
  • The connection management engine 108, in accordance with example implementations, may communicate with a connection management engine 154 of the keyboard 150 to set up the keyboard 150 for the wireless and wired modes of communication. The connection management engine 154, in accordance with example implementations, may be a processor-based engine 154 (as depicted by a processor 156) in Fig. 1.
  • Depending on the particular implementation, the connection management engine 108 of the tablet computer 104 may be a master, which controls the connection management engine 154 of the keyboard 150 as a slave for purposes of instructing the engine 154 to set up the keyboard 150 for wired or wireless communication with the tablet computer 104; or the connection management engine 154 of the keyboard 150 may operate autonomously to detect the docking status of the keyboard 150 and control whether the keyboard 150 is set up for wired or wireless communications. In accordance with further example implementations, the connection management engine 154 of the keyboard 150 may be a master, which controls the connection management engine 108 of the tablet computer 104 as a slave for purposes of instructing the engine 108 to set up the tablet computer 104 for wired or wireless communication with the keyboard 150.
  • In accordance with example implementations, before the keyboard 150 may be used to wirelessly communicate data with the tablet computer 104, the keyboard 150 and the tablet computer 104 are first wirelessly bonded, or paired. The wireless pairing of the radios 116 and 160 (and thus, the corresponding pairing of the keyboard 150 and the tablet computer 104) may occur many different ways, depending on the particular implementation. For example, the wireless pairing may be initiated in response to a human user depressing a designated pairing key or button on the keyboard 150. In accordance with some implementations, the connection management engine 108 may use a Simple Secure Pairing (SSP) protocol in a process that does not involve the user entering a pass key via the keyboard 150. In accordance with further implementations, the initial wireless pairing may involve the connection management engine 108 causing a display 120 of the tablet computer 140 to display a numeric code for the user to enter via keys 151 of the keyboard 150. In accordance with further example implementations, the tablet computer 104 and the keyboard 150 may be pre-paired by the manufacturer or seller of the tablet computer 104 and keyboard 150.
  • In accordance with example implementations, the keyboard 150 and the tablet computer 104 remain bonded, or paired, independently from the communication mode (wireless or wired) being used, unless the user undertakes action(s) on the tablet computer 104 to remove the pairing. Thus, in accordance with example implementations, the mode of communication between the tablet computer 104 and the keyboard 150 may transition between the wired and wireless modes, with the pairing remaining intact.
  • Among its other features, the tablet computer 104 may, in general, include a housing 106 in which the connection management engine 108, radio 114 and bus interface 118 are disposed. The housing 106 includes that includes a region for a display 120; openings for power buttons, camera(s), speaker(s), control buttons; and an opening through which the docking connector 130 extends. Moreover, the tablet computer 104 may include various other software and/or hardware components, as further described herein.
  • In addition to the docking connector 155, the connection management engine 154, the radio 160 and the bus interface 164, the keyboard 150 may include various other features, such as, for example, keys 151 and a trackpad 153 with associated mouse buttons.
  • Thus, referring to Fig. 2, in accordance with example implementations, a technique 200 includes communicating (block 204) data between a host computer and a peripheral device, where the peripheral device is docked to the host computer and the communication involves using a wired mode of communication. The technique 200 includes detecting (block 206) undocking of the peripheral device from the host computer; and in response to the detection of the undocking, automatically transitioning from using the wired mode of communication to using the wireless mode of communication to communicate data between the host computer and the peripheral device.
  • Moreover, referring to Fig. 3, in accordance with example implementations, a technique 300 includes a host computer communicating (block 304) with a peripheral device using a paired wireless connection between the peripheral device and a radio of the host computer in response to the peripheral device being disconnected from a docking connector. The technique includes the host computer determining (decision block 308) whether the peripheral device has engaged with docking connector of the host computer, and if not, communication continues using the paired wireless connection, pursuant to block 304. In response to a determination that the peripheral device has engaged the docking connector, pursuant to decision block 308, the technique 300 includes the host computer bypassing (block 312) using the paired wireless connection and using a wired connection to communicate data with the peripheral device.
  • Therefore, in accordance with example implementations, even if the peripheral device and the host computer are communicating using a wireless mode of communication, the mode is changed to a wired mode of communication when the peripheral device is attached, or docked. to the host computer. A wired mode of communication between the peripheral device and the host computer may be beneficial for certain operations of the host computer. For example, a user may use an attached keyboard to perform a lower level basic input/output system (BIOS) operation on the host computer, and this BIOS operation may not support the wireless mode of communication. As another example, the host computer may transition to a power conservation state (transition from a fully powered up state to a hibernation or sleep state, for example). The host computer may be able to wake up in response to a key stroke or trackpad input from a keyboard that communicates with the host computer using a wired mode of communication, but the host computer may be unable to wake up in response to keyboard input if the keyboard communicates with the host computer using a wireless mode of communication.
  • In accordance with some implementations, the connection management engine 108 (Fig. 1) may perform a technique 400 that is depicted in Fig. 4. The technique 400 assumes that a keyboard (the example peripheral device) is "out of the box," batteries have been installed in the keyboard, and the keyboard is wirelessly discoverable by the host computer. Referring to Fig. 4 in conjunction with Fig. 1, the technique 400 includes the connection management engine 108 determining (decision block 404) whether a docking event has occurred. If not, the connection management engine 108 determines (decision block 408) whether the host computer has been wirelessly paired with the keyboard.
  • If the host computer has not been wirelessly paired with the keyboard, then the connection management engine 108 determines (decision block 412) whether the host computer is operating in a BIOS mode of operation, which does not support wireless communication. If so, then the connection management engine 108 may not take further action. In accordance with further example implementations, in response to determining the host computer is operating in a BIOS mode of operation, the connection management engine 108 may set up the wired mode of communication so that the keyboard may be used if attached to the host computer.
  • If, pursuant to decision block 412, the connection management engine 108 determines that the host computer is not operating in a BIOS mode operation, then the connection management engine 108 wirelessly pairs the keyboard and host computer, pursuant to block 420. If the pairing is unsuccessful, then one or multiple attempts may be performed (as depicted in decision blocks 424 and 428).
  • If the wireless pairing is successful (decision block 424) or the host computer and keyboard are already paired (decision block 408), then the connection management engine 108 sets up the wireless mode of communication so that data is communicated using a wireless connection, pursuant to block 432.
  • In accordance with some implementations, the connection management engine 108 may transition the keyboard to the wired mode of operation in response to the host computer entering into a power conservation mode. Therefore, in accordance with some implementations, in response to the connection management engine 108 determining (decision block 436) that host computer is about to transition to a power conservation mode, the connection management engine 108 removes the wireless connection (block 444) and sets up a wired connection with the keyboard (block 454). Therefore, the user may dock the keyboard with the host computer and use input from the keyboard for purposes of thereafter waking up the computer from the power conservation mode, as described herein.
  • Otherwise, in accordance with example implementations, if the host computer is not transitioning to a power conservation mode and a docking event (decision block 440) has not been detected, the wired mode of communication remains, and data is communicated from the keyboard to the host computer using a wired connection, pursuant to block 432. As depicted in Fig. 4, upon determining a docking event has occurred (decision block 440), the connection management engine 108 may remove the wireless connection (block 444) and set up the wired connection with the keyboard, pursuant to block 454.
  • After setting up the wired connection with the keyboard, data may be communicated from the keyboard to the host computer, pursuant to block 458, until the connection management engine 108 determines (decision block 462) that an undocking event has occurred. When this occurs, control transitions to decision block 408, as described above.
  • Referring to Fig. 5 in connection with Fig. 1, in accordance with some implementations, the tablet computer 104 (an example of a host computer) may include hardware 510 and software 560. In this manner, the hardware 510 may include one or multiple processors 110, the radio 114, and one or multiple bus interfaces 118. The memory 514 contains a non-transitory storage medium that is formed from semiconductor storage devices, memristors, phase change devices, volatile memory devices, non-volatile memory devices, and so forth.
  • In accordance with example implementations, the tablet computer 104 includes instructions 564, which when executed by one or multiple processor(s) 110 cause the processor(s) 110 to form the connection management engine 108. Moreover, in accordance with example implementations, the software 560 may include sets 572 of machine executable instructions that when executed by the processor(s) 110 cause the processor(s) 110 to form one or multiple device drivers and sets 576 of machine executable instruction that when executed by the processor(s) 110 cause the processor(s) 110 to form one or multiple applications. Moreover, in accordance with example implementations, the tablet computer 104 may include various other sets of machine executable instructions, such as instructions 568, which when executed by the processor(s) 110 cause the processor(s) 110 to form an operating system. In accordance with some implementations, the machine executable instructions described herein may be stored in a non-transitory computer readable storage medium, such as the memory 514.
  • While the present invention has been described with respect to a limited number of embodiments, those skilled in the art, having the benefit of this disclosure, will appreciate numerous modifications and variations therefrom.

Claims (12)

  1. A method comprising:
    communicating data between a host computer (104) and a peripheral device (150), wherein the peripheral device (150) is docked to the host computer (104) and the communicating comprises using a wired mode of communication;
    detecting undocking of the peripheral device (150) from the host computer (104); and in response to the detection of the undocking, automatically transitioning from using the wired mode of communication to using a wireless mode of communication to communicate data between the host computer (104) and the peripheral device (150),
    wherein using the wireless mode of communication comprises using a paired wireless connection between the host computer (104) and the peripheral device (150);
    detecting the docking of the peripheral device (150) to the host computer (104); and in response to the detection of the docking, automatically transitioning from using the wireless mode of communication to using the wired mode of communication; and
    in response to the detection of the docking, bypassing the paired wireless connection between the host computer (104) and the peripheral device (150).
  2. The method of claim 1, further comprising:
    in response to a transition of the host computer (104) from a first power conservation state associated with a first power consumption to a second power conservation state associated with a second power consumption less than the first power consumption,
    transitioning from the wireless mode of communication to the wired mode of communication.
  3. The method of claim 1, further comprising:
    determining whether the host computer (104) is performing a basic input/output system, BIOS, function using data provided by a keyboard (150); and
    initiating transitioning from using the wireless mode of communication to using the wired mode of communication based at least in part on the determining.
  4. The method of claim 1, wherein the peripheral device (150) comprises a keyboard (150).
  5. An apparatus, comprising:
    a housing (106);
    a radio (160) contained in the housing;
    a processor contained in the housing (106); and
    a docking connector (155) to connect a peripheral device (150) to the housing (106) by a wired connection,
    wherein the processor is configured to:
    communicate data with the peripheral device (150) using a paired wireless connection between the peripheral device (150) and the radio (160) in response to the peripheral device (150) being undocked from the docking connector (130, 155);
    detect docking of the peripheral device (150) to the docking connector (130, 155), and in response to the detection of the docking of the peripheral device (150) with the docking connector (155) bypass the paired wireless connection and use the wired connection to communicate data with the peripheral device (150).
  6. The apparatus of claim 5, wherein the docking connector (130, 155) comprises a least one electrical connection pin associated with the wired connection.
  7. The apparatus of claim 5, further comprising:
    a touchscreen, and wherein the docking connector (130, 155) comprises a keyboard connector.
  8. The apparatus of claim 5, further comprising a first serial bus interface (164) contained in the housing (106), wherein:
    the wired connection comprises a serial bus; the first serial bus interface (164) is an agent on the serial bus;
    the peripheral device (150) comprises a second serial bus interface (118); and
    the second serial bus interface (118) is an agent on the serial bus, wherein physical terminal(s) are associated with the serial bus, and the host computer and the peripheral device (150) are agents of the serial bus.
  9. An article comprising a non-transitory computer readable storage medium to store instructions that when executed by a computer (104) cause the computer to:
    in response to a peripheral device (150), for example a keyboard (150), being undocked from a computer (104), automatically transition the computer (104) from a wired mode of communication to a paired wireless mode of communication to cause data between the peripheral device (150) and the computer (104) to be communicated wirelessly using a paired wireless connection; and
    in response to the peripheral device (150) being docked to the computer (104), automatically transition the computer (104) from the paired wireless mode of communication to a wired mode of communication to cause data between the peripheral device (150) and the computer (104) to be communicated using a wired connection, and, in response to the detection of the docking, bypassing the paired wireless connection between the host computer (104) and the peripheral device (150).
  10. The article of claim 9, the storage medium storing instructions that when executed by the computer (104) cause the computer (104) to, in response to the peripheral device (150) being docked to the computer (104), configuring the computer (104) to use a serial bus to
    communicate data between the peripheral device (150) and the computer (104).
  11. The article of claim 9, the storage medium storing instructions that when executed by the computer (104) cause the computer to determine whether the computer (104) is using input from the peripheral device (150) for a basic input/output system, BIOS, function and initiate the automatic transition from the wired mode of communication to the wireless mode of communication based at least in part on a result of the determination.
  12. The article of claim 9, the storage medium storing instructions that when executed by the computer (104) cause the computer (104) to pair the computer (104) with the peripheral device (150) using a Simple Secure Pairing, SSP, protocol.
EP16910719.0A 2016-07-28 2016-07-28 Controlling a mode of communication between a host computer and a detachable peripheral device Active EP3433699B1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/044366 WO2018022050A1 (en) 2016-07-28 2016-07-28 Controlling a mode of communication between a host computer and a detachable peripheral device

Publications (3)

Publication Number Publication Date
EP3433699A1 EP3433699A1 (en) 2019-01-30
EP3433699A4 EP3433699A4 (en) 2019-10-30
EP3433699B1 true EP3433699B1 (en) 2020-09-09

Family

ID=61017055

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16910719.0A Active EP3433699B1 (en) 2016-07-28 2016-07-28 Controlling a mode of communication between a host computer and a detachable peripheral device

Country Status (4)

Country Link
US (1) US10713204B2 (en)
EP (1) EP3433699B1 (en)
CN (1) CN109154844A (en)
WO (1) WO2018022050A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102514763B1 (en) * 2017-07-25 2023-03-28 삼성전자주식회사 Method for utilizing input device and electronic device for the same
DE102018132690A1 (en) * 2018-12-18 2020-06-18 Yaasa Living Ag Platform for a variable, adaptable piece of furniture, such a piece of furniture and method for controlling such a piece of furniture
WO2021015752A1 (en) * 2019-07-24 2021-01-28 Hewlett-Packard Development Company, L.P. Keyboard with input modes
CN113873479A (en) * 2021-08-02 2021-12-31 深兰科技(上海)有限公司 Communication method of stacked robot and related device
CN115295343B (en) * 2022-09-23 2023-04-07 荣耀终端有限公司 Signal transmission method and related equipment

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5889964A (en) * 1996-11-21 1999-03-30 Intel Corporation Method and apparatus for docking and undocking a notebook computer to and from a docking station while the notebook computer is in an active state
JP4634590B2 (en) * 2000-09-27 2011-02-16 株式会社東芝 Electronic device system, electronic device, and communication means switching method
US20030021082A1 (en) * 2001-07-26 2003-01-30 Inventec Corporation Detachable wireless input device of notebook computer
CN101587385B (en) * 2001-09-03 2011-09-28 杨泰和 Multifunctional wireless transmitting and receiving device
JP3857566B2 (en) * 2001-10-30 2006-12-13 インターナショナル・ビジネス・マシーンズ・コーポレーション Notebook computer
JP2004038332A (en) * 2002-06-28 2004-02-05 Toshiba Corp Information processor
US8213908B2 (en) * 2007-04-05 2012-07-03 Microsoft Corporation Systems and methods for pairing bluetooth devices
US20090058707A1 (en) * 2007-08-30 2009-03-05 Speakercraft, Inc. Dual mode remote control system
US20110099507A1 (en) * 2009-10-28 2011-04-28 Google Inc. Displaying a collection of interactive elements that trigger actions directed to an item
US9542203B2 (en) * 2010-12-06 2017-01-10 Microsoft Technology Licensing, Llc Universal dock for context sensitive computing device
US20120322376A1 (en) 2011-06-14 2012-12-20 Mitel Networks Corporation Centralized Bluetooth device pairing
US8621123B2 (en) * 2011-10-06 2013-12-31 Honeywell International Inc. Device management using virtual interfaces
WO2013076625A1 (en) * 2011-11-23 2013-05-30 Koninklijke Philips Electronics N.V. Method and apparatus for configuration and control of wireless docking
KR20130127746A (en) * 2012-05-15 2013-11-25 삼성전자주식회사 Method and apparatus for controlling power consumption
WO2013181778A1 (en) 2012-06-04 2013-12-12 Qualcomm Incorporated Automatic connection of bluetooth human interface devices
TWM451588U (en) * 2012-12-07 2013-04-21 Univ Southern Taiwan Sci & Tec Touch input panel
US20140168086A1 (en) 2012-12-14 2014-06-19 Geartonomy, Inc. Split keyboard for a tablet computer
US9836084B2 (en) * 2014-03-28 2017-12-05 Intel Corporation Inferred undocking for hybrid tablet computer
US9357576B2 (en) * 2014-09-27 2016-05-31 Intel Corporation Automatic pairing for portable computing devices
US10338636B2 (en) * 2017-09-16 2019-07-02 Lenovo (Singapore) Pte. Ltd. Computing device with keyboard mode

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
US10713204B2 (en) 2020-07-14
CN109154844A (en) 2019-01-04
EP3433699A1 (en) 2019-01-30
EP3433699A4 (en) 2019-10-30
WO2018022050A1 (en) 2018-02-01
US20190138483A1 (en) 2019-05-09

Similar Documents

Publication Publication Date Title
EP3433699B1 (en) Controlling a mode of communication between a host computer and a detachable peripheral device
US10268616B2 (en) Systems and methods for selective disablement of protocols on a USB type-C port
RU2696321C2 (en) Power control contracts for auxiliary devices
US9477625B2 (en) Reversible connector for accessory devices
US10127181B2 (en) Port disconnect charging function for USB hub
TWI544337B (en) Dual-operating-system architecture for sharing usb devices, and method for sharing usb devices in a dual-operating-system architecture
KR102564469B1 (en) Method and apparatus for protecting a battery
US9678560B2 (en) Methods and apparatuses to wake computer systems from sleep states
WO2017101047A1 (en) Charging control method and device, power adapter, and mobile terminal
KR20140027875A (en) An ultra low power apparatus and method to wake up a main processor
KR102209068B1 (en) Method for reconnecting master device and slave device
EP3468256A1 (en) Fast wireless fidelity connection method and apparatus
KR20060051923A (en) Automatic activation and deactivation of wireless network adapter
TW201546621A (en) FLEXCONNECT disconnect detection
US20150169039A1 (en) Electronic Apparatus, Method and Storage Medium
CN111400080A (en) Method and device for setting shipping mode of electronic product and electronic equipment
US9468026B2 (en) Method and system for shortening wireless pairing connection time by detecting an object or body
CN111432387A (en) Many-to-many switching module, multi-machine wireless communication system and communication method thereof
US20140347279A1 (en) Keyboard device with switchable connection path and its switching method
JP6255918B2 (en) Information processing apparatus, communication control method, and communication control program
EP3044668B1 (en) Systems and methods for controlling operating modes of smart platforms
CN111201522A (en) Universal serial bus equipment and power saving method thereof
JP5514794B2 (en) Information processing system
JP2018185664A (en) Control system, electronic apparatus, and control method
JP2017054278A (en) Information processing apparatus

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20181025

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

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602016043947

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: G06F0001160000

Ipc: G06F0013400000

A4 Supplementary search report drawn up and despatched

Effective date: 20190926

RIC1 Information provided on ipc code assigned before grant

Ipc: G06F 1/16 20060101ALI20190920BHEP

Ipc: H04L 12/12 20060101ALI20190920BHEP

Ipc: G06F 13/00 20060101ALI20190920BHEP

Ipc: G06F 13/40 20060101AFI20190920BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
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: 20200608

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: AT

Ref legal event code: REF

Ref document number: 1312460

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200915

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: 602016043947

Country of ref document: DE

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: 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: 20200909

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: 20201210

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: 20200909

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: 20201209

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: 20200909

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: 20200909

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: 20201209

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1312460

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200909

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200909

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: 20200909

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: 20200909

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: 20200909

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: 20200909

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: 20200909

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: 20210111

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: 20200909

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: 20200909

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

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: 20210109

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: 20200909

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: 20200909

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: 20200909

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016043947

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: 20200909

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

26N No opposition filed

Effective date: 20210610

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

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: 20200909

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: 20200909

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: 20200909

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: 20200909

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: 20210728

Ref country code: FR

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: IE

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

Effective date: 20210728

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: 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: 20200909

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: 20160728

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

Ref country code: GB

Payment date: 20230620

Year of fee payment: 8

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

Ref country code: DE

Payment date: 20230620

Year of fee payment: 8

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: 20200909

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: 20200909