EP3209062A1 - Systems and methods for triggering wireless access point handovers - Google Patents

Systems and methods for triggering wireless access point handovers Download PDF

Info

Publication number
EP3209062A1
EP3209062A1 EP16156298.8A EP16156298A EP3209062A1 EP 3209062 A1 EP3209062 A1 EP 3209062A1 EP 16156298 A EP16156298 A EP 16156298A EP 3209062 A1 EP3209062 A1 EP 3209062A1
Authority
EP
European Patent Office
Prior art keywords
aps
mobile device
velocity
time
access point
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
EP16156298.8A
Other languages
German (de)
French (fr)
Other versions
EP3209062B1 (en
Inventor
Zvi Reznic
Doron Ezri
Avi WEITZMAN
Ohad Klausner
Yungui Wang
Xingfeng Jiang
Wei Ruan
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co 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
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP16156298.8A priority Critical patent/EP3209062B1/en
Publication of EP3209062A1 publication Critical patent/EP3209062A1/en
Application granted granted Critical
Publication of EP3209062B1 publication Critical patent/EP3209062B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G01MEASURING; TESTING
    • G01SRADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
    • G01S11/00Systems for determining distance or velocity not using reflection or reradiation
    • G01S11/02Systems for determining distance or velocity not using reflection or reradiation using radio waves
    • G01S11/06Systems for determining distance or velocity not using reflection or reradiation using radio waves using intensity measurements
    • 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/0085Hand-off measurements
    • 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/00837Determination of triggering parameters for hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/322Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/24Reselection being triggered by specific parameters
    • H04W36/32Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W64/00Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination
    • 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/12WLAN [Wireless Local Area Networks]

Definitions

  • the present invention in some embodiments thereof, relates to wireless networking and, more specifically, but not exclusively, to management of changing access points used by a mobile device accessing a wireless network.
  • Mobile devices communicate wirelessly with Access Points (AP) that provide connectivity to a network.
  • AP Access Points
  • Each AP is limited to providing communication services to mobile devices located in a certain geographical area. Mobile devices moving from one geographical location to another geographical location may need to switch from using one AP to another AP.
  • the process of changing APs may also be termed BSS transition, or Handover.
  • a device for managing access point connections is configured to: determine signal reception data related to a mobile device registered to one or more access points (AP), access an access point mapping dataset indicative of geographical distances between the APs, calculate a crossover time in which the mobile device crosses over one of the APs by analyzing the signal reception data, estimate a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of the APs from the access point mapping dataset; and determine a handover time from one of the APs to another of the APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
  • AP access points
  • the device, system and/or method described herein allow for the handover to occur when the mobile device is located within overlapping coverage area, which may be a relatively small range of time (e.g., 1-10 seconds) when the mobile device is moving quickly and/or when the coverage range provided by each AP is relatively small.
  • the handover may occur when the client is not aware of wireless parameters values at the next AP (e.g., frequency, cell size, cell location, location of client within the cell, location and/or size of the overlapping area) and would otherwise be unable to perform the handoff during the limited time spent in the overlapping area, resulting in a gap in coverage.
  • the device, system, and/or method described herein improve data throughout, bandwidth, and/or utilization of the available wireless channel by allowing different APs to use different channels while providing fast moving mobile devices with handoffs without disconnection of wireless services, which improves channel utilization by reducing or preventing unused channels.
  • the handover time is calculated at the AP side without necessarily providing special instructions to the mobile device, for example, the mobile device is not instructed to switch to a different frequency of the next AP, then switch back to the original frequency of the current AP and report the RSSI measured in the other channel for processing by the AP, for example, as defined by the 802.11k protocol.
  • the device, system, and/or method described herein perform the processing to determine the handover time at the AP side, without necessarily requiring the mobile device to support a special protocol or perform special functions (e.g., to collect data and/or transmit data) to assist the AP with determining the handover time, providing support to a wide range of different mobile device implementing different wireless communication protocols.
  • the signal reception data is a received Signal Strength Indicator (RSSI) identified by one of the APs and related to the mobile device.
  • RSSI received Signal Strength Indicator
  • the signal reception data is a direction indicator calculated according to reading of first and second groups of directional antennas; wherein directional antennas of the first group and the directional antennas of the second group are facing opposite directions.
  • the APs are geographically distributed along at least one road.
  • the device is further configured to receive a past handover time during which a service given to the mobile device by one of the APs was exchanged by a similar service given to the mobile device by another of the APs, wherein the velocity is estimated based on a difference between the past handover time and the crossover time.
  • the velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • the device is further configured to receive a past crossover time during which the mobile device passed by one of the APs, wherein the velocity is estimated based on a difference between the past crossover time and the crossover time.
  • the velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • the velocity is estimated based on a weighted function that takes into account a past velocity of the mobile device and an average velocity calculated for mobile devices moving in a road passing between a first of the APs which currently gives service to the mobile device and a second of the APs which designated to give service to the mobile device instead of the first AP.
  • the weighted average function and/or the average velocity calculated for other mobile devices may be used in cases where the velocity of the mobile device varies, for example, due to traffic (or other reasons).
  • the weighted average function and/or average velocity calculate for other mobile devices may improve the accuracy of estimating when the mobile device will reach the handover point, such as when the velocity before and after the crossover point are significantly different (i.e., that assuming a constant velocity will result in an error large enough that the determined handover point will result in a gap in wireless service).
  • the velocity is estimated is calculated based on the time taken to the mobile device to pass a known distance between a third AP and the first AP.
  • the handover time is a future handover time during which a service given to the mobile device by one of the APs is exchanged by a similar service given to the mobile device by another of the APs.
  • Handing service over at the determined handover time maintains continuity of the wireless service to the moving mobile device, without data transfer gaps or disruptions.
  • the APs provide service for mobile clients by wireless signals having frequencies clustered around 2.4 gigahertz (GHz) and/or 5 GHz.
  • GHz gigahertz
  • the device, system, and/or method described herein maintains continuity of communication service for mobile devices serviced by APs with relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlap areas.
  • the APs provide a Wi-Fi based service to the mobile device.
  • the device, system, and/or method described herein provide faster handoff as compared to other methods based on other wireless communication data transfer protocols (e.g., 802.11r), that maintains wireless connectivity for fast moving mobile devices, for example, located within cars travelling on highways (e.g., about 100 kilometers per hour, or about 80 km/h, or about 120 km/h, or other speeds).
  • 802.11r wireless communication data transfer protocols
  • the handover time is determined to occur during an overlap region in which service provided by the one of the APs and the another of the APs overlap, and wherein the mobile device is estimated to remain within the overlap region for less than about one second.
  • the device, system, and/or method described herein maintains continuity of communication service for mobile devices moving quickly relative to APs (e.g., located within a car on a highway, or a train).
  • APs e.g., located within a car on a highway, or a train.
  • the geographical distance between any two of the APs is less than 1000 meters.
  • the device, system, and/or method described herein maintains continuity of communication service for mobile devices serviced by APs with relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlap areas.
  • a method for managing access point connections comprises determining signal reception data related to a mobile device registered to one or more APs, accessing an access point mapping dataset indicative of geographical distances between the APs, calculating a crossover time in which the mobile device crosses over one of the APs by analyzing the signal reception data, estimating a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of the APs from the access point mapping dataset, and determining a handover time from one of the APs to another of the APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
  • the present invention in some embodiments thereof, relates to wireless networking and, more specifically, but not exclusively, to management of changing access points used by a mobile device accessing a wireless network.
  • An aspect of some embodiments of the present invention relates to a device (e.g., processing unit), system and/or method (e.g., implemented by code instructions stored in a memory executed by a processor) that determines a handover time for a moving mobile device (e.g., a Smartphone in a car driving on a road) from one access point (AP) to another AP.
  • the handover time is calculated based on a determined crossover time (when the mobile device crosses over one of the APs), an estimated velocity of the mobile device, and a geographical distance defined relative to one or more of the APs.
  • the device, system, and/or method described herein maintains continuity of wireless communication service for mobile devices moving quickly relative to APs (e.g., when the mobile device is located within a car driving on a highway), for mobile devices communicating with APs having a relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlapping service areas.
  • Continuity of service may be maintained for applications that cannot tolerate gaps in service, for example, voice over internet protocol (VoIP) calls.
  • VoIP voice over internet protocol
  • the crossover time is determined based on an analysis of signal data (e.g., packets transmitted by the mobile device) received by the AP, optionally measured based on a received Signal Strength Indicator (RSSI).
  • RSSI Signal Strength Indicator
  • a direction indicator is calculated based on the difference between signal readings from a first group of directional antennas and a second group of directional antennas.
  • the first and second group of directional antennas are associated with the same AP, facing in opposite directions, one group facing towards the moving mobile device and another group facing away from the mobile device.
  • the direction indicator changes sign (e.g., from positive to negative, or from negative to positive), and/or when the value of the directional indicator is about zero, the direction indicator represents the time at which the mobile device is crossing over the AP.
  • the handover time may be selected to correspond to overlapping coverage areas between neighboring APs (i.e., the two APs involved in the handover) such that the handover occurs within the overlapping area.
  • the device, system and/or method described herein allow for the handover to occur when the mobile device is located within overlapping coverage area, which may be a relatively small range of time (e.g., 0.3-1 second, or 1-2 seconds) when the mobile device is moving quickly and/or when the coverage range provided by each AP is relatively small.
  • the handover may occur when the client is not aware of wireless parameters values at the next AP (e.g., frequency, cell size, cell location, location of client within the cell, location and/or size of the overlapping area) and would otherwise be unable to perform the handoff during the limited time spent in the overlapping area, resulting in a gap in coverage.
  • wireless parameters values at the next AP e.g., frequency, cell size, cell location, location of client within the cell, location and/or size of the overlapping area
  • the present invention may be a system, a method, and/or a computer program product.
  • the computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
  • the computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
  • the computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • a network for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • the computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
  • FPGA field-programmable gate arrays
  • PLA programmable logic arrays
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the figures.
  • two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
  • FIG. 1 is a flowchart of a method for managing AP connections for a moving mobile device by determining a handover time from one of the APs to another of the APs, in accordance with some embodiments of the present invention.
  • FIG. 2 is a diagram of components of a system 200 that allows a moving mobile device 202 to maintain communication connectivity with a network 204 by determining handover time(s) from one AP 206A to another AP 206B, in accordance with some embodiments of the present invention.
  • the device, system, and/or method described herein provide faster handoff as compared to other methods based on other wireless communication data transfer protocols (e.g., 802.11r), that maintains wireless connectivity for fast moving mobile devices, for example, located within cars travelling on highways (e.g., about 100 kilometers per hour, or about 80 km/h, or about 120 km/h, or other speeds).
  • 802.11r wireless communication data transfer protocols
  • the device, system, and/or method described herein improve data throughout, bandwidth, and/or utilization of the available wireless channel by allowing different APs to use different channels while providing fast moving mobile devices with handoffs without disconnection of wireless services, which improves channel utilization by reducing or preventing unused channels.
  • the handover time is calculated at the AP side without necessarily providing special instructions to the mobile device, for example, the mobile device is not instructed to switch to a different frequency of the next AP, then switch back to the original frequency of the current AP and report the RSSI measured in the other channel for processing by the AP, for example, as defined by the 802.11k protocol.
  • the device, system, and/or method described herein perform the processing to determine the handover time at the AP side, without necessarily requiring the mobile device to support a special protocol or perform special functions (e.g., to collect data and/or transmit data) to assist the AP with determining the handover time, providing support to a wide range of different mobile device implementing different wireless communication protocols.
  • the mobile device does not necessarily make its own handoff decisions, and/or does not necessarily measure RSSI to determine which AP to connect to (e.g., the AP with the highest RSSI), which reduces or prevents scenarios in which the mobile device connects to a less optimal AP, for example, when a truck is located in front of the mobile device hiding the next AP but not the current AP, the client may remain connected to the current AP even when a better scenario is to switch to the next AP (since the mobile device is moving and the blockage will end shortly).
  • RSSI to determine which AP to connect to
  • System 200 allows end users using mobile device(s) 202 to connect to network 204 while moving, for example, travelling in a car (or bus or truck) on a highway (or other road), in a boat travelling within a canal or close to shore, or on a train or subway.
  • Each mobile device(s) 202 includes or is in communication with one or more antennas 208 that provide wireless connectivity 222 with one or more antennas 210 of APs 206A-B.
  • Each AP 206A-B includes or is in communication with a network interface 220 that provides connectivity to network 204, providing mobile device(s) 202 with access to network 204.
  • Exemplary network(s) 204 include: the internet, a cellular network, a local area network, a city network, and a private network.
  • wireless connectivity 222 is based on a wireless computing technology designed for transfer of data (e.g., packets), optionally based on a Wi-Fi standard.
  • APs 206A-B are geographically distributed, optionally based on expected movement direction(s) of mobile device(s) 202, for example, along one or more roads.
  • the geographically distribution, such as the distance between APs 206A-B may be based on the range of wireless transmission (e.g., based on the selected wireless protocols providing communication services 222).
  • the geographical distance between any two APs may be, for example, about 200-500 meters, or about 500-1000 meters, or less than about 1000 meters, or about 1000-1500 meters, or about 1500-2000 meters, or other value ranges.
  • Antennas 210 are directional antennas arranged into at least two groups (each group include one or more antennas). Each antennas group is arranged to face towards moving mobile device 202, or away from moving mobile device 202. For example, when mobile device 202 is moving along a road, rail road, or canal, and APs 206A-B are installed along the side of the road, and directional antennas 210 are arranged to face towards mobile device 202, or away from mobile device 202.
  • the groups of directional antennas 210 are arranged opposite to one another. There may be, for example, 3 or 4 antennas 210 in each group, or 3 or 4 antennas 210 in total split between the two groups.
  • Exemplary antenna values include a gain of at least about 27decibels relative to isotropic (dBi) at 2.4 Gigahertz (Ghz).
  • AP 206A may provide service to mobile devices by wireless signals having frequencies clustered around 2.4 Ghz and/or 5 Ghz (optionally at both frequencies).
  • AP 206A-B may be installed to provide support to cases in which mobile device 202 has a line of sight with antenna(s) 210 (e.g., the user sitting in the front seat of the car using a Smartphone to surface the internet) and/or when mobile device 202 does not have a line of sight with antenna(s) 210 (e.g., the user sitting in the back seat holding the Smartphone on the seat).
  • APs 206A-B may be installed, for example, within existing wireless and/or cellular base stations, on poles, on traffic lights, on highway lighting poles, on bridges, on buildings, on fences at the side of roads, or other locations.
  • APs 206A-B may be installed to provide a line of sight with cars and/or moving mobile device(s) 202, for example, close to the road, above the road, and/or between lanes.
  • APs 206A-B may be installed at a height of about 4-8 meters above the expected locations of mobile devices 202 (e.g., above the surface of the road).
  • Each AP 206A-B may cover one direction of road travel.
  • Two APs 206A-B covering two cells may be installed on the same pole (or other location), with one cell of one AP covering lanes closer to the AP having one direction of travel and another cell of the other AP covering lanes further away of traffic in the opposite direction.
  • Exemplary mobile devices 202 include: smartphone, laptop, tablet computer, wearable computing device, glasses computing device, and watch computing device.
  • Each AP 206A-B may include a computing unit 212 that includes a processing unit 214 and memory 216 for storing instruction code executable by processing unit 214.
  • Computing unit 212 may be implemented, for example, as software installed on a base station computer, as a hardware card plugged into existing base station equipment, and/or as a stand-along unit in communication with base station equipment (e.g., using cables and/or a wireless connection).
  • computing unit 212 is implemented within a wireless network management server 250 in communication with AP 206A-B and/or other communication channel(s).
  • Server 250 provides centralized control of the wireless network, by receiving data from APts 206A-B (e.g., RSSI and/or other signal reception data, as described herein), analyzing the received data (e.g., calculating the directional indicator, crossover time, and/or handover time, as described herein), and transmitting instructions to APs 206A-B (e.g., when to handover the mobile device).
  • Server 250 may implement self organizing network (SON) code.
  • management server 250 is implemented within one or more AP 206A-B.
  • the AP hosting management server 250 may be designated as the AP group leader.
  • APs 206A-B (and other APs not shown) may form one or more management groups and elect one of the APs per management group to perform the functions of managements server 250.
  • Processing unit 214 may be implemented, for example, as a central processing unit(s) (CPU), a graphics processing unit(s) (GPU), field programmable gate array(s) (FPGA), digital signal processor(s) (DSP), and application specific integrated circuit(s) (ASIC).
  • Processing unit(s) 214 may include one or more processors (homogenous or heterogeneous), which may be arranged for parallel processing, as clusters and/or as one or more multi core processing units.
  • Memory 216 stores code instructions executed by processing unit 214, for example, a random access memory (RAM), read-only memory (ROM), and/or a storage device, for example, non-volatile memory, magnetic media, semiconductor memory devices, hard drive, removable storage, and optical media (e.g., DVD, CD-ROM).
  • RAM random access memory
  • ROM read-only memory
  • storage device for example, non-volatile memory, magnetic media, semiconductor memory devices, hard drive, removable storage, and optical media (e.g., DVD, CD-ROM).
  • Computing unit 212 includes a storage unit 218 that acts as a data repository for storing data, for example, a memory, a hard-drive, an optical disc, a storage unit, an interface to a remote storage server, and interface to a cloud server, and/or other storage units.
  • Storage unit 218 may store an AP mapping dataset 218A, as described herein.
  • AP mapping dataset 218A is stored on network management server 250.
  • AP mapping dataset 218A is stored on a server accessible to multiple APs 206A-B and/or network management server 250, for example, a network connected server accessible via network 204.
  • one mobile device 202 is depicted. It is understood that multiple mobile devices 202 may be simultaneously communicating with APs 206A-B. The multiple mobile devices 202 may be travelling in different directions (e.g., opposite to one another, for example, differ directions on highway lanes). Moreover, it is understood that two APs 206A-B are shown for clarity of explanation, however system 200 may include a large number of APs.
  • FIG. 3 is a schematic depicting an example environment in which the device (e.g., AP 206A-B), system (e.g., system 200 described with reference to FIG. 2 ), and/or method (e.g., described with reference to FIG. 1 ) described herein may be practiced, in accordance with some embodiments of the present invention.
  • APs 306 e.g., as described with reference to APs 206A-B of FIG. 2
  • Mobile device 302 is moving in the driving direction represented by arrow 308.
  • a first group of directional antennas 310A e.g., as described with reference to antenna(s) 210) is arranged to face towards mobile device 302, opposite driving direction 308 (e.g., the number represented by N , for example, 1, 2, 3, 4, or other values).
  • a second group of directional antennas 310B e.g., as described with reference to antenna(s) 210) is arranged to face away from mobile device 302, along the driving direction 308 (e.g., the number represented by M , for example, 1, 2, 3, 4, or other values).
  • the acts of the method may be implemented by computing unit 212 implemented within network management server 250 and/or access point(s) 206A and/or 206B, based on code instructions stored in memory 216 executed by processing unit 214.
  • the acts of the method are described in relation to components of system 200 of FIG. 2 .
  • AP 206A and/or 206B determine signal reception data related to mobile device 202.
  • the mobile device is registered (i.e., being provided communication services by) to a different AP than the AP that is determining the signal reception data.
  • the AP that is determining the signal reception data may be the AP to which the mobile device will be handed over to.
  • the mobile device is currently registered with the AP that is determining the signal reception data. In such a case the AP that is determining the signal reception data may be the AP that will be handing over the mobile device.
  • the signal reception data is a RSSI identified by one of the APs and related to the mobile device.
  • the signal reception data is calculated for signals (e.g., packet, which may carry data and/or voice such as in a VoIP application) transmitted from the mobile device and received by the AP.
  • signals e.g., packet, which may carry data and/or voice such as in a VoIP application
  • the signal reception data may be calculated based on signals that are transmitted by the mobile device as part of a data application which is not designed to comply with the handover process, for example, a web navigator application, a VoIP application, an email application, a short message service application, a chat application, or another data transmitting application installed on the mobile device.
  • the signals e.g., packets
  • the mobile device does not necessarily require to conform to a defined protocol, and/or to execute special software.
  • the signal reception data may be calculated based on predefined signals transmitted by the mobile device, for example, predefined packets (e.g., of a predefined size and/or containing predefined data) transmitted at predefined time intervals and/or using a predefined power setting.
  • predefined signals may be transmitted according to a predefined handover protocol and/or according to code installed on mobile device.
  • the signal reception data may be centrally calculated by network management server 250 for multiple APs 206A-B, and/or at each respective AP 206A-B.
  • a direction indicator is calculated based on the signal reception data.
  • the direction indicator defines a measurement for identifying the time at which the mobile device moves past the AP (e.g., when the car containing the mobile device drives past a pole on which the AP is installed, when the mobile device is located the closest distance to the AP).
  • the direction indicator defines the time when the mobile device moves from facing one set of directional antennas (i.e., the antennas facing opposite the direction of motion of the mobile device, e.g., the direction of traffic) to the other set of directional antennas (i.e., the antennas facing the direction of motion of the mobile device).
  • the time at which the mobile device moves from facing towards the first set of antennas to facing away from the second set of antennas is termed herein the crossover time.
  • the direction indicated is calculated according to reading (e.g., signal reception data, and/or RSSI) of the first and the second groups of directional antennas of the AP. As discussed herein, the first group and the second group of directional antennas are facing in opposite directions.
  • the direction indicator is calculated for the AP which is currently providing wireless communication services to the mobile device (i.e., the AP which will be handing over the mobile device to the next AP).
  • the direction indicator is calculated for the AP which is expected to receive the handed over mobile device (i.e., the AP which will provide wireless services after the handover).
  • the direction indicator may be calculated, for example, at the AP by the processing unit executing code instructions stored in the memory, and/or by the network management server that receives the signal reception data from the AP.
  • the mobile device number is denoted by i .
  • the AP antenna number is denoted by j .
  • the packet number (packets transmitted by client i ) is denoted by k.
  • the group of M directional antennas of the AP directed to the traffic direction is denoted by .
  • the group of N directional antenna facing the opposite direction is denoted by .
  • the received power (in milliWatts (mW)) of packet k from client i at receive antenna j is denoted by P( i , j , k ).
  • an access point mapping dataset (e.g., dataset 218A) indicative of geographical distances between the APs is accessed by network management server 250 and/or APs 206A and/or 206B.
  • Dataset 218A stores distances measured, for example, in meters.
  • Dataset 218A may be implemented, for example, as a database, as a look-up table, as a set of records, as text values (e.g., stored as comma separated values), or other implementations.
  • Dataset 218A is accessed to obtain the geographical distance between the current AP providing service to the mobile device, and the next AP which will be providing service to the mobile device after the handover.
  • the next AP may be determined as the next AP along the road in the direction of motion of the mobile device.
  • a crossover time in which the mobile device crosses over one of the APs is calculated by analyzing the signal reception data, optionally based on the DI which is calculated as described with reference to 106.
  • the crossover time may be calculated centrally by network management server 250 for each mobile device being serviced by the wireless network, and/or by respective APs.
  • the crossover time is represented by the time at which DI changes sign (or is about zero).
  • the DI may be continuously calculated (e.g., based on received packets from the mobile device), calculated at predefined intervals (e.g., once every second, or every 0.1 second, or other times), and/or calculated based on events (e.g., when packets are received, and/or significant changes in RSSI, or other events).
  • the crossover time may be determined, for example, by accessing a real-time clock (e.g., a time server accessed using a network connection), accessing a locally stored time (e.g., stored in network management server 250 and/or at each AP 206A-B), and/or setting the crossover time as a reference time (e.g., zero) relative to which the handover time is calculated.
  • a real-time clock e.g., a time server accessed using a network connection
  • a locally stored time e.g., stored in network management server 250 and/or at each AP 206A-B
  • setting the crossover time e.g., zero
  • FIG. 4 is a schematic diagram including graphs representing values used in calculating the directional indication, in accordance with some embodiments of the present invention.
  • Cross over point 450 is identified according to a change in sign (e.g., from negative to positive) of the direction indicator (line 452 denotes the positive or negative sign state of the direction indicator.
  • the value of the direction indicator as a function of position of mobile device 402 is represented by line 454.
  • the value of the direction indicator is calculated from the value of DI L ( i ) represented by line 456 (shown as a function of positive of mobile device 402) and from the value of DI R ( i ) represented by line 458 (shown as a function of positive of mobile device 402).
  • network management server 250 (or each respective AP, or another computing unit) estimates the velocity of the mobile device.
  • data may be transmitted from one AP to the other (for use in calculation of the velocity, as described below), for example, via network 204, via network management server 250, via wireless signals between APs, or other methods.
  • the velocity is estimated as a function of the signal reception data.
  • the velocity is estimated, in particular based on the determined crossover time (as described with reference to block 108) and a geographical distance between two of the APs retrieved from the access point mapping dataset 218A (as described with reference to block 106).
  • the estimation of the velocity is used to estimate the time from the determined crossover time to the handover time, represented herein as T ⁇ , as described with reference to block 112.
  • FIG. 5 is a schematic depicting a mobile device 502 (shown within a car driving along a road 504 in a driving direction shown by arrow 508) in the process of being handed between a previous AP 506A and a current AP 506B, in accordance with some embodiments of the present invention.
  • Crossover time T 3 is estimated for current AP 508B (as described herein).
  • the value of X 3 which represents the distance from the current AP where the mobile device is to be handed off to the next AP, may be determined, for example, based on predefined value according to system requirements, from AP mapping dataset 218A, and/or based on other methods.
  • the velocity is estimated based on a difference between a past crossover time (represented as T 1 in FIG. 5 ) during which the mobile device (e.g., 502) cross passed one of the APs (represented as previous AP 506A in FIG. 5 ) and the current crossover time (represented as T 3 in FIG. 5 ) during which the mobile device (e.g., 502) crosses the current AP (e.g., 506B).
  • X denotes the distance between AP 508A and AP 508B, which may be calculated as X 1 + X 2 , and/or obtained from AP mapping dataset 218A.
  • the value of crossover time T 1 and crossover time T 3 are determined for respective APs, for example, as described herein with reference to block 108.
  • the velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • the velocity of the mobile device V is estimated based on a difference between a past handover time (represented as T 2 in FIG. 5 ) during which service given to the mobile device by one of the APs was exchanged by a similar service given to the mobile device by another of the APs, and the calculated crossover time (represented as T3 in FIG. 5 ).
  • X 2 may be calculated based on the difference between the previous handover location and the location of the current AP 506B, for example, based on AP mapping dataset 218A, and/or based on predefined system values.
  • the velocity is estimated based on a weighted function that takes into account a past velocity of the mobile device and/or an average velocity calculated for other mobile devices moving (e.g., along a road passing) between a first of the APs which currently gives service to the mobile device and a second of the APs which is designated to give service to the mobile device instead of the first AP after the handover.
  • the weighted average function and/or the average velocity calculated for other mobile devices may be used in cases where the velocity of the mobile device varies, for example, due to traffic (or other reasons).
  • the weighted average function and/or average velocity calculate for other mobile devices may improve the accuracy of estimating when the mobile device will reach the handover point, such as when the velocity before and after the crossover point are significantly different (i.e., that assuming a constant velocity will result in an error large enough that the determined handover point will result in a gap in wireless service).
  • the velocity is estimated is calculated based on the time taken for the mobile device to pass a known distance (e.g., retrieved from AP mapping dataset 218A) between a third AP and the first AP, where the third AP is located in the direction of motion of the mobile device (e.g., down the road) after the second AP.
  • a known distance e.g., retrieved from AP mapping dataset 218A
  • the average velocity of moving mobile devices that were previously handed off may be compared between the first and second APs, to the average velocity of the moving mobile devices between the second and third APs.
  • the last 50 mobile devices may be excluded, based on the assumption that the last 50 mobile devices did not yet reach the next AP, and therefore their velocity is still unknown (for example, due to a traffic jam).
  • the most recent mobile devices may be considered to try and obtain an accurate picture of the current traffic state, since traffic conditions may vary significantly over time.
  • a handover time (represented as T 4 with reference to FIG. 5 ) from one of the APs to another of the APs is determined.
  • the handover time is a future handover time during which a service given to the mobile device by one of the APs is exchanged by a similar service given to the mobile device by another of the APs.
  • Handing service over at the determined handover time maintains continuity of the wireless service to the moving mobile device, without data transfer gaps or disruptions.
  • the handover time is determined based on the determined crossover time (represented as T 3 with reference to FIG. 5 ), the velocity of the mobile device represented as V ⁇ (e.g., determined as described with reference to block 110), and a second geographical distance represented as X 3 (e.g., retrieved from the access point mapping dataset 218A).
  • the handover time is determined to occur during an overlap region in which service provided by the current AP (which is currently providing the service) and the next AP (which is expected to take over the service) overlap.
  • the mobile device may be estimated to remain within the overlap region for less than about one second, or less than about 2 seconds, or less than about 0.7 seconds, or other values.
  • the overlap region may be relatively small (e.g., due to the short range service capabilities based on the protocol defining the wireless service) and/or the mobile device may be moving quickly enough (e.g., on an highway, or train) relative to the overlap region such that ht mobile device spends a short period of time within the overlap region.
  • the current AP providing service to the mobile device is instructed to initiate a handover process to the next AP to provide wireless service to the mobile device.
  • the triggering of the handover process may be performed by the AP itself, and/or based on instructions received from the network management server.
  • blocks 102-114 are repeated sequentially based on each AP the mobile devices passes, for example, as the car in which the mobile device is located within drives along the road, sequentially passing AP. In this manner, each AP hands over the mobile device to the next AP, providing continuous wireless services to the mobile device.
  • composition or method may include additional ingredients and/or steps, but only if the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the claimed composition or method.
  • a compound or “at least one compound” may include a plurality of compounds, including mixtures thereof.
  • range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the invention. Accordingly, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed subranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 3, 4, 5, and 6. This applies regardless of the breadth of the range.

Abstract

There is provided a device for managing access point connections, wherein the device is configured to determine signal reception data (102) related to a mobile device registered to a at least one of a plurality of access points AP, access an access point mapping dataset (106) indicative of geographical distances between the plurality of APs, calculate a crossover time (108) in which the mobile device crosses over one of the APs by analyzing the signal reception data, estimate a velocity (110) of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of the APs from the access point mapping dataset, and determine a handover time (112) from one of the APs to another of the APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.

Description

    BACKGROUND
  • The present invention, in some embodiments thereof, relates to wireless networking and, more specifically, but not exclusively, to management of changing access points used by a mobile device accessing a wireless network.
  • Mobile devices communicate wirelessly with Access Points (AP) that provide connectivity to a network. Each AP is limited to providing communication services to mobile devices located in a certain geographical area. Mobile devices moving from one geographical location to another geographical location may need to switch from using one AP to another AP. The process of changing APs may also be termed BSS transition, or Handover.
  • SUMMARY
  • It is an object of the present invention to provide an apparatus, a system, a computer program product, and a method for managing access point connections.
  • The foregoing and other objects are achieved by the features of the independent claims. Further implementation forms are apparent from the dependent claims, the description and the figures.
  • According to a first aspect, a device for managing access point connections is configured to: determine signal reception data related to a mobile device registered to one or more access points (AP), access an access point mapping dataset indicative of geographical distances between the APs, calculate a crossover time in which the mobile device crosses over one of the APs by analyzing the signal reception data, estimate a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of the APs from the access point mapping dataset; and determine a handover time from one of the APs to another of the APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
  • The device, system and/or method described herein allow for the handover to occur when the mobile device is located within overlapping coverage area, which may be a relatively small range of time (e.g., 1-10 seconds) when the mobile device is moving quickly and/or when the coverage range provided by each AP is relatively small. The handover may occur when the client is not aware of wireless parameters values at the next AP (e.g., frequency, cell size, cell location, location of client within the cell, location and/or size of the overlapping area) and would otherwise be unable to perform the handoff during the limited time spent in the overlapping area, resulting in a gap in coverage.
  • The device, system, and/or method described herein improve data throughout, bandwidth, and/or utilization of the available wireless channel by allowing different APs to use different channels while providing fast moving mobile devices with handoffs without disconnection of wireless services, which improves channel utilization by reducing or preventing unused channels. The handover time is calculated at the AP side without necessarily providing special instructions to the mobile device, for example, the mobile device is not instructed to switch to a different frequency of the next AP, then switch back to the original frequency of the current AP and report the RSSI measured in the other channel for processing by the AP, for example, as defined by the 802.11k protocol.
  • The device, system, and/or method described herein perform the processing to determine the handover time at the AP side, without necessarily requiring the mobile device to support a special protocol or perform special functions (e.g., to collect data and/or transmit data) to assist the AP with determining the handover time, providing support to a wide range of different mobile device implementing different wireless communication protocols.
  • In a first possible implementation of the first device according to the first aspect, the signal reception data is a received Signal Strength Indicator (RSSI) identified by one of the APs and related to the mobile device.
  • In a second possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the signal reception data is a direction indicator calculated according to reading of first and second groups of directional antennas; wherein directional antennas of the first group and the directional antennas of the second group are facing opposite directions.
  • In a third possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the APs are geographically distributed along at least one road.
  • In a fourth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect" the device is further configured to receive a past handover time during which a service given to the mobile device by one of the APs was exchanged by a similar service given to the mobile device by another of the APs, wherein the velocity is estimated based on a difference between the past handover time and the crossover time.
  • The velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • In a fifth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the device is further configured to receive a past crossover time during which the mobile device passed by one of the APs, wherein the velocity is estimated based on a difference between the past crossover time and the crossover time.
  • The velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • In a sixth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the velocity is estimated based on a weighted function that takes into account a past velocity of the mobile device and an average velocity calculated for mobile devices moving in a road passing between a first of the APs which currently gives service to the mobile device and a second of the APs which designated to give service to the mobile device instead of the first AP.
  • The weighted average function and/or the average velocity calculated for other mobile devices may be used in cases where the velocity of the mobile device varies, for example, due to traffic (or other reasons). The weighted average function and/or average velocity calculate for other mobile devices may improve the accuracy of estimating when the mobile device will reach the handover point, such as when the velocity before and after the crossover point are significantly different (i.e., that assuming a constant velocity will result in an error large enough that the determined handover point will result in a gap in wireless service).
  • In a seventh possible implementation form of the first device according to the preceding implementation form of the first aspect, the velocity is estimated is calculated based on the time taken to the mobile device to pass a known distance between a third AP and the first AP.
  • In an eighth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the handover time is a future handover time during which a service given to the mobile device by one of the APs is exchanged by a similar service given to the mobile device by another of the APs.
  • Handing service over at the determined handover time maintains continuity of the wireless service to the moving mobile device, without data transfer gaps or disruptions.
  • In a ninth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the APs provide service for mobile clients by wireless signals having frequencies clustered around 2.4 gigahertz (GHz) and/or 5 GHz.
  • The device, system, and/or method described herein maintains continuity of communication service for mobile devices serviced by APs with relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlap areas.
  • In a tenth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the APs provide a Wi-Fi based service to the mobile device.
  • The device, system, and/or method described herein provide faster handoff as compared to other methods based on other wireless communication data transfer protocols (e.g., 802.11r), that maintains wireless connectivity for fast moving mobile devices, for example, located within cars travelling on highways (e.g., about 100 kilometers per hour, or about 80 km/h, or about 120 km/h, or other speeds).
  • In an eleventh possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the handover time is determined to occur during an overlap region in which service provided by the one of the APs and the another of the APs overlap, and wherein the mobile device is estimated to remain within the overlap region for less than about one second.
  • The device, system, and/or method described herein maintains continuity of communication service for mobile devices moving quickly relative to APs (e.g., located within a car on a highway, or a train).
  • In a twelfth possible implementation form of the first device according to the first aspect as such or according to any of the preceding implementation forms of the first aspect, the geographical distance between any two of the APs is less than 1000 meters.
  • The device, system, and/or method described herein maintains continuity of communication service for mobile devices serviced by APs with relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlap areas.
  • According to a second aspect, a method for managing access point connections comprises determining signal reception data related to a mobile device registered to one or more APs, accessing an access point mapping dataset indicative of geographical distances between the APs, calculating a crossover time in which the mobile device crosses over one of the APs by analyzing the signal reception data, estimating a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of the APs from the access point mapping dataset, and determining a handover time from one of the APs to another of the APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
  • Unless otherwise defined, all technical and/or scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the invention pertains. Although methods and materials similar or equivalent to those described herein can be used in the practice or testing of embodiments of the invention, exemplary methods and/or materials are described below. In case of conflict, the patent specification, including definitions, will control. In addition, the materials, methods, and examples are illustrative only and are not intended to be necessarily limiting.
  • BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
  • Some embodiments of the invention are herein described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of embodiments of the invention. In this regard, the description taken with the drawings makes apparent to those skilled in the art how embodiments of the invention may be practiced.
  • In the drawings:
    • FIG. 1 is a method for managing AP connections for a moving mobile device by determining a handover time from one of the APs to another of the APs, in accordance with some embodiments of the present invention;
    • FIG. 2 is a diagram of components of a system that allows a moving mobile device to maintain communication connectivity with a network by determining handover time(s) from one AP to another AP, in accordance with some embodiments of the present invention;
    • FIG. 3 is a schematic depicting an environment in which the device, system, and/or method described herein may be practiced, in accordance with some embodiments of the present invention;
    • FIG. 4 is a schematic diagram including graphs representing values used in calculating the directional indication, in accordance with some embodiments of the present invention; and
    • FIG. 5 is a schematic depicting a mobile device in the process of being handed between a previous AP and a current, in accordance with some embodiments of the present invention.
    DETAILED DESCRIPTION
  • The present invention, in some embodiments thereof, relates to wireless networking and, more specifically, but not exclusively, to management of changing access points used by a mobile device accessing a wireless network.
  • An aspect of some embodiments of the present invention relates to a device (e.g., processing unit), system and/or method (e.g., implemented by code instructions stored in a memory executed by a processor) that determines a handover time for a moving mobile device (e.g., a Smartphone in a car driving on a road) from one access point (AP) to another AP. The handover time is calculated based on a determined crossover time (when the mobile device crosses over one of the APs), an estimated velocity of the mobile device, and a geographical distance defined relative to one or more of the APs. The device, system, and/or method described herein maintains continuity of wireless communication service for mobile devices moving quickly relative to APs (e.g., when the mobile device is located within a car driving on a highway), for mobile devices communicating with APs having a relatively small coverage areas (e.g., less than 1 kilometer), and/or APs with relatively small overlapping service areas. Continuity of service may be maintained for applications that cannot tolerate gaps in service, for example, voice over internet protocol (VoIP) calls.
  • Optionally, the crossover time is determined based on an analysis of signal data (e.g., packets transmitted by the mobile device) received by the AP, optionally measured based on a received Signal Strength Indicator (RSSI). Optionally, a direction indicator is calculated based on the difference between signal readings from a first group of directional antennas and a second group of directional antennas. The first and second group of directional antennas are associated with the same AP, facing in opposite directions, one group facing towards the moving mobile device and another group facing away from the mobile device. When the direction indicator changes sign (e.g., from positive to negative, or from negative to positive), and/or when the value of the directional indicator is about zero, the direction indicator represents the time at which the mobile device is crossing over the AP.
  • The handover time may be selected to correspond to overlapping coverage areas between neighboring APs (i.e., the two APs involved in the handover) such that the handover occurs within the overlapping area. The device, system and/or method described herein allow for the handover to occur when the mobile device is located within overlapping coverage area, which may be a relatively small range of time (e.g., 0.3-1 second, or 1-2 seconds) when the mobile device is moving quickly and/or when the coverage range provided by each AP is relatively small. The handover may occur when the client is not aware of wireless parameters values at the next AP (e.g., frequency, cell size, cell location, location of client within the cell, location and/or size of the overlapping area) and would otherwise be unable to perform the handoff during the limited time spent in the overlapping area, resulting in a gap in coverage.
  • Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not necessarily limited in its application to the details of construction and the arrangement of the components and/or methods set forth in the following description and/or illustrated in the drawings and/or the Examples. The invention is capable of other embodiments or of being practiced or carried out in various ways.
  • The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
  • The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
  • Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
  • The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
  • Reference is now made to FIG. 1 which is a flowchart of a method for managing AP connections for a moving mobile device by determining a handover time from one of the APs to another of the APs, in accordance with some embodiments of the present invention. Reference is also made to FIG. 2, which is a diagram of components of a system 200 that allows a moving mobile device 202 to maintain communication connectivity with a network 204 by determining handover time(s) from one AP 206A to another AP 206B, in accordance with some embodiments of the present invention.
  • The device, system, and/or method described herein provide faster handoff as compared to other methods based on other wireless communication data transfer protocols (e.g., 802.11r), that maintains wireless connectivity for fast moving mobile devices, for example, located within cars travelling on highways (e.g., about 100 kilometers per hour, or about 80 km/h, or about 120 km/h, or other speeds).
  • The device, system, and/or method described herein improve data throughout, bandwidth, and/or utilization of the available wireless channel by allowing different APs to use different channels while providing fast moving mobile devices with handoffs without disconnection of wireless services, which improves channel utilization by reducing or preventing unused channels. The handover time is calculated at the AP side without necessarily providing special instructions to the mobile device, for example, the mobile device is not instructed to switch to a different frequency of the next AP, then switch back to the original frequency of the current AP and report the RSSI measured in the other channel for processing by the AP, for example, as defined by the 802.11k protocol.
  • The device, system, and/or method described herein perform the processing to determine the handover time at the AP side, without necessarily requiring the mobile device to support a special protocol or perform special functions (e.g., to collect data and/or transmit data) to assist the AP with determining the handover time, providing support to a wide range of different mobile device implementing different wireless communication protocols. For example, the mobile device does not necessarily make its own handoff decisions, and/or does not necessarily measure RSSI to determine which AP to connect to (e.g., the AP with the highest RSSI), which reduces or prevents scenarios in which the mobile device connects to a less optimal AP, for example, when a truck is located in front of the mobile device hiding the next AP but not the current AP, the client may remain connected to the current AP even when a better scenario is to switch to the next AP (since the mobile device is moving and the blockage will end shortly).
  • System 200 allows end users using mobile device(s) 202 to connect to network 204 while moving, for example, travelling in a car (or bus or truck) on a highway (or other road), in a boat travelling within a canal or close to shore, or on a train or subway.
  • Each mobile device(s) 202 includes or is in communication with one or more antennas 208 that provide wireless connectivity 222 with one or more antennas 210 of APs 206A-B. Each AP 206A-B includes or is in communication with a network interface 220 that provides connectivity to network 204, providing mobile device(s) 202 with access to network 204. Exemplary network(s) 204 include: the internet, a cellular network, a local area network, a city network, and a private network.
  • Optionally, wireless connectivity 222 is based on a wireless computing technology designed for transfer of data (e.g., packets), optionally based on a Wi-Fi standard.
  • APs 206A-B are geographically distributed, optionally based on expected movement direction(s) of mobile device(s) 202, for example, along one or more roads. The geographically distribution, such as the distance between APs 206A-B may be based on the range of wireless transmission (e.g., based on the selected wireless protocols providing communication services 222). The geographical distance between any two APs may be, for example, about 200-500 meters, or about 500-1000 meters, or less than about 1000 meters, or about 1000-1500 meters, or about 1500-2000 meters, or other value ranges.
  • Antennas 210 are directional antennas arranged into at least two groups (each group include one or more antennas). Each antennas group is arranged to face towards moving mobile device 202, or away from moving mobile device 202. For example, when mobile device 202 is moving along a road, rail road, or canal, and APs 206A-B are installed along the side of the road, and directional antennas 210 are arranged to face towards mobile device 202, or away from mobile device 202. Optionally, the groups of directional antennas 210 are arranged opposite to one another. There may be, for example, 3 or 4 antennas 210 in each group, or 3 or 4 antennas 210 in total split between the two groups. Exemplary antenna values include a gain of at least about 27decibels relative to isotropic (dBi) at 2.4 Gigahertz (Ghz). AP 206A may provide service to mobile devices by wireless signals having frequencies clustered around 2.4 Ghz and/or 5 Ghz (optionally at both frequencies). AP 206A-B may be installed to provide support to cases in which mobile device 202 has a line of sight with antenna(s) 210 (e.g., the user sitting in the front seat of the car using a Smartphone to surface the internet) and/or when mobile device 202 does not have a line of sight with antenna(s) 210 (e.g., the user sitting in the back seat holding the Smartphone on the seat).
  • APs 206A-B may be installed, for example, within existing wireless and/or cellular base stations, on poles, on traffic lights, on highway lighting poles, on bridges, on buildings, on fences at the side of roads, or other locations. APs 206A-B may be installed to provide a line of sight with cars and/or moving mobile device(s) 202, for example, close to the road, above the road, and/or between lanes. APs 206A-B may be installed at a height of about 4-8 meters above the expected locations of mobile devices 202 (e.g., above the surface of the road). Each AP 206A-B may cover one direction of road travel. Two APs 206A-B covering two cells may be installed on the same pole (or other location), with one cell of one AP covering lanes closer to the AP having one direction of travel and another cell of the other AP covering lanes further away of traffic in the opposite direction.
  • Exemplary mobile devices 202 include: smartphone, laptop, tablet computer, wearable computing device, glasses computing device, and watch computing device.
  • Each AP 206A-B may include a computing unit 212 that includes a processing unit 214 and memory 216 for storing instruction code executable by processing unit 214. Computing unit 212 may be implemented, for example, as software installed on a base station computer, as a hardware card plugged into existing base station equipment, and/or as a stand-along unit in communication with base station equipment (e.g., using cables and/or a wireless connection).
  • Alternatively or additionally, computing unit 212 is implemented within a wireless network management server 250 in communication with AP 206A-B and/or other communication channel(s). Server 250 provides centralized control of the wireless network, by receiving data from APts 206A-B (e.g., RSSI and/or other signal reception data, as described herein), analyzing the received data (e.g., calculating the directional indicator, crossover time, and/or handover time, as described herein), and transmitting instructions to APs 206A-B (e.g., when to handover the mobile device). Server 250 may implement self organizing network (SON) code. Alternatively or additionally, management server 250 is implemented within one or more AP 206A-B. The AP hosting management server 250 may be designated as the AP group leader. APs 206A-B (and other APs not shown) may form one or more management groups and elect one of the APs per management group to perform the functions of managements server 250.
  • Processing unit 214 may be implemented, for example, as a central processing unit(s) (CPU), a graphics processing unit(s) (GPU), field programmable gate array(s) (FPGA), digital signal processor(s) (DSP), and application specific integrated circuit(s) (ASIC). Processing unit(s) 214 may include one or more processors (homogenous or heterogeneous), which may be arranged for parallel processing, as clusters and/or as one or more multi core processing units.
  • Memory 216 stores code instructions executed by processing unit 214, for example, a random access memory (RAM), read-only memory (ROM), and/or a storage device, for example, non-volatile memory, magnetic media, semiconductor memory devices, hard drive, removable storage, and optical media (e.g., DVD, CD-ROM).
  • Computing unit 212 includes a storage unit 218 that acts as a data repository for storing data, for example, a memory, a hard-drive, an optical disc, a storage unit, an interface to a remote storage server, and interface to a cloud server, and/or other storage units. Storage unit 218 may store an AP mapping dataset 218A, as described herein. Alternatively or additionally, AP mapping dataset 218A is stored on network management server 250. Alternatively or additionally, AP mapping dataset 218A is stored on a server accessible to multiple APs 206A-B and/or network management server 250, for example, a network connected server accessible via network 204.
  • It is noted that for clarity of explanation, one mobile device 202 is depicted. It is understood that multiple mobile devices 202 may be simultaneously communicating with APs 206A-B. The multiple mobile devices 202 may be travelling in different directions (e.g., opposite to one another, for example, differ directions on highway lanes). Moreover, it is understood that two APs 206A-B are shown for clarity of explanation, however system 200 may include a large number of APs.
  • Reference is now made to FIG. 3, which is a schematic depicting an example environment in which the device (e.g., AP 206A-B), system (e.g., system 200 described with reference to FIG. 2), and/or method (e.g., described with reference to FIG. 1) described herein may be practiced, in accordance with some embodiments of the present invention. APs 306 (e.g., as described with reference to APs 206A-B of FIG. 2) are located adjacent to a road 304 to provide network services to mobile device 302 (e.g., as described with reference to mobile device 202 of FIG. 2) located within a vehicle (e.g., car shown for example purposes) driving along road 304. Mobile device 302 is moving in the driving direction represented by arrow 308. A first group of directional antennas 310A (e.g., as described with reference to antenna(s) 210) is arranged to face towards mobile device 302, opposite driving direction 308 (e.g., the number represented by N, for example, 1, 2, 3, 4, or other values). A second group of directional antennas 310B (e.g., as described with reference to antenna(s) 210) is arranged to face away from mobile device 302, along the driving direction 308 (e.g., the number represented by M, for example, 1, 2, 3, 4, or other values).
  • Referring now back to FIG. 1, the acts of the method may be implemented by computing unit 212 implemented within network management server 250 and/or access point(s) 206A and/or 206B, based on code instructions stored in memory 216 executed by processing unit 214. For clarity, the acts of the method are described in relation to components of system 200 of FIG. 2.
  • At 102, AP 206A and/or 206B (or other nearby APs not shown in FIG. 2) determine signal reception data related to mobile device 202.
  • Optionally, the mobile device is registered (i.e., being provided communication services by) to a different AP than the AP that is determining the signal reception data. In such a case, the AP that is determining the signal reception data may be the AP to which the mobile device will be handed over to. Alternatively or additionally, the mobile device is currently registered with the AP that is determining the signal reception data. In such a case the AP that is determining the signal reception data may be the AP that will be handing over the mobile device.
  • Optionally, the signal reception data is a RSSI identified by one of the APs and related to the mobile device.
  • The signal reception data, optionally RSSI, is calculated for signals (e.g., packet, which may carry data and/or voice such as in a VoIP application) transmitted from the mobile device and received by the AP.
  • The signal reception data may be calculated based on signals that are transmitted by the mobile device as part of a data application which is not designed to comply with the handover process, for example, a web navigator application, a VoIP application, an email application, a short message service application, a chat application, or another data transmitting application installed on the mobile device. The signals (e.g., packets) associated with the application(s) may be analyzed to calculate the signal reception data along the transmission pathway into the network. In such an implementation, the mobile device does not necessarily require to conform to a defined protocol, and/or to execute special software. Alternatively or additionally the signal reception data may be calculated based on predefined signals transmitted by the mobile device, for example, predefined packets (e.g., of a predefined size and/or containing predefined data) transmitted at predefined time intervals and/or using a predefined power setting. The predefined signals may be transmitted according to a predefined handover protocol and/or according to code installed on mobile device.
  • The signal reception data may be centrally calculated by network management server 250 for multiple APs 206A-B, and/or at each respective AP 206A-B.
  • At 104, a direction indicator is calculated based on the signal reception data. The direction indicator defines a measurement for identifying the time at which the mobile device moves past the AP (e.g., when the car containing the mobile device drives past a pole on which the AP is installed, when the mobile device is located the closest distance to the AP). The direction indicator defines the time when the mobile device moves from facing one set of directional antennas (i.e., the antennas facing opposite the direction of motion of the mobile device, e.g., the direction of traffic) to the other set of directional antennas (i.e., the antennas facing the direction of motion of the mobile device).
  • The time at which the mobile device moves from facing towards the first set of antennas to facing away from the second set of antennas (i.e., when the mobile device is located the closest distance to the AP) is termed herein the crossover time.
  • The direction indicated is calculated according to reading (e.g., signal reception data, and/or RSSI) of the first and the second groups of directional antennas of the AP. As discussed herein, the first group and the second group of directional antennas are facing in opposite directions.
  • Optionally, the direction indicator is calculated for the AP which is currently providing wireless communication services to the mobile device (i.e., the AP which will be handing over the mobile device to the next AP). Alternatively or additionally, the direction indicator is calculated for the AP which is expected to receive the handed over mobile device (i.e., the AP which will provide wireless services after the handover).
  • The direction indicator may be calculated, for example, at the AP by the processing unit executing code instructions stored in the memory, and/or by the network management server that receives the signal reception data from the AP.
  • An exemplary method is now described for calculating the direction indicator and the associated crossover time:
  • The mobile device number is denoted by i. The AP antenna number is denoted by j. The packet number (packets transmitted by client i) is denoted by k. The group of M directional antennas of the AP directed to the traffic direction is denoted by
    Figure imgb0001
    . The group of N directional antenna facing the opposite direction is denoted by
    Figure imgb0002
    . The received power (in milliWatts (mW)) of packet k from client i at receive antenna j is denoted by P(i, j, k).
  • The direction indicator (i) is denoted as: DI(i) = DIR (i) - DIL (i), where: DI R i = 10 log 1 M i R k P i j k ,
    Figure imgb0003
    and DI L i = 10 log 1 N i L k P i j k
    Figure imgb0004
  • At 106, an access point mapping dataset (e.g., dataset 218A) indicative of geographical distances between the APs is accessed by network management server 250 and/or APs 206A and/or 206B. Dataset 218A stores distances measured, for example, in meters. Dataset 218A may be implemented, for example, as a database, as a look-up table, as a set of records, as text values (e.g., stored as comma separated values), or other implementations.
  • Dataset 218A is accessed to obtain the geographical distance between the current AP providing service to the mobile device, and the next AP which will be providing service to the mobile device after the handover. The next AP may be determined as the next AP along the road in the direction of motion of the mobile device.
  • At 108, a crossover time in which the mobile device crosses over one of the APs is calculated by analyzing the signal reception data, optionally based on the DI which is calculated as described with reference to 106. The crossover time may be calculated centrally by network management server 250 for each mobile device being serviced by the wireless network, and/or by respective APs.
  • The crossover time is represented by the time at which DI changes sign (or is about zero). The DI may be continuously calculated (e.g., based on received packets from the mobile device), calculated at predefined intervals (e.g., once every second, or every 0.1 second, or other times), and/or calculated based on events (e.g., when packets are received, and/or significant changes in RSSI, or other events). When the DI changes sign, the crossover time may be determined, for example, by accessing a real-time clock (e.g., a time server accessed using a network connection), accessing a locally stored time (e.g., stored in network management server 250 and/or at each AP 206A-B), and/or setting the crossover time as a reference time (e.g., zero) relative to which the handover time is calculated.
  • Reference is now made to FIG. 4, which is a schematic diagram including graphs representing values used in calculating the directional indication, in accordance with some embodiments of the present invention. FIG. 4 depicts values associated with the directional indicator (calculated using the equations above) as a function of position of mobile device 402 (shown within a driving car along axis 460) relative to AP 406 that includes a first group of antennas 410A facing opposite the direction of motion of mobile device 402 (
    Figure imgb0005
    ={1,2}) and a second group of antennas 410B facing towards the direction of motion of mobile device 402 (
    Figure imgb0006
    ={3}), as described herein.
  • Cross over point 450 is identified according to a change in sign (e.g., from negative to positive) of the direction indicator (line 452 denotes the positive or negative sign state of the direction indicator. The value of the direction indicator as a function of position of mobile device 402 is represented by line 454. The value of the direction indicator is calculated from the value of DIL (i) represented by line 456 (shown as a function of positive of mobile device 402) and from the value of DIR (i) represented by line 458 (shown as a function of positive of mobile device 402).
  • Referring now back to FIG. 1, at 110, network management server 250 (or each respective AP, or another computing unit) estimates the velocity of the mobile device. In the case in which each respective AP estimates the velocity of the mobile device, data may be transmitted from one AP to the other (for use in calculation of the velocity, as described below), for example, via network 204, via network management server 250, via wireless signals between APs, or other methods.
  • The velocity is estimated as a function of the signal reception data. The velocity is estimated, in particular based on the determined crossover time (as described with reference to block 108) and a geographical distance between two of the APs retrieved from the access point mapping dataset 218A (as described with reference to block 106).
  • The estimation of the velocity is used to estimate the time from the determined crossover time to the handover time, represented herein as , as described with reference to block 112.
  • Reference is now made to FIG. 5, which is a schematic depicting a mobile device 502 (shown within a car driving along a road 504 in a driving direction shown by arrow 508) in the process of being handed between a previous AP 506A and a current AP 506B, in accordance with some embodiments of the present invention.
  • Crossover time T3 is estimated for current AP 508B (as described herein). The handover time from current AP 508B to the next AP (not shown) is estimated as T 4 = T 3 + . The value of is estimated from an estimate of the velocity of mobile device 502 (represented as V) according to the relationship: T ^ = X 3 V ^
    Figure imgb0007
  • The value of X 3, which represents the distance from the current AP where the mobile device is to be handed off to the next AP, may be determined, for example, based on predefined value according to system requirements, from AP mapping dataset 218A, and/or based on other methods.
  • Optionally, the velocity is estimated based on a difference between a past crossover time (represented as T1 in FIG. 5) during which the mobile device (e.g., 502) cross passed one of the APs (represented as previous AP 506A in FIG. 5) and the current crossover time (represented as T3 in FIG. 5) during which the mobile device (e.g., 502) crosses the current AP (e.g., 506B). The velocity of the mobile device may be estimated based on the relationship (with reference to FIG. 5): V ^ = X T 3 T 1
    Figure imgb0008
  • Where X denotes the distance between AP 508A and AP 508B, which may be calculated as X 1 + X 2, and/or obtained from AP mapping dataset 218A. The value of crossover time T1 and crossover time T3 are determined for respective APs, for example, as described herein with reference to block 108. The velocity is assumed to be approximately constant (i.e., the velocity does not vary significantly enough to affect the estimation of the handover time, for example, within a tolerance requirement).
  • Alternatively or additionally, the velocity of the mobile device V is estimated based on a difference between a past handover time (represented as T2 in FIG. 5) during which service given to the mobile device by one of the APs was exchanged by a similar service given to the mobile device by another of the APs, and the calculated crossover time (represented as T3 in FIG. 5). The velocity of the mobile device may be estimated based on the relationship (with reference to FIG. 5): V ^ = X 2 T 3 T 2
    Figure imgb0009
  • X 2 may be calculated based on the difference between the previous handover location and the location of the current AP 506B, for example, based on AP mapping dataset 218A, and/or based on predefined system values.
  • Alternatively or additionally, the velocity is estimated based on a weighted function that takes into account a past velocity of the mobile device and/or an average velocity calculated for other mobile devices moving (e.g., along a road passing) between a first of the APs which currently gives service to the mobile device and a second of the APs which is designated to give service to the mobile device instead of the first AP after the handover. The weighted average function and/or the average velocity calculated for other mobile devices may be used in cases where the velocity of the mobile device varies, for example, due to traffic (or other reasons). The weighted average function and/or average velocity calculate for other mobile devices may improve the accuracy of estimating when the mobile device will reach the handover point, such as when the velocity before and after the crossover point are significantly different (i.e., that assuming a constant velocity will result in an error large enough that the determined handover point will result in a gap in wireless service).
  • Optionally, the velocity is estimated is calculated based on the time taken for the mobile device to pass a known distance (e.g., retrieved from AP mapping dataset 218A) between a third AP and the first AP, where the third AP is located in the direction of motion of the mobile device (e.g., down the road) after the second AP.
  • The average velocity of moving mobile devices that were previously handed off may be compared between the first and second APs, to the average velocity of the moving mobile devices between the second and third APs.
  • An exemplary method of calculating the velocity for the moving mobile device by considering the past velocity of other moving mobile devices is now presented:
    • X denotes the distance between the previous AP (e.g., 506A of FIG. 5) and the current AP (e.g. 506B of FIG. 5).
    • X' denotes the distance between the current AP and the next AP.
    • T(i) denotes the time it took previous mobile device i to travel between previous AP to current AP.
    • T'(i) denotes the time it took previous mobile device i to travel between current AP to next AP.
    • (j) denotes estimated velocity of the current mobile device between the current crossover geographical location and the handover geographical location.
    (j) may be calculated using the relationship: V ^ j = f X , X , T 1 , , T j , T 1 , , T j K
    Figure imgb0010
    f denotes some function and K denotes some positive integer.
  • An exemplary function f used to calculate (j): V ^ j = α X T j + 1 α 1 100 l = j 150 j 51 X T l , for 0 < α < 1.
    Figure imgb0011
  • The above relationship to estimates the velocity of the mobile device in the geographical distance between the current AP and the next AP as a weighted average between the speed of the mobile device in the geographical distance between the previous AP and the current AP, and the velocity of the other mobile devices that moved in the geographical distance between the current AP and the next AP.
  • For the other mobile devices in the geographical distance between the current AP and the next AP, the last 50 mobile devices (or other number of mobile devices) may be excluded, based on the assumption that the last 50 mobile devices did not yet reach the next AP, and therefore their velocity is still unknown (for example, due to a traffic jam). For the other mobile devices, the most recent mobile devices may be considered to try and obtain an accurate picture of the current traffic state, since traffic conditions may vary significantly over time.
  • At 112, a handover time (represented as T4 with reference to FIG. 5) from one of the APs to another of the APs is determined. The handover time is a future handover time during which a service given to the mobile device by one of the APs is exchanged by a similar service given to the mobile device by another of the APs. Handing service over at the determined handover time maintains continuity of the wireless service to the moving mobile device, without data transfer gaps or disruptions.
  • The handover time is determined based on the determined crossover time (represented as T3 with reference to FIG. 5), the velocity of the mobile device represented as (e.g., determined as described with reference to block 110), and a second geographical distance represented as X3 (e.g., retrieved from the access point mapping dataset 218A).
  • The handover time T4 is estimated from the relationship T 4 = T 3 + , where the value of is estimated according to the relationship: T ^ = X 3 V ^
    Figure imgb0012
  • Optionally, the handover time is determined to occur during an overlap region in which service provided by the current AP (which is currently providing the service) and the next AP (which is expected to take over the service) overlap. The mobile device may be estimated to remain within the overlap region for less than about one second, or less than about 2 seconds, or less than about 0.7 seconds, or other values. The overlap region may be relatively small (e.g., due to the short range service capabilities based on the protocol defining the wireless service) and/or the mobile device may be moving quickly enough (e.g., on an highway, or train) relative to the overlap region such that ht mobile device spends a short period of time within the overlap region.
  • At 114, when the determined handover time arrives (e.g., by comparison to a real-time clock, or a stop-watch), the current AP providing service to the mobile device is instructed to initiate a handover process to the next AP to provide wireless service to the mobile device. The triggering of the handover process may be performed by the AP itself, and/or based on instructions received from the network management server.
  • At 116, blocks 102-114 are repeated sequentially based on each AP the mobile devices passes, for example, as the car in which the mobile device is located within drives along the road, sequentially passing AP. In this manner, each AP hands over the mobile device to the next AP, providing continuous wireless services to the mobile device.
  • The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
  • It is expected that during the life of a patent maturing from this application many relevant access points, mobile devices, and wireless communication services will be developed and the scope of the terms access point, mobile device, and wireless service is intended to include all such new technologies a priori.
  • As used herein the term "about" refers to ± 10 %.
  • The terms "comprises", "comprising", "includes", "including", "having" and their conjugates mean "including but not limited to". This term encompasses the terms "consisting of" and "consisting essentially of".
  • The phrase "consisting essentially of" means that the composition or method may include additional ingredients and/or steps, but only if the additional ingredients and/or steps do not materially alter the basic and novel characteristics of the claimed composition or method.
  • As used herein, the singular form "a", "an" and "the" include plural references unless the context clearly dictates otherwise. For example, the term "a compound" or "at least one compound" may include a plurality of compounds, including mixtures thereof.
  • The word "exemplary" is used herein to mean "serving as an example, instance or illustration". Any embodiment described as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments and/or to exclude the incorporation of features from other embodiments.
  • The word "optionally" is used herein to mean "is provided in some embodiments and not provided in other embodiments". Any particular embodiment of the invention may include a plurality of "optional" features unless such features conflict.
  • Throughout this application, various embodiments of this invention may be presented in a range format. It should be understood that the description in range format is merely for convenience and brevity and should not be construed as an inflexible limitation on the scope of the invention. Accordingly, the description of a range should be considered to have specifically disclosed all the possible subranges as well as individual numerical values within that range. For example, description of a range such as from 1 to 6 should be considered to have specifically disclosed subranges such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6 etc., as well as individual numbers within that range, for example, 1, 2, 3, 4, 5, and 6. This applies regardless of the breadth of the range.
  • Whenever a numerical range is indicated herein, it is meant to include any cited numeral (fractional or integral) within the indicated range. The phrases "ranging/ranges between" a first indicate number and a second indicate number and "ranging/ranges from" a first indicate number "to" a second indicate number are used herein interchangeably and are meant to include the first and second indicated numbers and all the fractional and integral numerals therebetween.
  • It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination or as suitable in any other described embodiment of the invention. Certain features described in the context of various embodiments are not to be considered essential features of those embodiments, unless the embodiment is inoperative without those elements.
  • All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference. In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention. To the extent that section headings are used, they should not be construed as necessarily limiting.

Claims (14)

  1. A device for managing access point connections, wherein the device is configured to:
    determine signal reception data related to a mobile device registered to at least one of a plurality of access points (AP);
    access an access point mapping dataset indicative of geographical distances between said plurality of APs;
    calculate a crossover time in which the mobile device crosses over one of said plurality of APs by analyzing the signal reception data;
    estimate a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of said plurality of APs from the access point mapping dataset; and
    determine a handover time from one of the plurality of APs to another of the plurality of APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
  2. The device of claim 1, wherein said signal reception data is a received Signal Strength Indicator (RSSI) identified by one of said plurality of APs and related to said mobile device.
  3. The device of any of the previous claims, wherein said signal reception data is a direction indicator calculated according to reading of first and second groups of directional antennas; wherein directional antennas of said first group and the directional antennas of said second group are facing opposite directions.
  4. The device of any of the previous claims, wherein said plurality of APs are geographically distributed along at least one road.
  5. The device of any of the previous claims, further configured to receive a past handover time during which a service given to said mobile device by one of said plurality of APs was exchanged by a similar service given to said mobile device by another of said plurality of APs;
    wherein said velocity is estimated based on a difference between said past handover time and said crossover time.
  6. The device of any of the previous claims, further configured to receive a past crossover time during which said mobile device passed by one of said plurality of APs;
    wherein said velocity is estimated based on a difference between said past crossover time and said crossover time.
  7. The device of any of the previous claims, wherein said velocity is estimated based on a weighted function that takes into account a past velocity of said mobile device and an average velocity calculated for a plurality of mobile devices moving in a road passing between a first of said plurality of APs which currently gives service to said mobile device and a second of said plurality of APs which designated to give service to said mobile device instead of said first AP.
  8. The device of claim 7, wherein said velocity is estimated based on the time taken to said mobile device to pass a known distance between a third AP and said first AP.
  9. The device of any of the previous claims, wherein said handover time is a future handover time during which a service given to said mobile device by one of said plurality of APs is exchanged by a similar service given to said mobile device by another of said plurality of APs.
  10. The device of any of the previous claims, wherein said plurality of APs provide service for mobile clients by wireless signals having frequencies clustered around 2.4 gigahertz (GHz) and/or 5 GHz.
  11. The device of any of the previous claims, wherein the plurality of APs provide a Wi-Fi based service to the mobile device.
  12. The device of any of the previous claims, wherein the handover time is determined to occur during an overlap region in which service provided by the one of the plurality of APs and the another of the plurality of APs overlap, and wherein the mobile device is estimated to remain within the overlap region for less than about one second.
  13. The device of any one of the previous claims, wherein the geographical distance between any two of the plurality of APs is less than 1000 meters.
  14. A method for managing access point connections, comprising:
    determining signal reception data related to a mobile device registered to at least one of a plurality of access points (AP);
    accessing an access point mapping dataset indicative of geographical distances between said plurality of APs;
    calculating a crossover time in which the mobile device crosses over one of said plurality of APs by analyzing the signal reception data;
    estimating a velocity of the mobile device as a function of the signal reception data, in particular based on the crossover time and a first geographical distance between two of said plurality of APs from the access point mapping dataset; and
    determining a handover time from one of the plurality of APs to another of the plurality of APs based on the crossover time the velocity of the mobile device and a second geographical distance from the access point mapping dataset.
EP16156298.8A 2016-02-18 2016-02-18 Triggering a wireless access point handover Active EP3209062B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP16156298.8A EP3209062B1 (en) 2016-02-18 2016-02-18 Triggering a wireless access point handover

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP16156298.8A EP3209062B1 (en) 2016-02-18 2016-02-18 Triggering a wireless access point handover

Publications (2)

Publication Number Publication Date
EP3209062A1 true EP3209062A1 (en) 2017-08-23
EP3209062B1 EP3209062B1 (en) 2018-09-19

Family

ID=55409736

Family Applications (1)

Application Number Title Priority Date Filing Date
EP16156298.8A Active EP3209062B1 (en) 2016-02-18 2016-02-18 Triggering a wireless access point handover

Country Status (1)

Country Link
EP (1) EP3209062B1 (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010090558A1 (en) * 2009-02-04 2010-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for tracking mobile terminals
EP2804414A1 (en) * 2012-01-11 2014-11-19 Huawei Technologies Co., Ltd. Mobile terminal moving speed obtaining method, base station and terminal

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010090558A1 (en) * 2009-02-04 2010-08-12 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement for tracking mobile terminals
EP2804414A1 (en) * 2012-01-11 2014-11-19 Huawei Technologies Co., Ltd. Mobile terminal moving speed obtaining method, base station and terminal

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
IVAN ALDAYA ET AL: "Real-time traffic, handoff, and outage modeling in high RF pico cells", 2011 IEEE WIRELESS COMMUNICATIONS AND NETWORKING CONFERENCE (WCNC 2011) : CANCUN, MEXICO, 28 - 31 MARCH 2011, IEEE, PISCATAWAY, NJ, 28 March 2011 (2011-03-28), pages 410 - 415, XP031876288, ISBN: 978-1-61284-255-4, DOI: 10.1109/WCNC.2011.5779168 *
MOHAMMED A BEN-MUBARAK ET AL: "Movement direction-based handover scanning for mobile WiMAX", COMMUNICATIONS (APCC), 2011 17TH ASIA-PACIFIC CONFERENCE ON, IEEE, 2 October 2011 (2011-10-02), pages 737 - 742, XP032116054, ISBN: 978-1-4577-0389-8, DOI: 10.1109/APCC.2011.6152904 *

Also Published As

Publication number Publication date
EP3209062B1 (en) 2018-09-19

Similar Documents

Publication Publication Date Title
US9103690B2 (en) Automatic travel time and routing determinations in a wireless network
EP2932774B1 (en) Systems and methods for user equipment mobility prediction
EP2840836B1 (en) Method and system for mobile handover management in wireless communication network
CN106797536B (en) Mobility in dense networks
Ghosh et al. Enabling seamless V2I communications: toward developing cooperative automotive applications in VANET systems
EP1598985A1 (en) Intelligent wireless network switching
US10038978B2 (en) Techniques for mobile network geolocation
US8849309B2 (en) Method and system for forecasting travel times on roads
Sun et al. An RSU-assisted localization method in non-GPS highway traffic with dead reckoning and V2R communications
Sierpiński et al. Use of GSM Technology as the Support to Manage the Modal Distribution in the Cities
Yan et al. A grid-based on-road localization system in VANET with linear error propagation
Abou-Zeid et al. Evaluating mobile signal and location predictability along public transportation routes
EP2287820A1 (en) An apparatus and method operative for providing traffic information on a traffic area
Yang et al. Generating routes for autonomous driving in vehicle-to-infrastructure communications
EP2615857A1 (en) Method for determining a future location of a mobile electronic device
Raza et al. Mobile crowdsensing based architecture for intelligent traffic prediction and quickest path selection
EP3010255A1 (en) Method, system, user terminal and computer programs for estimating user terminal mobile paths through cellular network and map information
EP3073460A1 (en) Predicting the trajectory of mobile users
EP3209062A1 (en) Systems and methods for triggering wireless access point handovers
Pögel et al. Analysis of operational 3g network characteristics for adaptive vehicular connectivity maps
Mangel et al. An analysis of data traffic in cellular networks caused by inter-vehicle communication at intersections
KR20100091085A (en) A method of collecting traffic information by the segment unit of roads and the vehicle terminal thereof
US20190213875A1 (en) Distributed traffic guidance and surveillance system
Shakeel et al. Experimental evaluation of safety beacons dissemination in VANETs
EP3073776A1 (en) Method and apparatus for predicting wireless link states

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20180212

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/12 20090101ALN20180307BHEP

Ipc: H04W 36/32 20090101AFI20180307BHEP

Ipc: G01S 5/02 20100101ALN20180307BHEP

Ipc: H04W 64/00 20090101ALN20180307BHEP

Ipc: H04W 36/00 20090101ALN20180307BHEP

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/12 20090101ALN20180314BHEP

Ipc: H04W 36/00 20090101ALN20180314BHEP

Ipc: H04W 64/00 20090101ALN20180314BHEP

Ipc: H04W 36/32 20090101AFI20180314BHEP

Ipc: G01S 5/02 20100101ALN20180314BHEP

INTG Intention to grant announced

Effective date: 20180328

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1044783

Country of ref document: AT

Kind code of ref document: T

Effective date: 20181015

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602016005619

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181219

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181220

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20181219

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1044783

Country of ref document: AT

Kind code of ref document: T

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190119

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190119

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602016005619

Country of ref document: DE

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

26N No opposition filed

Effective date: 20190620

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190218

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190228

REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190218

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190218

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20200218

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20200218

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20160218

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20180919

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20221230

Year of fee payment: 8