Search

EP-3665537-B1 - GENERATING GEO-FENCE DATA

EP3665537B1EP 3665537 B1EP3665537 B1EP 3665537B1EP-3665537-B1

Inventors

  • HAN, Jing
  • WU, Lianhai
  • WANG, HAIMING
  • ZHANG, Zhuoyun

Dates

Publication Date
20260513
Application Date
20170811

Claims (8)

  1. A method (700) performed by an aerial device (115), the method comprising: accessing (705), by use of a processor, a base station from the aerial device (115); receiving (735) geo-fence data, the geo-fence data comprising geo-fence boundaries and a cell list of base stations the aerial device is permitted to communicate with, wherein all base stations of the cell list are within the geo-fence boundaries; receiving (710) measurement data from the base station, the measurement data indicating base stations that are both in the cell list and are one of the base station and a neighbor base station to the base station; measuring (715) the base stations indicated in the measurement data; communicating (720) a measurement report based only on measurements to the base stations indicated in the measurement data; and communicating flight path data to the base station in response to receiving a flight path data request that comprises a location information granularity requirement for the flight path data.
  2. The method (700) of claim 1, wherein the aerial device only communicates with the base stations of the cell list.
  3. The method (700) of claim 1, wherein the flight path data is communicated to the base station in response to receiving a flight path data request that comprises at least one of a report periodicity configuration and an associated planned time for location information.
  4. The method (700) of claim 1, wherein the flight path data is communicated to the base station in response to receiving an aerial device certification from the base station.
  5. The method (700) of claim 1, wherein the aerial device indicates that the flight path data is available in a Radio Resource Control setup procedure.
  6. The method (700) of claim 1, the flight path data comprises at least one of location points, a planned velocity, location point times, and a flight path plan.
  7. The method (700) of claim 1, the method further comprising communicating updated flight path data in response to a change in a flight path.
  8. An apparatus (400) comprising: a processor (405) arranged to: access a base station from an aerial device; receive geo-fence data, the geo-fence data comprising geo-fence boundaries and a cell list of base stations the aerial device is permitted to communicate with, wherein all base stations of the cell list are within the geo-fence boundaries; receive measurement data from the base station, the measurement data indicating base stations that are both in the cell list and are one of the base station and a neighbor base station to the base station; measure the base stations indicated in the measurement data; communicate a measurement report based only on measurements to the base stations indicated in the measurement data; and communicate flight path data to the base station in response to receiving a flight path data request that comprises a location information granularity requirement for the flight path data.

Description

FIELD The subject matter disclosed herein relates to geo-fence data for an aerial device. BACKGROUND DESCRIPTION OF THE RELATED ART An aerial device such as an aerial drone may communicate with through a mobile telephone network. US 2013/310053 A1 describes creating geofence assistance information that includes forming a geographic area enclosing a geofence boundary. WO 2009/152472 A1 describes a system whereby the position of a target being tracked is compared with a predefined geofence boundary. WO 2017/042403 A1 discloses a method, system and devices for establishing secure control mechanisms for the aerial navigation of unmanned vehicles. BRIEF SUMMARY The invention is defined by the appended claims. Claim 1 defines a method in an aerial device and claim 8 defines an apparatus. In the following, any method and/or apparatus referred to as embodiments but nevertheless do not fall within the scope of the appended claims are to be understood as examples helpful in understanding the invention. A method for geo-fence data is disclosed. A processor registers an aerial device at an aerial server. In addition, the processor calculates the geo-fence data for the aerial device. The geo-fence data includes geo-fence boundaries and a cell list of base stations permitted to communicate with the aerial device. Each base station of the cell list is within the geo-fence boundaries. The processor further communicates the geo-fence data to a base station. BRIEF DESCRIPTION OF THE DRAWINGS A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which: Figure 1 is a schematic block diagram illustrating one embodiment of an aerial device communication system;Figure 2A is a schematic block diagram illustrating one embodiment of flight path data;Figure 2B is a schematic block diagram illustrating one embodiment of a measurement report;Figure 2C is a schematic block diagram illustrating one embodiment of geo-fence data;Figure 2D is a schematic block diagram illustrating one embodiment of measurement data;Figure 2E is a schematic block diagram illustrating one embodiment of a handover request;Figure 2F is a schematic block diagram illustrating one embodiment of an aerial device certification confirmation;Figure 2G is a schematic block diagram illustrating one embodiment of system data;Figure 2H is a schematic block diagram illustrating one embodiment of a flight path data request;Figure 3A is a schematic block diagram illustrating one embodiment of a geo-fence process;Figure 3B is a schematic diagram illustrating one embodiment of mobile telephone cells;Figure 3C is a schematic diagram illustrating one embodiment of mobile telephone cells and an aerial device flight path;Figure 3D is a schematic block diagram illustrating one embodiment of a cell list;Figure 3E is a schematic block diagram illustrating one alternate embodiment of a cell list;Figure 3F is a schematic diagram illustrating one alternate embodiment of mobile telephone cells and an aerial device flight path;Figure 3G is a schematic block diagram illustrating one embodiment of a cell list;Figure 3H is a schematic block diagram illustrating one alternate embodiment of a cell list;Figure 4 is a schematic block diagram illustrating one embodiment of a computer;Figure 5A is a schematic flow chart diagram illustrating one embodiment of a geo-fence generation method;Figure 5B is a schematic flow chart diagram illustrating one alternate embodiment of a geo-fence generation method;Figure 5C is a schematic flow chart diagram illustrating one embodiment of a geo-fence data utilization method;Figure 5D is a schematic flow chart diagram illustrating one embodiment of an aerial device certification method;Figure 5E is a schematic flow chart diagram illustrating one embodiment of an aerial device handover method; andFigure 5F is a schematic flow chart diagram illustrating one embodiment of a geo-fence generation method. DETAILED DESCRIPTION As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, method or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a "circuit," "module" or "system." Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage