US20020132630A1 - Wireless private branch exchange (WPBX) and communicating between mobile units and base stations - Google Patents

Wireless private branch exchange (WPBX) and communicating between mobile units and base stations Download PDF

Info

Publication number
US20020132630A1
US20020132630A1 US10/078,008 US7800802A US2002132630A1 US 20020132630 A1 US20020132630 A1 US 20020132630A1 US 7800802 A US7800802 A US 7800802A US 2002132630 A1 US2002132630 A1 US 2002132630A1
Authority
US
United States
Prior art keywords
base station
base stations
handset
switch
call
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.)
Abandoned
Application number
US10/078,008
Inventor
Nitzan Arazi
Yaron Soffer
Haim Barak
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Commil USA LLC
Original Assignee
Commil Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=27393413&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US20020132630(A1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Commil Ltd filed Critical Commil Ltd
Priority to US10/078,008 priority Critical patent/US20020132630A1/en
Publication of US20020132630A1 publication Critical patent/US20020132630A1/en
Assigned to COMMIL USA LLC reassignment COMMIL USA LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COMMIL, LTD.
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0083Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835Determination of neighbour cell lists
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725Cordless telephones
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/06Reselecting a communication resource in the serving access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725Cordless telephones
    • H04M1/733Cordless telephones with a plurality of base stations connected to a plurality of lines
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/005Discovery of network devices, e.g. terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/16WPBX [Wireless Private Branch Exchange]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2250/00Details of telephonic subscriber devices
    • H04M2250/02Details of telephonic subscriber devices including a Bluetooth interface
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W56/00Synchronisation arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/105PBS [Private Base Station] network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices

Definitions

  • the invention relates to wireless communications systems having a plurality of mobile units (devices) having the ability to connect short-range with a plurality of Base Stations, and techniques for handing off a mobile unit from one Base Station to another when the mobile unit moves between areas of coverage of neighboring Base Stations.
  • WPBX Wireless Private Branch Exchange
  • a WPBX the Base Stations are interconnected in order to allow handsets that are in different cells to communicate with one another.
  • the handoff (or handover) of communication from one Base Station to another Base Station enables uninterrupted communication.
  • a central unit that is usually called the “Switch” is connected to all the Base Stations. The Switch controls the operation of the system, routes the call to Base Stations and to Gateways, which connect the WPBX to external communication systems.
  • the transmission power of a cordless handset in the WPBX is usually lower than the transmission power of the handset of a standard cellular system, which results in a WPBX for cordless handsets having much smaller cells (referred to as mini-cells, or micro-cells or picocells) than the cells of a standard cellular system.
  • cordless handsets use communication protocols that are also used in cellular system, but they transmit in a lower power than a mobile (cellular) handset.
  • protocols in use are GSM and IS-136. According to these protocols the handoff between cells is performed by collaboration of the cordless handset, the Base Stations and the Switch.
  • These handsets can connect to the WPBX when they are in its coverage area, and can also connect to any other cellular system that supports the communication protocol that they are using.
  • Some handsets use communication protocols that were designed especially to allow communication with WPBX. Some examples are DECT, CT-2, PAC, and PACS.
  • the handset is usually a dedicated handset that is used only in the area covered by the WBPX.
  • Some handsets have dual mode support. For example a handset may communicate with the WPBX using DECT, and may allow communication with other cellular systems using GSM.
  • Some WPBXs use standard cordless handsets. These handsets have no special mechanism to support the handoff between cells. In these systems the Switch and the Base Stations perform the handoff, and the handset is not aware of (does not participate actively in) the handoff process. When a standard cordless handset moves from one cell to another the Switch routes the call to another cell. Since cordless phones use “simple” protocols, for example an analog fixed transmission, when the call is routed to the new cell, the cordless phone automatically will receive it.
  • Short-range communication systems are used for many purposes.
  • a growing trend for short-range communication usage is Personal Area Network (PAN) devices and applications, among such is the “all in one handset” and personal data devices.
  • PAN Personal Area Network
  • Such type of handset supports standard cellular communication, and also has the ability to communicate with personal area network devices that are in its near vicinity, using short-range communication.
  • PAN short-range communication standards were not designed to allow mobility, i.e. they were not designed to allow handoff in between Base Stations in general and during an active session in particular. This limits a session via such device to be linked to a single Base Station and therefore to very limited area.
  • the “Bluetooth” standard is a short-range wireless communication standard that has many uses for voice applications and telephony (e.g. cordless phone, wireless headsets) and also for data applications (laptop to personal computer communication, wireless local area network Gateways etc.).
  • the Bluetooth wireless technology is implemented using a universal radio interface in the 2.45 GHz frequency band that enables portable electronic devices to connect and communicate wirelessly via short-range, ad hoc networks.
  • Each unit can simultaneously communicate with up to seven other units per piconet. Moreover, each unit can simultaneously belong to several piconets.
  • Bluetooth connection is planned to be standard feature in future cellular handsets, Personal Digital Assistants (PDAs), Palmtop and Laptop computers.
  • PDAs Personal Digital Assistants
  • Palmtop and Laptop computers.
  • the Bluetooth standard does not support mobility between Base Stations, since it was primarily designed for short-range communication as a cable replacement.
  • a cellular handset with Bluetooth wireless technology will be able to operate as a cordless phone, but only in the near vicinity of a single Base Station.
  • mobile personal data devices such as PDA's and mobile computers.
  • CT-2 a communication protocol DECT Digital Enhanced Cordless Telephone communication protocol DN Destination Number ECHO a response to a PING FIFO First In, First Out FTP File Transfer Protocol Gateway an interface for communications between dissimilar services GHz GigaHertz GSM: Global System for Mobile Communication handoff transfer of mobile devices from one Base Station to another Base Station ID Identification (number) IEEE 802.2 Ethernet protocol IS-136 communication protocol ISDN Integrated Services Digital Network ITU-T 802.15 a communication standard similar to the Bluetooth standard ITU-T Q.931 a telephony protocol for call setup IVR Interactive Voice Response LAN Local Area Network LMSE Least Mean Square Error MSC Mobile Switching Center (MSC) PAC a communication protocol PACS a communication protocol PAN Personal Area Network PBX Private Branch Exchange PABX Private Automatic Branch Exchange (also referred to as PBX) PDA Personal Digital (or Data) Assistant picocell a coverage area of a short-range Base Station PING a command which is sent, soliciting a response PPP Point-To-Point
  • a general object of the invention is to provide a technique for allowing mobile units (devices) such as standard cordless telephone handsets and PDA (Personal Digital Assistant), laptop or notebook computers or similar devices that support wireless communication (such as Bluetooth wireless technology) to seamlessly connect to a Wireless Private Branch Exchange (WPBX), or to a standard (wired) PBX or to a LAN or to a cellular telephone network or to a standard wired telephone network, thereby avoiding the use of special (typically expensive) handsets or attachmnents or software or hardware agents, with the abovementioned mobile devices.
  • WPBX Wireless Private Branch Exchange
  • a standard (wired) PBX or to a LAN or to a cellular telephone network or to a standard wired telephone network thereby avoiding the use of special (typically expensive) handsets or attachmnents or software or hardware agents, with the abovementioned mobile devices.
  • a wireless communication system comprising at least two Base Stations, at least one Switch in communication with the Base Stations, a method of communicating between mobile units and the Base Stations comprising: dividing a communication protocol into a low-level protocol for performing tasks that require accurate time synchronization and a high-level protocol which does not require accurate time synchronization; and for each connection of a mobile unit with a Base Station, running an instance of the low-level protocol at the Base Station connected with the mobile unit and running an instance of the high-level protocol at the Switch.
  • a wireless communication system comprising a Base Station connected with a mobile unit, a method of synchronizing at least one neighboring Base Station to the Base Station connected with the mobile unit comprising: from the Base Station connected with the mobile unit, sending call parameters and rough synchronization information to the at least one neighboring Base Station; and at the at least one neighboring Base Station, monitoring transmissions of at least one of: the Base Station connected with the mobile unit; the mobile unit; and a beacon signal from a beacon transmitter which is within range of the at least one neighboring Base Station and the Base Station connected with the mobile unit.
  • a method of synchronizing at least one neighboring Base Station to a Base Station connected with a mobile unit comprising: from the Base Station connected with the mobile unit, periodically transmitting during a selected time interval with higher transmission power than during normal transmission; and receiving the transmission with higher transmission power at the least one neighboring Base Station.
  • a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting the presence of a specific mobile unit in a coverage area of at least one neighboring Base Station, comprising: the Base Station connected with the mobile unit provides, to the at least one neighboring Base Station, information about the connection with the mobile unit, including rough TOD and a device address for the mobile unit; at the at least one neighboring Base Station, receiving information and generating a list of frequencies in which the mobile unit is likely to transmit; and at the at least one neighboring Base Station, checking for a signal transmitted by the mobile unit.
  • a method for detecting a mobile unit by a Base Station wherein frequency-hopping is used to communicate between Base Stations and mobile units, comprising: at a Base Station that is connected to a mobile unit, periodically yielding a hop; and during the hop which has been yielded by the Base Station connected with the mobile unit, communicating with the mobile unit from at least one neighboring Base Station.
  • a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting a handset by at least one Base Station which is waiting for the mobile unit to enter its coverage area, comprising: from the at least one Base Station waiting for the mobile unit to enter its coverage area and the Base Station connected with the mobile unit, sending a PING command to the mobile unit; and at the Base Station waiting for the mobile unit to enter its coverage area, receiving an ECHO reply from the mobile unit.
  • a wireless communication system comprising at least two Base Stations, at least one Switch in communication with the Base Stations, and at least one mobile unit, a method of handing off the mobile unit from a Base Station communicating with the mobile unit and a neighboring Base Station, comprising: smoothing a plurality of signals received from a handset by a plurality of Base Stations; comparing the signals with one another; and selecting a Base Station for handoff based on signal quality.
  • a wireless communication system comprising at least two Base Stations and at least one Switch in communication with the Base Stations, a method of performing handoff of a session from a Base Station connected with a mobile unit to a neighboring Base Station, wherein an instance of a low-level communications protocol is running at the Base Station connected with the mobile unit, comprising: at the Switch, determining when to perform handoff to a selected one of the neighboring Base Stations; at the selected one of the neighboring Base Stations, creating a copy of the low-level communications protocol, including at least a synchronized time of day (TOD) parameter; from the Switch, sending a command to stop communication with the mobile unit at a specified TOD to the Base Station connected with the mobile unit and sending a command to start communication with the mobile unit at the specified TOD to the selected one of the neighboring Base Stations; and updating session status tables in the Switch and in the Base Stations.
  • TOD time of day
  • a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting and synchronizing with the mobile unit prior to receiving a handoff of a session with the mobile unit, comprising: from the Base Station connected with the mobile unit, sending rough synchronization information to at least one neighboring Base Station; at the neighboring Base Station, performing a wide-range search for “target” signals having the correct timing for a mobile unit, based on the rough synchronization information provided by the Base Station which is connected with the mobile unit; narrowing the search for an actual signal from the mobile unit; acquiring the target signal; and synchronizing the neighboring Base Station to the Base Station connected with the mobile unit.
  • a system comprises one or more mobile units such as standard cordless handsets, two or more Base Stations, and at least one Switch.
  • the Base Stations are connected to one another and to the Switch.
  • the handsets communicate directly with the Base Stations, rather than with one another.
  • the Base Stations and Switch communicate directly with one another, rather than, for example, over the PSTN.
  • the system may interface with the PSTN, the Internet or a LAN, or with a PBX via a Gateway.
  • mobile units e.g., standard cordless handsets
  • the mobile device uses complicated digital communication methods, so simple handoff methods that only the Switch supports are inadequate. Rather, the Switch and Base Stations cooperate with one another for the handoff operation. Accurate synchronization of Base Stations facilitates handoff.
  • the handoff operation does not require explicit cooperation between the mobile device and the Base Stations.
  • a method for dividing the short-range communication protocol that is used by the handset between high-level protocols which do not need accurate time synchronization and low-level protocols which have strict time synchronization requirements (require accurate time synchronization).
  • the low-level protocols are performed by the Base Stations, and the high-level protocols are performed in the Switch. This enables handoff to be performed even when complex (e.g. frequency hopping, encryption, authentication) and multi-level protocols are used. This also reduces the synchronization requirements between Base Stations.
  • a method for accurately synchronizing the Base Stations and, more particularly, for synchronizing the Base Stations when frequency-hopping communication is used.
  • a method for detecting the presence of a mobile device in the coverage area of a Base Station (i.e., its picocell).
  • a method for determining when to perform handoff of a session(i.e., a phone call, a data link, etc.), and to which Base Station to hand the session, by measuring signal quality at the Base Stations. This method is effective, even when complex transmission methods are used.
  • the methods disclosed herein are not limited to the communication of a certain type of data. Hence, they can be utilized for telephony applications and for data applications.
  • FIG. 1 is a diagram of a cellular system covering a relatively large area and a Wireless Private Branch Exchange (WPBX) system covering a relatively smaller area, illustrating that a cellular handset can communicate with a Base Station of the cellular system and also with Base Stations of the WPBX;
  • WPBX Wireless Private Branch Exchange
  • FIG. 2 is a schematic block diagram illustrating main components and architecture of a WPBX system, suitable for use as the WPBX system of FIG. 1;
  • FIG. 3A is a schematic block diagram of a communications system incorporating a WPBX, such as the WPBX of FIG. 2, with the addition of a Gateway connecting the WPBX to the Public Switched Telephone Network (PSTN);
  • PSTN Public Switched Telephone Network
  • FIG. 3B is a schematic block diagram of a communications system incorporating a WPBX, such as the WPBX of FIG. 2, with the addition of a Gateway connecting the WPBX to a Private Branch Exchange (PBX);
  • WPBX Wideband Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packet Packe (PBX)
  • PBX Private Branch Exchange
  • FIG. 4 is a schematic block diagram illustrating an architecture for a WPBX, with the Base Stations, the Switch and the Gateway interconnected by a local area network (LAN);
  • LAN local area network
  • FIG. 5 is a flowchart illustrating a procedure for call “setup” at an originating Base Station of a WPBX
  • FIG. 6 is a flowchart illustrating a procedure for call “setup” at a receiving Base Station of a WPBX
  • FIG. 7 is a flowchart illustrating a procedure for call “setup” at a Switch of a WPBX
  • FIGS. 8A and 8B are schematic block diagrams illustrating an architecture for dividing the communication protocol into low-level and high-level protocols for implementation in the Base Stations and in the Switch, respectively, of a WPBX particularly during a handoff, according to the invention
  • FIGS. 9A, 9B and 9 C are schematic block diagrams illustrating rough and fine synchronization of Base Stations in a WPBX, particularly during a handoff, according to the invention.
  • FIG. 10 is a graph of a Base Station's transmission power, during hops, illustrating that once in every K hops the energy that the Base Station transmits may be increased to allow other Base Stations that normally do not receive transmissions from the transmitting Base Station to synchronize to the transmitting Base Station, according to the invention;
  • FIG. 11 is a schematic block diagram illustrating an architecture for major components of a Base Station, according to the invention.
  • FIG. 12 is a flowchart illustrating a “call routing task” that runs in the Switch in order to isolate the high-level protocols from the occurrence of the handoff, according to the invention
  • FIG. 13 is a schematic block diagram illustrating a passive method for detecting arrival of a handset in a Base Station's coverage area during a call, according to the invention
  • FIG. 14A is a diagram illustrating a handset communicating with one Base Station, and six other neighboring Base Stations waiting for the handset to enter their coverage area, according to the invention
  • FIGS. 14B, 14C and 14 D are graphs illustrating transmissions by the Base Station communicating with the handsets, and by the neighboring Base stations, according to the invention.
  • FIGS. 15A and 15B are diagrams illustrating detection of a handset by a Base Station in communication with the handset and a neighboring Base Station, according to the invention.
  • FIG. 16A is a flowchart illustrating a procedure that Base Stations may use to detect a handset that enters their coverage area, according to the invention
  • FIG. 16B is a flowchart illustrating a procedure that Base Stations may use to determine that a handset connected to them is moving into the coverage area of another Base Station, according to the invention
  • FIG. 17A is a schematic block diagram illustrating a method for making a handoff decision, performed in the central Switch, when a passive detection method is used, according to the invention
  • FIG. 17B is a schematic block diagram illustrating a method for making a handoff decision, performed in the central Switch, when an active detection method is used, according to the invention
  • FIG. 18 is a schematic block diagram of a Base Station comprising a central processing unit (CPU), front end processors, memory, TOD synchronization and handset detection unit, and an interface to a local area network (LAN), according to the invention;
  • CPU central processing unit
  • front end processors memory
  • TOD synchronization and handset detection unit an interface to a local area network (LAN)
  • LAN local area network
  • FIG. 19 is a schematic block diagram illustrating the front-end processor of the Base Station of FIG. 18, which comprises a base-band processor and a radio frequency (RF) front end, according to the invention
  • FIG. 20 is a schematic block diagram illustrating the structure of a detector and fine TOD estimator, based on a matching correlator, according to the invention.
  • FIG. 21 is a schematic block diagram of an implementation for the Time-Frequency Correlator of FIG. 20, according to the invention.
  • FIG. 22 is a diagram illustrating an implementation of a WPBX system with two Switches, according to the invention.
  • FIG. 23 is a flow chart illustrating a procedure for transmitting “PING” commands to a handset and receiving “ECHO” responses from the handset, when the Base Station originating the “PING” command is the same Base Station the handset is currently connected to, according to the invention.
  • FIG. 24 is a schematic block diagram of a system utilizing the methods of the current invention to support mobility of personal data devices as well as wireless handsets, according to the invention.
  • FIG. 1 illustrates the basic components and operation of an exemplary, overall communication system 100 .
  • a Base Station 101 of a cellular system covers a cell 111 having a relatively large coverage area 111 .
  • the Base Station 101 is shown off-center in its coverage area 111 , and the coverage area 111 is shown as elliptical rather than circular, for illustrative clarity.
  • Base Stations 107 , 108 and 109 of a WPBX system cover cells 102 , 103 and 104 , respectively, each having relatively smaller coverage areas.
  • the Base Stations 107 , 108 and 109 are shown off-center in their respective coverage areas 102 , 103 and 104 , for illustrative clarity.) Sometimes, these smaller cells 102 , 103 and 104 are referred to as “microcells”, or “picocells”, or “minicells”.
  • a mobile handset 110 can communicate with the cellular Base Station 101 via a communication link 105 and, when it is in the coverage area of the WPBX, it also can use short-range communication link 106 , to communicate with one of its Base Stations 107 , 108 and 109 .
  • a standard cellular handset 110 that is enhanced (additionally equipped) with a short-range communication link (e.g. Bluetooth wireless technology) can connect with the WPBX system whenever it is in range of one of the WPBX Base Stations 107 , 108 and 109 .
  • the WPBX system can also operate when there is no cellular coverage at all.
  • the handset 110 can be an ordinary cordless telephone handset. Therefore, the cellular Base Station 101 shown in FIG. 1 is optional, insofar as the WPBX system of the present invention is involved.
  • a handset which is an otherwise ordinary cordless telephone handset, equipped with a short-range communication link e.g. Bluetooth wireless link
  • a short-range communication link e.g. Bluetooth wireless link
  • a WPBX system improves availability of employees, who carry mobile handsets, and therefore reduces operational cost and increases productivity.
  • a WPBX system enables the use of the standard cellular handsets instead of special cordless phones.
  • the cost of equipment is lower then the cost of a standard WPBX which requires dedicated handsets. Since the WPBX handles calls between handsets connected to it, the communication charges are lower then when standard cellular communication is used for all the calls.
  • the handset 110 may indicate to the user that more then one service is available.
  • the user decides which service to use (Cellular or WPBX).
  • Cellular or WPBX Cellular or WPBX.
  • the handset 110 is merely an example of a “mobile unit” which can be any of a number of telephony, voice, computing or data devices which communicate via Base Stations, as described in greater detail hereinbelow.
  • Mobile Units are devices communicating wirelessly with (also referred to as “connected to”) Base Stations.
  • the handset 110 is currently communicating with (connected to) the Base Station 108 .
  • the Base Stations 107 and 109 are each referred to as “neighboring” Base Stations since they are each adjacent to the Base Station 108 that the handset is currently connected to.
  • the present invention deals largely with how communication with a Mobile Unit such as a handset is handed off (or passed off) from a one Base Station to another (neighboring) Base Station when the handset moves from one minicell to another minicell.
  • FIG. 2 illustrates the main components and architecture of a WPBX system 200 suitable for use as the WPBX system of FIG. 1.
  • the architecture of a WPBX system generally resembles the architecture of a cellular system. However, as described in greater detail hereinbelow, the function that each component performs is different, since the current invention deals with short-range communication with mobile units that have no built-in support for handoff.
  • the WPBX 200 comprises a plurality (three shown) of Base Stations 123 , 124 , 125 .
  • a handset 121 communicates via a short-range communication link 122 (e.g. Bluetooth wireless link) with Base Station # 1 123 .
  • Base Station # 2 124 and Base Station # 3 125 are ready to receive the call should handset 121 move into their coverage area.
  • the other Base Stations may participate in calls with other handsets.
  • Base Station # 2 124 communicates via a short-range communication link 134 (e.g. Bluetooth wireless link) with a handset 133 .
  • the handsets 121 and 133 may communicate with each other via the WPBX (as opposed to directly with one another), as described in greater detail hereinbelow.
  • Communication links 126 , 127 , 128 connect the Base Stations 123 , 124 , 125 with one another, as illustrated. These communications links transfer data between the Base Stations 123 , 124 , 125 , including voice communication, data communication, connection status information and synchronization information, as described in greater detail hereinbelow, and may be RF links or land lines (e.g., copper wires, optical fibers, etc.).
  • Communication links 130 , 131 , 132 connect the Base Stations 123 , 124 , 125 , respectively, with a Central Switch (hereinafter “Switch”) 129 .
  • Switch Central Switch
  • These communication links enable the Switch 129 to control the operation of the Base Stations and to participate in the higher levels of the communication protocols, as described in greater detail hereinbelow, and may be RF links or land lines.
  • FIG. 3A illustrates the addition of a Gateway 135 to the WPBX system 200 of FIG. 2.
  • the Gateway 135 connects the Switch 129 to a Public Switched Telephone Network (PSTN) 136 .
  • PSTN Public Switched Telephone Network
  • the Gateway 135 may be implemented in any suitable manner, such as in hardware and/or software.
  • a “Gateway” is a logical or physical connection between two different communication networks.
  • the term implies a need for conversion of some aspect of the information or communication in order to operate, as contrasted with a “port” which implies a point not requiring significant conversion of the message or information. Gateways are well known.
  • FIG. 3B illustrates the addition of a Gateway 137 to the WPBX system 200 of FIG. 2.
  • the Gateway 137 connects the Switch 129 to a standard Private Branch Exchange (PBX) 138 .
  • PBX Private Branch Exchange
  • the PBX 138 is interfaced with the PSTN 136 .
  • the WPBX system 200 can also communicate with other telecommunication systems (not shown) which are connected to the PSTN.
  • FIG. 4 illustrates a plurality (three shown) of Base Stations 123 , 124 and 125 (compare FIG. 2) connected via a communications link which is a Local Area Network (LAN) 140 which handles the transfer of information between the Base Stations 123 , 124 , and 125 , the Switch 129 and, in this example, the Gateway 135 to the PSTN 136 .
  • LAN Local Area Network
  • Using a standard local area network (LAN) as the communication backbone allows simple integration with other telephony application servers (not shown), such as IVR (interactive voice response), voice loggers, voice mail and billing systems.
  • the LAN 140 can be either wired, or wireless.
  • FIGS. 2, 3A, 3 B and 4 therefore illustrate, in a general manner, a number of ways in which the main components of a WPBX can be connected with one another, and interfaced with other communications systems (PSTN, PBX, etc.)
  • PSTN public switched telephone network
  • PBX public switched telephone network
  • the Switch 129 may be a standard computer that has the processing power required for handling the switching of hundreds of calls simultaneously. It should support operation in a multi-server environment. This can be achieved with standard server hardware.
  • the Switch 129 may be a part of one Base Station, or a part of several Base Stations.
  • FIGS. 5, 6 and 7 illustrate call setup procedures for a single call at an “originating” Base Station (e.g., 123 ), at a “receiving” Base Station (e.g., 124 ), and at the Switch (e.g., 129 ), respectively.
  • Call setup between the handset (e.g., 121 ) and the Base Station it is connected to (e.g., 123 ) is suitably performed according to standard telephony protocols, for example ITU-T Q.931.
  • a similar protocol is a part of the Bluetooth protocol stack.
  • the present invention is not limited to a specific protocol for call setup.
  • FIG. 5 illustrates a call setup procedure performed by an originating Base Station (e.g. 123 ) when a handset (e.g., 121 ) that is connected to it, tries to initiate a call.
  • the handset that is originating the call sends a destination number (DN).
  • the originating Base Station e.g., 123
  • the originating Base Station e.g., 123
  • the destination handset e.g., 133
  • Base Station Connection Table in other words, whether the destination handset is in the originating Base Station's coverage area.
  • step 160 the destination number (DN) is sent via the communications link (e.g., LAN 140 ) to the central WPBX Switch (e.g., 129 ).
  • the originating Base Station sets a timeout (step 161 ), and waits for a reply from the Switch.
  • the timeout set in the step 161 is suitably on the order of up to 5 seconds.
  • step 162 If there is a timeout (step 162 , “Y”), the Base Station sends a busy indication (suitably a tone) to the originating handset (step 177 ), and the Switch is updated about the failure of the call (step 178 ). If, there is not a timeout (step 162 , “N”), the originating Base Station receives (from the Switch) the address of a destination Base Station (step 163 ). The originating Base Station then calls the destination Base Station (step 164 ), and it also calls all the neighbors (neighboring Base Stations) of the destination Base Station (step 180 ). Then the originating Base Station sets a timeout (step 165 ) and waits for a reply from the called Base Station (and its neighbors). Calling more then one destination Base Station is preferred in order to overcome uncertainties during handoff. The timeout set in the step 165 is suitably on the order of up to 5 seconds. Next, it is determined in a step 166 whether there is a timeout.
  • step 166 If there is a timeout (step 166 , “Y”), the Base Station sends a busy tone to the originating handset (step 177 ), and the Switch is updated about the failure of the call (step 178 ). If, there is not a timeout (step 166 , “N”), and a reply from the destination Base Station is received, the originating Base Station checks if the call is connected (step 167 ), and then connects the originating handset (step 168 ), and updates the Switch about the success of the call (step 169 ).
  • step 163 If, in the step 163 the address of a destination Base Station is not received (N), it is determined (step 170 ) whether the destination of the call is the Switch itself. If so (step 170 , “Y”), a procedure similar to that for sending a call to another Base Station is implemented, except that the call is sent to the Switch (step 171 ) and not to another Base Station. Then the originating Base Station sets a timeout (step 172 ) and waits for the Switch to reply (step 173 ). The timeout is suitably on the order of up to 5 seconds. Next, it is determined in the step 173 whether there is a timeout.
  • step 173 , “Y” If there is a timeout (step 173 , “Y”), the Base Station sends a busy tone to the originating handset (step 177 ), and the Switch is updated about the failure of the call (step 178 ). If the Switch responds that the call is connected, there is not a timeout (step 173 , “N”), and the originating Base Station connects the handset (step 175 ), and updates the Switch (step 176 ) about the status of the call.
  • step 152 If it is determined that the destination handset is in the originating Base Station's coverage area (step 152 , “Y”), and a busy signal is not returned (step 153 , “N”), the originating Base Station then attempts (step 154 ) to connect the call to the destination handset, and also to all the neighboring Base Stations (step 181 ). Again, the calling of neighboring Base Stations is preferred in order to overcome uncertainties, such as the handset moving, during the call setup.
  • the originating Base Station performs a procedure similar to that described hereinabove of setting a timeout (step 155 ), waiting for the Switch to reply (step 156 ), connecting (step 158 ) or disconnecting (step 177 ) the call, and updating the Switch (steps 159 or 178 ).
  • the call setup procedure performed by an originating Base Station is that, first, the originating Base Station determines whether a call request from an originating handset (e.g., 121 ) is:
  • step 181 a. to a DN in the originating Base Station's coverage area (e.g., step 152 ), in which case the originating Base Station attempts (step 181 ) to also connect the call to its neighboring Base Stations; or
  • step 164 a Base Station's coverage area
  • the originating Base Station attempts (step 180 ) to also connect the call to Base Stations which are neighbors of the destination Base Station;
  • step 179 waits (step 179 ) for a new event (a new call setup).
  • FIG. 6 illustrates the call setup procedure performed at a destination Base Station (e.g., 124 ) which is receiving a call, whether it be from another Base Station or from the Switch.
  • a destination Base Station receives a request (step 201 ) to connect a call to a handset (e.g., 133 ) which is reportedly within its coverage area
  • a handset e.g., 133
  • it first checks (step 202 ) whether the handset is already communicating with (connected to) it. If the handset is already connected to the Base Station (step 202 , “Y”), the Base Station tries to connect the call to the handset.
  • a timeout is set (step 203 ), again on the order of up to 5 seconds, and the Base Station waits (step 204 ).
  • step 204 If a time-out occurs (step 204 , “Y”), or if a timeout does not occur (step 204 , “N”) but the call was unable to connect (step 205 , “N”), the destination Base Station returns an indication (step 208 ) of call setup failure (“unable to connect”) to the originating Base Station (or to the Switch, as the case may be). If, however, the connection succeeds (step 205 , “Y”) the Base Station returns an indication (step 206 ) of successful call setup (“call connected”) to the originating Base Station.
  • the destination Base Station sends similar indications (steps 211 , 212 , respectively) to all the neighboring Base Stations of the originating Base Station Again, sending the reply to the neighboring Base Stations is to overcome uncertainties during handoff. In both cases the Switch is updated at steps 207 and 209 , respectively. Finally the Base Station waits (step 210 ) for a new event (a new call setup).
  • FIG. 7 illustrates the call setup procedure performed at the Switch (e.g., 129 ).
  • the Switch handles two types of messages, one is a request to establish a new call, and the other is an update to the status of the call.
  • a step 231 it is determined whether the request is for a new call (step 231 , “Y”) or a request to update a call (step 231 , “N”).
  • step 231 If the arriving message is a request to update a call (step 231 , “N”), an update of the “Calls Table” is generally required (step 254 , “Y”).
  • the Switch checks if it receives indication that the call is connected (step 255 ). If the call is connected, (step 255 , “Y”), the status of the call is updated in the Calls Table (step 256 ). Otherwise (step 255 , “N”), the call is removed from the Calls Table (step 257 ).
  • the Switch checks if the call is intended to a handset connected to the WPBX (step 232 ). This is done by checking its “Connections Table”. If the call is intended to connect to outside the WPBX (e.g., via the PSTN 136 ), the Switch checks (step 233 ) if the destination number (DN) is a legal (valid) number. If the DN is a valid number (step 233 , “Y”), in a step 234 the Switch transfers the call to the Gateway (e.g., 135 ), sets a timeout (step 235 ) and waits (step 236 ). If not (step 233 , “N”), the program exits.
  • step 236 it is whether the call is connected determined (step 237 ). If the call is connected, (step 237 , “Y”), the Switch requests from the originating Base Station to transfer the call to the Switch (step 238 ), and waits for connection with originating Base Station (steps 239 , 240 ). If connection succeeds, and the call is connected (step 242 , “Y”), the call is added to the “Calls Table” (step 243 ), and the call is routed to the Gateway (step 244 ). If connection fails (step 240 , “Y”; or step 242 , “N”), the connection with the Gateway is disconnected (step 241 ).
  • the call destination is one of the Base Stations (step 259 ), its source may be another Base Station (step 249 ), or the Gateway (step 245 ). If the source is another Base Station, the Switch send to the originating Base Station the address of the destination Base Station, and adds the call to the “Calls Table”. If the call arrived from the Gateway the Switch tries to connect the call to the destination Base Station (step 245 ). If is succeeds the call is added to the “Calls Table” (step 252 ), the call is transferred to the destination (step 253 ). If it fails the connection with the Gateway is disconnected.
  • the procedure described in FIG. 7 is also applicable to the case when more than one Gateway connects to the WPBX to the PSTN—for example, in a case where two branch offices share a single WPBX, and each has its own independent connection to the PSTN.
  • the main difference would be that when the Switch handles an outgoing call, it will determine to which Gateway to send the call. This can either be done randomly, or can be pre-determined. The handling of the incoming calls would proceed as set forth above in FIG. 7.
  • FIGS. 5, 6 and 7 have illustrated a call setup procedure for the handling of a single call.
  • both Base Station software and Switch software are preferably based on a real time operating system that supports multi-tasking. For each new call, a new task will be created, and the task will perform the procedures described in FIGS. 5, 6 and 7 . The task will be closed when the procedure is completed.
  • FIG. 22 illustrates the division of the Base Stations, into two groups; a first group (Group A) 1050 comprising a plurality (four shown) of Base Stations 1050 a, 1050 b, 1050 c and 1050 d; and a second group (Group B) 1051 comprising a plurality (four shown) of Base Stations 1051 a, 1051 b, 1051 c, 1051 d.
  • the Base Stations of Group A are connected to a first Switch (Switch A) 1052
  • the Base Stations of Group B are connected to a second Switch (Switch B) 1053 .
  • the Base Stations and the Switches function according to the procedures described in FIGS. 5, 6 and 7 .
  • All the Switches mirror all the status tables of the other Switches, i.e. by having copies of each other's “Calls Table” and “Connections Table”.
  • a Switch updates one of its status tables, it sends the information to all the other Switches, and they update their tables accordingly.
  • the other Switches will send an indication that the message was received. If the originating Switch does not receive such a reply within T 1 milliseconds, it will retransmit the message. The retransmission will be repeated up to P times. For example T 1 shall be equal to 100, and P shall be equal to 5.
  • Switches 1052 and 1053 are intended to be exemplary rather than limiting.
  • the Switch maintains the “Calls Table”, which contains the status and information about all the active calls being handled by the WPBX.
  • the “Calls Table” comprises the following information:
  • Each active call has a unique “Call Identification number”.
  • the “Originating Base Station Identification” and the “Destination Base Station Identification” are updated when a handset moves from one Base Station to another.
  • the Switch updates these fields when it determines that the handoff should occur. During handoff, for a short time, there may be uncertainty about the validity of these fields.
  • the Base Stations compensate for the uncertainty by “multicasting” the call setup messages to a group of Base Stations, as described hereinabove with respect to FIGS. 5 and 6 (see, e.g., steps 180 , 181 , 211 , 212 ).
  • the procedures described above do not limit the WPBX from handling all unique telephony features that the Gateway and the handsets can support. For example, multiple connections can be created between handsets, and between handsets and the Gateway, when each connection is treated as a separate call. Another example is “Caller ID”, that the Gateway can send to a handset. Another example is a “Hook-Flash” (momentary disconnect) that the handset can pass to the Gateway.
  • the WPBX acts as a transparent relay for all these telephony features.
  • Each Base Station knows which handsets are in its coverage range.
  • the short-range communication protocol stack is divided into two parts:
  • the low-level protocols are the radio frequency (RF) transmitter and the base-band controller.
  • the base-band controller performs real time control over the RF, since the Bluetooth protocol utilizes frequency-hopping transmission.
  • the base-band protocol also determines, for each time slot of transmission (i.e. each frequency hop), what information will be transmitted.
  • the base-band protocol also deals with voice coding, error correction, encryption and authentication.
  • higher level protocols of the Bluetooth stack include the “Link Manager” which determines what information will go through the channels created by the “Base-Band”, and determines the state of operation (e.g. Active, Polling, Parked).
  • the low-level protocols that require real time capabilities are performed in the Base Station.
  • the higher-level protocols are performed at the Switch. (However, as described hereinbelow, certain high-level protocols can also be performed in the Base Station, even though they do not require real time capabilities.)
  • the Switch handles the routing of data from the higher-level protocols to the lower level protocols. (A call routing task ( 282 ) is described in greater detail hereinbelow.) Therefore, the higher-level protocols do not need to “know” in which Base Station the lower level protocol that they are controlling is being performed.
  • FIGS. 8A and 8B illustrate an example of a WPBX system 800 with two handsets 121 and 133 , two Base Stations 123 and 124 , and one Switch 129 .
  • two calls are being handled.
  • Gateways e.g., 135 , 137
  • the Switch can be divided into several units.
  • the handset 121 is currently communicating with (connected to) the Base Station 123 , and the handset 133 is currently communicating with the Base Station 124 .
  • An instance 280 of the low-level protocol is running on the Base Station 123
  • another instance 281 of the low-level protocol is running on the Base Station 124 .
  • Each instance of the low-level protocol supports only one call.
  • the Switch 129 handles an instance 283 of the high-level protocol for the call with the with the handset 121 , and another instance 284 of the high-level protocol for the call with the handset 133 .
  • a single call routing task 282 handles the data that is transferred between the instances of the low-level protocols and the high-level protocols to the correct destination.
  • the call routing task 282 routes data arriving from instance 280 of the low-level protocol to instance 283 of the high-level protocol, and from the instance 281 of the low-level protocol to the instance 284 of the high-level protocol. Since interaction between the high-level-protocol and low-level protocol, is normally relatively rare (e.g. call setup), there are no strict real time requirements from the call routing task.
  • the call routing task 282 is described in greater detail hereinbelow, with respect to FIG. 12.
  • the handset 133 is shown as having moved to the area covered by the Base Station 123 .
  • the Base Station 123 will handle the communication with the handset 133 , by creating a copy 281 ′ of the instance 281 of the low-level protocol, that previously ran on Base Station 124 . This allows the handset 133 to continue communication without “knowing” that a changeover of Base Stations has occurred.
  • the call routing task 282 will now route the data arriving from the instance 281 ′ of the low-level protocol running on Base Station 123 to the instance 284 of the high-level protocol 284 which is running on the Switch 129 .
  • the handsets do not need to be (and preferably are not) specially equipped or enabled to support mobility (i.e. handoff). Therefore, when a handset moves from one Base Station to another, the current and the next Base Stations are responsible for continuing the communication with the handset, preferably with no noticeable interruption in the communication, and the next Base Station to which the handset has moved should transmit substantially exactly as the previous Base Station from which the handset has moved would have transmitted. For purposes of the discussion of this example, it is assumed that it is known from which Base Station the handset has moved and to which Base Station the handset is moving, and that the exact timing of handoff is also known. These issues are discussed in greater detail hereinbelow.
  • FIGS. 9A, 9B and 9 C illustrate, in a general manner, a handoff taking place between two Base Stations 123 , 124 and a single handset 121 of a WPBX.
  • FIG. 9A illustrates the handset 121 communicating with (connected to) a Base Station (Base Station # 1 ) 123 via a short-range communication link 122 (e.g. Bluetooth wireless link).
  • the “current” Base Station 123 sends call parameters and rough synchronization information over the LAN 140 to the neighboring Base Stations, a one of which is shown as Base Station # 2 124 .
  • the neighboring Base Stations “know” that they are “candidate” Base Stations for receiving a handoff of the call from the current Base Station.
  • the information which is broadcast by the current Base Station to the candidate next Base Stations includes low-level communications protocol states and parameters, discussed in greater detail hereinbelow.
  • This communication from the Base Station 123 to the Base Stations 124 is indicated by the arrow 141 , and the information contained therein is used to achieve rough (coarse) synchronization between the Base Stations. Since this information does not need to be accurate in time, it can be transmitted over the data link (e.g., LAN 140 ) connecting all of the Base Stations.
  • the data link e.g., LAN 140
  • FIG. 9B illustrates a handoff as it is about to take place.
  • the handset 121 is situated in an area covered by both Base Stations 123 and 124 .
  • Base Station 124 uses this situation to achieve exact (fine) synchronization with the current Base Station 123 . This will enable the next Base Station 124 to transmit, after the handoff, substantially exactly as previous Base Station 123 would have transmitted if the handoff had not occurred.
  • a method for effecting this fine synchronization between neighboring Base Stations is discussed in greater detail hereinbelow.
  • Time Of Day (TOD), which can be determined with virtually any desired level of precision (e.g., microseconds).
  • TOD Time Of Day
  • the Base Station 124 that is waiting for the handset 121 may passively monitor the transmissions of either the handset 121 , or of the Base Station 123 that is currently connected with the handset.
  • FIG. 9B the two possible fine synchronization signals that the candidate next Base Station # 2 124 can monitor are shown, a signal 142 originating from the Base Station # 1 123 , and another signal 143 originating from the handset 121 .
  • FIG. 9C illustrates that synchronization of the Base Stations 123 and 124 may alternatively be achieved by use of a beacon signal from a beacon transmitter 299 which is within range of current and next Base Stations, in which case precise (fine) synchronization for the low-level protocols can also be achieved.
  • the beacon transmitter 299 transmits a beacon signal 144 to both of the Base Stations 123 and 124 to achieve synchronization of the Base Stations.
  • This method allows for the synchronization of many Base Stations, although only two are illustrated in this figure. In this case, there is no need to transmit synchronization information over the LAN 140 . Only call parameters (e.g., low-level protocol) need to be communicated between the current Base Station and the neighboring candidate next Base Stations, as indicated by the arrow 141 ′.
  • a short-range communication protocol with the handset can be divided into lower-level protocols which the Base Stations handle, since they have real time requirements, and higher-level protocols which the Switch handles since they do not require real time requirements.
  • Bluetooth wireless technology is an example of such a short-range communication protocol.
  • Table 1 a division of the Bluetooth short range wireless protocol into such low-level and high-level protocols is presented.
  • TABLE 1 Communication Protocols Element Description of Protocol Real time Level/ (Protocol Name) (Bluetooth Protocol) requirements Where Radio Frequency Defines the modulation scheme Control of radio Low/ (RF) and the frequency range frequency in real Base Station time required, modulates each symbol Base-band Frequency control, channel Control frequency Low/ definition, transmission/ hopping in real time.
  • Base Station reception control encryption, Determines what error correction, authentication. packet will be sent at each hop. Encryption/Error correction for each hop.
  • Table 1 shows the elements of the Bluetooth protocol, generally, as currently implemented. Other profiles may be added in the future (or may have already been added), and it is anticipated that these profiles will be high-level protocols, which do not have strict real time requirements.
  • the Link Manager and the Host Controller Interface can be implemented in either the Base Station or in the Switch. Although the Link Manager and Host Controller Interface, do not require real time performance, they may readily be implemented in the base-band controller of the Base-Station. It is within the scope of the invention that any of the high-level protocols can also be implemented in the Base Station as part of the low-level protocol, but then they will take part in the handoff.
  • the high-level protocols are “buffered” from the occurrence of handoff by the Base Stations and the routing task that runs on the Switch. Therefore, the present invention allows mobility of any device with Bluetooth wireless technology that supports any of the high-level protocols (e.g. LAN access, WAP, FAX, FTP).
  • LAN access e.g. LAN access, WAP, FAX, FTP.
  • WAP Wireless Fidelity
  • FAX Wireless FTP
  • Rough synchronization may be achieved via the local area network (see, e.g., LAN 140 , FIGS. 9A and 9B) connecting the Base Stations. Fine synchronization may be achieved by other methods described in greater detail hereinbelow.
  • TABLE 2 Low-Level Protocol Synchronization Element/ Synchronization Parameter Description method device address The unique address of the Base Station, Via LAN determines the hopping sequence, effects the encryption and authentication keys.
  • All the parameters listed in Table 2, except for the TOD, can be sent prior to handoff, thorough the local area network (e.g., LAN 140 ), or any other communication link connecting the Base Stations. As described hereinabove with respect to FIG. 9A, rough (coarse) TOD can also be sent through the LAN.
  • LAN 140 local area network
  • rough (coarse) TOD can also be sent through the LAN.
  • one of the other parts of the Bluetooth protocol stack is also implemented in the Base Station, then it will also take part in the handoff. Synchronizing the instances of the same protocols in different Base Stations is done as described above, by sending internal state parameters via the local area network (LAN 140 ). For example, by implementing the Link Manager and Host Controller Interface in the Base Station, the internal state parameters of these protocols will be broadcast to the neighboring Base Stations, by the Base Station that is connected to the handset.
  • LAN 140 local area network
  • the Base Station that is waiting for the handset should passively monitor the transmission of the handset and/or the Base Station that is currently connected with the handset.
  • FIG. 9B the two possible signals that the receiving (next) Base Station 124 can monitor are shown, one originating from Base Station 123 , and the other originating from the handset 121 which is currently connected to the Base Station 123 .
  • the next Base Station 124 can be finely synchronized by receiving synchronization signals from the current Base Station 123 .
  • the Base Station 124 does not receive signals from the Base Station 123 . Therefore, to facilitate the Base Station 124 receiving synchronization signals from the Base Station 123 , Base Station 123 periodically transmits with higher transmission power than during normal transmission. This allows the Base Station 124 to receive transmissions from Base Station 123 , without a substantial increase in spectral contamination.
  • the inventive technique is described in the context of frequency-hopping. Frequency-hopping techniques are well known, including techniques that change frequency with each hop.
  • FIG. 10 illustrates a technique for controlling the transmission power of a Base Station (e.g., 123 ) that is currently connected with the handset, for a plurality (series) of successive hops 290 .
  • the vertical axis of the graph is the Base Station's transmission power (in arbitrary units), and the horizontal axis is time.
  • T h is the duration of a hop 290 .
  • the hops 290 all have equal duration.
  • Tp is the time interval between successive hops (or “hop time slot”) and, in this example, the intervals between successive hops are constant (evenly spaced in time).
  • the normal transmission power for each hop 290 is P 0 .
  • the normal transmission power P 0 of a Base Station is suitably on the order of a hundreds of milliwatts.
  • every Kth hop 290 ′ is a “synchronization” hop that is transmitted with increased power P 1 .
  • P 1 is suitably substantially (e.g., 2-10 times) greater than P 0 .
  • every Kth (synchronization) hop will also be transmitted at a different frequency.
  • a variable time interval is provided between the synchronization hops 290 ′ that are transmitted with high power P 1 .
  • K that shall be denoted by K(n), i.e. K for hop number ‘n’
  • K(n) can be generated by a pseudo random sequence such as a maximal length shift register sequence. Pseudo random sequences are well known for use in communication systems.
  • a beacon transmitter e.g., 299
  • K can either be constant or it can be changed over time (variable), as described above.
  • FIG. 11 illustrates major components of a Base Station 1100 waiting for handoff, and a method of accurately synchronizing the TOD at the Base Station to the TOD of the Base Station which the handset is about to leave, including:
  • Antenna 301 [0171] Antenna 301 ;
  • Frequency Hopping Generator 304
  • Emulator 307 [0174]
  • a rough TOD from the Base Station currently connected with the handset is available to the (next) Base Station waiting for a handoff on a communication link such as the LAN 140 .
  • This rough TOD is provided to the TOD counter 303 (e.g., via an interface to the LAN 140 ).
  • a Time Clock 310 generates clock signals for incrementing the TOD counter 303 .
  • the output of the TOD counter 303 is therefore a rough estimate of the TOD (“TOD Estimate”).
  • TOD Estimate There is an uncertainty (margin of error) “Tu” between the rough estimate of TOD and the actual TOD, and which depends on the transmission latencies thorough the LAN 140 . “Tu” is readily calculated for a given WPBX system, according to its physical configuration.
  • a frequency-hopping list is generated by a frequency-hopping generator 304 and supplied to an emulator 307 which emulates the output of the receiver 305 .
  • a window with size of 2 ⁇ T u a single frequency from the hopping sequence is chosen, and the receiver 305 will wait on this frequency for duration of 2 ⁇ T u .
  • the receiver 305 will switch frequency, in response to a signal generated by the frequency-hopping generator 304 . Opening an acquisition window of 2 ⁇ T u ensures that during this time duration the receiver 305 will capture at least one hop.
  • a correlator/detector 308 receives the receiver's output (e.g. a base-band or intermediate frequency signal) and an emulation 307 of the signal that should appear at the receiver's output.
  • the output of the receiver 305 can be emulated, since a rough estimate of the TOD is available, and also from the hopping frequency list, and the receiver frequency list.
  • the emulator 307 continuously checks for a match between receiver frequency and the hopping frequency and, when it finds a match, it reports the frequency and the time (rough TOD) to the correlator/detector 308 .
  • the correlator 308 computes (and outputs) a fine estimate of the TOD offset (i.e., the error between the TOD estimate and the actual TOD), and provides this to Adder 309 , which also receives the rough TOD estimate from the TOD counter 303 and generates a signal (“Fine TOD”) indicative of the actual TOD.
  • Correlator-based time offset measurement is a standard estimation method that is described in many textbooks, and an example of its implementation is described in greater detail hereinbelow.
  • the Base Station to which the call is to be handed “knows” which call it is going to receive, and it has received the call parameter (via the LAN), and is able to accurately estimate the TOD, it will be able to perform a seamless handoff transmitting substantially exactly as the Base Station that the handset is about to leave.
  • an iteration of the low-level protocol e.g., 281 ′
  • the higher-level protocols are run at the Switch, and are therefore “ignorant” of the handoff processes.
  • the “call routing task” 282 (FIGS. 8A, 8B) isolates the high-level protocols from the changing environment.
  • the “call routing task” 282 maintains the “Connections Table”, which contains information about all the connections between handsets and Base Stations. Maintaining the Connections Table is described in greater detail hereinbelow. The following sections describe an example of how the Connections Table is used by the “call routing task” 282 .
  • FIG. 12 illustrates a method of implementing the “call routing task” 282 which was mentioned hereinabove with respect to FIG. 9A.
  • the “call routing task” 282 is performed in the Switch 129 .
  • the call routing task 282 waits for a message from one of the high-level protocol instances running on the Switch 129 or from one of the low-level protocol instances running on the Base Stations (e.g., 123 ). Then, in a step 352 , it is determined where the call came from.
  • step 352 If the message arrived from one of the Base Stations (step 352 , “Y”), the call parameters are compared with the Connections Table (step 353 ) and the message is sent (step 354 ) to the instance of the high-level protocol running on the Switch ( 129 ).
  • step 352 , “N” If the message arrived from the Switch (step 352 , “N”) the ID of the sending low-level protocol instance is located (step 353 ) in the “Connections Table”, and the message is sent (step 354 ) to an instance of a corresponding high-level protocol. If the message arrived from one of the high-level protocols (step 352 , “N”), it is determined (step 360 ) whether a handoff has begun (is in progress). If a handoff is not in progress (step 360 , “N”), the call parameters are compared with the Connections Table (step 358 ) and the message is sent to the Base Station on which the destination low-level protocol instance is running (step 359 ).
  • step 360 the call parameters are compared with the Connections Table (step 355 ) and the message is sent to the Base Station on which the destination low-level protocol instance is running (step 356 ). The message is also sent (step 357 ) to all the Base Stations that are candidates for handoff—e.g., neighboring Base Stations. The Base Stations receiving the message can then check if they are running the destination low-level protocol and, if not, the message is simply discarded.
  • the procedure shown in FIG. 12 handles a single message. By using a multi-tasking operating system, it is possible to run several instances of these procedures, and thus handle more than one message simultaneously.
  • the methods described thus far enable the communication protocols to continue operation when a handoff occurs. They rely on the ability to determine, which handset is in the coverage area of which Base Station, where a handset is moving, and when is the best time to perform handoff. By definition, handoff occurs between only two Base Stations, but for a certain time prior to the actual occurrence of the handoff there may be more than one Base Station that are candidates for handoff. Determining the candidates for handoff, which Base Station will actually participate in handoff and when to perform handoff requires collaboration of the Base Stations and the Switch.
  • the Base Stations will determine which handsets are in their coverage range, by either passively capturing transmission information, or by “tricking” the handset to transmit information that can be used for that purpose.
  • each Base Station will transmit, to all the neighboring Base Stations, information about the calls that are taking place in its coverage area.
  • This information will include all the call parameters that can be sent through a low bandwidth communication link, such as the shared local area network (e.g., LAN 140 ). This information is sufficient for detecting which handset is moving from one of the neighboring Base Stations into the coverage area of a Base Station.
  • FIG. 13 illustrates major components of a Base Station 1300 , waiting for handoff, and a method of accurately synchronizing the TOD at the Base Station to the TOD of the Base Station, which the handset is about to leave, and a passive method for detecting the arrival of a handset in a Base Station's coverage area during a call, including:
  • Antenna 382 (compare 301 );
  • Receiver 379 (compare 305 );
  • a Receiver Frequency Controller 375 A Receiver Frequency Controller 375 ;
  • FIG. 13 illustrates a passive method for determining which handsets' (i.e. handset which is participating in a call with a certain device address) transmissions is being received by a Base Station.
  • a plurality (“K”, three shown) of TOD counters 371 , 380 and 384 are set when a rough TOD (“Rough TOD”) estimate is received, via the LAN ( 140 ), from other Base Stations.
  • the counters 371 , 380 and 384 are incremented by the TOD clock 310 .
  • a corresponding plurality (“K”, three shown) of hopping frequency (sequence) generators 372 , 373 , 374 generate the list of frequencies in which the handsets are likely to transmit.
  • the receiver frequency controller 375 sets the frequency, which the receiver 379 will monitor.
  • a plurality (“K”, three shown) of correlators 381 , 382 and 383 is used to compare the energy at the receiver's output, to the emulation of the receiver's output.
  • the output of the receiver can be emulated, since a rough estimate of the TOD is available, as well as the hopping frequency list, and the receiver frequency list.
  • the emulator continuously checks for a match between receiver frequency and the hopping frequency, when it finds the match it reports to the correlator the frequency and the time.
  • the correlator By comparing the actual received signal with the emulation that is based on the rough TOD, the correlator detect the presence of the transmitter and computes a fine estimate of the TOD offset (i.e., the error between the rough TOD estimate and the actual TOD). Correlator-based time offset measurement is a standard estimation method that is described in many textbooks, example of implementation shall be described later on.
  • the number of handsets that can be detected simultaneously is equal to the number of hopping sequence generators, and the number of emulators of receiver output, and the number of correlators.
  • the receiver frequency controller 375 selects the frequency on which the receiver 379 will wait to “capture” hops. To increase the probability of detection, the receiver frequency controller 375 should be programmed to choose frequencies that are not blocked by interferences (e.g., interferences from other than Bluetooth transmitters). For each frequency that the receiver frequency controller 375 chooses, a histogram of the number of hops that have been detected in a certain duration of time, and their average signal-to-noise ratios are maintained by the receiver frequency controller 375 .
  • interferences e.g., interferences from other than Bluetooth transmitters
  • a measure of the spectral “cleanness” of a certain frequency can be determined as a function of the signal-to-noise ratios (SNRs) of the hops—for example, as the number of hops multiplied by the average signal-to-noise ratios (SNRs) of the hops.
  • SNRs signal-to-noise ratios
  • the receiver frequency controller 375 preferably chooses a group of ‘M’ frequencies that have the best “cleanness” measure, and the receiver 379 waits on them most of the time, when once in T1 milliseconds the controller changes the frequency. Once in T2 milliseconds (T2 is selected to be much larger then T1) the receiver frequency controller 375 selects a frequency which is not in the group of ‘M’ best, and the receiver 379 waits on it for T3 milliseconds (T3 is selected to be smaller then T1). This enables the receiver frequency controller 375 to monitor the “cleanness” of frequencies that are not in the ‘M’ best frequencies.
  • the receiver frequency controller 375 detects a frequency that is cleaner then one of the ‘M’ frequencies that is in its list, it puts it in the list, instead of the frequency with the lowest “cleanness” measure.
  • Typical values for the parameters M, T1, T2, T3 are 20, 250, 2500, 100, respectively.
  • the signal-to-noise ratio (SNR) or signal-to-interference ratio for each hop is measured by measuring the bursts of energy which match the expected hop duration, to all other signals that do not match the hop duration.
  • the average noise level is continuously monitored.
  • Th is the nominal hop duration; D is a measurement “window” interval
  • the hop energy will be computed, and it will be added to the average hop energy.
  • the average noise level is not be updated.
  • Typical values for Th and D are 0.65 milliseconds, and 1000 milliseconds respectively.
  • the neighboring Base Station(s) In order for the handset to receive their transmission, the neighboring Base Station(s) must therefore be synchronized with the Base Station that is currently communicating with the handset, and during the time that the neighboring Base Station(s) transmits, it (they) acts as if it were the Base Station that has yielded a transmission slot for handset detection by the neighboring Base Stations.
  • This method can be illustrated in the context of the Bluetooth short-range communication, wherein frequency hopping is used.
  • the Base Station that is currently communicating with the handset will give up a single hop. Any of the neighboring Base Stations that are not close to each other may use the same hop to transmit to the handset. The neighboring Base Stations that are close to each other will use different hops to call (communicate with) the handset. This is illustrated in FIGS. 14A, 14B, 14 C and 14 D.
  • FIG. 14A which is similar to FIG. 1, illustrates a wireless communication system 1400 (e.g., WPBX) having a Base Station 391 that is currently communicating with a mobile unit 390 that is a wireless telephone handset, and a plurality (six shown) of neighboring Base Stations 392 , 393 , 394 , 395 , 396 and 397 that are waiting (available) for the handset 390 to enter their coverage areas.
  • Each Base Station 391 , 392 , 393 , 394 , 395 , 396 and 397 has an area of coverage 391 a, 392 a, 393 a, 394 a, 395 a, 396 a and 397 a, respectively.
  • the interconnections between the Base Stations, and between the Base Stations and a central Switch, such as shown in FIGS. 2 and 4, are omitted, for illustrative clarity.
  • FIG. 14B which is similar to FIG. 10, illustrates that the Base Station 391 which is currently communicating with the handset 390 , periodically (once in K hops) transmits with higher power P 1 , in order to enable the neighboring Base Stations to synchronize their TOD.
  • the Base Station 391 also periodically (once in M hops) skips a transmission on a single hop 702 , 703 (shown as dashed lines) in order to allow the neighboring Base Stations 392 , 393 , 394 , 395 , 396 and 397 to transmit at these times.
  • a single hop 702 , 703 shown as dashed lines
  • three of the neighboring Base Stations 393 , 395 , 397 transmit on even-numbered skipped hops 705 .
  • the other three of the neighboring Base Stations 392 , 394 , 396 transmit on odd-numbered skipped hops 707 .
  • the neighboring Base Stations 392 , 393 , 394 , 395 , 396 and 397 may transmit normally to other handsets (not shown) to which they are connected.
  • the Base Station that is communicating with the handset sends the call parameters to neighboring Base Stations via the local area network (LAN 140 ) that connects all of the Base Stations. It will also send information regarding the timing of hops that they may use to call handsets that it is communicating with.
  • the neighboring Base Stations can synchronize the TOD. According to the timing of the hops received with high energy (P 1 ), the Base Stations that wait for the call, can determine the times in which they are allowed to try to call the handset. In these times the Base Stations transmit to all handsets that are communicating with neighboring Base Stations.
  • the handsets do not need to have a mechanism for supporting (actively participating in) handoff, they preferably have a mechanism that allows checking whether their communication links are operating normally. For example, in the Bluetooth short-range communication link, a “PING” command that is sent on the asynchronous link is used to check whether the data communication link is operative. When the handset receives a “PING” command it will automatically respond with an “ECHO” message (response). Since the “PING” command is sent on an asynchronous link, and not the synchronous link that is used for voice communication, in does not disrupt the voice quality, but only slightly (and temporarily) reduces the available bandwidth for data transfer.
  • the “PING” command includes the following data fields:
  • the “ECHO” response includes the:
  • the “PING” command and “ECHO” response are used by a Base Station in order to determine whether a certain handset has entered its coverage area. Unlike the methods of passively detecting the handset presence, discussed hereinabove, this method allows detection of a Base Station that was not actively engaged in a call at the time of handoff. It is enough for the handset to have only created an initial communication with a Base Station.
  • FIGS. 15A and 15B illustrate the use of “PING” command and the “ECHO” response by the Base Station that is waiting for the call.
  • the handset 121 is currently communicating with the Base Station # 1 123 via communications link 122 .
  • the Base Station # 2 124 that is waiting for the call will periodically send a “PING” command 145 to the handset 121 .
  • the handset 121 enters the coverage area (is in range) of the waiting Base Station 124 , and when it receives a “PING” command with its address, it will reply with an “ECHO” response 146 .
  • the “ECHO” response 146 is also received by the Base Station # 1 123 .
  • the waiting Base Station # 2 124 transmits the “PING” command 145 during the hops that the Base Station # 1 123 has dedicated (yielded) for this operation, as described hereinabove (see, e.g., FIG. 14B, 702, 703 ).
  • the “ECHO” reply 146 will be received by both Base Stations 123 and 124 , whereupon the Base Stations 123 and 124 can each measure the quality of the received signal (“ECHO”) and report the measurements to the Switch (e.g., 129 ; FIG. 2). Based on this measurement of the quality of the received signal, the Switch 129 can compare signal quality and decide when is the right time to perform the handoff, and implement the handoff procedures described hereinabove.
  • FIG. 15B illustrates an alternative, “active” method for detecting the handset 121 .
  • the Base Station # 1 123 that is currently connected to the handset 121 transmits a “PING” command 147 , once in M hops.
  • the handset 121 replies with an “ECHO” response 146 ′ for each “PING” command 147 it receives.
  • the neighboring Base Station # 2 124 will receive the “ECHO” response 146 ′ by monitoring each Mth hop, in order to receive the “ECHO” response of the handset 121 that is approaching it.
  • the neighboring Base Station # 2 124 receives the “ECHO” response 146 ′, it measures the quality of the received signal, and reports to the Switch 129 .
  • This method is different from the method previously described with respect to FIG. 15A in two aspects:
  • the quality of each hop may be measured by many known methods, such as energy level measurement, signal-to-noise ratio (SNR) measurement, packet loss ratio and bit error rate measurement (BER) that can be performed on the header of each message.
  • SNR signal-to-noise ratio
  • BER bit error rate measurement
  • Each Base Station maintains a “Neighbor Connections Table”, which includes information about the connections between handsets and neighboring Base Stations.
  • the “Neighbor Connections Table” includes the following information:
  • FIG. 16A illustrates a technique (procedure) for detecting a handset that enters the coverage area of a Base Station when (as in the example of FIG. 15B) the Base Station that the handset is currently connected to generates the “PING” command that is sent to the handsets. All of the Base Stations (e.g., 391 - 397 ; FIG. 14A) preferably perform the same detection procedure, whether they the handset is connected with them or not.
  • step 400 When a hop is due (steps 400 , 401 ), the even-numbered hops are used by the handset, and the Base Stations use the odd-numbered hops.
  • a hop counter is incremented by one, and if (as determined in the step 403 ) it is the Kth hop, the Base Station will to try to send a “PING” to one of the handsets that are candidates for handoff. If it is not the Kth hop (step 403 , “N”), the Base Station waits for the next hop (step 400 ).
  • NMAC represents the address of the handset that will be called
  • NegTab is an abbreviation of “Neighboring Connection Table”.
  • step 404 If handoff has not started yet with any handset (step 404 , “N”), all the handsets will be called in order.
  • the pointer to the NegTab is incremented (step 405 ), and the address of the handset is retrieved from the NegTab (step 406 ).
  • the Base Station then transmits a “PING” command with the address of the handset (step 407 ).
  • PING the address of the handset
  • the next item in the NegTab is checked (step 411 ) and, if handoff with it has already started, it will be “PINGED” (steps 412 , 407 ).
  • the handsets that have not started handoff will be “PING”ed only once in K2 “PING”s (steps 410 , 413 , 414 ).
  • step 420 When an “ECHO” is received (step 420 , “Y”) and it is determined to be from a handset that communicates with a neighboring Base Station (step 419 , “N”), it will be compared to all the entries in the “Neighbor Connections Table” (NegTab) 421 , 422 . If it is found in the NegTab (step 422 , “Y”), the quality of the hop is measured (step 423 ) and a record of the average quality in the previous hops is maintained in the “Neighbor Connections Table” (step 424 ). The following measurement parameters are sent to the Switch (step 425 ):
  • FIG. 16B illustrates a procedure that a Base Station performs when it receives an “ECHO” response from one of the handsets that are connected to it (from FIG. 16A, step 419 , “Y”).
  • the “ECHO” response can be received either when the connected Base Station or one of its neighbors sends a “PING” message to the handset. (See, e.g., FIGS. 15A and 15B.)
  • the Base Station checks to see if the “ECHO” reply was caused by itself, or by one of the neighboring Base Stations (steps 430 , 431 ). This information is contained in the Identifier of the “ECHO” reply, as described hereinabove.
  • step 431 If the “ECHO” was caused by a neighboring Base Station (step 431 , “Y”), the quality of the received signal is measured and averaged (step 432 ), and the measurement parameters are sent the Switch (step 433 ) to be used by the Switch in determining when to perform handoff. If the Base Station itself caused the “ECHO” reply (step 431 , “N”), the task simply exits (“B”).
  • FIGS. 16A and 16B illustrated the procedure of transmitting the “PING” from the Base Station that the handset is connected too, and detecting the arrival of a handset from a neighboring Base Station.
  • FIG. 23 illustrates a procedure for performed by the Base Station when reception or transmission of a hop is required (steps 1200 , 1201 ).
  • the Base Stations sends a “PING” to one of the handsets that are connected to it.
  • Tcount is incremented (step 1204 ), and the next handset that appears in the list of handsets (Connection Table, or “ConTab”) that are connected to the Base Station is chosen (step 1205 ).
  • the “PING” is sent with the address taken from the ConTab (step 1206 ).
  • the receiver looks for an “ECHO” response (step 1207 ). If an “ECHO” is received, and it originator was a neighboring Base Station (step 1208 ), the parameters are compared to the NegTab (step 1209 ), and if it is found in the table (step 1214 ), the quality of the signal is measured (step 1210 ) and averaged (step 1211 ). If the “ECHO” response was to a “PING” command that originated from the same Base Station, the quality is measured (step 1213 ). In both cases the connection parameters and the quality are sent to the Switch (step 1212 ).
  • the first handset detection method (FIGS. 13, 14A, 14 B, 14 C, 14 D) is based on passive monitoring of the handset.
  • the second handset detection method (FIGS. 15A, 15B, 16 A, 16 B) the handsets are actively “PING”ed, and their “ECHO” responses are noted.
  • a Base Station that is connected to a handset continuously sends received quality measurements to the Switch and, when a neighboring Base Station detects a handset, a quality measurement is also sent by the neighboring Base Station to the Switch.
  • FIG. 17A illustrates a method for making the handoff decision, when a passive detection method is used.
  • FIG. 17B illustrates a method for making the handoff decision, when an active detection method is used.
  • FIG. 17A illustrates a procedure that is implemented at the Switch ( 129 ) in order to decide to which Base Station the handset should be handed.
  • Energy measurements from two or more (three shown) Base Stations 801 , 802 and 803 receiving a signal (i.e., the same signal) from a single handset (i.e., the same handset, not shown) are provided to the Switch, as described hereinabove (e.g., over the LAN 140 ).
  • these measurements are “smoothed” by a plurality (three shown) of sliding window averaging filters 804 , 805 and 806 , respectively, and they are compared with one another by decision (handoff control) logic 807 , which issues a signal (“Select Base Station”) to effect handoff.
  • the sliding widow average filters 804 , 805 and 806 compute the average quality received from a given Base Station over the previous T r milliseconds, typically hundreds of milliseconds, (over a time interval encompassing at least two subsequent signals from the receiving Base Station), taking into account only the times in which the handset signal was received by more than one Base Station.
  • a Base Station receives the handset at a level which is stronger by at least D 1 decibels than the level which is currently received by the Base Station with which the handset currently communicates, and at least T d milliseconds have passed from the last handoff, a handoff is required. This is intended to address the situation of a moderate and slow movement of a handset from one Base Station to another.
  • a Base Station receives the handset at a level, which is stronger by at least D 2 decibels than the level, which is currently received by the Base Station with which the handset currently communicates a handoff will be performed immediately. This is intended to address the situation of an abrupt move from one Base Station to another.
  • the decision algorithm is basically the same as has just been described.
  • the main difference comes from the fact that in the active method the different Base Stations are able to determine the quality that they measured for a single hop, which all of them can identify. Therefore, the Switch is able to compute the quality difference per hop, and thus improve the timing accuracy of handoff.
  • FIG. 17B illustrates the handoff decision method when using an active detection method.
  • the measurements of the same hops are aligned in time ( 808 ). They are then averaged over X hops ( 804 , 805 , 806 ), and the same decision logic ( 807 ) that was described above may be used to determine which is the most suitable Base Station to connect to the handset, and issue the “select Base Station” signal.
  • the methods described hereinabove relate to performing handoff between Base Stations when the handset is conducting a call.
  • a handset When a handset is not conducting a call it may move from one Base Station to the other. When it moves, one connection will be ended, and another will be created.
  • the mechanism for ending a connection, and initiating a new one is part of the short-range wireless communication protocol. For example in the Bluetooth protocol, the handset searches for a Base Station, when it finds one, it stays connected to it. If it leaves the coverage area of the Base Station, the connection will end, and the handset will search again for a Base Station. This mechanism is sufficient for a handset that is not currently in a call, but it does not guarantee smooth handoff while in a call.
  • disconnecting from one Base Station and re-establishing connection with the other may take several seconds, and during this time it will not be possible to initiate a call.
  • One of the advantages of the method of actively “PING”ing a handset is that its movement can be detected quickly, even when it is not engaged in a call, and this “waiting” period can be eliminated.
  • Update Switch handleset ID, neighbor Base Station ID, and Base Station ID, TOD, handle of low-level protocol instance.
  • the Switch also keeps a LOG file of the events in the system.
  • the LOG file includes the quality measurements, call parameters (time, caller ID, called ID, reason for termination, etc.) and the handoff decisions. These may serve to analyze the Base Station's topology and allow for topology improvements and adjustments. For example the reason for a call termination may be correlated to low receive quality, which could imply that there is a “hole” in the coverage pattern.
  • FIG. 20 illustrates the implementation of detection and time synchronization method that is based on a correlator.
  • the correlator/detector ( 308 ) was the basis for synchronization of TOD in FIG. 11, and for the detection of presence of a transmitter and synchronization in FIG. 13.
  • a neighboring Base Station It is important for a neighboring Base Station to be able to detect and synchronize with a mobile unit prior to receiving a handoff. This process should be done as quickly as possible to ensure seamless handoff of a session.
  • the process begins with a wide-range search for “target” signals having the correct timing for a mobile unit, based on the rough synchronization information provided by the Base Station which is connected with the mobile unit. These “target” signals are estimated, based on the rough synchronization data. When a match is found (an actual signal from mobile unit is acquired) the search range can be narrowed accordingly (and dramatically). Then, synchronization can proceed as described hereinabove.
  • the detector/correlator 2000 comprises a signal detector 1001 and a correlator 1002 .
  • the task of the detector/correlator 2000 is to provide information whether a target signal is currently received, and to estimate the parameters which serve the hand-off process.
  • the signal detector 1001 and correlator 1002 receive the actual received signal 1008 and its corresponding time 1009 and frequency 1004 , as illustrated, and correlates them to the emulated time and frequency instances 1006 .
  • the fine TOD, drift and quality of the target signal are estimated by the correlator 1002 which reports the estimated parameters 1007 , along with a status which indicates whether the target signal has been acquired, or not.
  • the task of the signal detector 1001 is to process the received signal 1008 and to estimate its time of arrival (TOA), i.e. the exact timing of a hop, and quality values 1003 .
  • TOA time of arrival
  • This may be done by several techniques, which are well known from classical detection theory. As an example of such techniques, an energy detector and a matched filter can be used.
  • FIG. 21 shows an example of the implementation of the signal detector 1001 of FIG. 20.
  • the received signal 1008 which is received from the RF receiver output, is fed to an energy detector 1011 .
  • the energy detector 1011 produces a signal 1014 , which represents the temporal energy shape of the signal.
  • the temporal energy shape 1014 is fed into a matched filter 1012 .
  • the matched filter 1012 has an impulse response, which matches the energy shape the target signal.
  • the matched filter 1012 will produce maximum value at the time instance which represents an estimation of the time of arrival (TOA), i.e. exact timing of the hops, of the target signal 1008 .
  • TOA time of arrival
  • the maximum value of the filter output represents an estimation of the received signal quality.
  • the time instance which represents the estimation of the TOA, is represented in terms of the time clock 1009 .
  • the matched filter 1012 reports TOA and quality values of which the quality is above a threshold value T h , and the maximum is a global maximum within a two-sided time window of T s1 microseconds.
  • Other implementations of the signal detector 1001 in FIG. 20 can be utilized. Such implementations can correlate the received signal 1008 with the known portions of the target signal temporal pattern instead of its energy temporal shape. Such implementations may achieve improved estimation performance.
  • the time-frequency correlator 1002 in FIG. 20 receives the TOA and quality values 1003 produced by the signal detector 1001 and corresponding frequency values 1004 , which are the actual tuning frequency of the RF receiver. These inputs are referred to herein as the ‘actual’ TOA-frequency-quality instances. These include the estimated information of the signals, which are received from the various sources. On the other inputs, the time/frequency correlator 1002 receives emulated values of TOA and frequency 1006 instances for a specific target source (i.e. a specific handset). We will refer to these values hereafter as ‘target’ TOA-frequency instances. The time-frequency correlator seeks matches in the instances from both sources—the ‘actual’ and the ‘target’ and detects TOA-frequency patterns at the ‘actual’ instances which are ‘similar’ to the ‘target’ pattern. This process is performed in two possible modes:
  • the ‘actual’ data and 1004 is written into ‘actual’ instances history buffer (e.g., FIFO) and constitutes a list of which records consists of ‘actual_TOA’, ‘actual_frequency’ and ‘actual_quality’.
  • the ‘target’ data 1006 is written into ‘target’ instances histories buffer (e.g., FIFO) and constitutes a list of which records consist of ‘target_TOA’ and ‘target_frequency’.
  • LMSE least mean square error
  • the estimated linear line can be represented as:
  • diff ‘est diff 0 ’+‘est drift’*(TOA-TOA 0 )
  • TOA 0 is the smallest ‘actual TOA’ value out of the ‘diff cluster’ records
  • ‘est diff 0 ’ is the estimated output parameter of ‘fine TOD’ 1007
  • ‘est drift is the estimation the output parameter ‘drift’ 1007 .
  • the ‘diff quality histogram’ value normalized by the corresponding ‘bin population’ is the ‘quality’ output 1007 value.
  • the value of ‘known diff’ is set to ‘prev_est_diff 0 ’+‘prev_est_drift’*(‘current_TOA 0 ’-‘prev_TOA 0 ’).
  • the terms ‘prev_est_diff 0 ’ and ‘prev_TOA 0 ’ represented the ‘est_diff 0 ’ and ‘TOA 0 ’ which has been evaluated in the previous calculation (either in ‘acquisition’ mode or in ‘tracking’ mode).
  • the term ‘current_TOA 0 ’ is the ‘TOA 0 ’ of current calculation.
  • T y4 microseconds when Ty4 is typically 2000) for the ‘tracking’ mode replaces T y2 of the ‘acquisition’ mode.
  • FIG. 18 illustrates, in block diagram form, major components of a Base Station 1800 .
  • a plurality (three shown) of front-end processors 604 , 605 and 606 are connected to a plurality (three shown) of antennas 601 , 602 and 603 , respectively.
  • the front-end processors 604 , 605 and 606 perform the low-level protocols of the short-range communication protocol, described hereinabove.
  • a front-end processor 604 , 605 and 606 waits for a handset to establish a new connection.
  • a connection When a connection is created it reports the call parameters (e.g., Bluetooth device address, TOD, Encryption key, authentication key, etc.) and transfers the call stream to the central processing unit 607 .
  • a front-end processor When a front-end processor is idle, it can also be used to receive (detect, monitor) a handset that is leaving a neighboring Base Station.
  • the central processing unit 607 then sends the front-end processor, the call parameters, and the exact time of handoff.
  • the front-end processor would at that time, continue the communicating with the handset, as if it was still in the neighboring Base Station.
  • a separate circuit module 612 (TOD Synchronization & Handset Detection) is used to detect arrival of new handset, and also to synchronize the TOD of all the calls, according to the techniques described hereinabove.
  • This unit 612 is shown having its own antenna 611 .
  • the central processing unit 607 controls the operation of the front-end processors 604 , 605 and 606 , receives data about new handoff and fine TOD estimation, receives data from neighboring Base Station, maintains the “Neighbor Connection Table”, communicates with the Switch and the other Base Stations.
  • the local area network interface 609 is suitably a standard interface, for example a connection to a 10Base-T or 100-Base-T Ethernet, for connecting to the Local Area Network (LAN) 140 .
  • Memory 608 and Non-Volatile Memory (NVM) 610 is shown connected to the central processing unit (CPU) 607 .
  • FIG. 19 illustrates, in greater detail, an implementation of a representative one 604 of the front-end processors 604 , 605 and 606 described hereinabove with respect to FIG. 18.
  • a base-band processor 631 determines the transmission and reception channels, encodes and decodes speech, deals with error correction, authentication and encryption.
  • the radio frequency front end 630 modulates and demodulates the data, and connects to the antenna 601 .
  • the base-band processor 631 controls the frequency (“frequency control” 633 ) of each hop, sends and receives data (“energy, time of detection” 634 ) from the RF front end, and receives indication of signal strength (“base band parameters” 635 ).
  • the method for dividing the short-range communication protocol in order to support mobility of devices includes telephony-related protocols, and also protocols for data transfer, such as PPP over the short-range communication link.
  • These methods can be implemented in order to connect mobile devices that are equipped with a short-range communication transmitter/receiver such as a Bluetooth chipset. Such devices may move from the coverage area of one Base Station to the coverage area of another, when the Switch and Base Stations handle the handoff of the connection from one Base Station to another.
  • Typical application may be the connection of laptop computers equipped with a Bluetooth short-range communication link to the organization's e-mail server.
  • Another possible application is connecting such mobile devices that for example utilize the PPP (point-to-point protocol) over Bluetooth wireless link, to the Internet, via a central remote access server.
  • PPP point-to-point protocol
  • a system may also support several such applications.
  • a personal data (or digital) assistant (PDA) 1301 connects to the systems Base Stations 1304 and 1305 , as illustrated.
  • the PDA 1301 and the laptop 1302 may connect, via the local area network (LAN) 1306 to an e-mail server 1308 in order to send or receive messages, and may also connect to a remote access server (RAS) 1309 for Internet connection.
  • the cellular handset 1303 may connect to another handset (not shown) or, via a Telephony Gateway 1306 to the PSTN.
  • the Base Stations 1304 and 1305 and the Switch 1307 handle the various levels of the communication protocol, utilizing the methods described hereinabove.
  • the mobile unit is a device which is any of the following devices: telephone handset, standard cordless telephone handset, cellular telephone handset, personal data device, personal digital assistant (PDA), computer, laptop computer, e-mail server, and a device utilizing point-to-point protocol (PPP) to the Internet via a central remote access server, a headset (including a cordless headset), a personal server, a wearable computer (or computing device), a wireless (video or still) camera, or a mobile music players (i.e., MP-3 devices etc).
  • PDA personal digital assistant
  • PDA personal digital assistant
  • PDA personal digital assistant
  • laptop computer laptop computer
  • e-mail server e-mail server
  • PPP point-to-point protocol
  • PPP point-to-point protocol
  • a central remote access server a headset (including a cordless headset), a personal server, a wearable computer (or computing device), a wireless (video or still) camera, or a mobile music players (i.e., MP-3 devices etc).

