US20050059345A1 - Method and system for establishing a wireless communications link - Google Patents
Method and system for establishing a wireless communications link Download PDFInfo
- Publication number
- US20050059345A1 US20050059345A1 US10/660,544 US66054403A US2005059345A1 US 20050059345 A1 US20050059345 A1 US 20050059345A1 US 66054403 A US66054403 A US 66054403A US 2005059345 A1 US2005059345 A1 US 2005059345A1
- Authority
- US
- United States
- Prior art keywords
- link
- communications link
- uwb
- remote device
- short
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
- H04B1/69—Spread spectrum techniques
- H04B1/7163—Spread spectrum techniques using impulse radio
- H04B1/7183—Synchronisation
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/18—Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present invention relates to wireless communications. More particularly, the present invention relates to techniques for initiating wireless communications links.
- ultra wideband (UWB) techniques have become an attractive solution for short-range wireless communications because they allow for devices to exchange information at relatively high data rates.
- IR impulse radio
- data is transmitted by employing short baseband pulses that are separated in time by gaps.
- IR does not use a carrier signal.
- RF gating is a particular type of IR in which the impulse is a gated RF pulse. This gated pulse is a sine wave masked in the time domain with a certain pulse shape.
- IR transmission facilitates a relatively simple transmitter design, which basically requires a pulse generator and an antenna.
- This design does not necessarily require a power amplifier, because transmission power requirements are low.
- this design does not generally require modulation components such as voltage controlled oscillators (VCOs) and mixers, because the impulses are baseband signals.
- VCOs voltage controlled oscillators
- IR receiver designs are more complex than their corresponding transmitter designs. However, these designs are much simpler than conventional receiver designs because they typically do not employ intermediate frequency (IF) signals or filters.
- IF intermediate frequency
- IR impulses have to be very short in duration (e.g., a couple of nanoseconds). This requirement places stringent timing demands on receiver timing accuracy. The fulfillment of these demands can also provide IR receivers with accurate time resolution and positioning capabilities.
- Bluetooth defines a short-range radio network, originally intended as a cable replacement. It can be used to create ad hoc networks of up to eight devices, where one device is referred to as a master device. The other devices are referred to as slave devices. The slave devices can communicate with the master device and with each other via the master device.
- the Bluetooth Special Interest Group Specification Of The Bluetooth System , Volumes 1 and 2, Core and Profiles: Version 1.1, Feb. 22, 2001, describes the principles of Bluetooth device operation and communication protocols. This document is incorporated herein by reference in its entirety. The devices operate in the 2.4 GHz radio band reserved for general use by Industrial, Scientific, and Medical (ISM) applications. Bluetooth devices are designed to find other Bluetooth devices within their communications range and to discover what services they offer.
- the present invention is directed to a method and system for establishing a wireless communications link.
- the method and system determine, through a first short-range communications link of a first type, whether a remote device is capable of supporting a short-range communications link of a second type.
- the method and system also exchange information with the remote device across the first communications link to establish a second short-range communications link of the second type. Once established, communications with the remote device across the second short-range communications link may commence.
- Exchanging information with the remote device across the first communications link to establish the second communications link may include sending a request to the remote device across the first communications link. This request inquires whether the remote device desires to establish the second communications link. If the remote device so desires, an acknowledgement is received through the first communications link. When the first communications link is a Bluetooth link and the second communications link is a UWB link, this request may include a Bluetooth link manager protocol (LMP) message to the remote device.
- LMP Bluetooth link manager protocol
- the method and system may direct the remote device to start communicating across the second short-range wireless communications link.
- this may include sending a Bluetooth LMP message to the remote device.
- This LMP message is adapted to direct the remote device to begin accepting transmissions across the UWB link and may include one or more UWB parameters.
- the method and system may also establish the first short-range communications link with the remote device.
- the first link is a Bluetooth link
- this may include performing a Bluetooth paging process with the remote device.
- the present invention is also directed to a wireless communications device.
- This device includes a first segment that exchanges information with a remote device across a first short-range wireless communications link of a first type.
- the device includes a host that is coupled to the first segment. The host sets up a second short-range wireless communications link of a second type by causing the first segment to exchange information with the remote device across the first communications link. This information includes one or more parameters of the second short-range communications link.
- the device includes a second segment adapted to exchange information with the remote device across the second communications link.
- the first communications link may be a Bluetooth link and the second communications link may be a UWB link.
- the first segment of the device may include a link manager that exchanges one or more Bluetooth LMP messages with the remote device. These messages may include a message to direct the remote device to begin accepting transmissions across the UWB link, a message to inquire whether the remote device desires to establish the UWB link, and/or a message to determine whether the remote device is capable of supporting the UWB link. These messages may each include one or more UWB parameters.
- the present invention advantageously allows a UWB link to be established without transmitting UWB signals.
- Bluetooth may be used to establish UWB links. Since Bluetooth is viewed as a technology that will be soon be implemented in most phones and consumer electronic devices, devices having UWB capabilities will also be Bluetooth equipped. Accordingly, the present invention advantageously provides for the integration of Bluetooth and UWB capabilities
- a computer-readable medium may be encoded with processing instructions for implementing the various method and functions herein, such as establishing a wireless communications link, to be performed by a computerized system which can be embodied in wireless communications device.
- FIG. 1 is a diagram of an exemplary operational environment
- FIG. 2 is a block diagram of an exemplary communications device architecture in accordance with one embodiment
- FIG. 3 is a block diagram of an exemplary communications device implementation
- FIG. 4 is a flowchart of an exemplary link establishment process
- FIG. 5 is a flowchart of a second communications link initiation
- FIGS. 6-8 are diagrams of interactions between two devices according to the present invention.
- FIG. 9 is an exemplary communications device architecture in accordance with a further embodiment
- FIG. 10 is an exemplary packet type table
- FIG. 11 is an exemplary packet type table request parameters and packet type table parameters
- FIG. 12 is a diagram showing details of a packet type table parameter
- FIG. 13 is a diagram of a packet structure.
- FIG. 1 is a diagram of an operational environment which includes wireless communications devices 102 and 104 .
- Devices 102 and 104 are capable of engaging in wireless communications via at least two different types of short-range wireless links.
- devices 102 and 104 may support both Bluetooth and UWB links.
- Devices 102 and 104 each have a communications range that is defined by a coverage area. As shown in FIG. 1 , a coverage area 103 defines the communications range of device 102 , while a coverage area 105 defines the communications range of device 104 . These coverage areas illustrate a range in which the corresponding device can communicate across two different link types (e.g., both Bluetooth and UWB).
- two different link types e.g., both Bluetooth and UWB
- first wireless communications link 110 and a second wireless communications link 112 are established between devices 102 and 104 .
- These links may be of different types.
- first link 110 may be a Bluetooth link
- second link 112 may be a UWB link.
- first device 102 may communicate across first link 110 to establish second link 112 , and to initiate communications across link 112 .
- FIG. 2 is a block diagram showing a wireless communications device architecture, which may be used for devices 102 and 104 . Although this architecture is described in the context of Bluetooth and UWB communications, it may be employed with other wireless communications technologies.
- the device architecture of FIG. 2 includes a host 202 , which is coupled to a Bluetooth segment 204 , and a UWB segment 206 .
- Host 202 is responsible for functions involving user applications and higher protocol layers, while Bluetooth segment 204 and UWB segment 206 are responsible for lower layer protocols. More particularly, Bluetooth segment 204 is responsible for Bluetooth specific communications with other devices, and UWB segment 206 is responsible for UWB specific communications with other devices.
- Bluetooth segment 204 includes a host controller interface (HCI) 208 , a link manager 210 , a link controller 212 , a Bluetooth transceiver 214 , and an antenna 216 .
- HCI host controller interface
- Link manager 210 performs functions related to Bluetooth link set-up, security and control. These functions involve discovering corresponding link managers at remote devices and communicating with them according to a link manager protocol (LMP). To perform these functions, LMP defines a set of messages, which are also referred to as protocol data units (PDUs). Link manager 210 exchanges these PDUs with link managers at remote devices. Various LMP PDUs for performing the techniques of the present invention are described below with reference to FIG. 6 .
- Link manager 210 exchanges information with host 202 across HCI 208 .
- This information may include commands received from host 202 , and information transmitted to host 202 .
- HCI 208 defines a set of messages, which provide for this exchange of information.
- Various HCI messages for performing the techniques of the present invention are described below with reference to FIG. 6 .
- Link controller 212 operates as an intermediary between link manager 210 and Bluetooth transceiver 214 .
- Link controller 212 also performs baseband processing for Bluetooth transmission, such as error correction encoding and decoding.
- link controller 212 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of such physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol.
- ARQ automatic repeat request
- FIG. 2 shows that Bluetooth transceiver 214 is coupled to an antenna 216 .
- Transceiver 214 includes electronics that allow the device of FIG. 2 (in conjunction with antenna 216 ) to exchange wireless Bluetooth signals with devices, such as remote device 104 .
- Such electronics include modulators and demodulators, amplifiers, and filters.
- UWB segment 206 When the device of FIG. 2 engages in UWB communications, it employs the services of UWB segment 206 .
- UWB segment 206 includes a UWB module 218 , a UWB transceiver 220 , and an antenna 222 .
- UWB module 218 provides for the exchange of information across UWB links according to one or more protocol layers.
- UWB module may provide session management functionality to manage various UWB sessions.
- UWB module 218 may perform baseband processing, such as error correction encoding and decoding.
- UWB module 218 perform various link level protocols with remote devices according to physical layer protocols. Examples of such protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol.
- ARQ automatic repeat request
- UWB transceiver 220 is coupled to antenna 222 .
- UWB transceiver 220 includes electronics, which allow the device of FIG. 2 (in conjunction with antenna 222 ) to exchange wireless UWB signals with devices, such as remote device 104 .
- such electronics may include a pulse generator.
- For the reception of UWB signals, such electronics may include timing circuitry and filters.
- FIG. 2 may be implemented in hardware, software, firmware, or any combination thereof.
- FIG. 3 One such implementation is shown in FIG. 3 .
- This implementation includes a processor 310 , a memory 312 , and a user interface 314 .
- the implementation of FIG. 3 includes Bluetooth transceiver 214 , antenna 216 , UWB transceiver 220 , and antenna 222 .
- Transceivers 214 and 220 may be implemented as described above with reference to FIG. 2 .
- processor 310 is coupled to transceivers 214 and 220 .
- Processor 310 controls device operation.
- Processor 310 may be implemented with one or more microprocessors that are each capable of executing software instructions stored in memory 312 .
- Memory 312 includes random access memory (RAM), read only memory (ROM), and/or flash memory, and stores information in the form of data and software components (also referred to herein as modules). These software components include instructions that can be executed by processor 310 . Various types of software components may be stored in memory 312 . For instance, memory 312 may store software components that control the operations of transceivers 214 and 220 . Also, memory 312 may store software components that provide for the functionality of host 202 , HCI interface 208 , link manager 210 , link controller 212 , and UWB module 218 .
- memory 312 may store software components that control the exchange of information through user interface 314 .
- user interface 314 is also coupled to processor 310 .
- User interface 314 facilitates the exchange of information with a user.
- FIG. 3 shows that user interface 314 includes a user input portion 316 and a user output portion 318 .
- User input portion 316 may include one or more devices that allow a user to input information. Examples of such devices include keypads, touch screens, and microphones.
- User output portion 318 allows a user to receive information from WCD 102 .
- user output portion 318 may include various devices, such as a display, and one or more audio speakers.
- Exemplary displays include liquid crystal displays (LCDs), and video displays.
- the elements shown in FIG. 3 may be coupled according to various techniques.
- One such technique involves coupling transceivers 214 and 220 , processor 310 , memory 312 , and user interface 314 through one or more bus interfaces.
- each of these components is coupled to a power source, such as a removable and rechargeable battery pack (not shown).
- FIG. 4 is a flowchart of a link establishment process according to the present invention.
- an initiating device such as device 102
- uses a first communications link with a remote device such as device 104
- a second communications link with the remote device.
- These communications links may be of different types.
- the first communications link may be a Bluetooth link
- the second communications link may be a UWB link.
- This process begins with a step 402 , in which the initiating device and the remote device enter into short-range communications proximity.
- the initiating device learns the identity (or discovers the existence) of the remote device.
- This step may comprise the initiating device and the remote device engaging in an inquiry process.
- the initiating device operates in an inquiry state while the remote device operates in an inquiry scan state.
- the initiating device transmits an inquiry packet and the remote device listens for inquiry packets.
- the remote device When the remote device receives the inquiry packet from the initiating device, it transmits one or more frequency hop synchronization (FHS) packets, which are received by the initiating device.
- the FHS packet(s) allow the initiating device to become synchronized with the hop sequence of the remote device.
- the FHS packet(s) enable the initiating device to derive information necessary to make a Bluetooth connection with the remote device. This information includes the native clock of the remote device (CLKN), the Bluetooth address (BD_ADDR) of the remote device, and error correction coding information.
- the initiating device and the remote device join an ad hoc network to form the first communications link.
- this step may comprise the initiating device and the remote device performing a paging process.
- the paging process results in an unsecured connection being established between these devices.
- Bluetooth paging involves the exchange of various information between the initiating device (which is in a paging state) and remote device (which is in a page scan state).
- the initiating device enters the paging state and transmits one or more paging packets.
- Each of these paging packets includes an identification number based on the address of the remote device.
- the remote device (which is in the page scan state) responds to the paging packets by transmitting a packet containing its address.
- the initiating device receives this packet from the remote device.
- the initiating device transmits a frequency hop synchronization (FHS) packet.
- FHS frequency hop synchronization
- the FHS packet is used to pass information that allows the remote device to synchronize with the frequency hopping sequence of the initiating device.
- the remote device Upon receipt of this FHS packet, the remote device transmits a further packet to confirm receipt of the FHS packet.
- a Bluetooth link is formed between the initiating device and the remote device. Accordingly, both devices enter into a connection state. In the connection state, the initiating device operates as a master device and the remote device operates as a slave device. Thus, the remote device employs the timing and frequency hopping sequence of the initiating device. Additionally, the initiating device transmits a packet to verify that a link has been set up. The remote device confirms this link by sending a packet to the initiating device.
- the initiating device determines the communications capabilities of the remote device. This step may comprise these devices exchanging one or more messages, such as a request for the capabilities of the remote device and a response containing these capabilities. These capabilities may be communicated in the form of link type identifiers and their associated transmission formats (e.g., UWB radio standard and version).
- the initiating device determines whether the remote device is capable of forming the second link. For example, this step may comprise the initiating device determining whether the remote device has UWB communications capabilities. If so, then operation proceeds to a step 412 .
- the initiating device initiates a second link establishment process. An exemplary operation of this step is described below with reference to FIG. 5 .
- the initiating device may direct the remote device to start communicating across the second link in a step 416 .
- a step 420 follows step 416 .
- the initiating device and the remote device may engage in communications across the second link
- FIG. 5 is a flowchart illustrating a performance of step 412 in greater detail.
- This performance begins with a step 502 .
- the initiating device sends a request to the remote device over the first communications link.
- This request asks the remote device whether it desires to establish the second link.
- this request contains parameters for the second link. These parameters may include, for example, transmission format (e.g., UWB radio standard and version), and traffic classes.
- this request may include an LMP message, such as the LMP_host_connection_request_ext PDU, which is described below in greater detail.
- the initiating device receives an acknowledgement transmitted by the remote device.
- This acknowledgement is transmitted across the first link and indicates that the remote device desires to establish the second communications link.
- this acknowledgement may be in the form of an LMP message, such as a LMP_setup_complete message.
- the second communications link is set up (or configured).
- embodiments of the present invention may employ Bluetooth communications to initiate UWB communications.
- current Bluetooth standards do not provide a mechanism for establishing UWB connections. Therefore, the present invention provides for additional and modified Bluetooth messages that may be employed in establishing UWB communications. These messages include LMP PDUs and HCI commands. An exemplary set of such messages are provided below in Table 1. A description of these messages follows this table.
- Table 1 provides a listing of an exemplary set of modified or new LMP messages according to an embodiment of the present invention. As indicated by this table, LMP_features_req_ext and LMP_features_res_ext are modified messages of the present invention. These messages are based on the standard Bluetooth PDUs LMP_features_req and LMP_features_res.
- a first device transmits a LMP_features_req PDU to a second device.
- This PDU may be transmitted at any time after the two devices have completed a paging process.
- the second device transmits a LMP_features_res PDU, which conveys the features that it supports.
- LMP_features_req and LMP_features_res each includes a features parameter, which conveys the features supported by the transmitting device in a bitmap.
- This bitmap includes multiple bits, each bit corresponding to a particular radio, baseband, or LMP feature.
- the features parameter of the LMP_features_req_ext and LMP_features_res_ext PDUs has an extended bitmap.
- This extended bitmap includes a UWB capable bit as well as UWB information bits, which convey associated information, such as particular UWB operational parameters that are supported. Examples of such operational parameters include transmission format (e.g., UWB radio standard and version) and traffic classes.
- the present invention provides for a new LMP_switch_to_UWB_link_req PDU.
- This PDU is a directive that first UWB capable device may transmit to a second UWB capable device to direct the second device to commence accepting transmissions across a UWB link.
- This message may include parameters of the UWB link so that a receiving device may configure itself to receive and/or send UWB transmissions. Examples of such parameters include transmission format (e.g., UWB radio standard and version) and traffic classes.
- the second UWB capable device Upon receipt of this message, the second UWB capable device sends the first device a Bluetooth LMP_accepted PDU so that the first device may initiate UWB communications.
- LMP_host_connection_req_ext is a standard Bluetooth LMP PDU. This PDU indicates that a device wishes to create a connection with another device involving protocol layers above the link manager layer.
- LMP_host_connection_req_ext is an extension of LMP_host_connection_req. This extension provides parameter values and/or parameters to indicate that a device wishes to establish a UWB link with another device. For instance, such parameter values and/or parameters may convey information such as transmission format (e.g., UWB radio standard and version) and traffic classes.
- Table 1 also provides a listing of HCI commands according to an embodiment of the present invention.
- the present invention provides for a modified HCI_create_connection_req command.
- the standard Bluetooth HCI command instructs the link manager of a local Bluetooth device to create a connection with a remote Bluetooth device.
- this command instructs the link manager of the local Bluetooth device to initiate a paging process with the remote device.
- This command includes the following parameters: BD_ADDR, Packet_Type, Page_Scan_Repetition_Mode, Page_Scan_Mode, Clock_Offset, and Allow_Role_Switch. These parameters are described below.
- the BD_ADDR parameter specifies the Bluetooth device address (BD_ADDR) of the remote device.
- the Packet_Type parameter specifies which packet types the link manager shall use for the connection.
- the Page_Scan_Repetition_Mode and Page_Scan_Mode parameters indicate page scan modes supported by the remote device.
- the Clock_Offset parameter indicates a difference between the local device's clock and the clock of the remote device with BD_ADDR.
- the Allow_Role_Switch parameter indicates whether the local device accepts or rejects the request of a master-slave role switch.
- a modified HCI_create_connection_req command provides for a UWB value for the Packet_Type parameter.
- this modified HCI command instructs a link manager at a local device to pursue a UWB connection with a remote device specified by the BD_ADDR parameter.
- the present invention also provides for a modified HCI_connection_request_event command.
- this command is passed from the link manager to the host.
- the standard Bluetooth HCI_connection_request_event command includes a BD_ADDR parameter, a Class-of_Device parameter, and a Link_Type parameter. These parameters specify information regarding a device which is trying to establish a connection through a HCI_create_connection_req command.
- a modified HCI_connection_request_event command of the present invention provides for values which convey UWB information to be included in the Class-of_Device and Link_Type parameters.
- additional modifications to this command may exist, such as the creation of other parameters.
- the HCI_connection_complete_event message provides an indication to the hosts that a new connection has been established.
- the standard Bluetooth HCI_connection_complete_event message includes a Status parameter, a Connection_Handle parameter, a BD_ADDR parameter, a Link_Type parameter, and an Encryption_Mode parameter.
- the Link_Type parameter is modified to include a value to indicate that a UWB link has been completed.
- FIG. 6 illustrates an interaction between Bluetooth and UWB capable devices involving the messages of Table 1. This diagram is described with reference to the operational environment of FIG. 1 . However, this interaction may be performed in other environments.
- initiating device 102 includes a host 202 a , a link manager 210 a , an HCI 208 a , and a UWB segment 206 a .
- remote device 104 includes a host 202 b , a link manager 210 b , an HCI 208 b , and a UWB segment 206 b .
- devices 102 and 104 may each include a link controller 212 to handle baseband processing and information exchange as described above with reference to FIG. 2 .
- FIG. 6 includes a series of events that occur in a chronological sequence according to a time axis 601 . This interaction begins with an inquiry process 602 . In this process, initiating device 102 learns the identity of remote device 104 .
- terminal host 202 a sends message 603 to link manager 210 a .
- message 603 is a HCI_create_connection_req, which is modified as described above.
- message 603 includes the BD_ADDR of remote device 104 .
- this message instructs link manager 210 a to pursue a UWB connection with remote device 104 .
- link manager 210 a initiates a paging process 604 with remote device 104 .
- This paging process results in a link manager protocol (LMP) connection 606 being established between link managers 210 a and 210 b .
- LMP link manager protocol
- link manager 210 a transmits LMP_features_req_ext message 608 to link manager 210 b .
- this message inquires about the features supported by remote device 104 .
- link manager 210 b sends LMP_features res_ext message 610 to link manager 210 b .
- Message 610 conveys the features supported by remote device 104 .
- link manager 210 a sends LMP_host_connection_req_ext message 612 to link manager. As described above, this message is an extended Bluetooth message indicating that initiating device 102 wishes to create a UWB connection with remote device 104 .
- link manager 210 b Upon receipt of message 612 , link manager 210 b sends a message 614 to terminal host 202 b across HCI 208 b .
- Message 614 is an HCI_connection_request_event message, which is modified in the manner described above.
- message 614 includes parameter values which convey UWB information.
- terminal host 202 b may agree to establish a UWB connection with initiating device 102 . If so, then terminal host 202 b sends a message 616 to link manager 210 b across HCI 208 b . As shown in FIG. 6 , message 616 is a standard Bluetooth HCI_accept_connection_request message.
- devices 102 and 104 may engage in additional Bluetooth processes, as indicated by event 618 .
- additional Bluetooth processes include a master/slave switch and an authentication process.
- a master/slave switch is a process in which the master and slave roles of devices 102 and 104 are exchanged.
- Authentication is a process where two devices verify that they both have the same secret key. This secret key can then be used to effect security features, such as link encryption.
- FIG. 6 shows that link managers 210 a and 210 b exchange Bluetooth LMP_setup_complete messages 620 and 622 .
- the exchange of these messages indicates that the exchange of information between devices 102 and 104 for setting up a UWB link is complete.
- link manager 210 a sends a message 624 to host 202 a across HCI 208 a .
- link manager 210 b sends a message 626 to host 202 b across HCI 208 b .
- Messages 624 and 626 are each HCI_connection_complete_event messages. As shown in FIG. 6 , these messages are modified as described above such that the Link_Type parameter includes a value indicating that a UWB link has been completed.
- link manager 210 a sends to link manager 210 b LMP_switch_to_UWB_link_req message 628 .
- this message is a new message that requests remote device 104 to commence communications across the established UWB link. If the remote device 104 accepts this request, it sends initiating device 102 LMP_accepted message 630 .
- link manager 210 a receives LMP_accepted message 630 , devices 102 and 104 commence UWB communications, as indicated by interaction 632 .
- link manager 210 b of remote device 104 may send one or more HCI messages to host 202 b . These messages indicate to host 202 b that UWB transmissions are forthcoming. Upon receipt of such messages, host 202 b may send one or more messages to UWB segment 206 b directing it to prepare for the reception of UWB transmissions.
- link manager 210 a of initiating device 102 may send one or more HCI messages to host 202 a . These messages indicate to host 202 b that UWB transmissions may commence. In response to such messages, host 202 a may send one or more messages to UWB segment 206 a , which causes it to initiate UWB transmissions.
- FIG. 7 is a diagram illustrating a further interaction between devices in which a Bluetooth link is used to establish a UWB link. This interaction is similar to the interaction of FIG. 6 . However, this interaction additionally includes host 202 a sending to link manager 210 a an HCI_QoS_setup message 702 .
- This message is a standard Bluetooth message which specifies quality of service parameters, such as peak bandwidth, for a particular connection.
- the UWB link has been assigned a connection handle. Specific QoS requirements, like peak bandwidth is mapped to this connection handle. Message 702 assigns a large peak bandwidth to this connection handle. This signifies that a switch to UWB communications is desired. Accordingly, in response to receiving message 702 , link manager 210 a sends message 628 . As described above, this message requests remote device 104 to commence communications across the established UWB link.
- FIG. 8 shows yet a further interaction between devices according to the present invention. This interaction is also similar to the interaction of FIG. 6 . However, in this interaction, messages 612 , 614 , 624 , and 626 are replaced with messages 802 , 804 , 806 , and 808 , respectively. Further, this interaction includes an additional message 810 .
- Message 802 is a standard Bluetooth LMP_host_connection_req message, which indicates that initiating device 102 wishes to create a Bluetooth connection with remote device 104 .
- Message 804 is a standard Bluetooth HCI_connection_request_event command, which specifies information regarding initiating device 104 .
- Messages 806 and 808 are standard Bluetooth HCI_connection_complete_event messages.
- message 810 initiates the setup of a UWB link.
- Message 810 is a modified HCI_Change_Connection_Packet_Type command. This modified command includes values for its packet type parameter that designates a UWB link (as well as its corresponding parameters).
- link manager 210 a transmits message 628 to remote device 104 to commence communications across a UWB link.
- UWB or other High Bit Rate (High Rate or HR) wireless transmissions may be handled as a part of a Bluetooth piconet, employing wireless device architectures such as the architecture described below with reference to FIG. 9 .
- UWB/HR radio transmissions may be scheduled as Bluetooth transmissions in a time division manner that employs the timing of the Bluetooth slot structure.
- the UWB/HR link may be established in a link level by employing a framework presented in release after Bluetooth Version 1.2.
- release after Bluetooth Version 1.2 provides for the exchange of packet type requests and responses, which communicate link and packet type capabilities of a device.
- Different modulation and radio implementations can be provided by existing LMP packet type request and response commands (i.e., LMP_packet_typereq and LMP_packet_type_res), involving addresses (e.g., logical transport address or LT_ADDR) and packet type table (ptt) entries chosen according to desired modulation/radio characteristics.
- the logical transport address may be selected according to the Bluetooth Address (BD_ADDR) and the packet type table may be extended to include HR data and UWB data along with basic rate data and medium rate data. Accordingly, UWB and other higher rate links may be established by employing mechanisms provided by release after Bluetooth Version 1.2 while retaining backwards compatibility and reducing complexity in the development of media access control (MAC) to support the additional links.
- BD_ADDR Bluetooth Address
- MAC media access control
- FIG. 9 is a block diagram showing a wireless communications device architecture, which may be used for devices 102 and 104 , in accordance with the present invention.
- This architecture may be employed with the various systems and methods described above for establishing UWB links through Bluetooth communications.
- this architecture may employ packet type table techniques described in this section and with reference to FIGS. 11 and 12 .
- this architecture is described in the context of Bluetooth and UWB communications, it may be employed with other wireless communications technologies.
- the device architecture of FIG. 9 includes a host 202 , which is coupled to a segment 900 .
- Host 202 is responsible for functions involving user applications and higher protocol layers, while segment 900 is responsible for lower layer protocols, such as Bluetooth (e.g., basic rate, medium rate or higher rate), UWB, and/or other specific communications.
- Bluetooth e.g., basic rate, medium rate or higher rate
- UWB UltraWB
- segment 900 includes a host controller interface (HCI) 902 , a link manager 904 , a Bluetooth (BT) link controller 906 , a Bluetooth (BT) transceiver 908 , an antenna 910 , a UWB link controller 912 , a UWB/HR transceiver 914 , and an antenna 916 .
- HCI host controller interface
- BT Bluetooth
- BT Bluetooth
- Link manager 904 performs functions related to Bluetooth link and UWB link set-up, security and control. These functions involve discovering corresponding link managers at remote devices and communicating with them according to the link manager protocol (LMP). More particularly, link manager 904 exchanges LMP PDUs with link managers at remote devices. LMP PDUs for performing the techniques of the present invention are described herein with reference to FIGS. 6, 11 , and 12 .
- Link manager 904 exchanges information with host 202 across HCI 902 .
- This information may include commands received from host 202 , and information transmitted to host 202 .
- HCI 902 defines a set of messages, which provide for this exchange of information.
- BT link controller 906 operates as an intermediary between link manager 904 and BT transceiver 908 .
- Link controller 906 also performs baseband processing for Bluetooth transmissions, such as error correction encoding and decoding.
- link controller 906 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol.
- ARQ automatic repeat request
- BT transceiver 908 is coupled to antenna 910 .
- Transceiver 908 includes electronics to (in conjunction with antenna 910 ) exchange wireless Bluetooth signals with devices, such as remote device 104 .
- Such electronics include modulators, demodulators, amplifiers, and filters.
- UWB link controller 912 operates as an intermediary between link manager 904 and UWB/HR transceiver 914 .
- Link controller 912 also performs baseband processing for UWB transmission, such as error correction encoding and decoding.
- link controller 912 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of such physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol.
- ARQ automatic repeat request
- UWB/HR transceiver 914 is coupled to an antenna 916 .
- Transceiver 914 includes electronics to (in conjunction with antenna 916 ) exchange wireless UWB or HR signals with devices, such as remote device 104 .
- devices such as remote device 104 .
- such electronics may include a pulse generator.
- For the reception of UWB signals, such electronics may include timing circuitry and filters.
- FIG. 10 illustrates an exemplary packet type table 1000 which includes data identifying various kinds of link and packet types supported by a wireless communications device, such as a device employing the architecture of FIG. 9 .
- HR high rate
- FIG. 11 illustrates an exemplary packet type table request (LMP_packet_type_table_req) PDU 1102 .
- this PDU may include a member address (AM_ADDR) parameter and a packet type table parameter.
- AM_ADDR member address
- FIG. 12 is a diagram showing details of the packet type table parameter. As shown in FIG. 12 , this parameter includes an indicator 1202 , which specifies a column number of Table 1000 (i.e., a ptt value). As described above with reference to FIG. 10 , columns 2 and 3 correspond to HR communications and UWB communications, respectively. An exemplary range of potential values for indicator 1202 is 0 through 255.
- a packet type table response PDU (LMP_packet_type_table_res) includes information similar to the information conveyed in the LMP_packet_type_table_req PDU.
- a master device sends a packet type table request (LMP_packet_type_table_req) to a slave device.
- the master device receives packet type table response (LMP_packet_type_table_res) from the slave device.
- UWB/HR radio transmissions may be scheduled as Bluetooth transmissions in a time division manner that employs the timing of the Bluetooth slot structure. This may be performed by utilizing a current medium rate packet structure and transmitting higher data rate signals in the payload part of the packet.
- FIG. 13 is a diagram of a medium rate packet structure. This structure includes an access code 1302 , a packet header 1304 , a guard time and synchronization sequence 1306 , a payload 1308 , and a trailer 1310 .
- guard time and synchronization sequence 1306 The main difference in the packet structure of FIG. 13 from the basic rate packet structure is the addition of guard time and synchronization sequence 1306 following packet header 1304 .
- This guard time allows for settling and switching in the hardware during the transition from one modulation scheme to the other for payload 1308 .
- the payload With a DPSK modulated signal, the payload is followed with two trailer symbols.
- access code 1302 and header 1304 is sent by basic rate Bluetooth radio. However, during payload 1308 , the modulation or completely different radio is switched on. While, this radio is using Bluetooth slot timing, characteristics such as the used frequency band, modulation type, and UWB transmission are freely chosen for payload 1308 .
Abstract
Description
- The present invention relates to wireless communications. More particularly, the present invention relates to techniques for initiating wireless communications links.
- Since gaining approval by the Federal Communications Commission (FCC) in 2002, ultra wideband (UWB) techniques have become an attractive solution for short-range wireless communications because they allow for devices to exchange information at relatively high data rates.
- Although UWB systems for short-range networks are relatively new, their transmission techniques have been known for decades. In fact, the first radio transmission was made by a UWB technique when Heinrich Hertz discovered radio waves in 1887. This discovery was made with a spark gap transmitter, which can be viewed as an early UWB radio. Later on, such transmitters were banned because they emitted wide spectrum transmissions.
- Current FCC regulations permit UWB transmissions for communications purposes in the frequency band between 3.1 and 10.6 GHz. However, for such transmissions, the spectral density has to be under −41.3 dBm/MHz and the utilized bandwidth has to be higher than 500 MHz.
- There are many UWB transmission techniques that can fulfill these requirements. A common and practical UWB technique is called impulse radio (IR). In IR, data is transmitted by employing short baseband pulses that are separated in time by gaps. Thus, IR does not use a carrier signal. These gaps makes IR much more immune to multipath propagation problems than conventional continuous wave radios. RF gating is a particular type of IR in which the impulse is a gated RF pulse. This gated pulse is a sine wave masked in the time domain with a certain pulse shape.
- IR transmission facilitates a relatively simple transmitter design, which basically requires a pulse generator and an antenna. This design does not necessarily require a power amplifier, because transmission power requirements are low. In addition, this design does not generally require modulation components such as voltage controlled oscillators (VCOs) and mixers, because the impulses are baseband signals.
- In general, IR receiver designs are more complex than their corresponding transmitter designs. However, these designs are much simpler than conventional receiver designs because they typically do not employ intermediate frequency (IF) signals or filters. However, to fulfill spectral requirements, IR impulses have to be very short in duration (e.g., a couple of nanoseconds). This requirement places stringent timing demands on receiver timing accuracy. The fulfillment of these demands can also provide IR receivers with accurate time resolution and positioning capabilities.
- Existing FCC regulations require that a UWB capable device may only transmit UWB signals when it is associated with a receiver. Strictly interpreted, these regulations prohibit devices from sending UWB transmissions for the purpose of setting up a UWB connection. Thus, devices must use alternate transmission techniques to exchange information and parameters necessary to establish a UWB link. However, there is currently no presented solution as to how a UWB connection should be established.
- Other short-range networks exist but do not provide the high data rates offered by UWB. One such network is Bluetooth. Bluetooth defines a short-range radio network, originally intended as a cable replacement. It can be used to create ad hoc networks of up to eight devices, where one device is referred to as a master device. The other devices are referred to as slave devices. The slave devices can communicate with the master device and with each other via the master device. The Bluetooth Special Interest Group, Specification Of The Bluetooth System,
Volumes - The present invention is directed to a method and system for establishing a wireless communications link. The method and system determine, through a first short-range communications link of a first type, whether a remote device is capable of supporting a short-range communications link of a second type. The method and system also exchange information with the remote device across the first communications link to establish a second short-range communications link of the second type. Once established, communications with the remote device across the second short-range communications link may commence.
- Exchanging information with the remote device across the first communications link to establish the second communications link may include sending a request to the remote device across the first communications link. This request inquires whether the remote device desires to establish the second communications link. If the remote device so desires, an acknowledgement is received through the first communications link. When the first communications link is a Bluetooth link and the second communications link is a UWB link, this request may include a Bluetooth link manager protocol (LMP) message to the remote device.
- In addition to the above features, the method and system may direct the remote device to start communicating across the second short-range wireless communications link. In cases where the first short-range communications link is a Bluetooth link and the second short-range communications link is a UWB link, this may include sending a Bluetooth LMP message to the remote device. This LMP message is adapted to direct the remote device to begin accepting transmissions across the UWB link and may include one or more UWB parameters.
- The method and system may also establish the first short-range communications link with the remote device. When the first link is a Bluetooth link, this may include performing a Bluetooth paging process with the remote device.
- The present invention is also directed to a wireless communications device. This device includes a first segment that exchanges information with a remote device across a first short-range wireless communications link of a first type. In addition, the device includes a host that is coupled to the first segment. The host sets up a second short-range wireless communications link of a second type by causing the first segment to exchange information with the remote device across the first communications link. This information includes one or more parameters of the second short-range communications link. In addition, the device includes a second segment adapted to exchange information with the remote device across the second communications link.
- As with the method and system of the present invention, the first communications link may be a Bluetooth link and the second communications link may be a UWB link. Accordingly, the first segment of the device may include a link manager that exchanges one or more Bluetooth LMP messages with the remote device. These messages may include a message to direct the remote device to begin accepting transmissions across the UWB link, a message to inquire whether the remote device desires to establish the UWB link, and/or a message to determine whether the remote device is capable of supporting the UWB link. These messages may each include one or more UWB parameters.
- The present invention advantageously allows a UWB link to be established without transmitting UWB signals. Thus, Bluetooth may be used to establish UWB links. Since Bluetooth is viewed as a technology that will be soon be implemented in most phones and consumer electronic devices, devices having UWB capabilites will also be Bluetooth equipped. Accordingly, the present invention advantageously provides for the integration of Bluetooth and UWB capabilities
- A computer-readable medium may be encoded with processing instructions for implementing the various method and functions herein, such as establishing a wireless communications link, to be performed by a computerized system which can be embodied in wireless communications device.
- Further features and advantages of the present invention will become apparent from the following description.
- In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the reference number. The present invention will be described with reference to the accompanying drawings, wherein:
-
FIG. 1 is a diagram of an exemplary operational environment; -
FIG. 2 is a block diagram of an exemplary communications device architecture in accordance with one embodiment; -
FIG. 3 is a block diagram of an exemplary communications device implementation; -
FIG. 4 is a flowchart of an exemplary link establishment process; -
FIG. 5 is a flowchart of a second communications link initiation; -
FIGS. 6-8 are diagrams of interactions between two devices according to the present invention; -
FIG. 9 is an exemplary communications device architecture in accordance with a further embodiment; -
FIG. 10 is an exemplary packet type table; -
FIG. 11 is an exemplary packet type table request parameters and packet type table parameters; -
FIG. 12 is a diagram showing details of a packet type table parameter; and -
FIG. 13 is a diagram of a packet structure. - I. Operational Environment
- Before describing the invention in detail, it is helpful to describe an environment in which the invention may be used. Accordingly,
FIG. 1 is a diagram of an operational environment which includeswireless communications devices -
Devices devices -
Devices FIG. 1 , acoverage area 103 defines the communications range ofdevice 102, while acoverage area 105 defines the communications range ofdevice 104. These coverage areas illustrate a range in which the corresponding device can communicate across two different link types (e.g., both Bluetooth and UWB). - In the environment of
FIG. 1 devices devices first link 110 may be a Bluetooth link, whilesecond link 112 may be a UWB link. - According to the present invention,
first device 102 may communicate acrossfirst link 110 to establishsecond link 112, and to initiate communications acrosslink 112. - II. Wireless Communications Device
-
FIG. 2 is a block diagram showing a wireless communications device architecture, which may be used fordevices - The device architecture of
FIG. 2 includes ahost 202, which is coupled to aBluetooth segment 204, and aUWB segment 206.Host 202 is responsible for functions involving user applications and higher protocol layers, whileBluetooth segment 204 andUWB segment 206 are responsible for lower layer protocols. More particularly,Bluetooth segment 204 is responsible for Bluetooth specific communications with other devices, andUWB segment 206 is responsible for UWB specific communications with other devices. - As shown in
FIG. 2 ,Bluetooth segment 204 includes a host controller interface (HCI) 208, alink manager 210, alink controller 212, aBluetooth transceiver 214, and anantenna 216. -
Link manager 210 performs functions related to Bluetooth link set-up, security and control. These functions involve discovering corresponding link managers at remote devices and communicating with them according to a link manager protocol (LMP). To perform these functions, LMP defines a set of messages, which are also referred to as protocol data units (PDUs).Link manager 210 exchanges these PDUs with link managers at remote devices. Various LMP PDUs for performing the techniques of the present invention are described below with reference toFIG. 6 . -
Link manager 210 exchanges information withhost 202 acrossHCI 208. This information may include commands received fromhost 202, and information transmitted to host 202.HCI 208 defines a set of messages, which provide for this exchange of information. Various HCI messages for performing the techniques of the present invention are described below with reference toFIG. 6 . -
Link controller 212 operates as an intermediary betweenlink manager 210 andBluetooth transceiver 214.Link controller 212 also performs baseband processing for Bluetooth transmission, such as error correction encoding and decoding. In addition,link controller 212 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of such physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol. -
FIG. 2 shows thatBluetooth transceiver 214 is coupled to anantenna 216.Transceiver 214 includes electronics that allow the device ofFIG. 2 (in conjunction with antenna 216) to exchange wireless Bluetooth signals with devices, such asremote device 104. Such electronics include modulators and demodulators, amplifiers, and filters. - When the device of
FIG. 2 engages in UWB communications, it employs the services ofUWB segment 206. As shown inFIG. 2 ,UWB segment 206 includes aUWB module 218, aUWB transceiver 220, and anantenna 222. -
UWB module 218 provides for the exchange of information across UWB links according to one or more protocol layers. For example, UWB module may provide session management functionality to manage various UWB sessions. In addition,UWB module 218 may perform baseband processing, such as error correction encoding and decoding. In addition,UWB module 218 perform various link level protocols with remote devices according to physical layer protocols. Examples of such protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol. -
UWB transceiver 220 is coupled toantenna 222.UWB transceiver 220 includes electronics, which allow the device ofFIG. 2 (in conjunction with antenna 222) to exchange wireless UWB signals with devices, such asremote device 104. For the transmission of UWB signals, such electronics may include a pulse generator. For the reception of UWB signals, such electronics may include timing circuitry and filters. - The architecture of
FIG. 2 may be implemented in hardware, software, firmware, or any combination thereof. One such implementation is shown inFIG. 3 . This implementation includes aprocessor 310, amemory 312, and auser interface 314. In addition, the implementation ofFIG. 3 includesBluetooth transceiver 214,antenna 216,UWB transceiver 220, andantenna 222.Transceivers FIG. 2 . - As shown in
FIG. 3 ,processor 310 is coupled totransceivers Processor 310 controls device operation.Processor 310 may be implemented with one or more microprocessors that are each capable of executing software instructions stored inmemory 312. -
Memory 312 includes random access memory (RAM), read only memory (ROM), and/or flash memory, and stores information in the form of data and software components (also referred to herein as modules). These software components include instructions that can be executed byprocessor 310. Various types of software components may be stored inmemory 312. For instance,memory 312 may store software components that control the operations oftransceivers memory 312 may store software components that provide for the functionality ofhost 202,HCI interface 208,link manager 210,link controller 212, andUWB module 218. - In addition,
memory 312 may store software components that control the exchange of information throughuser interface 314. As shown inFIG. 3 ,user interface 314 is also coupled toprocessor 310.User interface 314 facilitates the exchange of information with a user.FIG. 3 shows thatuser interface 314 includes auser input portion 316 and auser output portion 318.User input portion 316 may include one or more devices that allow a user to input information. Examples of such devices include keypads, touch screens, and microphones.User output portion 318 allows a user to receive information fromWCD 102. Thus,user output portion 318 may include various devices, such as a display, and one or more audio speakers. Exemplary displays include liquid crystal displays (LCDs), and video displays. - The elements shown in
FIG. 3 may be coupled according to various techniques. One such technique involvescoupling transceivers processor 310,memory 312, anduser interface 314 through one or more bus interfaces. In addition, each of these components is coupled to a power source, such as a removable and rechargeable battery pack (not shown). - III. Link Establishment
-
FIG. 4 is a flowchart of a link establishment process according to the present invention. In this process, an initiating device (such as device 102) uses a first communications link with a remote device (such as device 104) to establish a second communications link with the remote device. These communications links may be of different types. For example, the first communications link may be a Bluetooth link, while the second communications link may be a UWB link. - This process begins with a
step 402, in which the initiating device and the remote device enter into short-range communications proximity. Next, in astep 404, the initiating device learns the identity (or discovers the existence) of the remote device. This step may comprise the initiating device and the remote device engaging in an inquiry process. In Bluetooth implementations, the initiating device operates in an inquiry state while the remote device operates in an inquiry scan state. When operating in the inquiry state, the initiating device transmits an inquiry packet and the remote device listens for inquiry packets. - When the remote device receives the inquiry packet from the initiating device, it transmits one or more frequency hop synchronization (FHS) packets, which are received by the initiating device. The FHS packet(s) allow the initiating device to become synchronized with the hop sequence of the remote device. In addition, the FHS packet(s) enable the initiating device to derive information necessary to make a Bluetooth connection with the remote device. This information includes the native clock of the remote device (CLKN), the Bluetooth address (BD_ADDR) of the remote device, and error correction coding information.
- In a
step 406, the initiating device and the remote device join an ad hoc network to form the first communications link. Accordingly, when the first communications link is a Bluetooth link, this step may comprise the initiating device and the remote device performing a paging process. Upon successful completion, the paging process results in an unsecured connection being established between these devices. Bluetooth paging involves the exchange of various information between the initiating device (which is in a paging state) and remote device (which is in a page scan state). - More particularly, the initiating device enters the paging state and transmits one or more paging packets. Each of these paging packets includes an identification number based on the address of the remote device. Meanwhile, the remote device (which is in the page scan state) responds to the paging packets by transmitting a packet containing its address.
- The initiating device receives this packet from the remote device. In response, the initiating device transmits a frequency hop synchronization (FHS) packet. The FHS packet is used to pass information that allows the remote device to synchronize with the frequency hopping sequence of the initiating device. Upon receipt of this FHS packet, the remote device transmits a further packet to confirm receipt of the FHS packet.
- At this point, a Bluetooth link is formed between the initiating device and the remote device. Accordingly, both devices enter into a connection state. In the connection state, the initiating device operates as a master device and the remote device operates as a slave device. Thus, the remote device employs the timing and frequency hopping sequence of the initiating device. Additionally, the initiating device transmits a packet to verify that a link has been set up. The remote device confirms this link by sending a packet to the initiating device.
- In a
step 408, the initiating device determines the communications capabilities of the remote device. This step may comprise these devices exchanging one or more messages, such as a request for the capabilities of the remote device and a response containing these capabilities. These capabilities may be communicated in the form of link type identifiers and their associated transmission formats (e.g., UWB radio standard and version). - In a
step 410, the initiating device determines whether the remote device is capable of forming the second link. For example, this step may comprise the initiating device determining whether the remote device has UWB communications capabilities. If so, then operation proceeds to astep 412. Instep 412, the initiating device initiates a second link establishment process. An exemplary operation of this step is described below with reference toFIG. 5 . - As indicated by a
step 414, if this link establishment process is successful, then the initiating device may direct the remote device to start communicating across the second link in astep 416. - A
step 420 followsstep 416. In this step, the initiating device and the remote device may engage in communications across the second link -
FIG. 5 is a flowchart illustrating a performance ofstep 412 in greater detail. This performance begins with astep 502. In this step, the initiating device sends a request to the remote device over the first communications link. This request asks the remote device whether it desires to establish the second link. In addition, this request contains parameters for the second link. These parameters may include, for example, transmission format (e.g., UWB radio standard and version), and traffic classes. - When the first link is a Bluetooth link, this request may include an LMP message, such as the LMP_host_connection_request_ext PDU, which is described below in greater detail.
- In a
step 504, the initiating device receives an acknowledgement transmitted by the remote device. This acknowledgement is transmitted across the first link and indicates that the remote device desires to establish the second communications link. When the first link is a Bluetooth link, this acknowledgement may be in the form of an LMP message, such as a LMP_setup_complete message. At this point, the second communications link is set up (or configured). - IV. Bluetooth Messages
- As described above, embodiments of the present invention may employ Bluetooth communications to initiate UWB communications. However, current Bluetooth standards do not provide a mechanism for establishing UWB connections. Therefore, the present invention provides for additional and modified Bluetooth messages that may be employed in establishing UWB communications. These messages include LMP PDUs and HCI commands. An exemplary set of such messages are provided below in Table 1. A description of these messages follows this table.
TABLE 1 LMP messages HCI messages LMP_features_req_ext HCI_create_connection_req (modified message) (modified message) LMP_features_res_ext HCI_connection_request_event (modified message) (modified message) LMP_host_connection_request HCI_connection_complete_event (modified message) (modified message) LMP_switch_to UWB_link_req (new message) - Table 1 provides a listing of an exemplary set of modified or new LMP messages according to an embodiment of the present invention. As indicated by this table, LMP_features_req_ext and LMP_features_res_ext are modified messages of the present invention. These messages are based on the standard Bluetooth PDUs LMP_features_req and LMP_features_res.
- These standard Bluetooth PDUs are exchanged to determine the features supported by a particular device. In particular, a first device transmits a LMP_features_req PDU to a second device. This PDU may be transmitted at any time after the two devices have completed a paging process. In response to the LMP_features_req PDU, the second device transmits a LMP_features_res PDU, which conveys the features that it supports.
- LMP_features_req and LMP_features_res each includes a features parameter, which conveys the features supported by the transmitting device in a bitmap. This bitmap includes multiple bits, each bit corresponding to a particular radio, baseband, or LMP feature. According to the present invention, the features parameter of the LMP_features_req_ext and LMP_features_res_ext PDUs, has an extended bitmap. This extended bitmap, includes a UWB capable bit as well as UWB information bits, which convey associated information, such as particular UWB operational parameters that are supported. Examples of such operational parameters include transmission format (e.g., UWB radio standard and version) and traffic classes.
- As indicated by Table 1, the present invention provides for a new LMP_switch_to_UWB_link_req PDU. This PDU is a directive that first UWB capable device may transmit to a second UWB capable device to direct the second device to commence accepting transmissions across a UWB link. This message may include parameters of the UWB link so that a receiving device may configure itself to receive and/or send UWB transmissions. Examples of such parameters include transmission format (e.g., UWB radio standard and version) and traffic classes.
- Upon receipt of this message, the second UWB capable device sends the first device a Bluetooth LMP_accepted PDU so that the first device may initiate UWB communications.
- The present invention also provides for a LMP_host_connection_req_ext message. LMP_host_connection_req is a standard Bluetooth LMP PDU. This PDU indicates that a device wishes to create a connection with another device involving protocol layers above the link manager layer. According to the present invention, LMP_host_connection_req_ext is an extension of LMP_host_connection_req. This extension provides parameter values and/or parameters to indicate that a device wishes to establish a UWB link with another device. For instance, such parameter values and/or parameters may convey information such as transmission format (e.g., UWB radio standard and version) and traffic classes.
- Table 1 also provides a listing of HCI commands according to an embodiment of the present invention. As indicated by this table, the present invention provides for a modified HCI_create_connection_req command. The standard Bluetooth HCI command instructs the link manager of a local Bluetooth device to create a connection with a remote Bluetooth device. In particular, this command instructs the link manager of the local Bluetooth device to initiate a paging process with the remote device. This command includes the following parameters: BD_ADDR, Packet_Type, Page_Scan_Repetition_Mode, Page_Scan_Mode, Clock_Offset, and Allow_Role_Switch. These parameters are described below.
- The BD_ADDR parameter specifies the Bluetooth device address (BD_ADDR) of the remote device. The Packet_Type parameter specifies which packet types the link manager shall use for the connection. The Page_Scan_Repetition_Mode and Page_Scan_Mode parameters indicate page scan modes supported by the remote device. The Clock_Offset parameter indicates a difference between the local device's clock and the clock of the remote device with BD_ADDR. The Allow_Role_Switch parameter indicates whether the local device accepts or rejects the request of a master-slave role switch.
- According to the present invention, a modified HCI_create_connection_req command provides for a UWB value for the Packet_Type parameter. Thus, this modified HCI command instructs a link manager at a local device to pursue a UWB connection with a remote device specified by the BD_ADDR parameter.
- The present invention also provides for a modified HCI_connection_request_event command. At a remote device, this command is passed from the link manager to the host. The standard Bluetooth HCI_connection_request_event command includes a BD_ADDR parameter, a Class-of_Device parameter, and a Link_Type parameter. These parameters specify information regarding a device which is trying to establish a connection through a HCI_create_connection_req command.
- A modified HCI_connection_request_event command of the present invention provides for values which convey UWB information to be included in the Class-of_Device and Link_Type parameters. In further embodiments, additional modifications to this command may exist, such as the creation of other parameters.
- At both the local and remote devices, the HCI_connection_complete_event message provides an indication to the hosts that a new connection has been established. The standard Bluetooth HCI_connection_complete_event message includes a Status parameter, a Connection_Handle parameter, a BD_ADDR parameter, a Link_Type parameter, and an Encryption_Mode parameter. In an embodiment of the present invention, the Link_Type parameter is modified to include a value to indicate that a UWB link has been completed.
- V. Device Interactions
-
FIG. 6 illustrates an interaction between Bluetooth and UWB capable devices involving the messages of Table 1. This diagram is described with reference to the operational environment ofFIG. 1 . However, this interaction may be performed in other environments. - As shown in
FIG. 6 , initiatingdevice 102 includes ahost 202 a, alink manager 210 a, anHCI 208 a, and aUWB segment 206 a. Similarly,remote device 104 includes ahost 202 b, alink manager 210 b, anHCI 208 b, and aUWB segment 206 b. Although not shown,devices link controller 212 to handle baseband processing and information exchange as described above with reference toFIG. 2 . - The interaction of
FIG. 6 includes a series of events that occur in a chronological sequence according to atime axis 601. This interaction begins with aninquiry process 602. In this process, initiatingdevice 102 learns the identity ofremote device 104. - Next,
terminal host 202 a sendsmessage 603 to linkmanager 210 a. As shown inFIG. 6 ,message 603 is a HCI_create_connection_req, which is modified as described above. In addition,message 603 includes the BD_ADDR ofremote device 104. Thus, this message instructslink manager 210 a to pursue a UWB connection withremote device 104. - In response to this request,
link manager 210 a initiates apaging process 604 withremote device 104. This paging process results in a link manager protocol (LMP)connection 606 being established betweenlink managers LMP connection 606 is established,link manager 210 a transmits LMP_features_req_extmessage 608 to linkmanager 210 b. As described above, this message inquires about the features supported byremote device 104. In response,link manager 210 b sendsLMP_features res_ext message 610 to linkmanager 210 b.Message 610 conveys the features supported byremote device 104. - If
message 610 indicates thatremote device 104 supports acceptable UWB capabilities, then linkmanager 210 a sendsLMP_host_connection_req_ext message 612 to link manager. As described above, this message is an extended Bluetooth message indicating that initiatingdevice 102 wishes to create a UWB connection withremote device 104. - Upon receipt of
message 612,link manager 210 b sends amessage 614 toterminal host 202 b acrossHCI 208 b.Message 614 is an HCI_connection_request_event message, which is modified in the manner described above. Thus,message 614 includes parameter values which convey UWB information. - After
message 614 is received,terminal host 202 b may agree to establish a UWB connection with initiatingdevice 102. If so, thenterminal host 202 b sends amessage 616 to linkmanager 210 b acrossHCI 208 b. As shown inFIG. 6 ,message 616 is a standard Bluetooth HCI_accept_connection_request message. - As a result of
message 616,devices event 618. Examples of such additional Bluetooth processes include a master/slave switch and an authentication process. A master/slave switch is a process in which the master and slave roles ofdevices - Following these additional Bluetooth processes,
FIG. 6 shows that linkmanagers Bluetooth LMP_setup_complete messages devices - Next, at initiating
device 102,link manager 210 a sends amessage 624 to host 202 a acrossHCI 208 a. Also, atremote device 104,link manager 210 b sends amessage 626 to host 202 b acrossHCI 208 b.Messages FIG. 6 , these messages are modified as described above such that the Link_Type parameter includes a value indicating that a UWB link has been completed. - Following
messages link manager 210 a sends to linkmanager 210 bLMP_switch_to_UWB_link_req message 628. As described above, this message is a new message that requestsremote device 104 to commence communications across the established UWB link. If theremote device 104 accepts this request, it sends initiatingdevice 102LMP_accepted message 630. - As shown in
FIG. 6 , afterlink manager 210 a receivesLMP_accepted message 630,devices interaction 632. - Although not shown, the interaction of
FIG. 6 may include additional messages. For example, following the receipt ofmessage 628,link manager 210 b ofremote device 104 may send one or more HCI messages to host 202 b. These messages indicate to host 202 b that UWB transmissions are forthcoming. Upon receipt of such messages, host 202 b may send one or more messages toUWB segment 206 b directing it to prepare for the reception of UWB transmissions. - Also, following receipt of
message 630,link manager 210 a of initiatingdevice 102 may send one or more HCI messages to host 202 a. These messages indicate to host 202 b that UWB transmissions may commence. In response to such messages, host 202 a may send one or more messages toUWB segment 206 a, which causes it to initiate UWB transmissions. - VI. Further Interactions
-
FIG. 7 is a diagram illustrating a further interaction between devices in which a Bluetooth link is used to establish a UWB link. This interaction is similar to the interaction ofFIG. 6 . However, this interaction additionally includeshost 202 a sending to linkmanager 210 a anHCI_QoS_setup message 702. This message is a standard Bluetooth message which specifies quality of service parameters, such as peak bandwidth, for a particular connection. - At the time in which
message 702 is transmitted, the UWB link has been assigned a connection handle. Specific QoS requirements, like peak bandwidth is mapped to this connection handle.Message 702 assigns a large peak bandwidth to this connection handle. This signifies that a switch to UWB communications is desired. Accordingly, in response to receivingmessage 702,link manager 210 a sendsmessage 628. As described above, this message requestsremote device 104 to commence communications across the established UWB link. -
FIG. 8 shows yet a further interaction between devices according to the present invention. This interaction is also similar to the interaction ofFIG. 6 . However, in this interaction,messages messages additional message 810. -
Message 802 is a standard Bluetooth LMP_host_connection_req message, which indicates that initiatingdevice 102 wishes to create a Bluetooth connection withremote device 104.Message 804 is a standard Bluetooth HCI_connection_request_event command, which specifies information regarding initiatingdevice 104.Messages - Accordingly, the interaction of
FIG. 8 in large part begins with normal Bluetooth connection establishment processes. However, followingmessage message 810 initiates the setup of a UWB link.Message 810 is a modified HCI_Change_Connection_Packet_Type command. This modified command includes values for its packet type parameter that designates a UWB link (as well as its corresponding parameters). Accordingly, in response to receivingmessage 810,link manager 210 atransmits message 628 toremote device 104 to commence communications across a UWB link. - VII. Further Architectural and Implementation Features
- In accordance with aspects of the present invention, UWB or other High Bit Rate (High Rate or HR) wireless transmissions may be handled as a part of a Bluetooth piconet, employing wireless device architectures such as the architecture described below with reference to
FIG. 9 . In this example, UWB/HR radio transmissions may be scheduled as Bluetooth transmissions in a time division manner that employs the timing of the Bluetooth slot structure. The UWB/HR link may be established in a link level by employing a framework presented in release after Bluetooth Version 1.2. - Specifically, as part of a medium rate data extension, release after Bluetooth Version 1.2 provides for the exchange of packet type requests and responses, which communicate link and packet type capabilities of a device. Different modulation and radio implementations can be provided by existing LMP packet type request and response commands (i.e., LMP_packet_typereq and LMP_packet_type_res), involving addresses (e.g., logical transport address or LT_ADDR) and packet type table (ptt) entries chosen according to desired modulation/radio characteristics.
- Specifically, the logical transport address may be selected according to the Bluetooth Address (BD_ADDR) and the packet type table may be extended to include HR data and UWB data along with basic rate data and medium rate data. Accordingly, UWB and other higher rate links may be established by employing mechanisms provided by release after Bluetooth Version 1.2 while retaining backwards compatibility and reducing complexity in the development of media access control (MAC) to support the additional links.
-
FIG. 9 is a block diagram showing a wireless communications device architecture, which may be used fordevices FIGS. 11 and 12 . Although this architecture is described in the context of Bluetooth and UWB communications, it may be employed with other wireless communications technologies. - The device architecture of
FIG. 9 includes ahost 202, which is coupled to asegment 900.Host 202 is responsible for functions involving user applications and higher protocol layers, whilesegment 900 is responsible for lower layer protocols, such as Bluetooth (e.g., basic rate, medium rate or higher rate), UWB, and/or other specific communications. - As shown in
FIG. 9 ,segment 900 includes a host controller interface (HCI) 902, alink manager 904, a Bluetooth (BT)link controller 906, a Bluetooth (BT)transceiver 908, anantenna 910, aUWB link controller 912, a UWB/HR transceiver 914, and anantenna 916. -
Link manager 904 performs functions related to Bluetooth link and UWB link set-up, security and control. These functions involve discovering corresponding link managers at remote devices and communicating with them according to the link manager protocol (LMP). More particularly,link manager 904 exchanges LMP PDUs with link managers at remote devices. LMP PDUs for performing the techniques of the present invention are described herein with reference toFIGS. 6, 11 , and 12. -
Link manager 904 exchanges information withhost 202 acrossHCI 902. This information may include commands received fromhost 202, and information transmitted to host 202.HCI 902 defines a set of messages, which provide for this exchange of information. -
BT link controller 906 operates as an intermediary betweenlink manager 904 andBT transceiver 908.Link controller 906 also performs baseband processing for Bluetooth transmissions, such as error correction encoding and decoding. In addition,link controller 906 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol. -
BT transceiver 908 is coupled toantenna 910.Transceiver 908 includes electronics to (in conjunction with antenna 910) exchange wireless Bluetooth signals with devices, such asremote device 104. Such electronics include modulators, demodulators, amplifiers, and filters. -
UWB link controller 912 operates as an intermediary betweenlink manager 904 and UWB/HR transceiver 914.Link controller 912 also performs baseband processing for UWB transmission, such as error correction encoding and decoding. In addition,link controller 912 exchanges data between corresponding link controllers at remote devices according to physical layer protocols. Examples of such physical layer protocols include retransmission protocols such as the automatic repeat request (ARQ) protocol. - UWB/
HR transceiver 914 is coupled to anantenna 916.Transceiver 914 includes electronics to (in conjunction with antenna 916) exchange wireless UWB or HR signals with devices, such asremote device 104. For the transmission of UWB signals, such electronics may include a pulse generator. For the reception of UWB signals, such electronics may include timing circuitry and filters. -
FIG. 10 illustrates an exemplary packet type table 1000 which includes data identifying various kinds of link and packet types supported by a wireless communications device, such as a device employing the architecture ofFIG. 9 . Packet type table 1000 includes data for basic rate and medium rate Bluetooth (e.g., ptt=1) communications as shown byreference number 1002. Packet type table 1000 is further modified to includedata 1004 for high rate (HR) communications (e.g., ptt=2) and UWB communications (e.g., ptt=3). -
FIG. 11 illustrates an exemplary packet type table request (LMP_packet_type_table_req)PDU 1102. As shown inFIG. 11 , this PDU may include a member address (AM_ADDR) parameter and a packet type table parameter. -
FIG. 12 is a diagram showing details of the packet type table parameter. As shown inFIG. 12 , this parameter includes anindicator 1202, which specifies a column number of Table 1000 (i.e., a ptt value). As described above with reference toFIG. 10 ,columns indicator 1202 is 0 through 255. - Although not shown, a packet type table response PDU (LMP_packet_type_table_res) includes information similar to the information conveyed in the LMP_packet_type_table_req PDU.
- An exemplary implementation will be described with reference to this additional packet table type embodiment with reference to
FIGS. 10 and 11 . In this implementation, general processes in establishing a Bluetooth link may be employed. However, a master device sends a packet type table request (LMP_packet_type_table_req) to a slave device. This request includes a packet type table value (e.g., ptt=3). In response, the master device receives packet type table response (LMP_packet_type_table_res) from the slave device. This response includes a packet type table value (e.g., ptt=3). - With this exchange of PDUs, the master device verifies that the slave device is UWB capable (e.g., ptt=3) and requests UWB link establishment (e.g. ptt=3). If the slave device accepts the proposed ptt, then the slave device sends to the master device an acceptance PDU (LMP_accepted). Thereafter, a UWB link is establish between the master and slave device. For example, the device with the active member address (AM_ADDR) or logical transport address (LT_ADDR) employs link according to the parameters in the column ptt=3, such as shown in
FIG. 10 . - As described above, UWB/HR radio transmissions may be scheduled as Bluetooth transmissions in a time division manner that employs the timing of the Bluetooth slot structure. This may be performed by utilizing a current medium rate packet structure and transmitting higher data rate signals in the payload part of the packet.
FIG. 13 is a diagram of a medium rate packet structure. This structure includes anaccess code 1302, apacket header 1304, a guard time andsynchronization sequence 1306, apayload 1308, and atrailer 1310. - The main difference in the packet structure of
FIG. 13 from the basic rate packet structure is the addition of guard time andsynchronization sequence 1306 followingpacket header 1304. This guard time allows for settling and switching in the hardware during the transition from one modulation scheme to the other forpayload 1308. With a DPSK modulated signal, the payload is followed with two trailer symbols. In every packet,access code 1302 andheader 1304 is sent by basic rate Bluetooth radio. However, duringpayload 1308, the modulation or completely different radio is switched on. While, this radio is using Bluetooth slot timing, characteristics such as the used frequency band, modulation type, and UWB transmission are freely chosen forpayload 1308. - While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not in limitation. For instance, although examples have been described involving Bluetooth and UWB technologies, other short-range and longer range communications technologies are within the scope of the present invention.
- Accordingly, it will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
Claims (29)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/660,544 US7352998B2 (en) | 2003-09-12 | 2003-09-12 | Method and system for establishing a wireless communications link |
EP04104392.8A EP1515497B1 (en) | 2003-09-12 | 2004-09-10 | Method and system for establishing a wireless communications link |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/660,544 US7352998B2 (en) | 2003-09-12 | 2003-09-12 | Method and system for establishing a wireless communications link |
Publications (2)
Publication Number | Publication Date |
---|---|
US20050059345A1 true US20050059345A1 (en) | 2005-03-17 |
US7352998B2 US7352998B2 (en) | 2008-04-01 |
Family
ID=34136776
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/660,544 Active 2025-06-29 US7352998B2 (en) | 2003-09-12 | 2003-09-12 | Method and system for establishing a wireless communications link |
Country Status (2)
Country | Link |
---|---|
US (1) | US7352998B2 (en) |
EP (1) | EP1515497B1 (en) |
Cited By (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050114714A1 (en) * | 2003-11-25 | 2005-05-26 | Microsoft Corporation | Modifying a power management algorithm based on wireless communication parameters |
US20050246470A1 (en) * | 2004-04-28 | 2005-11-03 | Brenner David G | Wireless docking station |
US20060009159A1 (en) * | 2004-07-09 | 2006-01-12 | Leung Hung F | Protocol layer analysis in mobile device testing |
US20060046736A1 (en) * | 2004-08-31 | 2006-03-02 | Pering Trevor A | Methods and apparatus for managing wireless device power consumption by selecting among plural communication transceivers |
US20060094402A1 (en) * | 2004-11-03 | 2006-05-04 | Samsung Electronics Co., Ltd. | Security monitoring method in bluetooth device |
US20060178161A1 (en) * | 2005-02-04 | 2006-08-10 | Samsung Electronics Co., Ltd. | Method and system for automatically updating user information in a push-to-talk system |
US20060198335A1 (en) * | 2005-03-04 | 2006-09-07 | Jukka Reunamaki | Embedding secondary transmissions in an existing wireless communications network |
US20070197218A1 (en) * | 2006-02-10 | 2007-08-23 | Cambridge Silicon Radio Limited | Channel Acquisition |
US7278084B2 (en) | 2003-10-29 | 2007-10-02 | Nokia Corporation | Method and system for providing communications security |
US20080013658A1 (en) * | 2006-07-17 | 2008-01-17 | Michael Lewis | Synchronizing high data-rate radio transceivers |
US20080118014A1 (en) * | 2006-11-16 | 2008-05-22 | Nokia Corporation | Utilizing wake-up signals for synchronizing multiradio timing |
US20080166967A1 (en) * | 2007-01-05 | 2008-07-10 | Apple Inc. | Power efficient high speed communication systems and methods |
US20090219974A1 (en) * | 2006-01-24 | 2009-09-03 | Cambridge Silicon Radio Limited | Varying device identities |
US20090221320A1 (en) * | 2008-02-28 | 2009-09-03 | John Walley | Method and system for bluetooth transport sharing to carry gps or other types of data |
US20090241147A1 (en) * | 2006-09-05 | 2009-09-24 | Taek Soo Kim | Method of transmitting link-adaptive transmission of data stream in a mobile communication system |
US7697893B2 (en) | 2004-06-18 | 2010-04-13 | Nokia Corporation | Techniques for ad-hoc mesh networking |
US7702284B2 (en) | 2003-09-12 | 2010-04-20 | Arto Palin | Method and system for processing acknowledgments in a wireless communications network |
US7782894B2 (en) | 2003-09-12 | 2010-08-24 | Nokia Corporation | Ultra-wideband/low power communication having a dedicated removable memory module for fast data downloads—apparatus, systems and methods |
US20100274874A1 (en) * | 2009-04-24 | 2010-10-28 | Nokia Corporation | Service discovery protocol enhancement |
US20120069772A1 (en) * | 2010-09-20 | 2012-03-22 | Research In Motion Limited | Communications system providing mobile wireless communications device application module associations for respective wireless communications formats and related methods |
US20130005243A1 (en) * | 2011-06-28 | 2013-01-03 | Broadcom Corporation | Device for Authenticating Wanted NFC Interactions |
US20140065970A1 (en) * | 2005-03-08 | 2014-03-06 | Broadcom Corporation | Mechanism for improved interoperability when content protection is used with an audio stream |
DE102014101526A1 (en) * | 2014-02-07 | 2015-08-13 | Aesculap Ag | Data communication device and method for data communication |
US20150245396A1 (en) * | 2012-09-28 | 2015-08-27 | Telefonaktiebolaget L M Ericsson | Short Range Communication in a Wireless Communications System |
JP2016019181A (en) * | 2014-07-09 | 2016-02-01 | 日本電信電話株式会社 | Radio communication system, radio base station device, radio terminal device and data distribution device |
US20160277878A1 (en) * | 2015-03-16 | 2016-09-22 | Samsung Electronics Co., Ltd. | Method for communicating data and electronic device thereof |
US20160366542A1 (en) * | 2009-10-02 | 2016-12-15 | Blackberry Limited | Methods and devices for facilitating bluetooth pairing using a camera as a barcode scanner |
US20170150532A1 (en) * | 2014-07-09 | 2017-05-25 | Aisin Aw Co., Ltd. | Wireless communication system, information terminal and communication device |
DE112006003342B4 (en) | 2005-12-05 | 2018-07-05 | Lenovo (Beijing) Ltd. | Wireless display system and method therefor |
US10228903B2 (en) | 2013-07-19 | 2019-03-12 | Samsung Electronics Co., Ltd. | Method and device for communication |
WO2019219115A1 (en) * | 2018-05-16 | 2019-11-21 | Bayerische Motoren Werke Aktiengesellschaft | Master-slave system |
US11013062B2 (en) * | 2019-01-31 | 2021-05-18 | Qualcomm Incorporated | Fast role switch between bluetooth true wireless stereo (TWS) earbuds |
CN114095937A (en) * | 2020-07-30 | 2022-02-25 | 株式会社东海理化电机制作所 | Control device, recording medium, and system |
CN115665717A (en) * | 2022-12-27 | 2023-01-31 | 合肥炬芯智能科技有限公司 | Data transmission method, electronic equipment and computer readable storage medium |
Families Citing this family (71)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7477913B2 (en) * | 2005-04-04 | 2009-01-13 | Research In Motion Limited | Determining a target transmit power of a wireless transmission according to security requirements |
US8730031B2 (en) | 2005-04-28 | 2014-05-20 | Proteus Digital Health, Inc. | Communication system using an implantable device |
CA2789262C (en) | 2005-04-28 | 2016-10-04 | Proteus Digital Health, Inc. | Pharma-informatics system |
US8836513B2 (en) | 2006-04-28 | 2014-09-16 | Proteus Digital Health, Inc. | Communication system incorporated in an ingestible product |
US8912908B2 (en) | 2005-04-28 | 2014-12-16 | Proteus Digital Health, Inc. | Communication system with remote activation |
US9198608B2 (en) | 2005-04-28 | 2015-12-01 | Proteus Digital Health, Inc. | Communication system incorporated in a container |
US8802183B2 (en) | 2005-04-28 | 2014-08-12 | Proteus Digital Health, Inc. | Communication system with enhanced partial power source and method of manufacturing same |
WO2007028035A2 (en) | 2005-09-01 | 2007-03-08 | Proteus Biomedical, Inc. | Implantable zero-wire communications system |
KR101568660B1 (en) | 2006-05-02 | 2015-11-12 | 프로테우스 디지털 헬스, 인코포레이티드 | Patient customized therapeutic regimens |
EP2080387B1 (en) * | 2006-10-17 | 2019-12-18 | D&M Holdings, Inc. | Configuring and connecting to a media wireless network |
US8054140B2 (en) | 2006-10-17 | 2011-11-08 | Proteus Biomedical, Inc. | Low voltage oscillator for medical devices |
MY158019A (en) | 2006-10-25 | 2016-08-30 | Proteus Digital Health Inc | Controlled activation ingestible identifier |
US8718193B2 (en) | 2006-11-20 | 2014-05-06 | Proteus Digital Health, Inc. | Active signal processing personal health signal receivers |
JP5524626B2 (en) | 2007-02-01 | 2014-06-18 | プロテウス デジタル ヘルス, インコーポレイテッド | Ingestible event marker system |
CN103066226B (en) | 2007-02-14 | 2016-09-14 | 普罗透斯数字保健公司 | There is the in-body power source of high surface area electrode |
US9270025B2 (en) | 2007-03-09 | 2016-02-23 | Proteus Digital Health, Inc. | In-body device having deployable antenna |
US8932221B2 (en) | 2007-03-09 | 2015-01-13 | Proteus Digital Health, Inc. | In-body device having a multi-directional transmitter |
JP2008271151A (en) | 2007-04-19 | 2008-11-06 | Sony Corp | Radio communication system, radio communication apparatus, program, and radio communication method |
US8115618B2 (en) | 2007-05-24 | 2012-02-14 | Proteus Biomedical, Inc. | RFID antenna for in-body device |
US9417934B2 (en) * | 2007-08-31 | 2016-08-16 | Core Wireless Licensing S.A.R.L. | Information distribution in a dynamic multi-device environment |
FI2192946T3 (en) | 2007-09-25 | 2022-11-30 | In-body device with virtual dipole signal amplification | |
US8493888B2 (en) * | 2007-11-08 | 2013-07-23 | Nokia Corporation | Connectivity architecture for service discovery |
US20090141692A1 (en) * | 2007-11-30 | 2009-06-04 | Mika Kasslin | Optimized ad hoc networking |
US9825863B2 (en) * | 2008-02-27 | 2017-11-21 | Nokia Technologies Oy | Buffer control for multi-transport architectures |
ATE541397T1 (en) * | 2008-02-27 | 2012-01-15 | Nokia Corp | TRANSPORT INDEPENDENT ARCHITECTURE |
CN104376659B (en) | 2008-03-05 | 2019-10-25 | 普罗透斯数字保健公司 | The ingestible event flag of multi-modal communications and system, and the method using it |
ES2696984T3 (en) | 2008-07-08 | 2019-01-21 | Proteus Digital Health Inc | Ingestion event marker data infrastructure |
CN104382598A (en) | 2008-08-13 | 2015-03-04 | 普罗透斯数字保健公司 | Method of producing a recognizer |
JP2010050514A (en) * | 2008-08-19 | 2010-03-04 | Sony Corp | Wireless communication device and wireless communication system |
JP5109905B2 (en) * | 2008-09-29 | 2012-12-26 | 富士通モバイルコミュニケーションズ株式会社 | Communication device |
US8036748B2 (en) | 2008-11-13 | 2011-10-11 | Proteus Biomedical, Inc. | Ingestible therapy activator system and method |
CA2746650A1 (en) | 2008-12-11 | 2010-06-17 | Proteus Biomedical, Inc. | Evaluation of gastrointestinal function using portable electroviscerography systems and methods of using the same |
US9659423B2 (en) | 2008-12-15 | 2017-05-23 | Proteus Digital Health, Inc. | Personal authentication apparatus system and method |
US9439566B2 (en) | 2008-12-15 | 2016-09-13 | Proteus Digital Health, Inc. | Re-wearable wireless device |
TWI424832B (en) | 2008-12-15 | 2014-02-01 | Proteus Digital Health Inc | Body-associated receiver and method |
JP5785097B2 (en) | 2009-01-06 | 2015-09-24 | プロテウス デジタル ヘルス, インコーポレイテッド | Pharmaceutical dosage delivery system |
CN102341031A (en) | 2009-01-06 | 2012-02-01 | 普罗秋斯生物医学公司 | Ingestion-related biofeedback and personalized medical therapy method and system |
WO2010111403A2 (en) | 2009-03-25 | 2010-09-30 | Proteus Biomedical, Inc. | Probablistic pharmacokinetic and pharmacodynamic modeling |
NZ619375A (en) | 2009-04-28 | 2015-03-27 | Proteus Digital Health Inc | Highly reliable ingestible event markers and methods for using the same |
WO2010132331A2 (en) | 2009-05-12 | 2010-11-18 | Proteus Biomedical, Inc. | Ingestible event markers comprising an ingestible component |
US8558563B2 (en) | 2009-08-21 | 2013-10-15 | Proteus Digital Health, Inc. | Apparatus and method for measuring biochemical parameters |
TWI517050B (en) | 2009-11-04 | 2016-01-11 | 普羅托斯數位健康公司 | System for supply chain management |
UA109424C2 (en) | 2009-12-02 | 2015-08-25 | PHARMACEUTICAL PRODUCT, PHARMACEUTICAL TABLE WITH ELECTRONIC MARKER AND METHOD OF MANUFACTURING PHARMACEUTICAL TABLETS | |
EP2531099B1 (en) | 2010-02-01 | 2018-12-12 | Proteus Digital Health, Inc. | Data gathering system |
RU2012143791A (en) | 2010-04-07 | 2014-05-20 | Проутьюс Диджитал Хэлс, Инк. | MINIATURE INGESTED DEVICE |
TWI557672B (en) | 2010-05-19 | 2016-11-11 | 波提亞斯數位康健公司 | Computer system and computer-implemented method to track medication from manufacturer to a patient, apparatus and method for confirming delivery of medication to a patient, patient interface device |
JP2014504902A (en) | 2010-11-22 | 2014-02-27 | プロテウス デジタル ヘルス, インコーポレイテッド | Ingestible device with medicinal product |
US8629758B2 (en) * | 2011-01-04 | 2014-01-14 | Critical Alert Systems, LLC | System and method for transmitting messages received from a paging network on a paging device to electronic devices |
US9439599B2 (en) | 2011-03-11 | 2016-09-13 | Proteus Digital Health, Inc. | Wearable personal body associated device with various physical configurations |
KR101760424B1 (en) * | 2011-05-20 | 2017-07-31 | 엘지전자 주식회사 | Mobile terminal and control method therof |
US8331960B1 (en) * | 2011-06-08 | 2012-12-11 | Critical Alert Systems Llc | Systems and methods for communicating with a paging network operations center through wireless cellular devices |
WO2015112603A1 (en) | 2014-01-21 | 2015-07-30 | Proteus Digital Health, Inc. | Masticable ingestible product and communication system therefor |
US9756874B2 (en) | 2011-07-11 | 2017-09-12 | Proteus Digital Health, Inc. | Masticable ingestible product and communication system therefor |
IN2014MN00183A (en) | 2011-07-21 | 2015-06-19 | Proteus Digital Health Inc | |
US20130089080A1 (en) * | 2011-10-06 | 2013-04-11 | Cambridge Silicon Radio Limited | Data merging for bluetooth devices |
US9235683B2 (en) | 2011-11-09 | 2016-01-12 | Proteus Digital Health, Inc. | Apparatus, system, and method for managing adherence to a regimen |
WO2014005939A1 (en) * | 2012-07-05 | 2014-01-09 | Iminds Vzw | Methods for configuring a device for establishing a first wireless link with a network. |
KR20150038038A (en) | 2012-07-23 | 2015-04-08 | 프로테우스 디지털 헬스, 인코포레이티드 | Techniques for manufacturing ingestible event markers comprising an ingestible component |
DK2910013T3 (en) | 2012-10-18 | 2018-08-06 | Proteus Digital Health Inc | Apparatus, system and method for adaptive optimization for power output and transmit power in a power source for a communication device |
WO2014120669A1 (en) | 2013-01-29 | 2014-08-07 | Proteus Digital Health, Inc. | Highly-swellable polymeric films and compositions comprising the same |
US10175376B2 (en) | 2013-03-15 | 2019-01-08 | Proteus Digital Health, Inc. | Metal detector apparatus, system, and method |
WO2014151929A1 (en) | 2013-03-15 | 2014-09-25 | Proteus Digital Health, Inc. | Personal authentication apparatus system and method |
JP6511439B2 (en) | 2013-06-04 | 2019-05-15 | プロテウス デジタル ヘルス, インコーポレイテッド | Systems, devices, and methods for data collection and outcome assessment |
US9357492B2 (en) * | 2013-08-05 | 2016-05-31 | Qualcomm Incorporated | WLAN-capable remote control device |
US9796576B2 (en) | 2013-08-30 | 2017-10-24 | Proteus Digital Health, Inc. | Container with electronically controlled interlock |
RU2628404C1 (en) | 2013-09-20 | 2017-08-16 | Протеус Диджитал Хелс, Инк. | Methods, devices and systems of signals receiving and decoding in the presence of noise using the shears and deformation |
JP2016537924A (en) | 2013-09-24 | 2016-12-01 | プロテウス デジタル ヘルス, インコーポレイテッド | Method and apparatus for use with electromagnetic signals received at frequencies that are not accurately known in advance |
US10084880B2 (en) | 2013-11-04 | 2018-09-25 | Proteus Digital Health, Inc. | Social media networking based on physiologic information |
US11051543B2 (en) | 2015-07-21 | 2021-07-06 | Otsuka Pharmaceutical Co. Ltd. | Alginate on adhesive bilayer laminate film |
BR112019000861B1 (en) | 2016-07-22 | 2020-10-27 | Proteus Digital Health, Inc | electronic device |
TWI735689B (en) | 2016-10-26 | 2021-08-11 | 日商大塚製藥股份有限公司 | Methods for manufacturing capsules with ingestible event markers |
Citations (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5307370A (en) * | 1991-06-03 | 1994-04-26 | Motorola, Inc. | Secure cordless radio-telephone |
US5677927A (en) * | 1994-09-20 | 1997-10-14 | Pulson Communications Corporation | Ultrawide-band communication system and method |
US5687169A (en) * | 1995-04-27 | 1997-11-11 | Time Domain Systems, Inc. | Full duplex ultrawide-band communication system and method |
US6144464A (en) * | 1997-09-11 | 2000-11-07 | 3Com Corporation | Method and system for modification of fax data rate over wireless channels |
US6172673B1 (en) * | 1996-04-23 | 2001-01-09 | Nokia Mobile Phones, Ltd. | Multimedia terminal and method for realizing multimedia reception |
US20010007815A1 (en) * | 1999-12-17 | 2001-07-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system for establishing a short-range radio link |
US20010049262A1 (en) * | 2000-05-26 | 2001-12-06 | Arto Lehtonen | Hands-free function |
US20010055356A1 (en) * | 2000-06-27 | 2001-12-27 | Davies Robert J. | Multicast radio communication system and apparatus |
US20020003792A1 (en) * | 2000-06-09 | 2002-01-10 | Schmidl Timothy M. | Wireless communications with frequency band selection |
US20020065099A1 (en) * | 1998-02-11 | 2002-05-30 | Per Bjorndahl | System, method and apparatus for secure transmission of confidential information |
US20020073269A1 (en) * | 2000-12-13 | 2002-06-13 | Hiroshi Kawashima | Data-recording-medium controller, data-recording-medium control method, data-recording apparatus and data-recording-apparatus control unit |
US20020080866A1 (en) * | 2000-11-30 | 2002-06-27 | Stephane Bouet | Method in short range RF communication |
US20020151276A1 (en) * | 2001-02-22 | 2002-10-17 | Osamu Ito | Wireless communication device and method therefor |
US6507734B1 (en) * | 1998-12-18 | 2003-01-14 | Skyworks Solutions, Inc. | Method and system which uses sound wave based communication to generate a secure wireless link between a handset and base station |
US20030032422A1 (en) * | 2001-08-13 | 2003-02-13 | Wynbeek John C. | Asymmetric wireless communication system using two different radio technologies |
US6539503B1 (en) * | 1999-11-23 | 2003-03-25 | Hewlett-Packard Company | Method and apparatus for testing error detection |
US20030063196A1 (en) * | 2000-05-08 | 2003-04-03 | Dennis Palatov | Handheld portable interactive data storage device |
US6549567B1 (en) * | 1994-09-20 | 2003-04-15 | Time Domain Corporation | Full duplex ultrawide-band communication system and method |
US20030078037A1 (en) * | 2001-08-17 | 2003-04-24 | Auckland David T. | Methodology for portable wireless devices allowing autonomous roaming across multiple cellular air interface standards and frequencies |
US6556825B1 (en) * | 2000-02-08 | 2003-04-29 | Sharp Laboratories Of America, Inc. | Method and apparatus for automatic adaptation of communications systems to regional spectrum variations |
US6571212B1 (en) * | 2000-08-15 | 2003-05-27 | Ericsson Inc. | Mobile internet protocol voice system |
US6571089B1 (en) * | 1999-06-14 | 2003-05-27 | Time Domain Corporation | Method and apparatus for moderating interference while effecting impulse radio wireless control of equipment |
US20030100288A1 (en) * | 2001-11-29 | 2003-05-29 | General Electric Company One Research Circle | Universal PLC radio frequency enhanced bridge |
US20030108010A1 (en) * | 2001-12-11 | 2003-06-12 | Samsung Electronics Co., Ltd. | Wireless communication apparatus and a method using the same |
US6587949B1 (en) * | 1998-06-26 | 2003-07-01 | Fotonation Holdings, Llc | Secure storage device for transfer of data via removable storage |
US20030137966A1 (en) * | 2002-01-22 | 2003-07-24 | Odman Knut T. | Method for improved media quality feedback |
US20030147453A1 (en) * | 2002-02-06 | 2003-08-07 | Texas Instruments Incorporated | Adaptive frequency hopping communication scheme |
US20030148767A1 (en) * | 2001-05-08 | 2003-08-07 | Shigeru Sugaya | Radio communication system, control station, communication apparatus, communication control method, radio communciation method, and communication control program |
US20030174048A1 (en) * | 1998-12-11 | 2003-09-18 | Mccorkle John W. | Method and system for performing distance measuring and direction finding using ultrawide bandwidth transmissions |
US20030203741A1 (en) * | 2002-04-26 | 2003-10-30 | Kabushiki Kaisha Toshiba | Autonomous distributed wireless network system, method of autonomous distributed wireless network communication and wireless terminal apparatus |
US20040066762A1 (en) * | 2001-02-09 | 2004-04-08 | Ari Alastalo | Data communication system |
US6799287B1 (en) * | 2000-05-01 | 2004-09-28 | Hewlett-Packard Development Company, L.P. | Method and apparatus for verifying error correcting codes |
US20040204076A1 (en) * | 2002-06-28 | 2004-10-14 | Motorola, Inc. | Subscriber device and method therein for enhancing interfaces thereto |
US20040214568A1 (en) * | 2002-03-27 | 2004-10-28 | Uraxs Communications, Inc. | Remote UltraWide Band communication system with short messaging and other functions |
US20040219897A1 (en) * | 2003-05-03 | 2004-11-04 | Samsung Electronics Co., Ltd. | Method and apparatus for ultra wideband wireless communication using channel information |
US20040235468A1 (en) * | 2003-05-19 | 2004-11-25 | Luebke Charles J. | Wireless network clustering communication system, wireless communication network, and access port for same |
US20050037775A1 (en) * | 2003-06-27 | 2005-02-17 | Mark Moeglein | Method and apparatus for wireless network hybrid positioning |
US20050078598A1 (en) * | 2003-08-21 | 2005-04-14 | Anuj Batra | Enhancement to the multi-band OFDM physical layer |
US20050193309A1 (en) * | 2003-08-21 | 2005-09-01 | Francesco Grilli | Methods for forward error correction coding above a radio link control layer and related apparatus |
US6957086B2 (en) * | 2002-05-01 | 2005-10-18 | Microsoft Corporation | Method for wireless capability discovery and protocol negotiation, and wireless device including same |
US6961541B2 (en) * | 2002-05-24 | 2005-11-01 | Aeroscout, Inc. | Method and apparatus for enhancing security in a wireless network using distance measurement techniques |
US20050283207A1 (en) * | 2002-05-31 | 2005-12-22 | Erwin Hochmair | Low power signal transmission |
US6993343B2 (en) * | 2000-08-29 | 2006-01-31 | Matsushita Electric Industrial Co., Ltd. | Base station device and wireless communication method |
US7096033B1 (en) * | 2000-07-18 | 2006-08-22 | Koninkiljke Phillips Electronics N.V. | Mobile apparatus enabling inter-network communication |
US7103314B2 (en) * | 2002-12-27 | 2006-09-05 | Atheros Communications, Inc. | System and method of conforming wireless devices to worldwide regulations |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2287383A (en) | 1994-03-11 | 1995-09-13 | Motorola Ltd | Notification by energy burst of messages with unacceptable quality |
EP1050144A1 (en) | 1998-01-22 | 2000-11-08 | Maxon Systems Inc. (London) Ltd. | Secure data communication system |
US6349199B1 (en) | 1998-02-12 | 2002-02-19 | Ericsson Inc. | Reliable continuously operating fixed cellular terminal |
EP0999717A2 (en) | 1998-11-05 | 2000-05-10 | Caly, Inc. | Broadband wireless mesh topology network |
EP1185033A4 (en) | 2000-04-06 | 2004-06-23 | Ntt Docomo Inc | Multicasting method, multicasting system, mobile station and base station |
WO2002021746A2 (en) | 2000-09-08 | 2002-03-14 | Parker Joseph A | Communication system |
JP2003018148A (en) | 2001-07-05 | 2003-01-17 | Toshiba Corp | Radio data communication device and data communication method therefor |
DE10140446A1 (en) | 2001-08-17 | 2003-03-06 | Siemens Ag | Data processing unit splits data and code between cellular and local networks |
US7117008B2 (en) | 2002-01-03 | 2006-10-03 | Intel Corporation | Mitigating interference among multiple radio device types |
KR100465208B1 (en) | 2002-04-02 | 2005-01-13 | 조광선 | System, Apparatus, and Method for Wireless Mobile Communication in association with Mobile AD-HOC Network Support |
US7702284B2 (en) | 2003-09-12 | 2010-04-20 | Arto Palin | Method and system for processing acknowledgments in a wireless communications network |
US7782894B2 (en) | 2003-09-12 | 2010-08-24 | Nokia Corporation | Ultra-wideband/low power communication having a dedicated removable memory module for fast data downloads—apparatus, systems and methods |
US7499674B2 (en) | 2003-09-12 | 2009-03-03 | Nokia Corporation | Method and system for repeat request in hybrid ultra wideband-bluetooth radio |
US7278084B2 (en) | 2003-10-29 | 2007-10-02 | Nokia Corporation | Method and system for providing communications security |
-
2003
- 2003-09-12 US US10/660,544 patent/US7352998B2/en active Active
-
2004
- 2004-09-10 EP EP04104392.8A patent/EP1515497B1/en active Active
Patent Citations (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5307370A (en) * | 1991-06-03 | 1994-04-26 | Motorola, Inc. | Secure cordless radio-telephone |
US5677927A (en) * | 1994-09-20 | 1997-10-14 | Pulson Communications Corporation | Ultrawide-band communication system and method |
US6549567B1 (en) * | 1994-09-20 | 2003-04-15 | Time Domain Corporation | Full duplex ultrawide-band communication system and method |
US5687169A (en) * | 1995-04-27 | 1997-11-11 | Time Domain Systems, Inc. | Full duplex ultrawide-band communication system and method |
US6172673B1 (en) * | 1996-04-23 | 2001-01-09 | Nokia Mobile Phones, Ltd. | Multimedia terminal and method for realizing multimedia reception |
US6144464A (en) * | 1997-09-11 | 2000-11-07 | 3Com Corporation | Method and system for modification of fax data rate over wireless channels |
US20020065099A1 (en) * | 1998-02-11 | 2002-05-30 | Per Bjorndahl | System, method and apparatus for secure transmission of confidential information |
US6587949B1 (en) * | 1998-06-26 | 2003-07-01 | Fotonation Holdings, Llc | Secure storage device for transfer of data via removable storage |
US20030174048A1 (en) * | 1998-12-11 | 2003-09-18 | Mccorkle John W. | Method and system for performing distance measuring and direction finding using ultrawide bandwidth transmissions |
US6507734B1 (en) * | 1998-12-18 | 2003-01-14 | Skyworks Solutions, Inc. | Method and system which uses sound wave based communication to generate a secure wireless link between a handset and base station |
US6571089B1 (en) * | 1999-06-14 | 2003-05-27 | Time Domain Corporation | Method and apparatus for moderating interference while effecting impulse radio wireless control of equipment |
US6539503B1 (en) * | 1999-11-23 | 2003-03-25 | Hewlett-Packard Company | Method and apparatus for testing error detection |
US20010007815A1 (en) * | 1999-12-17 | 2001-07-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method and system for establishing a short-range radio link |
US6556825B1 (en) * | 2000-02-08 | 2003-04-29 | Sharp Laboratories Of America, Inc. | Method and apparatus for automatic adaptation of communications systems to regional spectrum variations |
US6799287B1 (en) * | 2000-05-01 | 2004-09-28 | Hewlett-Packard Development Company, L.P. | Method and apparatus for verifying error correcting codes |
US20030063196A1 (en) * | 2000-05-08 | 2003-04-03 | Dennis Palatov | Handheld portable interactive data storage device |
US20010049262A1 (en) * | 2000-05-26 | 2001-12-06 | Arto Lehtonen | Hands-free function |
US20020003792A1 (en) * | 2000-06-09 | 2002-01-10 | Schmidl Timothy M. | Wireless communications with frequency band selection |
US20010055356A1 (en) * | 2000-06-27 | 2001-12-27 | Davies Robert J. | Multicast radio communication system and apparatus |
US7096033B1 (en) * | 2000-07-18 | 2006-08-22 | Koninkiljke Phillips Electronics N.V. | Mobile apparatus enabling inter-network communication |
US6571212B1 (en) * | 2000-08-15 | 2003-05-27 | Ericsson Inc. | Mobile internet protocol voice system |
US6993343B2 (en) * | 2000-08-29 | 2006-01-31 | Matsushita Electric Industrial Co., Ltd. | Base station device and wireless communication method |
US20020080866A1 (en) * | 2000-11-30 | 2002-06-27 | Stephane Bouet | Method in short range RF communication |
US20020073269A1 (en) * | 2000-12-13 | 2002-06-13 | Hiroshi Kawashima | Data-recording-medium controller, data-recording-medium control method, data-recording apparatus and data-recording-apparatus control unit |
US20040066762A1 (en) * | 2001-02-09 | 2004-04-08 | Ari Alastalo | Data communication system |
US20020151276A1 (en) * | 2001-02-22 | 2002-10-17 | Osamu Ito | Wireless communication device and method therefor |
US20030148767A1 (en) * | 2001-05-08 | 2003-08-07 | Shigeru Sugaya | Radio communication system, control station, communication apparatus, communication control method, radio communciation method, and communication control program |
US20030032422A1 (en) * | 2001-08-13 | 2003-02-13 | Wynbeek John C. | Asymmetric wireless communication system using two different radio technologies |
US20030078037A1 (en) * | 2001-08-17 | 2003-04-24 | Auckland David T. | Methodology for portable wireless devices allowing autonomous roaming across multiple cellular air interface standards and frequencies |
US20030100288A1 (en) * | 2001-11-29 | 2003-05-29 | General Electric Company One Research Circle | Universal PLC radio frequency enhanced bridge |
US20030108010A1 (en) * | 2001-12-11 | 2003-06-12 | Samsung Electronics Co., Ltd. | Wireless communication apparatus and a method using the same |
US20030137966A1 (en) * | 2002-01-22 | 2003-07-24 | Odman Knut T. | Method for improved media quality feedback |
US20030147453A1 (en) * | 2002-02-06 | 2003-08-07 | Texas Instruments Incorporated | Adaptive frequency hopping communication scheme |
US20040214568A1 (en) * | 2002-03-27 | 2004-10-28 | Uraxs Communications, Inc. | Remote UltraWide Band communication system with short messaging and other functions |
US20030203741A1 (en) * | 2002-04-26 | 2003-10-30 | Kabushiki Kaisha Toshiba | Autonomous distributed wireless network system, method of autonomous distributed wireless network communication and wireless terminal apparatus |
US6957086B2 (en) * | 2002-05-01 | 2005-10-18 | Microsoft Corporation | Method for wireless capability discovery and protocol negotiation, and wireless device including same |
US6961541B2 (en) * | 2002-05-24 | 2005-11-01 | Aeroscout, Inc. | Method and apparatus for enhancing security in a wireless network using distance measurement techniques |
US20050283207A1 (en) * | 2002-05-31 | 2005-12-22 | Erwin Hochmair | Low power signal transmission |
US20040204076A1 (en) * | 2002-06-28 | 2004-10-14 | Motorola, Inc. | Subscriber device and method therein for enhancing interfaces thereto |
US7103314B2 (en) * | 2002-12-27 | 2006-09-05 | Atheros Communications, Inc. | System and method of conforming wireless devices to worldwide regulations |
US20040219897A1 (en) * | 2003-05-03 | 2004-11-04 | Samsung Electronics Co., Ltd. | Method and apparatus for ultra wideband wireless communication using channel information |
US20040235468A1 (en) * | 2003-05-19 | 2004-11-25 | Luebke Charles J. | Wireless network clustering communication system, wireless communication network, and access port for same |
US20050037775A1 (en) * | 2003-06-27 | 2005-02-17 | Mark Moeglein | Method and apparatus for wireless network hybrid positioning |
US20050078598A1 (en) * | 2003-08-21 | 2005-04-14 | Anuj Batra | Enhancement to the multi-band OFDM physical layer |
US20050193309A1 (en) * | 2003-08-21 | 2005-09-01 | Francesco Grilli | Methods for forward error correction coding above a radio link control layer and related apparatus |
Cited By (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7702284B2 (en) | 2003-09-12 | 2010-04-20 | Arto Palin | Method and system for processing acknowledgments in a wireless communications network |
US7782894B2 (en) | 2003-09-12 | 2010-08-24 | Nokia Corporation | Ultra-wideband/low power communication having a dedicated removable memory module for fast data downloads—apparatus, systems and methods |
US7278084B2 (en) | 2003-10-29 | 2007-10-02 | Nokia Corporation | Method and system for providing communications security |
US20050114714A1 (en) * | 2003-11-25 | 2005-05-26 | Microsoft Corporation | Modifying a power management algorithm based on wireless communication parameters |
US7380145B2 (en) * | 2003-11-25 | 2008-05-27 | Microsoft Corporation | Modifying a power management algorithm based on wireless communication parameters |
US20050246470A1 (en) * | 2004-04-28 | 2005-11-03 | Brenner David G | Wireless docking station |
US7697893B2 (en) | 2004-06-18 | 2010-04-13 | Nokia Corporation | Techniques for ad-hoc mesh networking |
US20060009159A1 (en) * | 2004-07-09 | 2006-01-12 | Leung Hung F | Protocol layer analysis in mobile device testing |
US20060046736A1 (en) * | 2004-08-31 | 2006-03-02 | Pering Trevor A | Methods and apparatus for managing wireless device power consumption by selecting among plural communication transceivers |
US20060094402A1 (en) * | 2004-11-03 | 2006-05-04 | Samsung Electronics Co., Ltd. | Security monitoring method in bluetooth device |
US20060178161A1 (en) * | 2005-02-04 | 2006-08-10 | Samsung Electronics Co., Ltd. | Method and system for automatically updating user information in a push-to-talk system |
US20060198335A1 (en) * | 2005-03-04 | 2006-09-07 | Jukka Reunamaki | Embedding secondary transmissions in an existing wireless communications network |
US20140065970A1 (en) * | 2005-03-08 | 2014-03-06 | Broadcom Corporation | Mechanism for improved interoperability when content protection is used with an audio stream |
DE112006003342B4 (en) | 2005-12-05 | 2018-07-05 | Lenovo (Beijing) Ltd. | Wireless display system and method therefor |
US9794777B2 (en) * | 2006-01-24 | 2017-10-17 | Qualcomm Technologies International, Ltd. | Varying device identities |
US20090219974A1 (en) * | 2006-01-24 | 2009-09-03 | Cambridge Silicon Radio Limited | Varying device identities |
US7912466B2 (en) * | 2006-02-10 | 2011-03-22 | Cambridge Silicon Radio Limited | Channel acquisition |
US20070197218A1 (en) * | 2006-02-10 | 2007-08-23 | Cambridge Silicon Radio Limited | Channel Acquisition |
US8311172B2 (en) * | 2006-07-17 | 2012-11-13 | Infineon Technologies Ag | Synchronizing high data-rate radio transceivers |
US20080013658A1 (en) * | 2006-07-17 | 2008-01-17 | Michael Lewis | Synchronizing high data-rate radio transceivers |
US20090241147A1 (en) * | 2006-09-05 | 2009-09-24 | Taek Soo Kim | Method of transmitting link-adaptive transmission of data stream in a mobile communication system |
US20080118014A1 (en) * | 2006-11-16 | 2008-05-22 | Nokia Corporation | Utilizing wake-up signals for synchronizing multiradio timing |
US7813697B2 (en) * | 2007-01-05 | 2010-10-12 | Apple Inc. | Power efficient high speed communication systems and methods |
US20080166967A1 (en) * | 2007-01-05 | 2008-07-10 | Apple Inc. | Power efficient high speed communication systems and methods |
US20090221320A1 (en) * | 2008-02-28 | 2009-09-03 | John Walley | Method and system for bluetooth transport sharing to carry gps or other types of data |
US8583169B2 (en) * | 2008-02-28 | 2013-11-12 | Broadcom Corporation | Method and system for bluetooth transport sharing to carry GPS or other types of data |
US20100274874A1 (en) * | 2009-04-24 | 2010-10-28 | Nokia Corporation | Service discovery protocol enhancement |
US20160366542A1 (en) * | 2009-10-02 | 2016-12-15 | Blackberry Limited | Methods and devices for facilitating bluetooth pairing using a camera as a barcode scanner |
US10623934B2 (en) * | 2009-10-02 | 2020-04-14 | Blackberry Limited | Methods and devices for facilitating bluetooth pairing using a camera as a barcode scanner |
US8358596B2 (en) * | 2010-09-20 | 2013-01-22 | Research In Motion Limited | Communications system providing mobile wireless communications device application module associations for respective wireless communications formats and related methods |
US8730845B2 (en) | 2010-09-20 | 2014-05-20 | Blackberry Limited | Communications system providing mobile wireless communications device application module associations for respective wireless communications formats and related methods |
US20120069772A1 (en) * | 2010-09-20 | 2012-03-22 | Research In Motion Limited | Communications system providing mobile wireless communications device application module associations for respective wireless communications formats and related methods |
US9209867B2 (en) * | 2011-06-28 | 2015-12-08 | Broadcom Corporation | Device for authenticating wanted NFC interactions |
US20130005243A1 (en) * | 2011-06-28 | 2013-01-03 | Broadcom Corporation | Device for Authenticating Wanted NFC Interactions |
US9742470B2 (en) | 2011-06-28 | 2017-08-22 | Nxp Usa, Inc. | Device for authenticating wanted NFC interactions |
US9474096B2 (en) * | 2012-09-28 | 2016-10-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Short range communication in a wireless communications system |
US20150245396A1 (en) * | 2012-09-28 | 2015-08-27 | Telefonaktiebolaget L M Ericsson | Short Range Communication in a Wireless Communications System |
US9681478B2 (en) | 2012-09-28 | 2017-06-13 | Telefonaktiebolaget Lm Ericsson (Publ) | Short range communication in a wireless communications system |
US10228903B2 (en) | 2013-07-19 | 2019-03-12 | Samsung Electronics Co., Ltd. | Method and device for communication |
DE102014101526A1 (en) * | 2014-02-07 | 2015-08-13 | Aesculap Ag | Data communication device and method for data communication |
US20170150532A1 (en) * | 2014-07-09 | 2017-05-25 | Aisin Aw Co., Ltd. | Wireless communication system, information terminal and communication device |
JP2016019181A (en) * | 2014-07-09 | 2016-02-01 | 日本電信電話株式会社 | Radio communication system, radio base station device, radio terminal device and data distribution device |
US20160277878A1 (en) * | 2015-03-16 | 2016-09-22 | Samsung Electronics Co., Ltd. | Method for communicating data and electronic device thereof |
WO2019219115A1 (en) * | 2018-05-16 | 2019-11-21 | Bayerische Motoren Werke Aktiengesellschaft | Master-slave system |
DE102018207659A1 (en) * | 2018-05-16 | 2019-11-21 | Bayerische Motoren Werke Aktiengesellschaft | Master-slave system |
CN112106426A (en) * | 2018-05-16 | 2020-12-18 | 宝马股份公司 | Master-slave system |
US11646762B2 (en) | 2018-05-16 | 2023-05-09 | Bayerische Motoren Werke Aktiengesellschaft | Master-slave system |
US11013062B2 (en) * | 2019-01-31 | 2021-05-18 | Qualcomm Incorporated | Fast role switch between bluetooth true wireless stereo (TWS) earbuds |
US11729861B2 (en) | 2019-01-31 | 2023-08-15 | Qualcomm Incorporated | Fast role switch between bluetooth true wireless stereo (TWS) earbuds |
CN114095937A (en) * | 2020-07-30 | 2022-02-25 | 株式会社东海理化电机制作所 | Control device, recording medium, and system |
CN115665717A (en) * | 2022-12-27 | 2023-01-31 | 合肥炬芯智能科技有限公司 | Data transmission method, electronic equipment and computer readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
EP1515497B1 (en) | 2021-11-10 |
EP1515497A3 (en) | 2005-08-10 |
US7352998B2 (en) | 2008-04-01 |
EP1515497A2 (en) | 2005-03-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7352998B2 (en) | Method and system for establishing a wireless communications link | |
US7697893B2 (en) | Techniques for ad-hoc mesh networking | |
US10334508B2 (en) | Systems and methods for implementing band service discovery | |
US20200396017A1 (en) | Transmission rate switching method, bluetooth device, and computer-readable medium | |
JP4588954B2 (en) | Method and apparatus for dynamically controlling talk groups in a wireless network | |
US20070149123A1 (en) | Multiple radio usage in a wireless communications device | |
US9094424B2 (en) | Method, apparatus, and computer program product for digital stream swapping between signal sources | |
US6907226B2 (en) | Wireless communication apparatus, wireless communication method thereof, and wireless communication system employing the same | |
US7499674B2 (en) | Method and system for repeat request in hybrid ultra wideband-bluetooth radio | |
US7278084B2 (en) | Method and system for providing communications security | |
KR101707364B1 (en) | Apparatus and method for performing wireless docking service | |
US9699715B2 (en) | Discovery method and device in a wireless communication system | |
US20090147837A1 (en) | Wireless system synchronization using frequency shift modulation and on-off keying modulation | |
CN116711449A (en) | Communication device and communication method for multilink peer-to-peer communication | |
US20050059420A1 (en) | Method and system for power-based control of an ad hoc wireless communications network | |
US20080175197A1 (en) | Method and system for wireless communication using out-of-band channels | |
KR20220129518A (en) | Secure multicast/broadcast ranging | |
EP1419452A2 (en) | Naming distribution method for ad hoc networks | |
CN103067050B (en) | A kind of communication system and method | |
CN113455026B (en) | Access method and communication device | |
US20030139191A1 (en) | Wireless communication apparatus capable of improving connection rate | |
WO2014069870A1 (en) | Method and device for fast link synchronization in wlan system | |
JP2002246998A (en) | Radio communication equipment and communication method thereof, and radio communication system using the same | |
CN108684021A (en) | A kind of Bluetooth Low Energy communication means and device | |
Jain | Wireless Protocols for IoT Part I: Bluetooth and Bluetooth Smart |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA CORPORATION, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PALIN, ARTO;SALOKANNEL, JUHA;REUNAMAKI, JUKKA;REEL/FRAME:014501/0835 Effective date: 20030912 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: NOKIA TECHNOLOGIES OY, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NOKIA CORPORATION;REEL/FRAME:035570/0474 Effective date: 20150116 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 12 |