EP2717632A2 - Apparatus and method for controling power in a short-range communication device - Google Patents
Apparatus and method for controling power in a short-range communication device Download PDFInfo
- Publication number
- EP2717632A2 EP2717632A2 EP13187550.2A EP13187550A EP2717632A2 EP 2717632 A2 EP2717632 A2 EP 2717632A2 EP 13187550 A EP13187550 A EP 13187550A EP 2717632 A2 EP2717632 A2 EP 2717632A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- link key
- short
- unit
- range wireless
- portable terminal
- 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
Links
- 238000004891 communication Methods 0.000 title claims abstract description 79
- 230000006854 communication Effects 0.000 title claims abstract description 79
- 238000000034 method Methods 0.000 title claims abstract description 15
- 230000004044 response Effects 0.000 claims abstract description 15
- 230000000875 corresponding effect Effects 0.000 claims 6
- 230000001276 controlling effect Effects 0.000 claims 2
- QYPNKSZPJQQLRK-UHFFFAOYSA-N tebufenozide Chemical compound C1=CC(CC)=CC=C1C(=O)NN(C(C)(C)C)C(=O)C1=CC(C)=CC(C)=C1 QYPNKSZPJQQLRK-UHFFFAOYSA-N 0.000 claims 1
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B5/00—Near-field transmission systems, e.g. inductive or capacitive transmission systems
- H04B5/40—Near-field transmission systems, e.g. inductive or capacitive transmission systems characterised by components specially adapted for near-field transmission
- H04B5/48—Transceivers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B5/00—Near-field transmission systems, e.g. inductive or capacitive transmission systems
- H04B5/20—Near-field transmission systems, e.g. inductive or capacitive transmission systems characterised by the transmission technique; characterised by the transmission medium
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B5/00—Near-field transmission systems, e.g. inductive or capacitive transmission systems
- H04B5/70—Near-field transmission systems, e.g. inductive or capacitive transmission systems specially adapted for specific purposes
- H04B5/72—Near-field transmission systems, e.g. inductive or capacitive transmission systems specially adapted for specific purposes for local intradevice communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/24—Radio transmission systems, i.e. using radiation field for communication between two or more posts
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0492—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload by using a location-limited connection, e.g. near-field communication or limited proximity of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
- H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
- H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
-
- Y—GENERAL 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
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE 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/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present application relates to short-range wireless communication, and more particularly, to an apparatus and method for controlling power in a short-range wireless communication device.
- Portable terminals such as smart phones and tablet PCs provide a variety of useful functions to users through various applications.
- portable terminals are evolving into devices that can provide various types of information as well as voice calls by means of a number of functions.
- the functions of the portable terminals include especially a short-range wireless communication function that enables wireless communication with an external device within a short distance.
- Short-range wireless communication is conducted by Bluetooth or infrared communication.
- the term 'external device' covers a number of devices including a headset, a keyboard, a mouse, a game console, a smart TV, etc.
- a portable terminal When an external device is in power-on state, a portable terminal can attempt wireless communication with the external device. If the external device is connected wirelessly to another portable terminal, the portable terminal can attempt wireless communication with the external device after the external device releases the wireless connection from another portable terminal.
- NFC Near Field Communication
- Certain embodiments relate to an apparatus and method for receiving a link key by NFC and establishing a Bluetooth (BT) connection with a portable terminal using the received link key in a short-range wireless communication device.
- BT Bluetooth
- Certain embodiments relate to a power control apparatus in a short-range wireless communication device, in which when a second NFC unit is connected to a first NFC unit of a portable terminal by NFC, the second NFC unit transmits a link key request message requesting a link key to the first NFC unit and, upon receipt of a link key confirm message from the first NFC unit in response to the link key request message, powers on the short-range wireless communication device.
- Certain embodiments relate to an apparatus for controlling power of a short-range wireless communication device in a portable terminal, in which when a first NFC unit is connected to a second NFC unit of the short-range wireless communication device by NFC, the first NFC unit receives a link key request message from the second NFC unit and transmits a link key confirm message to the second NFC unit in response to the link key request message, and upon receipt of the link key request message from the first NFC unit, a first BT unit searches for a link key corresponding to the short-range wireless communication device in one or more pre-stored link keys and generates the link key confirm message based on a search result.
- Certain embodiments relate to a power control method in a short-range communication device, in which when the short-range wireless communication device is connected to a portable terminal by NFC, a link key request message requesting a link key is transmitted to the portable terminal, and upon receipt of a link key confirm message from the portable terminal in response to the link key request message, the short-range wireless communication device is powered on.
- Certain embodiments relate to a method for controlling power of a short-range wireless communication device in a portable terminal, in which when a portable terminal is connected to the short-range wireless communication device by NFC, a link key request message is received from the short-range wireless communication device, a link key corresponding to the short-range wireless communication device is searched for among one or more pre-stored link keys, and a link key confirm message is generated based on a search result and transmitted to the short-range wireless communication device by NFC.
- FIGURES 1 through 7 discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged wireless communication system. Reference will be made to preferred embodiments of the present disclosure with reference to the attached drawings. A detailed description of a generally known function and structure of the present disclosure will be avoided lest it should obscure the subject matter of the present invention.
- the term 'portable terminal' covers a variety of terminals including a video call phone, a portable phone, a smart phone, an International Mobile Telecommunications 2000 (IMT-2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunications System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a portable computer (e.g. a laptop or tablet), a digital camera, etc.
- IMT-2000 International Mobile Telecommunications 2000
- WCDMA Wideband Code Division Multiple Access
- UMTS Universal Mobile Telecommunications System
- PDA Personal Digital Assistant
- PMP Portable Multimedia Player
- DMB Digital Multimedia Broadcasting
- a portable computer e.g. a laptop or tablet
- a digital camera etc.
- FIG. 1 illustrates a short-range wireless communication system according to an embodiment of the present disclosure.
- the short-range wireless communication system includes a short-range wireless communication device 103 and a portable terminal 101.
- the short-range wireless communication device 103 is a device that provides a short-range wireless communication function.
- the short-range wireless communication device 103 can be any of a headset, a keyboard, a mouse, a game console, and a smart TV.
- the headset 103 provides Near Field Communication (NFC) functionality and Bluetooth (BT) functionality. When the headset 103 is in a power-off state, it can be turned on by the NFC functionality.
- NFC Near Field Communication
- BT Bluetooth
- the headset 103 when the headset 103 is connected to the portable terminal 101 1 by NFC, the headset 103 transmits a link key request (Link Key_REQ) message to the portable terminal 101 by NFC.
- the Link Key_REQ message which is used to request a link key, includes a first command requesting a link key and an Identifier (ID) of the headset 103 or the first command, the ID of the headset 103, and a BT address of the headset 103 used for Bluetooth communication with the portable terminal 101.
- ID Identifier
- the link key is a key used for a link between the headset 103 and the portable terminal 101.
- the link key is stored in memory units of the headset 103 and the portable terminal 101.
- the BT address is stored in the memory unit of the headset 103, when power-off of the headset 103 is requested.
- the ID of the headset 103 can be a Medium Access Control (MAC) address of the headset 103.
- MAC Medium Access Control
- the headset 103 receives a link key confirm (Link Key_CNF) message from the portable terminal 101 in response to the Link Key_REQ message.
- the Link Key_CNF message includes a response result for the Link Key_REQ message. If the portable terminal 101 pre-stores the link key of the headset 103, the Link Key_CNF message can include the link key of the headset 103 and a second command indicating that the portable terminal 101 pre-stores the link key of the headset 103. On the contrary, if the portable terminal 101 does not preserve the link key of the headset 103, the Link Key_CNF message can include a third command indicating the absence of the link key of the headset 103 in the portable terminal 101.
- the headset 103 powers on its BT unit for BT communication and determines whether the portable terminal 101 has the link key of the headset 103 by analyzing the Link Key_CNF message. The headset 103 makes the decision by checking the second or third command in the Link Key_CNF message.
- OOB pairing is for pairing with a specific device, for example, the portable terminal 101 in an out-of-band fashion.
- OOB pairing is defined in the Bluetooth standard and thus its description will not be provided herein.
- the headset 103 determines the presence of the link key of the headset 103 in the portable terminal 101, the headset 103 detects the link key from the Link Key_REQ message and compares the detected link key with one or more pre-stored link keys. If the detected link key is identical to any of the pre-stored link keys, the headset 103 establishes a BT connection with the portable terminal 101 using the detected link key. In contrast, if the detected key is identical to none of the pre-stored link keys, the headset 103 establishes a BT connection with the portable terminal 101 by OOB pairing.
- the portable terminal 101 provides the NFC functionality and the BT communication functionality.
- the portable terminal 101 1 powers on the headset 103 by the NFC functionality.
- the portable terminal 101 when the portable terminal 101 is connected to the headset 103 by NFC, the portable terminal 101 receives the Link Key_REQ message from the headset 103 by NFC. Then the portable terminal 101 searches for a link key corresponding to the headset 103 in its memory unit, generates the Link Key_CNF message based on the search result, and transmits the Link Key_CNF message to the headset 103. If the portable terminal 101 pre-stores the link key of the headset 103, the portable terminal 101 configures the Link Key_CNF message so as to include the detected link key and the second command indicating the presence of the link key. On the contrary, if the portable terminal 101 does not have the link key, it configures the Link Key_CNF message so as to include the third command indicating the absence of the link key.
- the portable terminal 101 upon receipt of a connection request message from the headset 103, the portable terminal 101 establishes a BT connection with the headset 103 using the detected link key and transmits a connection confirm message to the headset 103.
- the connection request message requests a BT connection setup using the detected link key and the connection confirm message indicates that the BT connection has been established using the detected link key.
- the portable terminal 101 upon receipt of an OOB pairing request message from the headset 103, the portable terminal 101 establishes a BT connection with the headset 103 by OOB pairing.
- FIG. 2 is a block diagram of the portable terminal according to an embodiment of the present disclosure.
- the portable terminal 101 includes a first NFC unit 201, a first BT unit 203, and a first memory unit 205.
- the first memory unit 205 includes a program memory and a data memory.
- the program memory stores a boot program and Operating System (OS) for controlling general operations of the portable terminal 101 and the data memory stores data generated during operations of the portable terminal 101.
- the first memory unit 205 pre-stores a plurality of link keys for a plurality of BT devices to which the portable terminal 103 was connected by BT.
- OS Operating System
- a link key is generated and stored in the memory units of the headset 103 and the portable terminal 101.
- the memory unit 205 can store the following link keys listed in (Table 1).
- Table 1 BT Device Link Key ID of 1 st BT device xxxx ID of 2 nd BT device yyyy
- the first NFC unit 201 provides the NFC functionality. Because the first NFC unit 201 operates using induced current, there is no need for supplying operation power to the first NFC unit 201. Particularly, the first NFC unit 201 monitors setup of an NFC connection to the headset 103. Upon setup of an NFC connection to the headset 103, the first NFC unit 201 determines whether a Link Key_REQ message has been received from the headset 103. Upon receipt of the Link Key_REQ message from the headset 103, the first NFC unit 201 transmits the Link Key_REQ message to the first BT unit 203.
- the first NFC unit 201 receives a Link Key_CNF message from the first BT unit 203 in response to the Link Key_REQ message and transmits the Link Key_CNF message to the headset 130 by NFC.
- the first BT unit 203 detects the ID of the headset 103 by analyzing the Link Key_REQ message and searches for a link key corresponding to the detected ID of the headset 103 among one or more pre-stored link keys corresponding to BT device IDs. Upon detection of the link key corresponding to the ID of the headset 103, the first BT unit 203 generates a Link Key_CNF message including the detected link key and the second command indicating the presence of the link key of the headset 103 in the portable terminal 101. On the other hand, if the link key corresponding to the ID of the headset 103 has not been detected, the first BT unit 203 generates a Link Key_CNF message including the third command indicating the absence of the link key of the headset 103 in the portable terminal 101.
- the first BT unit 203 determines whether a connection request message has been received from the headset 103 by BT communication.
- the connection request message requests setup of a BT connection using the detected link key.
- the first BT unit 203 establishes a BT connection with the headset 103 using the detected link key and transmits a connection confirm message to the first NFC unit 201.
- the connection confirm message indicates that the portable terminal 101 1 has established a BT connection using the detected link key.
- the first BT unit 203 determines whether an OOB pairing request message has been received. Upon receipt of the OOB pairing request message, the first BT unit 203 establishes a BT connection with the headset 103 by OOB pairing.
- FIG. 3 is a block diagram of the headset according to an embodiment of the present disclosure.
- the headset 103 includes a second NFC unit 301, a second BT unit 303, and a second memory unit 305.
- the second memory unit 305 pre-stores the ID and BT address of the headset 193 and one or more link keys.
- a link key is stored in the memory units 305 and 205 of the headset 103 and the portable terminal 101.
- the BT address of the headset 103 is stored in the second memory unit 305.
- the second NFC unit 301 provides the NFC functionality. Because the second NFC unit 301 operates using induced current, there is no need for supplying operation power to the second NFC unit 301. Particularly, the second NFC unit 301 monitors setup of an NFC connection to the portable terminal 101. Upon setup of an NFC connection to the portable terminal 101, the second NFC unit 301 generates a Link Key_REQ message and transmits the Link Key_REQ message to the portable terminal 101 by NFC.
- the second NFC unit 301 can detect the ID of the headset 103 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID and the first command requesting a link key. Or the second NFC unit 301 can detect the ID and BT address of the headset 103 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID, the detected BT address, and the first command.
- the second NFC unit 301 receives a Link Key_CNF message in response to the Link Key_REQ message.
- the Link Key_CNF message includes a response result for the Link Key_REQ message. If the portable terminal 101 pre-stores a link key related to the headset 103, the Link Key_CNF message can include the link key and the second command indicating the presence of the link key of the headset 103 in the portable terminal 101. On the other hand, if the portable terminal 101 does not have the link key of the headset 103, the Link Key_CNF message can include the third command indicating the absence of the link key of the headset 103 in the portable terminal 101.
- the second NFC unit 301 transmits a power-on request message to the second BT unit 303 to turn on the second BT unit 303.
- the second NFC unit 301 transmits the received Link Key_CNF message to the second BT unit 303.
- the second NFC unit 301 turns on the second BT unit 303 by transmitting the power-on request message to a power supply (not shown) of the second BT unit 303.
- the second BT unit 303 provides the BT functionality and is placed in power-off state. Especially when the second BT unit 303 is powered on by the power-on request message received from the second NFC unit 301, the second BT unit 303 activates the BT functionality.
- the second BT unit 303 receives the Link Key_CNF message from the second NFC unit 301 and determines whether the portable terminal 101 pre-stores the link key of the head set 103 by analyzing the Link Key_CNF message. Specifically, the second BT unit 303 determines whether the portable terminal 101 preserves the link key of the headset 103 by checking the second or third command in the Link Key_CNF message. If the second BT unit 303 determines that the portable terminal 101 does not preserve the link key of the headset 103, the second NT unit 303 establishes a BT connection with the portable terminal by OOB pairing.
- the second BT unit 303 determines that the portable terminal 101 pre-stores the link key of the headset 103, the second BT unit 303 detects the link key from the Link Key_CNF message and compares the detected link key with pre-stored one or more link keys. If the detected link key is identical to any of the pre-stored link keys, the second BT unit 303 establishes a BT connection with the portable terminal 101 using the detected link key. The second BT unit 303 transmits a connection request message and receives a connection confirm message in response to the connection request message.
- the connection request message requests setup of a BT connection using the pre-stored link key of the headset 103.
- the connection confirm message indicates that the portable terminal 101 1 has established a BT connection using the pre-stored link key of the headset 103.
- the second BT unit 303 establishes a BT connection with the portable terminal 101 by OOB pairing.
- FIG. 4 is a flowchart illustrating a power control operation in the short-range wireless communication system according to an embodiment of the present disclosure.
- the second NFC unit 301 is connected to the first NFC unit 201 by NFC in block 401.
- the second NFC unit 301 generates a Link Key_REQ message and transmits the Link Key_REQ message to the first NFC unit 201.
- the second NFC unit 301 can detect the ID of the headset 130 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID of the headset 103 and the first command requesting a link key.
- the second NFC unit 301 can detect the ID and BT address of the headset 130 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID and BT address of the headset 103 and the first command.
- the first NFC unit 201 receives the Link Key_REQ message and transmits the received Link Key_REQ message to the first BT unit 203 in block 405.
- the first BT unit 203 searches for a link key based on the Link Key_REQ message received from the first NFC unit 201 and generates a Link Key_CNF message based on a search result.
- the first BT unit 203 detects the ID of the headset 130 from the Link Key_REQ message by analyzing the Link Key_REQ message and searches for a link key corresponding to the ID of the headset 130 among link keys pre-stored in the first memory unit 205. If the first BT unit 203 detects the link key corresponding to the ID of the headset 103 in the first memory unit 205, the first BT unit 203 generates a Link Key_CNF message including the detected link key and the second command indicating that the portable terminal 101 pre-stores the link key of the headset 130.
- the first BT unit 203 fails in detecting the link key corresponding to the ID of the headset 103 in the first memory unit 205, the first BT unit 203 generates a Link Key_CNF message including the third command that the portable terminal 101 does not have the link key of the headset 103.
- the first BT unit 203 transmits the Link Key_CNF message to the first NFC unit 201 in block 409 and the first NFC unit 201 transmits the received Link Key_CNF message to the second NFC unit 301 by NFC in block 411.
- the second NFC unit 301 Upon receipt of the Link Key_CNF message from the first NFC unit 201 by NFC, the second NFC unit 301 powers on the second BT unit 303 by transmitting a power-on request message to the second BT unit 303 in block 413. Particularly, the second NFC unit 301 transmits the power-on request message to the power supply (not shown) of the second BT unit 303, thereby powering on the second BT unit 303.
- the second BT unit 303 activates its BT functionality.
- the second NFC unit 301 transmits the received Link Key_CNF message to the second BT unit 303 in block 417 and the second BT unit 303 determines whether the portable terminal 101 pre-stores the link key of the headset 103 by analyzing the Link Key_CNF message in block 419.
- the second BT unit 303 determines whether the link key has been received in the Link Key_CNF message by checking the second or third command included in the Link Key_CNF message. For example, in the presence of the second command in the Link Key_CNF message, the second BT unit 303 can determine that the link key has been received. In another example, if the Link Key_CNF message includes the third command, the second BT unit 303 can determine that the link key has not been received.
- the second BT unit 303 goes to block 425 and otherwise, the second BT unit 303 goes to block 423.
- the second BT unit 303 establishes a BT connection with the portable terminal 101 by OOB pairing.
- the second BT unit 303 detects the link key in the Link Key_CNF message and compares the detected link key with one or more pre-stored link keys. If the detected link key is identical to any of the pre-stored link keys, the second BT unit 303 proceeds to block 429 and otherwise, it returns to block 423.
- the second BT unit 303 transmits a connection request message to the first BT unit 203 by BT communication in block 429.
- the connection request message requests setup of a BT connection using the pre-stored link key of the headset 103.
- the first BT unit 203 Upon receipt of the connection request message, the first BT unit 203 establishes a BT connection with the headset 103 using the detected link key and transmits a connection confirm message to the second BT unit 201 in block 431.
- the connection confirm message indicates that the portable terminal 101 has established a BT connection using the pre-stored link key of the headset 103.
- FIG. 5 illustrates a power control operation of the headset according to an embodiment of the present disclosure.
- the headset 103 is connected to the portable terminal 101 by NFC in block 501.
- the headset 103 generates a Link Key_REQ message and transmits the Link Key_REQ message to the portable terminal 101 by NFC.
- the headset 103 can detect the ID of the headset 130 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID of the headset 103 and the first command requesting a link key.
- the headset 103 can detect the ID and BT address of the headset 130 from the second memory unit 305 and generate a Link Key_REQ message including the detected ID and BT address of the headset 103 and the first command.
- the headset 103 determines whether a Link Key_CNF message has been received from the portable terminal 101 by NFC. Upon receipt of the Link Key_CNF message from the portable terminal 101, the headset 103 proceeds to block 507 and otherwise, the headset 103 repeats block 505.
- the Link Key_CNF message includes a response result for the Link Key_REQ message. If the portable terminal 101 stores a link key related to the headset 103, the Link Key_CNF message can include the second command indicating the presence of the link key of the headset 103 in the portable terminal 101. On the contrary, if the portable terminal 101 does not store the link key of the headset 103, the Link Key_CNF message can include the third command indicating the absence of the link key of the headset 103 in the portable terminal 101.
- the headset 103 powers on the second BT unit 303 and activates its BT functionality.
- the headset 103 analyses the received Link Key_CNF message in block 509 and determines whether the link key has been received in the Link Key_CNF message in block 511.
- the headset 103 determines whether the link key has been received in the Link Key_CNF message by checking the second or third command included in the Link Key_CNF message. For example, in the presence of the second command in the Link Key_CNF message, the headset 103 can determine that the link key has been received. In another example, if the Link Key_CNF message includes the third command, the headset 103 can determine that the link key has not been received.
- the headset 103 establishes a BT connection with the portable terminal 101 by OOB pairing.
- the headset 103 detects the link key in the Link Key_CNF message and compares the detected link key with one or more pre-stored link keys. The headset 103 determines whether the detected link key is identical to any of the pre-stored link keys in block 517. If the detected link key is identical to any of the pre-stored link keys, the headset 103 proceeds to block 519 and otherwise, it goes to block 513.
- the headset 103 transmits a connection request message to the portable terminal 101 by BT communication in block 519.
- the connection request message requests setup of a BT connection using the pre-stored link key of the headset 103.
- the headset 103 receives a connection confirm message from the portable terminal 101 by BT communication in block 521.
- the connection confirm message indicates that the portable terminal 101 has established a BT connection using the pre-stored link key of the headset 103.
- FIG. 6 illustrates an operation for controlling the power of the headset at the portable terminal according to an embodiment of the present disclosure.
- the portable terminal 101 is connected to the headset 103 by NFC in block 601.
- the portable terminal 101 determines whether a Link Key_REQ message has been received from the headset 103 by NFC.
- the Link Key_REQ message is a message requesting a link key.
- the Link Key_REQ message can include the ID of the headset 103 and the first command requesting a link key or the ID and BT address of the headset 103 and the first command.
- the portable terminal 101 1 Upon receipt of the Link Key_REQ message, the portable terminal 101 1 goes to block 605 and otherwise, it repeats block 603. The portable terminal 101 searches for a link key based on the Link Key_REQ message received from the headset 103 in block 605 and generates a Link Key_CNF message based on a search result in block 607.
- the portable terminal 103 detects the ID of the headset 130 from the Link Key_REQ message by analyzing the received Link Key_REQ message, and searches for a link key corresponding to the ID of the headset 130 among link keys pre-stored in the first memory unit 205. If the link key corresponding to the ID of the headset 103 is detected from the first memory unit 205, the portable terminal 101 generates a Link Key_CNF message including the detected link key and the second command indicating that the portable terminal 101 pre-stores the link key of the headset 130.
- the portable terminal 101 If the link key corresponding to the ID of the headset 103 is not detected from the first memory unit 205, the portable terminal 101 generates a Link Key_CNF message including the third command that the portable terminal 101 does not store the link key of the headset 103.
- the portable terminal 101 determines whether a connection request message has been received from the headset 103 by BT communication in block 609.
- the connection request message requests setup of a BT connection using the pre-stored link key of the headset 103.
- the portable terminal 101 Upon receipt of the connection request message, the portable terminal 101 goes to block 611 and otherwise, it goes to block 615.
- the portable terminal 101 establishes a BT connection with the headset 103 using the detected link key in block 611.
- the portable terminal 101 generates a connection confirm message and transmits the connection confirm message to the headset 103 by BT communication.
- the connection confirm message indicates that the portable terminal 101 has established a BT connection using the detected link key.
- the portable terminal 101 monitors receipt of an OOB pairing request message. Upon the OOB pairing request message, the portable terminal 101 goes to block 617 and otherwise, the portable terminal 101 ends communication with the headset 103. In block 617, the portable terminal 101 establishes a BT connection with the headset 103 by OOB pairing.
- FIG. 7 illustrates a headset that is powered on according to an embodiment of the present disclosure.
- the headset 703 is powered on as indicated by reference numeral 705.
- the headset 703 transmits a Link Key_REQ message to the portable terminal 701 by NFC and receives a Link Key_CNF message from the portable terminal 701 by NFC in response to the Link Key_REQ message.
- the headset 703 is placed in the power-on state 705 and establishes a BT connection with the portable terminal 701 using a link key included in the Link Key_CNF message.
- a short-range wireless communication device is powered on by NFC, thus increasing user convenience.
- the short-range wireless communication device receives a link key by NFC and establishes a BT connection with a portable terminal using the received link key. Therefore, user convenience is further increased.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
- Selective Calling Equipment (AREA)
Abstract
Description
- The present application relates to short-range wireless communication, and more particularly, to an apparatus and method for controlling power in a short-range wireless communication device.
- Portable terminals such as smart phones and tablet PCs provide a variety of useful functions to users through various applications. Thus portable terminals are evolving into devices that can provide various types of information as well as voice calls by means of a number of functions. The functions of the portable terminals include especially a short-range wireless communication function that enables wireless communication with an external device within a short distance.
- Short-range wireless communication is conducted by Bluetooth or infrared communication. The term 'external device' covers a number of devices including a headset, a keyboard, a mouse, a game console, a smart TV, etc.
- When an external device is in power-on state, a portable terminal can attempt wireless communication with the external device. If the external device is connected wirelessly to another portable terminal, the portable terminal can attempt wireless communication with the external device after the external device releases the wireless connection from another portable terminal.
- To address the above-discussed deficiencies of the related art, it is a primary object to provide an apparatus and method for powering on by Near Field Communication (NFC) in a short-range wireless communication device.
- Certain embodiments relate to an apparatus and method for receiving a link key by NFC and establishing a Bluetooth (BT) connection with a portable terminal using the received link key in a short-range wireless communication device.
- Certain embodiments relate to a power control apparatus in a short-range wireless communication device, in which when a second NFC unit is connected to a first NFC unit of a portable terminal by NFC, the second NFC unit transmits a link key request message requesting a link key to the first NFC unit and, upon receipt of a link key confirm message from the first NFC unit in response to the link key request message, powers on the short-range wireless communication device.
- Certain embodiments relate to an apparatus for controlling power of a short-range wireless communication device in a portable terminal, in which when a first NFC unit is connected to a second NFC unit of the short-range wireless communication device by NFC, the first NFC unit receives a link key request message from the second NFC unit and transmits a link key confirm message to the second NFC unit in response to the link key request message, and upon receipt of the link key request message from the first NFC unit, a first BT unit searches for a link key corresponding to the short-range wireless communication device in one or more pre-stored link keys and generates the link key confirm message based on a search result.
- Certain embodiments relate to a power control method in a short-range communication device, in which when the short-range wireless communication device is connected to a portable terminal by NFC, a link key request message requesting a link key is transmitted to the portable terminal, and upon receipt of a link key confirm message from the portable terminal in response to the link key request message, the short-range wireless communication device is powered on.
- Certain embodiments relate to a method for controlling power of a short-range wireless communication device in a portable terminal, in which when a portable terminal is connected to the short-range wireless communication device by NFC, a link key request message is received from the short-range wireless communication device, a link key corresponding to the short-range wireless communication device is searched for among one or more pre-stored link keys, and a link key confirm message is generated based on a search result and transmitted to the short-range wireless communication device by NFC.
- Before undertaking the DETAILED DESCRIPTION below, it may be advantageous to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or," is inclusive, meaning and/or; the phrases "associated with" and "associated therewith," as well as derivatives thereof, may mean to include, be included within, interconnect with, contain, be contained within, connect to or with, couple to or with, be communicable with, cooperate with, interleave, juxtapose, be proximate to, be bound to or with, have, have a property of, or the like; and the term "controller" means any device, system or part thereof that controls at least one operation, such a device may be implemented in hardware, firmware or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely. Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
- For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:
-
FIG. 1 illustrates a short-range wireless communication system according to an embodiment of the present disclosure; -
FIG. 2 is a block diagram of a portable terminal according to an embodiment of the present disclosure; -
FIG. 3 is a block diagram of a headset according to an embodiment of the present disclosure; -
FIG. 4 illustrates a power control operation in the wireless communication system according to an embodiment of the present disclosure; -
FIG. 5 illustrates a power control operation in the headset according to an embodiment of the present disclosure; -
FIG. 6 illustrates an operation for controlling the power of the headset at the portable terminal according to an embodiment of the present disclosure; and -
FIG. 7 illustrates a headset that is powered on according to an embodiment of the present disclosure. - Throughout the drawings, the same drawing reference numerals will be understood to refer to the same elements, features and structures.
-
FIGURES 1 through 7 , discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged wireless communication system. Reference will be made to preferred embodiments of the present disclosure with reference to the attached drawings. A detailed description of a generally known function and structure of the present disclosure will be avoided lest it should obscure the subject matter of the present invention. - In accordance with certain embodiments of the present disclosure, the term 'portable terminal' covers a variety of terminals including a video call phone, a portable phone, a smart phone, an International Mobile Telecommunications 2000 (IMT-2000) terminal, a Wideband Code Division Multiple Access (WCDMA) terminal, a Universal Mobile Telecommunications System (UMTS) terminal, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a Digital Multimedia Broadcasting (DMB) terminal, an e-book reader, a portable computer (e.g. a laptop or tablet), a digital camera, etc.
-
FIG. 1 illustrates a short-range wireless communication system according to an embodiment of the present disclosure. - Referring to
FIG. 1 , the short-range wireless communication system includes a short-rangewireless communication device 103 and aportable terminal 101. The short-rangewireless communication device 103 is a device that provides a short-range wireless communication function. For example, the short-rangewireless communication device 103 can be any of a headset, a keyboard, a mouse, a game console, and a smart TV. - The
headset 103 provides Near Field Communication (NFC) functionality and Bluetooth (BT) functionality. When theheadset 103 is in a power-off state, it can be turned on by the NFC functionality. - Specifically, when the
headset 103 is connected to theportable terminal 101 1 by NFC, theheadset 103 transmits a link key request (Link Key_REQ) message to theportable terminal 101 by NFC. The Link Key_REQ message, which is used to request a link key, includes a first command requesting a link key and an Identifier (ID) of theheadset 103 or the first command, the ID of theheadset 103, and a BT address of theheadset 103 used for Bluetooth communication with theportable terminal 101. - The link key is a key used for a link between the
headset 103 and theportable terminal 101. When theheadset 103 is paired with theportable terminal 101, the link key is stored in memory units of theheadset 103 and theportable terminal 101. The BT address is stored in the memory unit of theheadset 103, when power-off of theheadset 103 is requested. The ID of theheadset 103 can be a Medium Access Control (MAC) address of theheadset 103. - The
headset 103 receives a link key confirm (Link Key_CNF) message from theportable terminal 101 in response to the Link Key_REQ message. The Link Key_CNF message includes a response result for the Link Key_REQ message. If theportable terminal 101 pre-stores the link key of theheadset 103, the Link Key_CNF message can include the link key of theheadset 103 and a second command indicating that theportable terminal 101 pre-stores the link key of theheadset 103. On the contrary, if theportable terminal 101 does not preserve the link key of theheadset 103, the Link Key_CNF message can include a third command indicating the absence of the link key of theheadset 103 in theportable terminal 101. - The
headset 103 powers on its BT unit for BT communication and determines whether theportable terminal 101 has the link key of theheadset 103 by analyzing the Link Key_CNF message. Theheadset 103 makes the decision by checking the second or third command in the Link Key_CNF message. - If the
headset 103 determines the absence of the link key in theportable terminal 101, theheadset 103 establishes a BT connection with theportable terminal 101 in an Out Of Band (OOB) pairing. OOB pairing is for pairing with a specific device, for example, theportable terminal 101 in an out-of-band fashion. OOB pairing is defined in the Bluetooth standard and thus its description will not be provided herein. - On the other hand, if the
headset 103 determines the presence of the link key of theheadset 103 in theportable terminal 101, theheadset 103 detects the link key from the Link Key_REQ message and compares the detected link key with one or more pre-stored link keys. If the detected link key is identical to any of the pre-stored link keys, theheadset 103 establishes a BT connection with theportable terminal 101 using the detected link key. In contrast, if the detected key is identical to none of the pre-stored link keys, theheadset 103 establishes a BT connection with theportable terminal 101 by OOB pairing. - The
portable terminal 101 provides the NFC functionality and the BT communication functionality. When theheadset 103 is powered off, theportable terminal 101 1 powers on theheadset 103 by the NFC functionality. - To be more specific, when the
portable terminal 101 is connected to theheadset 103 by NFC, theportable terminal 101 receives the Link Key_REQ message from theheadset 103 by NFC. Then theportable terminal 101 searches for a link key corresponding to theheadset 103 in its memory unit, generates the Link Key_CNF message based on the search result, and transmits the Link Key_CNF message to theheadset 103. If theportable terminal 101 pre-stores the link key of theheadset 103, theportable terminal 101 configures the Link Key_CNF message so as to include the detected link key and the second command indicating the presence of the link key. On the contrary, if theportable terminal 101 does not have the link key, it configures the Link Key_CNF message so as to include the third command indicating the absence of the link key. - Subsequently, upon receipt of a connection request message from the
headset 103, theportable terminal 101 establishes a BT connection with theheadset 103 using the detected link key and transmits a connection confirm message to theheadset 103. The connection request message requests a BT connection setup using the detected link key and the connection confirm message indicates that the BT connection has been established using the detected link key. On the other hand, upon receipt of an OOB pairing request message from theheadset 103, theportable terminal 101 establishes a BT connection with theheadset 103 by OOB pairing. -
FIG. 2 is a block diagram of the portable terminal according to an embodiment of the present disclosure. Referring toFIG. 2 , theportable terminal 101 includes afirst NFC unit 201, afirst BT unit 203, and afirst memory unit 205. Thefirst memory unit 205 includes a program memory and a data memory. The program memory stores a boot program and Operating System (OS) for controlling general operations of theportable terminal 101 and the data memory stores data generated during operations of theportable terminal 101. Especially, thefirst memory unit 205 pre-stores a plurality of link keys for a plurality of BT devices to which theportable terminal 103 was connected by BT. When theheadset 103 and theportable terminal 101 are paired with each other, a link key is generated and stored in the memory units of theheadset 103 and theportable terminal 101. For example, thememory unit 205 can store the following link keys listed in (Table 1).(Table 1) BT Device Link Key ID of 1st BT device xxxx ID of 2nd BT device yyyy - The
first NFC unit 201 provides the NFC functionality. Because thefirst NFC unit 201 operates using induced current, there is no need for supplying operation power to thefirst NFC unit 201. Particularly, thefirst NFC unit 201 monitors setup of an NFC connection to theheadset 103. Upon setup of an NFC connection to theheadset 103, thefirst NFC unit 201 determines whether a Link Key_REQ message has been received from theheadset 103. Upon receipt of the Link Key_REQ message from theheadset 103, thefirst NFC unit 201 transmits the Link Key_REQ message to thefirst BT unit 203. - The
first NFC unit 201 receives a Link Key_CNF message from thefirst BT unit 203 in response to the Link Key_REQ message and transmits the Link Key_CNF message to the headset 130 by NFC. - The
first BT unit 203 detects the ID of theheadset 103 by analyzing the Link Key_REQ message and searches for a link key corresponding to the detected ID of theheadset 103 among one or more pre-stored link keys corresponding to BT device IDs. Upon detection of the link key corresponding to the ID of theheadset 103, thefirst BT unit 203 generates a Link Key_CNF message including the detected link key and the second command indicating the presence of the link key of theheadset 103 in theportable terminal 101. On the other hand, if the link key corresponding to the ID of theheadset 103 has not been detected, thefirst BT unit 203 generates a Link Key_CNF message including the third command indicating the absence of the link key of theheadset 103 in theportable terminal 101. - The
first BT unit 203 determines whether a connection request message has been received from theheadset 103 by BT communication. The connection request message requests setup of a BT connection using the detected link key. Upon receipt of the connection request message, thefirst BT unit 203 establishes a BT connection with theheadset 103 using the detected link key and transmits a connection confirm message to thefirst NFC unit 201. The connection confirm message indicates that theportable terminal 101 1 has established a BT connection using the detected link key. - If the
first BT unit 203 has not received the connection request message, it determines whether an OOB pairing request message has been received. Upon receipt of the OOB pairing request message, thefirst BT unit 203 establishes a BT connection with theheadset 103 by OOB pairing. -
FIG. 3 is a block diagram of the headset according to an embodiment of the present disclosure. Referring toFIG. 3 , theheadset 103 includes asecond NFC unit 301, asecond BT unit 303, and asecond memory unit 305. Thesecond memory unit 305 pre-stores the ID and BT address of the headset 193 and one or more link keys. When theheadset 103 is paired with theportable terminal 101, a link key is stored in thememory units headset 103 and theportable terminal 101. When power-off of theheadset 103 is requested, the BT address of theheadset 103 is stored in thesecond memory unit 305. - The
second NFC unit 301 provides the NFC functionality. Because thesecond NFC unit 301 operates using induced current, there is no need for supplying operation power to thesecond NFC unit 301. Particularly, thesecond NFC unit 301 monitors setup of an NFC connection to theportable terminal 101. Upon setup of an NFC connection to theportable terminal 101, thesecond NFC unit 301 generates a Link Key_REQ message and transmits the Link Key_REQ message to theportable terminal 101 by NFC. - The
second NFC unit 301 can detect the ID of theheadset 103 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID and the first command requesting a link key. Or thesecond NFC unit 301 can detect the ID and BT address of theheadset 103 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID, the detected BT address, and the first command. - The
second NFC unit 301 receives a Link Key_CNF message in response to the Link Key_REQ message. The Link Key_CNF message includes a response result for the Link Key_REQ message. If theportable terminal 101 pre-stores a link key related to theheadset 103, the Link Key_CNF message can include the link key and the second command indicating the presence of the link key of theheadset 103 in theportable terminal 101. On the other hand, if theportable terminal 101 does not have the link key of theheadset 103, the Link Key_CNF message can include the third command indicating the absence of the link key of theheadset 103 in theportable terminal 101. - The
second NFC unit 301 transmits a power-on request message to thesecond BT unit 303 to turn on thesecond BT unit 303. After thesecond BT unit 303 is activated, thesecond NFC unit 301 transmits the received Link Key_CNF message to thesecond BT unit 303. Herein, thesecond NFC unit 301 turns on thesecond BT unit 303 by transmitting the power-on request message to a power supply (not shown) of thesecond BT unit 303. - The
second BT unit 303 provides the BT functionality and is placed in power-off state. Especially when thesecond BT unit 303 is powered on by the power-on request message received from thesecond NFC unit 301, thesecond BT unit 303 activates the BT functionality. Thesecond BT unit 303 receives the Link Key_CNF message from thesecond NFC unit 301 and determines whether theportable terminal 101 pre-stores the link key of the head set 103 by analyzing the Link Key_CNF message. Specifically, thesecond BT unit 303 determines whether theportable terminal 101 preserves the link key of theheadset 103 by checking the second or third command in the Link Key_CNF message. If thesecond BT unit 303 determines that theportable terminal 101 does not preserve the link key of theheadset 103, thesecond NT unit 303 establishes a BT connection with the portable terminal by OOB pairing. - On the other hand, if the
second BT unit 303 determines that theportable terminal 101 pre-stores the link key of theheadset 103, thesecond BT unit 303 detects the link key from the Link Key_CNF message and compares the detected link key with pre-stored one or more link keys. If the detected link key is identical to any of the pre-stored link keys, thesecond BT unit 303 establishes a BT connection with theportable terminal 101 using the detected link key. Thesecond BT unit 303 transmits a connection request message and receives a connection confirm message in response to the connection request message. - The connection request message requests setup of a BT connection using the pre-stored link key of the
headset 103. The connection confirm message indicates that theportable terminal 101 1 has established a BT connection using the pre-stored link key of theheadset 103. - If the detected key is identical to none of the pre-stored link keys, the
second BT unit 303 establishes a BT connection with theportable terminal 101 by OOB pairing. -
FIG. 4 is a flowchart illustrating a power control operation in the short-range wireless communication system according to an embodiment of the present disclosure. - Referring to
FIG. 4 , thesecond NFC unit 301 is connected to thefirst NFC unit 201 by NFC inblock 401. Inblock 403, thesecond NFC unit 301 generates a Link Key_REQ message and transmits the Link Key_REQ message to thefirst NFC unit 201. Specifically, thesecond NFC unit 301 can detect the ID of the headset 130 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID of theheadset 103 and the first command requesting a link key. Alternatively, thesecond NFC unit 301 can detect the ID and BT address of the headset 130 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID and BT address of theheadset 103 and the first command. - The
first NFC unit 201 receives the Link Key_REQ message and transmits the received Link Key_REQ message to thefirst BT unit 203 inblock 405. Inblock 407, thefirst BT unit 203 searches for a link key based on the Link Key_REQ message received from thefirst NFC unit 201 and generates a Link Key_CNF message based on a search result. - Specifically, the
first BT unit 203 detects the ID of the headset 130 from the Link Key_REQ message by analyzing the Link Key_REQ message and searches for a link key corresponding to the ID of the headset 130 among link keys pre-stored in thefirst memory unit 205. If thefirst BT unit 203 detects the link key corresponding to the ID of theheadset 103 in thefirst memory unit 205, thefirst BT unit 203 generates a Link Key_CNF message including the detected link key and the second command indicating that theportable terminal 101 pre-stores the link key of the headset 130. On the contrary, if thefirst BT unit 203 fails in detecting the link key corresponding to the ID of theheadset 103 in thefirst memory unit 205, thefirst BT unit 203 generates a Link Key_CNF message including the third command that theportable terminal 101 does not have the link key of theheadset 103. - The
first BT unit 203 transmits the Link Key_CNF message to thefirst NFC unit 201 inblock 409 and thefirst NFC unit 201 transmits the received Link Key_CNF message to thesecond NFC unit 301 by NFC inblock 411. - Upon receipt of the Link Key_CNF message from the
first NFC unit 201 by NFC, thesecond NFC unit 301 powers on thesecond BT unit 303 by transmitting a power-on request message to thesecond BT unit 303 inblock 413. Particularly, thesecond NFC unit 301 transmits the power-on request message to the power supply (not shown) of thesecond BT unit 303, thereby powering on thesecond BT unit 303. - In
block 415, upon power-on, thesecond BT unit 303 activates its BT functionality. Thesecond NFC unit 301 transmits the received Link Key_CNF message to thesecond BT unit 303 inblock 417 and thesecond BT unit 303 determines whether theportable terminal 101 pre-stores the link key of theheadset 103 by analyzing the Link Key_CNF message inblock 419. - Specifically, the
second BT unit 303 determines whether the link key has been received in the Link Key_CNF message by checking the second or third command included in the Link Key_CNF message. For example, in the presence of the second command in the Link Key_CNF message, thesecond BT unit 303 can determine that the link key has been received. In another example, if the Link Key_CNF message includes the third command, thesecond BT unit 303 can determine that the link key has not been received. - If determining that the link key has been received, the
second BT unit 303 goes to block 425 and otherwise, thesecond BT unit 303 goes to block 423. - In
block 423, thesecond BT unit 303 establishes a BT connection with theportable terminal 101 by OOB pairing. On the other hand, inblock 425, thesecond BT unit 303 detects the link key in the Link Key_CNF message and compares the detected link key with one or more pre-stored link keys. If the detected link key is identical to any of the pre-stored link keys, thesecond BT unit 303 proceeds to block 429 and otherwise, it returns to block 423. - The
second BT unit 303 transmits a connection request message to thefirst BT unit 203 by BT communication inblock 429. The connection request message requests setup of a BT connection using the pre-stored link key of theheadset 103. - Upon receipt of the connection request message, the
first BT unit 203 establishes a BT connection with theheadset 103 using the detected link key and transmits a connection confirm message to thesecond BT unit 201 inblock 431. The connection confirm message indicates that theportable terminal 101 has established a BT connection using the pre-stored link key of theheadset 103. -
FIG. 5 illustrates a power control operation of the headset according to an embodiment of the present disclosure. Referring toFIG. 5 , theheadset 103 is connected to theportable terminal 101 by NFC inblock 501. Inblock 503, theheadset 103 generates a Link Key_REQ message and transmits the Link Key_REQ message to theportable terminal 101 by NFC. Specifically, theheadset 103 can detect the ID of the headset 130 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID of theheadset 103 and the first command requesting a link key. Alternatively, theheadset 103 can detect the ID and BT address of the headset 130 from thesecond memory unit 305 and generate a Link Key_REQ message including the detected ID and BT address of theheadset 103 and the first command. - In
block 505, theheadset 103 determines whether a Link Key_CNF message has been received from theportable terminal 101 by NFC. Upon receipt of the Link Key_CNF message from theportable terminal 101, theheadset 103 proceeds to block 507 and otherwise, theheadset 103 repeats block 505. - The Link Key_CNF message includes a response result for the Link Key_REQ message. If the
portable terminal 101 stores a link key related to theheadset 103, the Link Key_CNF message can include the second command indicating the presence of the link key of theheadset 103 in theportable terminal 101. On the contrary, if theportable terminal 101 does not store the link key of theheadset 103, the Link Key_CNF message can include the third command indicating the absence of the link key of theheadset 103 in theportable terminal 101. - In
block 507, theheadset 103 powers on thesecond BT unit 303 and activates its BT functionality. Theheadset 103 analyses the received Link Key_CNF message inblock 509 and determines whether the link key has been received in the Link Key_CNF message inblock 511. - If determining that the link key has been received, the
headset 103 goes to block 515 and otherwise, thesecond BT unit 303 goes to block 513. Herein, theheadset 103 determines whether the link key has been received in the Link Key_CNF message by checking the second or third command included in the Link Key_CNF message. For example, in the presence of the second command in the Link Key_CNF message, theheadset 103 can determine that the link key has been received. In another example, if the Link Key_CNF message includes the third command, theheadset 103 can determine that the link key has not been received. - In
block 513, theheadset 103 establishes a BT connection with theportable terminal 101 by OOB pairing. On the other hand, inblock 515, theheadset 103 detects the link key in the Link Key_CNF message and compares the detected link key with one or more pre-stored link keys. Theheadset 103 determines whether the detected link key is identical to any of the pre-stored link keys inblock 517. If the detected link key is identical to any of the pre-stored link keys, theheadset 103 proceeds to block 519 and otherwise, it goes to block 513. - The
headset 103 transmits a connection request message to theportable terminal 101 by BT communication inblock 519. The connection request message requests setup of a BT connection using the pre-stored link key of theheadset 103. - The
headset 103 receives a connection confirm message from theportable terminal 101 by BT communication inblock 521. The connection confirm message indicates that theportable terminal 101 has established a BT connection using the pre-stored link key of theheadset 103. -
FIG. 6 illustrates an operation for controlling the power of the headset at the portable terminal according to an embodiment of the present disclosure. Referring toFIG. 6 , theportable terminal 101 is connected to theheadset 103 by NFC inblock 601. Inblock 603, theportable terminal 101 determines whether a Link Key_REQ message has been received from theheadset 103 by NFC. The Link Key_REQ message is a message requesting a link key. The Link Key_REQ message can include the ID of theheadset 103 and the first command requesting a link key or the ID and BT address of theheadset 103 and the first command. - Upon receipt of the Link Key_REQ message, the
portable terminal 101 1 goes to block 605 and otherwise, it repeatsblock 603. Theportable terminal 101 searches for a link key based on the Link Key_REQ message received from theheadset 103 inblock 605 and generates a Link Key_CNF message based on a search result inblock 607. - Specifically, the
portable terminal 103 detects the ID of the headset 130 from the Link Key_REQ message by analyzing the received Link Key_REQ message, and searches for a link key corresponding to the ID of the headset 130 among link keys pre-stored in thefirst memory unit 205. If the link key corresponding to the ID of theheadset 103 is detected from thefirst memory unit 205, theportable terminal 101 generates a Link Key_CNF message including the detected link key and the second command indicating that theportable terminal 101 pre-stores the link key of the headset 130. On the contrary, if the link key corresponding to the ID of theheadset 103 is not detected from thefirst memory unit 205, theportable terminal 101 generates a Link Key_CNF message including the third command that theportable terminal 101 does not store the link key of theheadset 103. - The
portable terminal 101 determines whether a connection request message has been received from theheadset 103 by BT communication inblock 609. The connection request message requests setup of a BT connection using the pre-stored link key of theheadset 103. Upon receipt of the connection request message, theportable terminal 101 goes to block 611 and otherwise, it goes to block 615. - The
portable terminal 101 establishes a BT connection with theheadset 103 using the detected link key inblock 611. Inblock 613, theportable terminal 101 generates a connection confirm message and transmits the connection confirm message to theheadset 103 by BT communication. The connection confirm message indicates that theportable terminal 101 has established a BT connection using the detected link key. - In
block 615, theportable terminal 101 monitors receipt of an OOB pairing request message. Upon the OOB pairing request message, theportable terminal 101 goes to block 617 and otherwise, theportable terminal 101 ends communication with theheadset 103. Inblock 617, theportable terminal 101 establishes a BT connection with theheadset 103 by OOB pairing. -
FIG. 7 illustrates a headset that is powered on according to an embodiment of the present disclosure. Referring toFIG. 7 , after aportable terminal 701 is connected to a headset 702 in power-off state 707 by NFC, theheadset 703 is powered on as indicated byreference numeral 705. Specifically, theheadset 703 transmits a Link Key_REQ message to theportable terminal 701 by NFC and receives a Link Key_CNF message from theportable terminal 701 by NFC in response to the Link Key_REQ message. Then theheadset 703 is placed in the power-onstate 705 and establishes a BT connection with theportable terminal 701 using a link key included in the Link Key_CNF message. - As is apparent from the above description, a short-range wireless communication device is powered on by NFC, thus increasing user convenience. The short-range wireless communication device receives a link key by NFC and establishes a BT connection with a portable terminal using the received link key. Therefore, user convenience is further increased.
- Although the present disclosure has been described with an exemplary embodiment, various changes and modifications may be suggested to one skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.
Claims (16)
- A power control apparatus in a short-range wireless communicat ion device (103), comprising:a second Near Field Communication (NFC) unit (301) configured to :transmit a link key request message requesting a link key to a first N FC unit (201) when the second NFC unit is connected to the first NFC unit of a portable terminal (101) by NFC, andpower on the short-range wireless communication device upon recei pt of a link key confirm message from the first NFC unit in response to the link key request message.
- The power control apparatus of claim 1, wherein the link key re quest message includes an Identifier (ID) of the short-range wireless comm unication device.
- The power control apparatus of claim 2, wherein the link key co nfirm message includes a link key corresponding to the ID of the short-ran ge wireless communication device.
- The power control apparatus of claim 1, further comprising a se cond Bluetooth (BT) unit (303) configured to establish a BT connection wit h a first BT unit (203) of the portable terminal using the included link key when the link key confirm message includes a link key.
- An apparatus for controlling power of a short-range wireless communication device (103) in a portable terminal (101), comprising:a first Near Field Communication (NFC) unit (201) configured to re ceive a link key request message from a second NFC unit (301) and transm it a link key confirm message to the second NFC unit in response to the lin k key request message when the first NFC unit is connected to the second NFC unit of the short-range wireless communication device by NFC; anda first Bluetooth (BT) unit (203) configured to, upon receipt of the li nk key request message from the first NFC unit, search for a link key corre sponding to the short-range wireless communication device in one or more pre-stored link keys and generate the link key confirm message based on a search result.
- The apparatus of claim 5, wherein the link key request message i ncludes an Identifier (ID) of the short-range wireless communication devic e.
- The apparatus of claim 6, wherein the link key confirm message includes a link key corresponding to the ID of the short-range wireless com munication device.
- The apparatus of claim 5, wherein upon receipt of a connection request message from the short-range wireless communication device, the first BT unit establishes a BT connection with a second BT unit (303) of the short-range wireless communication device using the detected link key.
- A power control method in a short-range communication device (103), comprising:transmitting a link key request message requesting a link key to a po rtable terminal (101), when the short-range wireless communication device is connected to the portable terminal by Near Field Communication (NFC) ; andpowering on the short-range wireless communication device, upon r eceipt of a link key confirm message from the portable terminal in response to the link key request message.
- The power control method of claim 9, wherein the link key requ est message includes an Identifier (ID) of the short-range wireless commun ication device.
- The power control method of claim 10, wherein the link key con firm message includes a link key corresponding to the ID of the short-range wireless communication device.
- The power control method of claim 9, further comprising, when the link key confirm message includes a link key, establishing a BT connec tion with the portable terminal using the included link key.
- A method for controlling power of a short-range wireless communication device (103) in a portable terminal (101), comprising:receiving a link key request message from the short-range wireless c ommunication device, when the portable terminal is connected to the short-range wireless communication device by Near Field Communication (NFC );searching for a link key corresponding to the short-range wireless co mmunication device among one or more pre-stored link keys and generatin g a link key confirm message based on a search result; andtransmitting the link key confirm message to the short-range wireles s communication device by NFC.
- The method of claim 13, wherein the link key request message i ncludes an Identifier (ID) of the short-range wireless communication devic e.
- The method of claim 14, wherein the link key confirm message i ncludes a link key corresponding to the ID of the short-range wireless com munication device.
- The method of claim 13, further comprising, upon receipt of a connection request message from the short-range wireless communication device, establishing a BT connection with the short-range wireless communication device using the detected link key.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020120111284A KR101995251B1 (en) | 2012-10-08 | 2012-10-08 | Apparatus and method for controlling a power in near field communication device |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2717632A2 true EP2717632A2 (en) | 2014-04-09 |
EP2717632A3 EP2717632A3 (en) | 2016-04-27 |
EP2717632B1 EP2717632B1 (en) | 2018-12-12 |
Family
ID=49354448
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13187550.2A Active EP2717632B1 (en) | 2012-10-08 | 2013-10-07 | Apparatus and method for controling power in a short-range communication device |
Country Status (7)
Country | Link |
---|---|
US (1) | US9749953B2 (en) |
EP (1) | EP2717632B1 (en) |
JP (1) | JP6316566B2 (en) |
KR (1) | KR101995251B1 (en) |
CN (1) | CN103716906B (en) |
AU (1) | AU2013237757A1 (en) |
WO (1) | WO2014058214A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3062475A1 (en) * | 2015-02-24 | 2016-08-31 | Ricoh Company, Ltd. | Communication device, communication method, and communication system |
WO2019145456A1 (en) * | 2018-01-29 | 2019-08-01 | Koninklijke Philips N.V. | Securing headless devices from malicious (re-)configuration |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5541430B1 (en) | 2013-08-19 | 2014-07-09 | ソニー株式会社 | Imaging unit, mounting device |
JP5527492B1 (en) * | 2013-08-19 | 2014-06-18 | ソニー株式会社 | Imaging apparatus, control method, and program |
US11159919B2 (en) | 2013-11-15 | 2021-10-26 | Synchrony Bank | Method and system for distributed management of remote transmitters interacting with mobile devices |
JP2015177273A (en) * | 2014-03-14 | 2015-10-05 | ソニー株式会社 | Electronic apparatus, communication system, electronic apparatus control method and program |
FR3022714A1 (en) * | 2014-06-23 | 2015-12-25 | Orange | SHORT DISTANCE COMMUNICATION DEVICE |
KR101568332B1 (en) | 2014-11-12 | 2015-11-12 | 현대자동차주식회사 | Vehicle supporting efficient bluetooth connection and method for controlling thereof |
KR101768134B1 (en) * | 2015-09-21 | 2017-08-14 | 현대자동차주식회사 | Apparatus and method for controlling system power in vehicle |
KR101672926B1 (en) * | 2016-05-31 | 2016-11-04 | 여동균 | Power controlling system for display |
CN106686528B (en) * | 2016-12-21 | 2021-01-01 | 杭州新中大科技股份有限公司 | Data transmission method and system, master device and slave device |
JP6942585B2 (en) * | 2017-09-25 | 2021-09-29 | キヤノン株式会社 | Power supply equipment, control method of power supply equipment, program |
US10708769B2 (en) * | 2017-12-20 | 2020-07-07 | Bose Corporation | Cloud assisted accessory pairing |
EP3657405A1 (en) * | 2018-11-23 | 2020-05-27 | Nxp B.V. | Method of operating an nfc device, the nfc device, and a communication system |
US11256317B2 (en) * | 2019-05-17 | 2022-02-22 | Facebook Technologies, Llc | Systems and methods for scheduling component activation |
US11997496B2 (en) * | 2019-05-31 | 2024-05-28 | Apple Inc. | Temporary pairing for wireless devices |
US20210058257A1 (en) * | 2019-08-20 | 2021-02-25 | Rune Labs, Inc. | Security and identity verification for neuromodulation therapy implant device programming |
US12048846B2 (en) | 2019-08-20 | 2024-07-30 | Rune Labs, Inc. | Neuromodulation therapy simulator |
US11817209B2 (en) | 2019-08-20 | 2023-11-14 | Rune Labs, Inc. | Neuromodulation therapy development environment |
CN110730441B (en) * | 2019-10-18 | 2021-07-02 | 飞天诚信科技股份有限公司 | Bluetooth device and working method thereof |
CN111800273B (en) * | 2020-06-30 | 2021-12-24 | 联想(北京)有限公司 | Information processing method, electronic device, and storage medium |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3671880B2 (en) * | 2001-07-18 | 2005-07-13 | ソニー株式会社 | COMMUNICATION SYSTEM AND METHOD, INFORMATION PROCESSING DEVICE AND METHOD, COMMUNICATION TERMINAL AND METHOD, EXPANSION DEVICE, AND PROGRAM |
JP3761505B2 (en) * | 2002-03-04 | 2006-03-29 | 株式会社東芝 | COMMUNICATION SYSTEM, RADIO COMMUNICATION TERMINAL, AND RADIO COMMUNICATION DEVICE |
US20050266798A1 (en) * | 2004-05-31 | 2005-12-01 | Seamus Moloney | Linking security association to entries in a contact directory of a wireless device |
US7643798B2 (en) * | 2005-12-09 | 2010-01-05 | Sony Ericsson Mobile Communications Ab | Passive NFC activation of short distance wireless communication |
KR100800733B1 (en) * | 2006-02-08 | 2008-02-01 | 삼성전자주식회사 | Bluetooth system and bluetooth bonding process method |
US20080090520A1 (en) * | 2006-10-17 | 2008-04-17 | Camp William O | Apparatus and methods for communication mobility management using near-field communications |
JP2009060526A (en) * | 2007-09-03 | 2009-03-19 | Ntt Docomo Inc | Communication apparatus, communication system and communication connection method |
KR101102673B1 (en) * | 2007-10-30 | 2012-01-05 | 삼성전자주식회사 | Apparatus and method to transmit/receive data in a communication system |
US7970350B2 (en) | 2007-10-31 | 2011-06-28 | Motorola Mobility, Inc. | Devices and methods for content sharing |
WO2009069971A2 (en) * | 2007-11-30 | 2009-06-04 | Samsung Electronics Co., Ltd. | Method and system for secure communication in near field communication network |
JP4613969B2 (en) * | 2008-03-03 | 2011-01-19 | ソニー株式会社 | Communication apparatus and communication method |
JP4506856B2 (en) * | 2008-03-10 | 2010-07-21 | ソニー株式会社 | Communication apparatus and communication method |
US8112066B2 (en) * | 2009-06-22 | 2012-02-07 | Mourad Ben Ayed | System for NFC authentication based on BLUETOOTH proximity |
US20110028091A1 (en) * | 2009-08-03 | 2011-02-03 | Motorola, Inc. | Method and system for near-field wireless device pairing |
EP2302884A1 (en) * | 2009-09-24 | 2011-03-30 | Research In Motion Limited | Mobile wireless communications device, method and system using magnetic sensor and activated NFC circuit for establishing communications between mobile wireless communications devices |
-
2012
- 2012-10-08 KR KR1020120111284A patent/KR101995251B1/en active IP Right Grant
-
2013
- 2013-10-07 EP EP13187550.2A patent/EP2717632B1/en active Active
- 2013-10-08 US US14/049,108 patent/US9749953B2/en active Active
- 2013-10-08 CN CN201310464838.1A patent/CN103716906B/en active Active
- 2013-10-08 WO PCT/KR2013/008994 patent/WO2014058214A1/en active Application Filing
- 2013-10-08 AU AU2013237757A patent/AU2013237757A1/en not_active Abandoned
- 2013-10-08 JP JP2013211203A patent/JP6316566B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
None |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3062475A1 (en) * | 2015-02-24 | 2016-08-31 | Ricoh Company, Ltd. | Communication device, communication method, and communication system |
US10009347B2 (en) | 2015-02-24 | 2018-06-26 | Ricoh Company, Ltd. | Communication device, communication method, and communication system |
WO2019145456A1 (en) * | 2018-01-29 | 2019-08-01 | Koninklijke Philips N.V. | Securing headless devices from malicious (re-)configuration |
US11856406B2 (en) | 2018-01-29 | 2023-12-26 | Koninklijke Philips N.V. | Securing headless devices from malicious (re-)configuration |
Also Published As
Publication number | Publication date |
---|---|
CN103716906A (en) | 2014-04-09 |
EP2717632B1 (en) | 2018-12-12 |
EP2717632A3 (en) | 2016-04-27 |
KR20140045125A (en) | 2014-04-16 |
US20140099889A1 (en) | 2014-04-10 |
JP6316566B2 (en) | 2018-04-25 |
CN103716906B (en) | 2019-04-12 |
KR101995251B1 (en) | 2019-09-30 |
US9749953B2 (en) | 2017-08-29 |
JP2014078944A (en) | 2014-05-01 |
WO2014058214A1 (en) | 2014-04-17 |
AU2013237757A1 (en) | 2014-04-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2717632A2 (en) | Apparatus and method for controling power in a short-range communication device | |
US9060069B2 (en) | Apparatus and method for connecting with bluetooth devices in a terminal using audio channel | |
EP3462803B1 (en) | Method for managing bluetooth connection and master bluetooth device | |
US20160105412A1 (en) | Network connection method, application authentication server, terminal and router | |
US20190327702A1 (en) | Cell Registration Method and Device | |
US8805338B2 (en) | Method and system for managing communication of a dual-standby portable terminal | |
US20150003432A1 (en) | Electronic device, method, and computer-readable storage medium | |
WO2015043338A1 (en) | Identify verifying method, account acquiring method, mobile terminal, and storage medium | |
US10691819B2 (en) | Method and apparatus for remotely deleting information | |
CN108089928B (en) | Terminal control method and device | |
CN104135728A (en) | Network connection method and device | |
CN112269086B (en) | Charging cable identification method and device, charging cable and readable storage medium | |
CN104581993A (en) | Wireless connection building method, data transmission method and terminal | |
CN110944313B (en) | Bluetooth connection method, device, storage medium and terminal | |
CN104684056A (en) | Pairing method and device for user equipment and server | |
WO2014183439A1 (en) | Method, apparatus and system for switching function mode | |
CN105530222A (en) | Method for establishing connection among terminals, and device and system | |
CN111314900B (en) | Wireless connection method, wireless connection device and mobile terminal | |
US20140344423A1 (en) | Method, apparatus and system for switching function mode | |
CN111885591A (en) | Network connection method, device, storage medium and terminal | |
CN112543493A (en) | Wifi connection method, terminal and computer storage medium | |
CN110582079B (en) | Bluetooth connection setting method and device, computer readable storage medium and terminal | |
CN114980044A (en) | Bluetooth connection method, storage medium and related equipment | |
CN112261634A (en) | Bluetooth transmission control method, device, terminal equipment and storage medium | |
KR101429274B1 (en) | Back up system and back up method |
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 |
|
AK | Designated contracting states |
Kind code of ref document: A2 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 |
|
PUAL | Search report despatched |
Free format text: ORIGINAL CODE: 0009013 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04B 5/00 20060101ALI20160317BHEP Ipc: H04W 52/02 20090101AFI20160317BHEP Ipc: H04L 29/06 20060101ALI20160317BHEP Ipc: H04W 4/00 20090101ALI20160317BHEP |
|
AK | Designated contracting states |
Kind code of ref document: A3 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 |
|
17P | Request for examination filed |
Effective date: 20160726 |
|
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: 20161206 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602013048065 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04W0052020000 Ipc: H04B0005000000 |
|
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 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 4/80 20180101ALI20180531BHEP Ipc: H04L 29/06 20060101ALI20180531BHEP Ipc: H04W 4/00 20180101ALI20180531BHEP Ipc: H04B 5/00 20060101AFI20180531BHEP Ipc: H04W 52/02 20090101ALI20180531BHEP |
|
INTG | Intention to grant announced |
Effective date: 20180629 |
|
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: AT Ref legal event code: REF Ref document number: 1077351 Country of ref document: AT Kind code of ref document: T Effective date: 20181215 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602013048065 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: FP |
|
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: 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: 20181212 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: 20190312 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: 20181212 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: 20181212 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: 20181212 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: 20190312 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: 20181212 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 1077351 Country of ref document: AT Kind code of ref document: T Effective date: 20181212 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20190313 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: 20181212 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: 20181212 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: 20181212 |
|
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: 20181212 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: 20181212 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: 20190412 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: 20181212 |
|
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: 20181212 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: 20190412 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: 20181212 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: 20181212 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: 20181212 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602013048065 Country of ref document: DE |
|
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: 20181212 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: 20181212 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: 20181212 |
|
26N | No opposition filed |
Effective date: 20190913 |
|
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: 20181212 |
|
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: 20181212 |
|
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: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191007 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20191031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191031 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191007 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20181212 |
|
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: 20131007 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: 20181212 |
|
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: 20181212 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20230920 Year of fee payment: 11 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240920 Year of fee payment: 12 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20240920 Year of fee payment: 12 |