WO2021058103A1 - Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés - Google Patents

Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés Download PDF

Info

Publication number
WO2021058103A1
WO2021058103A1 PCT/EP2019/076066 EP2019076066W WO2021058103A1 WO 2021058103 A1 WO2021058103 A1 WO 2021058103A1 EP 2019076066 W EP2019076066 W EP 2019076066W WO 2021058103 A1 WO2021058103 A1 WO 2021058103A1
Authority
WO
WIPO (PCT)
Prior art keywords
client device
mobility event
network node
mobility
handover
Prior art date
Application number
PCT/EP2019/076066
Other languages
English (en)
Inventor
Dalia-Georgiana POPESCU
Mikko SÄILY
Elena Virtej
Luis Guilherme Uzeda Garcia
Original Assignee
Nokia Technologies Oy
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 Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2019/076066 priority Critical patent/WO2021058103A1/fr
Publication of WO2021058103A1 publication Critical patent/WO2021058103A1/fr

Links

Classifications

    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H04W36/008375—Determination of triggering parameters for hand-off based on historical data
    • 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/322—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by location data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • 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/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H04W36/305—Handover due to radio link failure

Definitions

  • Various example embodiments relate to modern wireless communication devices and networks. In partic ular, various example embodiments relate to handover management.
  • RSRP reference signal received power
  • RSRQ reference signal received Quality
  • An example embodiment of a network node device comprises at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the network node de vice to at least perform: obtaining mobility event information for one or more client devices for wireless communication, each piece of the mobility event information comprising a first part indicating a mobility event associated with a client device of the one or more client devices and a second part indicating the position of the client device at the time of the mobility event; and based on the obtained mobility event infor mation, generating mobility event map information for assisting in the processing of subsequent handover events in a radio access network associated with the network node device, the mobility event map information depicting the indicated mobility events in the associ ated client device positions in the radio access net work.
  • the obtaining of the mobility event information comprises receiving the positions of the one or more client de vices from the one or more client devices.
  • the obtaining of the mobility event information comprises receiving data for determining the positions of the one or more client devices from the one or more client de vices.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network node device to at least perform: modifying the generated mobility event map in formation by indicating a trigger area around one or more of the client device positions associated with the mobility events.
  • the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network node device to at least perform: transmitting at least a portion of the gener ated or modified mobility event map information to one or more base station devices in the radio access net work.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed at network deployment.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed in response to a request from one or more of the base station devices.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed in accordance with a timer.
  • the network node device is configured to implement at least one of a location management function or a location management component.
  • the mobility event map information is one of mobility event type specific, client device type specific, or condi tions specific.
  • the mobility event comprises a mobility robustness optimi zation event.
  • the mobility event comprises at least one of a successful handover, a handover resulting in a radio link failure, a handover occurring too early, or a handover occurring too late.
  • An example embodiment of a network node device comprises means for performing: obtaining mobility event information for one or more client devices for wireless communication, each piece of the mobility event information comprising a first part indicating a mobility event associated with a client device of the one or more client devices and a second part indicating the position of the client device at the time of the mobility event; and based on the obtained mobility event infor mation, generating mobility event map information for assisting in the processing of subsequent handover events in a radio access network associated with the network node device, the mobility event map information depicting the indicated mobility events in the associ ated client device positions in the radio access net work.
  • An example embodiment of a method comprises: obtaining, by a network node device, mobility event information for one or more client devices for wireless communication, each piece of the mobility event information comprising a first part indicating a mobil ity event associated with a client device of the one or more client devices and a second part indicating the position of the client device at the time of the mobility event; and based on the obtained mobility event infor mation, generating, by the network node device, mobility event map information for assisting in the processing of subsequent handover events in a radio access network associated with the network node device, the mobility event map information depicting the indicated mobility events in the associated client device positions in the radio access network.
  • the obtaining of the mobility event information comprises receiving the positions of the one or more client de vices from the one or more client devices.
  • the obtaining of the mobility event information comprises receiving data for determining the positions of the one or more client devices from the one or more client de vices.
  • the method further comprises modifying, by the network node device, the generated mobility event map information by indicating a trigger area around one or more of the client device positions associated with the mobility events.
  • the method further comprises transmitting, by the network node device, at least a portion of the generated or modified mobility event map information to one or more base station devices in the radio access network.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed at network deployment.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed in response to a request from one or more of the base station devices.
  • the transmitting of the at least a portion of the generated or modified mobility event map information is performed in accordance with a timer.
  • the network node device is configured to implement at least one of a location management function or a location management component.
  • the mobility event map information is one of mobility event type specific, client device type specific, or condi tions specific.
  • the mobility event comprises a mobility robustness optimi zation event.
  • the mobility event comprises at least one of a successful handover, a handover resulting in a radio link failure, a handover occurring too early, or a handover occurring too late.
  • An example embodiment of a computer program product comprises program code configured to perform the method according to any of the above network node device related example embodiments, when the computer program product is executed on a computer.
  • An example embodiment of a base station device for wireless communication in a radio access network comprises at least one processor, and at least one memory including computer program code.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the base station device to at least perform: receiving, from a network node device, at least a portion of mobility event map information for assist ing in the processing of subsequent handover events in the radio access network, the mobility event map infor mation depicting previous mobility events in associated client device positions in the radio access network; tracking the movement of a client device in a radio access network cell served by the base station device; receiving signal strength information from the tracked client device; and in response to the received signal strength information indicating a triggering signal strength change and the tracked movement of the client device indicating that the client device is approaching an area in the radio access network cell that the received at least the portion of the mobility event map information depicts as an area in which triggering mobility events occurred previously, configuring a customized handover event for the client device based on the received signal strength information and the received
  • the triggering signal strength change comprises signal strength of the base station device decreasing and sig nal strength of a neighboring base station device in creasing.
  • the triggering mobility event comprises a handover occurring too early
  • the customized handover event for the client device comprises a safety threshold added to a handover event triggered when a neighboring cell becomes better than the serving cell by an offset.
  • the handover event triggered when a neighboring cell becomes better than the serving cell by an offset comprises a long-term evolution (LTE) A3 event.
  • the triggering mobility event comprises a handover occurring too late
  • the customized handover event for the client device comprises a handover event configured to trigger faster than default
  • An example embodiment of a base station device for wireless communication in a radio access network comprises means for performing: receiving, from a network node device, at least a portion of mobility event map information for assist ing in the processing of subsequent handover events in the radio access network, the mobility event map infor mation depicting previous mobility events in associated client device positions in the radio access network; tracking the movement of a client device in a radio access network cell served by the base station device; receiving signal strength information from the tracked client device; and in response to the received signal strength information indicating a triggering signal strength change and the tracked movement of the client device indicating that the client device is approaching an area in the radio access network cell that the received at least the portion of the mobility event map information depicts as an area in which triggering mobility events occurred previously, configuring a customized handover event for the client device based on the received signal strength information and the received at least the por tion of the mobility event map information.
  • An example embodiment of a method comprises: receiving, at a base station device from a net work node device, at least a portion of mobility event map information for assisting in the processing of sub sequent handover events in the radio access network, the mobility event map information depicting previous mo bility events in associated client device positions in the radio access network; tracking, by the base station device, the move ment of a client device in a radio access network cell served by the base station device; receiving, by the base station device, signal strength information from the tracked client device; and in response to the received signal strength information indicating a triggering signal strength change and the tracked movement of the client device indicating that the client device is approaching an area in the radio access network cell that the received at least the portion of the mobility event map information depicts as an area in which triggering mobility events occurred previously, configuring, by the base station device, a customized handover event for the client de vice based on the received signal strength information and the received at least the portion of the mobility event map information.
  • the triggering signal strength change comprises signal strength of the base station device decreasing and sig nal strength of a neighboring base station device in creasing.
  • the triggering mobility event comprises a handover occurring too early
  • the customized handover event for the client device comprises a safety threshold added to a handover event triggered when a neighboring cell becomes better than the serving cell by an offset.
  • the handover event triggered when a neighboring cell becomes better than the serving cell by an offset comprises a long-term evolution (LTE) A3 event.
  • the triggering mobility event comprises a handover occurring too late
  • the customized handover event for the client device comprises a handover event configured to trigger faster than default
  • An example embodiment of a computer program product comprises program code configured to perform the method according to any of the above base station device related example embodiments, when the computer program product is executed on a computer.
  • An example embodiment of a client device for wireless communication comprises at least one processor, and at least one memory including computer program code.
  • the at least one memory and the computer program code are configured to, with the at least one processor, cause the client device to at least perform: determining position information of the client device; and transmitting the determined position infor mation of the client device to a network node device for assisting in the processing of subsequent handover events in a radio access network associated with the network node device.
  • the position information of the client device comprises the position of the client device calculated by the client device based on one or more positioning reference signal transmission points.
  • the position information of the client device comprises up link positioning reference signal symbols, and infor mation about at least one of downlink positioning ref erence signal measurements, a cell identifier, a beam identifier, or a timing advance.
  • An example embodiment of a client device comprises means for performing: determining position information of the client device; and transmitting the determined position infor mation of the client device to a network node device for assisting in the processing of subsequent handover events in a radio access network associated with the network node device.
  • An example embodiment of a method comprises: determining, by a client device, position in formation of the client device; and transmitting, by the client device, the deter mined position information of the client device to a network node device for assisting in the processing of subsequent handover events in a radio access network associated with the network node device.
  • the position information of the client device comprises the position of the client device calculated by the client device based on one or more positioning reference signal transmission points.
  • the position information of the client device comprises up link positioning reference signal symbols, and infor mation about at least one of downlink positioning ref erence signal measurements, a cell identifier, a beam identifier, or a timing advance.
  • An example embodiment of a computer program product comprises program code configured to perform the method according to any of the above client device re lated example embodiments, when the computer program product is executed on a computer.
  • FIG. 1 shows an example embodiment of the sub ject matter described herein illustrating an example system, where various example embodiments of the present disclosure may be implemented;
  • FIG. 2A shows an example embodiment of the sub ject matter described herein illustrating a network node device
  • FIG. 2B shows an example embodiment of the sub ject matter described herein illustrating a base station device
  • FIG. 2C shows an example embodiment of the sub ject matter described herein illustrating a client device
  • FIG. 3 shows an example embodiment of the sub ject matter described herein illustrating a method
  • FIG. 4 shows an example embodiment of the sub ject matter described herein illustrating a customized new handover event
  • FIG. 5A shows an example embodiment of the sub ject matter described herein illustrating a mobility event map
  • FIG. 5B shows an example embodiment of the sub ject matter described herein illustrating a modified mobility event map.
  • Fig. 1 illustrates an example system 100, where various embodiments of the present disclosure may be implemented.
  • the system 100 may comprise a fifth gener ation (5G) new radio (NR) network.
  • An example represen tation of the system 100 is shown depicting client de vices 220A, 220B, 220C, base station devices 210A, 210B, a network node device 200, and a radio access network (RAN) 250.
  • the RAN 250 may comprise a next-generation radio access network (NG-RAN).
  • NG-RAN next-generation radio access network
  • the client devices 220A, 220B, 220C may include e.g. mobile phones, smartphones, tablet computers, smart watches, or any hand-held or portable device.
  • the client devices 220A, 220B, 220C may also be referred to as user equipment (UE).
  • the base station devices 210A, 210B may include e.g. fifth-generation base stations (gNB) or any such devices suitable for providing an air interface for client devices to connect to a wireless network via wireless transmissions.
  • gNB fifth-generation base stations
  • the network node device 200 may implement or include location management function (LMF) or a location management component (LMC).
  • LMF is a network entity in the 5G core network (5GC) that may provide various location management functionalities, such as obtaining downlink (DL) location measurements or a location estimate from a UE, and/or obtaining uplink (UL) location measurements from the NG RAN.
  • An LMC may provide substantially similar location management functionalities than an LMF, but whereas an LMF may be core network (CN) based, an LMC may be RAN based.
  • the system 100 may comprise an access and mobility management function (AMF) 230.
  • An AMF may offer services to e.g. session management func tion (SMF), other AMFs, policy control functions (PCF), short message service function (SMSF), location manage ment function (LMF), and/or gateway mobile location cen tre (GMLC).
  • SMF session management func tion
  • PCF policy control functions
  • SMSF short message service function
  • LMF location manage ment function
  • GMLC gateway mobile location cen tre
  • Some of these AMF services may include e.g. registration, connection, reachability and mobility management.
  • MRO mobility robust ness optimization
  • At least some of the example embodiments comprise three phases: i. an offline phase for collection of data and building of maps. This may be done offline for a large amount of UEs.
  • the LMF may be informed about the event and the position of the UE when the event takes place.
  • the LMF may build areas around the locations of the collected RLF events positions; ii. an offline/online phase in which the maps are sent to the gNBs. I.e. after building these maps, the LMF sends the map object to the gNBs; iii. an online phase in which new handover custom events are created using the maps.
  • the gNB may track the UE movement through the cell and the UE will report the signal strength from the serving gNB and the neighboring gNBs. In case the signal strength of the serving gNB is de creasing and the signal strength of a neighboring gNB is increasing, and the UE is approaching an area where RLFs occurred, then the gNB may proactively build and configure a custom handover event to the UE.
  • FIG. 2A is a block diagram of a network node device 200, in accordance with an example embodiment.
  • the network node device 200 may be con figured to implement a location management function (LMF) or a location management component (LMC).
  • LMF location management function
  • LMC location management component
  • the network node device 200 of Fig. 2A may include the network node device 200 of Fig. 1.
  • the network node device 200 comprises one or more processors 202, and one or more memories 204 that comprise computer program code.
  • the network node device 200 may also include a transceiver 205, as well as other elements not shown in FIG. 2A.
  • the network node device 200 is de picted to include only one processor 202, the network node device 200 may include more processors.
  • the memory 204 is capable of storing instruc tions, such as an operating system and/or various ap plications.
  • the processor 202 is capable of executing the stored instructions.
  • the processor 202 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and one or more single core pro cessors.
  • the processor 202 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for ex ample, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a mi crocontroller unit (MCU), a hardware accelerator, a spe cial-purpose computer chip, or the like.
  • the processor 202 may be configured to execute hard-coded functionality.
  • the proces sor 202 is embodied as an executor of software instruc tions, wherein the instructions may specifically con figure the processor 202 to perform the algorithms and/or operations described herein when the instructions are executed.
  • the memory 204 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices.
  • the memory 204 may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
  • the at least one memory 204 and the computer program code are configured to, with the at least one processor 202, cause the network node device 200 to perform obtaining mobility event information for one or more client devices 220A-220C for wireless communica tion.
  • mobility event comprises both a handover event (i.e. handover from a source cell to a target cell in RRC_CONNECTED state) and a cell selection / cell re-selection event (i.e. cell selection or cell re-selection in RRC_INACTIVE or RRC_IDLE states).
  • RRC refers to radio resource control pro tocol.
  • Each piece of the mobility event information comprises a first part indicating a mobility event as sociated with a client device of the one or more client devices 220A-220C, and a second part indicating the po sition of this client device at the time of the mobility event.
  • the mobility event may comprise a mobility robustness optimization (MRO) event.
  • MRO mobility robustness optimization
  • 5G NR MRO is intended to automatically configure handover pa rameters in cells to improve handover performance. That is, the goal of MRO is to automatically detect and solve problems related to intra-5G and inter-RAT (radio access technology) mobility, which include, but not limited to, too early handover, too late handover, handover to wrong cell, unnecessary handover, and ping-pang handover.
  • MRO mobility robustness optimization
  • the mobility event may comprise a successful handover, a handover resulting in a radio link failure, a handover occurring too early, and/or a handover occurring too late.
  • the first part of the mobility event information may be based on information about the occurred mobility event that the network node device 200 receives or acquires from a base station device 210A, 210B responsible for handling the occurred mobility event.
  • the obtaining of the mobility event information may comprise receiving the positions of the one or more client devices 220A-220C from the one or more client devices 220A-220C.
  • client device or UE based positioning may be utilized. That is, in this embodiment, the UE knows the location (relative or absolute) of positioning reference signal (PRS) transmission points, computes its position, and sends it to the network node device 200 (e.g. LMC/LMF).
  • PRS positioning reference signal
  • the obtaining of the mobility event information may comprise receiving data for determining the positions of the one or more client devices 220A-220C from the one or more client devices 220A-220C.
  • client device or UE assisted positioning may be utilized. That is, in this embodiment, the UE may transmit uplink PRS symbols for network-based measurements. Furthermore, the UE may send information about downlink PRS measurements, Cell-ID, Beam ID, TA, etc. to the network node device 200 (e.g. LMC/LMF). Then, the network node device 200 (e.g. LMC/LMF) may calculate the UE position. Optionally, the network node device 200 (e.g. LMC/LMF) may also send the calculated UE position to the AMF 230 (e.g. to ensure backwards compatibility with previous communication network versions).
  • the network node device 200 e.g. LMC/LMF
  • the network node device 200 may also send the calculated UE position to the AMF 230 (e.g. to ensure backward
  • the collection of the mobility event information may be done (e.g. offline) for a large amount of UEs, to ensure reliability and lack of bias of data.
  • a mobility event for example a successful handover, or a handover that ends with a radio link failure (e.g. too early handover) is triggered
  • the LMF is informed by a base station device (gNB) about the mobility event, and the LMF is informed by a UE about the position of the UE when the mobility event took place.
  • the LMF may assign a label for the mobility event and build a map of the mobility events, as further discussed below.
  • the at least one memory 204 and the computer program code are further configured to, with the at least one processor 202, cause the network node device 200 to perform generating mobility event map information (e.g. a map object) for assisting in the processing of subsequent handover events in a radio access network 250 associated with the network node device 200, based on the obtained mobility event information.
  • the mobility event map information depicts the indicated mobility events in the associated client device positions in the radio access network 250.
  • the mobility event map information may be mobility event type spe cific, client device type specific, and/or conditions specific.
  • the mobility event map infor mation may have e.g. different res olution, use-cases and validity time.
  • Examples include: one map per event-type (too early HO, beam failure, etc.), one map per UE -type or optimized per UE type (such as mMTC (massive machine type communications), eMBB (enhanced mobile broadband), URLLC (ultra-reliable and low-latency communications)), speed, etc.), and one map per conditions and/or environment (such as day/night, indoor/outdoor).
  • one map per event-type too early HO, beam failure, etc.
  • one map per UE -type or optimized per UE type such as mMTC (massive machine type communications), eMBB (enhanced mobile broadband), URLLC (ultra-reliable and low-latency communications)), speed, etc.
  • mMTC massive machine type communications
  • eMBB enhanced mobile broadband
  • URLLC ultra-reliable and low-latency communications
  • Diagram 500 of Fig. 5A shows an example of the mobility event map information depicting base stations devices gNBl-gNB7.
  • the mobility events in the associated client device positions are shown as dots 501.
  • the at least one memory 204 and the computer program code may optionally be further configured to, with the at least one processor 202, cause the network node device 200 to perform modifying the generated mo bility event map information by indicating a trigger area (or a safety area) around one or more of the client device positions associated with the mobility events.
  • a trigger area refers to an area around a mobility event position (s) in which a custom handover event may be configured to be triggered in addition to the actual mobility event position (s), for example for safety reasons.
  • the network node device 200 may process/optimize the generated mobility event map information after collecting the mobility event information.
  • Diagram 550 of Fig. 5B shows an ex ample of building trigger areas around the locations of the collected RLF events positions. For example, for a too late handover, an example possibility is to expand the area for triggering the handover to prevent such a failure in the future.
  • the at least one memory 204 and the computer program code may optionally be further configured to, with the at least one processor 202, cause the network node device 200 to perform transmitting at least a por tion of the generated or modified mobility event map information to one or more base station devices 210A- 210B in the radio access network 250.
  • the network node device 200 may store mobility event map information for the entire net work that the network node device 200 "sees", while a given base station device (gNB) is passed just a portion of the mobility event map information that is relevant for its surroundings (for example just the area inside its cell borders).
  • gNB base station device
  • This embodiment may minimize signal ing overhead and the quantity of information passed to the base station device.
  • the network node device 200 and the base station devices 210A-210B may store the same mobility event map information.
  • the transmitting of the at least a portion of the generated or modified mobility event map information may be performed at net work deployment.
  • the mobility event map information may be passed just once, at the deployment of the network.
  • a new object may be introduced for this purpose. This example embodiment may allow lower com plexity.
  • the transmit ting of the at least a portion of the generated or modified mobility event map information may be performed in response to a request from one or more of the base station devices 210A-210B.
  • the base sta tion devices 210A-210B may request e.g. the mo bility event map information of specific events after observing an increase in the statistical distribution of a specific MRO event. For example, if many UEs suffer beam failure, the gNBs may request for mobility event map information optimized for such an event.
  • the trans mitting of the at least a portion of the generated or modified mobility event map information may be performed in accordance with a timer.
  • the network node device 200 may e.g. pass all the mobility event map information to the base station devices 210A- 210B (gNBs) after a configured timer. After the expira tion of this timer, the validity of the mobility event map information may expire. In this example embodiment, the mobility event map information may need to be built periodically.
  • the timer can be configured e.g. per event type, i.e. per mobility event map information type.
  • FIG. 2B is a block diagram of a base station device 210A for wireless communication in a radio access network 250, in accordance with an example embodiment.
  • a “base station device” refers to a device suit able for providing an air interface for client devices to connect to a wireless network via wireless transmis sions), such as a 5G base station or gNB.
  • the base station device 210A of Fig. 2B may include e.g. the base station device 210A of Fig. 1.
  • the base station device 210A comprises one or more processors 212A, and one or more memories 214A that comprise computer program code.
  • the base station device 210A may also include a transceiver 215A, as well as other elements not shown in FIG. 2B.
  • the base station device 210A is de picted to include only one processor 212A, the base station device 210A may include more processors.
  • the memory 214A is capable of storing in structions, such as an operating system and/or various applications.
  • the processor 212A is capable of executing the stored instructions.
  • the processor 212A may be embodied as a multi-core proces sor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors.
  • the processor 212A may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated cir cuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor 212A may be configured to exe cute hard-coded functionality.
  • the processor 212A is embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 212A to perform the algorithms and/or operations described herein when the instructions are executed.
  • the memory 214A may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices.
  • the memory 214A may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
  • the at least one memory 214A and the computer program code are configured to, with the at least one processor 212A, cause the base station device 210A to perform receiving, from the network node device 200, at least a portion of the mobility event map information for assisting in the processing of subsequent handover events in the radio access network 250.
  • the mo bility event map information depicts previous mobility events in associated client device positions in the ra dio access network 250.
  • the at least one memory 214A and the computer program code are further configured to, with the at least one processor 212A, cause the base station device 210A to perform tracking the movement of a client device 220A in a radio access network cell served by the base station device 210A.
  • the at least one memory 214A and the computer program code are further configured to, with the at least one processor 212A, cause the base station device 210A to perform receiving signal strength information from the tracked client device 220A.
  • the at least one memory 214A and the computer program code are further configured to, with the at least one processor 212A, cause the base station device 210A to perform configur ing a customized handover event for the client device 220A based on the received signal strength information and the received at least the portion of the mobility event map information.
  • the triggering signal strength change may comprise signal strength of the base station device 210A decreasing and signal strength of a neigh boring base station device 220B increasing.
  • the triggering mobility event may comprise a handover occurring too early
  • the cus tomized handover event for the client device 220A may comprise a safety threshold added to a handover event triggered when a neighboring cell becomes better than the serving cell by an offset.
  • the handover event trig gered when a neighboring cell becomes better than the serving cell by an offset may comprise a long-term evo lution LTE A3 event.
  • the triggering mobility event may comprise a handover occurring too late
  • the customized handover event for the client device 220A may comprise a handover event configured to trigger faster than default
  • a gNB tracks the UE movement through the cell, and the UE reports the signal strength from the servicing gNB and the neigh boring gNBs. If the serving gNB signal strength is de creasing and the neighboring gNB signal strength is in creasing, and the UE is approaching an area where RLFs occurred, then the gNB builds and configures to the UE a custom HO event, proactively. This custom HO event may prevent the UE from an RLF.
  • examples of custom HO events include:
  • Diagram 400 of Fig. 4 illustrates a customized new handover event built starting from learning too late handover events and exploiting RSRP measurements.
  • the measured RSRP 401 from the source gNB is decreasing and the measured RSRP 402 from the target gNB is increasing.
  • the measured RSRP 401 and the measured RSRP 402 intersect at point 404.
  • a conventional LTE A3 event would trigger at point 404.
  • a conventional handover event would occur later, e.g. at point 405, and thus it would be a "too late HO", i.e. a failure.
  • at least some of the embodiments described herein allow the net work to have access to statistics of such previous events so that a customized HO event may be built at a timestamp earlier (e.g. at point 403) than the usual A3 event at point 404.
  • custom HO events are not limited to be optimized only by the adaptation of the signal strength threshold for the triggering or time or position, but instead further embodiments may be implemented by taking into consideration e.g. UE type, traffic type, mobility profile, trajectory, speed, etc.
  • base station device 210A directly result from the functionalities and parameters of the network node device 200 and thus are not repeated here.
  • FIG. 2C is a block diagram of the client device 220A for wireless communication, in accordance with an example embodiment.
  • the client device 220A may comprise a client device for wireless communication, such as any of various types of devices used directly by an end user entity and capable of com munication in a wireless network.
  • Such devices include but are not limited to smartphones, tablet computers, smart watches, lap top computers, Internet-of-Things (IoT) devices, etc.
  • the client device 220A of Fig. 2C may include e.g. the client device 220A of Fig. 1.
  • the client device 220A comprises one or more processors 222A, and one or more memories 224A that comprise computer program code.
  • the client device 220A may also include a transceiver 225A, as well as other elements not shown in FIG. 2C.
  • the client device 220A is depicted to include only one processor 222A, the client device 220A may include more processors.
  • the memory 224A is capable of storing instructions, such as an operating system and/or various applications.
  • the processor 222A is capable of executing the stored instructions.
  • the processor 222A may be embodied as a multi-core proces sor, a single core processor, or a combination of one or more multi-core processors and one or more single core processors.
  • the processor 222A may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated cir cuit (ASIC), a field programmable gate array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like.
  • the processor 222A may be configured to exe cute hard-coded functionality.
  • the processor 222A is embodied as an executor of software instructions, wherein the instructions may specifically configure the processor 222A to perform the algorithms and/or operations described herein when the instructions are executed.
  • the memory 224A may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices.
  • the memory 224A may be embodied as semiconductor memories (such as mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.).
  • the at least one memory 224A and the computer program code are configured to, with the at least one processor 222A, cause the client device 220A to perform determining position information of the client device 220A.
  • the position information of the client device 220A may comprise the position of the client device 220A calculated by the client device 220A based on one or more positioning reference signal trans mission points.
  • the position information of the client device 220A may comprise uplink position ing reference signal symbols, and information about at least one of downlink positioning reference signal meas urements, a cell identifier, a beam identifier, or a timing advance.
  • the at least one memory 224A and the computer program code are further configured to, with the at least one processor 222A, cause the client device 220A to perform transmitting the determined position infor mation of the client device 220A to a network node device 200 for assisting in the processing of subsequent hand over events in the radio access network 250 associated with the network node device 200.
  • client device 220A directly result from the functionalities and parameters of the network node device 200 and the base station device 210A, and thus are not repeated here.
  • Fig. 3 illustrates an example signaling diagram of a method 300 of handover management, in accordance with an example embodiment.
  • the network node device 200 obtains mobility event information for the one or more client devices 220A-220C.
  • Each piece of the mobility event information comprises a first part indicating a mobility event associated with a client device of the one or more client devices 220A-220C, and a second part indicating the position of this client device at the time of the mobility event. At least the second part may be based on the position information received at oper ation 302.
  • the network node device 200 generates mobility event map information for assisting in the processing of subsequent handover events in the ra dio access network 250 associated with the network node device 200.
  • the mobility event map information depicts the indicated mobility events in the associated client device positions in the radio access network 250.
  • the network node device 200 may modify the generated mobility event map information by indicating a trigger area around one or more of the client device positions associated with the mobility events.
  • the network node device 200 transmits at least a portion of the generated or modi fied mobility event map information to one or more base station devices 210A-210B in the radio access network 250. Also at operation 306, the one or more base station devices 210A-210B receive the at least a portion of the generated or modified mobility event map information.
  • the base station device 210A tracks the movement of a client device 220A in a radio access network cell served by the base station device 210A.
  • the base station device 210A receives signal strength information from the tracked client device 220A.
  • the base station device 210A configures a customized handover event for the client device 220A based on the received signal strength information and the received at least the portion of the mobility event map information.
  • the method 300 may be performed by the network node device 200 of Fig. 2A (or Fig. 1), the base station device 210A of Fig. 2B (or Fig. 1), and the client device 220A of Fig. 2C (or Fig. 1). Further features of the method 300 directly result from the functionalities and parameters of the network node device 200, the base station device 210A, and the client device 220A and thus are not repeated here.
  • the method 300 can be performed by computer program (s).
  • At least some of the embodiments described herein may allow triggering custom handover events by learning from MRO events.
  • at least some of the embodiments described herein may allow triggering handover events in a more proactive way by exploiting, in addition to the handover events, mobility events ex perienced by a set of training UEs correlated with lo cation to optimize resource utilization and user expe rience.
  • at least some of the embod iments described herein may allow triggering handover events proactively via correlation of radio link failure events to the position of the UE.
  • At least some of the embodiments described herein may allow collecting HO and RLF data to inform involved network nodes and to improve the HO parameters to be used for the next HO events.
  • the collection of the position of the HO events used for learning involves: in the learning phase, the MRO event is collected at position (x,y) for RSRP value z.
  • the network builds a custom HO event for position (x+a, y+b).
  • the embodiments allow improving the traditional HO event (in which the network would ask for RSRP meas urements and if they fit the HO event description, the HO would be triggered), but instead when the UE reaches the area of the new HO event, the network triggers the HO.
  • the functionality described herein can be per formed, at least in part, by one or more computer program product components such as software components.
  • the network node device 200, the base station device 210A, and/or the client device 220A comprise a processor configured by the program code when executed to execute the embodiments of the operations and functionality described.
  • the functionality described herein can be per formed, at least in part, by one or more hardware logic components.
  • illus trative types of hardware logic components include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and Graphics Processing Units (GPUs).
  • FPGAs Field-programmable Gate Arrays
  • ASICs Program-specific Integrated Circuits
  • ASSPs Program-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • GPUs Graphics Processing Units

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des dispositifs, des procédés et des produits de programme informatique pour une gestion de transfert intercellulaire. Un dispositif de nœud de réseau obtient des informations d'événement de mobilité pour un ou plusieurs dispositifs clients. Chacune des informations d'événement de mobilité comprend une première partie indiquant un événement de mobilité associé à un dispositif client et une seconde partie indiquant la position du dispositif client au moment de l'événement de transfert intercellulaire. Sur la base des informations d'événement de mobilité obtenues, le dispositif de nœud de réseau génère des informations de carte d'événement de mobilité pour aider au traitement d'événements de transfert intercellulaire ultérieurs dans un réseau d'accès radio associé au dispositif de nœud de réseau. Les informations de carte d'événement de mobilité représentent les événements de mobilité indiqués dans les positions de dispositif client associées dans le réseau d'accès radio.
PCT/EP2019/076066 2019-09-26 2019-09-26 Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés WO2021058103A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/076066 WO2021058103A1 (fr) 2019-09-26 2019-09-26 Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2019/076066 WO2021058103A1 (fr) 2019-09-26 2019-09-26 Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés

Publications (1)

Publication Number Publication Date
WO2021058103A1 true WO2021058103A1 (fr) 2021-04-01

Family

ID=68136356

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/076066 WO2021058103A1 (fr) 2019-09-26 2019-09-26 Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés

Country Status (1)

Country Link
WO (1) WO2021058103A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022124972A1 (fr) * 2020-12-11 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'informations de rétroaction d'événement de mobilité

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013034191A1 (fr) * 2011-09-09 2013-03-14 Nokia Siemens Networks Oy Carte de configuration de mesure pour le signalement d'événements de mesure dans un réseau de communication cellulaire
US20130150023A1 (en) * 2011-12-09 2013-06-13 Electronics And Telecommunications Research Institute Handover controlling method, operating method of wireless communication terminal, and station
GB2511860A (en) * 2013-03-15 2014-09-17 Vodafone Ip Licensing Ltd A Method and System of Providing Data Service According to a User's Future Location
US20150045028A1 (en) * 2013-08-09 2015-02-12 Qualcomm Incorporated User equipment specific mobility optimization and improved performance metrics for improving handover performance
US20180098258A1 (en) * 2016-10-03 2018-04-05 Qualcomm Incorporated Inter-rat mobility measurements and operations to support ue connectivity
WO2019101334A1 (fr) * 2017-11-24 2019-05-31 Huawei Technologies Co., Ltd. Nœuds d'accès au réseau et procédés associés

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013034191A1 (fr) * 2011-09-09 2013-03-14 Nokia Siemens Networks Oy Carte de configuration de mesure pour le signalement d'événements de mesure dans un réseau de communication cellulaire
US20130150023A1 (en) * 2011-12-09 2013-06-13 Electronics And Telecommunications Research Institute Handover controlling method, operating method of wireless communication terminal, and station
GB2511860A (en) * 2013-03-15 2014-09-17 Vodafone Ip Licensing Ltd A Method and System of Providing Data Service According to a User's Future Location
US20150045028A1 (en) * 2013-08-09 2015-02-12 Qualcomm Incorporated User equipment specific mobility optimization and improved performance metrics for improving handover performance
US20180098258A1 (en) * 2016-10-03 2018-04-05 Qualcomm Incorporated Inter-rat mobility measurements and operations to support ue connectivity
WO2019101334A1 (fr) * 2017-11-24 2019-05-31 Huawei Technologies Co., Ltd. Nœuds d'accès au réseau et procédés associés

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022124972A1 (fr) * 2020-12-11 2022-06-16 Telefonaktiebolaget Lm Ericsson (Publ) Gestion d'informations de rétroaction d'événement de mobilité

Similar Documents

Publication Publication Date Title
US10912143B2 (en) Method and apparatus for transmitting a handover report and an RLF report
CN110958630B (zh) 一种测量方法及设备
CN102685788B (zh) 发现无线网络问题的方法、装置及系统
EP2340671B1 (fr) Partage d informations de type de cellule entre des stations de base voisines
CN103945469B (zh) 一种确定目标小区的方法及设备
EP2326122A1 (fr) Procédé et dispositif pour déterminer un dispositif de télécommunication sans fil vers lequel doit être effectué un transfert de terminal mobile
US6577616B1 (en) Systems and methods for implementing large CDMA cell sizes
US9143992B2 (en) Handover method of terminal, and base station thereof
US9924453B2 (en) Method and device for determining cell identifier
US10257755B2 (en) Handover of a user equipment having offloaded user data traffic between two small cells controlled by different macro cells
CN105491625B (zh) 无线通信中切换接入点的方法、网络控制节点和用户设备
WO2014169880A1 (fr) Procédé de commutation de cellule, station de base et support de stockage informatique
CN107852650B (zh) 相邻小区测量方法、基站和终端设备
CN106851750B (zh) 一种通信方法、基站及系统
EP2957060A1 (fr) Station de base radio et procédé réalisé sur celle-ci pour envoyer une configuration d'alignement temporel à un équipement d'utilisateur
US10292084B2 (en) Communication system and control method
WO2021058103A1 (fr) Gestion de transfert intercellulaire par l'intermédiaire d'un apprentissage à partir d'événements de mobilité passés
WO2015039625A1 (fr) Procédé, système et équipement de signalement d'informations de mobiles
CN104519512A (zh) 一种自动邻区关系小区检测方法
US9736811B1 (en) Determining a customized paging area
CN103916873B (zh) 一种现网补站的邻区配置方法和装置
CN107295601B (zh) 一种多运营商核心网中接入核心网的方法及装置
CN106792934B (zh) 一种切换方法及装置
CN110049577B (zh) 一种无线资源控制rrc重建立的方法及装置
US11647447B2 (en) Candidate link locating by a wireless terminal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19782517

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19782517

Country of ref document: EP

Kind code of ref document: A1