SEAMLESS REPLACEMENT OF A FIRST DRONE BASE STATION WITH A SECOND DRONE BASE STATION

Abstract

A method is provided of replacing a first drone base station with a second drone base station, the first drone base station, the method comprising: sending by the first drone base station first pilot signals indicating a cell identifier; receiving by the first drone base station information that the second drone base station is in the vicinity of the first drone base station; sending by the second drone base station second pilot signals which indicate the same cell identifier as the first drone base station; receiving by the first drone base station from the second drone base station an indication to cease to send first pilot signals;and dependent upon receiving by the first drone base station from the second drone base station the indication to cease to send first pilot signals, ceasing by the first drone base station the sending of first pilot signals.

Claims

1. A method of replacing a first drone base station with a second drone base station, the method comprising: sending by the first drone base station first pilot signals indicating a cell identifier; receiving by the first drone base station information that the second drone base station is in the vicinity of the first drone base station; sending by the second drone base station second pilot signals which indicate the same cell identifier as the first drone base station; receiving by the first drone base station from the second drone base station an indication to cease to send first pilot signals; and dependent upon receiving by the first drone base station from the second drone base station the indication to cease to send first pilot signals, ceasing by the first drone base station the sending of first pilot signals.

2. A method according to claim 1, further comprising: upon said receiving by the first drone base station information that the second drone base station is in the vicinity, transferring user context information of connections of the first drone base station with user terminals from the first drone base station to the second drone base station; switching uplink user data connections with the plurality of user terminals from the first drone base station to both the first drone base station and the second drone base station, and then switching the uplink user data connections with the plurality of user terminals to the second drone base station but not the first drone base station.

3. A method according to claim 2, in which the switching the uplink user data connections with the plurality of user terminals to the second drone base station but not the first drone base station comprises the second drone base station sending an instruction to the first drone base station to stop uplink reception and the first drone base station sending an acknowledgement.

4. A method according to claim 3, in which the acknowledgement is sent together with user context data of uplink user data that has been received and forwarded by the first drone base station towards a backhaul node.

5. A method according to claim 1, further comprising switching the path for downlink user data from via the first drone base station to via the second drone base station by making use of IP addresses to differentiate between the first and second drone base stations.

6. A method according to claim 5, in which said switching the path for downlink user data is triggered by the second drone base station sending a request for switching the path for downlink user data.

7. A method according to claim 1, in which the second drone base station uses the same radio frequency band as the first base station.

8. A first drone base station configured to be replaced by a second drone base station, the first drone base station comprising: sending logic configured to send first pilot signals indicating a cell identifier; receiving logic configured to receive information that the second drone base station is in the vicinity of the first drone base station, the second base station being configured to send second pilot signals which indicate the same cell identifier as the first drone base station; indication receiving logic configured to receive from the second drone base station an indication to cease to send first pilot signals; and ceasing logic configured to cease the sending of first pilot signals dependent upon receiving from the second drone base station the indication to cease to send first pilot signals.

9. A first drone base station according to claim 8, further comprising: user context information sending logic configured to, upon being informed that the second drone base station is in the vicinity, send user context information of connections with user terminals towards the second drone base station; reception logic configured to receive an instruction to stop uplink reception; and stopping logic configured to, in response, stop uplink user data connections with the plurality of user terminals to the first drone base station and acknowledgement logic configured to send an acknowledgment of the instruction towards the second base station.

10. A first drone base station according to claim 9, comprising user context data sending logic configured to send, together with the acknowledgement, user context data of uplink user data that has been received and forwarded by the first drone base station to a backhaul node.

11. A second drone base station configured to replace a first drone base station that is configured to send first pilot signals indicating a cell identifier, the second drone base station comprising: receiving logic configured to receive a command to fly to a given location in the vicinity of the first drone base station, transmitting logic configured to transmit a signal indicating that the location has been flown to, sending logic configured to send from the second drone base station second pilot signals which indicate the same cell identifier as the first drone base station; indication sending logic configured to send towards the first drone base station an indication to cease to send first pilot signals.

12. A second drone base station according to claim 11, further comprising: reception logic configured to receive user context information from the first drone base station of the connections with the plurality of user terminals, undertaking logic configured to undertake uplink reception, instruction sending logic configured to send towards the first drone base station an instruction to stop uplink reception so as to have the uplink user data connections with the plurality of user terminals with the second drone base station but not with the first drone base station, acknowledgement receiving logic configured to receive from the first base station an acknowledgement of the instruction.

13. A second drone base station according to claim 1, further comprising: logic configured to send an instruction towards a backhaul node to switch the path for downlink user data from via the first drone base station to via the second drone base station by making use of IP addresses to differentiate between the first and second base stations.

14. A controller for controlling drone base station replacement, the controller comprising: receiving logic configured to receive a message indicating that a first drone base station which sends first pilot signals indicating a cell identifier should be replaced; sending logic configured to send a command towards a second drone base station to fly to a given location in the vicinity of the first drone base station, indication receiving logic configured to receive an indication from the second drone base station that the second drone base station has arrived at the given location, indication sending logic configured to send an indication towards the first base station that the second drone base station is now in the vicinity of the first drone base station, the indication being a trigger for the second drone base station, upon sending second pilot signals which indicate the same cell identifier as the first drone base station, to send to the first drone base station an indication to cease to send first pilot signals, and commanding logic configured to command the first drone base station to fly away.

15. A controller according to claim 14, comprising reception logic configured to receive a request from the second drone base station for downlink user data to be sent to the second drone base station instead of the first drone base station by making use of IP addresses to differentiate between the first and second base stations, and switching logic configured to in response to receiving the request switch to sending the downlink user data via the second drone base station.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0053] An embodiment of the present invention will now be described by way of example and with reference to the drawings, in which:

[0054] FIG. 1 is a diagram illustrating a known handover procedure (PRIOR ART)

[0055] FIG. 2 is a diagram illustrating a known drone base station handover procedure (PRIOR ART),

[0056] FIG. 3 is a diagram illustrating a network according to a first embodiment of the present invention at a first time where drone BS-A serves certain users,

[0057] FIG. 4 is a diagram illustrating the network shown in FIG. 3 but at a later time when a drone BS-B flies to the target location in preparation to be handed over to,

[0058] FIG. 5 is a diagram illustrating the network shown in FIG. 4 but at a later time at which the drone BS-B has been handed over to, so has taken over providing the wireless service,

[0059] FIG. 6 is a message sequence diagram illustrating the drone handover procedure in the network shown in FIGS. 3 to 5,

[0060] FIG. 7 is a diagram illustration how the two drone base stations are differentiated by the backhaul node for downlink user data transmissions using Internet Protocol identifying numbers,

[0061] FIG. 8 is a diagram illustrating the X2 interface routing in the network shown in FIGS. 3 to 5,

[0062] FIG. 9 is a diagram illustrating alternative X2 interface routing in an alternative network (not shown),

[0063] FIG. 10 is a diagram illustrating use of a single RF frequency band in the network shown in FIGS. 3 to 5,

[0064] FIG. 11 is a diagram illustrating the drone base stations in the network shown in FIGS. 3 to 5, and

[0065] FIG. 12 is a diagram illustrating alternative drone base stations in an alternative network (not shown).

DETAILED DESCRIPTION

[0066] A known technique for handover between cellular base stations is shown in FIG. 1. The technique involves radio handover of the connection between the base stations, transfer of user terminal (UE) context data over the X2 backhaul interface between the base stations, and updating the S1AP path routing for a User terminal's Internet Protocol (IP) data and user data via the core network. There are three known options for handover, namely Break before Make, Make before Break and dual connectivity. In all these procedures, the Cell Identity (Cell ID) that identifies the base station that is connected to must be changed. Also the Radio Network Temporary Identifier (RNTI) of a user terminal is changed due to handover, as RNTIs identify information for a particular user in a particular cell where common or shared channels are used for data transmission.

[0067] Considering replacement of drone base stations, in a manner that appears seamless in terms of service provided to user terminals, a known technique is illustrated in FIG. 2. It consists of the following steps. The serving drone base station (Drone-BS-A) having cell Id1 informs the drone management module connected via a backhaul node of the need for replacement. In consequence the drone management module directs Drone-BS-B to the location of Drone-BS-A. Configuration data is transferred from Drone-BS-A to Drone-BS-B. Then Drone-BS-B activates its cell coverage (Cell Id2). Drone-BS-A then reduces its pilot power so as to trigger handovers. Currently connected user terminals are then handed over from Drone-BS-A to Drone-BS-B. This involves user terminals providing measurements of pilot signals of neighbouring cells in known fashion, triggering a handover request message by Drone-BS-A for the particular user terminal. It is identified that Cell ID2 (namely Drone-BS-B) which operated at a different frequency band is to be the target cell for handover, and handover is effected to the cell having Cell ID2. Once these handovers are complete, Drone-BS-A ceases providing wireless service and is directed to fly away.

[0068] The inventors realised that this known approach was complex and slow, and an approach giving improved performance could be provided as described below.

[0069] An example network will first be described from a structural perspective then example operation in terms of drone replacement will be explained.

Network

[0070] As shown in FIGS. 3 to 5, a network 32 for cellular wireless telecommunications includes a terrestrial base station 34, a backhaul node 36, drone management stage 38 and a cellular communications core network 40. The backhaul node is connected wirelessly to two drone base stations 42, denoted Drone-BS-A and Drone-BS-B.

[0071] The backhaul node 36 and terrestrial base station 34 are connected to the drone management stage 38 and the core network 40. Some user terminals are connected to the terrestrial base station 34. In the FIGS. 3 to 5, two of these user terminals are shown for simplicity, denoted UE3 and UE4.

[0072] The terrestrial base station 34 is a base station mounted at a fixed location. In this example, the terrestrial base station 34 is a macrocell base station. In another otherwise similar example (not shown) the terrestrial base station 34 is a small cell base station.

[0073] The drone base stations 42 each consists of a small cell base station mounted on a drone, where a drone is a small pilot-less radio controlled aircraft and have a radio link to the backhaul node 36. A drone base station 42 provides a small cell coverage area to provide service to user terminals. Two drone-connected user terminals denoted UE1 and UE2 are shown for simplicity in FIGS. 3 to 5.

[0074] In this example, the radio link from each drone base station 42 to the backhaul node 36 is on the same Radio Access Technology (RAT), same frequency band and same antenna type as the connections to the user terminals UE1, UE2. However in some other, otherwise similar, examples (not shown) a different RAT, frequency band and/or antenna type is/are used.

[0075] The backhaul node 6 acts to transmit data from the drone base stations 42 into the network 32. The drone management stage 38 is shown as a separate unit for ease of explanation. In practise, the drone management stage is integrated into any of the network nodes, for example the terrestrial base station, core network or backhaul node.

Before Drone Base Station Replacement

[0076] As seen in FIG. 3, in a first phase, a Drone-BS-A serves user terminals UE1, UE2.

Drone Base Station Replacement

[0077] An example mechanism for drone base station replacement will now be described with reference to FIGS. 3 to 6. The numbering of the steps as used here are those of the steps as numbered in FIG. 6. Of course, other mechanisms are possible.

[0078] In FIG. 6, a mobile management entity (MME) and Packet Data Network Gateway (PDN GW) are shown. These are parts for the core network 40.

[0079] Detecting the Need for Replacement:

[0080] Step 1: Drone-BS-A detects the need to be replaced, in this example because its battery is getting empty. Drone-BS-A informs the network 32 by sending a message via the backhaul node 36 to the Drone Management stage 38. The message contains information as to: Cause for replacement, Measurement reports of base stations measured by Drone-BS-A, and Measurement reports of Drone base stations as well as of terrestrial bases stations, if available, as measured by user terminals and sent to the Drone-BS-A.

Sending Replacement Drone-BS to the Location:

[0081] Step 2: The Drone Management stage 38 decides that another drone should replace Drone-BS-A. It selects Drone-BS-B for this and commands Drone-BS-B to fly to the location of Drone-BS-A (see FIG. 4). Please note that for safety reasons, Drone-BS-B is always kept at least a minimum distance from Drone-BS-A.

Drone-BS-B Arrives in the Vicinity of Drone-BS-A:

[0082] Step 3: Once Drone-BS-B has reached the given geographical position, Drone-BS-B informs the Drone-Management stage 38 that it has reached that target position.

[0083] Step 4: The Drone-Management stage 38 informs Drone-BS-A that the replacement drone, namely Drone-BS-B, is now available. (In an otherwise similar alternative embodiment (not shown), Drone-BS-B send this information of availability directly to the Drone-BS-A).

Take-Over of the Wireless Service by Drone-BS-B (see FIG. 5):

[0084] Step 5: Drone-BS-B is then configured to take over the wireless service. This includes the transfer to Drone BS-B of configuration data in respect of Drone-DB-A and the transfer of the current users' contexts.

[0085] Step 6: Drone-BS-B starts receiving uplink user data (while Drone-BS-A still does too). At this time, only Drone-BS-A forwards the uplink user data to the backhaul node 36.

[0086] Step 7: When Drone-BS-B identifies that itself (Drone-BS-B) is properly receiving the uplink data and forwarding that data to the backhaul node 36, Drone-BS-B instructs Drone-BS-A to stop uplink reception.

[0087] Step 8: Drone-BS-A acknowledges stopping uplink reception and reports to Drone-BS-B the context information for the uplink user data that Drone BS-A has already forwarded via backhaul node 36.

[0088] Step 9: Drone-BS-B starts sending uplink data via the backhaul node 36 (making use of the context information for data already sent via Drone-BS-A and the backhaul node 36).

[0089] Step 10: Drone-BS-B starts sending Pilot Signals (using the same cell-id, namely Cell ID1, and same radio frequency band f1, as used by Drone-BS-A).

[0090] Step 11: Drone-BS-A stops sending Pilot Signals.

[0091] In this example Steps 10 and 11 are synchronized by Drone-BS-A detecting (not shown) a pilot signal from Drone-BS-B. Other options are possible. For example in some other embodiments (not shown) a message is sent from Drone-BS-B to Drone BS-A to indicate that Drone-BS-B has started sending pilot signals and Drone-BS-A should stop pilot signals).

[0092] Step 12: Drone-BS-B informs the backhaul node 36 directly to switch the path for the downlink user data so that the downlink user data is no longer sent to Drone-BS-A but to Drone-BS-B. In an alternative embodiment (not shown), Drone-BS-A informs the backhaul node. In another alternative embodiment (not shown), the backhaul node 36 is informed via the drone management stage rather than directly via the backhaul node. As shown in FIG. 7, the backhaul node 36 and Drone management stage 38 differentiate between the two drone base stations for this purpose using their unique Internet Protocol identifiers. In this example, these identifiers are IP1 for Drone-BS-A and IP2 for Drone-BS-B. The identities IP1 and IP2 are provided by an Operations and Management Centre OMC which is part of the core network. The drone base stations also have an ECGI (Enhanced Cell Global Identifier which is the same for both drone base stations in this example. The drone base stations also share a further identifier PC1 1.

[0093] Step 13: Drone-BS-B starts transmitting downlink user data.

[0094] Step 14: Drone-BS-A stops transmitting downlink user data; and Drone-BS-B informs the drone management stage 38 that the procedure is completed (Drone BS-B has now taken over all wireless service).

[0095] Step 15: The drone management stage 38 instructs Drone BS-A to fly to a different location.

Drone-BS-A Flies Away:

[0096] Step 16: Drone-BS-A flies away, e.g., to its base or to another location where, for example, the battery can be charged or replaced.

Some Further Details

[0097] It should be noted that this drone replacement procedure is transparent to the user terminals that were connected to Drone-BS-A before the drone replacement. Their user data transmissions continue as the connections to the user terminals are seamlessly handed over to the replacement Drone-BS-B.

[0098] In these seamless handovers, the cell identity (CellID1 in this example) is unchanged. From the perspective of a user terminal no handover is seen. Also the C-RNTI (Control planeRadio Network Temporary Identifier) is retained unchanged by the drone handover.

[0099] Also the mobile management entity sees an unchanged cell identifier CellID1, so a S1AP Path switch is not required to attach Drone-BS-B to the MME. S1 denotes an interface between a small cell base station and a gateway (not shown in FIGS. 3 to 6). AP denotes Access Point. Also no new S1 interface is required.

[0100] As regards the drone management stage 38, this sees the both drones, in other words two small cells, both having the same cell identifier, CellID1. The drone management stage coordinates the handover via appropriate control signalling to the drones.

X2 Routing

[0101] As part of the drone replacement procedure, both the cell context and user terminal context (denoted UE context) are transferred from Drone-BS-A to Drone-BS-B using an X2 interface. The X2 interface is a logical direct link between the two drones.

[0102] As shown in FIG. 8, in this example (which described above with reference to FIGS. 3 to 6), physically speaking, the X2 interface passes via the backhaul node 36. In consequence, the UE context is routed via the backhaul node 36. This approach has an advantage in providing and guaranteeing a layer of interoperability if Drone-BS-A and Drone-BS-B are from different equipment manufacturers.

[0103] Referring back to FIG. 7, the drone base stations exchange information over the X2 interface using, as addresses in the information messages, their IP identifiers, IP1 and IP2.

[0104] As shown in FIG. 9, alternatively, in otherwise similar example networks (not shown), the X2 interface passes physically directly from drone to drone. X2 messages pass directly over a wireless interface between the drones, where the wireless interface uses any appropriate radio access technology (RAT), for example Long Term Evolution Device-to-Device ((LTE-D2D) technology, Wireless Local Area Network (WLAN), or microwave. The UE context is transmitted directly between the drones. This has the advantage that UE context transfer is faster as no intermediate node, such as the backhaul node, is involved. In some alternative examples, the direct physical interface uses a different radio access technology and radio frequency band to that used between the drone base station and its connected user terminals. Other advantages are that there is no load on the backhaul node due to UE context transfer and there is less radio interference to terrestrial base stations, for example to macrocell base stations in an underlying macrocellular network. Of course in the case that the drones are from different manufacturers, the protocols of the physical interface may need to be standardised.

[0105] It will be noted that that in the examples shown in FIGS. 8 and 9, even though the interface between drones differs physically, the relevant control signalling procedures are the same as they are defined logically by the X2 interface between the drones.

Frequency Band Usage

[0106] As shown in FIG. 10, in the example described by reference to FIGS. 3 to 8, both Drone-BS-A and Drone-BS-B use the same frequency band. Drone-BS-A and Drone-BS-B are synchronised so that when Drone-BS-B starts sending pilot signals, Drone-BS- stops sending pilot signals. Similarly, when Drone-BS-A stops transmitting user data downlink (to a user terminal), Drone-BS-B takes over the transmission of user data downlink.

[0107] Alternatively, in an otherwise similar example (not shown), the frequency band is split into two-sub-bands and each of the two drone base stations uses a different sub-band. This reduces the requirement of synchronisation. Also there is less risk of significant interference between the two drone base stations. Taking this approach, during UE context transfer, the Drone-BS-A occupies the first sub-band serving some user terminals in the cell. Meanwhile, Drone-BS-B uses the other sub-band to make connections with both other user terminals in the cell and user terminals connected to Drone-BS-A for which Drone-BS-B has received the UE context.

Base Transceiver Unit

[0108] As shown in FIGS. 11 and 12, considering a base station 43 as including a base transceiver unit 45 and a radio head 47, in the example described above with reference to FIGS. 3 to 7 and 9 the base stations 43 are mounted on the drones 41, to form the drone base stations 42.

[0109] Alternatively, as shown in FIGS. 13 and 14, a radio head 47 is mounted on a drone 41 whilst the base transceiver unit 45 is located elsewhere in the network for example on the ground attached to the backhaul node. The radio head 47 is then often referred to as a remote radio head (RRH). Using this approach, it can be considered that the drone-mounted base station 43 is pared down. Less processing is undertaken on the drone 41, for example UE context transfer. Also synchronisation requirements are less stringent as both Drone-BS-A and Drone-BS-B are served by the same base transceiver unit. However, more control data is sent via the backhaul link with the backhaul node than compared to if the base transceiver unit were drone-mounted.

[0110] The present invention may be embodied in other specific forms without departing from its essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope.

[0111] A person skilled in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Some embodiments relate to program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. Some embodiments involve computers programmed to perform said steps of the above-described methods.