Abstract

Methods to create a cellular-like communication system, such as a Wireless Private Branch Exchange (WPBX), which includes mobile devices such as standard cordless phones (handsets), particularly, mobile devices utilizing the Bluetooth short-range wireless communication protocol. The methods provide seamless and reliable handoff of sessions between Base Stations while the mobile device is moving between picocells, by implementing a high-level of synchronization between the Base Stations and the Switch. Base Stations of picocells having small coverage areas communicate with the handsets. The communication protocol is divided into a low-level protocol performed by the Base Stations and a high-level protocol performed by the Switch connected to all the Base Stations. The methods support mobile computing or telephony devices and communication protocols, which are not specified to handle handoffs of sessions while moving between Base Stations coverage areas in a data, voice or telephony wireless network.

Description

  • This Application is a Divisional of U.S. patent application Ser. No. 09/784,109 filed Feb. 16, 2001, currently pending.[0001]
  • TECHNICAL FIELD OF THE INVENTION
  • The invention relates to wireless communications systems having a plurality of mobile units (devices) having the ability to connect short-range with a plurality of Base Stations, and techniques for handing off a mobile unit from one Base Station to another when the mobile unit moves between areas of coverage of neighboring Base Stations. [0002]
  • BACKGROUND OF THE INVENTION
  • The effective range of a mobile device, such as a cordless handset, from its Base Station is limited by its transmission power and by the receiver sensitivity of the mobile device and the Base Station. Wireless Private Branch Exchange (WPBX) systems address this limitation by using more than one Base Station (BS). The area that a Base Station covers is called a cell. In the main, hereinafter, mobile units (devices) that are cordless (telephone) handsets are discussed. [0003]
  • In a WPBX, the Base Stations are interconnected in order to allow handsets that are in different cells to communicate with one another. When a handset moves from one cell to another during a call, the handoff (or handover) of communication from one Base Station to another Base Station enables uninterrupted communication. A central unit that is usually called the “Switch” is connected to all the Base Stations. The Switch controls the operation of the system, routes the call to Base Stations and to Gateways, which connect the WPBX to external communication systems. The transmission power of a cordless handset in the WPBX is usually lower than the transmission power of the handset of a standard cellular system, which results in a WPBX for cordless handsets having much smaller cells (referred to as mini-cells, or micro-cells or picocells) than the cells of a standard cellular system. [0004]
  • Some cordless handsets use communication protocols that are also used in cellular system, but they transmit in a lower power than a mobile (cellular) handset. For examples protocols in use are GSM and IS-136. According to these protocols the handoff between cells is performed by collaboration of the cordless handset, the Base Stations and the Switch. These handsets can connect to the WPBX when they are in its coverage area, and can also connect to any other cellular system that supports the communication protocol that they are using. [0005]
  • Some handsets use communication protocols that were designed especially to allow communication with WPBX. Some examples are DECT, CT-2, PAC, and PACS. The handset is usually a dedicated handset that is used only in the area covered by the WBPX. [0006]
  • Some handsets have dual mode support. For example a handset may communicate with the WPBX using DECT, and may allow communication with other cellular systems using GSM. [0007]
  • Some WPBXs use standard cordless handsets. These handsets have no special mechanism to support the handoff between cells. In these systems the Switch and the Base Stations perform the handoff, and the handset is not aware of (does not participate actively in) the handoff process. When a standard cordless handset moves from one cell to another the Switch routes the call to another cell. Since cordless phones use “simple” protocols, for example an analog fixed transmission, when the call is routed to the new cell, the cordless phone automatically will receive it. [0008]
  • During the last years short-range communication protocols have become much more complicated. Very low power is used in order to allow many systems to operate in close vicinity. Complex transmissions methods like frequency hopping and spread spectrum are used in order to overcome interference, and improve the communication quality. Digital communication methods are used allowing communication of data and voice on the same system. Error correction encoders are used in order to improve reliability. Security and privacy of the communication is improved with the use of Digital authentication and encryption. [0009]
  • Short-range communication systems are used for many purposes. A growing trend for short-range communication usage is Personal Area Network (PAN) devices and applications, among such is the “all in one handset” and personal data devices. Such type of handset supports standard cellular communication, and also has the ability to communicate with personal area network devices that are in its near vicinity, using short-range communication. Some PAN short-range communication standards were not designed to allow mobility, i.e. they were not designed to allow handoff in between Base Stations in general and during an active session in particular. This limits a session via such device to be linked to a single Base Station and therefore to very limited area. [0010]
  • The “Bluetooth” standard is a short-range wireless communication standard that has many uses for voice applications and telephony (e.g. cordless phone, wireless headsets) and also for data applications (laptop to personal computer communication, wireless local area network Gateways etc.). The Bluetooth wireless technology is implemented using a universal radio interface in the 2.45 GHz frequency band that enables portable electronic devices to connect and communicate wirelessly via short-range, ad hoc networks. Each unit can simultaneously communicate with up to seven other units per piconet. Moreover, each unit can simultaneously belong to several piconets. [0011]
  • Bluetooth connection is planned to be standard feature in future cellular handsets, Personal Digital Assistants (PDAs), Palmtop and Laptop computers. The Bluetooth standard does not support mobility between Base Stations, since it was primarily designed for short-range communication as a cable replacement. A cellular handset with Bluetooth wireless technology will be able to operate as a cordless phone, but only in the near vicinity of a single Base Station. The same limitation applies to mobile personal data devices such as PDA's and mobile computers. [0012]
  • Glossary [0013]
  • Unless otherwise noted, or as may be evident from the context of their usage, any terms, abbreviations, acronyms or scientific symbols and notations used herein are to be given their ordinary meaning in the technical discipline to which the invention most nearly pertains. The following glossary of terms is intended to lend clarity and consistency to the various descriptions contained herein, as well as in prior art documents: [0014]
    ATM Asynchronous Transfer Mode
    BER Bit Error Rate
    Bluetooth short-range wireless communications
    standard/interface/protocol
    BS Base Station
    CPU Central Processing Unit
    CRC Cyclic Redundancy Check.
    CT-2 a communication protocol
    DECT Digital Enhanced Cordless Telephone
    communication protocol
    DN Destination Number
    ECHO a response to a PING
    FIFO First In, First Out
    FTP File Transfer Protocol
    Gateway an interface for communications
    between dissimilar services
    GHz GigaHertz
    GSM: Global System for Mobile
    Communication
    handoff transfer of mobile devices from one
    Base Station to another Base Station
    ID Identification (number)
    IEEE 802.2 Ethernet protocol
    IS-136 communication protocol
    ISDN Integrated Services Digital Network
    ITU-T 802.15 a communication standard similar
    to the Bluetooth standard
    ITU-T Q.931 a telephony protocol for call setup
    IVR Interactive Voice Response
    LAN Local Area Network
    LMSE Least Mean Square Error
    MSC Mobile Switching Center (MSC)
    PAC a communication protocol
    PACS a communication protocol
    PAN Personal Area Network
    PBX Private Branch Exchange
    PABX Private Automatic Branch Exchange
    (also referred to as PBX)
    PDA Personal Digital (or Data) Assistant
    picocell a coverage area of a short-range
    Base Station
    PING a command which is sent,
    soliciting a response
    PPP Point-To-Point Protocol
    PSTN Public Switched Telephone
    Network
    RF Radio Frequency
    SNR Signal-to-Noise Ratio
    Switch Apparatus for routing
    telephone calls
    TOD Time Of Day
    WAP Wireless Application Protocol
    WPBX Wireless Private Branch Exchange
  • SUMMARY OF THE INVENTION
  • A general object of the invention is to provide a technique for allowing mobile units (devices) such as standard cordless telephone handsets and PDA (Personal Digital Assistant), laptop or notebook computers or similar devices that support wireless communication (such as Bluetooth wireless technology) to seamlessly connect to a Wireless Private Branch Exchange (WPBX), or to a standard (wired) PBX or to a LAN or to a cellular telephone network or to a standard wired telephone network, thereby avoiding the use of special (typically expensive) handsets or attachmnents or software or hardware agents, with the abovementioned mobile devices. [0015]
  • According to the present invention there is provided, in a wireless communication system comprising at least two Base Stations, at least one Switch in communication with the Base Stations, a method of communicating between mobile units and the Base Stations comprising: dividing a communication protocol into a low-level protocol for performing tasks that require accurate time synchronization and a high-level protocol which does not require accurate time synchronization; and for each connection of a mobile unit with a Base Station, running an instance of the low-level protocol at the Base Station connected with the mobile unit and running an instance of the high-level protocol at the Switch. [0016]
  • According to the present invention there is provided, in a wireless communication system comprising a Base Station connected with a mobile unit, a method of synchronizing at least one neighboring Base Station to the Base Station connected with the mobile unit comprising: from the Base Station connected with the mobile unit, sending call parameters and rough synchronization information to the at least one neighboring Base Station; and at the at least one neighboring Base Station, monitoring transmissions of at least one of: the Base Station connected with the mobile unit; the mobile unit; and a beacon signal from a beacon transmitter which is within range of the at least one neighboring Base Station and the Base Station connected with the mobile unit. [0017]
  • According to the present invention there is provided, in a wireless communication system comprising a plurality of Base Stations and at least one Switch in communication with the Base Stations, a method of synchronizing at least one neighboring Base Station to a Base Station connected with a mobile unit comprising: from the Base Station connected with the mobile unit, periodically transmitting during a selected time interval with higher transmission power than during normal transmission; and receiving the transmission with higher transmission power at the least one neighboring Base Station. [0018]
  • According to the present invention there is provided, in a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting the presence of a specific mobile unit in a coverage area of at least one neighboring Base Station, comprising: the Base Station connected with the mobile unit provides, to the at least one neighboring Base Station, information about the connection with the mobile unit, including rough TOD and a device address for the mobile unit; at the at least one neighboring Base Station, receiving information and generating a list of frequencies in which the mobile unit is likely to transmit; and at the at least one neighboring Base Station, checking for a signal transmitted by the mobile unit. [0019]
  • According to the present invention there is provided a method for detecting a mobile unit by a Base Station, wherein frequency-hopping is used to communicate between Base Stations and mobile units, comprising: at a Base Station that is connected to a mobile unit, periodically yielding a hop; and during the hop which has been yielded by the Base Station connected with the mobile unit, communicating with the mobile unit from at least one neighboring Base Station. [0020]
  • According to the present invention there is provided, in a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting a handset by at least one Base Station which is waiting for the mobile unit to enter its coverage area, comprising: from the at least one Base Station waiting for the mobile unit to enter its coverage area and the Base Station connected with the mobile unit, sending a PING command to the mobile unit; and at the Base Station waiting for the mobile unit to enter its coverage area, receiving an ECHO reply from the mobile unit. [0021]
  • According to the present invention there is provided, in a wireless communication system comprising at least two Base Stations, at least one Switch in communication with the Base Stations, and at least one mobile unit, a method of handing off the mobile unit from a Base Station communicating with the mobile unit and a neighboring Base Station, comprising: smoothing a plurality of signals received from a handset by a plurality of Base Stations; comparing the signals with one another; and selecting a Base Station for handoff based on signal quality. [0022]
  • According to the present invention there is provided, in a wireless communication system comprising at least two Base Stations and at least one Switch in communication with the Base Stations, a method of performing handoff of a session from a Base Station connected with a mobile unit to a neighboring Base Station, wherein an instance of a low-level communications protocol is running at the Base Station connected with the mobile unit, comprising: at the Switch, determining when to perform handoff to a selected one of the neighboring Base Stations; at the selected one of the neighboring Base Stations, creating a copy of the low-level communications protocol, including at least a synchronized time of day (TOD) parameter; from the Switch, sending a command to stop communication with the mobile unit at a specified TOD to the Base Station connected with the mobile unit and sending a command to start communication with the mobile unit at the specified TOD to the selected one of the neighboring Base Stations; and updating session status tables in the Switch and in the Base Stations. [0023]
  • According to the present invention there is provided, in a wireless communication system comprising a Base Station connected with a mobile unit, a method of detecting and synchronizing with the mobile unit prior to receiving a handoff of a session with the mobile unit, comprising: from the Base Station connected with the mobile unit, sending rough synchronization information to at least one neighboring Base Station; at the neighboring Base Station, performing a wide-range search for “target” signals having the correct timing for a mobile unit, based on the rough synchronization information provided by the Base Station which is connected with the mobile unit; narrowing the search for an actual signal from the mobile unit; acquiring the target signal; and synchronizing the neighboring Base Station to the Base Station connected with the mobile unit. [0024]
  • According to the present invention, a system comprises one or more mobile units such as standard cordless handsets, two or more Base Stations, and at least one Switch. The Base Stations are connected to one another and to the Switch. The handsets communicate directly with the Base Stations, rather than with one another. [0025]
  • According to an aspect of the present invention, the Base Stations and Switch communicate directly with one another, rather than, for example, over the PSTN. However, the system may interface with the PSTN, the Internet or a LAN, or with a PBX via a Gateway. [0026]
  • According to a feature of the present invention, a method is provided for handing off calls from a one Base Station to another (neighboring) Base Station, with mobile units (e.g., standard cordless handsets) that do not support connection to more than one Base Station and that do not support mobility with seamless handoff between Base Stations. This is an important feature because the mobile device uses complicated digital communication methods, so simple handoff methods that only the Switch supports are inadequate. Rather, the Switch and Base Stations cooperate with one another for the handoff operation. Accurate synchronization of Base Stations facilitates handoff. Advantageously, the handoff operation does not require explicit cooperation between the mobile device and the Base Stations. [0027]
  • According to an aspect of the present invention, a method is provided for dividing the short-range communication protocol that is used by the handset between high-level protocols which do not need accurate time synchronization and low-level protocols which have strict time synchronization requirements (require accurate time synchronization). The low-level protocols are performed by the Base Stations, and the high-level protocols are performed in the Switch. This enables handoff to be performed even when complex (e.g. frequency hopping, encryption, authentication) and multi-level protocols are used. This also reduces the synchronization requirements between Base Stations. [0028]
  • According to an aspect of the present invention, a method is provided for accurately synchronizing the Base Stations and, more particularly, for synchronizing the Base Stations when frequency-hopping communication is used. [0029]
  • According to an aspect of the present invention, a method is provided for detecting the presence of a mobile device in the coverage area of a Base Station (i.e., its picocell). [0030]
  • According to an aspect of the present invention, a method is provided for determining when to perform handoff of a session(i.e., a phone call, a data link, etc.), and to which Base Station to hand the session, by measuring signal quality at the Base Stations. This method is effective, even when complex transmission methods are used. [0031]
  • The methods disclosed herein are not limited to the communication of a certain type of data. Hence, they can be utilized for telephony applications and for data applications. [0032]
  • Other objects, features and advantages of the invention will become apparent in light of the following description thereof. [0033]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Reference will be made in detail to preferred embodiments of the invention, examples of which may be illustrated in the accompanying drawing figures. The figures are intended to be illustrative, not limiting. Although the invention is generally described in the context of these preferred embodiments, it should be understood that it is not intended to limit the spirit and scope of the invention to these particular embodiments. [0034]
  • In flowcharts presented herein, rectangular boxes generally represent a sequential step being performed, a diamond shaped box generally represents a decision step (test) having two mutually-exclusive results (“Y”=Yes; “N”=No), and an empty circle is not a step or a test, but is merely a graphical junction point at which two or more paths in the flowchart converge. [0035]
  • The structure, operation, and advantages of the present preferred embodiment of the invention will become further apparent upon consideration of the following description, taken in conjunction with the accompanying figures, wherein: [0036]
  • FIG. 1 is a diagram of a cellular system covering a relatively large area and a Wireless Private Branch Exchange (WPBX) system covering a relatively smaller area, illustrating that a cellular handset can communicate with a Base Station of the cellular system and also with Base Stations of the WPBX; [0037]
  • FIG. 2 is a schematic block diagram illustrating main components and architecture of a WPBX system, suitable for use as the WPBX system of FIG. 1; [0038]
  • FIG. 3A is a schematic block diagram of a communications system incorporating a WPBX, such as the WPBX of FIG. 2, with the addition of a Gateway connecting the WPBX to the Public Switched Telephone Network (PSTN); [0039]
  • FIG. 3B is a schematic block diagram of a communications system incorporating a WPBX, such as the WPBX of FIG. 2, with the addition of a Gateway connecting the WPBX to a Private Branch Exchange (PBX); [0040]
  • FIG. 4 is a schematic block diagram illustrating an architecture for a WPBX, with the Base Stations, the Switch and the Gateway interconnected by a local area network (LAN); [0041]
  • FIG. 5 is a flowchart illustrating a procedure for call “setup” at an originating Base Station of a WPBX; [0042]
  • FIG. 6 is a flowchart illustrating a procedure for call “setup” at a receiving Base Station of a WPBX; [0043]
  • FIG. 7 is a flowchart illustrating a procedure for call “setup” at a Switch of a WPBX; [0044]
  • FIGS. 8A and 8B are schematic block diagrams illustrating an architecture for dividing the communication protocol into low-level and high-level protocols for implementation in the Base Stations and in the Switch, respectively, of a WPBX particularly during a handoff, according to the invention; [0045]
  • FIGS. 9A, 9B and [0046] 9C are schematic block diagrams illustrating rough and fine synchronization of Base Stations in a WPBX, particularly during a handoff, according to the invention;
  • FIG. 10 is a graph of a Base Station's transmission power, during hops, illustrating that once in every K hops the energy that the Base Station transmits may be increased to allow other Base Stations that normally do not receive transmissions from the transmitting Base Station to synchronize to the transmitting Base Station, according to the invention; [0047]
  • FIG. 11 is a schematic block diagram illustrating an architecture for major components of a Base Station, according to the invention; [0048]
  • FIG. 12 is a flowchart illustrating a “call routing task” that runs in the Switch in order to isolate the high-level protocols from the occurrence of the handoff, according to the invention; [0049]
  • FIG. 13 is a schematic block diagram illustrating a passive method for detecting arrival of a handset in a Base Station's coverage area during a call, according to the invention; [0050]
  • FIG. 14A is a diagram illustrating a handset communicating with one Base Station, and six other neighboring Base Stations waiting for the handset to enter their coverage area, according to the invention; [0051]
  • FIGS. 14B, 14C and [0052] 14D are graphs illustrating transmissions by the Base Station communicating with the handsets, and by the neighboring Base stations, according to the invention;
  • FIGS. 15A and 15B are diagrams illustrating detection of a handset by a Base Station in communication with the handset and a neighboring Base Station, according to the invention; [0053]
  • FIG. 16A is a flowchart illustrating a procedure that Base Stations may use to detect a handset that enters their coverage area, according to the invention; [0054]
  • FIG. 16B is a flowchart illustrating a procedure that Base Stations may use to determine that a handset connected to them is moving into the coverage area of another Base Station, according to the invention; [0055]
  • FIG. 17A is a schematic block diagram illustrating a method for making a handoff decision, performed in the central Switch, when a passive detection method is used, according to the invention; [0056]
  • FIG. 17B is a schematic block diagram illustrating a method for making a handoff decision, performed in the central Switch, when an active detection method is used, according to the invention; [0057]
  • FIG. 18 is a schematic block diagram of a Base Station comprising a central processing unit (CPU), front end processors, memory, TOD synchronization and handset detection unit, and an interface to a local area network (LAN), according to the invention; [0058]
  • FIG. 19 is a schematic block diagram illustrating the front-end processor of the Base Station of FIG. 18, which comprises a base-band processor and a radio frequency (RF) front end, according to the invention; [0059]
  • FIG. 20 is a schematic block diagram illustrating the structure of a detector and fine TOD estimator, based on a matching correlator, according to the invention; [0060]
  • FIG. 21 is a schematic block diagram of an implementation for the Time-Frequency Correlator of FIG. 20, according to the invention; [0061]
  • FIG. 22 is a diagram illustrating an implementation of a WPBX system with two Switches, according to the invention. [0062]
  • FIG. 23 is a flow chart illustrating a procedure for transmitting “PING” commands to a handset and receiving “ECHO” responses from the handset, when the Base Station originating the “PING” command is the same Base Station the handset is currently connected to, according to the invention; and [0063]
  • FIG. 24 is a schematic block diagram of a system utilizing the methods of the current invention to support mobility of personal data devices as well as wireless handsets, according to the invention.[0064]
  • DETAILED DESCRIPTION OF THE INVENTION
  • FIG. 1 illustrates the basic components and operation of an exemplary, [0065] overall communication system 100. A Base Station 101 of a cellular system covers a cell 111 having a relatively large coverage area 111. (The Base Station 101 is shown off-center in its coverage area 111, and the coverage area 111 is shown as elliptical rather than circular, for illustrative clarity.) Base Stations 107, 108 and 109 of a WPBX system cover cells 102, 103 and 104, respectively, each having relatively smaller coverage areas. (The Base Stations 107, 108 and 109 are shown off-center in their respective coverage areas 102, 103 and 104, for illustrative clarity.) Sometimes, these smaller cells 102, 103 and 104 are referred to as “microcells”, or “picocells”, or “minicells”.
  • A [0066] mobile handset 110 can communicate with the cellular Base Station 101 via a communication link 105 and, when it is in the coverage area of the WPBX, it also can use short-range communication link 106, to communicate with one of its Base Stations 107, 108 and 109. In this manner, a standard cellular handset 110, that is enhanced (additionally equipped) with a short-range communication link (e.g. Bluetooth wireless technology) can connect with the WPBX system whenever it is in range of one of the WPBX Base Stations 107, 108 and 109.
  • The WPBX system can also operate when there is no cellular coverage at all. And the [0067] handset 110 can be an ordinary cordless telephone handset. Therefore, the cellular Base Station 101 shown in FIG. 1 is optional, insofar as the WPBX system of the present invention is involved. In the main hereinafter, a handset which is an otherwise ordinary cordless telephone handset, equipped with a short-range communication link (e.g. Bluetooth wireless link) will be used to describe the invention.
  • In an office environment, a WPBX system improves availability of employees, who carry mobile handsets, and therefore reduces operational cost and increases productivity. In the home environment, a WPBX system enables the use of the standard cellular handsets instead of special cordless phones. [0068]
  • In the present invention, when the handset is the same as the cellular handset, the cost of equipment is lower then the cost of a standard WPBX which requires dedicated handsets. Since the WPBX handles calls between handsets connected to it, the communication charges are lower then when standard cellular communication is used for all the calls. [0069]
  • The [0070] handset 110 may indicate to the user that more then one service is available. The user decides which service to use (Cellular or WPBX). The ability to choose between services is a well-known feature in many mobile phones.
  • It should be understood that the [0071] handset 110 is merely an example of a “mobile unit” which can be any of a number of telephony, voice, computing or data devices which communicate via Base Stations, as described in greater detail hereinbelow. As used herein, “Mobile Units” are devices communicating wirelessly with (also referred to as “connected to”) Base Stations.
  • As illustrated in FIG. 1 (and ignoring the [0072] cellular Base Station 101 and link 105) the handset 110 is currently communicating with (connected to) the Base Station 108. The Base Stations 107 and 109 are each referred to as “neighboring” Base Stations since they are each adjacent to the Base Station 108 that the handset is currently connected to. The present invention deals largely with how communication with a Mobile Unit such as a handset is handed off (or passed off) from a one Base Station to another (neighboring) Base Station when the handset moves from one minicell to another minicell.
  • FIG. 2 illustrates the main components and architecture of a [0073] WPBX system 200 suitable for use as the WPBX system of FIG. 1. The architecture of a WPBX system generally resembles the architecture of a cellular system. However, as described in greater detail hereinbelow, the function that each component performs is different, since the current invention deals with short-range communication with mobile units that have no built-in support for handoff.
  • The [0074] WPBX 200 comprises a plurality (three shown) of Base Stations 123, 124, 125. A handset 121 communicates via a short-range communication link 122 (e.g. Bluetooth wireless link) with Base Station # 1 123. Base Station # 2 124 and Base Station # 3 125 are ready to receive the call should handset 121 move into their coverage area. At the same time, the other Base Stations may participate in calls with other handsets. For example, Base Station # 2 124 communicates via a short-range communication link 134 (e.g. Bluetooth wireless link) with a handset 133. The handsets 121 and 133 may communicate with each other via the WPBX (as opposed to directly with one another), as described in greater detail hereinbelow.
  • Communication links [0075] 126, 127, 128 connect the Base Stations 123, 124, 125 with one another, as illustrated. These communications links transfer data between the Base Stations 123, 124, 125, including voice communication, data communication, connection status information and synchronization information, as described in greater detail hereinbelow, and may be RF links or land lines (e.g., copper wires, optical fibers, etc.).
  • Communication links [0076] 130, 131, 132 connect the Base Stations 123, 124, 125, respectively, with a Central Switch (hereinafter “Switch”) 129. These communication links enable the Switch 129 to control the operation of the Base Stations and to participate in the higher levels of the communication protocols, as described in greater detail hereinbelow, and may be RF links or land lines.
  • FIG. 3A illustrates the addition of a [0077] Gateway 135 to the WPBX system 200 of FIG. 2. The Gateway 135 connects the Switch 129 to a Public Switched Telephone Network (PSTN) 136. This enables the WPBX system 200 to receive incoming calls from and to send outgoing calls to other telecommunication systems (not shown) which are connected to the PSTN. The Gateway 135 may be implemented in any suitable manner, such as in hardware and/or software.
  • As used herein, a “Gateway” is a logical or physical connection between two different communication networks. The term implies a need for conversion of some aspect of the information or communication in order to operate, as contrasted with a “port” which implies a point not requiring significant conversion of the message or information. Gateways are well known. [0078]
  • FIG. 3B illustrates the addition of a [0079] Gateway 137 to the WPBX system 200 of FIG. 2. The Gateway 137 connects the Switch 129 to a standard Private Branch Exchange (PBX) 138. This enables the WPBX system 200 to receive incoming calls from and to send outgoing calls to standard telephone sets 139 connected to the PBX 138. As illustrated, the PBX 138 is interfaced with the PSTN 136. Thus, the WPBX system 200 can also communicate with other telecommunication systems (not shown) which are connected to the PSTN.
  • Having dedicated connections for all the [0080] Base Stations 123, 124, 125 and the Switch 129, such as illustrated in FIG. 2, hereinabove, is generally not cost-effective. Rather, when real time interaction or synchronization is not required, a shared local network, for example a local area network such as the IEEE 802.2 Ethernet, can connect these units in a cost-effective manner.
  • FIG. 4 illustrates a plurality (three shown) of [0081] Base Stations 123, 124 and 125 (compare FIG. 2) connected via a communications link which is a Local Area Network (LAN) 140 which handles the transfer of information between the Base Stations 123, 124, and 125, the Switch 129 and, in this example, the Gateway 135 to the PSTN 136. Using a standard local area network (LAN) as the communication backbone allows simple integration with other telephony application servers (not shown), such as IVR (interactive voice response), voice loggers, voice mail and billing systems. The LAN 140 can be either wired, or wireless.
  • FIGS. 2, 3A, [0082] 3B and 4 therefore illustrate, in a general manner, a number of ways in which the main components of a WPBX can be connected with one another, and interfaced with other communications systems (PSTN, PBX, etc.)
  • For office WPBX applications the [0083] Switch 129 may be a standard computer that has the processing power required for handling the switching of hundreds of calls simultaneously. It should support operation in a multi-server environment. This can be achieved with standard server hardware. For home WPBX applications, the Switch 129 may be a part of one Base Station, or a part of several Base Stations.
  • Call Setup Procedures [0084]
  • FIGS. 5, 6 and [0085] 7 illustrate call setup procedures for a single call at an “originating” Base Station (e.g., 123), at a “receiving” Base Station (e.g., 124), and at the Switch (e.g., 129), respectively. Call setup between the handset (e.g., 121) and the Base Station it is connected to (e.g., 123) is suitably performed according to standard telephony protocols, for example ITU-T Q.931. A similar protocol is a part of the Bluetooth protocol stack. However, the present invention is not limited to a specific protocol for call setup.
  • FIG. 5 illustrates a call setup procedure performed by an originating Base Station (e.g. [0086] 123) when a handset (e.g., 121) that is connected to it, tries to initiate a call. As shown in the step 151, the handset that is originating the call sends a destination number (DN). In a next step 152, the originating Base Station (e.g., 123) checks whether the destination handset (e.g., 133) is in its “Base Station Connection Table”—in other words, whether the destination handset is in the originating Base Station's coverage area. If not (step 152, “N”), in a step 160 the destination number (DN) is sent via the communications link (e.g., LAN 140) to the central WPBX Switch (e.g., 129). The originating Base Station then sets a timeout (step 161), and waits for a reply from the Switch. The timeout set in the step 161 is suitably on the order of up to 5 seconds. Next, it is determined in a step 162 whether there is a timeout.
  • If there is a timeout ([0087] step 162, “Y”), the Base Station sends a busy indication (suitably a tone) to the originating handset (step 177), and the Switch is updated about the failure of the call (step 178). If, there is not a timeout (step 162, “N”), the originating Base Station receives (from the Switch) the address of a destination Base Station (step 163). The originating Base Station then calls the destination Base Station (step 164), and it also calls all the neighbors (neighboring Base Stations) of the destination Base Station (step 180). Then the originating Base Station sets a timeout (step 165) and waits for a reply from the called Base Station (and its neighbors). Calling more then one destination Base Station is preferred in order to overcome uncertainties during handoff. The timeout set in the step 165 is suitably on the order of up to 5 seconds. Next, it is determined in a step 166 whether there is a timeout.
  • If there is a timeout (step [0088] 166, “Y”), the Base Station sends a busy tone to the originating handset (step 177), and the Switch is updated about the failure of the call (step 178). If, there is not a timeout (step 166, “N”), and a reply from the destination Base Station is received, the originating Base Station checks if the call is connected (step 167), and then connects the originating handset (step 168), and updates the Switch about the success of the call (step 169).
  • If, in the [0089] step 163 the address of a destination Base Station is not received (N), it is determined (step 170) whether the destination of the call is the Switch itself. If so (step 170, “Y”), a procedure similar to that for sending a call to another Base Station is implemented, except that the call is sent to the Switch (step 171) and not to another Base Station. Then the originating Base Station sets a timeout (step 172) and waits for the Switch to reply (step 173). The timeout is suitably on the order of up to 5 seconds. Next, it is determined in the step 173 whether there is a timeout.
  • If there is a timeout ([0090] step 173, “Y”), the Base Station sends a busy tone to the originating handset (step 177), and the Switch is updated about the failure of the call (step 178). If the Switch responds that the call is connected, there is not a timeout (step 173, “N”), and the originating Base Station connects the handset (step 175), and updates the Switch (step 176) about the status of the call.
  • If it is determined that the destination handset is in the originating Base Station's coverage area ([0091] step 152, “Y”), and a busy signal is not returned (step 153, “N”), the originating Base Station then attempts (step 154) to connect the call to the destination handset, and also to all the neighboring Base Stations (step 181). Again, the calling of neighboring Base Stations is preferred in order to overcome uncertainties, such as the handset moving, during the call setup. Then the originating Base Station performs a procedure similar to that described hereinabove of setting a timeout (step 155), waiting for the Switch to reply (step 156), connecting (step 158) or disconnecting (step 177) the call, and updating the Switch (steps 159 or 178).
  • In summary, the call setup procedure performed by an originating Base Station (e.g., [0092] 123) is that, first, the originating Base Station determines whether a call request from an originating handset (e.g., 121) is:
  • a. to a DN in the originating Base Station's coverage area (e.g., step [0093] 152), in which case the originating Base Station attempts (step 181) to also connect the call to its neighboring Base Stations; or
  • b. to a DN in another Base Station's coverage area (e.g., step [0094] 164), in which case the originating Base Station attempts (step 180) to also connect the call to Base Stations which are neighbors of the destination Base Station; or
  • c. to a DN outside of the WPBX coverage area and is to be routed through a Gateway (see FIG. 7) associated with the Switch ([0095] steps 170, 171).
  • In each case, the originating Base Station then: [0096]
  • d. sets a timeout ([0097] steps 155, 165, 172);
  • e. waits for the Switch to reply ([0098] steps 156, 166, 173) that the call is connected ( steps 157, 167, 174)
  • f. connects the originating handset ([0099] steps 158, 168, 175);
  • g. updates the Switch ([0100] steps 159, 169, 176) about the status of the call; and
  • h. waits (step [0101] 179) for a new event (a new call setup).
  • FIG. 6 illustrates the call setup procedure performed at a destination Base Station (e.g., [0102] 124) which is receiving a call, whether it be from another Base Station or from the Switch. When the destination Base Station receives a request (step 201) to connect a call to a handset (e.g., 133) which is reportedly within its coverage area, it first checks (step 202) whether the handset is already communicating with (connected to) it. If the handset is already connected to the Base Station (step 202, “Y”), the Base Station tries to connect the call to the handset. A timeout is set (step 203), again on the order of up to 5 seconds, and the Base Station waits (step 204).
  • If a time-out occurs ([0103] step 204, “Y”), or if a timeout does not occur (step 204, “N”) but the call was unable to connect (step 205, “N”), the destination Base Station returns an indication (step 208) of call setup failure (“unable to connect”) to the originating Base Station (or to the Switch, as the case may be). If, however, the connection succeeds (step 205, “Y”) the Base Station returns an indication (step 206) of successful call setup (“call connected”) to the originating Base Station. In either case (call connected, unable to connect), the destination Base Station sends similar indications ( steps 211, 212, respectively) to all the neighboring Base Stations of the originating Base Station Again, sending the reply to the neighboring Base Stations is to overcome uncertainties during handoff. In both cases the Switch is updated at steps 207 and 209, respectively. Finally the Base Station waits (step 210) for a new event (a new call setup).
  • FIG. 7 illustrates the call setup procedure performed at the Switch (e.g., [0104] 129). The Switch handles two types of messages, one is a request to establish a new call, and the other is an update to the status of the call. In a step 231, it is determined whether the request is for a new call (step 231, “Y”) or a request to update a call (step 231, “N”).
  • If the arriving message is a request to update a call ([0105] step 231, “N”), an update of the “Calls Table” is generally required (step 254, “Y”). The Switch checks if it receives indication that the call is connected (step 255). If the call is connected, (step 255, “Y”), the status of the call is updated in the Calls Table (step 256). Otherwise (step 255, “N”), the call is removed from the Calls Table (step 257).
  • If the arriving message is a request to initiate a new call ([0106] step 231, “Y”), the Switch checks if the call is intended to a handset connected to the WPBX (step 232). This is done by checking its “Connections Table”. If the call is intended to connect to outside the WPBX (e.g., via the PSTN 136), the Switch checks (step 233) if the destination number (DN) is a legal (valid) number. If the DN is a valid number (step 233, “Y”), in a step 234 the Switch transfers the call to the Gateway (e.g., 135), sets a timeout (step 235) and waits (step 236). If not (step 233, “N”), the program exits.
  • If the connection via the Gateway succeeds ([0107] step 236, “N”), it is whether the call is connected determined (step 237). If the call is connected, (step 237, “Y”), the Switch requests from the originating Base Station to transfer the call to the Switch (step 238), and waits for connection with originating Base Station (steps 239, 240). If connection succeeds, and the call is connected (step 242, “Y”), the call is added to the “Calls Table” (step 243), and the call is routed to the Gateway (step 244). If connection fails (step 240, “Y”; or step 242, “N”), the connection with the Gateway is disconnected (step 241).
  • If the call destination is one of the Base Stations (step [0108] 259), its source may be another Base Station (step 249), or the Gateway (step 245). If the source is another Base Station, the Switch send to the originating Base Station the address of the destination Base Station, and adds the call to the “Calls Table”. If the call arrived from the Gateway the Switch tries to connect the call to the destination Base Station (step 245). If is succeeds the call is added to the “Calls Table” (step 252), the call is transferred to the destination (step 253). If it fails the connection with the Gateway is disconnected.
  • The procedure described in FIG. 7 is also applicable to the case when more than one Gateway connects to the WPBX to the PSTN—for example, in a case where two branch offices share a single WPBX, and each has its own independent connection to the PSTN. The main difference would be that when the Switch handles an outgoing call, it will determine to which Gateway to send the call. This can either be done randomly, or can be pre-determined. The handling of the incoming calls would proceed as set forth above in FIG. 7. [0109]
  • FIGS. 5, 6 and [0110] 7 have illustrated a call setup procedure for the handling of a single call. When either the Base Stations or the Switch need to handle more then one call, several instances of these procedures can be run in parallel. For that purpose, both Base Station software and Switch software are preferably based on a real time operating system that supports multi-tasking. For each new call, a new task will be created, and the task will perform the procedures described in FIGS. 5, 6 and 7. The task will be closed when the procedure is completed.
  • In systems with a very large number of Base Stations, due to limited processing power of each Switch, it may be preferable to divide the Switch into two or more units. Dividing the Switch into several units can also improve the reliability of the WPBX, by eliminating the possibility of having a single point of failure shutting down the entire system. [0111]
  • FIG. 22 illustrates the division of the Base Stations, into two groups; a first group (Group A) [0112] 1050 comprising a plurality (four shown) of Base Stations 1050 a, 1050 b, 1050 c and 1050 d; and a second group (Group B) 1051 comprising a plurality (four shown) of Base Stations 1051 a, 1051 b, 1051 c, 1051 d. The Base Stations of Group A are connected to a first Switch (Switch A) 1052, and the Base Stations of Group B are connected to a second Switch (Switch B) 1053. The Base Stations and the Switches function according to the procedures described in FIGS. 5, 6 and 7. All the Switches mirror all the status tables of the other Switches, i.e. by having copies of each other's “Calls Table” and “Connections Table”. When a Switch updates one of its status tables, it sends the information to all the other Switches, and they update their tables accordingly. In order for this process to be reliable, the other Switches will send an indication that the message was received. If the originating Switch does not receive such a reply within T1 milliseconds, it will retransmit the message. The retransmission will be repeated up to P times. For example T1 shall be equal to 100, and P shall be equal to 5.
  • It is within the scope of the invention that more than two Switches, and corresponding more than two groups of Base Stations can be employed. As described hereinabove, all of the Switches would mirror and update each other's status tables. The description of two [0113] Switches 1052 and 1053 is intended to be exemplary rather than limiting.
  • Calls Table [0114]
  • The Switch ([0115] 129) maintains the “Calls Table”, which contains the status and information about all the active calls being handled by the WPBX. The “Calls Table” comprises the following information:
  • 1) Each active call has a unique “Call Identification number”. [0116]
  • 2) The origin of the call, which can be either “Internal” or “External”. [0117]
  • 3) The destination of the call, which can be either “Internal” or “External”. [0118]
  • 4) “Calling Number Identification (CNID)”, the number of the calling party, if available. [0119]
  • 5) Destination Number (DN), the number of the answering party if available. [0120]
  • 6) “Originating Base Station Identification” for calls from internal origin [0121]
  • 7) “Destination Base Station Identification” for calls with internal destination, [0122]
  • 8) Status of call—initiated, connected, disconnected. [0123]
  • 9) Additional information for billing, performance analysis, such as call starts time, number of handoffs, time since last handoff, etc. [0124]
  • The “Originating Base Station Identification” and the “Destination Base Station Identification” are updated when a handset moves from one Base Station to another. The Switch updates these fields when it determines that the handoff should occur. During handoff, for a short time, there may be uncertainty about the validity of these fields. The Base Stations compensate for the uncertainty by “multicasting” the call setup messages to a group of Base Stations, as described hereinabove with respect to FIGS. 5 and 6 (see, e.g., steps [0125] 180, 181, 211, 212).
  • The procedures described above do not limit the WPBX from handling all unique telephony features that the Gateway and the handsets can support. For example, multiple connections can be created between handsets, and between handsets and the Gateway, when each connection is treated as a separate call. Another example is “Caller ID”, that the Gateway can send to a handset. Another example is a “Hook-Flash” (momentary disconnect) that the handset can pass to the Gateway. The WPBX acts as a transparent relay for all these telephony features. [0126]
  • High-Level and Low-Level Protocols [0127]
  • In the descriptions set forth hereinabove, it has generally been assumed that: [0128]
  • 1. Each Base Station knows which handsets are in its coverage range. [0129]
  • 2. The Switch is aware of the connections of all the Base Stations. [0130]
  • 3. Connections appear static to users and also to the high-level call setup procedures described above. [0131]
  • A method to achieve mobility, which fulfills these three assumptions is described in detail, hereinbelow. [0132]
  • According to the invention, the short-range communication protocol stack is divided into two parts: [0133]
  • low-level protocols performing real time tasks, and [0134]
  • high-level protocols that do not have real time requirements. [0135]
  • For example in the Bluetooth short-range communication protocol stack, the low-level protocols are the radio frequency (RF) transmitter and the base-band controller. The base-band controller performs real time control over the RF, since the Bluetooth protocol utilizes frequency-hopping transmission. The base-band protocol also determines, for each time slot of transmission (i.e. each frequency hop), what information will be transmitted. The base-band protocol also deals with voice coding, error correction, encryption and authentication. For example, higher level protocols of the Bluetooth stack include the “Link Manager” which determines what information will go through the channels created by the “Base-Band”, and determines the state of operation (e.g. Active, Polling, Parked). [0136]
  • The low-level protocols that require real time capabilities are performed in the Base Station. The higher-level protocols are performed at the Switch. (However, as described hereinbelow, certain high-level protocols can also be performed in the Base Station, even though they do not require real time capabilities.) The Switch handles the routing of data from the higher-level protocols to the lower level protocols. (A call routing task ([0137] 282) is described in greater detail hereinbelow.) Therefore, the higher-level protocols do not need to “know” in which Base Station the lower level protocol that they are controlling is being performed.
  • FIGS. 8A and 8B illustrate an example of a [0138] WPBX system 800 with two handsets 121 and 133, two Base Stations 123 and 124, and one Switch 129. In this example, two calls are being handled. Gateways (e.g., 135, 137) are omitted, for illustrative clarity. As mentioned hereinabove (see, e.g., FIG. 22), the Switch can be divided into several units.
  • As illustrated in FIG. 8A, the [0139] handset 121 is currently communicating with (connected to) the Base Station 123, and the handset 133 is currently communicating with the Base Station 124. An instance 280 of the low-level protocol is running on the Base Station 123, and another instance 281 of the low-level protocol is running on the Base Station 124. Each instance of the low-level protocol supports only one call. In a similar manner, the Switch 129 handles an instance 283 of the high-level protocol for the call with the with the handset 121, and another instance 284 of the high-level protocol for the call with the handset 133. A single call routing task 282 handles the data that is transferred between the instances of the low-level protocols and the high-level protocols to the correct destination.
  • As illustrated in FIG. 8A, the [0140] call routing task 282 routes data arriving from instance 280 of the low-level protocol to instance 283 of the high-level protocol, and from the instance 281 of the low-level protocol to the instance 284 of the high-level protocol. Since interaction between the high-level-protocol and low-level protocol, is normally relatively rare (e.g. call setup), there are no strict real time requirements from the call routing task. The call routing task 282 is described in greater detail hereinbelow, with respect to FIG. 12.
  • As illustrated in FIG. 8B, the [0141] handset 133 is shown as having moved to the area covered by the Base Station 123. The Base Station 123 will handle the communication with the handset 133, by creating a copy 281′ of the instance 281 of the low-level protocol, that previously ran on Base Station 124. This allows the handset 133 to continue communication without “knowing” that a changeover of Base Stations has occurred. The call routing task 282 will now route the data arriving from the instance 281′ of the low-level protocol running on Base Station 123 to the instance 284 of the high-level protocol 284 which is running on the Switch 129.
  • For each connection of a Base Station with a handset, there is a separate instance of the low-level protocol running at a Base Station connected to the handset, and a corresponding separate instance of the high-level protocol running at the Switch. These instances are created, on an as-needed basis, when a connection is initiated. Preferably, a real time multi-tasking operating system is used in order to allow handling of many instances of the protocols simultaneously in the Base Stations and in the Switch. The procedures that the Switch uses during initiation of a connection and later, during handoff, are discussed in greater detail hereinbelow. [0142]
  • Synchronization of Base Stations During a Handoff [0143]
  • There follows a description of procedures that are performed during handoff of a call from one Base Station to another Base Station. The Base Station with which a handset is currently connected is termed the “current” Base Station. The Base Station to which a handset is being handed off is termed the “next” Base Station, and is typically a “neighboring” Base Station. Once the handoff has occurred, this neighboring/next Base Station becomes the “current” Base Station and the Base Station from which the handset has moved becomes the “previous” Base Station. [0144]
  • According to an aspect of the invention, the handsets do not need to be (and preferably are not) specially equipped or enabled to support mobility (i.e. handoff). Therefore, when a handset moves from one Base Station to another, the current and the next Base Stations are responsible for continuing the communication with the handset, preferably with no noticeable interruption in the communication, and the next Base Station to which the handset has moved should transmit substantially exactly as the previous Base Station from which the handset has moved would have transmitted. For purposes of the discussion of this example, it is assumed that it is known from which Base Station the handset has moved and to which Base Station the handset is moving, and that the exact timing of handoff is also known. These issues are discussed in greater detail hereinbelow. [0145]
  • FIGS. 9A, 9B and [0146] 9C illustrate, in a general manner, a handoff taking place between two Base Stations 123, 124 and a single handset 121 of a WPBX.
  • FIG. 9A illustrates the [0147] handset 121 communicating with (connected to) a Base Station (Base Station #1) 123 via a short-range communication link 122 (e.g. Bluetooth wireless link). The “current” Base Station 123 sends call parameters and rough synchronization information over the LAN 140 to the neighboring Base Stations, a one of which is shown as Base Station # 2 124. In this manner, the neighboring Base Stations “know” that they are “candidate” Base Stations for receiving a handoff of the call from the current Base Station. The information which is broadcast by the current Base Station to the candidate next Base Stations includes low-level communications protocol states and parameters, discussed in greater detail hereinbelow. This communication from the Base Station 123 to the Base Stations 124 is indicated by the arrow 141, and the information contained therein is used to achieve rough (coarse) synchronization between the Base Stations. Since this information does not need to be accurate in time, it can be transmitted over the data link (e.g., LAN 140) connecting all of the Base Stations.
  • FIG. 9B illustrates a handoff as it is about to take place. Here, the [0148] handset 121 is situated in an area covered by both Base Stations 123 and 124. Base Station 124 uses this situation to achieve exact (fine) synchronization with the current Base Station 123. This will enable the next Base Station 124 to transmit, after the handoff, substantially exactly as previous Base Station 123 would have transmitted if the handoff had not occurred. A method for effecting this fine synchronization between neighboring Base Stations is discussed in greater detail hereinbelow.
  • An important parameter of synchronization is Time Of Day (TOD), which can be determined with virtually any desired level of precision (e.g., microseconds). As described in greater detail hereinbelow, in order to achieve fine synchronization of TOD, the [0149] Base Station 124 that is waiting for the handset 121 may passively monitor the transmissions of either the handset 121, or of the Base Station 123 that is currently connected with the handset. In FIG. 9B, the two possible fine synchronization signals that the candidate next Base Station # 2 124 can monitor are shown, a signal 142 originating from the Base Station # 1 123, and another signal 143 originating from the handset 121.
  • FIG. 9C illustrates that synchronization of the [0150] Base Stations 123 and 124 may alternatively be achieved by use of a beacon signal from a beacon transmitter 299 which is within range of current and next Base Stations, in which case precise (fine) synchronization for the low-level protocols can also be achieved. The beacon transmitter 299 transmits a beacon signal 144 to both of the Base Stations 123 and 124 to achieve synchronization of the Base Stations. This method allows for the synchronization of many Base Stations, although only two are illustrated in this figure. In this case, there is no need to transmit synchronization information over the LAN 140. Only call parameters (e.g., low-level protocol) need to be communicated between the current Base Station and the neighboring candidate next Base Stations, as indicated by the arrow 141′.
  • Bluetooth Short-Range Wireless Communication Protocol [0151]
  • As discussed hereinabove, a short-range communication protocol with the handset can be divided into lower-level protocols which the Base Stations handle, since they have real time requirements, and higher-level protocols which the Switch handles since they do not require real time requirements. Bluetooth wireless technology is an example of such a short-range communication protocol. In Table 1, a division of the Bluetooth short range wireless protocol into such low-level and high-level protocols is presented. [0152]
    TABLE 1
    Communication Protocols
    Element Description of Protocol Real time Level/
    (Protocol Name) (Bluetooth Protocol) requirements Where
    Radio Frequency Defines the modulation scheme Control of radio Low/
    (RF) and the frequency range frequency in real Base Station
    time required,
    modulates each
    symbol
    Base-band Frequency control, channel Control frequency Low/
    definition, transmission/ hopping in real time. Base Station
    reception control, encryption, Determines what
    error correction, authentication. packet will be sent at
    each hop.
    Encryption/Error
    correction for each
    hop. Accurate time
    synchronization
    Link Manager Link setup and control None Low or High
    Base station
    or Switch
    Host Controller Communication between None Low or High
    Interface protocol stack and lower level Base station
    implementation or Switch
    Logical link High level protocol None High/
    manager multiplexing, packet Switch
    segmentation and Reassembly,
    quality of service management
    Service Locating a service available by None High/
    discovery a Bluetooth device Switch
    RF COMM A subset of the ETSI TS 07.10 None High/
    standard, emulation of serial Switch
    port over the Logical link
    manager
    Ird Interoperability for applications None High/
    Interoperability over Bluetooth and infra-red Switch
    protocols
    Telephony Call control signaling and none High/
    control protocol establishment of speech and Switch
    data calls between Bluetooth
    devices.
    Interoperability Bluetooth protocol with PPP as none High/
    requirements for communication bearer for WAP Switch
    Bluetooth
    technology as
    WAP bearer
    Host control Command interface to the none High/
    Interface base-band controller and link Switch
    manager, and access to status
    information
    Generic Access Generic procedures for none High/
    Protocol Discovery of services and Switch
    connection of Bluetooth devices
    Service Procedures for an application in none High/
    discovery a Bluetooth device to discover Switch
    application the services in other Bluetooth
    profile devices
    Cordless Procedures in an all in one none High/
    Telephony handset Switch
    Profile
    Intercom Profile Support for intercom feature in none High/
    an all in one handset Switch
    Serial Port Procedure for emulation of none High/
    Profile serial cable Switch
    Headset Profile Headset use over Bluetooth none High/
    wireless link Switch
    Dial up Support for dial up networking none High/
    Networking in a device with Bluetooth Switch
    Profile wireless technology
    FAX Profile Support for fax transmission or none High/
    reception on a device with Switch
    Bluetooth wireless technology
    LAN Access Defines how device with none High/
    Profile Bluetooth wireless technology Switch
    can access a LAN with PPP
    Generic Object Defines the possibility of none High/
    Exchange Profile Generic Object Exchange Switch
    Object Push Support for object push model none High/
    Profile Switch
    File Transfer Support for file transfer none High/
    Profile Switch
    Synchronization Synchronization of Bluetooth none High/
    Profile enabled device, e.g. PDAs Switch
    Laptops
  • Table 1 shows the elements of the Bluetooth protocol, generally, as currently implemented. Other profiles may be added in the future (or may have already been added), and it is anticipated that these profiles will be high-level protocols, which do not have strict real time requirements. [0153]
  • As shown in Table 1, the Link Manager and the Host Controller Interface can be implemented in either the Base Station or in the Switch. Although the Link Manager and Host Controller Interface, do not require real time performance, they may readily be implemented in the base-band controller of the Base-Station. It is within the scope of the invention that any of the high-level protocols can also be implemented in the Base Station as part of the low-level protocol, but then they will take part in the handoff. [0154]
  • According to the inventive technique of dividing the low-level and high-level protocols, the high-level protocols are “buffered” from the occurrence of handoff by the Base Stations and the routing task that runs on the Switch. Therefore, the present invention allows mobility of any device with Bluetooth wireless technology that supports any of the high-level protocols (e.g. LAN access, WAP, FAX, FTP). The solution for mobility of cordless phones, described hereinabove, is only an example of how the methods can be utilized. [0155]
  • As described hereinabove with respect to FIGS. 8A and 8B, different instances of the low-level protocols that represent the same connection (e.g., [0156] 281, 281′) need to be synchronized. Table 2, presents elements (parameters) of the low-level protocols that the Base Stations will synchronize. For each element, it also shows whether rough or fine synchronization is required. Again, the protocols are described, by way of example, in the context of the Bluetooth short-range communication protocol.
  • Rough synchronization may be achieved via the local area network (see, e.g., [0157] LAN 140, FIGS. 9A and 9B) connecting the Base Stations. Fine synchronization may be achieved by other methods described in greater detail hereinbelow.
    TABLE 2
    Low-Level Protocol Synchronization
    Element/ Synchronization
    Parameter Description method
    device address The unique address of the Base Station, Via LAN
    determines the hopping sequence, effects
    the encryption and authentication keys.
    TOD Time Of Day, measured in micro-seconds, Rough
    it determines the exact timing of the synchronization via
    hopping sequence LAN, fine
    synchronization by
    other methods
    SCO Synchronous voice channels allocation Via LAN
    FEC Forward error correction parameters Via LAN
    Encryption key Use to encrypt data and voice Via LAN
    Authentication key Used to initiate a connection Via LAN
    Voice coding Method of voice coding: CVSD or PCM Via LAN
    AM_ADDR Address of member in a picocell Via LAN
    PM_ADDR Address of a parked handset (energy saving Via LAN
    mode, when the handset is inactive)
    ACL Definition of the asynchronous data link Via LAN
    FIFO Data FIFOs Flush of data, and
    using flow control
    to halt data during
    handoff
  • All the parameters listed in Table 2, except for the TOD, can be sent prior to handoff, thorough the local area network (e.g., LAN [0158] 140), or any other communication link connecting the Base Stations. As described hereinabove with respect to FIG. 9A, rough (coarse) TOD can also be sent through the LAN.
  • If one of the other parts of the Bluetooth protocol stack is also implemented in the Base Station, then it will also take part in the handoff. Synchronizing the instances of the same protocols in different Base Stations is done as described above, by sending internal state parameters via the local area network (LAN [0159] 140). For example, by implementing the Link Manager and Host Controller Interface in the Base Station, the internal state parameters of these protocols will be broadcast to the neighboring Base Stations, by the Base Station that is connected to the handset.
  • Fine Synchronization [0160]
  • As mentioned hereinabove, in order to achieve fine synchronization of TOD, the Base Station that is waiting for the handset, should passively monitor the transmission of the handset and/or the Base Station that is currently connected with the handset. In FIG. 9B, the two possible signals that the receiving (next) [0161] Base Station 124 can monitor are shown, one originating from Base Station 123, and the other originating from the handset 121 which is currently connected to the Base Station 123.
  • According to the invention, the [0162] next Base Station 124 can be finely synchronized by receiving synchronization signals from the current Base Station 123. Normally, the Base Station 124 does not receive signals from the Base Station 123. Therefore, to facilitate the Base Station 124 receiving synchronization signals from the Base Station 123, Base Station 123 periodically transmits with higher transmission power than during normal transmission. This allows the Base Station 124 to receive transmissions from Base Station 123, without a substantial increase in spectral contamination. The inventive technique is described in the context of frequency-hopping. Frequency-hopping techniques are well known, including techniques that change frequency with each hop.
  • FIG. 10 illustrates a technique for controlling the transmission power of a Base Station (e.g., [0163] 123) that is currently connected with the handset, for a plurality (series) of successive hops 290. The vertical axis of the graph is the Base Station's transmission power (in arbitrary units), and the horizontal axis is time. Th is the duration of a hop 290. In this example, the hops 290 all have equal duration. Tp is the time interval between successive hops (or “hop time slot”) and, in this example, the intervals between successive hops are constant (evenly spaced in time). The normal transmission power for each hop 290 is P0. For example, in a short-range communication system, the normal transmission power P0 of a Base Station is suitably on the order of a hundreds of milliwatts.
  • According to the invention, in order to effect synchronization between a Base Station and its neighboring Base Stations, every [0164] Kth hop 290′ is a “synchronization” hop that is transmitted with increased power P1. P1 is suitably substantially (e.g., 2-10 times) greater than P0. In the case that the transmitter changes the transmission frequency in each hop, every Kth (synchronization) hop will also be transmitted at a different frequency.
  • Alternatively, it is within the scope of the invention that a variable time interval (Tp) is provided between the synchronization hops [0165] 290′ that are transmitted with high power P1. For example a changing K (that shall be denoted by K(n), i.e. K for hop number ‘n’), can be generated by a pseudo random sequence such as a maximal length shift register sequence. Pseudo random sequences are well known for use in communication systems.
  • In the case that a beacon transmitter (e.g., [0166] 299) is used (in addition to signals received from the Base Station and handset) to synchronize the Base Stations (see, e.g., FIG. 9C), it can suitably transmit the beacon signal once in K hops, and K can either be constant or it can be changed over time (variable), as described above.
  • Low-Level Synchronization at the Base Station [0167]
  • FIG. 11 illustrates major components of a [0168] Base Station 1100 waiting for handoff, and a method of accurately synchronizing the TOD at the Base Station to the TOD of the Base Station which the handset is about to leave, including:
  • [0169] Time Clock 310;
  • [0170] TOD counter 303;
  • [0171] Antenna 301;
  • [0172] Receiver 305;
  • [0173] Frequency Hopping Generator 304;
  • [0174] Emulator 307;
  • [0175] Correlation Detector 308; and
  • Adder (ADD) [0176] 309;
  • all connected as illustrated in the figure and as discussed hereinbelow. [0177]
  • As described hereinabove with respect to FIG. 9A, a rough TOD from the Base Station currently connected with the handset is available to the (next) Base Station waiting for a handoff on a communication link such as the [0178] LAN 140. This rough TOD is provided to the TOD counter 303 (e.g., via an interface to the LAN 140). A Time Clock 310 generates clock signals for incrementing the TOD counter 303. The output of the TOD counter 303 is therefore a rough estimate of the TOD (“TOD Estimate”). There is an uncertainty (margin of error) “Tu” between the rough estimate of TOD and the actual TOD, and which depends on the transmission latencies thorough the LAN 140. “Tu” is readily calculated for a given WPBX system, according to its physical configuration.
  • From the rough estimate of the TOD output by the TOD counter and the device address (“Commonly denoted by Media Access Control Address, or MAC address”,), a frequency-hopping list is generated by a frequency-hopping [0179] generator 304 and supplied to an emulator 307 which emulates the output of the receiver 305. In a window with size of 2·Tu, a single frequency from the hopping sequence is chosen, and the receiver 305 will wait on this frequency for duration of 2·Tu. Once in a period of 2·Tu, the receiver 305 will switch frequency, in response to a signal generated by the frequency-hopping generator 304. Opening an acquisition window of 2·Tu ensures that during this time duration the receiver 305 will capture at least one hop. A correlator/detector 308 receives the receiver's output (e.g. a base-band or intermediate frequency signal) and an emulation 307 of the signal that should appear at the receiver's output. The output of the receiver 305 can be emulated, since a rough estimate of the TOD is available, and also from the hopping frequency list, and the receiver frequency list. The emulator 307 continuously checks for a match between receiver frequency and the hopping frequency and, when it finds a match, it reports the frequency and the time (rough TOD) to the correlator/detector 308. By comparing the actual received signal with the emulation that is based on the rough TOD, the correlator 308 computes (and outputs) a fine estimate of the TOD offset (i.e., the error between the TOD estimate and the actual TOD), and provides this to Adder 309, which also receives the rough TOD estimate from the TOD counter 303 and generates a signal (“Fine TOD”) indicative of the actual TOD. Correlator-based time offset measurement is a standard estimation method that is described in many textbooks, and an example of its implementation is described in greater detail hereinbelow.
  • Since the Base Station to which the call is to be handed “knows” which call it is going to receive, and it has received the call parameter (via the LAN), and is able to accurately estimate the TOD, it will be able to perform a seamless handoff transmitting substantially exactly as the Base Station that the handset is about to leave. As mentioned above, an iteration of the low-level protocol (e.g., [0180] 281′) can be prepared at the receiving Base Station in anticipation of the handoff.
  • Call Routing Task ([0181] 282)
  • The higher-level protocols are run at the Switch, and are therefore “ignorant” of the handoff processes. At the Switch the “call routing task” [0182] 282 (FIGS. 8A, 8B) isolates the high-level protocols from the changing environment. The “call routing task” 282 maintains the “Connections Table”, which contains information about all the connections between handsets and Base Stations. Maintaining the Connections Table is described in greater detail hereinbelow. The following sections describe an example of how the Connections Table is used by the “call routing task” 282.
  • The following information is included in the Connections Table: [0183]
  • 1) Handset ID [0184]
  • 2) Current Base Station ID [0185]
  • 3) Handle (of instance) of high-level protocols [0186]
  • 4) Handle (of instance) of low-level protocols [0187]
  • 5) Number of candidate Base Stations for handoff [0188]
  • 6) List of candidate Base Stations for handoff [0189]
  • 7) List of Handoff status for each candidate Base Station (i.e., Idle/Started) [0190]
  • The messages that the high-level protocol (that runs on the Switch) and the low-level protocol (that runs on the Base Station), send each other have the following format: [0191]
  • 1) Message Header [0192]
  • Origin: [0193]
  • from low-level protocol [0194]
  • from high-level protocol [0195]
  • Handset ID [0196]
  • Base Station ID [0197]
  • Low-Level Protocol Handle in the Base Station (number of instance of low-level protocol) [0198]
  • High-Level Protocol Handle in the Switch, (number of instance of high-level protocol) [0199]
  • HEC (header error correction) [0200]
  • 2) Message Data [0201]
  • 3) CRC (Cyclic Redundancy Check) [0202]
  • FIG. 12 illustrates a method of implementing the “call routing task” [0203] 282 which was mentioned hereinabove with respect to FIG. 9A. The “call routing task” 282 is performed in the Switch 129.
  • In a [0204] first step 351, the call routing task 282 waits for a message from one of the high-level protocol instances running on the Switch 129 or from one of the low-level protocol instances running on the Base Stations (e.g., 123). Then, in a step 352, it is determined where the call came from.
  • If the message arrived from one of the Base Stations ([0205] step 352, “Y”), the call parameters are compared with the Connections Table (step 353) and the message is sent (step 354) to the instance of the high-level protocol running on the Switch (129).
  • If the message arrived from the Switch ([0206] step 352, “N”) the ID of the sending low-level protocol instance is located (step 353) in the “Connections Table”, and the message is sent (step 354) to an instance of a corresponding high-level protocol. If the message arrived from one of the high-level protocols (step 352, “N”), it is determined (step 360) whether a handoff has begun (is in progress). If a handoff is not in progress (step 360, “N”), the call parameters are compared with the Connections Table (step 358) and the message is sent to the Base Station on which the destination low-level protocol instance is running (step 359 ). If a handoff is in progress (step 360, “Y”) the call parameters are compared with the Connections Table (step 355) and the message is sent to the Base Station on which the destination low-level protocol instance is running (step 356). The message is also sent (step 357) to all the Base Stations that are candidates for handoff—e.g., neighboring Base Stations. The Base Stations receiving the message can then check if they are running the destination low-level protocol and, if not, the message is simply discarded. The procedure shown in FIG. 12 handles a single message. By using a multi-tasking operating system, it is possible to run several instances of these procedures, and thus handle more than one message simultaneously.
  • Detecting a Handset [0207]
  • The methods described thus far enable the communication protocols to continue operation when a handoff occurs. They rely on the ability to determine, which handset is in the coverage area of which Base Station, where a handset is moving, and when is the best time to perform handoff. By definition, handoff occurs between only two Base Stations, but for a certain time prior to the actual occurrence of the handoff there may be more than one Base Station that are candidates for handoff. Determining the candidates for handoff, which Base Station will actually participate in handoff and when to perform handoff requires collaboration of the Base Stations and the Switch. [0208]
  • As is evident from the discussions hereinabove, the handsets do not actively participate in the handoff operations. Therefore, the Base Stations will determine which handsets are in their coverage range, by either passively capturing transmission information, or by “tricking” the handset to transmit information that can be used for that purpose. [0209]
  • As discussed hereinabove, each Base Station will transmit, to all the neighboring Base Stations, information about the calls that are taking place in its coverage area. This information will include all the call parameters that can be sent through a low bandwidth communication link, such as the shared local area network (e.g., LAN [0210] 140). This information is sufficient for detecting which handset is moving from one of the neighboring Base Stations into the coverage area of a Base Station.
  • FIG. 13 illustrates major components of a Base Station [0211] 1300, waiting for handoff, and a method of accurately synchronizing the TOD at the Base Station to the TOD of the Base Station, which the handset is about to leave, and a passive method for detecting the arrival of a handset in a Base Station's coverage area during a call, including:
  • Three TOD counters [0212] 371, 380 and 384 (compare 303)
  • Antenna [0213] 382 (compare 301);
  • Receiver [0214] 379 (compare 305);
  • A [0215] Receiver Frequency Controller 375;
  • Three Hopping [0216] Sequence Generators 372, 373 and 374;
  • [0217] Three Emulators 376, 377 and 378;
  • [0218] Three Correlators 381, 382 and 383 (compare 308),
  • all connected as illustrated in the figure and as discussed hereinbelow. [0219]
  • FIG. 13 illustrates a passive method for determining which handsets' (i.e. handset which is participating in a call with a certain device address) transmissions is being received by a Base Station. [0220]
  • A plurality (“K”, three shown) of TOD counters [0221] 371, 380 and 384 are set when a rough TOD (“Rough TOD”) estimate is received, via the LAN (140), from other Base Stations. The counters 371, 380 and 384 are incremented by the TOD clock 310. Using the TOD and the device addresses (“Bluetooth Device Address”) that are connected to calls in which handsets in the neighboring cells (connected to neighboring Base Stations) participates, a corresponding plurality (“K”, three shown) of hopping frequency (sequence) generators 372, 373, 374 generate the list of frequencies in which the handsets are likely to transmit.
  • The [0222] receiver frequency controller 375 sets the frequency, which the receiver 379 will monitor. A plurality (“K”, three shown) of correlators 381, 382 and 383 is used to compare the energy at the receiver's output, to the emulation of the receiver's output. The output of the receiver can be emulated, since a rough estimate of the TOD is available, as well as the hopping frequency list, and the receiver frequency list. The emulator continuously checks for a match between receiver frequency and the hopping frequency, when it finds the match it reports to the correlator the frequency and the time. By comparing the actual received signal with the emulation that is based on the rough TOD, the correlator detect the presence of the transmitter and computes a fine estimate of the TOD offset (i.e., the error between the rough TOD estimate and the actual TOD). Correlator-based time offset measurement is a standard estimation method that is described in many textbooks, example of implementation shall be described later on. The number of handsets that can be detected simultaneously is equal to the number of hopping sequence generators, and the number of emulators of receiver output, and the number of correlators.
  • In FIG. 13 up to ‘K’ handsets can simultaneously be detected. The main advantage of the method described above is that since the detection is passive, there is no need to achieve fine synchronization between Base Stations. Another advantage of this passive method is that there is no need to decode the messages that the handset transmits, and therefore it is relatively easy to implement. [0223]
  • The [0224] receiver frequency controller 375 selects the frequency on which the receiver 379 will wait to “capture” hops. To increase the probability of detection, the receiver frequency controller 375 should be programmed to choose frequencies that are not blocked by interferences (e.g., interferences from other than Bluetooth transmitters). For each frequency that the receiver frequency controller 375 chooses, a histogram of the number of hops that have been detected in a certain duration of time, and their average signal-to-noise ratios are maintained by the receiver frequency controller 375. A measure of the spectral “cleanness” of a certain frequency can be determined as a function of the signal-to-noise ratios (SNRs) of the hops—for example, as the number of hops multiplied by the average signal-to-noise ratios (SNRs) of the hops.
  • The [0225] receiver frequency controller 375 preferably chooses a group of ‘M’ frequencies that have the best “cleanness” measure, and the receiver 379 waits on them most of the time, when once in T1 milliseconds the controller changes the frequency. Once in T2 milliseconds (T2 is selected to be much larger then T1) the receiver frequency controller 375 selects a frequency which is not in the group of ‘M’ best, and the receiver 379 waits on it for T3 milliseconds (T3 is selected to be smaller then T1). This enables the receiver frequency controller 375 to monitor the “cleanness” of frequencies that are not in the ‘M’ best frequencies. If the receiver frequency controller 375 detects a frequency that is cleaner then one of the ‘M’ frequencies that is in its list, it puts it in the list, instead of the frequency with the lowest “cleanness” measure. Typical values for the parameters M, T1, T2, T3 are 20, 250, 2500, 100, respectively.
  • Generally, the signal-to-noise ratio (SNR) or signal-to-interference ratio for each hop is measured by measuring the bursts of energy which match the expected hop duration, to all other signals that do not match the hop duration. The average noise level is continuously monitored. When the energy increases for duration ranging from Th−D to Th+D (Th is the nominal hop duration; D is a measurement “window” interval), the hop energy will be computed, and it will be added to the average hop energy. During the duration of the hop the average noise level is not be updated. Typical values for Th and D, are 0.65 milliseconds, and 1000 milliseconds respectively. [0226]
  • Another Method of Detecting a Handset [0227]
  • An alternative method for detecting a handset which enters the coverage area of a Base Station, is now described. This method is also passive, and also relies on a handset being engaged in a call in order to detect the handset. This method requires fine synchronization between the Base Stations and therefore is somewhat more complicated than the passive method previously described, but using this method has a few substantial advantages over the method previously described, including: [0228]
  • improved detection performance, [0229]
  • improved timing of handoff, and [0230]
  • the ability to detect a moving handset that is not currently participating in a call. [0231]
  • According to the invention, once in a while the Base Station that is currently communicating with the handset will “give up” (omit, yield to its neighbors) a short transmission duration, during which one or more neighboring Base Stations may transmit to the handset. In order for the handset to receive their transmission, the neighboring Base Station(s) must therefore be synchronized with the Base Station that is currently communicating with the handset, and during the time that the neighboring Base Station(s) transmits, it (they) acts as if it were the Base Station that has yielded a transmission slot for handset detection by the neighboring Base Stations. [0232]
  • This method can be illustrated in the context of the Bluetooth short-range communication, wherein frequency hopping is used. The Base Station that is currently communicating with the handset, will give up a single hop. Any of the neighboring Base Stations that are not close to each other may use the same hop to transmit to the handset. The neighboring Base Stations that are close to each other will use different hops to call (communicate with) the handset. This is illustrated in FIGS. 14A, 14B, [0233] 14C and 14D.
  • FIG. 14A, which is similar to FIG. 1, illustrates a wireless communication system [0234] 1400 (e.g., WPBX) having a Base Station 391 that is currently communicating with a mobile unit 390 that is a wireless telephone handset, and a plurality (six shown) of neighboring Base Stations 392, 393, 394, 395, 396 and 397 that are waiting (available) for the handset 390 to enter their coverage areas. Each Base Station 391, 392, 393, 394, 395, 396 and 397 has an area of coverage 391 a, 392 a, 393 a, 394 a, 395 a, 396 a and 397 a, respectively. The interconnections between the Base Stations, and between the Base Stations and a central Switch, such as shown in FIGS. 2 and 4, are omitted, for illustrative clarity.
  • FIG. 14B, which is similar to FIG. 10, illustrates that the [0235] Base Station 391 which is currently communicating with the handset 390, periodically (once in K hops) transmits with higher power P1, in order to enable the neighboring Base Stations to synchronize their TOD. According to the handset detection technique being discussed, the Base Station 391 also periodically (once in M hops) skips a transmission on a single hop 702, 703 (shown as dashed lines) in order to allow the neighboring Base Stations 392, 393, 394, 395, 396 and 397 to transmit at these times. As shown in FIG. 14C, three of the neighboring Base Stations 393, 395, 397 transmit on even-numbered skipped hops 705. As shown in FIG. 14D, the other three of the neighboring Base Stations 392, 394, 396 transmit on odd-numbered skipped hops 707. At other times (other than the hops 705, 707), the neighboring Base Stations 392, 393, 394, 395, 396 and 397 may transmit normally to other handsets (not shown) to which they are connected.
  • As described hereinabove, the Base Station that is communicating with the handset sends the call parameters to neighboring Base Stations via the local area network (LAN [0236] 140) that connects all of the Base Stations. It will also send information regarding the timing of hops that they may use to call handsets that it is communicating with. As described hereinabove with respect to FIG. 11, the neighboring Base Stations can synchronize the TOD. According to the timing of the hops received with high energy (P1), the Base Stations that wait for the call, can determine the times in which they are allowed to try to call the handset. In these times the Base Stations transmit to all handsets that are communicating with neighboring Base Stations.
  • Detecting Movement of a Handset [0237]
  • The two techniques for detecting a handset, described immediately hereinabove, are “passive” in the sense that they do not require any actions to be taken by the handset, other than the initial action of being engaged in a call (connected to a Base Station). The technique described immediately hereinbelow is “active” in the sense that it requires some further participation (albeit minimal) from the handset. However, such a mechanism is standard in most wireless communication protocols, even in those that were not originally meant to support mobility (handoff). In either case (“passive” or “active”), it is important to recognize that the present invention can work with standard handsets, without modification thereto. [0238]
  • Although the handsets do not need to have a mechanism for supporting (actively participating in) handoff, they preferably have a mechanism that allows checking whether their communication links are operating normally. For example, in the Bluetooth short-range communication link, a “PING” command that is sent on the asynchronous link is used to check whether the data communication link is operative. When the handset receives a “PING” command it will automatically respond with an “ECHO” message (response). Since the “PING” command is sent on an asynchronous link, and not the synchronous link that is used for voice communication, in does not disrupt the voice quality, but only slightly (and temporarily) reduces the available bandwidth for data transfer. [0239]
  • The “PING” command includes the following data fields: [0240]
  • Device address [0241]
  • Identifier [0242]
  • Length [0243]
  • Data (optional) [0244]
  • The “ECHO” response includes the: [0245]
  • Identifier [0246]
  • Length [0247]
  • Data (optional) [0248]
  • In the Identifier, an identification of the originating Base Station is sent. Hence, when the handset replies it is possible for any Base Station receiving the “ECHO” reply to know which Base Station originated the reply. [0249]
  • The “PING” command and “ECHO” response are used by a Base Station in order to determine whether a certain handset has entered its coverage area. Unlike the methods of passively detecting the handset presence, discussed hereinabove, this method allows detection of a Base Station that was not actively engaged in a call at the time of handoff. It is enough for the handset to have only created an initial communication with a Base Station. [0250]
  • FIGS. 15A and 15B, illustrate the use of “PING” command and the “ECHO” response by the Base Station that is waiting for the call. [0251]
  • As shown in FIG. 15A, the [0252] handset 121 is currently communicating with the Base Station # 1 123 via communications link 122. During this time, the Base Station # 2 124 that is waiting for the call will periodically send a “PING” command 145 to the handset 121. When the handset 121 enters the coverage area (is in range) of the waiting Base Station 124, and when it receives a “PING” command with its address, it will reply with an “ECHO” response 146. The “ECHO” response 146 is also received by the Base Station # 1 123.
  • The waiting [0253] Base Station # 2 124 transmits the “PING” command 145 during the hops that the Base Station # 1 123 has dedicated (yielded) for this operation, as described hereinabove (see, e.g., FIG. 14B, 702, 703). The “ECHO” reply 146 will be received by both Base Stations 123 and 124, whereupon the Base Stations 123 and 124 can each measure the quality of the received signal (“ECHO”) and report the measurements to the Switch (e.g., 129; FIG. 2). Based on this measurement of the quality of the received signal, the Switch 129 can compare signal quality and decide when is the right time to perform the handoff, and implement the handoff procedures described hereinabove.
  • FIG. 15B illustrates an alternative, “active” method for detecting the [0254] handset 121. In this example, The Base Station # 1 123 that is currently connected to the handset 121 transmits a “PING” command 147, once in M hops. The handset 121 replies with an “ECHO” response 146′ for each “PING” command 147 it receives. When the handset 121 enters the coverage area of neighboring Base Station # 2 124, the neighboring Base Station # 2 124 will receive the “ECHO” response 146′ by monitoring each Mth hop, in order to receive the “ECHO” response of the handset 121 that is approaching it. When the neighboring Base Station # 2 124 receives the “ECHO” response 146′, it measures the quality of the received signal, and reports to the Switch 129. This method is different from the method previously described with respect to FIG. 15A in two aspects:
  • 1) In the method of FIG. 15B, the [0255] Base Station 123 connected to the handset, does not skip each Mth hop, but rather transmits a “PING” to the handset
  • 2) In the method of FIG. 15B, the neighboring Base Stations (e.g., [0256] 124) do not transmit “PING”s to the handset 121—rather, they only passively monitor each Mth hop
  • The quality of each hop may be measured by many known methods, such as energy level measurement, signal-to-noise ratio (SNR) measurement, packet loss ratio and bit error rate measurement (BER) that can be performed on the header of each message. [0257]
  • Another Handset Detection Technique [0258]
  • Each Base Station maintains a “Neighbor Connections Table”, which includes information about the connections between handsets and neighboring Base Stations. The “Neighbor Connections Table”, includes the following information: [0259]
  • Connection number [0260]
  • Handset ID [0261]
  • Base Station ID [0262]
  • Handoff status: Idle/Started [0263]
  • Handset detection status [0264]
  • Number of successful “PING”[0265]
  • Time of last successful “PING”[0266]
  • Quality measurements in successful “PING”[0267]
  • FIG. 16A illustrates a technique (procedure) for detecting a handset that enters the coverage area of a Base Station when (as in the example of FIG. 15B) the Base Station that the handset is currently connected to generates the “PING” command that is sent to the handsets. All of the Base Stations (e.g., [0268] 391-397; FIG. 14A) preferably perform the same detection procedure, whether they the handset is connected with them or not.
  • When a hop is due ([0269] steps 400, 401), the even-numbered hops are used by the handset, and the Base Stations use the odd-numbered hops. In a step 402, a hop counter is incremented by one, and if (as determined in the step 403) it is the Kth hop, the Base Station will to try to send a “PING” to one of the handsets that are candidates for handoff. If it is not the Kth hop (step 403, “N”), the Base Station waits for the next hop (step 400).
  • As used herein, “NMAC” represents the address of the handset that will be called, and “NegTab” is an abbreviation of “Neighboring Connection Table”. [0270]
  • If handoff has not started yet with any handset ([0271] step 404, “N”), all the handsets will be called in order. The pointer to the NegTab is incremented (step 405), and the address of the handset is retrieved from the NegTab (step 406). The Base Station then transmits a “PING” command with the address of the handset (step 407). When handoff has already started with one or more than one handsets, these handsets are “PING”ed more often than the others. The next item in the NegTab is checked (step 411) and, if handoff with it has already started, it will be “PINGED” (steps 412, 407). The handsets that have not started handoff, will be “PING”ed only once in K2 “PING”s ( steps 410, 413, 414).
  • When an “ECHO” is received ([0272] step 420, “Y”) and it is determined to be from a handset that communicates with a neighboring Base Station (step 419, “N”), it will be compared to all the entries in the “Neighbor Connections Table” (NegTab) 421,422. If it is found in the NegTab (step 422, “Y”), the quality of the hop is measured (step 423) and a record of the average quality in the previous hops is maintained in the “Neighbor Connections Table” (step 424). The following measurement parameters are sent to the Switch (step 425):
  • Base Station communicating with handset [0273]
  • Base Station originating “PING”[0274]
  • Base Station receiving “PING”[0275]
  • Identification of handset [0276]
  • Quality of received signal [0277]
  • FIG. 16B illustrates a procedure that a Base Station performs when it receives an “ECHO” response from one of the handsets that are connected to it (from FIG. 16A, [0278] step 419, “Y”). The “ECHO” response can be received either when the connected Base Station or one of its neighbors sends a “PING” message to the handset. (See, e.g., FIGS. 15A and 15B.)
  • First, the Base Station checks to see if the “ECHO” reply was caused by itself, or by one of the neighboring Base Stations ([0279] steps 430, 431). This information is contained in the Identifier of the “ECHO” reply, as described hereinabove.
  • If the “ECHO” was caused by a neighboring Base Station ([0280] step 431, “Y”), the quality of the received signal is measured and averaged (step 432), and the measurement parameters are sent the Switch (step 433) to be used by the Switch in determining when to perform handoff. If the Base Station itself caused the “ECHO” reply (step 431, “N”), the task simply exits (“B”).
  • FIGS. 16A and 16B illustrated the procedure of transmitting the “PING” from the Base Station that the handset is connected too, and detecting the arrival of a handset from a neighboring Base Station. [0281]
  • FIG. 23 illustrates a procedure for performed by the Base Station when reception or transmission of a hop is required ([0282] steps 1200, 1201). Once in K hops (step 1202), if the next time slot is for transmission (step 1203), the Base Stations sends a “PING” to one of the handsets that are connected to it. Tcount is incremented (step 1204), and the next handset that appears in the list of handsets (Connection Table, or “ConTab”) that are connected to the Base Station is chosen (step 1205).
  • The “PING” is sent with the address taken from the ConTab (step [0283] 1206). When it is time to receive a hop, the receiver looks for an “ECHO” response (step 1207). If an “ECHO” is received, and it originator was a neighboring Base Station (step 1208), the parameters are compared to the NegTab (step 1209), and if it is found in the table (step 1214), the quality of the signal is measured (step 1210) and averaged (step 1211). If the “ECHO” response was to a “PING” command that originated from the same Base Station, the quality is measured (step 1213). In both cases the connection parameters and the quality are sent to the Switch (step 1212).
  • When an “ECHO” response is received (FIG. 16A, [0284] step 425; or FIG. 16B, step 433; or FIG. 23, step 1212), the following data is sent to the Switch:
  • Received quality [0285]
  • If from handset from neighbor Base Station, the average quality of the received “PINGS”. [0286]
  • If from handset connected to same Base Station, the received quality that is monitored continuously, and also the average quality of the received “PINGS”. [0287]
  • Base Station originating “PING”[0288]
  • Base Station receiving “ECHO”[0289]
  • Base Station currently connected to handset [0290]
  • Measurement TOD [0291]
  • Performing Handoff [0292]
  • Two methods for detecting that a handset moves from one Base Station to another have been described hereinabove. The first handset detection method (FIGS. 13, 14A, [0293] 14B, 14C, 14D) is based on passive monitoring of the handset. In the second handset detection method (FIGS. 15A, 15B, 16A, 16B) the handsets are actively “PING”ed, and their “ECHO” responses are noted. Using either one of these two methods, a Base Station that is connected to a handset continuously sends received quality measurements to the Switch and, when a neighboring Base Station detects a handset, a quality measurement is also sent by the neighboring Base Station to the Switch. A Base Station receiving an “ECHO” from one of the handsets that are connected to it (e.g., FIG. 15B), also sends the quality measurement to the Switch. The decision as to when to perform handoff, between one Base Station and another, is made at the Switch, which uses these signal quality measurements from the Base Stations to determine the time for and destination of a handoff. FIG. 17A illustrates a method for making the handoff decision, when a passive detection method is used. FIG. 17B illustrates a method for making the handoff decision, when an active detection method is used.
  • FIG. 17A illustrates a procedure that is implemented at the Switch ([0294] 129) in order to decide to which Base Station the handset should be handed. Energy measurements from two or more (three shown) Base Stations 801, 802 and 803 receiving a signal (i.e., the same signal) from a single handset (i.e., the same handset, not shown) are provided to the Switch, as described hereinabove (e.g., over the LAN 140). At the Switch, these measurements are “smoothed” by a plurality (three shown) of sliding window averaging filters 804, 805 and 806, respectively, and they are compared with one another by decision (handoff control) logic 807, which issues a signal (“Select Base Station”) to effect handoff. The sliding widow average filters 804, 805 and 806 compute the average quality received from a given Base Station over the previous Tr milliseconds, typically hundreds of milliseconds, (over a time interval encompassing at least two subsequent signals from the receiving Base Station), taking into account only the times in which the handset signal was received by more than one Base Station.
  • The following pseudo-code describes a preferred operation of the decision logic [0295] 807:
  • The inputs to the decision logic are marked by X[0296] l . . . Xk.
  • The current Base Station communicating with the handset is Base Station ‘m’[0297]
  • (1) If maximum (X[0298] l, . . . ,Xk)=Xj
  • (2) If X[0299] j>Xm+D1
  • (3) If time from previous handoff>T[0300] d
  • (4) Transfer call to Base Station j [0301]
  • (5) If X[0302] j>Xm+D2
  • (6) Transfer call to Base Station j [0303]
  • If a Base Station receives the handset at a level which is stronger by at least D[0304] 1 decibels than the level which is currently received by the Base Station with which the handset currently communicates, and at least Td milliseconds have passed from the last handoff, a handoff is required. This is intended to address the situation of a moderate and slow movement of a handset from one Base Station to another.
  • If a Base Station receives the handset at a level, which is stronger by at least D[0305] 2 decibels than the level, which is currently received by the Base Station with which the handset currently communicates a handoff will be performed immediately. This is intended to address the situation of an abrupt move from one Base Station to another.
  • When the Base Stations use one of the active methods to detect handset presence, the decision algorithm is basically the same as has just been described. The main difference comes from the fact that in the active method the different Base Stations are able to determine the quality that they measured for a single hop, which all of them can identify. Therefore, the Switch is able to compute the quality difference per hop, and thus improve the timing accuracy of handoff. [0306]
  • FIG. 17B illustrates the handoff decision method when using an active detection method. According to the TOD indication that is received along with the quality measurements, the measurements of the same hops are aligned in time ([0307] 808). They are then averaged over X hops (804, 805, 806), and the same decision logic (807) that was described above may be used to determine which is the most suitable Base Station to connect to the handset, and issue the “select Base Station” signal.
  • The methods described hereinabove relate to performing handoff between Base Stations when the handset is conducting a call. When a handset is not conducting a call it may move from one Base Station to the other. When it moves, one connection will be ended, and another will be created. The mechanism for ending a connection, and initiating a new one is part of the short-range wireless communication protocol. For example in the Bluetooth protocol, the handset searches for a Base Station, when it finds one, it stays connected to it. If it leaves the coverage area of the Base Station, the connection will end, and the handset will search again for a Base Station. This mechanism is sufficient for a handset that is not currently in a call, but it does not guarantee smooth handoff while in a call. Although this method may be suitable in some conditions, disconnecting from one Base Station and re-establishing connection with the other may take several seconds, and during this time it will not be possible to initiate a call. One of the advantages of the method of actively “PING”ing a handset is that its movement can be detected quickly, even when it is not engaged in a call, and this “waiting” period can be eliminated. [0308]
  • Operation Procedures [0309]
  • The following sections describe the operation procedures of the Base Stations and the Switch, that are used on the following events: [0310]
  • A new connection is created [0311]
  • A connection is closed [0312]
  • A handset presence is detected [0313]
  • Switch decides on handoff [0314]
  • Handoff performed by Base Stations [0315]
  • When receiving an update message from a Base Station [0316]
  • Base Station Procedures: [0317]
  • New connection created: [0318]
  • Create new low-level protocol instance. [0319]
  • Add connection to “Base Station Connections Table”[0320]
  • Set reserved hops for neighbors transmissions (if active detection method is used) [0321]
  • Send new connection information (handset ID, Base Station ID, handle to low-level protocol instance) to Switch [0322]
  • Send new connection information to all neighboring Base Stations (handset, id, Base Station id, reserved hops, call's parameters: TOD, device address, encryption key, authentication key, links status, etc.) [0323]
  • 2) Connection closed: [0324]
  • Close low-level protocol instance. [0325]
  • Remove connection from “Base Station Connections Table”[0326]
  • Send closed connection information to Switch (handset ID, Base Station ID, handle to low-level protocol instance) [0327]
  • Send closed connection information to neighboring Base Stations (handset ID, Base Station ID) [0328]
  • 3) Receive new connection information from neighboring Base Station [0329]
  • Add connection information to “Neighboring Connections Table”[0330]
  • 4) Receive closed connection information from neighboring Base Station [0331]
  • Remove connection from “Neighboring Connections Table”[0332]
  • 5) Detect presence of handset in coverage area [0333]
  • Create low-level protocol instance. [0334]
  • Synchronize TOD [0335]
  • Measure received quality [0336]
  • Update Switch (handset ID, neighbor Base Station ID, and Base Station ID, TOD, handle of low-level protocol instance). [0337]
  • 6) Receive message from high-level protocol [0338]
  • Check if corresponding low-level protocol is running on Base Station and, if it is: [0339]
  • Route message to the corresponding low-level protocol instance. [0340]
  • 7) Receive handoff command with TOD of handoff [0341]
  • If the Base Station is the Base Station currently communicating with the handset: [0342]
  • Wait until handoff TOD [0343]
  • Stop transmissions to the handset [0344]
  • Move connection parameters from “Base Station connection table” to [0345]
  • “Neighboring Connection Table”[0346]
  • If the Base Station was a neighbor of the Base Station communicating with the handset: [0347]
  • Wait until handoff TOD [0348]
  • Start transmitting to handset [0349]
  • Route call to destination Base Station or Switch [0350]
  • Send new connection information (handset id, Base Station ID, handle to low-level protocol instance) to Switch [0351]
  • Send new connection information to all neighboring Base Stations (handset, ID, Base Station ID, reserved hops, call's parameters: TOD, device address, encryption key, authentication key, links status, etc.) [0352]
  • Switch procedures: [0353]
  • 1) Receive new connection information [0354]
  • Create instance of high-level protocol [0355]
  • Update “Connections Table”[0356]
  • 1) Receive close connection message [0357]
  • Close high-level protocol instance [0358]
  • Remove from “Connections Table”[0359]
  • 1) Receive quality measurement from Base Station [0360]
  • If from Base Station connected to the handset, [0361]
  • Store measured quality and TOD of measurement [0362]
  • Check if a neighboring Base Stations should be removed from the handoff candidate list (according to last TOD in which they detected the handset), and remove if necessary [0363]
  • If from a neighbor of the Base Station connected to the handset, [0364]
  • Add neighbor as candidate for handoff to “Connection Table” with TOD of message. [0365]
  • Perform quality comparison and decision of handoff. [0366]
  • If a handoff is required: [0367]
  • Send handoff commands to the originating Base Station and the Base Station receiving the handset. [0368]
  • Update “Connections Table”[0369]
  • When there is more than one Switch in the system (see, e.g., FIG. 22) the Switch procedures will be slightly different, as follows: [0370]
  • 1) Receive new connection information [0371]
  • Create instance of high-level protocol [0372]
  • Update “Connections Table”[0373]
  • Send new connection information to all the Switches. [0374]
  • 1) Receive close connection message [0375]
  • Close high-level protocol instance [0376]
  • Remove from “Connections Table”[0377]
  • Send remove connection to all Switches [0378]
  • 1) Receive quality measurement from Base Station [0379]
  • If from Base Station connected to the handset [0380]
  • Store measured quality and TOD of measurement [0381]
  • Check if the neighboring Base Stations should be removed from handoff candidate list (according to last TOD in which they detected the handset), and remove if necessary [0382]
  • If one of the neighboring Base Stations is connected to a different Switch, send updated information to the other Switch. [0383]
  • If from a neighbor of the Base Station connected to the handset [0384]
  • Add neighbor as candidate for handoff to “Connection Table” with TOD of message. [0385]
  • Perform quality comparison and decision of handoff. [0386]
  • If a handoff is required: [0387]
  • Send handoff commands to the originating Base Station and the Base Station receiving the handset. [0388]
  • Update “Connections Table”[0389]
  • Update “Calls Table”[0390]
  • Send information to all Switches [0391]
  • 1) Receive update from another Switch [0392]
  • If new connection: add item to “Connections Table”[0393]
  • If closed connection: remove item from “Connections Table”[0394]
  • If quality measurement: update “Connection Table”[0395]
  • If handoff [0396]
  • Update “Connections Table”[0397]
  • Update “Calls Table”[0398]
  • The Switch also keeps a LOG file of the events in the system. The LOG file includes the quality measurements, call parameters (time, caller ID, called ID, reason for termination, etc.) and the handoff decisions. These may serve to analyze the Base Station's topology and allow for topology improvements and adjustments. For example the reason for a call termination may be correlated to low receive quality, which could imply that there is a “hole” in the coverage pattern. [0399]
  • Detection and Time Synchronization [0400]
  • FIG. 20 illustrates the implementation of detection and time synchronization method that is based on a correlator. As described hereinabove, the correlator/detector ([0401] 308) was the basis for synchronization of TOD in FIG. 11, and for the detection of presence of a transmitter and synchronization in FIG. 13.
  • It is important for a neighboring Base Station to be able to detect and synchronize with a mobile unit prior to receiving a handoff. This process should be done as quickly as possible to ensure seamless handoff of a session. Generally, the process begins with a wide-range search for “target” signals having the correct timing for a mobile unit, based on the rough synchronization information provided by the Base Station which is connected with the mobile unit. These “target” signals are estimated, based on the rough synchronization data. When a match is found (an actual signal from mobile unit is acquired) the search range can be narrowed accordingly (and dramatically). Then, synchronization can proceed as described hereinabove. [0402]
  • The detector/[0403] correlator 2000 comprises a signal detector 1001 and a correlator 1002. The task of the detector/correlator 2000 is to provide information whether a target signal is currently received, and to estimate the parameters which serve the hand-off process. The signal detector 1001 and correlator 1002 receive the actual received signal 1008 and its corresponding time 1009 and frequency 1004, as illustrated, and correlates them to the emulated time and frequency instances 1006. The fine TOD, drift and quality of the target signal are estimated by the correlator 1002 which reports the estimated parameters 1007, along with a status which indicates whether the target signal has been acquired, or not. The task of the signal detector 1001 is to process the received signal 1008 and to estimate its time of arrival (TOA), i.e. the exact timing of a hop, and quality values 1003. This may be done by several techniques, which are well known from classical detection theory. As an example of such techniques, an energy detector and a matched filter can be used.
  • FIG. 21 shows an example of the implementation of the [0404] signal detector 1001 of FIG. 20. In FIG. 21, the received signal 1008, which is received from the RF receiver output, is fed to an energy detector 1011. The energy detector 1011 produces a signal 1014, which represents the temporal energy shape of the signal. The temporal energy shape 1014 is fed into a matched filter 1012. The matched filter 1012 has an impulse response, which matches the energy shape the target signal. As is known, per classical estimation and detection theory, the matched filter 1012 will produce maximum value at the time instance which represents an estimation of the time of arrival (TOA), i.e. exact timing of the hops, of the target signal 1008. The maximum value of the filter output represents an estimation of the received signal quality. The time instance, which represents the estimation of the TOA, is represented in terms of the time clock 1009. The matched filter 1012 reports TOA and quality values of which the quality is above a threshold value Th, and the maximum is a global maximum within a two-sided time window of Ts1 microseconds. Other implementations of the signal detector 1001 in FIG. 20 can be utilized. Such implementations can correlate the received signal 1008 with the known portions of the target signal temporal pattern instead of its energy temporal shape. Such implementations may achieve improved estimation performance.
  • The time-[0405] frequency correlator 1002 in FIG. 20 receives the TOA and quality values 1003 produced by the signal detector 1001 and corresponding frequency values 1004, which are the actual tuning frequency of the RF receiver. These inputs are referred to herein as the ‘actual’ TOA-frequency-quality instances. These include the estimated information of the signals, which are received from the various sources. On the other inputs, the time/frequency correlator 1002 receives emulated values of TOA and frequency 1006 instances for a specific target source (i.e. a specific handset). We will refer to these values hereafter as ‘target’ TOA-frequency instances. The time-frequency correlator seeks matches in the instances from both sources—the ‘actual’ and the ‘target’ and detects TOA-frequency patterns at the ‘actual’ instances which are ‘similar’ to the ‘target’ pattern. This process is performed in two possible modes:
  • 1. ‘Acquisition’ mode in which a match of the ‘target’ to ‘actual’ patterns is searched over longer time shifts periods, which cover the uncertainty of the possible fine TOD. [0406]
  • 2. ‘Tracking’ mode in which the fine TOD and drift have been already estimated, and the match between of the ‘target’ to ‘actual’ is searched and verified on new TOA-frequency instances over a shorter uncertainty period. [0407]
  • The ‘actual’ data and [0408] 1004 is written into ‘actual’ instances history buffer (e.g., FIFO) and constitutes a list of which records consists of ‘actual_TOA’, ‘actual_frequency’ and ‘actual_quality’. The ‘target’ data 1006 is written into ‘target’ instances histories buffer (e.g., FIFO) and constitutes a list of which records consist of ‘target_TOA’ and ‘target_frequency’.
  • In the ‘acquisition’ mode, at any given time, records from both lists of which TOA values are ‘younger’than T[0409] y1 milliseconds (where Ty1, is typically 10,000) in relation to current time clock (to be referred hereafter as ‘young’ records) are processed as follows:
  • For each ‘target’ record, look for ‘actual’ records, which satisfy: [0410]
  • Matching frequency value (i.e. ‘actual_frequency’=‘target_frequency’). [0411]
  • Absolute value of ‘TOA_diff’ (‘TOA_diff’=‘known_diff’−(‘actual_TOA’-‘target TOA’)) is smaller than T[0412] y2 milliseconds (where Ty2 is typically 500). Note: ‘known_diff’ is 0 in the acquisition mode.
  • The ‘target’ and ‘actual’ records, which satisfy the conditions, are referred hereafter as ‘candidate_records’. [0413]
  • For each of the ‘candidate_records’ write the corresponding ‘TOA_diff’, ‘actual_quality’ value and ‘actual_TOA’ value into a ‘candidates_list’. [0414]
  • When all the ‘young_target’ records are processed against all ‘young_actual’ records, sort the ‘candidate_list’ by the ‘TOA_diff’ values and produce a ‘diff_histogram’ with resolution of T[0415] y3 microseconds (where Ty3 is typically 1000) as follows:
  • Scan the sorted ‘candidate_list’ records, identify the ‘TOA_diff’ values which are within the TOA diff range of each bin, and accumulate the corresponding ‘quality_values’ producing ‘diff_quality_histogram’ values per each bin. [0416]
  • Search the ‘diff_quality_histogram’ for values, which are bigger than Ky (where Ky is typically 50). If found, set the [0417] status output 1007 value to ‘detected’, and identify the corresponding ‘actual_TOA’ and ‘TOA_diff’ values. The corresponding ‘actual_TOA’ and ‘actual_diff’ values are referred to hereinafter as a ‘diff_cluster’ of records. If no ‘diff_quality_histogram’ values exceed Ky, set the status output 1007 to ‘not_detected’.
  • If status has been set to ‘detected’ perform a ‘least mean square error’ (LMSE) estimation of a linear line which mostly fits the two-dimensional ‘diff cluster’ instances (‘actual_TOA’ by ‘actual_diff’). LMSE estimation is a well-known estimation technique and is described in the classical literature. [0418]
  • The estimated linear line can be represented as: [0419]
  • diff=‘est diff[0420] 0’+‘est drift’*(TOA-TOA0) where TOA0 is the smallest ‘actual TOA’ value out of the ‘diff cluster’ records, ‘est diff0’ is the estimated output parameter of ‘fine TOD’ 1007 and ‘est drift is the estimation the output parameter ‘drift’ 1007. The ‘diff quality histogram’ value normalized by the corresponding ‘bin population’ is the ‘quality’ output 1007 value.
  • In the ‘tracking’ mode, at any given time, process the data in a similar way as in the ‘acquisition mode but with the following differences: [0421]
  • The value of ‘known diff’ is set to ‘prev_est_diff[0422] 0’+‘prev_est_drift’*(‘current_TOA0’-‘prev_TOA0’). The terms ‘prev_est_diff0’ and ‘prev_TOA0’ represented the ‘est_diff0’ and ‘TOA0’ which has been evaluated in the previous calculation (either in ‘acquisition’ mode or in ‘tracking’ mode). The term ‘current_TOA0’ is the ‘TOA0’ of current calculation.
  • A smaller value of T[0423] y4 microseconds (when Ty4 is typically 2000) for the ‘tracking’ mode replaces Ty2 of the ‘acquisition’ mode.
  • Base Station [0424]
  • FIG. 18 illustrates, in block diagram form, major components of a [0425] Base Station 1800. A plurality (three shown) of front- end processors 604, 605 and 606 are connected to a plurality (three shown) of antennas 601, 602 and 603, respectively. The front- end processors 604, 605 and 606 perform the low-level protocols of the short-range communication protocol, described hereinabove.
  • When idle, a front-[0426] end processor 604, 605 and 606 waits for a handset to establish a new connection. When a connection is created it reports the call parameters (e.g., Bluetooth device address, TOD, Encryption key, authentication key, etc.) and transfers the call stream to the central processing unit 607. When a front-end processor is idle, it can also be used to receive (detect, monitor) a handset that is leaving a neighboring Base Station. The central processing unit 607 then sends the front-end processor, the call parameters, and the exact time of handoff. The front-end processor, would at that time, continue the communicating with the handset, as if it was still in the neighboring Base Station.
  • A separate circuit module [0427] 612 (TOD Synchronization & Handset Detection) is used to detect arrival of new handset, and also to synchronize the TOD of all the calls, according to the techniques described hereinabove. This unit 612 is shown having its own antenna 611.
  • The [0428] central processing unit 607 controls the operation of the front- end processors 604, 605 and 606, receives data about new handoff and fine TOD estimation, receives data from neighboring Base Station, maintains the “Neighbor Connection Table”, communicates with the Switch and the other Base Stations. The local area network interface 609 is suitably a standard interface, for example a connection to a 10Base-T or 100-Base-T Ethernet, for connecting to the Local Area Network (LAN) 140. Memory 608 and Non-Volatile Memory (NVM) 610 is shown connected to the central processing unit (CPU) 607.
  • FIG. 19 illustrates, in greater detail, an implementation of a [0429] representative one 604 of the front- end processors 604, 605 and 606 described hereinabove with respect to FIG. 18. A base-band processor 631 determines the transmission and reception channels, encodes and decodes speech, deals with error correction, authentication and encryption. The radio frequency front end 630 modulates and demodulates the data, and connects to the antenna 601. The base-band processor 631 controls the frequency (“frequency control” 633) of each hop, sends and receives data (“energy, time of detection” 634) from the RF front end, and receives indication of signal strength (“base band parameters” 635).
  • Applications for the WPBX [0430]
  • Most of the preceding sections discussed the use of the methods disclosed in the current invention for a WPBX supporting telephony applications. Except for the methods shown in FIGS. 5, 6 and [0431] 7, most of the methods disclosed hereinabove are application independent, as follows:
  • The method for dividing the short-range communication protocol in order to support mobility of devices. The high-level protocols, including telephony-related protocols, and also protocols for data transfer, such as PPP over the short-range communication link. [0432]
  • The methods for synchronizing the Base Station. [0433]
  • The methods for detecting movement of transmitter from one Base Station to another. [0434]
  • The methods for decide when to perform handoff and to what Base Station to hand the call. [0435]
  • These methods can be implemented in order to connect mobile devices that are equipped with a short-range communication transmitter/receiver such as a Bluetooth chipset. Such devices may move from the coverage area of one Base Station to the coverage area of another, when the Switch and Base Stations handle the handoff of the connection from one Base Station to another. Typical application may be the connection of laptop computers equipped with a Bluetooth short-range communication link to the organization's e-mail server. Another possible application is connecting such mobile devices that for example utilize the PPP (point-to-point protocol) over Bluetooth wireless link, to the Internet, via a central remote access server. A system may also support several such applications. [0436]
  • For example in FIG. 24, a personal data (or digital) assistant (PDA) [0437] 1301, a laptop computer 1302 and a cellular handset 1303, connect to the systems Base Stations 1304 and 1305, as illustrated. The PDA 1301 and the laptop 1302 may connect, via the local area network (LAN) 1306 to an e-mail server 1308 in order to send or receive messages, and may also connect to a remote access server (RAS) 1309 for Internet connection. The cellular handset 1303 may connect to another handset (not shown) or, via a Telephony Gateway 1306 to the PSTN. The Base Stations 1304 and 1305 and the Switch 1307 handle the various levels of the communication protocol, utilizing the methods described hereinabove.
  • It is within the scope of the invention that the mobile unit is a device which is any of the following devices: telephone handset, standard cordless telephone handset, cellular telephone handset, personal data device, personal digital assistant (PDA), computer, laptop computer, e-mail server, and a device utilizing point-to-point protocol (PPP) to the Internet via a central remote access server, a headset (including a cordless headset), a personal server, a wearable computer (or computing device), a wireless (video or still) camera, or a mobile music players (i.e., MP-3 devices etc). [0438]
  • Although the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made, and are intended to be within the scope of the invention, as disclosed herein. [0439]

