[go: up one dir, main page]

WO2015137601A1 - Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil - Google Patents

Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil Download PDF

Info

Publication number
WO2015137601A1
WO2015137601A1 PCT/KR2014/012070 KR2014012070W WO2015137601A1 WO 2015137601 A1 WO2015137601 A1 WO 2015137601A1 KR 2014012070 W KR2014012070 W KR 2014012070W WO 2015137601 A1 WO2015137601 A1 WO 2015137601A1
Authority
WO
WIPO (PCT)
Prior art keywords
data length
information
maximum
data
time information
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.)
Ceased
Application number
PCT/KR2014/012070
Other languages
English (en)
Korean (ko)
Inventor
권영환
이재호
이민수
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Priority to US15/125,498 priority Critical patent/US10219183B2/en
Priority to CN201480077076.2A priority patent/CN106105310B/zh
Priority to JP2016556251A priority patent/JP6374526B2/ja
Priority to KR1020167023647A priority patent/KR101869070B1/ko
Publication of WO2015137601A1 publication Critical patent/WO2015137601A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/22—Negotiating communication rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
    • H04W28/0221—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices power availability or consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks

Definitions

  • the present invention relates to a method and apparatus for adjusting a data rate in a wireless communication system, and more particularly, to a method and apparatus for increasing a data rate in a Bluetooth communication.
  • the device When performing wireless communication between two devices using Bluetooth communication, a user performs a procedure of searching for a Bluetooth device and requesting a connection. do.
  • the device may mean an apparatus and an apparatus.
  • the user may perform a connection after searching for the Bluetooth device according to the Bluetooth communication method to use using the Bluetooth device.
  • Bluetooth communication methods include Bluetooth BR / EDR (Basic Rate / Enhanced Data Rate) and Bluetooth Low Energy (LE).
  • the Bluetooth BR / EDR scheme may be referred to as classic Bluetooth.
  • Classic Bluetooth includes Bluetooth technology that has been passed from Bluetooth 1.0 to 2.1 using Basic Rate and Bluetooth technology that uses Enhanced Data Rate supported from Bluetooth 2.0.
  • Bluetooth Low Energy (hereinafter referred to as Bluetooth LE) technology can consume hundreds of kilobytes of information and reliably consume less power.
  • the Bluetooth low energy energy technology uses an attribute protocol to exchange information between devices. This Bluetooth LE method can reduce energy overhead by reducing the header overhead and simplifying the operation.
  • Some Bluetooth devices do not have a display or a user interface.
  • the complexity of connection / management / control / disconnection between various kinds of Bluetooth devices and similarly applied Bluetooth devices is increasing.
  • Bluetooth can achieve a relatively high speed at a relatively low power, low cost, but the transmission distance is limited to a maximum of 100m, it is suitable for use in a limited space.
  • the Bluetooth LE technology has reduced the amount of data that can be transmitted compared to the existing Bluetooth BR / EDR, which takes a long time when transmitting a large amount of data, and because the Bluetooth module must be activated continuously, There is a problem of increased power consumption.
  • An object of the present invention is to provide a method for changing the data rate in Bluetooth communication.
  • Another object of the present invention is to provide a method for improving data transmission rate in Bluetooth communication.
  • Another object of the present invention is to provide a method for negotiating packet length in order to improve data transmission rate in an initial Bluetooth pairing step.
  • Another object of the present invention is to provide a method for changing a data rate during data transmission after a Bluetooth connection.
  • Another object of the present invention is to provide a method for negotiating packet length in order to improve data transmission rate during data transmission after Bluetooth connection.
  • the present invention provides a method and apparatus for extending data length of Bluetooth communication in order to solve the above problems.
  • the method of extending data length includes: receiving a first message including information of the second device from a second device; Sending a connection request message to the second device based on the first message; Performing a Bluetooth connection with the second device based on the connection request message; Transmitting an extension request message requesting an extension of a transmission data length and a reception data length through the connected Bluetooth; And receiving an extended response message in response to the request message through the connected Bluetooth, wherein the request message includes first maximum transmission data length information, first maximum received data length information, and a first maximum reception data length information of the first device. At least one of first maximum transmission time information or first maximum reception time information, and the response message includes second maximum transmission data length information, second maximum reception data length information, and second maximum transmission time of the second device. And at least one of information or second maximum reception time information.
  • the present invention further includes negotiating a transmission data length and a reception data length, wherein the transmission data length is negotiated based on at least one of third maximum transmission data length information and third maximum transmission time information.
  • the received data length may be negotiated based on at least one of third maximum received data length information and third maximum received time information.
  • the third maximum transmission data length information is negotiated with a smaller value of the first maximum transmission data length information and the second maximum reception data length information, and the third maximum transmission time information is the above-mentioned.
  • the third maximum received data length information is negotiated with a smaller value among first maximum transmission time information and the second maximum reception time information, and the third maximum received data length information is smaller than the first maximum received data length information and the second maximum transmitted data length information.
  • the third maximum reception time information is negotiated by a smaller value among the first maximum reception time information and the second maximum transmission time information.
  • connection request message may include at least one of window size information, window offset information, and connect interval information.
  • the present invention includes the steps of transmitting a window size update request message for changing the window size; And receiving a response message in response to the window size update request message.
  • the present invention includes the steps of receiving from the second device the first information related to the transmission data length and the reception data length extension support; Receiving second information related to a data length of the second device from the second device; Negotiating a data length based on the second information and third information related to the data length of the first device; And transmitting the negotiated data length to the second device, wherein the second information includes first maximum transmission data length information, first maximum received data length information, first maximum transmission time information, or first maximum And at least one of reception time information, wherein the third information includes at least one of second maximum transmission data length information, second maximum reception data length information, second maximum transmission time information, or second maximum reception time information. It provides a method comprising the.
  • the negotiated data length may include at least one of a transmission data length, a reception data length, a transmission time, or a reception time.
  • the transmission data length represents a smaller value of the second maximum transmission data length information and the first maximum reception data length information
  • the reception data length is equal to the second maximum reception data length information.
  • the transmission time represents a smaller value of the second maximum transmission time information and the first maximum reception time information
  • the reception time is the second maximum reception. And a smaller value between time information and the first maximum transmission time information.
  • the first information and the second information is characterized in that it is transmitted at the same time in one message.
  • the present invention may further include transmitting a request message for requesting the second information.
  • the present invention includes the steps of transmitting a change request message requesting a change in the negotiated data length; And receiving a change request response message in response to the change request message.
  • the change request message includes at least one of first received data length information or first transmitted data length information
  • the change response message includes response information related to whether to allow the change request; And at least one of second received data length information and second transmitted data length information.
  • the second received data length information is determined based on the first received data length information
  • the second transmitted data length information is determined based on the first transmitted data length information. It features.
  • the communication unit for transmitting and receiving a signal to the outside by wire and / or wireless; And a controller operatively connected to the communication unit, wherein the controller receives a first message including information of the second device from a second device and connects to the second device based on the first message. Transmit a request message, perform a Bluetooth connection with the second device based on the connection request message, transmit an extension request message requesting an extension of a transmission data length and a reception data length through the connected Bluetooth; An extension response message is received in response to the request message via Bluetooth, wherein the request message includes first maximum transmission data length information, first maximum reception data length information, first maximum transmission time information, or first information of the first device. 1 response including at least one of the maximum reception time information; The message may include at least one of second maximum transmission data length information, second maximum reception data length information, second maximum transmission time information, or second maximum reception time information of the second device. do.
  • control unit negotiates a transmission data length and a reception data length, wherein the transmission data length is negotiated based on at least one of third maximum transmission data length information and third maximum transmission time information.
  • the received data length may be negotiated based on at least one of third maximum received data length information and third maximum received time information.
  • the third maximum transmission data length information is negotiated with a smaller value of the first maximum transmission data length information and the second maximum reception data length information, and the third maximum transmission time information is the above-mentioned.
  • the third maximum received data length information is negotiated with a smaller value among first maximum transmission time information and the second maximum reception time information, and the third maximum received data length information is smaller than the first maximum received data length information and the second maximum transmitted data length information.
  • the third maximum reception time information is negotiated by a smaller value among the first maximum reception time information and the second maximum transmission time information.
  • connection request message may include at least one of window size information, window offset information, and connect interval information.
  • control unit may transmit a window size update request message for changing the window size, and receive a response message in response to the window size update request message.
  • the communication unit for transmitting and receiving a signal to the outside by wire and / or wireless; And a control unit operatively connected to the communication unit, wherein the control unit receives first information related to whether to support a transmission data length and a reception data length extension from a second device, and receives the second information from the second device.
  • Receiving second information related to a data length negotiating a data length based on the second information and third information related to a data length of the first device, and transmitting the negotiated data length to the second device
  • the second information may include at least one of first maximum transmission data length information, first maximum reception data length information, first maximum transmission time information, or first maximum reception time information.
  • the information includes second maximum transmission data length information, second maximum received data length information, second maximum transmission time information, or second maximum Receiving time at least provide a device which is characterized in that it comprises any of the information.
  • the Bluetooth data rate changing method by negotiating the packet length, there is an effect that can improve the data rate.
  • the Bluetooth data rate changing method according to an embodiment of the present invention, as the data rate is improved through packet length negotiation, there is an effect that the data transmission time can be shortened.
  • the Bluetooth data rate changing method As the amount of data that can be transmitted at a time increases through packet length negotiation, the data rate is improved, thereby reducing power consumption of the Bluetooth device. .
  • the data rate that can be delivered as a scan request response through the packet length negotiation in the pairing step is improved, thereby improving the data transmission efficiency of the Bluetooth device.
  • the Bluetooth data rate changing method since a large amount of data can be transmitted through packet length negotiation after a blue pitcher connection, it is possible to improve data transmission speed and reduce power consumption of a Bluetooth device. It has an effect.
  • the Bluetooth data rate changing method since the data rate can be changed according to the amount of data to be transmitted through packet length negotiation after the Bluetooth connection, it is possible to efficiently transmit data.
  • 1 is a diagram illustrating a protocol stack provided for Bluetooth communication to which the present invention is applied.
  • FIG. 2 is a diagram illustrating an example of an internal block diagram of a device to which the present invention is applied.
  • 3 to 5 are diagrams illustrating an example of a general connection process and packet format of Bluetooth.
  • FIG. 6 is a diagram illustrating an example of a packet format for improving a data rate to which the present invention is applied.
  • FIGS. 7 to 9 are diagrams illustrating an example of a packet length negotiation and a packet format in a Bluetooth connection process to which the present invention is applied.
  • FIGS. 10 and 11 are diagrams illustrating an example of a process and a packet format for negotiating packet length through a scan request and a scan response in a Bluetooth connection process to which the present invention is applied.
  • 12 to 14 illustrate another example of a process and a packet format for negotiating packet length through a scan request and a scan response in a Bluetooth connection process to which the present invention is applied.
  • 15 and 16 illustrate examples of a process and a packet format for using an extended scan response through packet length negotiation in a Bluetooth connection process to which the present invention is applied.
  • 17 and 18 are diagrams illustrating a process and a packet format for changing a packet length after a Bluetooth connection to which the present invention is applied.
  • 19 and 20 are diagrams illustrating a process packet format for extending a packet length after a Bluetooth connection to which the present invention is applied.
  • Electronic devices described herein may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, and the like.
  • PDA personal digital assistant
  • PMP portable multimedia player
  • the configuration according to the embodiments described herein may also be applied to fixed terminals such as digital TVs, desktop computers, etc., except when applicable only to mobile terminals.
  • the signals described herein may be transmitted in the form of frames as well as messages.
  • 1 is a diagram illustrating a protocol stack provided for Bluetooth communication to which the present invention is applied.
  • (a) shows an example of a protocol stack of Bluetooth Basic Rate (BR) / Enhanced Data Rate (EDR), and (b) shows an example of a protocol stack of Bluetooth Low Energy (LE). Indicates.
  • BR Basic Rate
  • EDR Enhanced Data Rate
  • LE Bluetooth Low Energy
  • the Bluetooth BR / EDR protocol stack includes a controller stack 10 and a host stack based on a host controller interface HCI 18. Stack, 20).
  • the host stack (or host module) 20 refers to a wireless transceiver module for receiving a 2.4 GHz Bluetooth signal and hardware for transmitting or receiving a Bluetooth packet.
  • the host stack (or host module) 20 is connected to a Bluetooth module which is the controller stack 10 to connect a Bluetooth module. Control and perform actions.
  • the host stack 20 may include a BR / EDR PHY layer 12, a link controller layer 14, and a link manager layer 16.
  • the BR / EDR PHY layer 12 is a layer for transmitting / receiving a 2.4 GHz radio signal and may transmit data by hopping 79 RF channels when using Gaussian Frequency Shift Keying (GFSK) modulation.
  • GFSK Gaussian Frequency Shift Keying
  • the link controller layer 14 is responsible for transmitting a digital signal, selects a channel sequence hopping 1400 times per second, and transmits a 625us length time slot for each channel.
  • the link manager layer 16 controls the overall operation (link setup, control, security) of the Bluetooth connection by using a link manager protocol (LMP).
  • LMP link manager protocol
  • the link manager layer 16 may perform the following functions.
  • the host controller interface layer 18 provides an interface between the host module and the controller module so that the host can provide commands and data to the controller, and the controller can provide events and data to the host.
  • the host stack (or host module 20) includes a logical link control and adaptation protocol (L2CAP, 21), a BR / EDR protocol (22), a generic access profile (GAP, 23), and a BR / EDR profile. (24).
  • L2CAP logical link control and adaptation protocol
  • BR / EDR protocol 22
  • GAP generic access profile
  • BR / EDR profile. 24
  • the logical link control and adaptation protocol (L2CAP) 21 may provide one bidirectional channel for transmitting data to a specific protocol or profile.
  • the L2CAP 21 may multiplex various protocols, profiles, etc. provided by a higher layer of Bluetooth.
  • L2CAP of Bluetooth BR / EDR uses dynamic channel, supports protocol service multiplexer, retransmission, streaming mode, and provides segmentation, reassembly, per-channel flow control, and error control.
  • the BR / EDR Protocol 22 and Profiles 24 define a service profile using Bluet BR / EDR and an application protocol for sending and receiving these data, and the Generic Access Profile (GAP). , 23) defines the method of device discovery, connection, and providing information to the user, and provides privacy.
  • GAP Generic Access Profile
  • the Bluetooth LE protocol stack is a controller stack 30 operable to handle timing critical radio interface and a host operable to process high level data. It contains a stack (Host stack, 40).
  • the controller stack 30 may be implemented using a communication module that may include a Bluetooth radio, for example, a processor module that may include a processing device such as a microprocessor.
  • the host stack may be implemented as part of an OS running on a processor module, or as an instance of a package on the OS.
  • controller stack and the host stack can be operated or executed on the same processing device in the processor module.
  • the controller stack 30 includes a physical layer 32, a link layer 34, and a host controller interface 36.
  • the physical layer (wireless transmit / receive module) 32 transmits and receives a 2.4 GHz radio signal and uses Gaussian Frequency Shift Keying (GFSK) modulation and a frequency hopping method consisting of 40 RF channels.
  • GFSK Gaussian Frequency Shift Keying
  • the link layer 34 which transmits or receives a Bluetooth packet, creates a connection between devices after performing advertising and scanning functions using three advertising channels, and generates up to 42 bytes of data packets through 37 data channels. Provides the ability to send and receive.
  • the host stack includes a generic access profile (GAP) 40, a logical link control and adaptation protocol (L2CAP, 41), a security manager (SM, 42), an attribute protocol (ATT, 43), and a general attribute profile.
  • GAP generic access profile
  • L2CAP logical link control and adaptation protocol
  • SM security manager
  • ATT attribute protocol
  • ATT attribute protocol
  • general attribute profile GATT, 44
  • GATT Generic Attribute Profile
  • LE profile 46 may be included.
  • the host stack 40 is not limited to this and may include various protocols and profiles.
  • the host stack uses L2CAP to multiplex the various protocols, profiles, etc. provided by Bluetooth.
  • L2CAP Logical Link Control and Adaptation Protocol 41 may provide one bidirectional channel for transmitting data to a specific protocol or profile.
  • the L2CAP 41 may be operable to multiplex data among higher layer protocols, segment and reassemble packages, and manage multicast data transmission.
  • Bluetooth LE uses three fixed channels (one for the signaling channel, one for the Security Manager, and one for the Attribute protocol).
  • BR / EDR Base Rate / Enhanced Data Rate
  • the SM (Security Manager) 42 is a protocol for authenticating a device and providing key distribution.
  • Attribute Protocol (ATT) 43 defines a rule for accessing data of a counterpart device in a server-client structure. ATT has six message types (Request, Response, Command, Notification, Indication, Confirmation).
  • the Request message is a message for requesting specific information from the client device to the server device
  • the Response message is a response message to the request message, which is a message transmitted from the server device to the client device.
  • Command message A message sent from the client device to the server device to indicate a command of a specific operation.
  • the server device does not transmit a response to the command message to the client device.
  • Notification message This message is sent from the server device to the client device for notification such as an event.
  • the client device does not transmit a confirmation message for the notification message to the server device.
  • Indication and Confirm message This message is transmitted from the server device to the client device for notification such as an event. Unlike the notification message, the client device transmits a confirmation message for the Indication message to the server device.
  • the General Access Profile (GAP) 45 is a newly implemented layer for Bluetooth LE technology, and is used to control role selection and multi-profile operation for communication between Bluetooth LE devices.
  • the general access profile 45 is mainly used for device discovery, connection creation, and security procedures, and defines a method of providing information to a user, and defines the type of an attribute as follows.
  • UUID Universal Unique Identifier, value type
  • the LE profile 46 is mainly applied to a Bluetooth LE device as profiles having a dependency on GATT.
  • the LE profile 46 may be, for example, Battery, Time, FindMe, Proximity, Time, Object Delivery Service, and the like. Details of GATT-based Profiles are as follows.
  • the generic attribute profile GATT 44 may be operable as a protocol describing how the attribute protocol 43 is used in the construction of services.
  • the generic attribute profile 44 may be operable to specify how ATT attributes are grouped together into services, and may be operable to describe features associated with the services.
  • the generic attribute profile 44 and the attribute protocol may use features to describe the state and services of a device, and how features relate to each other and how they are used.
  • FIG. 2 is a diagram illustrating an example of an internal block diagram of a device to which the present invention is applied.
  • the server device 200 refers to a device that directly communicates with the client device 100 to receive a request and provide data through a response.
  • the server device 200 transmits a notification and an indication message to the client device 100 to provide data information, and confirms from the client device 100 when the indication message is transmitted. You may receive a (Confirm) message.
  • One server device may be connected to a plurality of client devices, and may be easily reconnected with the client devices by using bonding information.
  • the client device 100 refers to an apparatus for requesting data information and transmission from the server device 200.
  • the client device 100 receives data from the server device 200 through a notification and an indication message, and receives a confirmation message in response to receiving the indication message. You can say the sending device.
  • the client device 100 and the server device 200 are each of the communication unit 110 and 210, the user input unit 120 and 220, the output unit 130 and 230, the control unit 140 and 240, and the memory 150 and 250. ) And power supply units 160 and 260.
  • the communication unit 110 and 210, the user input unit 120 and 220, the output unit 130 and 230, the control unit 140 and 240, the memory 150 and 250, and the power supply unit 160 and 260 are proposed in the present invention. Functionally connected to perform the method.
  • FIG. 2 The components illustrated in FIG. 2 are not essential, and thus an electronic device having more or fewer components may be implemented.
  • the communication unit 110 and 210 may include one or more modules that enable wireless communication between a device and a wireless communication system or between a device and a network in which the device is located.
  • the communication units 110 and 210 may include a broadcast receiving module (not shown), a mobile communication module (not shown), a wireless internet module (not shown), and a short range communication module (not shown).
  • the communication unit 110 and 210 may be referred to as a transceiver.
  • the mobile communication module transmits and receives a radio signal with at least one of a base station, an external terminal, and a server on a mobile communication network.
  • the wireless signal may include various types of data according to transmission and reception of a voice call signal, a video call signal, or a text / multimedia message.
  • the wireless internet module refers to a module for wireless internet access, and the wireless internet module may be embedded or external to the device.
  • Wireless Internet technologies may include Wireless LAN (WiFi), Wireless Broadband (Wibro), World Interoperability for Microwave Access (Wimax), High Speed Downlink Packet Access (HSDPA), and the like.
  • the short range communication module refers to a module for short range communication.
  • a Bluetooth module a Radio Frequency Identification (RFID) module, an infrared data association (IrDA) module, an ultra wideband (UWB), a ZigBee module, and the like may be used.
  • RFID Radio Frequency Identification
  • IrDA infrared data association
  • UWB ultra wideband
  • ZigBee ZigBee module
  • the server device 200 and the client device 100 may establish a Bluetooth connection through the Bluetooth module, and may transmit / receive data through the Bluetooth connection.
  • the communication unit (110, 210) enables the transmission of messages or data, such as command (initiating device-initiated device), request, action, response.
  • the user input units 120 and 220 generate input data for the user to control the operation of the terminal.
  • the user input units 120 and 220 may be configured of a key pad dome switch, a touch pad (static pressure / capacitance), a jog wheel, a jog switch, and the like.
  • the output units 130 and 230 are used to generate output related to visual, auditory or tactile senses, and may include display modules 132 and 232 and sound output modules 134 and 234.
  • the display modules 132 and 232 display and output information processed by the device. For example, when the device is in a call mode, the device displays a user interface (UI) or a graphic user interface (GUI) related to the call. When the device is in a video call mode or a photographing mode, a photographed and / or received image, a UI, or a GUI is displayed.
  • UI user interface
  • GUI graphic user interface
  • the display modules 132 and 232 may include a liquid crystal display, a thin film transistor liquid crystal display, an organic light emitting diode, a flexible display, and a 3D display (3D). display).
  • the sound output modules 134 and 234 output audio data received from the communication unit 110 and 210 or stored in the memory 150 and 250 in a call signal reception, a call mode or a recording mode, a voice recognition mode, and a broadcast reception mode. You may.
  • the sound output modules 134 and 234 output sound signals related to functions (eg, call signal reception sound, message reception sound, etc.) performed in the device.
  • the sound output modules 134 and 234 may include a receiver, a speaker, a buzzer, a microphone, and the like.
  • the microphone may receive a tone transmitted from the counterpart device, and the speaker may transmit a tone to the counterpart device.
  • the controllers 140 and 240 refer to a module for controlling overall operations of the connection initiation device and the connection target device, and control to process a message request and a received message through a Bluetooth interface and another communication interface. can do.
  • the controllers 140 and 240 may be referred to as a controller, a microcontroller, a microprocessor, and the like.
  • the controllers 140 and 240 may include hardware, firmware, It may be implemented by software, or a combination thereof.
  • the controllers 140 and 240 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and / or a data processing device.
  • ASIC application-specific integrated circuit
  • the memory 150 and 250 may store a program for the operations of the controllers 140 and 240 and may temporarily store input / output data.
  • the memories 150 and 250 may store data relating to various patterns of vibration and sound output when a touch input on the touch screen is performed.
  • the memory 150 and 250 are media for storing various types of information of a terminal, and are connected to the controller to store programs, applications, general files, and input / output data for the operations of the controllers 140 and 240. Can be stored.
  • the memory 150 and 250 may be a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (eg, SD or XD memory, etc.). ), Random Access Memory (RAM), Static Random Access Memory (SRAM), ReadOnly Memory (ROM), Electrically Erasable Programmable ReadOnly Memory (EEPROM), Programmable ReadOnly Memory (PROM), Magnetic Disk, Optical Disk It may include at least one type of storage medium.
  • RAM Random Access Memory
  • SRAM Static Random Access Memory
  • ROM ReadOnly Memory
  • EEPROM Electrically Erasable Programmable ReadOnly Memory
  • PROM Programmable ReadOnly Memory
  • Magnetic Disk Optical Disk It may include at least one type of storage medium.
  • the power supply units 160 and 260 refer to a module for supplying power required for the operation of each component by receiving external power and internal power under the control of the controllers 140 and 240.
  • 3 is a flowchart illustrating an example of a general connection process of Bluetooth.
  • the Bluetooth LE procedure includes a device filtering procedure, an advertising procedure, a scanning procedure, a discovery procedure, a connecting procedure, and the like.
  • the device filtering procedure is a method for reducing the number of devices performing a response to a request, an indication, a notification, etc. in the controller stack.
  • the controller stack can control the number of requests sent, reducing power consumption in the Bluetooth LE controller stack.
  • Device 1 300 may perform the device filtering procedure to limit a device receiving an advertisement packet, a scan request, or a connection request.
  • the advertising device refers to a device that transmits an advertising event, that is, performs an advertisement, and is also referred to as an advertiser.
  • the scanning device refers to a device that performs scanning and a device that transmits a scan request.
  • the scanning device when the scanning device receives some advertising packets from the advertising device, the scanning device needs to send a scan request to the advertising device. If the device filtering procedure is used to filter the advertising device to which the scan request is to be sent in advance, the scanning device may ignore the advertising packets sent by the advertising device.
  • the device filtering procedure may also be used in the connection request process. If the device making the connection request does not use the pre-device filtering procedure for the device responding to the connection request, the device receiving the connection request (for example, the advertisement device that performed the advertisement) is connected to the connection request. Must respond.
  • the device making the connection request may be represented as an initiating device or an initiator.
  • the scanning device may use a device filtering procedure to limit devices to send a scan request or a connection request to the advertising device.
  • the device 1 300 which is an advertising device, performs an advertising procedure to perform a non-directional broadcast to devices in the region (S310).
  • the non-directional broadcast refers to broadcast in all directions rather than broadcast in a specific direction.
  • directional broadcasts refer to broadcasts in a particular direction. Non-directional broadcasts occur without a connection procedure between an advertising device and a device in a listening (or listening) state (hereinafter referred to as a listening device).
  • the advertising procedure is used to establish a Bluetooth connection with a nearby initiating device.
  • the advertising procedure may be used to provide periodic broadcast of user data to scanning devices that are listening on the advertising channel.
  • all advertisements (or advertisement events) are broadcast over an advertising physical channel.
  • Bluetooth LE devices connected to a Bluetooth LE piconet can advertise using a particular type of advertisement event.
  • Device 2 400 which is a scanning device, may transmit a scan request to obtain additional user data from the advertising device (S320).
  • the device 1 300 transmits a response to the scan request to the device 2 400 that transmits the scan request through the same advertisement physical channel that receives the scan request (S330).
  • Broadcast user data sent as part of an advertisement packet is dynamic data, while scan response data is generally static data.
  • the advertising device may receive a connection request from the initiating device on the advertising (broadcast) physical channel. If the advertising device used a connectable advertising event and the initiating device was not filtered by the device filtering procedure, the advertising device stops the advertising and enters the connected mode. The advertising device may start advertising again after the connected mode.
  • the device performing scanning that is, device 2 400, performs a scanning procedure to listen for non-directional broadcasts of user data from advertising devices using the advertising physical channel.
  • the device 2 400 transmits a scan request to the advertisement device through the advertisement physical channel in order to request additional user data from the advertisement device (S320).
  • the device 1 300 which is an advertising device, transmits a scan response that is a response to the scan request, including additional user data requested by the scanning device through an advertising physical channel.
  • the scanning procedure can be used while connected to another Bluetooth LE device in a Bluetooth LE piconet.
  • the scanning device is in an initiator mode capable of receiving a broadcasted advertising event and initiating a connection request
  • the device 2 400 is connected to the device 1 300 through an advertising physical channel.
  • the Bluetooth connection can be started by transmitting a connection request to the advertisement device (S340).
  • the scanning device stops scanning the initiator mode for further broadcast and enters the connected mode.
  • Bluetooth devices Devices capable of Bluetooth communication (hereinafter referred to as Bluetooth devices) perform an advertisement procedure and a scanning procedure in order to find nearby devices or to be discovered by other devices within a given area.
  • the discovery procedure is performed asymmetrically.
  • a Bluetooth device that attempts to find other devices around it is called a discovering device and listens for devices that advertise scannable advertising events.
  • Bluetooth devices discovered and available from other devices are referred to as discoverable devices, and actively broadcast advertising events so that other devices can scan through an advertising (broadcast) physical channel.
  • Both the discovering device and the discoverable device may already be connected with other Bluetooth devices in the piconet.
  • connection procedure is asymmetric, and the connection procedure requires the other Bluetooth device to perform the scanning procedure while the specific Bluetooth device performs the advertisement procedure.
  • the advertising procedure can be the goal, so that only one device will respond to the advertising.
  • the connection may be initiated by sending a connection request to the advertising device via the advertising (broadcast) physical channel.
  • an operation state of the BLE technology that is, an advertising state, a scanning state, an initiating state, and a connection state will be briefly described.
  • the link layer LL enters the advertisement state by the instruction of the host (stack). If the link layer is in the advertisement state, the link layer sends advertisement packet data units (PDUs) in the advertisement events.
  • PDUs advertisement packet data units
  • Each advertising event consists of at least one advertising PDU, which is transmitted via the advertising channel indexes used.
  • the advertisement event may terminate when the advertisement PDU is transmitted through each of the advertisement channel indexes used, or may terminate the advertisement event earlier when the advertisement device needs to make space for performing another function.
  • the link layer enters the scanning state by the indication of the host (stack). In the scanning state, the link layer listens for advertising channel indices.
  • scanning states There are two types of scanning states: passive scanning and active scanning, each scanning type being determined by the host.
  • ScanInterval is defined as the interval (interval) between the starting points of two consecutive scan windows.
  • the link layer must listen for completion of all scan intervals in the scan window as indicated by the host. In each scan window, the link layer must scan a different advertising channel index. The link layer uses all available advertising channel indexes.
  • the link layer When passive scanning, the link layer only receives packets and does not transmit any packets.
  • the link layer When active scanning, the link layer performs listening to rely on the advertising PDU type, which may request advertising PDUs and additional information related to the advertising device from the advertising device.
  • the link layer enters the initiation state by the indication of the host (stack).
  • the link layer performs listening for the advertising channel indexes.
  • the link layer listens for the advertising channel index during the scan window period.
  • the link layer enters the connected state when the device performing the connection request, i.e., the initiating device, sends the CONNECT_REQ PDU to the advertising device or when the advertising device receives the CONNECT_REQ PDU from the initiating device.
  • connection After entering the connected state, the connection is considered to be created. However, it does not need to be considered to be established at the time the connection enters the connected state. The only difference between the newly created connection and the established connection is the link layer connection supervision timeout value.
  • the link layer that performs the master role is called a master, and the link layer that performs the slave role is called a slave.
  • the master controls the timing of the connection event, and the connection event is the point in time when the master and the slave are synchronized.
  • the Bluetooth LE procedure adopts only three channels less than the Bluetooth BR / EDR procedure and uses it as an advertising channel, it uses 10 to 20 times less power than the Bluetooth BR / EDR technique.
  • the packet structure of the Bluetooth LE will be described in order to examine the length of data that can be transmitted in the Bluetooth LE technology.
  • 4 and 5 illustrate an example of a Bluetooth packet format.
  • the Bluetooth LE has one (a) link layer packet 410 format used for both the advertisement channel packet and the data channel packet.
  • Each packet consists of four fields: preamble, access address, packet data unit (PDU), and CRC.
  • the length of the PDU is at least 2 octets and at most 39 octets, and the length of data that can be transmitted at one time through the Bluetooth LE may be determined according to the length of the PDU.
  • the PDU When one packet is sent on an advertising physical channel, the PDU will be an advertising channel PDU, and when one packet is sent on a data physical channel, the PDU will be a data channel PDU.
  • the Advertising Channel PDU (420) has a 16-bit header 430 and a payload length of at least 0 octets up to 31 octets, and (c) the header of the advertising channel PDU (
  • the 430 may include a PDU type, a reserved for future use (RFU), a TxAdd, an RxAdd, and a Length field.
  • the TxAdd field and the RxAdd field include information for the PDU Type, and the Length field indicates the length of the Payload field and may be expressed in octets.
  • TxAdd field or the RxAdd field may be used as the RFU field.
  • the PDU Type field indicates a PDU type as defined in Table 1 below.
  • the maximum length of the advertising channel PDU is 39 octets. Therefore, the length of data that can be transmitted at one time through advertising is limited to 31 octets, which limits the information that can be provided.
  • advertising channel PDU types are called advertising PDUs and are used in specific events.
  • ADV_IND Connectable Non-Oriented Ads Event
  • ADV_DIRECT_IND Connectable Directional Advertising Event
  • ADV_NONCONN_IND Non-connectable non-directional advertising event
  • ADV_SCAN_IND Scannable Non-Oriented Advertising Event
  • the PDUs are transmitted at the link layer in the advertisement state and received by the link layer in the scanning state or initiating state.
  • the advertising channel PDU type below is called a scanning PDU and is used in the state described below.
  • SCAN_REQ Sent by the link layer in the scanning state and received by the link layer in the advertising state.
  • SCAN_RSP Sent by the link layer in the advertising state and received by the link layer in the scanning state.
  • the advertising channel PDU type below is called the initiating PDU.
  • CONNECT_REQ Sent by the link layer in the initiating state and received by the link layer in the advertising state.
  • the data channel PDU 510 of FIG. 5 may have a 16-bit header, payloads of various lengths, and include a message integrity check (MIC) field.
  • MIC message integrity check
  • the data channel PDU header 520 may include a Logical Link Identifier (LLID), the Next Expected Sequence Number (NESN), a Sequence Number (SN), a More Data (MD), and a Length field.
  • LLID Logical Link Identifier
  • NESN Next Expected Sequence Number
  • SN Sequence Number
  • MD More Data
  • the LLID field includes information for identifying whether the data channel PDU is an LL Data PDU or an LL Control PDU.
  • the NESN field and the SN field are fields that perform an acknowledgment (ACK) function when exchanging data.
  • ACK acknowledgment
  • the SN field value is compared with the NESN field value, and if it is the same, it is regarded as NAK (Negative Acknowledge), and old data is resent, otherwise, the SN field value is increased (0 or 1 since the SN field is 1 bit information). New data can be transferred.
  • the received data is regarded as NAK.
  • the NESN field value is not changed, and thus the SN field value and the NESN field value are the same at the next packet transmission, and the data is retransmitted.
  • the MD field may be used to indicate that there is more data to be transmitted by the device.
  • the length of data that can be transmitted at a time is limited to a maximum of 37 octets.
  • the Bluetooth LE technology aims to quickly transmit a small amount of data using low power, and thus the data length that can be transmitted at a time through an advertising channel PDU or a data channel PDU is limited. As a result, it takes a long time to transmit a large amount of data and may cause a problem of increased power consumption.
  • FIG. 6 is a diagram illustrating an example of a packet format for improving a data rate to which the present invention is applied.
  • the length of the PDU of the link layer packet may be set larger than that of the existing linkator packet to increase the data length that can be transmitted at one time.
  • the length of the PDU including the data to be transmitted in the link layer packet 610 used in the advertisement channel packet and the data channel packet in the Bluetooth LE technology can be extended to a maximum of 249 octets.
  • the length of the advertisement channel PDU and data channel PDU using the link layer packet 610 format may also be extended up to 249 octets, and the payload may also be extended. It can be extended up to 245 octets.
  • the Long Length field may be added to the header 620 of the advertisement channel PDU and the header 630 of the data channel PDU to inform other devices whether the extended link layer packet is supported.
  • the length of the link layer PDU is extended, the length of the payload of the link layer PDU is also extended, so that the length field indicating the length of the payload in the advertisement channel PDU header 620 and the data channel PDU header 630 is included.
  • the length is also changed to 8 bits to indicate the length of the extended payload.
  • the packet format of FIG. 6 may be used in the following embodiments.
  • the length of data that can be transmitted is increased compared to the existing packet format. Therefore, when a large amount of data is transmitted, the number of data exchanges between devices is reduced, thereby reducing data transmission time. This can also reduce the power consumption of the device.
  • FIGS. 7 to 9 are diagrams illustrating an example of a packet length negotiation and a packet format in a Bluetooth connection process to which the present invention is applied.
  • data length may be struck through advertisement and connection request.
  • the device 1 300 when the device 1 300 tries to connect with the device 2 400 through the Bluetooth LE technology, the device 1 300 transmits an advertisement message or a frame to the device 2 400. It may be (S710).
  • the advertisement message or frame has the same format as the link layer packet 610 of FIG. 6, and when the device 1 300 supports the extended link layer PDU, the advertisement channel PDU header 620 of FIG. This can be informed to the device 2 (400).
  • the PDU payload of the advertisement message or frame may have the format of (a) or (b) of FIG. 8.
  • the above-described PDU payloads of the ADV_IND, the ADV_NONCONN_IND, and the ADV_SCAN_IND are shown in FIG. 8A
  • the ADV_DIRECT_IND is a packet format as shown in FIG. 8B.
  • the advertising channel PDU payload of FIGS. 8A and 8B includes an AdvA field including an address of the device 1 300, which is an advertisement device, and an AdvData field including a supporting data length. do.
  • the (b) advertisement channel PDU payload 820 used in the ADV_DIRECT_INT may further include an InitA field indicating an address of a device requesting a connection.
  • the AdvData field 830 of the advertisement channel PDU includes an AdvData Type indicating the type of the advertisement message or frame, a Maximum RX LE Payload Size field indicating the maximum data length that can be received, and a Maximum TX LE Payload indicating the maximum data length that can be transmitted. It may include a Size field.
  • the device 2 400 that receives the advertisement message or frame may know whether the device 1 300 supports an extended LE packet through a length field included in a header of the advertisement message or frame.
  • the connection request may be transmitted to the device 1 300 based on the information included in the advertisement message or the frame (S720).
  • the data channel PDU payload 910 of the connection request may include an InitA field, an AdvA field, and an LL Data field.
  • the InitA may include an address of a device making a connection request, for example, an address of the device 2 400 of FIG. 7.
  • the LL Data field may include the fields of Table 2 below and the Tx Payload Size, Rx Payload Size, Maximum RX LE Payload Size, and Maximum TX LE Payload Size fields of FIG. 9.
  • the AA field includes an access address for link layer connection.
  • the CRCInt field includes an initial setting value for calculating a CRC (Cyclical Redundancy Check) indicating whether a content of a frame is modified during transmission.
  • CRC Cyclical Redundancy Check
  • the WinSize field may include a value for the length of a section in which actual data can be transmitted and received within a single Connect Interval, and the WinOffset field may include an off set value until the actual Transmit Window is started in the Connect Interval.
  • the Interval field may include an interval between Connect Events.
  • the Latency field is used to terminate the connection when there is no data exchange during a specific event during connection maintenance.
  • the Timeout field includes a time when it is determined that the connection is impossible when the device can no longer connect.
  • the chM field includes information such as a channel used during channel hopping or an unused channel, and the hop field includes a distance value to the next channel when channel hopping in Bluetooth LE.
  • the SCA field may include sleep clock accuracy information of a master device, and accuracy levels are shown in Table 3 below.
  • the Maximum RX LE Payload Size field of FIG. 9 includes a maximum data length that can be received by the device 2 400, and the Maximum TX LE Payload Size field has a maximum data length that can be transmitted by the device 1 300. It may include.
  • the Tx Payload Size and the Rx Payload Size fields include data length information to be used for data transmission and reception determined by negotiation between the device 1 300 and the device 2 400.
  • the minimum value of the maximum received data length received from the device 1 (300) and the maximum transmitted data length of the device 2 (400) may be determined as the Tx Payload Size, and the maximum received from the device 1 (300).
  • the minimum value of the transmission data length and the maximum reception data length that can be provided may be determined as the Rx payload size.
  • Equation 1 is a formula for determining the Tx Payload Size
  • Equation 2 is an equation for determining the Rx Payload Size.
  • the maximum transmission payload value that the device 1 300 can support is 150 and the maximum reception payload value is 150
  • the maximum transmission payload value that the device 2 400 can support is 230
  • the maximum reception payload value is 230.
  • the device 1 (300) transmits the advertisement message or frame having an AdvData Type of 0xF3FB, the Maximum RX LE Payload Size value of 150, and the Maximum TX LE Payload Size value of 150 to the device 2 (400)
  • the device 2 400 may recognize that the length of the reception payload and the length of the transmission payload that the device 1 300 can support is 150 at most.
  • the LL Data field may include the fields of Table 2, the Tx Payload Size field, and the Rx Payload Size field.
  • the device 2 400 sets the RX payload size to 150 and the TX payload size value to 150.
  • the connection request may be transmitted to the device 1 300.
  • the device 1 (300) and the device 2 (400) can extend the payload length through this method, and can transmit and receive data through the extended payload.
  • the device 1 (300) has informed the device 2 (400) to support the extended LE packet through the advertisement message or the advertisement frame, the Maximum of the device 1 (300) The value of RX LE Payload Size and the value of Maximum TX LE Payload Size may not be informed.
  • the device 2 400 attempts to connect with the device 1 300 with a general data length rather than an extended LE packet, and the Maximum RX LE Payload Size of the device 2 400 through a connection request.
  • the value of and the value of the Maximum TX LE Payload Size may be informed to the device 1 (300).
  • the connection is not performed with the extended data length
  • the information of the device 2 400 is transmitted to the device 1 300 in order to extend the data length later.
  • FIGS. 10 and 11 are diagrams illustrating an example of a process and a packet format for negotiating packet length through a scan request and a scan response in a Bluetooth connection process to which the present invention is applied.
  • a Bluetooth LE data length may be extended by providing an extension request and information of a data length through a scan request for requesting additional device information during the Bluetooth LE connection.
  • the device 1 300 when the device 1 300 tries to connect with the device 2 400 through the Bluetooth LE technology, the device 1 300 transmits an advertisement message or a frame to the device 2 400. It may be (S1010).
  • the advertisement message or frame may have the same format as the link layer packet 610 of FIG. 6.
  • the device 1 300 may inform the device 2 400 of this through the length field of the advertisement channel PDU header of FIG. 6.
  • the advertisement channel PDU payload 1110 of the advertisement message or frame may include an AdvA field and an Adv Data field.
  • the AdvA field may include an address of the device 1 300, which is an advertisement device, and the AdvData field may include information of the device 1 300.
  • the AdvData field does not include extended packet length information supported by the device 1 300.
  • the device 2 400 may transmit a scan request to the device 1 300 to obtain extended packet length information supported by the device 1 300 (S1020).
  • the packet format of the scan request is the same as the link layer packet 610 of FIG. 6, and the header may also have the same packet structure as the advertisement channel PDU header 620 of FIG. 6.
  • a long length field in the header of the scan request is used to request data length information supported by the device 1 (300).
  • the scan request PDU payload 1120 of the scan request may include a ScanA field and an AdvA field, wherein the ScanA includes an address of the device 2 400, which is a device requesting information.
  • the AdvA field contains the address of the device 1 (300).
  • the device 1 300 may include information on a packet length supported by the device 1 300 in the scan response and transmit the information to the device 2 400 (S1030).
  • the scan response may include (c) a scan response PDU payload 1130, and the scan response PDU payload 1130 may include an AdvA field including an address of the device 1 300, which is a device that provides scan information. It may include a ScanRspData field including additional information.
  • the Scan RspData field may include a ScanRspData Type field indicating a message type, a Maximum RX LE Payload Size field, and a Maximum TX LE payload Size field.
  • the device 2 400 receiving the scan response negotiates the length of the data packet in the same manner as described in FIGS. 7 to 9, and then performs the Bluetooth connection with the negotiated new data length.
  • the connection request may be transmitted to 1 (300) (S1040).
  • the device 2 400 is an RX / TX payload. You can negotiate size to 150.
  • the data channel PDU payload format of the connection request is the same as that of FIG. 9, and the format of the LL data includes the fields of Table 1, the Tx Payload Size field, the Rx Payload Size field, the Maximum RX LE Payload Size field, and It may include a Maximum TX LE Payload field.
  • a connection request is made in an extended data length format.
  • a packet having an extended data length can be used than the existing data packet length.
  • the number of packet transmissions and data This reduces the transmission time and reduces the power consumed by the device.
  • 12 to 14 illustrate another example of a process and a packet format for negotiating packet length through a scan request and a scan response in a Bluetooth connection process to which the present invention is applied.
  • the device 1 300 may inform a neighboring device whether an extended data packet is supported to an adjacent device through an advertisement, and the device 2 400 may transmit the device 1 (300). ) And an extended data packet format for Bluetooth connectivity.
  • the device 1 300 when the device 1 300 tries to connect with the device 2 400 through Bluetooth LE technology, the device 1 300 sends an advertisement message or frame to the device 2 400. It may transmit (S1210).
  • the advertisement message or frame has the same format as the link layer packet 610 of FIG. 6, and when the device 1 300 supports an extended link layer PDU, the length field of the advertisement channel PDU header of FIG. 6 is set. This can be informed to the device 2 (400).
  • the advertisement message or frame may include an advertisement channel PDU payload 1310, and the advertisement channel PDU payload 1410 may include an AdvaA field and an AdvData field.
  • the AdvData field does not include extended packet length information supported by the device 1 300.
  • the device 2 400 may transmit a scan request to the device 1 300 in order to obtain additional information of the device 1 300 (for example, the extended packet length information) (S1220).
  • additional information of the device 1 300 for example, the extended packet length information
  • the packet format of the scan request is the same as the link layer packet 610 of FIG. 6, and the header may also have the same packet structure as the advertisement channel PDU header 620 of FIG. 6.
  • a long length field in the header of the scan request is used to request data length information supported by the device 1 (300).
  • the scan request includes a scan request PDU payload 1320, and the scan request PDU payload 1320 may include a ScanA field, an AdvA field, and a ScanReqData field.
  • the ScanReqData field includes extended packet length information supported by the device 2 400 from the device 2 400 to the device 1 300.
  • the ScanReqData field may include a ScanReqData Type field indicating a type of the ScanReqData, a Maximum RX LE Payload Size field, and a Maximum TX LE Payload Size field.
  • the Maximum RX LE Payload Size field includes maximum received data length information supported by the device 2 400, and the Maximum TX LE Payload Size field includes maximum transmitted data length information supported by the device 2 400. do.
  • the device 1 300 may include packet length information supported by the device 1 in the scan response and transmit it to the device 2 400 (S1230).
  • the scan response may include (c) a scan response PDU payload 1330, and (c) the scan response PDU payload 1330 may be an address of the device 1 300 that is a device that provides scan information, and It may include a ScanRspData field including scan information.
  • the Scan RspData field may again include a ScanRspData Type indicating a message type, a Maximum RX LE Payload Size field, and a Maximum TX LE payload Size field.
  • the device 2 400 After receiving the scan response, the device 2 400 negotiates the length of the data packet in the same manner as described with reference to FIGS. 7 to 9, and then requests a connection to the device 1 300 with the negotiated new data length. It may transmit (S1240).
  • the connection request may include a data channel PDU payload 1410, and the data channel PDU payload may include an InitA field, an AdvA field, and an LL Data field.
  • the LL Data field may include a field of Table 2, a Tx Payload Size field, and an Rx Payload Size field.
  • the Tx Payload Size field may include negotiated new transmission data length information
  • the Rx Payload Size field may include negotiated new received data length information
  • the device 1 (300) finds that the device 1 (300) supports the extended packet through the advertisement of the device 1 (300), the device 2 (400) may support the device 1 (300).
  • a scan request including information of 150 octets may be transmitted.
  • the device 1 300 may transmit a scan response including information that the maximum transmit / receive data length that can be supported to the device 2 400 is 170 octets in response to the scan request.
  • the device 2 400 may determine 150 octets, which is a minimum value of the maximum transmit / receive data length of the device 1 300 and its maximum transmit / receive data length, as an extended data length, and request a connection request including the determined value. It may transmit to the device 1 (300).
  • 15 and 16 illustrate examples of a process and a packet format for using an extended scan response through packet length negotiation in a Bluetooth connection process to which the present invention is applied.
  • a scan response message may be transmitted using the extended data packet according to whether the extended data packet is supported in the Bluetooth connection process.
  • the device 1 300 may transmit an advertisement message or a frame to the device 2 400. There is (S1510).
  • the advertisement message or frame has the same format as the link layer packet 610 of FIG. 6, and when the device 1 300 supports an extended link layer PDU, the advertisement channel PDU header 620 of FIG. This may be informed to the device 2 400 through a length field.
  • the PDU Type field of the advertisement channel PDU header may have a value of “0110” which is a value of ADV_SCAN_IND indicating a scanable non-directional advertisement event in Table 1 above.
  • the advertising message or frame may include (a) an advertising channel PDU payload 1610, and the advertising channel PDU payload 1610 may include an AdvA field and an Adv Data field.
  • the AdvData field may include an AdvData Type indicating a type of the advertisement message or frame, a Maximum RX LE Payload Size field indicating a maximum data length that can be received, and a Maximum TX LE Payload Size field indicating a maximum data length that can be transmitted.
  • the device 2 400 Since the device 2 400 has received an advertisement message or a frame capable of a scan request from the device 1 300, the device 2 400 transmits a scan request to the device 1 300 to request additional information of the device 1 300. It may be (S1520).
  • the scan request may include (b) a scan request PDU Payload 1620, and the scan request PDU Payload 1620 may include a ScanA field, an AdvA field, or a ScanReqData field.
  • the ScanReqData field is a field including information on the maximum data length that the device 2 400 can support, and may include a ScanReqData Type field, a Maximum RX LE Payload Size field, and a Maximum TX LE Payload Size field.
  • the ScanReqData Type field includes information about the data type of the scan request
  • the Maximum RX LE Payload Size field includes information about the maximum received data packet length that the device 2 400 can support.
  • the Maximum TX LE Payload Size field includes information on the length of a maximum received data packet that can be supported by the device 2 400.
  • the device 1 (300) receiving the scan request is based on information on the maximum data packet length supported by the device 2 (400) included in the scan request and the maximum data packet length supported by the device 1 (300).
  • the extended received data length and the extended transmitted data length can be negotiated with.
  • the device 1 300 may use the equation 1 and the equation 2 to expand the received data length or the minimum value among the maximum supportable transmission or reception data lengths of the device 1 300 and the device 2 400. Can negotiate with extended transmission data length.
  • the device 1 300 when the length of the maximum transmit / receive data packet that the device 1 300 can support is 150 octets and the length of the maximum transmit / receive data packet that the device 2 400 can support is 130 octets, the device 1 300 ) May determine the extended transmit / receive data length to 130 octets.
  • the device 1 300 may transmit a scan response to the device 2 400 using a data format to which the extended data packet length is applied (S1530).
  • the scan response may include (c) a scan response PDU Payload 1630, and the scan response PDU Payload 1630 may include an AdvA field and a ScanRspData field.
  • the ScanRspData field may have a length (eg, 130 octets) equal to the value of the extended transmission data length negotiated by the device 1 (300).
  • 17 and 18 are diagrams illustrating a process and a packet format for changing a packet length after a Bluetooth connection to which the present invention is applied.
  • the negotiated transmission / reception data length may be changed during data transmission / reception.
  • the device 1 300 may transmit an advertisement message or a frame to establish a Bluetooth connection (S1710).
  • the advertisement message or frame has the same packet format as the format described with reference to FIGS. 6 and 8.
  • the device 2 400 that receives the advertisement message or frame may transmit a scan request to the device 1 300 when necessary (eg, when additional information is needed).
  • the device 2 400 receiving the scan request may transmit a scan response to the device 1 300.
  • the device 2 400 transmits a connection request including information for the Bluetooth connection to the device 1 300 to perform a Bluetooth connection (S1720).
  • the device 1 300 and the device 2 400 may negotiate the extended transmission / reception data packet length through one of the methods described with reference to FIGS. 7 to 16.
  • the device 1 400 transmits and receives data using the data packet to which the length of the negotiated transmit / receive data packet is applied, the device 1 400 needs to change the length of the transmit / receive data packet.
  • the device 1 300 transmits a maximum data length change request 1810 to the device 2 400 (S1730).
  • the maximum data length change request 1810 may include an Op Code field and a CtrData field.
  • the Op Code field indicates the type of a LL control packet that transmits a Bluetooth control command and may have a value shown in Table 4 below.
  • the Op Code field may have a value of '0x14' shown in Table 4 because the Op Code field is a control packet transmission for changing the maximum transmission / reception data length.
  • the CtrData field may include an RX LE Payload Size field including information about the length of the received data to be changed, and a TX LE Payload Size field including information about the length of the transmission data to be changed.
  • the device 2 400 may transmit a maximum data length change response 1820 to the device 1 300 to change the maximum data length (S1740).
  • the maximum data length change response 1820 may include an Op Code field and a Ctr Data field.
  • the op code is an op code of a response to a request for changing the maximum data length
  • the op code may include a value '0x15' of Table 2.
  • the Ctr Data field may include an Rsp Code field, an RX LE Payload Size field, and a TX LE Payload Size field.
  • the Rsp Code field may include information related to whether the device 2 (400) is allowed for the request for changing the maximum data length of the device 1 (300), and OK (change allowed), NEW (provide a new value), and reject (Not acceptable), and the like.
  • the RX LE Payload Size field and the TX LE Payload Size field include length information of the transmission / reception data packet changed by the device 2 400 based on the change request of the device 1 300.
  • the device 2 400 sends a value of the RX LE Payload Size field and the TX LE Payload Size field to the device 2 400.
  • the maximum data length change request can be transmitted with 150 octets each.
  • the Rsp code is allowed to be changed. It can be set to an OK value indicating.
  • the device 2 400 may set the Rsp code to a reject value indicating no acceptance.
  • the CtrData of the maximum data length change response 1820 may not include the RX LE Payload Size field and the TX LE Payload Size field values. Can be.
  • the device 2 400 wants to change the transmission / reception data length to 180 octets, which is larger than the value to be changed by the device 1 300, the new transmission / reception data length value and the Rsp code value are set to New.
  • the maximum data response may be transmitted to the device 1 300.
  • the device 1 300 may determine whether to allow the newly proposed data length value.
  • the device 1 300 may determine whether the device 2 400 re-suggests the data length value again, whether OK (change allowed), NEW (provides a new value), or reject (not acceptable).
  • the device 1 300 may change the maximum transmission / reception data length by transmitting a maximum data length change response to the device 2 400.
  • the device 1 (300) is possible only when transmitting data 180, which is the maximum data length value provided by the device 2 (400), the device 1 (300) is OK, RX LE Payload Size
  • the maximum data change response may be transmitted to the device 2 400 using a field value of 150 and a TX LE Payload Size field value of 180.
  • the data packet length negotiated after the Bluetooth connection step or the Bluetooth connection can be extended or shortened.
  • the data packet length change procedure extends the data length after the Bluetooth connection. To change the length of data, the procedure was performed.
  • the data packet length change procedure reduces the data length after the Bluetooth connection. To change the data length, the procedure was performed.
  • This change in data length may occur as necessary in the process of transmitting and receiving data after the Bluetooth connection.
  • the data length may be extended through a data length change procedure. Can be.
  • the data packet length can be reduced through the data length change procedure.
  • 19 and 20 are diagrams illustrating a process for extending a packet length after a Bluetooth connection and a packet format thereof according to the present invention.
  • the packet length may be negotiated to adjust the packet length.
  • the device 1 300 and the device 2 400 exist in an unconnected state not connected to each other (S1900).
  • the device 1 (300) transmits an advertisement message or frame containing its information to the device 2 (400) for Bluetooth connection (S1910). ).
  • the device 2 400 Upon receiving the advertisement message or frame, the device 2 400 transmits a connection request to the device 1 300 to establish a Bluetooth connection when the device 1 300 to which the device 1 300 is connected is correct (S1920). .
  • connection request is a message for the master device to perform a connection procedure with the corresponding slave device in the unconnected state, and at this time, all schedule parameter values used in the connected state can be set.
  • -Transmit Window Size It means the length of the interval that real data can be transmitted and received within a single Connect Interval. At least one packet must be transmitted and received.
  • Window_offset The offset until the actual Transmit Window starts in the Connect Interval.
  • Connect Interval Interval between Connect Events.
  • the device 1 (300) receiving the connection request attempts to establish a Bluetooth connection by setting the schedule parameter value with the device 2 (400), and when connected, the device 1 (300) and the device 2 (400) connect. It becomes a state (S1930).
  • the device 1 300 and the device 2 400 in the connected state may transmit and receive data, request and provide specific control information through a control packet, or instruct a specific operation.
  • Bluetooth LE technology typically uses short data packets. Therefore, in order to use the extended packet, one of the two devices may request the data packet extension. Before that, it is necessary to confirm whether the counterpart device supports the extended data packet.
  • the device 1 300 may transmit a feature request to the device 2 400 to determine whether to support the extended data packet (S1940).
  • the device 2 400 may inform the device 1 300 of whether the extended data packet is supported through a Feature Response (S1950).
  • the device 1 300 makes a length extension request to the device 2 400 to expand the data packet (S1960).
  • the Length Extension request 2010 may include an Op Code field and a CtrData field, and the Op Code may have a value of '0x14' shown in Table 2 above.
  • the CtrData field may include a MaxRxLen field, a MaxRxTime field, a MaxTxLen field, and a MaxTxTime field.
  • the MaxRxLen field may include length information of a maximum received data packet supported by the device 1 300, and the length of the maximum data packet may be expressed as an octet value.
  • the MaxRxtime field includes transmission time information of a maximum received data packet that can be supported by the device 1 (300).
  • the MaxTxLen field includes length information of the maximum transmission data packet that the device 1 300 can support, and the length of the maximum data packet may be expressed as an octet value.
  • the MaxTxTime field includes transmission time information of a maximum transmission data packet that can be supported by the device 1 (300).
  • the device 2 400 Upon receiving the Length Extension request 2010, the device 2 400 transmits a Length Extension response to the device 1 300 (S1970).
  • the Length Extension response may have the same packet format as the Length Extension request.
  • the Op Code may have a value of '0x15' of Table 2.
  • the device 1 300 and the device 2 400 may obtain the maximum data packet information supported by the other device through the length extension request 2010 and the length extension response. You can negotiate.
  • the device 1 (300) and the device 2 (400) negotiate the minimum value of the lengths of the transmit and receive data packets supported by the device and the counterpart device to the length of the extended transmit / receive packet, and the data transmit / receive time supported by the device and the counterpart device.
  • the device 1 300 sends a message to the device 2 400 to change the Transmit Window Size.
  • the Window Size Update request may be transmitted (S1980).
  • the Window Size Update request 2020 includes an Op Code field and a CtrData field.
  • the Op Code may have a value of '0x16'.
  • the CtrData field may include a Window Size field and a Connect Interval field.
  • the Window Size may include Window Size information to be changed to transmit and receive an extended packet
  • the Connect Interval field may include Interval information between Connect Events for the changed Window Size.
  • the device 2 400 may transmit a response to the device 1 300 to perform Window Size Update (S1990).
  • the device 1300 and the device 2 400 expand or extend the length of the data packet through the maximum data length changing procedure of FIG. 17. Can be shrunk.
  • the length of a data packet can be extended and changed even after a Bluetooth connection, and the schedule parameter can be changed according to the length of the data packet.
  • the length of the data packet can be reduced again, so that the length of the data packet can be flexibly changed according to the situation.
  • the present invention provides a method for changing the data rate in a wireless communication system.
  • the present invention provides a method and apparatus for changing a data rate by changing a length of a data packet in a Bluetooth communication, which is a short range wireless communication technology.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé et un dispositif pour étendre le longueur du paquet de données dans une communication Bluetooth, le procédé comprenant les étapes consistant : à effectuer une connexion Bluetooth par un premier dispositif et un second dispositif ; à transmettre un message de requête d'extension pour demander l'extension d'une longueur de données de transmission et d'une longueur de données de réception par l'intermédiaire du Bluetooth connecté ; et à recevoir un message de réponse d'extension, le message de requête comprenant des premières informations de longueur de données de transmission maximale, des premières informations de longueur de données de réception maximale, des premières informations de temps de transmission maximal et/ou des premières informations de temps de réception maximal du premier dispositif, et le message de réponse comprenant des secondes informations de longueur de données de transmission maximale, des secondes informations de longueur de données de réception maximale, des secondes informations de temps de transmission maximal et/ou des secondes informations de temps de réception maximal du second dispositif.
PCT/KR2014/012070 2014-03-12 2014-12-09 Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil Ceased WO2015137601A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US15/125,498 US10219183B2 (en) 2014-03-12 2014-12-09 Method and device for adjusting data transmission rate in wireless communication system
CN201480077076.2A CN106105310B (zh) 2014-03-12 2014-12-09 无线通信系统中调整数据传输速率的方法和设备
JP2016556251A JP6374526B2 (ja) 2014-03-12 2014-12-09 無線通信システムにおけるデータ送信率調節方法及び装置
KR1020167023647A KR101869070B1 (ko) 2014-03-12 2014-12-09 무선통신 시스템에서 데이터 전송률 조절 방법 및 장치

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201461951547P 2014-03-12 2014-03-12
US61/951,547 2014-03-12

Publications (1)

Publication Number Publication Date
WO2015137601A1 true WO2015137601A1 (fr) 2015-09-17

Family

ID=54072004

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/012070 Ceased WO2015137601A1 (fr) 2014-03-12 2014-12-09 Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil

Country Status (5)

Country Link
US (1) US10219183B2 (fr)
JP (1) JP6374526B2 (fr)
KR (1) KR101869070B1 (fr)
CN (1) CN106105310B (fr)
WO (1) WO2015137601A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105635943A (zh) * 2015-12-21 2016-06-01 中颖电子股份有限公司 一种基于低功耗蓝牙技术的数据交互方法以及采用该方法的信标装置和信标数据交互装置
CN106060962A (zh) * 2016-06-22 2016-10-26 杭州华三通信技术有限公司 一种通信方法及装置
KR20170037304A (ko) * 2015-09-25 2017-04-04 삼성전자주식회사 전자 장치 및 그 연결 방법
CN109076624A (zh) * 2016-05-13 2018-12-21 华为技术有限公司 无线连接建立方法及设备
WO2020055046A1 (fr) * 2018-09-13 2020-03-19 엘지전자 주식회사 Système de gestion de batterie sans fil de véhicule
US11601995B2 (en) 2018-09-13 2023-03-07 Lg Electronics Inc. Wireless battery management system for vehicle

