GB2586920A - Cellular telecommunications network - Google Patents
Cellular telecommunications network Download PDFInfo
- Publication number
- GB2586920A GB2586920A GB2014167.7A GB202014167A GB2586920A GB 2586920 A GB2586920 A GB 2586920A GB 202014167 A GB202014167 A GB 202014167A GB 2586920 A GB2586920 A GB 2586920A
- Authority
- GB
- United Kingdom
- Prior art keywords
- base station
- donor
- mobile base
- reference object
- mobile
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000001413 cellular effect Effects 0.000 title claims abstract description 21
- 230000006855 networking Effects 0.000 claims abstract 2
- 238000000034 method Methods 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 4
- 230000000977 initiatory effect Effects 0.000 claims 1
- 238000005259 measurement Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 3
- 238000007430 reference method Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/18502—Airborne stations
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/18502—Airborne stations
- H04B7/18504—Aircraft used as relay or high altitude atmospheric platform
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/14—Relay systems
- H04B7/15—Active relay systems
- H04B7/185—Space-based or airborne stations; Stations for satellite systems
- H04B7/1853—Satellite systems for providing telephony service to a mobile station, i.e. mobile satellite service
- H04B7/18539—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection
- H04B7/18541—Arrangements for managing radio, resources, i.e. for establishing or releasing a connection for handover of resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0064—Transmission or use of information for re-establishing the radio link of control information between different access points
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/24—Reselection being triggered by specific parameters
- H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
- H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/005—Moving wireless networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Astronomy & Astrophysics (AREA)
- Aviation & Aerospace Engineering (AREA)
- General Physics & Mathematics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A cellular telecommunications network having a first base station 30 and a second base station 20, wherein the first base station 30, e.g. an Unmanned Aerial Vehicle (UAV), is moving relative to a reference object, e.g. the earth, and serves a User Equipment (UE) 40. The UE’s relative speed with respect to the reference object is identified and a message to handover the UE 40 is prepared and sent to the second base station 20 to initiate handover, the message including information elements that indicate the UE’s relative speed to the reference object, wherein a mobility state for the UE 40 may be estimated from the information elements. The first base station 30 is connectable to a core networking entity via a donor connection to a donor base station 10, and the information elements include a first information element representing a size of the donor base station’s coverage area and a second information element representing a time the donor base station 10 has acted as a donor for the first base station 30.
Description
Intellectual Property Office Application No. GB2014167.7 RTM Date:17November 2020 The following terms are registered trade marks and should be read as such wherever they occur in this document:
LT E
Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo
CELLULAR TELECOMMUNICATIONS NETWORK
Field of the Invention
The present invention relates to a method in a cellular telecommunications network. In particular, it relates to a method of determining a mobility state estimate of a User Equipment (UE) in a cellular telecommunications network.
Background
A cellular telecommunications network comprises a plurality of base stations which each have a coverage area. User Equipment (UE) are typically mobile and travel within and in between the coverage areas of the plurality of base stations The cellular telecommunications network provides several processes, known as cell reselection and handover, to allow UEs to move from the coverage area of one base station to the coverage area of another base station without losing service.
One parameter in cellular telecommunications networks is the UE's speed (or an estimate thereof), which in the Long Term Evolution (LTE) protocol is known as the mobility state estimate'. When a UE is in connected mode, the serving base station estimates this parameter for a UE in order to classify the UE into one of three mobility states (e.g. "normal", "fast" or "very fast"), based upon which the base station configures several mobility related parameters (e.g. measurement reporting triggers) for the UE.
When a UE first connects to a base station in the cellular telecommunications network (e.g. after power-up), the base station will classify the UE as having a "normal" mobility state estimate and will use the associated mobility related parameters. Thereafter, the UE will be transferred between base stations as it moves between their respective coverage areas. Following several such handovers, a base station will more accurately estimate the UE's mobility state based on information contained in a handover request message. The handover request message from the serving base station to the target base station includes a "UE History" field indicating, for the last 16 serving base stations for that UE including the current serving base station: an identifier for each serving base station, the time the UE stayed in the coverage area of each of those serving base stations, and an approximate size of each coverage area of those serving base stations. The target base station may then estimate the UE's mobility state from this historical information.
Modern cellular telecommunications networks also use mobile base stations, in which the base stations are movable either through self-powered movement or by being fixed to a moving vehicle (such as a train or car). They are particularly useful in areas where there are sudden increases in demand and/or where fixed infrastructure is difficult or expensive to deploy. When a UE is connected to a mobile base station, it may be correctly identified as having the "normal" mobility state estimate if it is moving at the same or similar speed with respect to the mobile base station's frame of reference. However, if the mobile base station and UE are both moving relatively quickly with respect to a non-mobile base station's frame of reference, then a problem arises if the non-mobile base station is the target base station in a handover from the mobile base station. That is, if the UE History information indicates that the UE has been inside the mobile base station's coverage area for a long time, then the target base station will classify the UE into the "normal" mobility state estimate and set its mobility related parameters (e.g. measurement reporting triggers) based on that estimate. However, if the UE and serving base station are both mobile and moving relatively fast to the target base station's frame of reference, such that the UE would more correctly described as "fast" or "very fast' relative to the target base station's frame of reference, then these mobility related parameters will be inappropriate. The UE will then experience poor Quality of Service (QoS).
It is therefore desirable to alleviate some or all of the above problems. In particular, it is desirable for the UE's mobility state estimate to be correctly classified following a transfer from a mobile serving base station to a target base station.
Summary of the Invention
According to a first aspect of the invention, there is a provided a method as claimed in Claim 1 According to a second aspect of the invention, there is provided a computer program product comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method of the first aspect of the invention. The computer program may be stored on a computer readable data-carrier.
According to a third aspect of the invention, there is provided a network node as claimed in Claim 4.
Brief Description of the Figures
In order that the present invention may be better understood, embodiments thereof will now be described, by way of example only, with reference to the accompanying drawings in which.
Figure 1 is a schematic diagram of a cellular telecommunications network; Figure 2 is a schematic diagram of a first terrestrial base station of the network of Figure 1; Figure 3 is a schematic diagram of a mobile base station of the network of Figure 1; Figures 4a to 4c illustrate the mobile base station of Figure 3 moving relative to a first and second terrestrial base station of the network of Figure 1; Figure 5 is a flow diagram of a first example of a reference method; Figures 6a to 6c illustrate the mobile base station in an embodiment of the present invention; and Figure 7 is a flow diagram of an embodiment of a method of the present invention.
Detailed Description of Embodiments
An example of a cellular telecommunications network 1 will now be described with reference to Figures 1 to 3. The cellular telecommunications network 1 includes a first and second terrestrial base station 10,20, and a mobile base station 30. In this example, the mobile base station 30 is an Unmanned Aerial Vehicle (UAV), and it serves a User Equipment (UE) 40.
The first terrestrial base station 10 is shown in more detail in Figure 2. The first terrestrial base station 10 includes a first transceiver 11, a processor 13, memory 15, and a second transceiver 17, all connected via bus 19. In this example, the first transceiver 11 is an antenna configured for wireless communications via the Long Term Evolution (LTE) protocol, and the second transceiver 17 is an optical fibre connection for wired communications with a core network (not shown) and other base stations of the cellular telecommunications network 1. The first terrestrial base station 10 is configured to use the first transceiver 11 to communicate with a UE of the cellular network 1 (e.g. UE 40) to provide voice and/or data communication services.
The first terrestrial base station 10 stores, in memory 15, a "UE History" database. This data indicates, for each UE that the first terrestrial base station 10 serves, information regarding the first terrestrial base station 10 and up to fifteen prior serving base stations for the UE. This information includes their identifier (e.g. E-UTRAN Cell Global Identifier, eCGI), an approximate size of their coverage areas (e.g. very small, small, medium or large), and the time the UE stayed within its coverage area. As will be explained in more detail, this information may be used to define the mobility state estimate (i.e. a speed estimate) for the UE.
The second terrestrial base station 20 is substantially the same as the first terrestrial base station 10, such that it may communicate with a UE (e.g. UE 40) using the LTE protocol and with the core network via an optical fibre connection.
The mobile base station 30 is shown in more detail in Figure 3 and is also similar to the first terrestrial base station 10 and includes a first and second transceiver 31, 37, a processor 33 and memory 35, all connected via bus 39. However, the second transceiver 37 is a wireless communications interface for communicating with the core network of the cellular network 1, which, in this example, is via a terrestrial base station.
The mobile base station 30 may therefore serve UE 40 via its first transceiver 31, and any data traffic associated with this UE is transmitted between the UE and the core network via the mobile base station 30 and the first or second terrestrial base station 10, 20 (that is, the first or second terrestrial base station 10, 20 may act as a "donor" base station for the mobile base station 30).
In this example, the mobile base station 30 includes a plurality of rotors which allow the mobile base station 30 to generate lift, a plurality of actuators and sensors to control its flight (which operate under the control of an autonomous flight function of the processor 33), and a power supply. Furthermore, the mobile base station 30 includes a Global Navigation Satellite System (GNSS) function, such as a Global Positioning System (GPS) function, in order to determine its position (and time derivatives thereof, such as velocity and acceleration), a compass to determine its bearing, and an altimeter to determine its height.
A first example of a reference method will now be described with reference to Figures 4a, 4b, 4c and Figure 5. In this first example, the mobile base station 30 serves UE 40 and uses the first terrestrial base station 10 as a donor base station. As shown in the diagram of Figure 4a, the mobile base station 30 is moving at a first velocity (as illustrated by its respective arrow in Figure 4a), UE 40 is also moving at the first velocity or a velocity substantially the same as the first velocity (as illustrated by its respective arrow in Figure 4a), and the first and second terrestrial base stations 10, 20 are both stationary. The UE 40 therefore remains substantially stationary relative to the mobile base station 30, whilst the UE 40 and mobile base station 30 are both moving relative to the first and second terrestrial base stations 10, 20. Figures 4a, 4b and 4c illustrate the network at times t, t+1 and t+2, showing the progression of the mobile base station 30 and UE 40 towards the position of the second terrestrial base station 20.
At time t+2, the mobile base station 30 and UE 40 move to a position within the second terrestrial base station's coverage area. In step Si, as shown in Figure 5, a condition is met to initiate a handover of the UE 40 from the mobile base station 30 to the second terrestrial base station 20. Accordingly, the mobile base station 30 prepares a handover request message, which, in this embodiment, is prepared according to the following steps.
In step S3, the mobile base station 30 retrieves data from its UE History database for UE 40. This data is represented in the following table: Previous Serving Base Base Station Information Type Value Station 1 Base Station Identifier eCGli (eCGI) Size of Base Station's Sizei Coverage Area Time UE Stayed in Base Station's Coverage Area Timei 2 Base Station Identifier eCGI2 (eCGI) Size of Base Station's Size2 Coverage Area Time UE Stayed in Base Stations Coverage Area Time2 Table 1: Table illustrating the UE History for UE 40 stored in memory of the mobile base station 30 In step S5, the mobile base station 30 compiles a handover request message, including a first part including a request that the second terrestrial base station 20 accept a handover for the UE 40 and thereafter provide voice and/or data communication services to the UE 40, and a second part being a UE History Information Element including the UE History information retrieved in step S3.
In step 57, the mobile base station 30 modifies one or more values of the UE History Information Element for UE 40. In this first example, the mobile base station 30 modifies the value of "Time UE Stayed in Base Station's Coverage Area" to indicate the time period UE 40 would have stayed in the base station's coverage area had the mobile base station 30 been stationary. This is achieved by: * the mobile base station 30 determining its own velocity, truss, using GPS measurements. This may also be expressed as the mobile base station's relative velocity to a stationary object, fi -M85 rel SO; * the mobile base station 30 determining its relative velocity with the UE 40, 11M8S rel UE, based on angle of arrival and/or UE location reports; and * the mobile base station 30 calculating the UE's relative velocity to the stationary object, a -UE rel SO, as OUE rel SO = IIMBS ret SO ± IIMBS rel UE * the mobile base station 30 calculating the time the UE would have stayed within its coverage area if the mobile base station 30 had been stationary based on the stored value of 'Size of the Base Station's Coverage Area' (=Sizei) and the UE's velocity relative to the stationary object, D'UE ret SO-As the stored value for the size of the base station's coverage area is one of 'very small', 'small', 'medium', or 'large', the base station first translates this stored value into a suitable distance metric (e.g. standardised distance values for each size). The mobile base station 30 then divides this distance by the UE's velocity relative to the stationary object, ilUE rel SO, to calculate the modified time value.
In step 59, the mobile base station 30 sends the handover request message to the second terrestrial base station 20. In step 511, the second terrestrial base station 20 determines that the handover may proceed. In step S13, the second terrestrial base station 20 populates its respective UE History database with the data in the UE History Information Element from the handover request message, including the modified time value for Time UE Stayed in Base Station's Coverage Area' for the mobile base station 30, and, in step 515, estimates a mobility state of the UE 40 based on this information. As this time value is modified such that it represents the UE's velocity relative to a stationary object, rather than relative to the mobile base station 30, the second terrestrial base station 20 will estimate a mobility state for UE 40 that accurately reflects its velocity relative to the (also stationary) second terrestrial base station 20. In step S17, the second terrestrial base station 20 sets mobility related parameters, such as the measurement reporting parameters, based on this mobility state estimate. These parameters will now be more appropriate for the UE's velocity relative to the second terrestrial base station 20 than if they had been set according to a mobility state estimated from the original time value, Timei'. In one example, the second terrestrial base station 20 may set a measurement reporting frequency that is appropriate for a fast moving UE that may move out of its coverage area in a short timeframe whereas, if the mobility state was estimated from the original time value, the measurement frequency may have been set inappropriately low (or even not at all). Alternatively, the second terrestrial base station 20 may use event based measurement reporting, and these events may be set based upon the mobility state estimate.
In step 319, the target base station 20 sends a handover request acknowledgement message to the UE (via the mobile base station 30). This includes RRC Connection Reconfiguration parameters including (or derived from) the mobility related parameters determined in step S17.
In this first example, the mobile base station 30 and UE 40 have a velocity in the same direction. However, the skilled person will understand that the method applies equally in other scenarios, such as when the UE 40 is being served by a mobile base station 30 that is travelling in an opposing direction relative to the UE 40. That is, the step of determining the relative velocity between the UE 40 and the mobile base station 30 will take this into account by summing the two relative velocities together (where one value would of course be a negative value due to it being in the opposite direction). This would result in the time value being modified to indicate that the UE would have been in the coverage area of the mobile base station 30 for a greater time had the mobile base station 30 been stationary. The target base station may then interpret the modified UE History Information Element to estimate a mobility state that is more appropriate for a slower moving UE (e.g. "normal") compared to what would have been estimated if the time value had not been modified (e.g. "fast").
In the above example, the UE and mobile base station 30 are moving at the same velocity (e.g. they are both travelling on the same moving vehicle, such as a train), such that it is possible to implement the invention by only determining velocity in a single axis (indeed, it would be possible to implement the invention using scalar speed alone). The skilled person will also understand that the method above may be expanded to cover scenarios in which the UE and mobile base station 30 are not moving along a single axis only. That is, the method outlined above may be expanded to cover movement in a two-dimensional coordinate system. In this manner, the relative velocity of the UE 40 to a stationary object may be resolved in both axes and the time value may then be modified based on the greater of these two relative velocities.
The skilled person will also understand that the target base station may use additional factors to estimate the mobility state of the UE. That is, if the target base station is itself a mobile base station, then it may estimate the mobility state of the UE using both the relative velocity of the UE to the stationary object, a relative velocity between itself and the UE (e.g. based on the UE location reports), and the size of the target base station's coverage area. It is therefore beneficial for the serving base station to modify the time value based on the relative velocity of the UE to a stationary object, such as the Earth, such that this may be interpreted in any suitable way by the target base station. It is also possible for the serving base station to modify the time value to be indicative of the UE's relative velocity to any reference object, which both the serving and target base stations may calculate their relative velocities to, in order to implement the method of the above embodiment. However, the relative velocity to a stationary object such as the Earth requires fewer processing steps.
In the first example above, the serving base station modifies the value of the time the UE stayed within its coverage area. However, the skilled person will understand that the serving base station may also modify the size of its coverage area to realise the same technical benefits. In this manner, the serving base station may convey the relative velocity of the UE and the stationary object by modifying its coverage area to be larger or smaller than it actually is (e.g. "small" to "medium" or "large" to "medium") to indicate that the relative velocity of the UE to the stationary object is greater or less than its velocity relative to the serving base station. However, it is beneficial to modify the time value as there is a limited set of options for the coverage area size and the method loses accuracy.
The above first example also has the technical benefit in that the problem of UE's having incorrect mobility state estimates when being transferred from mobile serving base stations is solved in a way which is backwards compatible with existing base stations. That is, by modifying the values indicative of the UE's velocity from a standardised message (e.g. the UE History IE of the handover request message), the serving base station may encourage any target base station to estimate the correct mobility state for the UE.
In the above first example, the serving base station 20 had a connection to the core network via a donor connection to another base station. However, this is non-essential, as the serving base station 20 may connect to the core network via any suitable method (e.g. microwave link, Wireless Local Area Network (WLAN), etc.).
There are also further examples of how the serving base station may modify the UE History Information Element to convey the relative velocity of the UE to the stationary object, which will now be described.
An embodiment of a method of the present invention will now be described with reference to Figures 6a, 6b, Sc and Figure 7. In this embodiment, the cellular telecommunications network further includes a third terrestrial base station 50, which, alike the first and second terrestrial base stations, may also act as a donor base station to the mobile base station 30. In this embodiment, the UE 40 is positioned within the coverage area of the mobile base station 30 and is being served by the mobile base station 30. At time t, as shown in Figure 6a, the mobile base station 30 and UE 40 are both within the coverage area of the first terrestrial base station 10, which acts as a donor base station to the mobile base station 30.
The mobile base station 30 is configured to populate its UE History database with information on the UE's prior serving base stations. However, in this embodiment, the UE History database is modified such that each prior base station that requires a donor connection to the core network (e.g. the mobile base station 30 of this second embodiment) is replaced with information on its one or more donor base stations. Thus, in this example, the UE History includes information on the mobile base station's donor base station (the first terrestrial base station 10) and up to fifteen prior base stations (which either previously served the UE directly or acted as a donor base station to a base station that previously served the UE). The information on the donor base station(s) includes: the donor base station's identifier (eCGI), an approximate size of the donor base station's coverage area (e.g. very small, small, medium or large), and the time the donor base station acted as donor to the mobile base station. This information, as will be detailed in the following description of a method according to this embodiment, is used in a handover message to encourage the target base station to more accurately estimate the mobility state of the UE. This will now be described.
As shown in Figure 6b, the mobile base station 30 and UE 40 both move from the first terrestrial base station's coverage area to the second terrestrial base station's coverage area at time t+1, and the second terrestrial base station 20 becomes the donor base station for the mobile base station 30. In response to the mobile base station 30 detecting that it is being served by a new donor base station, it updates its UE History database with information on the second terrestrial base station 20 (and the information regarding the first terrestrial base station 10 remains in the database as a prior donor base station).
At time t+2, as shown in Figure Sc, the mobile base station 30 and UE 40 both move from the second terrestrial base station's coverage area to the third terrestrial base station's coverage area, and the third terrestrial base station 50 becomes the donor base station for the mobile base station 30. Again, the mobile base station 30 updates its UE History database with information on the new donor base station, and the information regarding the first and second terrestrial base stations 10, 20 remains in the database. Furthermore, a condition is met such that a handover of the UE 40 from the mobile base station 30 to the third terrestrial base station 50 is triggered (step S21).
Following this trigger, in step 323, the mobile base station 30 retrieves, from memory, all entries within the UE History database. As noted above, this includes data on (up to) the last sixteen prior base stations (that previously served the UE directly or acted as a donor base station to a base station that previously served the UE) for the mobile base station 30, including their respective identifiers, their respective sizes, and the time each donor base station served the mobile base station 30.
In step 325, the mobile base station 30 prepares a handover request message having a first part including a request that the third terrestrial base station 50 accepts a handover of the UE 40 and thereafter provides voice and/or data services to the UE 40, and a second part including a UE History Information Element. In this embodiment, the UE History Information Element is populated using the following process.
In step 327, the mobile base station 30 determines if the target base station is the current donor base station. If this determination is negative (such that the target base station is not the current donor base station), then the UE History Information Element is populated with this data without any changes (step S29a). However, in this embodiment, the determination in step S27 is positive so, in step S29b, the mobile base station 30 modifies the data for the last donor base station (the third terrestrial base station 50) to use the mobile base station's identifier and the mobile base station's coverage area size (the time value remains the same to represent the time the third terrestrial base station 50 has been the donor for the mobile base station 30).
In step 331, the mobile base station 30 sends the handover request message to the third terrestrial base station 50. In step S33, the third terrestrial base station 50 determines that the handover can proceed. In step S35, the third terrestrial base station 50 populates its respective UE History database with the data in the UE History Information Element from the handover request message, including information on each prior base station, and, in step 337, estimates the mobility state of the UE 40 based on this data.
Accordingly, the UE 40 estimates the mobility state as if the UE had been previously served by the first and second (stationary) base stations 10, 20, rather than the mobile base station 30, using their respective coverage area sizes and the time the UE stayed within their respective coverage areas (based on the time the mobile base station 30 used each base station as a donor). As these two prior donor base stations are stationary, this again conveys the UE's velocity relative to a stationary object such that the target base station may accurately estimate its mobility state. The third terrestrial base station 50 then determines mobility related parameters for the UE 40 based upon this more accurate mobility state. In step S39, the third terrestrial base station 50 sends a handover request acknowledgement message to the UE (via the mobile base station 30). This includes RRC Connection Reconfiguration parameters including (or derived from) these mobility related parameters.
In the above embodiment, the mobile base station 30 modifies the entry in the UE History IE with its own data if the most recent donor is the target base station, but the time value remains as the time the target base station has been the donor to the mobile base station.
This has the benefit that it forestalls any confusion caused by a future handover in which the UE History IE would otherwise indicate that the third terrestrial base station is the serving base station and is also the immediately preceding serving base station. However, this is not essential. In an alternative scenario, the mobile base station 30 may modify the UE History IE such that the base station identifier includes dummy data.
In an IDLE mode implementation of the example of the reference method above, the UE may determine its velocity itself (that is, its relative velocity with respect to a stationary object), e.g. using GPS. The UE may then estimate its mobility state based upon the number of cell reselecfions performed in a time period, modified to take into account its actual velocity. That is, the UE calculates the time it would have been positioned within the mobile base station's coverage area had the mobile base station 30 been stationary (e.g. based upon the size of the mobile base station's coverage area and its own velocity), rather than using the actual time it has been positioned within the mobile base station's coverage area, in order to more accurately estimate its mobility state. In an IDLE mode implementation of the embodiment of the present invention above, the mobile base station 30 may also broadcast information on its donor base station, and the UE may use the donor base station's information rather than the mobile base station's information for its mobility state estimate.
The above embodiment is described for the LTE protocol, in which the UE's speed estimate is known specifically as the mobility state estimate. However, the term "mobility state" covers all forms of UE speed estimates in any cellular communications protocol.
The skilled person will understand that any combination of features is possible within the scope of the invention, as claimed.
Claims (4)
- CLAIMS1. A method of operating a first base station in a cellular telecommunications network, the cellular telecommunications network having a second base station, wherein the first base station is moving relative to a reference object and serves a User Equipment, UE, the method comprising the steps of: identifying the UE's relative speed with respect to the reference object; preparing a message to handover the UE to the second base station, the message including one or more information elements that indicate the UE's relative speed to the reference object, wherein a mobility state for the UE may be estimated from the one or more information elements indicating the UE's relative speed with respect to the reference object; and initiating a handover of the UE from the first base station to the second base station by sending the message to the second base station, wherein the message includes the one or more information elements that indicate the UE's relative speed with respect to the reference object, wherein the first base station is connectable to a core networking entity via a donor connection to a donor base station, and the one or more information elements includes a first information element representing a size of the donor base station's coverage area and a second information element representing a time the donor base station has acted as a donor for the first base station.
- 2. A computer program product comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method of Claim 1.
- 3. A computer-readable data carrier having stored thereon the computer program of Claim 2.
- 4. A network node for a cellular telecommunications network, the cellular telecommunications network including a first base station being movable relative to a reference object and serving a User Equipment, UE, wherein the network node further comprises memory and a processor, the processor configured to implement the steps of the method of Claim 1, wherein the network node is the first base station.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB2014167.7A GB2586920B (en) | 2018-02-21 | 2018-02-21 | Cellular telecommunications network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1802788.8A GB2571273B (en) | 2018-02-21 | 2018-02-21 | Cellular telecommunications network |
GB2014167.7A GB2586920B (en) | 2018-02-21 | 2018-02-21 | Cellular telecommunications network |
Publications (3)
Publication Number | Publication Date |
---|---|
GB202014167D0 GB202014167D0 (en) | 2020-10-21 |
GB2586920A true GB2586920A (en) | 2021-03-10 |
GB2586920B GB2586920B (en) | 2021-10-06 |
Family
ID=72841449
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB2014167.7A Active GB2586920B (en) | 2018-02-21 | 2018-02-21 | Cellular telecommunications network |
Country Status (1)
Country | Link |
---|---|
GB (1) | GB2586920B (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130084884A1 (en) * | 2011-10-04 | 2013-04-04 | Telefonaktiebolaget L M Ericsson (Publ) | Cell Selection Mechanism in Mobile Relay Operation |
US20150181480A1 (en) * | 2012-07-24 | 2015-06-25 | Nokia Solutions And Networks Oy | Signaling a new information element for the mobility state estimate of moving relay user equipments |
-
2018
- 2018-02-21 GB GB2014167.7A patent/GB2586920B/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130084884A1 (en) * | 2011-10-04 | 2013-04-04 | Telefonaktiebolaget L M Ericsson (Publ) | Cell Selection Mechanism in Mobile Relay Operation |
US20150181480A1 (en) * | 2012-07-24 | 2015-06-25 | Nokia Solutions And Networks Oy | Signaling a new information element for the mobility state estimate of moving relay user equipments |
Also Published As
Publication number | Publication date |
---|---|
GB2586920B (en) | 2021-10-06 |
GB202014167D0 (en) | 2020-10-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11470533B2 (en) | Handover from a moving base station | |
KR20230036080A (en) | Apparatus and method for recommending target user equipment for sidelink-assisted positioning | |
KR20230026339A (en) | Manual positioning with sidelink support | |
EP2878161A2 (en) | Enhancing positioning in multi-plmn deployments | |
US11363418B2 (en) | Method and apparatus for handling positioning of a target device | |
WO2022216353A1 (en) | Signaling timing error group updates for positioning | |
WO2022154861A1 (en) | Reference selection for double difference positioning | |
KR20230107578A (en) | Uplink-based positioning | |
WO2021225499A1 (en) | User equipment, network node and methods in a radio communications network | |
GB2586920A (en) | Cellular telecommunications network | |
US20220231805A1 (en) | Reference selection for double difference positioning | |
GB2571273A (en) | Cellular telecommunications network | |
WO2022086378A1 (en) | User equipment (ue) movement state estimation based on measurements for two or more sites in a wireless network | |
WO2023014432A1 (en) | Prioritization criteria for positioning measurements in a time window measurement scheme | |
US20230050110A1 (en) | Network notification of a cell timing source outage | |
KR20240032817A (en) | Timing error group pair priority indications for positioning | |
WO2023009045A1 (en) | Network node, user equipment and methods for determining reliability of positions of a user equipment | |
KR20240019108A (en) | Configure baseline location device capabilities | |
KR20240022488A (en) | UE flight path reporting | |
CN115997431A (en) | Method, apparatus, system and product for position determination | |
WO2024039400A1 (en) | Updating machine learning model for positioning | |
KR20240036587A (en) | Sidelink assisted arrival time difference-based positioning | |
CN117014799A (en) | Communication method and device | |
OA20170A (en) | Method and apparatus for handling positioning of a target device. |