Claims (11)

What is claimed is:
1. In a wireless communication system comprising a plurality of Base Stations and at least one Switch in communication with the Base Stations, a method of synchronizing at least one neighboring Base Station to a Base Station connected with a mobile unit comprising:
from the Base Station connected with the mobile unit, periodically transmitting during a selected time interval with higher transmission power than during normal transmission; and
receiving the transmission with higher transmission power at the least one neighboring Base Station.
2. Method, according to claim 1, wherein:
the selected time interval is a synchronization hop in a series of periodic hops; and
the increased transmission power during the synchronization hop is at least twice as great as the normal transmission power.
3. Method, according to claim 1, wherein:
the selected time interval is a synchronization hop in a series of periodic hops; and
the synchronization hop is transmitted at a different frequency than the remaining periodic hops.
4. Method, according to claim 1, wherein:
the mobile unit is equipped with a short-range wireless communication transmitter/receiver.
5. Method, according to claim 1, wherein the mobile unit is a device selected from the group consisting of:
telephone handset, standard cordless telephone handset, cellular telephone handset, personal data device, personal digital assistant (PDA), computer, laptop computer, e-mail server, a device utilizing point-to-point protocol (PPP) to the Internet via a central remote access server a headset, a personal server, a wearable computer, a wireless camera, and a mobile music player.
6. Method, according to claim 1, further comprising:
providing communication links between the Base Stations, wherein the communication links between the Base Stations are selected from the group consisting of RF links and land lines; and
transferring connection status information and rough synchronization information between the Base Stations over the communications links.
7. Method, according to claim 1, wherein:
the Base Stations and the Switch are connected via a wired or wireless local area network (LAN).
8. Method, according to claim 1, wherein:
a first plurality of Base Stations are connected to a first Switch;
a second plurality of Base Stations are connected to a second Switch;
the Switches maintain status tables for calls and connections that they are handling, and maintain copies of each other's status tables; and
when a Switch updates one of its status tables, it sends the updated status table to the other Switches.
9. Method, according to claim 1, wherein:
the wireless communication system comprises a wireless private branch exchange (WPBX) handling calls from mobile units comprising handsets.
10. Method, according to claim 9, further comprising:
in the Switch, maintaining a table of calls being handled by the WPBX, comprising information selected from the group consisting of a unique Call Identification number for each active call being handles by the WPBX, the origin of the call, the destination of the call, Calling Number Identification (CNID), Destination Number (DN), Originating Base Station Identification, Destination Base Station Identification, Status of call, information for billing, and information for performance analysis.
11. Method, according to claim 9, further comprising:
in the Switch, for each call, maintaining a table of connections comprising information selected from the group consisting of Handset ID, Current Base Station ID, handle of high-level protocols, handle of low-level protocols, Number of candidate Base Stations for handoff, List of candidate Base Stations for handoff, and List of handoff status for each candidate Base Station.
US10/078,008 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations Abandoned US20020132630A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/078,008 US20020132630A1 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US19521900P 2000-04-07 2000-04-07
US20830600P 2000-06-01 2000-06-01
US09/784,109 US6430395B2 (en) 2000-04-07 2001-02-16 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/078,008 US20020132630A1 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/784,109 Division US6430395B2 (en) 2000-04-07 2001-02-16 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Publications (1)

Publication Number Publication Date
US20020132630A1 true US20020132630A1 (en) 2002-09-19

Family

ID=27393413

Family Applications (7)

Application Number Title Priority Date Filing Date
US09/784,109 Expired - Lifetime US6430395B2 (en) 2000-04-07 2001-02-16 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/078,008 Abandoned US20020132630A1 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/077,969 Expired - Lifetime US7107057B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/078,007 Expired - Fee Related US7231212B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/077,985 Expired - Fee Related US7274934B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/077,970 Expired - Fee Related US7215952B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US11/828,394 Expired - Fee Related US7499717B2 (en) 2000-04-07 2007-07-26 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/784,109 Expired - Lifetime US6430395B2 (en) 2000-04-07 2001-02-16 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Family Applications After (5)

Application Number Title Priority Date Filing Date
US10/077,969 Expired - Lifetime US7107057B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/078,007 Expired - Fee Related US7231212B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/077,985 Expired - Fee Related US7274934B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US10/077,970 Expired - Fee Related US7215952B2 (en) 2000-04-07 2002-02-20 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US11/828,394 Expired - Fee Related US7499717B2 (en) 2000-04-07 2007-07-26 Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Country Status (6)

Country Link
US (7) US6430395B2 (en)
EP (6) EP2296401A3 (en)
JP (3) JP4754146B2 (en)
KR (1) KR20030014201A (en)
AU (1) AU2001249274A1 (en)
WO (1) WO2001078246A1 (en)

Cited By (38)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020147016A1 (en) * 2000-04-07 2002-10-10 Commil Ltd Was Filed In Parent Case Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20030119490A1 (en) * 2001-02-26 2003-06-26 Jahangir Mohammed Wireless communications handset for facilitating licensed and unlicensed wireless communications, and method of operation
US20040009749A1 (en) * 2001-03-20 2004-01-15 Nitzan Arazi Wireless private branch exchange(wpbx) and communicating between mobile units and base stations
EP1420601A2 (en) * 2002-11-06 2004-05-19 Samsung Electronics Co. Ltd. Wireless communication system and a hand-off method therefor
US20040116120A1 (en) * 2002-10-18 2004-06-17 Gallagher Michael D. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US20040192211A1 (en) * 2001-02-26 2004-09-30 Gallagher Michael D. Apparatus for supporting the handover of a telecommunication session between a licensed wireless system and an unlicensed wireless system
US20070054680A1 (en) * 2005-08-19 2007-03-08 Matsushita Electric Industrial Co., Ltd. Method of band multiplexing to improve system capacity for a multi-band communication system
US20090323572A1 (en) * 2005-08-26 2009-12-31 Jianxiong Shi Intelligent access point scanning with self-learning capability
US7756546B1 (en) 2005-03-30 2010-07-13 Kineto Wireless, Inc. Methods and apparatuses to indicate fixed terminal capabilities
US7809381B2 (en) * 2004-07-16 2010-10-05 Bridgeport Networks, Inc. Presence detection for cellular and internet protocol telephony
US7843900B2 (en) 2005-08-10 2010-11-30 Kineto Wireless, Inc. Mechanisms to extend UMA or GAN to inter-work with UMTS core network
US7852817B2 (en) 2006-07-14 2010-12-14 Kineto Wireless, Inc. Generic access to the Iu interface
US7873015B2 (en) 2002-10-18 2011-01-18 Kineto Wireless, Inc. Method and system for registering an unlicensed mobile access subscriber with a network controller
US7885644B2 (en) 2002-10-18 2011-02-08 Kineto Wireless, Inc. Method and system of providing landline equivalent location information over an integrated communication system
US7912004B2 (en) 2006-07-14 2011-03-22 Kineto Wireless, Inc. Generic access to the Iu interface
US7929977B2 (en) 2003-10-17 2011-04-19 Kineto Wireless, Inc. Method and system for determining the location of an unlicensed mobile access subscriber
US7933598B1 (en) 2005-03-14 2011-04-26 Kineto Wireless, Inc. Methods and apparatuses for effecting handover in integrated wireless systems
US7949326B2 (en) 2002-10-18 2011-05-24 Kineto Wireless, Inc. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7953423B2 (en) 2002-10-18 2011-05-31 Kineto Wireless, Inc. Messaging in an unlicensed mobile access telecommunications system
US7957348B1 (en) 2004-04-21 2011-06-07 Kineto Wireless, Inc. Method and system for signaling traffic and media types within a communications network switching system
US7974624B2 (en) 2002-10-18 2011-07-05 Kineto Wireless, Inc. Registration messaging in an unlicensed mobile access telecommunications system
US7995994B2 (en) 2006-09-22 2011-08-09 Kineto Wireless, Inc. Method and apparatus for preventing theft of service in a communication system
US8005076B2 (en) 2006-07-14 2011-08-23 Kineto Wireless, Inc. Method and apparatus for activating transport channels in a packet switched communication system
US8019331B2 (en) 2007-02-26 2011-09-13 Kineto Wireless, Inc. Femtocell integration into the macro network
US8036664B2 (en) 2006-09-22 2011-10-11 Kineto Wireless, Inc. Method and apparatus for determining rove-out
US8041335B2 (en) 2008-04-18 2011-10-18 Kineto Wireless, Inc. Method and apparatus for routing of emergency services for unauthorized user equipment in a home Node B system
US8041385B2 (en) 2004-05-14 2011-10-18 Kineto Wireless, Inc. Power management mechanism for unlicensed wireless communication systems
US8073428B2 (en) 2006-09-22 2011-12-06 Kineto Wireless, Inc. Method and apparatus for securing communication between an access point and a network controller
US8130703B2 (en) 2002-10-18 2012-03-06 Kineto Wireless, Inc. Apparatus and messages for interworking between unlicensed access network and GPRS network for data services
US8150397B2 (en) 2006-09-22 2012-04-03 Kineto Wireless, Inc. Method and apparatus for establishing transport channels for a femtocell
US8165585B2 (en) 2002-10-18 2012-04-24 Kineto Wireless, Inc. Handover messaging in an unlicensed mobile access telecommunications system
US8165086B2 (en) 2006-04-18 2012-04-24 Kineto Wireless, Inc. Method of providing improved integrated communication system data service
US8204502B2 (en) 2006-09-22 2012-06-19 Kineto Wireless, Inc. Method and apparatus for user equipment registration
US8577291B1 (en) * 2007-02-01 2013-11-05 Broadcom Corporation Method and system for optimizing data throughput in a bluetooth communication system
US9265073B2 (en) 2010-05-21 2016-02-16 Kineto Wireless, Llc System and method for dual mode communication
US9490857B2 (en) 2002-09-20 2016-11-08 Iii Holdings 1, Llc Systems and methods for parallel signal cancellation
US9648644B2 (en) 2004-08-24 2017-05-09 Comcast Cable Communications, Llc Determining a location of a device for calling via an access point
US9774695B2 (en) 2009-06-17 2017-09-26 Counterpath Corporation Enhanced presence detection for routing decisions