Families Citing this family (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9924342B2 (en) 2015-06-16 2018-03-20 Google Llc Establishing a connection over a low power communication type
KR101673308B1 (ko) * 2015-08-20 2016-11-07 현대자동차주식회사 블루투스 듀얼모드를 이용한 블루투스 자동 연결 방법 및 장치
WO2018169671A1 (fr) * 2017-02-27 2018-09-20 Mavenir Networks, Inc. Système et procédé pour une installation radio distante à câblage réseau
DE102018202176B4 (de) * 2018-02-13 2025-06-12 Bayerische Motoren Werke Aktiengesellschaft Master-Slave-System zur Kommunikation über eine Bluetooth-Low-Energy-Verbindung
JP7081220B2 (ja) * 2018-03-06 2022-06-07 日本電気株式会社 制御装置、無線通信装置、使用チャネル決定方法、及び制御プログラム
JP2019169839A (ja) * 2018-03-23 2019-10-03 カシオ計算機株式会社 無線通信装置、無線通信方法、及びプログラム
CN110661964A (zh) * 2018-06-28 2020-01-07 佳能株式会社 摄像设备、配件设备及其通信控制方法和存储介质
CN116193247B (zh) 2018-06-28 2025-05-27 佳能株式会社 摄像设备、配件设备及其通信控制方法和存储介质
KR102600892B1 (ko) * 2018-08-08 2023-11-10 삼성전자주식회사 블루투스 저전력을 이용하여 통신을 수행하는 장치 및 방법
US11120811B2 (en) * 2018-08-29 2021-09-14 Qualcomm Incorporated Power optimized link quality detection and feedback
CN112640505B (zh) * 2018-12-22 2022-04-26 华为技术有限公司 一种传输速率的控制方法及设备
CN109587733A (zh) * 2019-01-18 2019-04-05 苏州德姆斯信息技术有限公司 低功耗无线通讯传输方法
KR102652380B1 (ko) * 2019-03-05 2024-03-29 삼성전자주식회사 블루투스 네트워크 환경에서 응답 메시지를 전송하기 위한 전자 장치 및 그에 관한 방법
WO2020213959A1 (fr) * 2019-04-16 2020-10-22 엘지전자 주식회사 Procédé de réception de données audio à l'aide d'une technologie bluetooth et appareil associé
CN110213758B (zh) * 2019-06-13 2022-10-04 桃芯科技(苏州)有限公司 基于蓝牙Mesh的数据通信方法、存储介质和电子设备
KR20210017327A (ko) * 2019-08-07 2021-02-17 삼성전자주식회사 전자 장치 간의 빠른 통신을 위한 방법 및 장치
US11153038B2 (en) * 2019-11-22 2021-10-19 Qualcomm Incorporated MIC recovery of BR/EDR links
US10911923B1 (en) * 2020-01-15 2021-02-02 Schlage Lock Company Llc Technologies for implementing unified mode bluetooth advertisements
US11357020B2 (en) * 2020-02-06 2022-06-07 International Business Machines Corporation Connecting computer processing systems and transmitting data
US11405766B2 (en) 2020-02-06 2022-08-02 International Business Machines Corporation Connecting computer processing systems and transmitting data
CN111065084A (zh) * 2020-02-25 2020-04-24 北京百瑞互联技术有限公司 一种提高低功耗蓝牙传输速度的方法
CN111542038A (zh) * 2020-05-14 2020-08-14 浙江强脑科技有限公司 具有时间同步功能的蓝牙组网系统
CN113709055B (zh) * 2020-05-20 2023-12-05 安徽华米信息科技有限公司 基于ble的通讯方法、装置、设备、系统以及存储介质
CN111654450B (zh) * 2020-05-28 2023-08-08 北京小米移动软件有限公司 数据传输方法及装置、存储介质
KR102221849B1 (ko) * 2020-06-09 2021-03-03 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR102792594B1 (ko) * 2020-07-31 2025-04-08 주식회사 모카시스템 리더기 및 그 제어 방법
CN112566082B (zh) * 2020-11-16 2023-01-24 深圳市元征科技股份有限公司 数据传输方法、装置、设备及介质
US12408080B2 (en) * 2021-06-17 2025-09-02 Cypress Semiconductor Corporation Data flow management in wireless networks
US12349083B2 (en) 2021-06-17 2025-07-01 Cypress Semiconductor Corporation Device synchronization and connection management in wireless networks
US20230171331A1 (en) * 2021-11-30 2023-06-01 Texas Instruments Incorporated Bluetooth low energy connection power consumption
CN114827887B (zh) * 2022-03-31 2022-12-30 远峰科技股份有限公司 一种基于蓝牙AoA定位测距时序同步数字钥匙定位系统
CN117992091B (zh) * 2024-04-02 2024-06-07 深圳朗田亩半导体科技有限公司 一种基于文件特征描述的固件升级方法和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090245279A1 (en) * 2008-03-31 2009-10-01 Mediatek Inc. Apparatus and method for coordinating bluetooth and wireless local area network (wlan) and wimax communications
US20100020729A1 (en) * 2008-07-28 2010-01-28 John Walley Method and system for half duplex audio in a bluetooth stereo headset
WO2012033340A2 (fr) * 2010-09-07 2012-03-15 비씨카드 주식회사 Procédé et système pour la communication bluetooth
WO2012096546A2 (fr) * 2011-01-14 2012-07-19 삼성전자 주식회사 Procédé et appareil de transmission d'entrée d'utilisateur de dispositif collecteur à dispositif source dans système de communication direct wi-fi
US20140059235A1 (en) * 2012-08-22 2014-02-27 Nokia Corporation Method and apparatus for utilizing advertisements to provide information regarding connection setup

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7471681B2 (en) 2002-10-10 2008-12-30 Intel Corporation Determining network path transmission unit
US20060155856A1 (en) * 2003-01-10 2006-07-13 Sharp Kabushiki Kaisha Communications device, network system, communication management method, request signal, response signal, program, and recording medium containing the program
CN102006215B (zh) 2009-09-01 2012-08-01 中国移动通信集团公司 一种数据传输方法、系统及设备
CN102726093B (zh) * 2010-02-02 2016-08-03 马维尔国际贸易有限公司 通信设备中的节电特征
CN101841394B (zh) 2010-06-09 2012-08-08 中南大学 一种测算蓝牙设备文件传输能耗的方法及装置
US20120052802A1 (en) 2010-08-24 2012-03-01 Nokia Corporation Advertisement of an existing wireless connection
US8971800B2 (en) * 2011-05-31 2015-03-03 Qualcomm Incorporated Methods and apparatus for improving NFC activation and data exchange reporting mechanisms
US8989658B2 (en) * 2011-06-24 2015-03-24 Qualcomm Incorporated Methods and apparatuses for improving NFC parameter update mechanisms
US9113284B2 (en) * 2011-08-26 2015-08-18 Qualcomm Incorporated Methods and apparatus for improving management of NFC logical connections
US9445305B2 (en) * 2011-09-12 2016-09-13 Microsoft Corporation Low energy beacon encoding
US9706496B2 (en) * 2011-10-31 2017-07-11 Avago Technologies General Ip (Singapore) Pte. Ltd Concurrent BLE scanning and initiation for bandwidth efficiency and power saving
CN104488348B (zh) * 2012-06-01 2018-04-24 诺基亚技术有限公司 用于无线网络中的自适应设备发现的方法、装置和计算机程序产品
US9628979B2 (en) * 2012-08-22 2017-04-18 Nokia Technologies Oy Method and apparatus for utilizing advertisements in conjunction with device discovery

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090245279A1 (en) * 2008-03-31 2009-10-01 Mediatek Inc. Apparatus and method for coordinating bluetooth and wireless local area network (wlan) and wimax communications
US20100020729A1 (en) * 2008-07-28 2010-01-28 John Walley Method and system for half duplex audio in a bluetooth stereo headset
WO2012033340A2 (fr) * 2010-09-07 2012-03-15 비씨카드 주식회사 Procédé et système pour la communication bluetooth
WO2012096546A2 (fr) * 2011-01-14 2012-07-19 삼성전자 주식회사 Procédé et appareil de transmission d'entrée d'utilisateur de dispositif collecteur à dispositif source dans système de communication direct wi-fi
US20140059235A1 (en) * 2012-08-22 2014-02-27 Nokia Corporation Method and apparatus for utilizing advertisements to provide information regarding connection setup

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20170037304A (ko) * 2015-09-25 2017-04-04 삼성전자주식회사 전자 장치 및 그 연결 방법
KR102393286B1 (ko) * 2015-09-25 2022-05-02 삼성전자주식회사 전자 장치 및 그 연결 방법
CN105635943A (zh) * 2015-12-21 2016-06-01 中颖电子股份有限公司 一种基于低功耗蓝牙技术的数据交互方法以及采用该方法的信标装置和信标数据交互装置
CN105635943B (zh) * 2015-12-21 2020-02-28 中颖电子股份有限公司 低功耗蓝牙信标数据交互装置、信标装置及方法
CN109076624A (zh) * 2016-05-13 2018-12-21 华为技术有限公司 无线连接建立方法及设备
EP3451784A4 (fr) * 2016-05-13 2019-05-15 Huawei Technologies Co., Ltd. Procédé et appareil permettant d'établir une connexion sans fil
US10764408B2 (en) 2016-05-13 2020-09-01 Huawei Technologies Co., Ltd. Method for establishing wireless connection and device
CN106060962A (zh) * 2016-06-22 2016-10-26 杭州华三通信技术有限公司 一种通信方法及装置
CN106060962B (zh) * 2016-06-22 2020-01-03 新华三技术有限公司 一种通信方法及装置
WO2020055046A1 (fr) * 2018-09-13 2020-03-19 엘지전자 주식회사 Système de gestion de batterie sans fil de véhicule
US11395119B2 (en) 2018-09-13 2022-07-19 Lg Electronics Inc. Wireless battery management system for vehicle
US11601995B2 (en) 2018-09-13 2023-03-07 Lg Electronics Inc. Wireless battery management system for vehicle

Also Published As

Publication number Publication date
JP2017513309A (ja) 2017-05-25
JP6374526B2 (ja) 2018-08-15
CN106105310A (zh) 2016-11-09
KR20160114671A (ko) 2016-10-05
US10219183B2 (en) 2019-02-26
CN106105310B (zh) 2019-09-17
KR101869070B1 (ko) 2018-07-19
US20170086098A1 (en) 2017-03-23

Similar Documents

Publication Publication Date Title
WO2015137601A1 (fr) Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil
WO2018222024A1 (fr) Procédé et appareil permettant de connecter des dispositifs à l'aide de la technologie bluetooth à faible consommation d'énergie
WO2020096412A1 (fr) Procédé et appareil de réception de données audio en utilisant la technologie bluetooth
WO2015163680A1 (fr) Procédé et appareil pour transmettre et recevoir des données à l'aide d'une technique bluetooth à faible consommation d'énergie dans un système de communication sans fil
WO2018074892A1 (fr) Procédé et dispositif d'émission et de réception de données à l'aide de la technologie bluetooth
WO2015194854A1 (fr) Procédé et appareil d'établissement d'une connexion entre des dispositifs à l'aide d'une technologie bluetooth à faible énergie énergie (le)
WO2016182404A1 (fr) Procédé et dispositif destinés à la connexion de moyens de communication de remplacement à l'aide de la technologie bluetooth à faible énergie
WO2015069093A1 (fr) Procédé et appareil de connexion bluetooth
WO2017030232A1 (fr) Procédé pour transmettre et recevoir des données, et dispositif associé
WO2018021877A1 (fr) Procédé et appareil d'établissement de connexion à un dispositif
WO2016039598A1 (fr) Procédé et dispositif destinés à commander un dispositif en utilisant la technologie bluetooth
WO2016178542A1 (fr) Procédé et appareil pour envoyer et recevoir des données par bluetooth
WO2014204272A1 (fr) Procédé et appareil pour reproduire des contenus multimédias à l'aide de bluetooth dans un système de communication sans fil
WO2016017907A1 (fr) Procédé et appareil de commande d'un dispositif électronique dans un système de communication sans fil prenant en charge une communication bluetooth
WO2016175454A1 (fr) Procédé et dispositif de transmission/réception de données utilisant un réseau maillé bluetooth
WO2022124870A1 (fr) Procédé d'émission et de réception de données et dispositif destiné audit procédé dans un système de communication sans fil à courte portée
WO2015182896A1 (fr) Procédé et appareil de connexion bluetooth
WO2019031822A1 (fr) Procédé et appareil permettant d'établir une connexion entre des dispositifs à l'aide d'une technologie bluetooth a faible énergie
WO2018135926A1 (fr) Procédé et appareil de communication bluetooth
WO2017018604A1 (fr) Procédé et dispositif de connexion de moyen de communication de substitution à l'aide de la technique bluetooth basse consommation (le)
WO2021096257A1 (fr) Procédé de transmission de données audio à l'aide d'une communication de courte portée dans un système de communication sans fil, et dispositif associé
WO2017043869A1 (fr) Procédé et appareil de commande de dispositifs au moyen de la technologie bluetooth
WO2016036206A2 (fr) Procédé et dispositif de commande d'un dispositif à l'aide d'une technique bluetooth à basse énergie (le)
WO2019235892A1 (fr) Procédé et appareil de commande de puissance d'un dispositif au moyen d'une technologie bluetooth
WO2019031870A1 (fr) Procédé et appareil pour appeler un service de reconnaissance vocale à l'aide d'une technologie bluetooth à basse énergie

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14885443

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20167023647

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2016556251

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15125498

Country of ref document: US

122 Ep: pct application non-entry in european phase

Ref document number: 14885443

Country of ref document: EP

Kind code of ref document: A1