WO2015163547A1 - 무선 통신시스템에서 블루투스를 이용하여 http 데이터를 전송하기 위한 방법 및 장치 - Google Patents
무선 통신시스템에서 블루투스를 이용하여 http 데이터를 전송하기 위한 방법 및 장치 Download PDFInfo
- Publication number
- WO2015163547A1 WO2015163547A1 PCT/KR2014/009694 KR2014009694W WO2015163547A1 WO 2015163547 A1 WO2015163547 A1 WO 2015163547A1 KR 2014009694 W KR2014009694 W KR 2014009694W WO 2015163547 A1 WO2015163547 A1 WO 2015163547A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- http
- client device
- request
- data
- response
- Prior art date
Links
Images
Classifications
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
Definitions
- the present invention relates to a data transmission method, and more particularly, to a method and apparatus for transmitting HTTP data using Bluetooth, a short-range wireless communication technology.
- Bluetooth is a proposed Radio Frequency (RF) specification for the transmission of short range, point-to-multipoint voice and data.
- RF Radio Frequency
- Bluetooth can transmit through solid, nonmetallic materials.
- the transmission range is 10cm to 10m, but can be extended to 100m by increasing the transmission power. It is based on a low cost, short range wireless link and facilitates ad hoc connectivity in fixed and mobile communication environments.
- Bluetooth uses the same ISM band, 2.45GHz frequency as 802.11b / g, which is a wireless LAN standard.Bluetooth devices can perform wireless communication by searching, selecting, and authenticating Bluetooth devices in the vicinity. have.
- 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.
- Bluetooth has begun to become popular with the addition of the Enhanced Data Rate (EDR) standard to the 2.0 version, which has ensured a certain level of communication quality.
- EDR Enhanced Data Rate
- Bluetooth is becoming common, for example, listening to music wirelessly through Bluetooth communication with a Bluetooth headset.
- the frequency of use of the music is increasing, such as playing music through smartphone-car speaker interworking using Bluetooth or playing music through Bluetooth docking speaker-smartphone interlocking.
- WPAN Wireless Personal Area Network
- WPAN Wireless Personal Area Network
- Home Network Small Office
- Vehicular Network Vehicular Network
- WPAN is widely used because it provides real-time A / V Streaming service through electronic devices such as a headset within a limited bandwidth and maximizes energy efficiency even when performing a remote control function.
- An object of the present invention is to provide a method and apparatus for smoothly transmitting HTTP data using Bluetooth low energy technology in a wireless communication system.
- An object of the present invention is to provide a method and apparatus for distinguishing devices transmitting HTTP data using Bluetooth low energy technology in a wireless communication system.
- An object of the present invention is to provide a method and apparatus for resolving an error that occurs when transmitting HTTP data using Bluetooth low energy technology in a wireless communication system.
- An object of the present invention is to provide a method and apparatus for transmitting an error message for solving an error occurring when HTTP data is transmitted using Bluetooth low energy technology in a wireless communication system.
- An object of the present invention is to provide a method and apparatus for determining a data transmission method when HTTP data is transmitted using Bluetooth low energy technology in a wireless communication system.
- An object of the present invention is to provide a method and apparatus for providing information of transmitted data when HTTP data is transmitted using Bluetooth low energy technology in a wireless communication system.
- a method comprising: receiving a first write request including information related to a Hyper Text Transfer Protocol (HTTP) request from a first client device; Transmitting the HTTP request related information generated based on the information included in the received first write request, to a web server; Receiving an HTTP response message in response to the HTTP request related information from the web server; Notifying the first client device of an HTTP status code indicating an status of data included in the received HTTP response message; And receiving a read request for requesting data transmission based on information included in the HTTP status code from the first client device, wherein the first write request is received.
- HTTP Hyper Text Transfer Protocol
- the error response indicates that the gateway is performing an operation for generating the HTTP request related information with the first client device, or the gateway generates the HTTP request related information. It is characterized by indicating that the resource is not sufficient because the operation to perform.
- receiving the first write request may include receiving a Universal Resource Identifier (URI) write request from the first client device; Sending a URI write response to the first client device in response to the received URI write request; Receiving an HTTP Header write request from the first client device; Sending an HTTP header write response to the first client device in response to the received HTTP Header write request; Receiving an HTTP Entity Body write request from the first client device; Sending an HTTP Entity Body response to the first client device in response to the received HTTP Entity Body write request; Receiving an HTTP Control Point request indicative of a specific action associated with the HTTP request message from the first client device; And transmitting an HTTP Control Point response to the first client device in response to the received HTTP Control Point request.
- URI Universal Resource Identifier
- receiving the read request may include: receiving an HTTP header read request from the first client device; Transmitting an HTTP header read response to the first client device in response to an HTTP header read request; Receiving an HTTP Entity Body read request from the first client device; And transmitting an HTTP Entity Body read response to the first client device in response to an HTTP Entity Body read request.
- the data may include at least one of a header or an entity body received from the web server.
- HTTP Status Code is characterized in that it contains information related to the length of the data.
- HTTP Status Code is characterized in that the notification (Notify) together with the information related to the data length.
- the information related to the data length includes a value of 0 or 1, and when the information related to the data length is 0, it indicates that the data exists, and the information related to the data length is 1
- the length of the data exceeds the maximum data transmission length, characterized in that transmitted by the maximum data transmission length.
- the information related to the data length includes the data length, and if the length of the data is equal to or smaller than the ATT_MTU-2 value, the data is transmitted to the first client device through a read request procedure.
- the ATT_MTU-2 value may indicate a maximum data length that can be transmitted at one time through a read request procedure.
- the information related to the data length includes the data length, and if the length of the data exceeds the ATT_MTU-2 value and is equal to or smaller than the maximum ATT data length, read blob
- the data is transmitted to the first client device through a request procedure, wherein the maximum ATT data length indicates a maximum size of data that can be transmitted through an attribute protocol.
- the information related to the data length includes the data length, and if the length of the data exceeds the maximum ATT Data Length, L2CAP Logical Link Control and Adaptation Protocol Connection Oriented And transmitting the data to the first client device through a channel.
- the present invention also includes receiving a request message requesting a client ID value from the first client device; Sending a response message in response to the request message; And when the client ID value is NULL, receiving a change request message requesting a change from the first client device to the first client device information.
- the first client device information may include at least one of a user ID and an ID of the first client device.
- the present invention may further include notifying the changed client ID to other client devices connected to the gateway.
- the changed client ID is changed to NULL after a request from the first client or a specific time elapses.
- the present invention includes the steps of receiving from the first client device a request message requesting a protected value indicating whether another client is in use; Sending a response message in response to the request message; And when the protected value is No, receiving a request message for requesting a change of the protected value from the first client device.
- the present invention may further comprise notifying the changed protected value to other client devices connected to the gateway.
- the changed protected value is changed to No after a request from the first client or a specific time elapses.
- the present invention also provides a method comprising: transmitting a read request to the server to request information related to a first object; Receiving a read response including information related to the first object from the server in response to the read request; Sending a message to the server to change the first object to a second object; And receiving an error code related to a second object from the server, wherein the error code indicates that the resource of the server is not sufficient.
- 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 write request including information related to a Hyper Text Transfer Protocol (HTTP) request from a first client device, and receives the received request.
- HTTP Hyper Text Transfer Protocol
- the HTTP request related information is generated based on the information included in the first write request, the HTTP request related information is transmitted to the web server, and an HTTP response message is received in response to the HTTP request related information from the web server.
- Receive an HTTP status code indicating a status of data included in the received HTTP response message, and notify the first client device from the first client device to the HTTP status code.
- HTTP data can be efficiently transmitted using Bluetooth low power energy technology.
- an error message when there is a request for HTTP data transmission from another device during data transmission using Bluetooth low power energy technology, an error message may be improved by transmitting an error message.
- 1 is a diagram illustrating an example of transmitting HTTP data using Bluetooth low energy.
- FIG. 2 is a diagram illustrating an example of an internal block diagram of a server device and a client device to which the present invention is applied.
- FIG. 3 is a diagram schematically showing a functional configuration of an internal configuration of a device to which the present invention is applied.
- FIG. 4 is a diagram schematically illustrating a functional configuration for transmitting HTTP data using Bluetooth Low Energy, to which the present invention is applied.
- FIG. 5 is a diagram illustrating an example of transmitting HTTP data using Bluetooth low energy.
- 6 and 7 illustrate an example in which a plurality of client devices transmit a write request to the same gateway.
- FIG. 8 is a diagram illustrating an example of transmitting an error response when a plurality of devices transmit a write request to which the present invention is applied.
- FIG. 9 is a diagram illustrating an example of transmitting an error response according to a data length to which the present invention is applied.
- FIG. 10 is a diagram illustrating an example of transmitting HTTP data using a currently used client ID to which the present invention is applied.
- FIG. 11 is a diagram illustrating an example of transmitting a current client ID to a plurality of devices to which the present invention is applied.
- FIG. 12 is a diagram illustrating an example of notifying that there is a device that is already transmitting HTTP data when the device transmits HTTP data to which the present invention is applied.
- FIG. 13 is a diagram illustrating another example of notifying that a plurality of devices are already transmitting HTTP data to a plurality of devices to which the present invention is applied.
- FIG. 14 is a diagram illustrating an example of enabling / disabling a security function to which the present invention is applied.
- 15 is a diagram illustrating an example in which a transmission scheme is changed according to a data size to which the present invention is applied.
- 16 is a diagram illustrating an example of a Bluetooth data transmission method to which the present invention is applied.
- 17 and 18 are diagrams showing an example of a method of informing a data length in HTTP data transmission to which the present invention is applied.
- 19 is a flowchart illustrating an example of transmitting an error code in an object transfer service 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 an example of transmitting HTTP data using Bluetooth low energy.
- FIG. 1 an example is shown in which a device supporting Bluetooth is connected to the Internet web through a gateway supporting Bluetooth.
- Bluetooth is one of the representative short-range wireless technologies that transmit and receive information by connecting various devices (smartphones, PCs, earphones, headphones) to each other.
- Bluetooth Low Energy technology consumes less power and can reliably provide hundreds of kilobytes of information.
- the Bluetooth low energy energy technology uses an attribute protocol to exchange information between devices.
- This approach can reduce energy consumption by reducing the overhead of the header and simplifying the operation.
- Bluetooth low energy energy technology can also connect to and send data from the Internet. This allows Bluetooth-enabled devices to access and provide information on the Internet web so users can access the information they need anywhere, anytime.
- a gateway that can access Web services must connect the device to the Internet Web.
- a client device 10 that supports Bluetooth low energy (hereinafter referred to as Bluetooth LE) and the gateway 20 are connected using Bluetooth.
- Bluetooth LE Bluetooth low energy
- the client device 100 may transmit data to the gateway 200.
- the gateway 200 is connected to the web server 400 by using Wi-Fi, Long Term Evolution (LTE), or other technology, through which the data received from the client device 100 is web. You can send it to the server.
- Wi-Fi Wireless Fidelity
- LTE Long Term Evolution
- the present invention provides a method and apparatus for efficiently transmitting HTTP data using Bluetooth.
- FIG. 2 is a diagram illustrating an example of an internal block diagram of a server device and a client device to which the present invention is applied.
- the gateway 200 may refer to any electronic device capable of directly communicating with the client device 100.
- the gateway 200 may be referred to as a server device.
- the client device 100 may refer to any electronic device capable of supporting a Bluetooth function.
- the gateway 200 may directly communicate with the client device 100, receive data, and notify the client device 100 of a result of processing the received data.
- the client device 100 may request data and transmit the requested data back to the client device 100.
- a notification or indication message is sent to the client device 100. It may be sent, and may receive a confirmation message for this from the client device (100).
- 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 and the gateway 200 may be a communication unit 110 and 210, a user input unit 220 and 120, an output unit 230 and 130, a control unit 140 and 240, and a memory 150 and 250, respectively. And power supplies 160 and 260.
- the communication unit, user input unit, output unit, control unit, memory, and power supply unit are functionally connected to perform the method proposed by the present invention.
- 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 160 and 260 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 transmission / reception unit.
- 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 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 device may establish a Wi-Fi peer-to-peer connection with another device through the wireless internet module.
- a Wi-Fi P2P connection may provide a streaming service between devices, and may provide a printing service by connecting to a data transmission / reception or a printer.
- the gateway 200 may be connected to the client device 100 through a short range communication module, and may receive data and receive a data request from the client device 100 through this.
- the gateway 200 may be connected to a web server through the wireless internet module to access the internet network, thereby transmitting data received from the client device 100 to the web server or the client device 100. Can receive the requested data.
- the user input units 120 and 220 generate input data for controlling the operation of the user.
- 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 may 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.
- 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, and the like.
- the controllers 140 and 240 refer to a module that controls the overall operation of the client device 100 or the gateway 200, and processes a request for transmission of a message and a received message through a Bluetooth interface and another communication interface. Can be controlled.
- 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, 250 is a medium for storing various types of information of a terminal.
- the memory 150, 250 is connected to the controller to store programs, applications, general files, and input / output data for the operation of the controller 160, 260. Can be stored.
- the memories 130 and 230 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.
- the device may operate in association with a web storage that performs a storage function of the memories 130 and 230 on the Internet.
- 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.
- Bluetooth LE technology which is applied in the present invention, has a small duty cycle and can greatly reduce power consumption through a low data rate, so that the power supply units 160 and 260 can each have a low output power (100 mW (10 dBm or less). It can supply power for the operation of the components.
- FIG. 3 is a diagram schematically showing a functional configuration of an internal configuration of a device to which the present invention is applied.
- the client device and the server device are each composed of a host 320 and a controller 310, and the controller 310 is composed of a physical layer PHY 312 and a link layer layer LL 314.
- the host 320 is, again, Logical Link Control and Adaptation Protocol (L2CAP, 331), Security Manager (Security Manager, SM, 332), Attribute Protocol (ATT, 333), It consists of a Generic Attribute Profile (GATT, 334), a Generic Access Profile (GAP, 335), and a GATT based profile (336).
- L2CAP Logical Link Control and Adaptation Protocol
- SM Security Manager
- ATT Attribute Protocol
- GATT Generic Attribute Profile
- GAP Generic Access Profile
- GATT Generic Access Profile
- the controller 310 and the host 320 are connected to a host controller interface (HCI) 316.
- HCI host controller interface
- the host 320 may provide a command and data to the controller 310 through the HCI 316, and the controller may provide an event and data to the host through the HCI 316. May be provided to 320.
- the controller 310 refers to a wireless transceiver module for receiving a Bluetooth signal and hardware for transmitting or receiving a Bluetooth packet.
- the PHY layer 312 is a layer for transmitting / receiving a radio signal using a Gaussian Frequency Shift Keying (GFSK) modulation and a frequency hopping scheme composed of 40 RF channels.
- GFSK Gaussian Frequency Shift Keying
- the link layer layer 314 performs an advertising and scanning function using three advertising channels to create a connection between devices, and generates a data packet through 37 data channels. It can provide the function of sending and receiving.
- the host 320 may multiplex various protocols, profiles, etc. provided by a higher level of Bluetooth using the logical link control and adaptation protocol (hereinafter referred to as L2CAP, 311). .
- L2CAP logical link control and adaptation protocol
- the L2CAP 331 may provide one bidirectional channel for transmitting data to a specific protocol or profile, and uses three fixed channels in Bluetooth low power energy.
- the fixed channel may be used for the signaling channel, the security manager 332 and the attribute protocol (hereinafter referred to as ATT, 333), respectively.
- the Bluetooth Basic Rate / Enhanced Data Rate uses a dynamic channel and can support protocol service multiplexers, retransmissions, and streaming modes.
- the security manager (hereinafter referred to as SM, 332) is a protocol for providing device authentication and key distribution.
- the ATT 333 is used for communication between the server and the client, and has an attribute handle used by the client to access attributes in the server.
- Protocol operation commands include 'Request', 'Response', 'Command', 'Notification', 'Indication', and '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 response message, which is a message transmitted to 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 A message sent to a server device for notification, such as an event, to a client device.
- the client device does not transmit a confirmation message for a notification message to the server device.
- the client device transmits a confirmation message for the Indication message to the server device from the server device to the client device.
- GATT 334 The general attribute profile (hereinafter referred to as GATT 334) is a newly implemented layer for Bluetooth LE technology, and defines a procedure for obtaining corresponding information with a message defined in the S / W component of the Bluetooth device below and the ATT protocol. . This procedure can define the settings of the discovering, reading, writing, notify, and indicating properties.
- UUID Universally Unique Identifier
- the general access profile (hereinafter, referred to as a GAP) 335 may define a method of discovering, connecting to a defined device, and providing information to a user, and may provide privacy.
- the GATT based profile 336 is mainly applied to low energy devices with profiles that depend on the GATT 334.
- the GATT-based profile 366 includes a profile related to battery, time, proximity, phone alert, heart rate, and HTTP proxy service (337). This may be included.
- the HTTP proxy service 337 may perform a function of requesting HTTP message delivery using a GATT (Generic Attribute Profile) function of Bluetooth.
- the client device 100 and the host device 200 may transmit an HTTP message transfer request and data transmitted from a web server to the client device 100 using the HTTP proxy service 337.
- GATT Generic Attribute Profile
- FIG. 4 is a diagram schematically illustrating a functional configuration for transmitting HTTP data using Bluetooth Low Energy, to which the present invention is applied.
- the gateway 200 receiving data from the client device 100 through Bluetooth may transmit it to the internet web server 400.
- the client device 100 includes an HTTP proxy client 12.
- the client device 100 and the gateway 200 may support Bluetooth low energy technology.
- the HTTP proxy client 12 functions to use the HTTP proxy server 22 of the gateway 200 because the client device 100 cannot access a web server through the Internet using Bluetooth technology. Can provide.
- the client device 100 may be connected to the gateway 200 through the HTTP proxy client 12, and may transmit a data request message or data to the gateway 200 through the HTTP proxy client 12.
- the gateway 200 includes an HTTP proxy server 22 and an HTTP client 24.
- the HTTP proxy server 22 provides an HTTP proxy service function for providing connectivity between the client device 100 and the HTTP server 400.
- the HTTP client 24 functions as a client to send and receive an HTTP request to an HTTP server in order to provide an HTTP proxy function of the client device 100, and generates an HTTP message with data of an HTTP proxy service. Communicate with an HTTP server.
- the gateway 200 may receive a message or data to be transmitted from the client device 100 to the web server through the HTTP proxy server 22, and generate an HTTP message through the received data.
- the gateway 200 may transmit the generated HTTP message to the HTTP server 400 through wireless communication through the HTTP client 24.
- the wireless communication refers to a communication means capable of connecting with an internet server as wireless communication excluding Bluetooth.
- wireless communication excluding Bluetooth.
- the HTTP server refers to a server using the HTTP protocol to provide a web (web) service.
- the gateway may receive data requested by the client device 100 from the HTTP server 400 through the HTTP client 24.
- the received data is converted into a form that can be transmitted via Bluetooth again, and then transmitted to the HTTP proxy client 12 of the client device 100 through the HTTP proxy server 220.
- Characteristic of HTTP proxy service contains information for providing HTTP proxy service.
- the URI Characteristic is used to construct a URI for subsequent requests.
- the URI characteristic includes a URI used for an HTTP request and can be used up to a defined maximum length. For example, the maximum length of an HTTP request that contains a current URI is 512 octets.
- the HTTP Header Characteristic is used to include a header included in a write request or a read request.
- the HTTP Header Characteristic may be used up to a defined maximum length.
- the maximum length of the current HTTP Header Characteristic is 512 octec.
- the HTTP Entity Body includes a body of a message to be transmitted.
- the HTTP L2CAP Protocol Service Multiplexer represents an identifier indicating which protocol or service the data information is for.
- the gateway may inform or notify the client device of the changed value.
- the HTTP Status Code Characteristic may include information representing the status of the received data.
- the state of the received data refers to the state of data included in the HTTP header and / or HTTP entity body received by the gateway 200 from the web server 400.
- the HTTP control point serves to instruct the HTTP proxy service to perform a specific operation.
- Table 2 below shows the commands that can be included in the HTTP control point.
- the HTTPS Security includes information indicating whether to use a function related to security. If the HTTPS Security function is Yes, the security function may be used by using HTTPS, and when No, the security function may not be used by using HTTP.
- the HTTP security characteristic may be expressed as a Boolean.
- FIG. 5 is a diagram illustrating an example of transmitting HTTP data using Bluetooth low energy.
- the client device 1 100 may transmit information for generating an HTTP request message to the gateway 200 through a write request.
- the write request may include one characteristic.
- the client device 1 (100) transmits a Universal Resource Identifier (URI) through a write request (S510).
- the client device 100 then transmits an HTTP header through a write request (S512), and sequentially through an write request, an HTTP entity body and an HTTP control.
- a point (HTTP control point) is transmitted (S514 and S516).
- the gateway 200 may transmit a response message for each write request to the client device 1 (100).
- the client responds to the write request including the URI, the response to the write request including the HTTP header, the response to the write request including the HTTP entity body, and the response to the write request including the HTTP control point. It may transmit to the device 1 (100).
- the gateway 200 may generate an HTTP request message based on the information received from the client device 1 100 and transmit the generated HTTP request message to the web server 400 (S518).
- the HTTP request message may include information related to the HTTP request, that is, information (URI, HTTP header, HTTP entity body) transmitted from the client device 1 (100).
- information URI, HTTP header, HTTP entity body
- the client device 1 100 transmits information related to the HTTP request to the gateway 200, and the gateway 200 transmits the information related to the HTTP request in the form of a message or frame to the web server 400. ) Can be sent.
- the web server 400 transmits an HTTP response message including the requested data and an HTTP status code to the gateway in step S520.
- the HTTP status code is a code indicating the status of the requested data.
- the gateway 200 receiving the HTTP response message may convert the information into a form that can be transmitted through Bluetooth.
- the gateway After receiving the HTTP response message from the web server 400, the gateway transmits an indication message including a status code to the client device 100 (S522). Through this, the client device can know whether the gateway 200 correctly received the requested data, did not receive it, or received it incompletely.
- the client device 100 may request information received from the web server 400 by the gateway to the gateway 200 through a read request.
- the client device 100 may receive a URI by transmitting a read request to the gateway 200 (S524), and may receive an HTTP header through the read request (S526). Thereafter, the client device 100 may transmit a read request to the gateway 200 to receive the HTTP entity body and receive the HTTP entity body from the gateway 200 (S528).
- the client device 1 100 may transmit and receive data from the web server 400.
- the gateway 200 may be connected to a plurality of client devices at the same time, and in this case, a smooth service may not be provided because it cannot distinguish which device uses the corresponding service.
- 6 and 7 illustrate an example in which a plurality of client devices transmit a write request to the same gateway.
- steps S710 to S 718 of FIG. 7 are the same as steps S510 to S 518 of FIG. 5, description thereof will be omitted.
- the devices 100, 120, and 140 supporting the Bluetooth function transmit a write request including the HTTP request related information to the gateway 200 for HTTP data transmission.
- the gateway 200 may be connected to a client device to transmit an HTTP message including the HTTP request related information requested by the client device to the web server 300. However, while the client device 100 transmits a write request for generating an HTTP message to the gateway 200, the gateway 200 again transmits the HTTP message from another client device 120 or 140. When receiving a write request for generation, there is a problem in that it is impossible to maintain existing characteristics.
- the client device 1 (100) when the client device 1 (100) receives a write request from the client device 2 (120) while transmitting information to the gateway 200 through a write request, the client device 1 (100) previously receives information.
- the client device 1 100 may not maintain information on the characteristic transmitted to the gateway 200.
- the client 1 may not receive the data requested by the client 1, and may not perform smooth data transmission.
- FIG. 8 is a diagram illustrating an example of transmitting an error response when a plurality of devices transmit a write request to which the present invention is applied.
- steps S810 to S816 of FIG. 8 are the same as steps S510 to S516 of FIG. 5, description thereof will be omitted.
- the client device 1 (100) While the client device 1 (100) is transmitting data to the gateway 200 through a write request, the client device 2 (120) uses URI information through a write request to generate an HTTP request message. It may transmit (S818).
- the gateway 200 cannot accept the write request of the client device 2 (200).
- the gateway may reject the request of the client device 2 120 because there is a write request already in progress or the resource of the gateway is insufficient.
- the gateway 200 since the gateway 200 cannot accept a write request from the client device 2 120, the gateway 200 transmits an error response to the client device 2 120 (S820).
- Table 3 below shows error codes that may be included in an error response to a write request of a client device.
- the gateway 200 may transmit 0x80 to an error response to the client 2 120, and the client 2 may stop a write request when the error response message is received.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to a web server, and as shown in step S518 You can receive an HTTP response containing HTTP data from a web server.
- the HTTP response may include a status code indicating a status of the HTTP data.
- steps S822 to S828 are the same as those of steps S522 to S528 of FIG. 5, description thereof will be omitted.
- the error codes shown in Table 3 may be used in other services of Bluetooth in addition to the HTTP proxy service of the present invention, for example, in a Bluetooth Object Transfer Service, which will be described in detail with reference to FIG. 19. .
- FIG. 9 is a diagram illustrating an example of transmitting an error response according to a data length to which the present invention is applied.
- the gateway 200 transmits an error message to transmit data in another method.
- steps S910 to S916 are the same as steps S510 to S516 of FIG. 5, description thereof will be omitted.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to the web server, and as shown in step S518.
- An HTTP response including HTTP data may be received from the web server.
- Steps S918 to S922 are the same as steps S522 to S526 of FIG. 5, and thus descriptions thereof will be omitted.
- the HTTP response may include a status code indicating a status of the HTTP data.
- the client device 1 transmits a read request to the gateway 200 to read an HTTP entity body from the gateway 200 (S924).
- the gateway transmits an error response to the client device 1 (100) (S926).
- the error response may include 0x81 code of Table 3.
- the client device 1 may open the L2CAP Connection Oriented Channel (L2CAP Connection Oriented Channel) instead of the ATT protocol to receive the HTTP entity body (S928).
- L2CAP Connection Oriented Channel L2CAP Connection Oriented Channel
- FIG. 10 is a diagram illustrating an example of transmitting HTTP data using a currently used client ID to which the present invention is applied.
- the Client ID Characteristic includes an ID of a Client to use the HTTP proxy function. If the Client ID value is null, the HTTP proxy service (HPS) may be used. However, if the client ID value is null, the HTTP proxy service (HPS) cannot be requested.
- the Client ID may identify a user or a device by using a user ID or a device ID, and may distinguish a service inside a user or a device by adding a service UUID.
- the Protected Characteristic may set the corresponding function to yes when a request is made from a client device, and if set to yes, other clients cannot send the request.
- a client device may read a client ID value from a gateway, and if the client ID value is an ID value of another client device, the client device may not use the HTTP proxy service.
- the client device 1 (100) transmits a read request (Client Request) of the client ID to the gateway 200 (S1010).
- the gateway 200 may transmit information of the client device to the client device 1 (100).
- the gateway 200 transmits a read response including a NULL value to the client device 1 100 (S1012).
- the client device 1 (100) confirming that there is no client device using the HTTP proxy service through the write request to the gateway 200, the information of the client device 1 (100) to the client ID value In operation S1014, a request may be made to write.
- the gateway 200 receiving the request may input the information of the client device 1 (100) into the client ID, and may transmit a response message to the request to the client device 1 (100).
- steps S1016 to 1022 are the same as steps S510 to S516 of FIG. 5, description thereof will be omitted.
- the client device 2 120 may request a client ID value through a read request in order to use the HTTP proxy service (S1024).
- the gateway 200 may provide information about the client device 1 (100), for example, a user ID or a device ID, to the client ID value. Can be transmitted.
- the client device 1 100 may use the HTTP proxy service.
- the client device 2 120 suspends the HTTP proxy service request until the client ID value becomes NULL.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to the web server, and as shown in step S518.
- An HTTP response including HTTP data may be received from the web server.
- the HTTP response may include a status code indicating a status of the HTTP data.
- steps S1028 to S1034 are the same as those of steps S522 to S528 of FIG. 5, description thereof is omitted.
- Proxy services can be provided.
- FIG. 11 is a diagram illustrating an example of transmitting a current client ID to a plurality of devices to which the present invention is applied.
- the HTTP proxy service connection can be smoothly performed by notifying the clients connected to the gateway 200.
- the client device 1 (100) may request to input the information of the client device 1 (100) to the client ID value through a write request. (S1110).
- the gateway 200 may input information of the client device 1 100, for example, a user ID or a device ID of the client device 1 100, in response to the client ID value. May be transmitted to the client device 1 (100).
- the gateway 200 may notify devices connected to the gateway 200 through a notification or an indication that the client ID value has been changed (S1112).
- the devices receiving the indication transmit a confirmation message to the gateway 200.
- step S1114 to step S1120 are the same as step S510 to step S516 of FIG. 5, description thereof is omitted.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to the web server, and as shown in step S518.
- An HTTP response including HTTP data may be received from the web server.
- the HTTP response may include a status code indicating a status of the HTTP data.
- steps S1122 to S1228 are the same as steps S522 to S528 of FIG. 5, description thereof is omitted.
- the gateway 200 Since the client device 1 (100), which has received all the requested data from the gateway 200, has ended the use of the HTTP proxy service, the gateway 200 to change the client ID value back to NULL through a write request. Can request (S1130).
- the gateway 200 may change the value of the client ID to NULL according to the request of the client device 1 100, and may notify or indicate the changed value to the connected devices.
- the connected devices may transmit a confirmation message to the gateway 200.
- the request of the HTTP proxy service may come from a plurality of client devices, but if the request comes in at the same time, the data is damaged and the request must be transmitted again.
- a client device can know whether the HTTP proxy service is used, and even when the use is terminated, it can be known whether or not the HTTP proxy service is available through a notification or an instruction.
- FIG. 12 is a diagram illustrating an example of notifying that there is a device that is already transmitting HTTP data when the device transmits HTTP data to which the present invention is applied.
- the client device when the client device is using the HTTP proxy service, the client device may be notified to another client device, thereby preventing a request for using the HTTP proxy service of the other client device.
- the client device 100 may request a protected value through the read request from the gateway 200 (S1210).
- the gateway 200 may include a Yes value when providing an HTTP proxy service to another client device and a No value when not providing the HTTP proxy service in the read response.
- the client device cannot use the HTTP proxy service because another client device is using the HTTP proxy service.
- the client device 1 may use the HTTP proxy service.
- steps S1214 to S1220 are the same as steps S510 to S516 of FIG. 5, description thereof will be omitted.
- the protected value may be changed to Yes.
- the client device 2 120 may request a protection value from the gateway 200 through a read request in order to use the HTTP proxy service (S1222).
- the gateway transmits a Yes value as the protected value to the client device 2 (120) (S1224).
- the client device 2 120 that receives the Yes value as the protection value from the gateway 200 may know that the HTTP proxy service is in use.
- the client device 2 (120) that finds out that the HTTP proxy service is not available cannot request the gateway 200 to use the HTTP proxy service.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to a web server.
- the web server may receive an HTTP response including HTTP data.
- the HTTP response may include a status code indicating a status of the HTTP data.
- steps S1226 to S1232 are the same as those of steps S522 to S528 of FIG. 5, description thereof will be omitted.
- the protected value may be changed to No when the gateway 200 does not operate with the client device 1 100 for a predetermined time, and the client device 1 100 may request to write the protected value. Can be changed to No.
- FIG. 13 is a diagram illustrating another example of notifying that a plurality of devices are already transmitting HTTP data to a plurality of devices to which the present invention is applied.
- the client device 1 may request the gateway 200 to change the protected value to Yes through a write request (S1310).
- the gateway 200 receiving the write request may change the protected value to Yes and transmit a response message to the write request to the client device 1 (100).
- the gateway 200 may notify the other connected client device, for example, the client device 2 120, through the notification or the indication of the changed protected value (S1312).
- a confirmation message may be transmitted to the gateway 200.
- step S1314 to step S1320 are the same as step S510 to step S516 of FIG. 5, description thereof will be omitted.
- the gateway 200 may transmit the HTTP request related information received from the client device 1 (100) to a web server. You can receive an HTTP response containing HTTP data from a web server.
- the HTTP response may include a status code indicating a status of the HTTP data.
- step S1322 to step 1328 are the same as step S522 to step S528 of FIG. 5, description thereof will be omitted.
- the client device 100 When the client device 1 (100) receiving the requested data from the gateway 200 no longer uses the HTTP proxy service, the client device 100 changes the protected value to No through a write request. In operation S1330, the user may request 200.
- the gateway 200 that has been requested to change the protected value may change the protected value to No, and then transmit a response to the client device 1 (100).
- the protected value may be changed when there is no operation of the client device 1 100 for a predetermined time in addition to the request of the client device 1 100.
- the gateway 200 may notify other connected client devices through notification or indication (S1332).
- a request of an HTTP proxy service may be received from a plurality of client devices, but if a request is received at the same time, data may be damaged and the request must be transmitted again.
- FIG. 14 is a diagram illustrating an example of enabling / disabling a security function to which the present invention is applied.
- a request for changing an HTTPS security characteristic value may be directly requested by a client device through a write request.
- Table 5 below shows another example of the characteristic of the HTTP proxy service different from the above [Table 1].
- [Table 5] shows that [Table 1] and HTTPS Security can be used as well as Read.
- This not only can inform the gateway that the HTTPS Security value has changed, but also indicates that a client device can directly request the gateway to change the HTTPS Security value.
- the client device 1 may request the gateway 100 to change the HTTPS security value to Yes through a write request (S1410).
- the gateway 200 receiving the write request may change the HTTPS security value to Yes, and then transmit a response message to the client device 1 (100).
- steps S1412 to S1416 are the same as those of steps S510 to S514 of FIG. 5, description thereof will be omitted.
- the client device 1 (100) may request transmission of an HTTPS PUT Request message to the gateway 200 through an HTTP control point characteristic (S1418), and the gateway 200 sends a response to the client device 1 (100). ) Can be sent.
- the gateway 200 may transmit an HTTPS PUT request message to the web server 400 (S1420).
- the HTTPS PUT request message may include information related to an HTTP request, that is, information (URI, HTTP header, HTTP entity body) received from the client device 1 (100).
- the web server 400 may receive an HTTPS PUT response in response to the HTTPS PUT request message (S1422).
- the HTTPS PUT response message may include HTTP data requested by the client device 1 (100) and / or a status code indicating a status of the HTTP data.
- the client device 1 100 may change the value of the HTTPS security characteristic to No.
- the client device 1 may request the gateway 200 to change the value of the HTTPS security characteristic to No through a write request (S1424).
- the gateway 200 receiving the write request may transmit a response message to the client device 1 (100).
- steps S1426 to S1430 are the same as steps S510 to S514 of FIG. 5, description thereof will be omitted.
- the client device 1 (100) may request the transmission of the HTTP PUT Request to the gateway 200 through the HTTP control point characteristic (S1432), and the gateway 200 sends a response to the client device 1 ( 100).
- the gateway 200 may transmit an HTTP PUT request message to the web server 400 (S1434).
- the HTTPS PUT request message may include information related to an HTTP request, that is, information (URI, HTTP header, HTTP entity body) received from the client device 1 (100).
- the web server 400 may receive an HTTP PUT response message in response to the HTTP PUT request message (S1436).
- the HTTP PUT response message may include a HTTP code requested by the client device 1 (100) and / or a status code indicating a status of the HTTP data.
- the client device as well as the gateway 200 may directly request to change the HTTP security characteristic value.
- Table 6 below shows another example of the characteristic of the HTTP proxy service.
- Body Length Characteristic of Table 6 may include information related to the length of the HTTP Entity Body or HTTP Header. This informs the gateway of data length information to be written by the client device through a write request, or data length information that the client device reads from the gateway through a read request. It can be seen.
- the gateway may inform the client device using the HTTP proxy service through a notification or an indication.
- the client device may know that there is no data to be read from the gateway when the data length characteristic value is 0 or empty. If the data length characteristic value is other than 0, the data to be read is an HTTP header or an HTTP entity. You can see it is in the Body.
- the data length is less than the length of the data requested by the client to the gateway through a write request
- the data length is known through a read request, notification, or indication. We can see that only part of the data received from the web server was sent.
- 15 is a diagram illustrating an example in which a transmission scheme is changed according to a data size to which the present invention is applied.
- the client device may be provided with data length information to be transmitted from the gateway, and may change the transmission scheme according to the data length information.
- the client device may obtain information related to the data length to be transmitted from the gateway through a read request, notification, or indication (S1510).
- the client device may know the data length (or size) to be transmitted from the gateway through the obtained data length information.
- the client device may know whether the data length is 0 through the data length information (S1512). If the data length is 0, the client device may know that there is no data to be transmitted from the gateway (S1514). . That is, it can be seen that there is no data to be transmitted because the gateway does not receive data from the web server.
- the client device may compare the obtained data length with an ATT_MTU-2 value (S1516).
- the ATT_MTU-2 value represents a maximum data length that can be received at one time through a read request sub procedure.
- the client device may receive data through a read request sub procedure (S1520).
- the client device may again compare the maximum ATT data length with the data length (S1522).
- the read blob request refers to a method of dividing and transmitting data when all data cannot be transmitted at once. This will be described with reference to FIG. 16.
- the client device may receive the data through an L2CAP channel. It may be (S1526).
- the length of the data to be transmitted for example, the length of the HTTP header or the HTTP entity body, is informed through a read request, notification, or indication. You can receive data.
- 16 is a diagram illustrating an example of a Bluetooth data transmission method to which the present invention is applied.
- the client device 1 may request data transmission from the gateway 200 through a read request (S1610).
- the gateway 200 receiving the read request may transmit data requested by the client through a read response (S1612).
- the gateway 200 may divide and transmit data.
- Bluetooth HTTP data transmission method For example, suppose the data to be transmitted is “Bluetooth HTTP data transmission method” and the length that can be transmitted at one time is “Bluetooth HTTP”.
- the client device 1 100 may receive data called “Bluetooth HTTP” through a read response (S1612).
- the client device 1 transmits a read blob request to the gateway 200 (S1614).
- the gateway Upon receiving the read blob request, the gateway transmits “data transmission”, which is next to the transmitted data, to the client device 1 100 through a read response (S1616).
- the client device 1 (100) transmits a read blob request to the gateway 200 again, and the gateway 200 determines the remaining data portion. ”Is transmitted to the client device 1 (100) through a read response.
- the client device 1 (100) may be transmitted from the gateway (200).
- 17 and 18 are diagrams showing an example of a method of informing a data length in HTTP data transmission to which the present invention is applied.
- the client device may know the transmitted entity body length through a read request.
- Steps S1710 to S1720 are the same as those of steps S1412 to S1422 of FIG. 14, and thus descriptions thereof will be omitted.
- the gateway 200 transmits an indication message including a status code to the client device 1 (100) (S1722). Through this, the client device can know whether the gateway 200 correctly received the requested data, did not receive it, or received it incompletely.
- the client device 1 100 may transmit a confirmation message to the gateway 200 in response to the indication message.
- the client device 100 may request information received from the web server 400 by the gateway to the gateway 200 through a read request.
- the client device 100 may receive a URI by transmitting a read request to the gateway 200 (S1724) and may receive an HTTP header through the read request (S1726).
- the client may request the gateway 200 to read the length information of the HTTP entity body to be transmitted through a read request (S1728).
- the client device 1 may receive the HTTP entity body using one of a Read Request Sub Procedure, Read Blob Request, or L2CAP channel, which is the method illustrated in FIG. 15, according to the received length information of the HTTP entity body. There is (S1730).
- the gateway 200 may include a data length value in a status code to notify or indicate.
- Steps S1810 to S1820 are the same as those of step S1710 to step S1720 of FIG. 17, and thus description thereof is omitted.
- the gateway 200 receives the data from the web server 400 and informs the client device 1 (100) of the status code and the length information of the received data through an indication or notification. It may be (S1822).
- the status code may indicate whether the gateway 200 has received data from the web server 400, and the data length information indicates the length (or size) of data received from the web server 400. Can be represented.
- the data length information may be transmitted to the client device 1 100 through the indication or the notification as the status code.
- the information may be included in the status code and transmitted to the client device 1 100 through the indication or the notification.
- the gateway 200 transmits the indication message to the client device 1 100, the client device 1 100 sends a confirmation message in response thereto. It may transmit to the gateway 200.
- Table 7 below shows an example of the HTTP Status code.
- the client device 1 (100) obtains data received through the data length information included in or transmitted with the HTTP status code, that is, information about the length of data included in an HTTP header or an HTTP entity body. can do.
- the client device 1 100 may recognize that there is no data to be read from the gateway 200 when the value for the length is 0 or empty, and the value for the length is other than 0. If you indicate a value, you can see that the data to be read is in the HTTP header or HTTP Entity Body.
- the data length information may have a value of 1 or 0, and when the data length information is 0, it may indicate that no data exists because the data is not received from the web server 400. When the data length information is 1, it may indicate that data has been received from the web server 400.
- the size of the data length information may have a size of one octet and may indicate a data state transmitted according to a bit operation of the octet value.
- the first bit is 1, it can indicate that data exists in the header. If the second bit is 1, it indicates that the data in the transmitted header exceeds the maximum transmission size (for example, 512 bytes). Can be.
- the maximum transmission size for example, 512 bytes.
- the third bit is 1, it may indicate that data exists in the transmitted body. If the fourth bit is 1, the data of the transmitted body indicates the maximum transmission size (for example, 512 bytes). It may indicate the excess.
- step S1726 to step S1730 of FIG. 17, description thereof will be omitted.
- 19 is a flowchart illustrating an example of transmitting an error code when an error occurs during service provision to which the present invention is applied.
- the server may inform the client of the Bluetooth object transfer service.
- the object transfer service may be referred to as an object delivery service.
- the server 1900 may inform the client 1910 that an object delivery service may be provided through an advertising channel (S1912).
- a physical channel for transmitting information is divided into an advertising channel and a data channel, and the advertising channel is divided into three channels. In the channel, there may be 37 channels in the data channel.
- the advertising channel may provide information for pairing to surrounding clients.
- the server 1900 may inform the surrounding clients that the server 1900 can provide an object delivery service through the advertising channel ( S1912).
- the client 1910 when the client 1910 is a device to receive the object delivery service, the client 1910 transmits a connection request for pairing to the server 1900 (S1914).
- the client 1910 reads information on an object name through a read request in order to receive current object information provided by the object delivery service.
- the server may request it (S1916).
- the server 1900 may transmit a name of an object currently provided by the object delivery service to the client through a read response (S1918). .
- the client 1910 having received the object name transmits an object list control point for changing an object to the server 1900 to obtain information on a next object, and transmits the current object to the next object.
- the change may be requested (S1920).
- the server 1900 may be notified by transmitting an error code to the client 1910 (S1924).
- the server 1900 may not generate information on a new object due to a lack of resources of the server 1900, for example, a CPU power, a memory resource, or the like. have.
- the error codes of Table 8 may be transmitted.
- the server 1900 may inform the client 1910 why the error occurred.
- the present specification provides a method and apparatus for transmitting and receiving data using a wireless communication system.
- the present invention provides a method and apparatus for transmitting and receiving HTTP data with a web server through Bluetooth, which is a short range wireless communication technology.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Characteristic Name | Requirement | Mandatory Properties | Optional Properties | Security Permissions |
URI | M | Read, Write | Optional | |
HTTP Header | M | Read, Write | Optional | |
HTTP Status Code | M | Notify, Indicate | Optional | |
HTTP Entity Body | M | Read, Write | Optional | |
HTTP L2CAP | M | Read | Optional | |
HTTP Control Point | M | Write, Indicate | Optional | |
HTTPS Sercurity | M | Read | Optional |
Op Code Value | Procedure |
0x00 | Reserved for Future Use |
0x01 | HTTP GET Request |
0x02 | HTTP HEAD Request |
0x03 | HTTP POST Request |
0x04 | HTTP PUT Request |
0x05 | HTTP DELETE Request |
0x06 | HTTPS GET Request |
0x07 | HTTPS HEAD Request |
0x08 | HTTPS POST Request |
0x09 | HTTPS PUT Request |
0x0a | HTTPS DELETE Request |
0x0b | HTTPS Request Cancel |
0x0c - 0xff | Reserved for Future Use |
Name | Error Code | Description |
Other Client is using | 0x80 | Can not write a value because of Server is servicing to other client |
Long HTTP Entity Body | 0x81 | L2CAP delivery is needed because of HTTP Entity Body is Long |
Characteristic Name | Requirement | Mandatory Properties | Optional Properties | Security Permissions |
Client ID | Read, WriteIndication/Notification | |||
Protected | Read, WriteIndication/Notification | |||
URI | M | Read, Write | Optional | |
HTTP Header | M | Read, Write | Optional | |
HTTP Status Code | M | Notify, Indicate | Optional | |
HTTP Entity Body | M | Read, Write | Optional | |
HTTP L2CAP | M | Read | Optional | |
HTTP Control Point | M | Write, Indicate | Optional | |
HTTPS Sercurity | M | Read | Optional |
Characteristic Name | Requirement | Mandatory Properties | Optional Properties | Security Permissions |
URI | M | Read, Write | Optional | |
HTTP Header | M | Read, Write | Optional | |
HTTP Status Code | M | Notify, Indicate | Optional | |
HTTP Entity Body | M | Read, Write | Optional | |
HTTP L2CAP | M | Read | Optional | |
HTTP Control Point | M | Write, Indicate | Optional | |
HTTPS Sercurity | M | Read | Optional |
Characteristic Name | Requirement | Mandatory Properties | Optional Properties | Security Permissions |
URI | M | Read, Write | Optional | |
HTTP Header | M | Read, Write | Optional | |
HTTP Status Code | M | Notify, Indicate | Optional | |
HTTP Entity Body | M | Read, Write | Optional | |
HTTP L2CAP | M | Read | Optional | |
HTTP Control Point | M | Write, Indicate | Optional | |
HTTPS Sercurity | M | Read | Optional | |
Body Length | Read, Write,Indication/Notification |
Status Code | Length | |
Octet Order | LSO | MSO |
Format Type | Unsigned Integer | Unsigned Integer |
Size | 2 Octet | Over 2 Octets |
Name | Error code | Description |
Concurrency Limit Exceeded | 0x83 | The server is unable to service the Read Request or Write Request because it exceeds the cuncurrency limit of the service |
Claims (20)
- 무선 통신시스템에서 블루투스(Bluetooth) 통신을 이용하여 웹 서버와 데이터를 송수신하기 위한 방법에 있어서, 게이트웨이(Gateway)에 의해 수행되는 방법은,제1 클라이언트 디바이스로부터 HTTP(Hyper Text Transfer Protocol) 요청 관련 정보를 포함하는 제1 쓰기 요청(write request)을 수신하는 단계;상기 수신된 제1 쓰기 요청에 포함된 정보를 기초로 생성된 HTTP 요청 관련 정보를 웹 서버로 전송하는 단계;상기 웹 서버로부터 상기 HTTP 요청 관련 정보에 대한 응답으로 HTTP 응답 메시지를 수신하는 단계;상기 수신된 HTTP 응답 메시지에 포함된 데이터의 상태를 나타내는 HTTP 상태 코드(HTTP Status Code)를 상기 제1 클라이언트 디바이스에게 통지(Notifying)하는 단계; 및상기 제1 클라이언트 디바이스로부터 상기 HTTP 상태 코드(HTTP Status Code)에 포함된 정보에 기초하여 데이터 전송을 요청하는 읽기 요청(read request)을 수신하는 단계를 포함하되,상기 제1 쓰기 요청(write request)을 수신하는 중 다른 클라이언트 디바이스로부터 제2 쓰기 요청(write request)을 수신한 경우, 상기 다른 클라이언트 디바이스에게 에러 응답(error response)를 전송하는 것을 특징으로 하는 방법.
- 제 1항에 있어서,상기 에러 응답(error response)은 상기 게이트웨이가 상기 제1 클라이언트 디바이스와 상기 HTTP 요청 관련 정보 생성을 위한 동작을 수행하고 있음을 나타내거나, 상기 게이트웨이가 상기 HTTP 요청 관련 정보를 생성하기 위한 동작을 수행하고 있어 자원이 충분하지 못함을 나타내는 것을 특징으로 하는 방법.
- 제 1에 있어서, 상기 제1 쓰기 요청(write request)을 수신하는 단계는,상기 제1 클라이언트 디바이스로부터 URI(Universal Resource Identifier) 쓰기 요청을 수신하는 단계;상기 제1 클라이언트 디바이스에게 상기 수신된 URI 쓰기 요청에 대한 응답으로 URI 쓰기 응답(write response)을 전송하는 단계;상기 제1 클라이언트 디바이스로부터 HTTP 헤더 쓰기 요청(HTTP Header write request)을 수신하는 단계;상기 제1 클라이언트 디바이스에게 상기 수신된 HTTP 헤더 쓰기 요청(HTTP Header write request)에 대한 응답으로 HTTP 헤더 쓰기 응답(HTTP Header write response)을 전송하는 단계;상기 제1 클라이언트 디바이스로부터 HTTP 엔터티 바디 쓰기 요청(Entity Body write request)을 수신하는 단계;상기 제1 클라이언트 디바이스에게 상기 수신된 HTTP 엔터티 바디 쓰기 요청(Entity Body write request)에 대한 응답으로 HTTP 엔터티 바디 쓰기 응답(HTTP Entity Body response)을 전송하는 단계;상기 제1 클라이언트 디바이스로부터 상기 HTTP 요청 메시지(HTTP request message)와 관련된 특정 동작을 지시하는 HTTP 컨트롤 포인트 요청(HTTP Control Point request)을 수신하는 단계; 및상기 제1 클라이언트 디바이스에게 상기 수신된 HTTP 컨트롤 포인트 요청(HTTP Control Point request)에 대한 응답으로 HTTP 컨트롤 포인트 응답(HTTP Control Point response)을 전송하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 1항에 있어서, 상기 읽기 요청(read request)을 수신하는 단계는,상기 제1 클라이언트 디바이스로부터 HTTP 헤더 읽기 요청(Header read request)을 수신하는 단계;상기 제1 클라이언트 디바이스에게 HTTP 헤더 읽기 요청(Header read request)에 대한 응답으로 HTTP 헤더 읽기 응답(HTTP Header read response)을 전송하는 단계;상기 제1 클라이언트 디바이스로부터 HTTP 엔터티 바디 읽기 요청(HTTP Entity Body read request)을 수신하는 단계; 및상기 제1 클라이언트 디바이스에게 HTTP 엔터티 바디 읽기 요청(HTTP Entity Body read request)에 대한 응답으로 HTTP 엔터티 바디 읽기 응답(HTTP Entity Body read response)을 전송하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 1항에 있어서, 상기 데이터는,상기 웹 서버로부터 수신된, 헤더 또는 엔터티 바디 중 적어도 하나를 포함하는 것을 특징으로 하는 방법.
- 제 1항에 있어서, 상기 HTTP 상태 코드(HTTP Status Code)는,데이터 길이와 관련된 정보를 포함하는 것을 특징으로 하는 방법.
- 제 1항에 있어서, 상기 HTTP 상태 코드(HTTP Status Code)는,데이터 길이와 관련된 정보와 함께 통지(Notify) 되는 것을 특징으로 하는 방법.
- 제 6항 또는 제 7항에 있어서,상기 데이터 길이와 관련된 정보는, 0 또는 1의 값을 포함하며,상기 데이터 길이와 관련된 정보가 1인 경우, 상기 데이터가 수신되었음을 나타내는 것을 특징으로 하는 방법.
- 제 6항 또는 제 7항에 있어서, 상기 데이터 길이와 관련된 정보는 데이터 길이를 포함하며,상기 데이터의 길이가 ATT_MTU-2 값과 동일하거나 작은 경우, read request 절차를 통해서 상기 데이터를 상기 제1 클라이언트 디바이스에게 전송하되,상기 ATT_MTU-2 값은 read request 절차를 통해서 한번에 전송할 수 있는 최대 데이터의 길이를 나타내는 것을 특징으로 하는 방법.
- 제 6항 또는 제 7항에 있어서, 상기 데이터 길이와 관련된 정보는 데이터 길이를 포함하며,상기 데이터의 길이가 ATT_MTU-2 값을 초과하고, 최대 ATT 데이터 길이(Max ATT Data Length)와 동일하거나 작은 경우, read blob request 절차를 통해서 상기 데이터를 상기 제1 클라이언트 디바이스에게 전송하되,상기 최대 ATT 데이터 길이는 Attribute Protocol을 통해서 전송할 수 있는 데이터의 최대 크기를 나타내는 것을 특징으로 하는 방법.
- 제 6항 또는 제 7항에 있어서, 상기 데이터 길이와 관련된 정보는 데이터 길이를 포함하며상기 데이터의 길이가 최대 ATT 데이터 길이(Max ATT Data Length)를 초과하는 경우, L2CAP CoC(Logical Link Control and Adaptation Protocol Connection Oriented Channel)을 통해서 상기 데이터를 상기 제1 클라이언트 디바이스에게 전송하는 것을 특징으로 하는 방법.
- 제 1항에 있어서,상기 제1 클라이언트 디바이스로부터 클라이언트 ID 값을 요청하는 요청 메시지를 수신하는 단계;상기 요청 메시지에 대한 응답으로 응답 메시지를 전송하는 단계; 및상기 클라이언트 ID 값이 NULL인 경우, 상기 제1 클라이언트 디바이스로부터 상기 클라이언트 ID 값을 제1 클라이언트 디바이스 정보로 변경을 요청하는 변경 요청 메시지를 수신하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 12항에 있어서,상기 제1 클라이언트 디바이스 정보는 사용자 ID 또는 상기 제1 클라이언트 디바이스의 ID 중 적어도 어느 하나를 포함하는 것을 특징으로 하는 방법.
- 제 12항에 있어서,상기 변경된 클라이언트 ID를 상기 게이트웨이와 연결된 다른 클라이언트 디바이스들에게 통지(Notifying)하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 12항에 있어서,상기 변경된 클라이언트 ID는 상기 제1 클라이언트의 요청 또는 특정 시간이 경과된 후에 NULL로 변경되는 것을 특징으로 하는 방법.
- 제 1항에 있어서,상기 제1 클라이언트 디바이스로부터 다른 클라이언트의 사용여부를 나타내는 프로텍티드(Protected) 값을 요청하는 요청 메시지를 수신하는 단계;상기 요청 메시지에 대한 응답으로 응답 메시지를 전송하는 단계; 및상기 프로텍티드 값이 No인 경우, 상기 제1 클라이언트 디바이스로부터 상기 프로텍티드 값의 변경을 요청하는 요청 메시지를 수신하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 16항에 있어서,상기 변경된 프로텍티드 값을 상기 게이트웨이와 연결된 다른 클라이언트 디바이스들에게 통지(Notifying)하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 16항에 있어서,상기 변경된 프로텍티드 값은 상기 제1 클라이언트의 요청 또는 특정 시간이 경과된 후에 No로 변경되는 것을 특징으로 하는 방법.
- 무선 통신시스템에서 블루투스(Bluetooth) 통신을 이용하여 데이터를 송수신하기 위한 방법에 있어서, 클라이언트 장치(Client Device)에 의해 수행되는 방법은,상기 서버에게 제1 오브젝트와 관련된 정보를 요청하기 위해 읽기 요청(Read Request)을 전송하는 단계;상기 서버로부터 상기 읽기 요청(Read Request)에 대한 응답으로 상기 제1 오브젝트(first Object)와 관련된 정보가 포함된 읽기 응답을 수신하는 단계;상기 서버에게 상기 제 1오브젝트를 제 2오브젝트로 변경하기 위한 메시지를 전송하는 단계; 및상기 서버로부터 제 2오브젝트와 관련된 에러 코드를 수신하는 단계를 포함하되,상기 에러코드는 상기 서버의 자원이 충분하지 않은 것을 나타내는 것을 특징으로 하는 방법.
- 무선 통신시스템에서 블루투스(Bluetooth) 통신을 이용하여 웹 서버와 데이터를 송수신하기 위한 방법에 있어서, 게이트웨이(Gateway)는,외부와 유선 및/또는 무선으로 신호를 송수신하기 위한 통신부; 및상기 통신부와 기능적으로 연결되는 제어부를 포함하되, 상기 제어부는,제1 클라이언트 디바이스로부터 HTTP(Hyper Text Transfer Protocol) 요청 관련 정보를 포함하는 제1 쓰기 요청(write request)을 수신하고,상기 수신된 제1 쓰기 요청에 포함된 정보를 기초로 상기 HTTP 요청 관련 정보를 생성하며,상기 생성된 HTTP 요청 관련 정보를 웹 서버로 전송하고,상기 웹 서버로부터 상기 HTTP 요청 관련 정보에 대한 응답으로 HTTP 응답 메시지를 수신하며,상기 수신된 HTTP 응답 메시지에 포함된 데이터의 상태를 나타내는 HTTP 상태 코드(Status Code)를 상기 제1 클라이언트 디바이스에게 통지하고,상기 제1 클라이언트 디바이스로부터 상기 HTTP 상태 코드(Status Code)에 포함된 정보에 기초하여 데이터 전송을 요청하는 읽기 요청(read request)을 수신하되,상기 제1 쓰기 요청(write request)를 수신하는 중 다른 클라이언트 디바이스로부터 제2 쓰기 요청(write request)을 수신한 경우, 상기 다른 클라이언트 디바이스에게 에러 응답(error response)을 전송하는 것을 특징으로 하는 장치.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020167029187A KR101990489B1 (ko) | 2014-04-21 | 2014-10-15 | 무선 통신시스템에서 블루투스를 이용하여 http 데이터를 전송하기 위한 방법 및 장치 |
US15/305,964 US9961481B2 (en) | 2014-04-21 | 2014-10-15 | Method and apparatus for transmitting a HTTP data using bluetooth in wireless communication system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201461982292P | 2014-04-21 | 2014-04-21 | |
US61/982,292 | 2014-04-21 | ||
US201462019853P | 2014-07-01 | 2014-07-01 | |
US62/019,853 | 2014-07-01 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015163547A1 true WO2015163547A1 (ko) | 2015-10-29 |
Family
ID=54332687
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2014/009694 WO2015163547A1 (ko) | 2014-04-21 | 2014-10-15 | 무선 통신시스템에서 블루투스를 이용하여 http 데이터를 전송하기 위한 방법 및 장치 |
Country Status (3)
Country | Link |
---|---|
US (1) | US9961481B2 (ko) |
KR (1) | KR101990489B1 (ko) |
WO (1) | WO2015163547A1 (ko) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017112120A1 (en) * | 2015-12-23 | 2017-06-29 | Intel Corporation | Method, system and apparatus for communication through wireless charging network |
WO2021215553A1 (ko) * | 2020-04-22 | 2021-10-28 | 엘지전자 주식회사 | 자율주행시스템에서 차량의 데이터 전송방법 |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11423165B2 (en) * | 2017-05-18 | 2022-08-23 | NeuShield, Inc. | Computer-implemented methods and system for preventing unauthorized file modification by malicious software and the like |
US10326804B1 (en) * | 2018-05-03 | 2019-06-18 | T-Mobile Usa, Inc. | Reducing network protocol overhead |
US11212368B2 (en) * | 2019-05-17 | 2021-12-28 | Netflix, Inc. | Fire-and-forget offload mechanism for network-based services |
US11991537B2 (en) * | 2021-06-21 | 2024-05-21 | Blackberry Limited | Method and system for cloud extended attribute profile |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20020081183A (ko) * | 2002-09-09 | 2002-10-26 | 이민수 | 블루투스 통신을 이용한 이동통신기기의 결제서비스시스템 및 그 방법 |
KR20030010002A (ko) * | 2001-07-25 | 2003-02-05 | 주식회사 비즈모델라인 | 블루투스를 이용한 무선 결제 방법 |
US20060039348A1 (en) * | 2004-08-20 | 2006-02-23 | Nokia Corporation | System, device and method for data transfer |
US20090327827A1 (en) * | 2004-11-23 | 2009-12-31 | Juniper Networks, Inc. | Rule-based networking device |
US20140032643A1 (en) * | 2012-07-30 | 2014-01-30 | Adam D. Dirstine | Enhanced http messaging for devices |
Family Cites Families (27)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6594697B1 (en) * | 1999-05-20 | 2003-07-15 | Microsoft Corporation | Client system having error page analysis and replacement capabilities |
AU5027200A (en) * | 1999-05-20 | 2000-12-12 | Intensifi, Inc. | Method and apparatus for access to, and delivery of, multimedia information |
US20020124100A1 (en) * | 1999-05-20 | 2002-09-05 | Jeffrey B Adams | Method and apparatus for access to, and delivery of, multimedia information |
US20020194498A1 (en) * | 2001-05-30 | 2002-12-19 | Palm, Inc. | Mobile communication system for location aware services |
US20040073811A1 (en) * | 2002-10-15 | 2004-04-15 | Aleksey Sanin | Web service security filter |
US7577964B2 (en) * | 2003-02-28 | 2009-08-18 | Hewlett-Packard Development Company, L.P. | System and methods for defining a binding for web-services |
US7676562B2 (en) * | 2004-01-20 | 2010-03-09 | Microsoft Corporation | Computer system for accessing instrumentation information |
US10057105B2 (en) * | 2004-11-23 | 2018-08-21 | Kodiak Networks, Inc. | Architecture framework to realize push-to-X services using cloudbased storage services |
WO2006063118A2 (en) * | 2004-12-07 | 2006-06-15 | Pure Networks, Inc. | Network management |
US8478849B2 (en) * | 2004-12-07 | 2013-07-02 | Pure Networks LLC. | Network administration tool |
US8190773B2 (en) * | 2005-06-03 | 2012-05-29 | Nokia Corporation | System and method for accessing a web server on a device with a dynamic IP-address residing behind a firewall |
KR100748937B1 (ko) * | 2006-08-04 | 2007-08-13 | 주식회사 이노와이어리스 | 이동전화번호를 이용한 wap데이터 추출방법 |
US7640460B2 (en) * | 2007-02-28 | 2009-12-29 | Microsoft Corporation | Detect user-perceived faults using packet traces in enterprise networks |
US10067831B2 (en) * | 2009-12-29 | 2018-09-04 | International Business Machines Corporation | Slice migration in a dispersed storage network |
US8346853B2 (en) * | 2010-05-27 | 2013-01-01 | Robert Paul Morris | Methods, systems, and computer program products for processing an attached command response |
US9176638B2 (en) * | 2011-08-26 | 2015-11-03 | Citrix Systems, Inc. | User interface for large scale system monitoring |
US9172807B2 (en) * | 2011-09-11 | 2015-10-27 | ZenDesk, Inc. | Techniques for customer relationship management |
US8924799B2 (en) * | 2012-04-16 | 2014-12-30 | Yahoo! Inc. | Method and system for providing a predefined content to a user |
US9037926B2 (en) * | 2012-06-07 | 2015-05-19 | International Business Machines Corporation | Background buffering of content updates |
US8799360B2 (en) * | 2012-08-31 | 2014-08-05 | Tweedle Group, Inc. | Systems, methods and articles for a server providing communications and services involving automobile head units |
US20150033335A1 (en) * | 2012-11-28 | 2015-01-29 | Verisign, Inc. | SYSTEMS AND METHODS TO DETECT AND RESPOND TO DISTRIBUTED DENIAL OF SERVICE (DDoS) ATTACKS |
US8869275B2 (en) * | 2012-11-28 | 2014-10-21 | Verisign, Inc. | Systems and methods to detect and respond to distributed denial of service (DDoS) attacks |
US9143978B2 (en) * | 2012-12-07 | 2015-09-22 | At&T Intellectual Property I, L.P. | Network congestion prevention and/or mitigation |
WO2014140807A2 (en) * | 2013-03-15 | 2014-09-18 | Assa Abloy Ab | Method, system, and device for generating, storing, using, and validating nfc tags and data |
US20150296027A1 (en) * | 2014-04-09 | 2015-10-15 | Nokia Corporation | Continuous Browsing Across Devices |
US10536523B2 (en) * | 2014-05-11 | 2020-01-14 | Microsoft Technology Licensing, Llc | File service using a shared file access-rest interface |
CA2971865A1 (en) * | 2014-12-22 | 2016-06-30 | Capital One Services, Llc | A system, method, and apparatus for locating a bluetooth enabled transaction card |
-
2014
- 2014-10-15 WO PCT/KR2014/009694 patent/WO2015163547A1/ko active Application Filing
- 2014-10-15 US US15/305,964 patent/US9961481B2/en active Active
- 2014-10-15 KR KR1020167029187A patent/KR101990489B1/ko active IP Right Grant
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20030010002A (ko) * | 2001-07-25 | 2003-02-05 | 주식회사 비즈모델라인 | 블루투스를 이용한 무선 결제 방법 |
KR20020081183A (ko) * | 2002-09-09 | 2002-10-26 | 이민수 | 블루투스 통신을 이용한 이동통신기기의 결제서비스시스템 및 그 방법 |
US20060039348A1 (en) * | 2004-08-20 | 2006-02-23 | Nokia Corporation | System, device and method for data transfer |
US20090327827A1 (en) * | 2004-11-23 | 2009-12-31 | Juniper Networks, Inc. | Rule-based networking device |
US20140032643A1 (en) * | 2012-07-30 | 2014-01-30 | Adam D. Dirstine | Enhanced http messaging for devices |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2017112120A1 (en) * | 2015-12-23 | 2017-06-29 | Intel Corporation | Method, system and apparatus for communication through wireless charging network |
US10123154B2 (en) | 2015-12-23 | 2018-11-06 | Intel Corporation | Method, system and apparatus for communication through wireless charging network |
WO2021215553A1 (ko) * | 2020-04-22 | 2021-10-28 | 엘지전자 주식회사 | 자율주행시스템에서 차량의 데이터 전송방법 |
Also Published As
Publication number | Publication date |
---|---|
KR20160141759A (ko) | 2016-12-09 |
US9961481B2 (en) | 2018-05-01 |
US20170048656A1 (en) | 2017-02-16 |
KR101990489B1 (ko) | 2019-09-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018048268A1 (ko) | 블루투스 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2015137601A1 (ko) | 무선통신 시스템에서 데이터 전송률 조절 방법 및 장치 | |
WO2018074892A1 (ko) | 블루투스 기술을 이용하여 데이터를 송수신하기 위한 방법 및 장치 | |
WO2015069093A1 (ko) | 블루투스 연결 방법 및 장치 | |
WO2014204272A1 (ko) | 무선 통신시스템에서 블루투스를 이용하여 멀티미디어 콘텐츠를 재생하기 위한 방법 및 장치 | |
WO2018222024A1 (ko) | 블루투스 le 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2016182404A1 (ko) | 블루투스 저전력 에너지 기술을 이용하여 대체 통신 수단을 연결하기 위한 방법 및 장치 | |
WO2015194854A1 (ko) | 블루투스 le(low energy) 기술을 이용하여 디바이스 간 커넥션을 형성하기 위한 방법 및 장치 | |
WO2015163547A1 (ko) | 무선 통신시스템에서 블루투스를 이용하여 http 데이터를 전송하기 위한 방법 및 장치 | |
WO2015182896A1 (ko) | 블루투스 연결 방법 및 장치 | |
WO2015163680A1 (ko) | 무선 통신 시스템에서 블루투스 저전력 에너지 기술을 이용하여 데이터를 송수신하기 위한 방법 및 장치 | |
WO2020096412A1 (ko) | 블루투스 기술을 이용하여 오디오 데이터를 수신하기 위한 방법 및 이에 대한 장치 | |
WO2018169380A1 (ko) | 블루투스 기술을 이용하여 오디오 신호를 처리하기 위한 방법 및 장치 | |
WO2017030232A1 (ko) | 데이터 송수신 방법 및 이를 위한 디바이스 | |
WO2015069031A1 (ko) | 블루투스를 이용한 커뮤니케이션 링크 형성 방법 및 장치 | |
WO2018021877A1 (ko) | 디바이스의 연결을 형성하기 위한 방법 및 장치 | |
WO2020213959A1 (ko) | 블루투스 기술을 이용하여 오디오 데이터를 수신하기 위한 방법 및 이에 대한 장치 | |
WO2015002385A1 (ko) | 무선 통신시스템에서 디바이스들 간에 커뮤니케이션을 위한 방법 및 장치 | |
WO2016178542A1 (ko) | 블루투스에서 데이터를 송수신하기 위한 방법 및 장치 | |
WO2017018604A1 (ko) | 블루투스 le(low energy) 기술을 이용하여 대체 통신 수단을 연결하기 위한 방법 및 장치 | |
WO2016036206A2 (ko) | 블루투스 le(low energy) 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2019031822A1 (ko) | 블루투스 저전력 에너지 기술을 이용하여 디바이스간 연결을 형성하기 위한 방법 및 장치 | |
WO2020149708A1 (ko) | 블루투스 기술을 이용하여 오디오 서비스를 제공하기 위한 방법 및 장치 | |
WO2020180168A1 (ko) | 블루투스 기술을 이용하여 오디오 데이터를 수신하기 위한 방법 및 이에 대한 장치 | |
WO2018009040A1 (ko) | 블루투스 기술을 이용하여 데이터를 송수신하기 위한 방법 및 장치 |
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: 14890057 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20167029187 Country of ref document: KR 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: 15305964 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14890057 Country of ref document: EP Kind code of ref document: A1 |