Families Citing this family (245)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5960344A (en) * 1993-12-20 1999-09-28 Norand Corporation Local area network having multiple channel wireless access
EP0863684A3 (en) * 1997-03-03 2000-05-17 Victor Company Of Japan, Ltd. Communication system
DE69830977T2 (en) * 1997-06-04 2006-04-20 Ntt Docomo, Inc. MOBILE RADIO TRANSMISSION SYSTEM, MOBILE STATION AND METHOD FOR CONTROLLING THE DIVERSITY BRANCHES
DE19848306A1 (en) * 1998-10-14 2000-04-20 Schering Ag High yield preparation of cytotoxic or fungicidal compound epothilon B, from phenylsulfonyl-butanol derivative by multistage process via new thiazole derivative intermediates
US6898427B1 (en) * 1999-12-29 2005-05-24 Bellsouth Intellectual Property Corporation Method of coupling portable communications device to first network by way of second network
US6917280B1 (en) * 1999-12-29 2005-07-12 Bellsouth Intellectual Property Corporation Cradle for accepting portable communications device and coupling portable communications device to first network by way of second network
US6766160B1 (en) * 2000-04-11 2004-07-20 Nokia Corporation Apparatus, and associated method, for facilitating authentication of communication stations in a mobile communication system
US6714797B1 (en) * 2000-05-17 2004-03-30 Nokia Corporation System and method for the transfer of digital data to a mobile device
FI110296B (en) * 2000-05-26 2002-12-31 Nokia Corp Hands-free function
JP2004515933A (en) * 2000-06-13 2004-05-27 レッド−エム(コミュニケーションズ)リミテッド Call processing equipment
US6834192B1 (en) * 2000-07-03 2004-12-21 Nokia Corporation Method, and associated apparatus, for effectuating handover of communications in a bluetooth, or other, radio communication system
US6633761B1 (en) * 2000-08-11 2003-10-14 Reefedge, Inc. Enabling seamless user mobility in a short-range wireless networking environment
US6757532B1 (en) * 2000-08-30 2004-06-29 Telefonaktiebolaget Lm Ericsson (Publ) Permissible operating mode determination in a dual-mode radio
SE0003098D0 (en) * 2000-09-01 2000-09-01 Ericsson Telefon Ab L M A telecommunication system
US6691227B1 (en) * 2000-09-08 2004-02-10 Reefedge, Inc. Location-independent packet routing and secure access in a short-range wireless networking environment
GB0022269D0 (en) * 2000-09-12 2000-10-25 Koninkl Philips Electronics Nv Data transmission system
US7979057B2 (en) * 2000-10-06 2011-07-12 S.F. Ip Properties 62 Llc Third-party provider method and system
KR100364368B1 (en) * 2000-10-18 2002-12-12 엘지전자 주식회사 Private Network Using Bluetooth and Communication Method Using the Network
US6922557B2 (en) * 2000-10-18 2005-07-26 Psion Teklogix Inc. Wireless communication system
US20090111457A1 (en) 2007-10-31 2009-04-30 Raze Technologies, Inc. Wireless communication system and device for coupling a base station and mobile stations
US7346347B2 (en) 2001-01-19 2008-03-18 Raze Technologies, Inc. Apparatus, and an associated method, for providing WLAN service in a fixed wireless access communication system
US7039022B1 (en) * 2000-11-16 2006-05-02 Telefonaktiebolaget Lm Ericsson (Publ) Transaction system
US20020065065A1 (en) * 2000-11-30 2002-05-30 E. Michael Lunsford Method and system for applying line of sight IR selection of a receiver to implement secure transmission of data to a mobile computing device via an RF link
US20020090947A1 (en) * 2000-12-22 2002-07-11 Frank Brooks Automatic reconnect of dropped calls
FI110560B (en) * 2000-12-27 2003-02-14 Nokia Corp Grouping of wireless communication terminals
US7016325B2 (en) * 2001-01-18 2006-03-21 Strix Systems, Inc. Link context mobility method and system for providing such mobility, such as a system employing short range frequency hopping spread spectrum wireless protocols
GB0102813D0 (en) * 2001-02-05 2001-03-21 Nokia Mobile Phones Ltd Exchange of information in Bluetooth
US20020123307A1 (en) * 2001-03-03 2002-09-05 Tyson Winarski Wireless based system for managing the use of wireless communications and micoprocessor-based systems
US6954443B2 (en) 2001-03-09 2005-10-11 Nokia Corporation Short range RF network with roaming terminals
US6823197B1 (en) * 2001-03-13 2004-11-23 At&T Corp. Method and system for providing mobility to enhanced call service features at remote locations
GB0124884D0 (en) * 2001-03-20 2001-12-05 Koninkl Philips Electronics Nv Information system for travellers
US20040166864A1 (en) * 2001-03-28 2004-08-26 Stephen Hill Minimising signal interference within a wireless network
US7296042B2 (en) * 2001-04-20 2007-11-13 Palo Alto Research Center Incorporated System and method for enabling communication among arbitrary components
WO2002089411A2 (en) * 2001-05-01 2002-11-07 Koninklijke Philips Electronics N.V. Handoff in radio communication arrangements
EP1391100A4 (en) 2001-05-02 2009-03-11 Strix Systems Inc Wireless base station neighbor discovery in a communication system employing a short-range frequency hopping scheme
US7151757B2 (en) 2001-05-02 2006-12-19 Strix Systems, Inc. Wireless base station to base station synchronization in a communication system, such as a system employing a short-range frequency hopping or time division duplex scheme
US7194010B2 (en) * 2001-05-02 2007-03-20 Strix Systems, Inc. Wireless base station to base station synchronization in a communication system, such as a system employing a short range frequency hopping or time division duplex scheme
US20030041175A2 (en) * 2001-05-03 2003-02-27 Singhal Sandeep K Method and System for Adapting Short-Range Wireless Access Points for Participation in a Coordinated Networked Environment
US7224979B2 (en) * 2001-05-03 2007-05-29 Symantec Corporation Location-aware service proxies in a short-range wireless environment
US6968334B2 (en) * 2001-05-15 2005-11-22 Nokia Corporation Method and business process to maintain privacy in distributed recommendation systems
US6826154B2 (en) * 2001-05-24 2004-11-30 3Com Corporation Method and apparatus for seamless mobility between different access technologies
US7009952B1 (en) 2001-05-24 2006-03-07 3Com Corporation Method and apparatus for seamless mobility with layer two assistance
US20030036374A1 (en) * 2001-06-04 2003-02-20 Time Domain Corporation Wireless local area network using impulse radio technology to improve communications between mobile nodes and access points
US7801260B2 (en) * 2001-06-18 2010-09-21 St-Ericsson Sa Peak detection accuracy
US20020197984A1 (en) * 2001-06-22 2002-12-26 Tadlys Ltd. Flexible wireless local networks
US7020472B2 (en) * 2001-06-22 2006-03-28 Gallitzin Allegheny Llc Cellular channel bonding for improved data transmission
US7536691B2 (en) * 2001-08-09 2009-05-19 Infineon Technologies Ag Method and apparatus for software-based allocation and scheduling of hardware resources in a wireless communication device
WO2003021978A1 (en) * 2001-08-10 2003-03-13 Strix Systems, Inc. Virtual linking using a wireless device
US20030054767A1 (en) * 2001-08-14 2003-03-20 Mandhyan Indur B. Method and apparatus for using wireless network enabled devices over existing wired telephone networks
GB0119957D0 (en) * 2001-08-15 2001-10-10 Red M Communications Ltd Handoff of bluetooth connections
US8195950B2 (en) * 2001-08-15 2012-06-05 Optimum Path LLC Secure and seamless wireless public domain wide area network and method of using the same
US6850125B2 (en) * 2001-08-15 2005-02-01 Gallitzin Allegheny Llc Systems and methods for self-calibration
US20030035388A1 (en) * 2001-08-15 2003-02-20 Schmidt Dominik J. RF sniffer
US7080116B2 (en) * 2001-08-21 2006-07-18 The Boeing Company Network blocking device for paid Internet services
US20030045283A1 (en) * 2001-09-06 2003-03-06 Hagedoorn Johan Jan Bluetooth enabled hearing aid
US6760804B1 (en) * 2001-09-11 2004-07-06 3Com Corporation Apparatus and method for providing an interface between legacy applications and a wireless communication network
US7058040B2 (en) * 2001-09-21 2006-06-06 Schmidt Dominik J Channel interference reduction
JP3641228B2 (en) * 2001-09-26 2005-04-20 株式会社東芝 Wireless base station, wireless communication system, program, and connection control method
KR100401199B1 (en) * 2001-09-27 2003-10-10 삼성전자주식회사 Signal supply apparatus for public and private mobile communication system
US8644475B1 (en) 2001-10-16 2014-02-04 Rockstar Consortium Us Lp Telephony usage derived presence information
US6975877B1 (en) * 2001-10-17 2005-12-13 Cisco Technology, Inc. System and method for synchronizing clock dividers in a wireless network
US7164886B2 (en) * 2001-10-30 2007-01-16 Texas Instruments Incorporated Bluetooth transparent bridge
US7085306B1 (en) * 2001-10-30 2006-08-01 3Com Corporation System and method for a multi-frequency upstream channel in a computer network
US7151764B1 (en) 2001-11-01 2006-12-19 Nokia Corporation Service notification on a low bluetooth layer
US7555287B1 (en) 2001-11-01 2009-06-30 Nokia Corporation Customized messaging between wireless access point and services
US6744753B2 (en) * 2001-11-01 2004-06-01 Nokia Corporation Local service handover
CN1582596B (en) * 2001-11-20 2013-09-25 艾利森电话股份有限公司 Method, apparatus and arrangement in telecommunication network for providing control over and enabling advanced service and user interfaces in mobile telephone
JP4075461B2 (en) * 2001-11-27 2008-04-16 ソニー株式会社 Communication system, communication terminal, and communication method
FI20012358A0 (en) 2001-11-30 2001-11-30 Nokia Corp Mobile equipment and procedure for performing software function
EP1455467A1 (en) * 2001-12-06 2004-09-08 Fujitsu Limited Portable terminal having function of detecting approach of person by using proximity wireless communication means, recorded medium used for the same, and server
WO2003052962A1 (en) * 2001-12-14 2003-06-26 Interdigital Technology Corporation System for context transfer for wireless internet devices
DE60205712T2 (en) 2001-12-28 2006-06-29 Kabushiki Kaisha Toshiba Portable terminal with combined short-range radio communication for direct and cellular mobile communications
JP2003218763A (en) * 2002-01-17 2003-07-31 Matsushita Electric Ind Co Ltd Apparatus allowing radio communication
US7336602B2 (en) * 2002-01-29 2008-02-26 Intel Corporation Apparatus and method for wireless/wired communications interface
US8184603B2 (en) 2002-01-31 2012-05-22 Lgc Wireless, Llc Communication system having a community wireless local area network for voice and high speed data communication
US7340214B1 (en) 2002-02-13 2008-03-04 Nokia Corporation Short-range wireless system and method for multimedia tags
EP1479251A4 (en) * 2002-02-25 2010-06-23 Radioframe Networks Inc Radio system having distributed real-time processing
US7369532B2 (en) * 2002-02-26 2008-05-06 Intel Corporation Apparatus and method for an audio channel switching wireless device
US7254708B2 (en) * 2002-03-05 2007-08-07 Intel Corporation Apparatus and method for wireless device set-up and authentication using audio authentication—information
AU2002304330A1 (en) * 2002-03-13 2003-09-22 Nokia Coporation Method and apparatus for performing handover in a bluetooth radiocommunication system
US7787908B2 (en) * 2002-03-19 2010-08-31 Qualcomm Incorporated Multi-call display management for wireless communication devices
US7102640B1 (en) * 2002-03-21 2006-09-05 Nokia Corporation Service/device indication with graphical interface
CN1214597C (en) * 2002-03-26 2005-08-10 华为技术有限公司 Network access faciity based on protocol 802.1X and method for realizing handshake at client end
EP1357710A1 (en) * 2002-04-23 2003-10-29 Red-M (Communications) Limited A hand-off mechamism
US8554915B2 (en) * 2002-05-15 2013-10-08 Telcordia Technologies Inc. Management of communication among network devices having multiple interfaces
US7103359B1 (en) 2002-05-23 2006-09-05 Nokia Corporation Method and system for access point roaming
US7805161B1 (en) 2002-06-03 2010-09-28 Sprint Spectrum L.P. Virtual visitor location register for a wireless local area network
US7103313B2 (en) * 2002-06-05 2006-09-05 Nokia Corporation Automatic determination of access point content and services for short-range wireless terminals
FR2840756B1 (en) * 2002-06-06 2004-12-17 Cit Alcatel METHOD FOR SYNCHRONIZING DECT BASE STATIONS INTERCONNECTED VIA AN IP ARCHITECTURE LAN NETWORK
US6778824B2 (en) 2002-06-19 2004-08-17 Telular Corp. Apparatus for wirelessly-coupling a bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular network
US20040001530A1 (en) * 2002-06-27 2004-01-01 International Business Machines Corporation Insertion of null packets to mitigate the effects of interference in wireless communications
US20040014422A1 (en) * 2002-07-19 2004-01-22 Nokia Corporation Method and system for handovers using service description data
US20050060319A1 (en) * 2002-08-02 2005-03-17 Cisco Technology, Inc. Method for central planning and distributed control of client roaming and reassociation
US7010731B2 (en) * 2002-08-14 2006-03-07 Intel Corporation Method and apparatus of generating a quality indicator
US7610050B2 (en) * 2002-08-14 2009-10-27 Tadaaki Chigusa System for mobile broadband networking using dynamic quality of service provisioning
GB2392056B (en) 2002-08-15 2007-03-21 Iml Ltd A participant response system and method
US7433336B1 (en) * 2002-08-27 2008-10-07 Broadcom Corporation Method and apparatus for distributing data to a mobile device using plural access points
US20050227763A1 (en) * 2004-03-31 2005-10-13 Microsoft Corporation Game controller power management
US7835328B2 (en) 2002-09-13 2010-11-16 Strix Systems, Inc. Network access points using multiple devices
US8254346B2 (en) * 2002-09-17 2012-08-28 Broadcom Corporation Communication system and method for discovering end-points that utilize a link layer connection in a wired/wireless local area network
US8392609B2 (en) 2002-09-17 2013-03-05 Apple Inc. Proximity detection for media proxies
US7555108B2 (en) * 2002-10-01 2009-06-30 Nortel Networks Limited Presence information for telephony users
US7634269B2 (en) 2002-10-18 2009-12-15 Kineto Wireless, Inc. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7471655B2 (en) 2003-10-17 2008-12-30 Kineto Wireless, Inc. Channel activation messaging in an unlicensed mobile access telecommunications system
US6963739B2 (en) * 2002-10-21 2005-11-08 Motorola, Inc. Method and apparatus for providing information intercept in an ad-hoc wireless network
KR100448318B1 (en) * 2002-11-08 2004-09-16 삼성전자주식회사 Method for hand-off in a wileless network
EP1580925B1 (en) 2002-12-12 2008-02-06 Huawei Technologies Co., Ltd. Method for establishing or cancelling a service connection between a wireless local area network and a user terminal
US8561069B2 (en) 2002-12-19 2013-10-15 Fujitsu Limited Task computing
US7711810B2 (en) * 2003-01-03 2010-05-04 Nortel Networks Limited Distributed services based on presence technology
US7062291B2 (en) * 2003-01-06 2006-06-13 Vtech Telecommunications Limited Wireless multi-handset telephone system with integrated video monitoring accessories
US7096024B2 (en) 2003-01-31 2006-08-22 Qualcomm, Incorporated Method and apparatus to initiate point-to-point call during shared-channel delivery of broadcast content in a wireless telephone network
US7450943B2 (en) * 2003-02-12 2008-11-11 Qualcomm Incorporated Method and apparatus for determining coverage and switching between overlay communication systems
DE10310521B4 (en) * 2003-03-11 2007-05-31 Tenovis Gmbh & Co. Kg Method for changing a physical connection in a data network
US20040179485A1 (en) * 2003-03-12 2004-09-16 Terrier Carl M. Method of transmitting and receiving two-way serial digital signals in a wireless network utilizing a simplified baseband processor
US20040181517A1 (en) * 2003-03-13 2004-09-16 Younghee Jung System and method for social interaction
US7620027B2 (en) * 2003-03-14 2009-11-17 Canon Kabushiki Kaisha Communication system, information processing device, connection device, and connection device designation method for designating connection device for communication device to connect to
US7738917B2 (en) * 2003-03-31 2010-06-15 Vtech Telecommunications Limited Intercom/wireless door bell for multi-handset telephone system
US20130198867A1 (en) * 2011-12-09 2013-08-01 Z124 A Docking Station for Portable Devices Providing Authorized Power Transfer and Facility Access
US7904068B2 (en) * 2003-06-06 2011-03-08 At&T Intellectual Property I, L.P. System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed spectrum and wired access with licensed spectrum
US7627338B2 (en) * 2003-06-06 2009-12-01 At&T Intellectual Property I, L.P. System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed spectrum and wired access with licensed spectrum
US7657270B2 (en) 2003-06-06 2010-02-02 At&T Intellectual Property I, L.P. System and method for providing a single telephone number for use with a plurality of telephone handsets
US8457082B2 (en) * 2003-06-06 2013-06-04 At&T Intellectual Property I, L.P. System and method for providing integrated voice and data services utilizing wired cordless access with unlicensed/unregulated spectrum
EP1494394A1 (en) * 2003-06-30 2005-01-05 Sony International (Europe) GmbH Distance-aware service mechanism for determining the availability of remote services in wireless personal area networks
US7646777B2 (en) 2003-07-07 2010-01-12 At&T Intellectual Property I, L.P. Communication environment switchover
KR100526552B1 (en) * 2003-08-01 2005-11-03 삼성전자주식회사 Wireless personal area network for extending service area
JP4416792B2 (en) * 2003-08-06 2010-02-17 パナソニック株式会社 Terminal apparatus and method for master station transfer in media access communication system
CN1279722C (en) 2003-08-14 2006-10-11 华为技术有限公司 Method for rapid accessing attached networks of user terminal in wireless LAN
CN1277381C (en) * 2003-08-14 2006-09-27 华为技术有限公司 Method for maintaining initial network selective set in wireles LAN
US7496387B2 (en) * 2003-09-25 2009-02-24 Vocollect, Inc. Wireless headset for use in speech recognition environment
US20050071158A1 (en) * 2003-09-25 2005-03-31 Vocollect, Inc. Apparatus and method for detecting user speech
US7583643B2 (en) * 2003-09-30 2009-09-01 Motorola, Inc. Enhanced passive scanning
US7675878B2 (en) * 2003-09-30 2010-03-09 Motorola, Inc. Enhanced passive scanning
US7272397B2 (en) 2003-10-17 2007-09-18 Kineto Wireless, Inc. Service access control interface for an unlicensed wireless communication system
US7283822B2 (en) 2003-10-17 2007-10-16 Kineto Wireless, Inc. Service access control interface for an unlicensed wireless communication system
US7366542B2 (en) * 2003-10-21 2008-04-29 Gallitzin Allegheny Llc Wireless security
US7734293B2 (en) 2003-10-29 2010-06-08 Martin Zilliacus Mapping wireless proximity identificator to subscriber identity for hotspot based wireless services for mobile terminals
JP2005142766A (en) * 2003-11-05 2005-06-02 Matsushita Electric Ind Co Ltd Base station apparatus and method for allocating resource of base station apparatus
US7177664B2 (en) * 2003-11-10 2007-02-13 Ronald Lachman Bluetooth interface between cellular and wired telephone networks
US8271024B1 (en) 2003-11-26 2012-09-18 Genband Us Llc Messaging service interworking
US9118574B1 (en) * 2003-11-26 2015-08-25 RPX Clearinghouse, LLC Presence reporting using wireless messaging
JP4389569B2 (en) * 2003-12-05 2009-12-24 パナソニック株式会社 Private branch exchange
US8117280B2 (en) * 2003-12-12 2012-02-14 Fujitsu Limited Task computing
US20050136837A1 (en) * 2003-12-22 2005-06-23 Nurminen Jukka K. Method and system for detecting and using context in wireless networks
US8064903B2 (en) * 2003-12-30 2011-11-22 Cisco Technology, Inc. Methods and apparatus for reducing roaming latency in a mobile node
EP1696605A1 (en) * 2004-03-10 2006-08-30 Matsushita Electric Industrial Co., Ltd. Access control system, access control device used for the same, and resource providing device
US8229454B1 (en) 2004-03-22 2012-07-24 Avaya Inc. Personal location information management
WO2006105010A1 (en) 2005-03-25 2006-10-05 Neocific, Inc. Methods and apparatus for cellular broadcasting and communication system
US7508840B2 (en) 2004-05-28 2009-03-24 Bae Systems Information And Electronic Systems Integration Inc. Mobile temporary incident area network for local communications interoperability
WO2006053185A2 (en) * 2004-11-10 2006-05-18 Bae Systems Information And Electronic Systems Integration Inc. Wearable portable device for establishing communications interoperability at an incident site
US20060009206A1 (en) * 2004-07-06 2006-01-12 Gandhi Asif D Method of adding a sector to an active set
US8364081B1 (en) * 2004-07-12 2013-01-29 Stragent, Llc System, method, and computer program product for using a cellular phone as an interface for a VoIP-equipped computer
US7697489B1 (en) * 2004-07-12 2010-04-13 Sprint Spectrum L.P. Method and system for timer-based mobile IP re-registration in a wireless wide area network
US8249106B2 (en) * 2004-08-23 2012-08-21 Alcatel Lucent Extended cellular telephony protocol
EP1643779A1 (en) * 2004-09-30 2006-04-05 Avaya ECS Ltd. Telephone system for interfacing via bluetooth a cordless handset with a basestation in a wireless network
US20060075075A1 (en) * 2004-10-01 2006-04-06 Malinen Jouni I Method and system to contextually initiate synchronization services on mobile terminals in an enterprise environment
CA2624928A1 (en) * 2004-11-10 2006-05-18 Bae Systems Information And Electronic Systems Integration Inc. Device for establishing communications interoperability at an incident site including means for recording crisis incidents
US8090001B2 (en) * 2004-12-03 2012-01-03 Lantiq Deutschland Gmbh Fast frequency-hopping transceiver and method
US8065336B2 (en) * 2004-12-20 2011-11-22 Fujitsu Limited Data semanticizer
US8036676B2 (en) * 2005-02-14 2011-10-11 Mitsubishi Electric Corporation Frequency sharing method, receiving station and transmitting station
US7555318B2 (en) * 2005-02-15 2009-06-30 Broadcom Corporation Handover of call serviced by modular ear-piece/microphone between servicing base portions
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
US7773555B1 (en) * 2005-04-11 2010-08-10 Sprint Communications Company L.P. Extension of an ethernet backhaul system for wireless base stations over a cable television distribution network
US7519021B1 (en) 2005-04-11 2009-04-14 Sprint Communications Company Lp Third party access to Ethernet service from wireless base stations
US20060227767A1 (en) * 2005-04-11 2006-10-12 Sprint Communications Company L. P. Fault tolerant architecture for wireless base stations using ethernet backhaul
US8243779B2 (en) * 2005-04-29 2012-08-14 Alcatel Lucent Method of quality-based frequency hopping in a wirelesscommunication system
US8169953B2 (en) * 2005-05-17 2012-05-01 Qualcomm Incorporated Method and apparatus for wireless multi-carrier communications
US8619816B2 (en) 2005-05-20 2013-12-31 Go Net Systems Ltd. Method and corresponding device for improved bandwidth utilization
US8045484B2 (en) 2005-05-20 2011-10-25 Yaron Menahem Peleg Method for problematic user detection
US20060264214A1 (en) * 2005-05-20 2006-11-23 Nextwave Broadband, Inc. Mode-switching wireless communications equipment
CN101998285B (en) * 2005-06-09 2012-12-12 桥扬科技有限公司 Methods and apparatus for power efficient broadcasting and communication systems
GB2427790B (en) * 2005-06-29 2008-02-06 Motorola Inc Apparatus and method for determining call quality in a communication system
US7515544B2 (en) 2005-07-14 2009-04-07 Tadaaki Chigusa Method and system for providing location-based addressing
US8230491B2 (en) * 2005-08-19 2012-07-24 Opnet Technologies, Inc. Automatic access to network devices using various authentication schemes
US9118770B2 (en) * 2005-08-31 2015-08-25 Plantronics, Inc. Remote headset configuration
TWI274284B (en) * 2005-09-07 2007-02-21 Micro Star Int Co Ltd Method for changing parameter values of embedded system by way of object push profile
KR100734838B1 (en) * 2005-10-10 2007-07-03 한국전자통신연구원 Packet forwarding method, path reconstructing method and state transition method for avoiding packet loss during Handover
GB0521269D0 (en) * 2005-10-19 2005-11-30 Vodafone Plc Identifying communications between telecommunications networks
AU2006309464B2 (en) * 2005-10-31 2009-10-29 Lg Electronics Inc. Method for processing control information in a wireless mobile communication system
US8401555B2 (en) * 2005-11-30 2013-03-19 Qualcomm Incorporated Receiver status message management during handoff
US8842631B2 (en) * 2005-11-30 2014-09-23 Qualcomm Incorporated Data state transition during handoff
US8417185B2 (en) 2005-12-16 2013-04-09 Vocollect, Inc. Wireless headset and method for robust voice data communication
US7694180B2 (en) * 2005-12-30 2010-04-06 Cisco Technology, Inc. Collecting debug information according to user-driven conditions
US7773767B2 (en) 2006-02-06 2010-08-10 Vocollect, Inc. Headset terminal with rear stability strap
US7885419B2 (en) 2006-02-06 2011-02-08 Vocollect, Inc. Headset terminal with speech functionality
KR100744297B1 (en) * 2006-02-17 2007-07-30 삼성전자주식회사 Apparatus and method for searching and communicating with bluetooth device
KR100738929B1 (en) 2006-03-08 2007-07-12 에스케이 텔레콤주식회사 Method and system for handoff cdma 1x unlicensed mobile access service and cdma 2000 1x service
US8972872B2 (en) 2006-03-27 2015-03-03 Fujitsu Limited Building computing applications based upon metadata
US7778149B1 (en) 2006-07-27 2010-08-17 Tadaaki Chigusa Method and system to providing fast access channel
EP2060130A4 (en) * 2006-10-31 2010-03-10 Kineto Wireless Inc Method and apparatus to enable hand-in for femtocells
US8160096B1 (en) 2006-12-06 2012-04-17 Tadaaki Chigusa Method and system for reserving bandwidth in time-division multiplexed networks
TWI493952B (en) 2006-12-27 2015-07-21 Signal Trust For Wireless Innovation Method and apparatus for base station self-configuration
US20080167031A1 (en) * 2007-01-04 2008-07-10 General Instrument Corporation Satellite Receiver Having Bluetooth or Other Short-Range Wireless Interface
KR20080075297A (en) * 2007-02-12 2008-08-18 삼성전자주식회사 Apparatus and method for bluetooth connecting in portable communication system
EP1978664A1 (en) * 2007-04-05 2008-10-08 Alcatel Lucent Transmitting data packets over an air interface
US8594678B2 (en) * 2007-04-18 2013-11-26 Qualcomm Incorporated Backhaul network for femto base stations
JP5209046B2 (en) * 2007-05-23 2013-06-12 アギア システムズ インコーポレーテッド System and method for time-saving cell search for mobile devices in single and multiple wireless technology communication systems
US8830950B2 (en) * 2007-06-18 2014-09-09 Qualcomm Incorporated Method and apparatus for PDCP reordering at handoff
US8532026B2 (en) * 2007-06-21 2013-09-10 Ubeeairwalk, Inc. System, method, and computer-readable medium for multi-stage transmit protection in a femtocell system
CN101779419B (en) * 2007-07-30 2013-08-28 马维尔国际贸易有限公司 Simultaneously maintaining bluetooth and 802.11 connections to increase data throughput
KR20090012606A (en) * 2007-07-30 2009-02-04 삼성전자주식회사 Mobile device, printer server and private network system using them and methods thereof
KR100945245B1 (en) * 2007-08-10 2010-03-03 한국전자통신연구원 Method and apparatus for secure and efficient partial encryption of speech packets
US20090059868A1 (en) * 2007-08-31 2009-03-05 Samsung Electronics Co., Ltd. Cell Base Station Radio Frequency Channel Selection
US8116815B2 (en) * 2007-11-05 2012-02-14 Hewlett-Packard Development Company, L.P. Systems and methods for maintaining base stations in wireless networks
US8094610B2 (en) * 2008-02-25 2012-01-10 Virginia Tech Intellectual Properties, Inc. Dynamic cellular cognitive system
US20090232021A1 (en) * 2008-03-17 2009-09-17 Nokia Siemens Networks Oy Wireless network automation: network topology learning
TWI383703B (en) * 2008-04-28 2013-01-21 Quanta Comp Inc Communication system and method thereof
KR101089982B1 (en) * 2008-05-29 2011-12-05 교세라 가부시키가이샤 Base station and mobile station
EP2164289A1 (en) * 2008-09-12 2010-03-17 Nokia Siemens Networks OY Method for changing radio channels, composed network and access router
USD605629S1 (en) 2008-09-29 2009-12-08 Vocollect, Inc. Headset
US8874034B2 (en) * 2008-11-10 2014-10-28 Broadcom Corporation Method and system for quick Bluetooth low energy (BLE) protocol signal presence detection for coexistence
US8238902B2 (en) * 2009-01-05 2012-08-07 Centurylink Intellectual Property Llc Wireless DECT phone adaptor
US9014376B2 (en) * 2009-03-19 2015-04-21 Intel Corporation Method and apparatus for low-power AP-assisted fast wireless roaming using optimized neighbor graphs
US8270415B2 (en) * 2009-04-22 2012-09-18 Samsung Electronics Co., Ltd. Apparatus and method for routing data in a wireless network using bluetooth
US8774060B2 (en) * 2009-04-22 2014-07-08 Joshua R. Bryant Wireless headset communication system
KR101562224B1 (en) * 2009-04-23 2015-10-22 삼성전자주식회사 Apparatus and method for forwarding data for reducing handover interrupt time in wireless communication system
US8160287B2 (en) 2009-05-22 2012-04-17 Vocollect, Inc. Headset with adjustable headband
US9590733B2 (en) * 2009-07-24 2017-03-07 Corning Optical Communications LLC Location tracking using fiber optic array cables and related systems and methods
JP5257306B2 (en) 2009-09-11 2013-08-07 ブラザー工業株式会社 Wireless communication apparatus and computer program
US20110076951A1 (en) * 2009-09-30 2011-03-31 Kabushiki Kaisha Toshiba Information processing apparatus
US8438659B2 (en) 2009-11-05 2013-05-07 Vocollect, Inc. Portable computing device and headset interface
US20110276885A1 (en) * 2010-05-04 2011-11-10 Qwest Communications International Inc. Multi-client local network base station
US9500222B2 (en) 2010-05-04 2016-11-22 Qwest Communications International Inc. Passive suction base
US9356790B2 (en) 2010-05-04 2016-05-31 Qwest Communications International Inc. Multi-user integrated task list
US9559869B2 (en) 2010-05-04 2017-01-31 Qwest Communications International Inc. Video call handling
US9501802B2 (en) 2010-05-04 2016-11-22 Qwest Communications International Inc. Conversation capture
GB2481573A (en) * 2010-06-15 2012-01-04 Nds Ltd Splicng of encoded media content
US8570914B2 (en) 2010-08-09 2013-10-29 Corning Cable Systems Llc Apparatuses, systems, and methods for determining location of a mobile device(s) in a distributed antenna system(s)
KR101152848B1 (en) * 2010-08-19 2012-06-12 주식회사 라온테크놀러지 Digital wireless intercom system and method of driving the same
EP2472812B1 (en) * 2010-12-29 2014-02-12 Rtx A/S Scalable wireless multicell voip architecture
JP5278506B2 (en) * 2011-06-30 2013-09-04 株式会社デンソー Near field communication device
WO2013025539A1 (en) * 2011-08-12 2013-02-21 Interdigital Patent Holdings, Inc. Systems and/or methods for providing mobility robustness in heterogeneous network and small cell deployments
US8761671B2 (en) * 2011-10-06 2014-06-24 Cambridge Silicon Radio Limited Data merging for bluetooth devices
US9173185B1 (en) 2012-04-10 2015-10-27 Sprint Spectrum L.P. Methods and systems for managing registration signaling based on off-time duration
US9054750B2 (en) * 2012-04-23 2015-06-09 Qualcomm Incorporated Methods and apparatus for improving RF discovery for peer mode communications
CN103582042B (en) * 2012-08-08 2016-09-14 电信科学技术研究院 A kind of method and apparatus determining adjacent area
US20150009834A1 (en) * 2013-07-08 2015-01-08 Qualcomm Incorporated Generation of timing pulses based on acquired synchronization
US9119064B2 (en) * 2013-11-20 2015-08-25 At&T Intellectual Property I, L.P. Method and apparatus for providing broadcast channel encryption to enhance cellular network security
JP2015150881A (en) * 2014-02-19 2015-08-24 京セラ株式会社 Liquid discharge head and recording device using the same
US9560143B2 (en) * 2014-06-27 2017-01-31 Intel Corporation System and method for automatic session data transfer between computing devices based on zone transition detection
CN105491574A (en) * 2014-09-15 2016-04-13 普天信息技术有限公司 Method and device for determining priority of neighbor regions in neighbor region planning
US10117043B2 (en) * 2014-09-22 2018-10-30 Symbol Technologies, Llc Serially-connected bluetooth low energy nodes
CN107635240B (en) * 2017-10-27 2021-06-15 深圳市银河风云网络系统股份有限公司 Seamless roaming networking system and wireless communication system
CN112312489B (en) * 2019-07-31 2021-12-24 华为技术有限公司 Method, communication device and communication system for transmitting data
US11129027B2 (en) * 2019-09-30 2021-09-21 Juniper Networks, Inc. Intelligent radio band reconfiguration of access points in a wireless network
CN112188470B (en) * 2020-09-10 2022-08-12 中国联合网络通信集团有限公司 Method and device for determining privacy number platform

Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4617674A (en) * 1983-07-14 1986-10-14 Rca Corporation Synchronizing system for spread spectrum transmissions between small earth stations by satellite via an intermediate hop to a large earth station
US5353331A (en) * 1992-03-05 1994-10-04 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5410588A (en) * 1991-04-03 1995-04-25 Kabushiki Kaisha Toshiba Mobile radio communications system having a supervising radio transmitting station for transmitting a reference synchronizing signal to a first and second base stations via a radio link
US5579379A (en) * 1992-03-05 1996-11-26 Bell Atlantic Network Services, Inc. Personal communications service having a calling party pays capability
US5715521A (en) * 1994-04-22 1998-02-03 Oki Electric Industry Co., Ltd. Method of controlling synchronization signal power in a communication system
US5734699A (en) * 1995-05-04 1998-03-31 Interwave Communications International, Ltd. Cellular private branch exchanges
US5818824A (en) * 1995-05-04 1998-10-06 Interwave Communications International, Ltd. Private multiplexing cellular network
US5845211A (en) * 1995-01-13 1998-12-01 Bell South Corporation Wireless digital network
US5887256A (en) * 1995-05-04 1999-03-23 Interwave Communications International, Ltd. Hybrid cellular communication apparatus and method
US5911120A (en) * 1995-09-08 1999-06-08 At&T Wireless Services Wireless communication system having mobile stations establish a communication link through the base station without using a landline or regional cellular network and without a call in progress
US5913163A (en) * 1996-03-14 1999-06-15 Telefonaktiebolaget Lm Ericsson Integrated local communication system
US6005856A (en) * 1993-11-01 1999-12-21 Omnipoint Corporation Communication protocol for spread spectrum wireless communication system
US6021138A (en) * 1996-07-15 2000-02-01 Daewoo Telecom, Ltd. Digital cordless telephone system for a private automatic branch exchange
US6047177A (en) * 1996-01-26 2000-04-04 Telia Ab Method, device, and system for radio communication at short distances
US6058106A (en) * 1997-10-20 2000-05-02 Motorola, Inc. Network protocol method, access point device and peripheral devices for providing for an efficient centrally coordinated peer-to-peer wireless communications network
US6069588A (en) * 1999-02-11 2000-05-30 Ericsson Inc. Systems and methods for coaxially coupling an antenna to a radiotelephone through a window and amplifying signals adjacent and inside the window
US6259685B1 (en) * 1997-03-27 2001-07-10 Nokia Telecommunications Oy Method for channel allocation utilizing power restrictions
US6278699B1 (en) * 1998-06-22 2001-08-21 Telefonaktiebolaget Lm Ericsson (Publ) Synchronization techniques and systems for spread spectrum radiocommunication
US6396457B1 (en) * 2000-02-29 2002-05-28 Texas Instruments Incorporated Concentrator for coupling local wireless networks to a wired network
US6430395B2 (en) * 2000-04-07 2002-08-06 Commil Ltd. Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Family Cites Families (77)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5949776A (en) * 1990-01-18 1999-09-07 Norand Corporation Hierarchical communication system using premises, peripheral and vehicular local area networking
US5115463A (en) * 1990-06-25 1992-05-19 David Moldavsky Extended cordless telephone system
IL100213A (en) * 1990-12-07 1995-03-30 Qualcomm Inc CDMA microcellular telephone system and distributed antenna system therefor
IT1250515B (en) * 1991-10-07 1995-04-08 Sixtel Spa NETWORK FOR LOCAL AREA WITHOUT WIRES.
FI96157C (en) * 1992-04-27 1996-05-10 Nokia Mobile Phones Ltd Digital cellular radio telephone network based on time multiplexing to move a radio connection from the base station to a new base station
US5255307A (en) * 1992-05-07 1993-10-19 Sony Electronics Inc. Status indicator control for cellular mobile telephone system
US5396541A (en) 1992-10-23 1995-03-07 At&T Corp. Call handoff in a wireless telephone system
DE4317895C2 (en) * 1993-05-28 1996-11-14 Siemens Ag Method for synchronizing base stations in a multi-cellular, wireless telephone system
CA2123736C (en) * 1993-10-04 1999-10-19 Zygmunt Haas Packetized cellular system
US5537434A (en) * 1993-10-25 1996-07-16 Telefonaktiebolaget Lm Ericsson Frequency hopping control channel in a radio communication system
EP0656708A1 (en) * 1993-12-03 1995-06-07 International Business Machines Corporation System and method for the transmission and validation of an updated encryption key between two users
US5960344A (en) * 1993-12-20 1999-09-28 Norand Corporation Local area network having multiple channel wireless access
US5448569A (en) * 1994-04-12 1995-09-05 International Business Machines Corporation Handoff monitoring in cellular communication networks using slow frequency hopping
JPH089455A (en) * 1994-06-22 1996-01-12 Hitachi Ltd Radio communication system and communication equipment
US5745850A (en) * 1994-10-24 1998-04-28 Lucent Technologies, Inc. Apparatus and method for mobile (e.g. cellular or wireless) telephone call handover and impersonation
JP3244610B2 (en) * 1995-01-27 2002-01-07 株式会社日立製作所 Frequency hopping wireless LAN system
FI100444B (en) * 1995-02-20 1997-11-28 Nokia Mobile Phones Ltd Data transfer method and system
US5546411A (en) * 1995-02-28 1996-08-13 Motorola, Inc. Method and apparatus for adaptively selecting a communication strategy in a selective call radio communication system
JP3047767B2 (en) * 1995-03-20 2000-06-05 株式会社日立製作所 Wireless LAN system
US5594718A (en) * 1995-03-30 1997-01-14 Qualcomm Incorporated Method and apparatus for providing mobile unit assisted hard handoff from a CDMA communication system to an alternative access communication system
US5842138A (en) * 1995-05-04 1998-11-24 Interwave Communications International Ltd. Configuration-independent methods and apparatus for software communication in a cellular network
CN1185885A (en) * 1995-05-31 1998-06-24 西门子公司 Cellular cordless telecommunication system with ISDN connection
JPH0955978A (en) * 1995-08-11 1997-02-25 Fujitsu Ltd Method and device for radio frame synchronization between base stations
US5675629A (en) * 1995-09-08 1997-10-07 At&T Cordless cellular system base station
US5809415A (en) * 1995-12-11 1998-09-15 Unwired Planet, Inc. Method and architecture for an interactive two-way data communication network
US5987062A (en) * 1995-12-15 1999-11-16 Netwave Technologies, Inc. Seamless roaming for wireless local area networks
US6314081B1 (en) * 1996-01-18 2001-11-06 Ericsson Inc. High power short message service using dedicated carrier frequency
JPH09312874A (en) * 1996-03-19 1997-12-02 Canon Inc Radio communication equipment, radio communication system and their control method
JPH09289674A (en) * 1996-04-24 1997-11-04 Hitachi Ltd Radio interface monitor system for radio base station
US5784695A (en) * 1996-05-14 1998-07-21 Trw Inc. Method and apparatus for handover control in a satellite based telecommunications system
US5822313A (en) * 1996-05-24 1998-10-13 National Semiconductor Corporation Seamless handover in a cordless TDMA system
US6055427A (en) * 1996-07-18 2000-04-25 Nokia Telecommunications Oy Hard handoff and a radio system
US5896375A (en) * 1996-07-23 1999-04-20 Ericsson Inc. Short-range radio communications system and method of use
US6009332A (en) * 1996-08-28 1999-12-28 Telefonaktiebolaget Lm Ericsson Method and system for autonomously allocating a frequency hopping traffic channel in a private radio system
JP3622875B2 (en) * 1996-11-11 2005-02-23 ソニー株式会社 Pilot signal detection device, pilot signal detection method, and mobile communication terminal device
US6119006A (en) * 1997-01-03 2000-09-12 Siemens Information And Communication Systems, Inc. System and method for calendar-based cellular smart switching
CA2228493C (en) 1997-02-03 2005-05-03 Nippon Telegraph And Telephone Corporation Scheme for carrying out modular calculations based on redundant binary calculation
FR2761224B1 (en) * 1997-03-20 2001-10-05 Alsthom Cge Alkatel METHOD OF RECORDING AT LEAST ONE BIMODE MOBILE STATION WITH AN ASSOCIATED HOME BASE STATION
US6201962B1 (en) * 1997-05-14 2001-03-13 Telxon Corporation Seamless roaming among multiple networks including seamless transitioning between multiple devices
JP3478062B2 (en) * 1997-06-12 2003-12-10 三菱電機株式会社 Mobile communication system, mobile station, and base station
JP3088345B2 (en) * 1997-07-10 2000-09-18 日本電気株式会社 Phase synchronization error correction method and phase synchronization error correction system in telecommunications
US5872774A (en) * 1997-09-19 1999-02-16 Qualcomm Incorporated Mobile station assisted timing synchronization in a CDMA communication system
US6078571A (en) * 1997-09-19 2000-06-20 Motorola, Inc. Apparatus and method for transmitting beacon signals in a communication system
JP3856253B2 (en) * 1997-10-16 2006-12-13 ソニー株式会社 Cellular radio communication system and base station
JP3437070B2 (en) * 1997-10-20 2003-08-18 富士通株式会社 Subscriber wireless access system
DE19747534A1 (en) * 1997-10-28 1999-04-29 Cit Alcatel Digital telecommunications system with DECT interface for fax and data applications
US6175860B1 (en) * 1997-11-26 2001-01-16 International Business Machines Corporation Method and apparatus for an automatic multi-rate wireless/wired computer network
JP3080156B2 (en) * 1997-12-24 2000-08-21 日本電気株式会社 Automatic Gain Control Method for Frequency Hopping Communication Receiver
US6134440A (en) * 1998-01-26 2000-10-17 Qualcomm Inc. Method and apparatus for performing mobile station assisted hard handoff using off line searching
JP3540928B2 (en) * 1998-02-23 2004-07-07 株式会社日立コミュニケーションテクノロジー Telephone switching equipment
FI980517A (en) * 1998-03-06 1999-09-07 Nokia Networks Oy Procedure for handover
US6112094A (en) * 1998-04-06 2000-08-29 Ericsson Inc. Orthogonal frequency hopping pattern re-use scheme
JP3371801B2 (en) 1998-04-24 2003-01-27 三菱電機株式会社 Frequency hopping type mobile station, base station and mobile communication system
DE69937795T2 (en) * 1998-06-13 2008-04-30 Samsung Electronics Co., Ltd., Suwon METHOD AND DEVICE FOR STATE SYNCHRONIZATION IN A CDMA SYSTEM
KR100413418B1 (en) * 1998-07-10 2004-02-14 엘지전자 주식회사 Separated Soft Handoff Control Method of Reverse Link
DE19833777A1 (en) * 1998-07-27 2000-02-03 Siemens Ag Method, device and system for operating mobile telecommunication terminals in a public, cellular mobile radio network
KR20010085327A (en) * 1998-08-03 2001-09-07 추후제출 A plug and play wireless architecture supporting packet data and ip voice/multimedia services
CN1135885C (en) * 1998-09-03 2004-01-21 因特威夫通讯有限公司 Cellular network communication system
FI108200B (en) * 1998-09-14 2001-11-30 Nokia Mobile Phones Ltd Switching the connection between mobile networks
US6519236B1 (en) * 1998-09-18 2003-02-11 Telefonaktiebolaget Lm Ericsson (Publ) Automatic power control in uncoordinated frequency-hopping radio systems
EP1011274A1 (en) * 1998-12-16 2000-06-21 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Method and service providing means for providing services in a telecommunication network
US6600734B1 (en) * 1998-12-17 2003-07-29 Symbol Technologies, Inc. Apparatus for interfacing a wireless local network and a wired voice telecommunications system
US6205552B1 (en) * 1998-12-31 2001-03-20 Mci Worldcom, Inc. Method and apparatus for checking security vulnerability of networked devices
JP2000224102A (en) * 1999-01-29 2000-08-11 Nec Corp System for controlling downstream line transmission power
US6724739B1 (en) * 1999-02-25 2004-04-20 Qualcomm, Incorporated Method for handoff between an asynchronous CDMA base station and a synchronous CDMA base station
US6456606B1 (en) * 1999-03-24 2002-09-24 Qualcomm Incorporated Handoff control in an asynchronous CDMA system
US6490446B1 (en) * 1999-04-09 2002-12-03 Telefonaktiebolaget Lm Ericsson (Publ) Uncoordinated frequency hopping cellular system
US6574266B1 (en) * 1999-06-25 2003-06-03 Telefonaktiebolaget Lm Ericsson (Publ) Base-station-assisted terminal-to-terminal connection setup
US6628632B1 (en) * 1999-07-19 2003-09-30 Lucent Technologies Inc. Method and apparatus for permitting direct handoff between base stations in a wireless network
US6625198B1 (en) * 1999-08-13 2003-09-23 Qualcomm Incorporated Method and apparatus for concurrently processing multiple calls in a spread spectrum communications system
US6675015B1 (en) * 1999-09-15 2004-01-06 Nokia Corporation Apparatus, and associated method, for facilitating communication handovers in a bluetooth-public-access radio communication system
US6650871B1 (en) * 1999-10-14 2003-11-18 Agere Systems Inc. Cordless RF range extension for wireless piconets
AU2001235001A1 (en) * 2000-02-11 2001-08-20 Richard A. Geving Device and method for transmitting vehicle position
US6640098B1 (en) * 2000-02-14 2003-10-28 Action Engine Corporation System for obtaining service-related information for local interactive wireless devices
US7173923B2 (en) 2000-03-17 2007-02-06 Symbol Technologies, Inc. Security in multiple wireless local area networks
US7173922B2 (en) 2000-03-17 2007-02-06 Symbol Technologies, Inc. Multiple wireless local area networks occupying overlapping physical spaces
US6665541B1 (en) * 2000-05-04 2003-12-16 Snaptrack, Incorporated Methods and apparatuses for using mobile GPS receivers to synchronize basestations in cellular networks

Patent Citations (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4617674A (en) * 1983-07-14 1986-10-14 Rca Corporation Synchronizing system for spread spectrum transmissions between small earth stations by satellite via an intermediate hop to a large earth station
US5410588A (en) * 1991-04-03 1995-04-25 Kabushiki Kaisha Toshiba Mobile radio communications system having a supervising radio transmitting station for transmitting a reference synchronizing signal to a first and second base stations via a radio link
US6011975A (en) * 1992-03-05 2000-01-04 Bell Atlantic Network Services, Inc. Method of personal communications service using wireline/wireless integration detecting a predetermined event during process of a call
US5506887A (en) * 1992-03-05 1996-04-09 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5353331A (en) * 1992-03-05 1994-10-04 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5579379A (en) * 1992-03-05 1996-11-26 Bell Atlantic Network Services, Inc. Personal communications service having a calling party pays capability
US5664005A (en) * 1992-03-05 1997-09-02 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5469496A (en) * 1992-03-05 1995-11-21 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5758281A (en) * 1992-03-05 1998-05-26 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US5610972A (en) * 1992-03-05 1997-03-11 Bell Atlantic Network Services, Inc. Personal communications service using wireline/wireless integration
US6005856A (en) * 1993-11-01 1999-12-21 Omnipoint Corporation Communication protocol for spread spectrum wireless communication system
US5715521A (en) * 1994-04-22 1998-02-03 Oki Electric Industry Co., Ltd. Method of controlling synchronization signal power in a communication system
US5845211A (en) * 1995-01-13 1998-12-01 Bell South Corporation Wireless digital network
US5999813A (en) * 1995-05-04 1999-12-07 Interwave Communications Overlay cellular communication system
US5818824A (en) * 1995-05-04 1998-10-06 Interwave Communications International, Ltd. Private multiplexing cellular network
US5734699A (en) * 1995-05-04 1998-03-31 Interwave Communications International, Ltd. Cellular private branch exchanges
US5887256A (en) * 1995-05-04 1999-03-23 Interwave Communications International, Ltd. Hybrid cellular communication apparatus and method
US5911120A (en) * 1995-09-08 1999-06-08 At&T Wireless Services Wireless communication system having mobile stations establish a communication link through the base station without using a landline or regional cellular network and without a call in progress
US6047177A (en) * 1996-01-26 2000-04-04 Telia Ab Method, device, and system for radio communication at short distances
US5913163A (en) * 1996-03-14 1999-06-15 Telefonaktiebolaget Lm Ericsson Integrated local communication system
US6021138A (en) * 1996-07-15 2000-02-01 Daewoo Telecom, Ltd. Digital cordless telephone system for a private automatic branch exchange
US6259685B1 (en) * 1997-03-27 2001-07-10 Nokia Telecommunications Oy Method for channel allocation utilizing power restrictions
US6058106A (en) * 1997-10-20 2000-05-02 Motorola, Inc. Network protocol method, access point device and peripheral devices for providing for an efficient centrally coordinated peer-to-peer wireless communications network
US6278699B1 (en) * 1998-06-22 2001-08-21 Telefonaktiebolaget Lm Ericsson (Publ) Synchronization techniques and systems for spread spectrum radiocommunication
US6069588A (en) * 1999-02-11 2000-05-30 Ericsson Inc. Systems and methods for coaxially coupling an antenna to a radiotelephone through a window and amplifying signals adjacent and inside the window
US6396457B1 (en) * 2000-02-29 2002-05-28 Texas Instruments Incorporated Concentrator for coupling local wireless networks to a wired network
US6430395B2 (en) * 2000-04-07 2002-08-06 Commil Ltd. Wireless private branch exchange (WPBX) and communicating between mobile units and base stations

Cited By (71)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7107057B2 (en) 2000-04-07 2006-09-12 Commil Ltd. Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20020160779A1 (en) * 2000-04-07 2002-10-31 Commil Ltd Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20020160806A1 (en) * 2000-04-07 2002-10-31 Commil Ltd Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20020164991A1 (en) * 2000-04-07 2002-11-07 Commil Ltd Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20020147016A1 (en) * 2000-04-07 2002-10-10 Commil Ltd Was Filed In Parent Case Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US7274934B2 (en) 2000-04-07 2007-09-25 Commil Usa Llc Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US7231212B2 (en) 2000-04-07 2007-06-12 Commil Usa, Llc Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US7215952B2 (en) 2000-04-07 2007-05-08 Commil Usa, Llc Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20040192211A1 (en) * 2001-02-26 2004-09-30 Gallagher Michael D. Apparatus for supporting the handover of a telecommunication session between a licensed wireless system and an unlicensed wireless system
US7720481B2 (en) 2001-02-26 2010-05-18 Kineto Wireless, Inc. Apparatus for supporting the handover of a telecommunication session between a licensed wireless system and an unlicensed wireless system
US6922559B2 (en) 2001-02-26 2005-07-26 Kineto Wireless, Inc. Unlicensed wireless communications base station to facilitate unlicensed and licensed wireless communications with a subscriber device, and method of operation
US8160588B2 (en) 2001-02-26 2012-04-17 Kineto Wireless, Inc. Method and apparatus for supporting the handover of a telecommunication session between a licensed wireless system and an unlicensed wireless system
US7996009B2 (en) 2001-02-26 2011-08-09 Kineto Wireless, Inc. Method for authenticating access to an unlicensed wireless communications system using a licensed wireless communications system authentication process
US7890099B2 (en) 2001-02-26 2011-02-15 Kineto Wireless, Inc. Method for automatic and seamless call transfers between a licensed wireless system and an unlicensed wireless system
US20030119480A1 (en) * 2001-02-26 2003-06-26 Jahangir Mohammed Apparatus and method for provisioning an unlicensed wireless communications base station for operation within a licensed wireless communications system
US20030119490A1 (en) * 2001-02-26 2003-06-26 Jahangir Mohammed Wireless communications handset for facilitating licensed and unlicensed wireless communications, and method of operation
US20040009749A1 (en) * 2001-03-20 2004-01-15 Nitzan Arazi Wireless private branch exchange(wpbx) and communicating between mobile units and base stations
US9490857B2 (en) 2002-09-20 2016-11-08 Iii Holdings 1, Llc Systems and methods for parallel signal cancellation
US9544044B2 (en) 2002-09-20 2017-01-10 Iii Holdings 1, Llc Systems and methods for parallel signal cancellation
US9647708B2 (en) 2002-09-20 2017-05-09 Iii Holdings 1, Llc Advanced signal processors for interference cancellation in baseband receivers
US7885644B2 (en) 2002-10-18 2011-02-08 Kineto Wireless, Inc. Method and system of providing landline equivalent location information over an integrated communication system
US7949326B2 (en) 2002-10-18 2011-05-24 Kineto Wireless, Inc. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7668558B2 (en) 2002-10-18 2010-02-23 Kineto Wireless, Inc. Network controller messaging for paging in an unlicensed wireless communication system
US7684803B2 (en) 2002-10-18 2010-03-23 Kineto Wireless, Inc. Network controller messaging for ciphering in an unlicensed wireless communication system
US8165585B2 (en) 2002-10-18 2012-04-24 Kineto Wireless, Inc. Handover messaging in an unlicensed mobile access telecommunications system
US8130703B2 (en) 2002-10-18 2012-03-06 Kineto Wireless, Inc. Apparatus and messages for interworking between unlicensed access network and GPRS network for data services
US7769385B2 (en) 2002-10-18 2010-08-03 Kineto Wireless, Inc. Mobile station messaging for registration in an unlicensed wireless communication system
US7773993B2 (en) 2002-10-18 2010-08-10 Kineto Wireless, Inc. Network controller messaging for channel activation in an unlicensed wireless communication system
US8090371B2 (en) 2002-10-18 2012-01-03 Kineto Wireless, Inc. Network controller messaging for release in an unlicensed wireless communication system
US7818007B2 (en) 2002-10-18 2010-10-19 Kineto Wireless, Inc. Mobile station messaging for ciphering in an unlicensed wireless communication system
WO2004036770A3 (en) * 2002-10-18 2004-07-08 Kineto Wireless Inc Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US20040116120A1 (en) * 2002-10-18 2004-06-17 Gallagher Michael D. Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7873015B2 (en) 2002-10-18 2011-01-18 Kineto Wireless, Inc. Method and system for registering an unlicensed mobile access subscriber with a network controller
KR100822120B1 (en) 2002-10-18 2008-04-14 키네토 와이어리즈 인코포레이션 Apparatus and method for extending the coverage area of a licensed wireless communication system using an unlicensed wireless communication system
US7107055B2 (en) 2002-10-18 2006-09-12 Kineto, Wireless, Inc. Mobile station GPRS implementation for switching between licensed and unlicensed wireless systems
US7974624B2 (en) 2002-10-18 2011-07-05 Kineto Wireless, Inc. Registration messaging in an unlicensed mobile access telecommunications system
US7953423B2 (en) 2002-10-18 2011-05-31 Kineto Wireless, Inc. Messaging in an unlicensed mobile access telecommunications system
EP1420601A2 (en) * 2002-11-06 2004-05-19 Samsung Electronics Co. Ltd. Wireless communication system and a hand-off method therefor
EP1420601A3 (en) * 2002-11-06 2006-09-13 Samsung Electronics Co. Ltd. Wireless communication system and a hand-off method therefor
US7929977B2 (en) 2003-10-17 2011-04-19 Kineto Wireless, Inc. Method and system for determining the location of an unlicensed mobile access subscriber
US7957348B1 (en) 2004-04-21 2011-06-07 Kineto Wireless, Inc. Method and system for signaling traffic and media types within a communications network switching system
US8041385B2 (en) 2004-05-14 2011-10-18 Kineto Wireless, Inc. Power management mechanism for unlicensed wireless communication systems
US7809381B2 (en) * 2004-07-16 2010-10-05 Bridgeport Networks, Inc. Presence detection for cellular and internet protocol telephony
US10517140B2 (en) 2004-08-24 2019-12-24 Comcast Cable Communications, Llc Determining a location of a device for calling via an access point
US10070466B2 (en) 2004-08-24 2018-09-04 Comcast Cable Communications, Llc Determining a location of a device for calling via an access point
US9648644B2 (en) 2004-08-24 2017-05-09 Comcast Cable Communications, Llc Determining a location of a device for calling via an access point
US11252779B2 (en) 2004-08-24 2022-02-15 Comcast Cable Communications, Llc Physical location management for voice over packet communication
US7933598B1 (en) 2005-03-14 2011-04-26 Kineto Wireless, Inc. Methods and apparatuses for effecting handover in integrated wireless systems
US7756546B1 (en) 2005-03-30 2010-07-13 Kineto Wireless, Inc. Methods and apparatuses to indicate fixed terminal capabilities
US8045493B2 (en) 2005-08-10 2011-10-25 Kineto Wireless, Inc. Mechanisms to extend UMA or GAN to inter-work with UMTS core network
US7843900B2 (en) 2005-08-10 2010-11-30 Kineto Wireless, Inc. Mechanisms to extend UMA or GAN to inter-work with UMTS core network
US20070054680A1 (en) * 2005-08-19 2007-03-08 Matsushita Electric Industrial Co., Ltd. Method of band multiplexing to improve system capacity for a multi-band communication system
US7454218B2 (en) * 2005-08-19 2008-11-18 Panasonic Corporation Method of band multiplexing to improve system capacity for a multi-band communication system
US20090323572A1 (en) * 2005-08-26 2009-12-31 Jianxiong Shi Intelligent access point scanning with self-learning capability
US7904084B2 (en) 2005-08-26 2011-03-08 Kineto Wireless, Inc. Intelligent access point scanning with self-learning capability
US8165086B2 (en) 2006-04-18 2012-04-24 Kineto Wireless, Inc. Method of providing improved integrated communication system data service
US7852817B2 (en) 2006-07-14 2010-12-14 Kineto Wireless, Inc. Generic access to the Iu interface
US7912004B2 (en) 2006-07-14 2011-03-22 Kineto Wireless, Inc. Generic access to the Iu interface
US8005076B2 (en) 2006-07-14 2011-08-23 Kineto Wireless, Inc. Method and apparatus for activating transport channels in a packet switched communication system
US7995994B2 (en) 2006-09-22 2011-08-09 Kineto Wireless, Inc. Method and apparatus for preventing theft of service in a communication system
US8073428B2 (en) 2006-09-22 2011-12-06 Kineto Wireless, Inc. Method and apparatus for securing communication between an access point and a network controller
US8204502B2 (en) 2006-09-22 2012-06-19 Kineto Wireless, Inc. Method and apparatus for user equipment registration
US8036664B2 (en) 2006-09-22 2011-10-11 Kineto Wireless, Inc. Method and apparatus for determining rove-out
US8150397B2 (en) 2006-09-22 2012-04-03 Kineto Wireless, Inc. Method and apparatus for establishing transport channels for a femtocell
US8577291B1 (en) * 2007-02-01 2013-11-05 Broadcom Corporation Method and system for optimizing data throughput in a bluetooth communication system
US20140056170A1 (en) * 2007-02-01 2014-02-27 Broadcom Corporation Method and System for Optimizing Data Throughput in a Bluetooth Communication System
US8892043B2 (en) * 2007-02-01 2014-11-18 Broadcom Corporation Method and system for optimizing data throughput in a bluetooth communication system
US8019331B2 (en) 2007-02-26 2011-09-13 Kineto Wireless, Inc. Femtocell integration into the macro network
US8041335B2 (en) 2008-04-18 2011-10-18 Kineto Wireless, Inc. Method and apparatus for routing of emergency services for unauthorized user equipment in a home Node B system
US9774695B2 (en) 2009-06-17 2017-09-26 Counterpath Corporation Enhanced presence detection for routing decisions
US9265073B2 (en) 2010-05-21 2016-02-16 Kineto Wireless, Llc System and method for dual mode communication

Also Published As

Publication number Publication date
JP2004509481A (en) 2004-03-25
US20020160779A1 (en) 2002-10-31
KR20030014201A (en) 2003-02-15
US20080026775A1 (en) 2008-01-31
EP2346213A2 (en) 2011-07-20
US7107057B2 (en) 2006-09-12
EP2296402A3 (en) 2012-06-13
JP5819342B2 (en) 2015-11-24
US7499717B2 (en) 2009-03-03
US7231212B2 (en) 2007-06-12
EP2296401A2 (en) 2011-03-16
US20020164991A1 (en) 2002-11-07
EP1279235A4 (en) 2007-12-12
EP2296417A3 (en) 2012-06-20
JP4754146B2 (en) 2011-08-24
WO2001078246A1 (en) 2001-10-18
US20020160806A1 (en) 2002-10-31
AU2001249274A1 (en) 2001-10-23
US20010041594A1 (en) 2001-11-15
US6430395B2 (en) 2002-08-06
EP2296401A3 (en) 2012-06-20
EP2296402A2 (en) 2011-03-16
US7274934B2 (en) 2007-09-25
US20020147016A1 (en) 2002-10-10
EP2315475A2 (en) 2011-04-27
EP1279235B1 (en) 2017-10-25
EP2315475A3 (en) 2012-05-23
EP2296417A2 (en) 2011-03-16
EP2315475B1 (en) 2018-11-07
US7215952B2 (en) 2007-05-08
EP2346213A3 (en) 2012-05-23
JP2013168978A (en) 2013-08-29
EP1279235A1 (en) 2003-01-29
JP2011182424A (en) 2011-09-15

Similar Documents

Publication Publication Date Title
US7231212B2 (en) Wireless private branch exchange (WPBX) and communicating between mobile units and base stations
US20040009749A1 (en) Wireless private branch exchange(wpbx) and communicating between mobile units and base stations
US20040077349A1 (en) Handoff method for wireless private branch exchange enabled for standard cellular handsets and wireless data devices
EP0856232B1 (en) A method for performing handover and roaming in a radio communication environment
US7613171B2 (en) Cellular network service over WLAN
RU2353073C2 (en) Service forwarding between wireless local network and cellular system
JP2004509481A5 (en)
JPH07177558A (en) Packeted cellar communication
KR20130036861A (en) Mobile terminal and method for executing handoff thereof
RU2354051C2 (en) Communications controller and method for communications connection flow control during repeated cell selection
WO2002058248A2 (en) Handoff methods for wireless private branch exchange
Lin et al. Implementing automatic location update for follow-me database using VoIP and bluetooth technologies
JP4021110B2 (en) PHS channel switching method
GB2386035A (en) A method of routing communications between networks dependent on access levels

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: COMMIL USA LLC, TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COMMIL, LTD.;REEL/FRAME:019084/0328

Effective date: 20070318