EP3251406B1 - Transfert dans un scenario à grande vitesse - Google Patents

Transfert dans un scenario à grande vitesse Download PDF

Info

Publication number
EP3251406B1
EP3251406B1 EP15703753.2A EP15703753A EP3251406B1 EP 3251406 B1 EP3251406 B1 EP 3251406B1 EP 15703753 A EP15703753 A EP 15703753A EP 3251406 B1 EP3251406 B1 EP 3251406B1
Authority
EP
European Patent Office
Prior art keywords
handover
target cell
cell
predetermined target
network node
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.)
Active
Application number
EP15703753.2A
Other languages
German (de)
English (en)
Other versions
EP3251406A1 (fr
Inventor
Joakim Axmon
Peter Alriksson
Christopher Callender
Muhammad Kazmi
Torgny Palenius
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP3251406A1 publication Critical patent/EP3251406A1/fr
Application granted granted Critical
Publication of EP3251406B1 publication Critical patent/EP3251406B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/04—Reselecting a cell layer in multi-layered cells
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
    • 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/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • 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
    • 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/302—Reselection being triggered by specific parameters by measured or perceived connection quality data due to low signal strength
    • 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
    • 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
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks

Definitions

  • Embodiments herein relate to a wireless communication system and more specifically to a network node and a user equipment for controlling handover in such a system.
  • Wireless communication systems i.e. systems that provide communication services to wireless communication devices such as mobile phones, smartphones etc. (often denoted by UE that is short for user equipment), have evolved during the last decade into systems that must utilize the radio spectrum in the most efficient manner possible.
  • a reason for this is the ever increasing demand for high speed data communication capabilities in terms of, e.g., bitrate and to provide these capabilities at any given time, at any geographical location and also in scenarios where the wireless communication device is moving at a high speed, e.g., on board a high speed train.
  • the high speed scenario may further comprise of mission critical, MC, operations involving high speed vehicles in the air.
  • Example of MC operation is Air Ground Air communications, A2G, where high speed vehicles may comprise of helicopters and planes containing wireless terminals.
  • the A2G vehicles may be served by high speed radio nodes, also known as A2G base stations, A2G eNode B etc.
  • the speed of helicopter and planes may be in the order of 200-300 km/h
  • High speed movement of the UE may also lead to significant Doppler shifts of the received radio signals.
  • a Doppler shift forces the UE to increase its demodulation frequency when moving towards a cell (i.e. moving towards an antenna that defines a radio lobe of the cell), and decrease demodulation frequency when moving away from a cell, in order to maintain an acceptable receiver performance.
  • an UE 101 is on a high speed train 103 on a railway track 104, connected to and moving away from cell A2 105 and quickly needs to detect cell B1 107 towards which the UE 101 is moving with a velocity v UE 109 of the train.
  • an antenna 111, 113 of a cell site can be as close as 2m from the railway track 104, mainly motivated by that the wireless communication network would be integrated with the high-speed railway infrastructure.
  • handover to a new primary cell, PCell, configuration of a new secondary cell, SCell, and configuration and activation of a new primary secondary cell, PSCell is usually based on measurement reports from the UE, where the UE has been configured by the network node to send measurement reports periodically, at particular events, or a combination thereof.
  • measurement reports typically contain physical cell identity, reference signal strength, RSRP, and reference signal quality, RSRQ, of the detected cells.
  • Handovers can also be blind (i.e. no measurements performed on target carrier and/or cell) based on the network node having knowledge about coverage on other carriers and location of the UE. An example of this can be found in US patent number 8892103 entitled "Methods and nodes supporting cell change".
  • 3GPP TS 36.331 V11.9.0 and 3GPP TS 36.321 V11.5.0 Existing core requirements on interruption time are stated in 3GPP TS 36.133 V11.10.0. (Those as well as other referenced 3GPP specifications can be found at www.3gpp.org/ftp/Specs/.)
  • the latency at a handover to a known (measured) PCell counted from reception of the handover command at the UE antenna until the UE carries out contention-free random access towards the target cell can be up to 65ms comprising 15ms radio resource control, RRC, procedure delay, 20ms preparation time for the UE, and up to 30ms latency for next physical random access channel, PRACH, occasion.
  • RRC radio resource control
  • PRACH next physical random access channel
  • One of the purposes with random access is to configure the UE with an appropriate timing advance value such that uplink transmissions by the UE are aligned with the subframe timing when received by the network node.
  • Each random access attempt typically takes 20ms hence in case the UE has to repeat the random access due to not getting response from the network node the time will be prolonged, but as a general figure one can assume 85ms in total until the UE can resume communication in the target cell provided that the first attempt of random access is successful.
  • the preparation time is needed, e.g., for stopping processing and tearing down data structures and data memory associated with the source cell to release processing, memory and radio resources so they are available for the configuration to be used in the target cell.
  • the reconfiguration may in general require re-partitioning of the data memories due to other bandwidth used in target cell, loading of new program code to support other transmission modes or radio access technology than in source cell.
  • the document WO 2013/177778 A1 is considered the closest prior art. The preambles of the independent claims are based on this document.
  • the document discloses a method, an apparatus and a corresponding computer program product for autonomous cell change by user equipment in a network.
  • One method determines at least one cell in a network sharing context of at least one user equipment with at least one other cell within the network, and then creates at least one measurement configuration being used by the at least one user equipment, wherein the at least one measurement configuration indicates at least to the at least one user equipment that it can decide whether to perform cell change without transmitting back its measurement report to its serving cell. Then the method further transmits the created at least one measurement configuration to the at least one user equipment.
  • an object of the present disclosure is to overcome or at least mitigate at least some of the drawbacks related to prior art in handling radio communication with wireless communication devices.
  • the network node maintains a source cell in the network, to which source cell a user equipment, UE, is connected.
  • the method comprises:
  • the method further comprises:
  • the present disclosure introduces a new kind of handover where the UE is pre-configured by the network node of the source cell with one or more target cells and associated conditions to be fulfilled for the UE to autonomously decide when to execute the handover.
  • the UE may be pre-configured while in good radio conditions, being connected to the source cell, and hence the UE does not risk going out of source cell coverage before being handed over to a target cell.
  • the target cell is also pre-configured by the network node in the source cell at an earlier time than in prior art procedures.
  • the source cell provides information to the target cell on UE context necessary to execute the handover, and the target cell provides configuration information to the network node of source cell, which is indicated to the UE enabling the UE to become pre-configured while the UE is still in good radio conditions in connection with the network node of the source cell.
  • the target cell has been made aware to expect an inbound handover from the UE at some point in the future, and the target cell has all necessary information to maintain the connection when this occurs, and correspondingly the UE has all necessary information to make a connection to the target cell autonomously when the trigger condition occurs.
  • the at least one event triggering condition is configured for triggering any event of:
  • the method comprises:
  • the method comprises:
  • the object of the present disclosure is also achieved in a second aspect by a method, performed by a a user equipment, UE, in a radio access network, RAN, where a network node maintains a source cell in the RAN, to which source cell the UE is connected.
  • the method comprises:
  • the method further comprises:
  • the at least one event triggering condition is configured for triggering any event of:
  • the reception of the handover configuration data comprises reception of at least one timing advance, TA, value for use in the at least one predetermined target cell, and the method comprises:
  • the reception of the handover configuration data comprises reception of at least one system frame number, SFN, offset between a SFN associated with the source cell and a SFN associated with the at least one predetermined target cell, and the method comprises:
  • the network node comprises input/output circuitry, a processor and a memory.
  • the memory contains instructions executable by the processor whereby the network node is operative to:
  • the network node is further operative to;
  • a user equipment comprising radio frequency, RF, circuitry, a processor and a memory.
  • the memory contains instructions executable by said processor whereby the UE is operative to:
  • the user equipment is further operative to:
  • carrier comprising computer programs according to the summarized aspects above, wherein the carriers are one of an electronic signal, an optical signal, a radio signal and a computer readable storage medium.
  • FIGs 2a -b schematically illustrate drawbacks associated with prior art handover procedures for 300m inter-site distance.
  • an antenna node 211 defines a cell 212 and an antenna node 213 defines a cell 214 and the inter-site distance is defined by the distance between antenna node 211 and antenna node 213.
  • a UE 201 is onboard a westbound train 215 and a UE 203 is onboard an eastbound train 217.
  • the diagrams in figure 2b are aligned with figure 2a such that the east-west distance markers in figure 2b are lined up with corresponding points in figure 2a .
  • antenna node 211 is located at distance marker 0m and antenna node 213 is located at distance marker 300m.
  • the SINR For a UE in RRC connected mode (in relation to a source cell) to detect an intra-frequency neighbor cell the SINR must be above -6dB.
  • the UE 201 on the westbound train 215, which is connected mode in relation to the cell 214 it is not until the UE 201 is about 100m away from the source cell 214 (i.e. at distance marker 200m in the upper diagram of figure 2b ) that the SINR of a target cell (which in the scenario of figure 2a is cell 212) comes into the range where the UE 201 shall be able to detect it. After approximately 100m further in the westward direction (i.e.
  • a handover zone 220 is defined as being between these two distance markers 100m east of the antenna node 211 and 100m west of antenna node 213.
  • the UE 201 will be within this handover zone 220 for about 700ms when travelling at 500km/h, while the cell detection requirements in 3GPP TS 36.133 state that the UE shall be able to detect and report a new neighbor cell that fulfills the side conditions within 800ms.
  • the scenario is further complicated by that there may be several kHz frequency offset between source and target cells due to Doppler shifts with opposite signs.
  • UE demodulation performance degrades significantly when the SINR decreases, and already at SINR -4dB it becomes challenging for a legacy UE to receive a handover command from a source cell.
  • the available time for handing off the UE i.e. a procedure including: UE detecting neighbor cell, UE reporting neighbor cell, network node reconfiguring the UE to handover to target cell
  • the available time for handing off the UE is considerably less than assumed in the standard, and there is a significant risk that the UE, once it has reported the target cell, cannot receive the handover command from the source cell due to high interference.
  • source cell may also be denoted serving cell, primary cell, PCell, primary secondary cell, PSCell, current cell etc.
  • target cell may be denoted neighbour cell, new source or serving cell, non-serving cell etc.
  • the UE may be served by single source cell or in multiple source cells (e.g. in scenarios involving carrier aggregation, dual connectivity etc).
  • network node and “UE” are used.
  • network nodes include: antenna node, Node B, enhanced NodeB, e-NodeB, radio network controller, RNC, base station, base station controller, BSC, access point, base transceiver station, BTS, remote radio head, RRH, remote radio unit, RRU, relay, core network node etc.
  • UE may be any type of wireless device capable of communicating with a network node and/or with another wireless device over a wireless link.
  • Non-limiting examples of UE are mobile terminal, laptop, USB device, embedded device, machine type communication, MTC, or machine-to-machine, M2M, capable, device-to-device, D2D, capable UE aka proximity service, ProSe, UE etc.
  • Figure 3 illustrates a network 300 and where a UE 306 is moving in a direction 314 along a path 313, e.g. onboard a high-speed train as discussed above.
  • the UE is in connection with a network node 301 in a source cell 310 that is maintained by the network node 301.
  • Figure 3 also shows a network node 303 that maintains cells 320, 321 and 322.
  • cells 320,321 and 322 may become target cells for the UE 306 in a handover from the source cell 310.
  • Embodiments of a method in the network node 301 will be described, referring to figure 4a , in terms of a number of steps or actions.
  • the network node 301 receives, from at least one cell in the network 300, data that comprises information regarding UE handover, whereby the at least one cell in the network from which the data is received defines at least one predetermined target cell to which a UE 306 is to perform handover.
  • the data may be received via the network node 303 from any of cells 320, 321, 322.
  • the network node 301 provides, to the UE 306, handover configuration data comprising the data received from the at least one cell and comprising at least one event triggering condition that defines radio signal measurement conditions for use by the UE when performing an autonomous decision to initiate the handover.
  • the network node 301 provides, to the at least one predetermined target cell, context information associated with the UE 306 for preparing the target cell for a handover procedure initiated by the UE.
  • the present disclosure introduces a new kind of handover where the UE is pre-configured by the network node of the source cell with one or more target cells and associated conditions to be fulfilled for the UE to autonomously decide when to execute the handover.
  • the UE may be pre-configured while in good radio conditions, being connected to the source cell, and hence the UE does not risk going out of source cell coverage before being handed over to a target cell.
  • the target cell is also pre-configured by the network node in the source cell at an earlier time than in prior art procedures.
  • the source cell provides information to the target cell on UE context necessary to execute the handover, and the target cell provides configuration information to the network node of source cell, which is indicated to the UE enabling the UE to become pre-configured while the UE is still in good radio conditions in connection with the network node of the source cell.
  • the target cell has been made aware to expect an inbound handover from the UE at some point in the future, and the target cell has all necessary information to maintain the connection when this occurs, and correspondingly the UE has all necessary information to make a connection to the target cell autonomously when the trigger condition occurs.
  • the at least one event triggering condition that is provided to the UE 306 in action 402 may be configured for triggering any event of:
  • the event AX may be seen as a preconfigured target PCell becoming offset better than serving PCell, remembering that here and in all other parts of the present disclosure, "source cell” may also be denoted serving cell, primary cell, PCell, primary secondary cell, PSCell, current cell etc. Similarly, “target cell” may be denoted neighbour cell, new source or serving cell, non-serving cell etc.
  • the UE shall for associated preconfigured target PCell:
  • Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell
  • Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Mp is the measurement result of the PCell, not taking into account any offsets.
  • offsetFreq the frequency specific offset of the primary frequency (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the primary frequency).
  • Ocp is the cell specific offset of the PCell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the primary frequency), and is set to zero if not configured for the PCell.
  • Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
  • Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
  • Ocn , Ofp , Ocp , Hys , Off are expressed in dB.
  • the event AY may be seen as a PCell becomes worse than thresh1 and preconfigured PCell becomes better than thresh2. That is: The UE shall for associated preconfigured PCell:
  • Mp is the measurement result of the PCell, not taking into account any offsets.
  • Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
  • offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell
  • Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
  • Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
  • Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigEUTRA for this event).
  • Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigEUTRA for this event).
  • Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
  • Thresh1 is expressed in the same unit as Mp.
  • Thresh2 is expressed in the same unit as Mn.
  • Some embodiments involve handover configuration data that comprises a timer value that specifies a time period during which the UE is allowed to initiate the handover procedure. These are illustrated in figure 4b :
  • the network node 301 provides the timer value to the UE 306.
  • a timer is started, using the timer value.
  • the network node 301 provides, to the at least one predetermined target cell, if the UE has not initiated a handover procedure prior to the timer expiring, information that disables the UE from being handed over to the at least one predetermined target cell.
  • the provision of the timer value to the UE in action 412 is conditioned on a mobility profile as follows.
  • the network node 301 determines a mobility profile for the UE, the mobility profile comprising at least one movement criterion associated with the UE.
  • the network node 301 sets the timer value based on the at least one movement criterion.
  • the timer value to be applied by the UE 306 upon having decoded e.g., a RRC message carrying the handover configuration data may be provided. If the UE 306 has not initiated the handover before the timer expires it is no longer granted to do the handover autonomously and resources in target cell(s) may, e.g., be de-allocated by the source cell.
  • the timer value may be selected by the network node based on UE mobility profile (e.g. UE trail, position, UE velocity, Doppler frequency, change in Doppler frequency, direction of motion, acceleration or change of velocity etc.) and/or knowledge about the infrastructure, e.g., whether UEs are bound to follow a railway track.
  • one additional timer value that overrides the standardized value for radio link failure may be provided by the network.
  • the UE shall not initiate reestablishment before this timer has expired.
  • figure 4c Some embodiments are illustrated in figure 4c , comprising:
  • the network node 301 determines a mobility profile for the UE, the mobility profile comprising at least one movement criterion associated with the UE.
  • the provision of the handover configuration data to the UE is made conditional of the at least one movement criterion.
  • the network node provides the mobility profile to the UE.
  • the network node may configure the UE 306 with the handover configuration information provided that the UE mobility profile as determined by the network node meets one or more criteria.
  • the network node can determine the UE mobility profile based on signals received from the UE and/or UE mobility profile information transmitted by the UE to the network node.
  • the at least one movement criterion associated with the UE comprises any of:
  • the criteria for the UE mobility profile can be predefined or the UE may be configured by the network node.
  • the criteria related to UE mobility profile for triggering the handover are:
  • the criteria for the UE mobility profile may also be associated with a particular deployment scenario related to high speed train environment.
  • the autonomous handover procedure may be applied only when the UE operates in a network deployed for high speed train environment.
  • the UE 306 may determine that it is operating in high speed train environment based on explicit information received from the network node e.g. indicator sent to the UE 306 that cells on certain carrier, f1, belong to high speed train environment. Therefore the UE 306 may execute the new handover procedure only if the target cell operates in high speed train environment as indicated by an indicator signalled by the network node 301.
  • figure 4d comprising:
  • the network node 301 determines a position of the UE 306.
  • the network node 301 determines the at least one predetermined target cell based on a preconfigured set of likely candidate cells depending on the determined position of the UE 306.
  • the UE 306 may be prevented from going out of coverage and thereby losing connection due to radio link failure when the source cell coverage suddenly is lost, either due to the share speed of the UE 306, or due to the UE 306 being located in an urban environment for instance passing a corner by which the UE 306 suddenly might get into line-of-sight to a strong intra-frequency neighbour cell by which the serving cell might drown in interference, with radio link failure as result.
  • the serving cell may configure one or more likely candidate cells for handover, and preconfigure the UE with those.
  • figure 4e comprising:
  • the network node 301 receives, from one target cell among the at least one predetermined target cells, a notification that the UE 306 has performed a handover procedure associated with the one target cell.
  • the network node 301 releases UE-specific resources associated with the source cell and releasing UE-specific resources associated with any predetermined target cell with which the UE has not performed a handover procedure.
  • the UE 306 autonomously may carry out random access and/or transmit a scheduling requests in the target cell.
  • the target network node may notify the source network node, which then can release UE-specific resources both in the source cell and the remaining preconfigured target cells, should there be any.
  • a similar procedure may be applied in case the serving cell is lost.
  • figure 4f Some embodiments are illustrated in figure 4f , comprising:
  • the network node 301 provides, to the UE, an instruction not to apply discontinuous reception, DRX, or an instruction to apply a specific discontinuous reception, DRX, cycle.
  • the network node 301 controls scheduling of the UE such that a rate of reduction of amounts of data in data buffers in the UE is increased.
  • the network node 301 may reconfigure the UE 306 with a suitable DRX cycle (or non-DRX) when providing the handover configuration data, in order for the UE 306 to carry out cell detection quick enough for the scenario. For instance, in high-speed train scenarios it is desirable that the UE 306 measures as had it been non-DRX or DRX cycle length up to 40ms. Alternatively, when the UE 306 gets preconfigured with a target cell for doing possible handover to the target cell, it shall measure for instance according to non-DRX requirements or according to shorter DRX requirements (e.g. DRX cycle below 80ms).
  • the network node 301 may assume that the UE 306 even if configured in DRX starts operating in non-DRX or shorter DRX cycle from the instance the UE 306 is preconfigured with the target cell until the handover is executed.
  • the network node 301 may also adapt scheduling for the UE during this time when the UE 306 goes into non-DRX or shorter DRX. For example the network node 301 may schedule the UE 306 more frequently during this phase. This will allow the serving cell to empty the UE buffer and avoid the loss of data during a handover phase.
  • figure 4g comprising:
  • the network node 301 determines a range of positions of the UE 306 in relation to the source cell and the at least one predetermined target cell, the range of positions defining a range in which the handover procedure is to be performed.
  • the network node 301 provides, to the UE 306, based on the range of positions, data comprising at least one timing advance, TA, value for use in the at least one predetermined target cell.
  • the handover configuration data may carry information on timing advance to be applied in the target cell, where the timing advance is based on estimated range of UE positions where the handover is to be executed. This could be estimated by a network node (such as the serving or target eNB) in advance of the handover.
  • the UE position where handover is executed in turn depends e.g. on UE relative measurement accuracy, UE mobility profile (e.g. UE velocity), and acceptable UL timing tolerance (generally ⁇ 1-2 ⁇ s).
  • the timing advance may vary within 1 ⁇ s depending on UE position assuming equally strong cells and no handover measurement offset being used, whereas for larger inter-site distance it is bigger.
  • figure 4h Some embodiments are illustrated in figure 4h , comprising:
  • the network node 301 determines at least one system frame number, SFN, offset between a SFN associated with the source cell and a SFN associated with the at least one predetermined target cell,
  • the provision of the handover configuration data to the UE 306 in action 402 then comprises providing, to the UE, data comprising the at least one SFN offset for use in the at least one predetermined target cell.
  • the UE 306 uses the SFN in order to apply configurations for reporting, DRX, measurement gaps, sounding reference signal, SRS, hybrid automatic repeat request, HARQ, processing etc. Therefore according to legacy handover procedures the UE has to read the MIB to acquire SFN as part of the handover.
  • the handover configuration data may carry also an SFN offset between source and target cell(s), such that the UE 306 can skip the MIB reading and apply the cell-specific configurations some 20-30ms earlier than otherwise possible.
  • SFN offset between source and target cells is fixed.
  • SFN offset between the source and target cell(s) may drift with time and may be determined by network nodes.
  • figure 4i Some embodiments are illustrated in figure 4i , comprising:
  • the network node 301 receives, from the UE 306, capability information that the UE is capable of performing an autonomous decision to initiate a handover.
  • the provision of the handover configuration data to the UE in action 402 is then conditional of the received capability information.
  • the UE 306 supporting the use of handover configuration data as described herein may indicate that it is capable of handling the new handover procedure to the network node (e.g. base station, access point, MME etc).
  • the UE 306 may send this the capability report or message to the network node 301 autonomously or in response to a request (e.g. UE capability inquiry message) received from the network node 301.
  • the network node 301 may use the received UE capability message for one or more operations.
  • the network node 301 may configure the UE 306 with the handover configuration data only if the UE 306 supports such capability.
  • the network node 301 may also determine the UE mobility profile and configure the UE 306 with one or more thresholds or conditions related to the UE mobility profile for triggering the new handover procedure, e.g. UE speed, maximum Doppler frequency etc.
  • the UE 306 receives, from the network node 301, handover configuration data that comprises information regarding UE handover to at least one predetermined target cell to which the UE is to perform handover and at least one event triggering condition that defines radio signal measurement conditions for use by the UE when performing an autonomous decision to initiate the handover.
  • the UE 306 measures radio signals associated with the source cell and radio signals associated with the at least one predetermined target cell.
  • the UE 306 determines, based on the measuring of radio signals, an event according to the at least one event triggering condition.
  • the UE 306 performs, based on the determined event, an autonomous decision to initiate handover to the at least one predetermined target cell.
  • the at least one event triggering condition that is received by the UE 306 in action 501 may be configured for triggering any event of:
  • the event AX may be seen as a preconfigured target PCell becoming offset better than serving PCell and the event AY may be seen as a PCell becomes worse than thresh1 and preconfigured PCell becomes better than thresh2.
  • figure 5b Some embodiments are illustrated in figure 5b , comprising:
  • the UE 306 determines a mobility profile for the UE, the mobility profile comprising at least one movement criterion associated with the UE.
  • the determination of the mobility profile for the UE may comprise receiving the mobility profile from the network node 301.
  • the at least one movement criterion associated with the UE may comprise any of:
  • the performing of the autonomous decision to initiate handover is then conditional of the at least one movement criterion.
  • the network node may configure the UE with the handover configuration data but the UE may only initiate the handover provided that the UE mobility profile as determined by the UE meets one or more criteria.
  • the UE can determine the UE mobility profile based on signals received from the network node and/or UE mobility profile information transmitted by the network node to the UE.
  • figure 5c Some embodiments are illustrated in figure 5c , comprising:
  • the UE 306 receives, from the network node 301, an instruction not to apply discontinuous reception, DRX, or an instruction to apply a specific discontinuous reception, DRX, cycle.
  • the UE 306 operates in accordance with the received DRX instructions.
  • the network node 301 may reconfigure the UE 306 with a suitable DRX cycle (or non-DRX) when providing the handover configuration data, in order for the UE 306 to carry out cell detection quick enough for the scenario. For instance, in high-speed train scenarios it is desirable that the UE 306 measures as had it been non-DRX or DRX cycle length up to 40ms. Alternatively, when the UE 306 gets preconfigured with a target cell for doing possible handover to the target cell, it shall measure for instance according to non-DRX requirements or according to shorter DRX requirements (e.g. DRX cycle below 80ms).
  • the network node 301 may assume that the UE 306 even if configured in DRX starts operating in non-DRX or shorter DRX cycle from the instance the UE 306 is preconfigured with the target cell until the handover is executed.
  • the network node 301 may also adapt scheduling for the UE during this time when the UE 306 goes into non-DRX or shorter DRX. For example the network node 301 may schedule the UE 306 more frequently during this phase. This will allow the serving cell to empty the UE buffer and avoid the loss of data during a handover phase.
  • the reception of the handover configuration data comprises reception of at least one timing advance, TA, value for use in the at least one predetermined target cell.
  • the UE 306 performs a handover procedure with the at least one predetermined target cell, wherein the handover procedure comprises requesting a scheduling grant without performing a random access, RA, procedure.
  • the UE 306 when a target cell TA value is provided to the UE 306, the UE 306 can bypass a random access procedure and immediately request a scheduling grant. Thereby the handover procedure as such can be significantly shortened since the random access part of it may take up to 50ms even if the first attempt is successful. Moreover, in case no timing advance is provided to the UE 306, the UE 306 may carry out contention-free random access to the preconfigured target cell so as to acquire the appropriate timing advance to apply in a way similar to how it is done in the legacy handover procedure.
  • the reception of the handover configuration data comprises reception of at least one system frame number, SFN, offset between a SFN associated with the source cell and a SFN associated with the at least one predetermined target cell.
  • the UE 306 performs a handover procedure with the at least one predetermined target cell, wherein the handover procedure comprises requesting a scheduling grant without reading a master information block, MIB, associated the at least one predetermined target cell.
  • the handover procedure comprises requesting a scheduling grant without reading a master information block, MIB, associated the at least one predetermined target cell.
  • the UE 306 uses the SFN in order to apply configurations for reporting, DRX, measurement gaps, sounding reference signal, SRS, hybrid automatic repeat request, HARQ, processing etc. Therefore according to legacy handover procedures the UE has to read the MIB to acquire SFN as part of the handover.
  • the handover configuration data may carry also an SFN offset between source and target cell(s), such that the UE 306 can skip the MIB reading and apply the cell-specific configurations some 20-30ms earlier than otherwise possible.
  • SFN offset between source and target cells is fixed.
  • SFN offset between the source and target cell(s) may drift with time and may be determined by network nodes.
  • the UE may acquire the SFN of the preconfigured target cell similar to how it is done in a legacy handover procedure.
  • figure 5f Some embodiments are illustrated in figure 5f , comprising:
  • the UE 306 provides, to the network node 301, capability information that the UE is capable of performing an autonomous decision to initiate a handover.
  • the UE 306 supporting the use of handover configuration data as described herein may indicate that it is capable of handling the new handover procedure to the network node (e.g. base station, access point, MME etc).
  • the UE 306 may send this the capability report or message to the network node 301 autonomously or in response to a request (e.g. UE capability inquiry message) received from the network node 301.
  • the network node 301 may use the received UE capability message for one or more operations.
  • the network node 301 may configure the UE 306 with the handover configuration data only if the UE 306 supports such capability.
  • the network node 301 may also determine the UE mobility profile and configure the UE 306 with one or more thresholds or conditions related to the UE mobility profile for triggering the new handover procedure, e.g. UE speed, maximum Doppler frequency etc.
  • figure 5g comprising:
  • the UE 306 receives, from the network node 301, a timer value.
  • the UE 306 starts a timer using the timer value.
  • the UE 306 initiates, if not a handover has occurred (as checked in action 562) before the timer has expired (as checked in action 563), a reestablishment procedure in action 564.
  • the timer value to be applied by the UE 306 upon having decoded e.g., a RRC message carrying the handover configuration data may be provided. If the UE 306 has not initiated the handover before the timer expires it is no longer granted to do the handover autonomously and resources in target cell(s) may, e.g., be de-allocated by the source cell.
  • the timer value may be selected by the network node based on UE mobility profile (e.g. UE trail, position, UE velocity, Doppler frequency, change in Doppler frequency, direction of motion, acceleration or change of velocity etc.) and/or knowledge about the infrastructure, e.g., whether UEs are bound to follow a railway track.
  • one additional timer value that overrides the standardized value for radio link failure may be provided by the network.
  • the UE shall not initiate reestablishment before this timer has expired.
  • FIG 6 illustrates parts of a 3GPP long term evolution, LTE, wireless network 600 in which the embodiments described herein may be realized.
  • Base stations enhanced NodeB, eNodeB or eNB
  • eNodeB enhanced NodeB
  • eNodeB enhanced NodeB
  • eNB enhanced NodeB
  • the base stations 606, 607 and 608 are connected to a mobility management entity, MME, 610, which keeps information about UEs (e.g. UE contexts) regarding capabilities etc., which the MME 610 shares, e.g., with base stations connected to it.
  • MME mobility management entity
  • the MME 610 is also managing handover of a UE from one MME to another when a UE leaves the pool of base stations managed by a source MME, or when the X2 connection is missing between the source and target base stations.
  • the base stations 606, 607 and 608 are further connected to a serving gateway, SGW, 612, which is handing the user data plane transport to and from the base station to which a UE is connected, and to one or more packet data network gateways, PGW, 614, which connect UEs to the internet 616.
  • SGW serving gateway
  • PGW packet data network gateways
  • the MME in whose pool of base stations a UE resides configures which base station the SGW shall connect to for transport of the UE user plane data.
  • the base station 608 may be a network node as defined above and the base station/network node 608 is connected to a number of antenna nodes 620, 622.
  • the base station/network node 608 may control the antenna nodes 620,622 such that antenna node 620 maintains a source cell 621 and antenna node 622 maintains a number of cells 623, 624 and 625 that may be a target cell as described herein.
  • a UE 630 is illustrated, which may correspond to any UE described herein.
  • Figure 7 schematically illustrates a network node 700 comprising input/output circuitry 706, a processor 702 and a memory 704.
  • the memory 704 contains instructions executable by the processor 702 whereby the network node 700 is operative to:
  • the instructions that are executable by the processor 702 may be software in the form of a computer program 741.
  • the computer program 741 may be contained in or by a carrier 742, which may provide the computer program 741 to the memory 704 and processor 702.
  • the carrier 742 may be in any suitable form including an electronic signal, an optical signal, a radio signal or a computer readable storage medium.
  • the network node 700 is operative such that the at least one event triggering condition is configured for triggering any event of:
  • the network node 700 is operative such that the handover configuration data comprises a timer value that specifies a time period during which the UE is allowed to initiate the handover procedure, and where the method comprises:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • the network node 700 is operative such that the at least one movement criterion associated with the UE comprises any of:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • the network node 700 is operative to any of any of:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • the network node 700 is operative to:
  • Figure 8 schematically illustrates a UE 700 comprising radio frequency, RF, circuitry 806, a processor 802 and a memory 804.
  • the memory 804 contains instructions executable by the processor 802 whereby the UE 800 is operative to:
  • the instructions that are executable by the processor 802 may be software in the form of a computer program 841.
  • the computer program 841 may be contained in or by a carrier 842, which may provide the computer program 841 to the memory 804 and processor 802.
  • the carrier 842 may be in any suitable form including an electronic signal, an optical signal, a radio signal or a computer readable storage medium.
  • the UE 800 is operative such that the at least one event triggering condition is configured for triggering any event of:
  • the UE 800 is operative to:
  • the UE 800 is operative such that the determination of the mobility profile for the UE comprises:
  • the UE 800 is operative such that the at least one movement criterion associated with the UE comprises any of:
  • the UE 800 is operative to any of:
  • the UE 800 is operative such that the reception of the handover configuration data comprises reception of at least one timing advance, TA, value for use in the at least one predetermined target cell, and operative to:
  • the UE 800 is operative such that the reception of the handover configuration data comprises reception of at least one system frame number, SFN, offset between a SFN associated with the source cell and a SFN associated with the at least one predetermined target cell, and operative to:
  • the UE 800 is operative to:
  • the UE 800 is operative to:
  • FIG 9 illustrates a network node 900 that comprises:
  • the network node 900 may comprise further modules that are configured to perform in a similar manner as, e.g., the network node 700 described above in connection with figure 7 .
  • FIG 10 illustrates a UE 1000 that comprises:
  • the UE 1000 may comprise further modules that are configured to perform in a similar manner as, e.g., the UE 800 described above in connection with figure 8 .
  • processing module may refer to a processing circuit, a processing unit, a processor, an Application Specific integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or the like.
  • ASIC Application Specific integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a processor, an ASIC, an FPGA or the like may comprise one or more processor kernels.
  • the processing module may be embodied by a software module or hardware module. Any such module may be a determining means, estimating means, capturing means, associating means, comparing means, identification means, selecting means, receiving means, transmitting means or the like as disclosed herein.
  • the expression “means” may be a module, such as a determining module, selecting module, etc.
  • the expression “configured to” may mean that a processing circuit is configured to, or adapted to, by means of software configuration and/or hardware configuration, perform one or more of the actions described herein.
  • memory may refer to a hard disk, a magnetic storage medium, a portable computer diskette or disc, flash memory, random access memory (RAM) or the like. Furthermore, the term “memory” may refer to an internal register memory of a processor or the like.
  • the term "computer readable medium” may be a Universal Serial Bus (USB) memory, a DVD-disc, a Blu-ray disc, a software module that is received as a stream of data, a Flash memory, a hard drive, a memory card, such as a MemoryStick, a Multimedia Card (MMC), etc.
  • USB Universal Serial Bus
  • DVD-disc DVD-disc
  • Blu-ray disc Blu-ray disc
  • a software module that is received as a stream of data
  • Flash memory such as a MemoryStick, a Multimedia Card (MMC), etc.
  • MMC Multimedia Card
  • computer readable code units may be text of a computer program, parts of or an entire binary file representing a computer program in a compiled format or anything there between.
  • number may be any kind of digit, such as binary, real, imaginary or rational number or the like. Moreover, “number”, “value” may be one or more characters, such as a letter or a string of letters. “number”, “value” may also be represented by a bit string.

Landscapes

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

Claims (25)

  1. Procédé mis en œuvre par un nœud de réseau (301) dans un réseau (300) où le nœud de réseau maintient une cellule source (310) dans le réseau, cellule source à laquelle un équipement utilisateur, UE, (306) est connecté, le procédé comprenant :
    - la réception (401), depuis au moins une cellule dans le réseau, de données qui comprennent des informations concernant un transfert, moyennant quoi l'au moins une cellule dans le réseau à partir de laquelle les données sont reçues définit au moins une cellule cible prédéterminée vers laquelle l'UE doit mettre en œuvre un transfert,
    - la fourniture (402), à l'UE, de données de configuration de transfert comprenant les données reçues de l'au moins une cellule et comprenant au moins une condition de déclenchement d'événement qui définit des conditions de mesure de signal radio pour utilisation par l'UE lors de la mise en œuvre d'une décision autonome pour lancer le transfert, et
    - la fourniture (403), à l'au moins une cellule cible prédéterminée, d'informations de contexte associées à l'UE pour préparer la cellule cible à une procédure de transfert lancée par l'UE ; le procédé étant caractérisé par
    - la détermination (420) d'un profil de mobilité pour l'UE, le profil de mobilité comprenant au moins un critère de mouvement associé à l'UE, et
    - la fourniture des données de configuration de transfert à l'UE étant conditionnelle de l'au moins un critère de mouvement ;
    dans lequel l'au moins un critère de mouvement associé à l'UE comprend l'un quelconque parmi :
    - une vitesse de l'UE est supérieure à un seuil de vitesse,
    - une fréquence Doppler maximale associée à des signaux radio transmis par et/ou reçu par l'UE est supérieure à un seuil de fréquence Doppler,
    - un taux de changement de direction de l'UE est supérieur à un seuil de taux de changement de direction, et
    - une détermination quant à savoir si l'UE fonctionne ou non dans un environnement de train à grande vitesse.
  2. Procédé selon la revendication 1, dans lequel l'au moins une condition de déclenchement d'événement est configurée pour déclencher n'importe quel événement parmi :
    - un événement AX étant déclenché par l'UE sur la base d'un résultat d'une comparaison de mesures de signal mises en œuvre par l'UE sur la cellule source et l'au moins une cellule cible prédéterminée,
    - un événement AY étant déclenché par l'UE sur la base d'un résultat d'une comparaison d'une mesure de signal mise en œuvre par l'UE sur la cellule source à un premier seuil, et sur la base d'un résultat d'une comparaison d'une mesure de signal mise en œuvre par l'UE sur l'au moins une cellule cible prédéterminée à un deuxième seuil.
  3. Procédé selon la revendication 1 ou la revendication 2, dans lequel les données de configuration de transfert comprennent une valeur de temporisateur qui spécifie une période de temps pendant laquelle l'UE est autorisé à lancer la procédure de transfert, et où le procédé comprend :
    - la fourniture (412), à l'UE, de la valeur de temporisateur,
    - le démarrage d'un temporisateur (413) en utilisant la valeur de temporisateur,
    - la fourniture (415), à l'au moins une cellule cible prédéterminée, si l'UE n'a pas lancé de procédure de transfert avant que le temporisateur n'expire, d'informations qui empêchent l'UE d'être transféré vers l'au moins une cellule cible prédéterminée, et :
    - le réglage de la valeur de temporisateur (411) sur la base de l'au moins un critère de mouvement.
  4. Procédé selon l'une quelconque des revendications 1 à 3, comprenant :
    - la fourniture (422) du profil de mobilité à l'UE.
  5. Procédé selon l'une quelconque des revendications 1 à 4, comprenant :
    - la réception (440), depuis une cellule cible parmi l'au moins une cellule cible prédéterminée, d'une notification indiquant que l'UE a mis en œuvre une procédure de transfert associée à la cellule cible précitée et, en conséquence de la notification :
    - la libération (441) de ressources spécifiques à l'UE associées à la cellule source et la libération de ressources spécifiques à l'UE associées à n'importe quelle cellule cible prédéterminée avec laquelle l'UE n'a pas mis en œuvre de procédure de transfert.
  6. Procédé selon l'une quelconque des revendications 1 à 5, comprenant l'une quelconque parmi :
    - la fourniture (450), à l'UE, d'une instruction de ne pas appliquer de réception discontinue, DRX, et
    - la fourniture (450), à l'UE, d'une instruction pour appliquer un cycle spécifique de réception discontinue, DRX.
  7. Procédé selon l'une quelconque des revendications 1 à 6, comprenant :
    - la détermination (460) d'une plage de positions de l'UE par rapport à la cellule source et à l'au moins une cellule cible prédéterminée, la plage de positions définissant une plage dans laquelle la procédure de transfert doit être mise en œuvre, et
    - la fourniture (461), à l'UE, sur la base de la plage de positions, de données comprenant au moins une valeur d'avance de temporisation, TA, pour utilisation dans l'au moins une cellule cible prédéterminée.
  8. Procédé selon l'une quelconque des revendications 1 à 7, comprenant :
    - la détermination (470) d'au moins un décalage de numéro de trame système, SFN, entre un SFN associé à la cellule source et un SFN associé à l'au moins une cellule cible prédéterminée, et dans lequel la fourniture des données de configuration de transfert comprend :
    - la fourniture (471), à l'UE, de données comprenant l'au moins un décalage de SFN pour utilisation dans l'au moins une cellule cible prédéterminée.
  9. Procédé selon l'une quelconque des revendications 1 à 8, comprenant :
    - la réception (480), depuis l'UE, d'informations de capacité indiquant que l'UE est capable de mettre en œuvre une décision autonome pour lancer un transfert, et dans lequel
    - la fourniture (481) des données de configuration de transfert à l'UE est conditionnelle des informations de capacité reçues.
  10. Procédé mis en œuvre par un équipement utilisateur, UE, (306) dans un réseau (300) où un nœud de réseau (301) maintient une cellule source (310) dans le réseau, cellule source à laquelle l'UE est connecté, le procédé comprenant :
    - la réception (501), depuis le nœud de réseau, de données de configuration de transfert qui comprennent des informations concernant un transfert vers au moins une cellule cible prédéterminée vers laquelle l'UE doit mettre en œuvre un transfert et au moins une condition de déclenchement d'événement qui définit des conditions de mesure de signal radio pour utilisation par l'UE lors de la mise en œuvre d'une décision autonome pour lancer le transfert,
    - la mesure (502) de signaux radio associés à la cellule source et de signaux radio associés à l'au moins une cellule cible prédéterminée,
    - la détermination (503), sur la base de la mesure de signaux radio, d'un événement selon l'au moins une condition de déclenchement d'événement, et
    - la mise en œuvre (504), sur la base de l'événement déterminé, d'une décision autonome pour lancer un transfert vers l'au moins une cellule cible prédéterminée ; le procédé étant caractérisé par
    - la détermination (420) d'un profil de mobilité pour l'UE, le profil de mobilité comprenant au moins un critère de mouvement associé à l'UE, et
    - la mise en œuvre de la décision autonome de déclencher un transfert étant conditionnelle de
    l'au moins un critère de mouvement ;
    dans lequel l'au moins un critère de mouvement associé à l'UE comprend l'un quelconque parmi :
    - une vitesse de l'UE est supérieure à un seuil de vitesse,
    - une fréquence Doppler maximale associée à des signaux radio transmis par et/ou reçu par l'UE est supérieure à un seuil de fréquence Doppler,
    - un taux de changement de direction de l'UE est supérieur à un seuil de taux de changement de direction, et
    - une détermination quant à savoir si l'UE fonctionne ou non dans un environnement de train à grande vitesse.
  11. Procédé selon la revendication 10, dans lequel l'au moins une condition de déclenchement d'événement est configurée pour déclencher n'importe quel événement parmi :
    - un événement AX étant déclenché par l'UE sur la base d'un résultat d'une comparaison de mesures de signal mises en œuvre par l'UE sur la cellule source et l'au moins une cellule cible prédéterminée,
    - un événement AY étant déclenché par l'UE sur la base d'un résultat d'une comparaison d'une mesure de signal mise en œuvre par l'UE sur la cellule source à un premier seuil, et sur la base d'un résultat d'une comparaison d'une mesure de signal mise en œuvre par l'UE sur l'au moins une cellule cible prédéterminée à un deuxième seuil.
  12. Procédé selon l'une quelconque des revendications 10 et 11, dans lequel la détermination du profil de mobilité pour l'UE comprend :
    - la réception du profil de mobilité depuis le nœud de réseau.
  13. Procédé selon l'une quelconque des revendications 10 à 12, comprenant l'un quelconque parmi :
    - la réception (520), depuis le nœud de réseau, d'une instruction de ne pas appliquer de réception discontinue, DRX, et
    - la réception (520), depuis le nœud de réseau, d'une instruction pour appliquer un cycle spécifique de réception discontinue, DRX, et
    - le fonctionnement (521) conformément aux instructions de DRX reçues.
  14. Procédé selon l'une quelconque des revendications 10 à 13, dans lequel la réception des données de configuration de transfert comprend la réception d'au moins une valeur d'avance de temporisation, TA, pour utilisation dans l'au moins une cellule cible prédéterminée, et comprenant :
    - la mise en œuvre (530) d'une procédure de transfert avec l'au moins une cellule cible prédéterminée, dans lequel la procédure de transfert comprend la demande d'une autorisation de planification sans mettre en œuvre de procédure d'accès aléatoire, RA.
  15. Procédé selon l'une quelconque des revendications 10 à 14, dans lequel la réception des données de configuration de transfert comprend la réception d'au moins un décalage de numéro de trame système, SFN, entre un SFN associé à la cellule source et un SFN associé à l'au moins une cellule cible prédéterminée, et comprenant :
    - la mise en œuvre (540) d'une procédure de transfert avec l'au moins une cellule cible prédéterminée, dans lequel la procédure de transfert comprend la demande d'une autorisation de planification sans lire un bloc d'informations maître, MIB, associé à l'au moins une cellule cible prédéterminée.
  16. Procédé selon l'une quelconque des revendications 10 à 15, comprenant :
    - la fourniture (550), au nœud de réseau, d'informations de capacité indiquant que l'UE est capable de mettre en œuvre une décision autonome pour lancer un transfert.
  17. Procédé selon l'une quelconque des revendications 10 à 16, comprenant :
    - la réception (560), depuis le nœud de réseau, d'une valeur de temporisateur,
    - le démarrage (561) d'un temporisateur en utilisant la valeur de temporisateur,
    - le lancement (564), si aucun transfert ne s'est produit avant que le temporisateur n'ait expiré, d'une procédure de rétablissement.
  18. Nœud de réseau (301, 700) pour utilisation dans un réseau (300) où le nœud de réseau est configuré pour maintenir une cellule source (310) dans le réseau, cellule source à laquelle un équipement utilisateur, UE, (306) est connecté, le nœud de réseau comprenant un circuit d'entrée/sortie (706), un processeur (702) et une mémoire (704), ladite mémoire contenant des instructions exécutables par ledit processeur, moyennant quoi ledit nœud de réseau est conçu pour :
    - recevoir, depuis au moins une cellule dans le réseau, des données qui comprennent des informations concernant un transfert, moyennant quoi l'au moins une cellule dans le réseau à partir de laquelle les données sont reçues définit au moins une cellule cible prédéterminée vers laquelle l'UE doit mettre en œuvre un transfert,
    - fournir, à l'UE, des données de configuration de transfert comprenant les données reçues de l'au moins une cellule et comprenant au moins une condition de déclenchement d'événement qui définit des conditions de mesure de signal radio pour utilisation par l'UE lors de la mise en œuvre d'une décision autonome pour lancer le transfert, et
    - fournir, à l'au moins une cellule cible prédéterminée, des informations de contexte associées à l'UE pour préparer la cellule cible à une procédure de transfert lancée par l'UE, ledit nœud de réseau caractérisé en ce qu'il est conçu pour ;
    - déterminer un profil de mobilité pour l'UE, le profil de mobilité comprenant au moins un critère de mouvement associé à l'UE, dans lequel :
    - la fourniture des données de configuration de transfert à l'UE est conditionnelle de l'au moins un critère de mouvement ; et dans lequel l'au moins un critère de mouvement associé à l'UE comprend l'un quelconque parmi :
    - une vitesse de l'UE est supérieure à un seuil de vitesse,
    - une fréquence Doppler maximale associée à des signaux radio transmis par et/ou reçu par l'UE est supérieure à un seuil de fréquence Doppler,
    - un taux de changement de direction de l'UE est supérieur à un seuil de taux de changement de direction, et
    - une détermination quant à savoir si l'UE fonctionne ou non dans un environnement de train à grande vitesse.
  19. Nœud de réseau selon la revendication 18, conçu pour :
    - déterminer au moins un décalage de numéro de trame système, SFN, entre un SFN associé à la cellule source et un SFN associé à l'au moins une cellule cible prédéterminée, et conçu pour fournir les données de configuration de transfert à l'UE, dans lequel les données de configuration de transfert comprennent en outre l'au moins un décalage de SFN pour utilisation dans l'au moins une cellule cible prédéterminée.
  20. Équipement utilisateur, UE, (306, 800) pour utilisation dans un réseau (300) où un nœud de réseau (301) maintient une cellule source (310) dans le réseau, cellule source à laquelle l'UE est connecté, l'UE comprenant un circuit radiofréquence, RF (806), un processeur (802) et une mémoire (804), ladite mémoire contenant des instructions exécutables par ledit processeur, moyennant quoi ledit UE est conçu pour :
    - recevoir, depuis le nœud de réseau, des données de configuration de transfert qui comprennent des informations concernant un transfert vers au moins une cellule cible prédéterminée vers laquelle l'UE doit mettre en œuvre un transfert et au moins une condition de déclenchement d'événement qui définit des conditions de mesure de signal radio pour utilisation par l'UE lors de la mise en œuvre d'une décision autonome pour lancer le transfert,
    - mesurer des signaux radio associés à une cellule source et des signaux radio associées à l'au moins une cellule cible prédéterminée,
    - déterminer, sur la base de la mesure de signaux radio, un événement selon l'au moins une condition de déclenchement d'événement, et
    - mettre en œuvre, sur la base de l'événement déterminé, une décision autonome pour lancer un transfert vers l'au moins une cellule cible prédéterminée, ledit équipement utilisateur caractérisé en ce qu'il est conçu pour :
    - déterminer un profil de mobilité pour l'UE, le profil de mobilité comprenant au moins un critère de mouvement associé à l'UE, dans lequel :
    - la mise en œuvre de la décision autonome pour lancer un transfert est conditionnelle de l'au moins un critère de mouvement ; et
    dans lequel l'au moins un critère de mouvement associé à l'UE comprend l'un quelconque parmi :
    - une vitesse de l'UE est supérieure à un seuil de vitesse,
    - une fréquence Doppler maximale associée à des signaux radio transmis par et/ou reçu par l'UE est supérieure à un seuil de fréquence Doppler,
    - un taux de changement de direction de l'UE est supérieur à un seuil de taux de changement de direction, et
    - une détermination quant à savoir si l'UE fonctionne ou non dans un environnement de train à grande vitesse.
  21. UE selon la revendication 20, conçu pour recevoir les données de configuration de transfert, dans lequel les données de configuration de transfert comprennent en outre au moins une valeur d'avance de temporisation, TA, pour utilisation dans l'au moins une cellule cible prédéterminée, et conçu pour :
    - mettre en œuvre une procédure de transfert avec l'au moins une cellule cible prédéterminée, dans lequel la procédure de transfert comprend la demande d'une autorisation de planification sans mettre en œuvre de procédure d'accès aléatoire, RA.
  22. UE selon l'une quelconque des revendications 20 à 21 conçu pour recevoir les données de configuration de transfert, dans lequel les données de configuration de transfert comprennent en outre au moins un décalage de numéro de trame système, SFN, entre un SFN associé à la cellule source et un SFN associé à l'au moins une cellule cible prédéterminée, et conçu pour :
    - mettre en œuvre une procédure de transfert avec l'au moins une cellule cible prédéterminée, dans lequel la procédure de transfert comprend la demande d'une autorisation de planification sans lire un bloc d'informations maître, MIB, associé à l'au moins une cellule cible prédéterminée.
  23. Programme informatique (741) comprenant des instructions qui, lorsqu'elles sont exécutées sur au moins un processeur (702) dans un nœud de réseau (700), amènent le nœud de réseau à effectuer toutes les étapes du procédé selon l'une quelconque des revendications 1 à 9.
  24. Programme informatique (841) comprenant des instructions qui, lorsqu'elles sont exécutées sur au moins un processeur (802) dans un équipement utilisateur, UE, (800), amènent l'UE à effectuer toutes les étapes du procédé selon l'une quelconque des revendications 10 à 17.
  25. Porteuse (742, 842), comprenant le programme informatique selon la revendication 23 ou la revendication 24, dans laquelle la porteuse est l'un parmi un signal électronique, un signal optique, un signal radio et un support de stockage lisible par ordinateur.
EP15703753.2A 2015-01-30 2015-01-30 Transfert dans un scenario à grande vitesse Active EP3251406B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2015/051931 WO2016119876A1 (fr) 2015-01-30 2015-01-30 Transfert dans un scenario à grande vitesse

Publications (2)

Publication Number Publication Date
EP3251406A1 EP3251406A1 (fr) 2017-12-06
EP3251406B1 true EP3251406B1 (fr) 2020-01-15

Family

ID=52465348

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15703753.2A Active EP3251406B1 (fr) 2015-01-30 2015-01-30 Transfert dans un scenario à grande vitesse

Country Status (3)

Country Link
US (1) US9860807B2 (fr)
EP (1) EP3251406B1 (fr)
WO (1) WO2016119876A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118607A (zh) * 2020-10-12 2020-12-22 中国联合网络通信集团有限公司 小区切换方法、终端和基站

Families Citing this family (33)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107534918B (zh) * 2015-06-05 2020-03-10 华为技术有限公司 无线通信网络中的方法和节点
CN107710798B (zh) * 2015-06-29 2022-03-11 夏普株式会社 用户设备、具备ProSe功能的装置以及通信控制方法
US9986476B2 (en) * 2016-03-01 2018-05-29 Futurewei Technologies, Inc. Scheduling and handover of a vehicular connection with periodic messaging
US20180139673A1 (en) * 2016-05-11 2018-05-17 Telefonaktiebolaget Lm Ericsson (Publ) Methods and Apparatus for Controlling Mobility in a Wireless Network
US10080105B2 (en) * 2016-06-09 2018-09-18 Huawei Technologies Co., Ltd. System and method for managing mobile virtual machine type communication devices
KR102515541B1 (ko) * 2016-07-19 2023-03-30 한국전자통신연구원 이동무선백홀 네트워크에서의 고속 이동체 단말 및 그의 제어정보 전송 방법과, 기지국의 제어정보 수신 방법
WO2018104217A1 (fr) * 2016-12-09 2018-06-14 Nokia Technologies Oy Transfert autonome d'un équipement d'utilisateur dans un spectre avec ou sans licence
CN108337700B (zh) * 2017-01-20 2020-11-17 北京佰才邦技术有限公司 一种终端自动切换的方法、基站及终端
US11765637B2 (en) 2017-02-01 2023-09-19 Interdigital Patent Holdings, Inc. Assurance driven mobility management
CN108471631B (zh) * 2017-02-23 2020-05-12 北京佰才邦技术有限公司 一种切换准备方法、相关基站及ue
CN110546991B (zh) * 2017-03-22 2022-10-25 摩托罗拉移动有限责任公司 用于切换的条件
EP3607775B1 (fr) * 2017-04-05 2023-06-21 QUALCOMM Incorporated Sélection de cellule de desserte autonome d'équipement utilisateur dans une nouvelle radio
EP3622744B1 (fr) * 2017-05-10 2022-10-26 Nokia Solutions and Networks Oy Procédés se rapportant à des demandes de sélection de tranches de réseau
US10813029B2 (en) * 2017-07-21 2020-10-20 Perspecta Labs Inc. Directed handovers in a cellular network for airborne mobile telemetry
CN110351789A (zh) * 2018-04-03 2019-10-18 维沃移动通信有限公司 用于小区变换的方法和设备
KR102460324B1 (ko) 2018-04-17 2022-10-28 삼성전자 주식회사 무선 통신 시스템에서 단말의 이동성을 지원하는 방법 및 장치
US11419023B2 (en) 2018-05-10 2022-08-16 Nokia Technologies Oy Apparatus and method for optimization of conditional handover confirmation
WO2020077517A1 (fr) * 2018-10-16 2020-04-23 华为技术有限公司 Procédé et dispositif de commutation de cellules dans un contexte mobile à grande vitesse
EP3900433A1 (fr) 2018-12-18 2021-10-27 Telefonaktiebolaget LM Ericsson (publ) Sélection de mobilité conditionnelle
US20220078686A1 (en) * 2019-01-17 2022-03-10 Apple Inc. System and method to avoid user equipment triggering a measurement report after exit of conditional handover
WO2020164073A1 (fr) * 2019-02-14 2020-08-20 Oppo广东移动通信有限公司 Procédé de configuration déclenché par une condition, et produit associé
US11310715B2 (en) * 2019-02-26 2022-04-19 Lg Electronics Inc. Relaxation of mobility condition based on serving cell quality
JP7434363B2 (ja) * 2019-05-13 2024-02-20 フラウンホッファー－ゲゼルシャフト ツァ フェルダールング デァ アンゲヴァンテン フォアシュンク エー．ファオ セルラーネットワークのセルへの条件付きハンドオーバーをサポートするユーザ機器および条件付きハンドオーバーをサポートするセルラーネットワーク
WO2021005575A1 (fr) * 2019-07-10 2021-01-14 Telefonaktiebolaget Lm Ericsson (Publ) Réduction au minimum de charge de signalisation pendant un transfert intercellulaire de ntn
US11696205B2 (en) * 2019-09-26 2023-07-04 Samsung Electronics Co., Ltd. Context-specific customization of handover parameters using characterization of a device's radio environment
CN112788676B (zh) * 2019-11-07 2022-07-12 维沃移动通信有限公司 小区管理方法、小区管理配置方法、终端和网络侧设备
CN112788674B (zh) * 2019-11-07 2022-08-16 维沃移动通信有限公司 切换方法、配置方法、终端及网络设备
US11716657B2 (en) 2020-01-23 2023-08-01 Qualcomm Incorporated Movement direction based communications between user equipment (UE) and base station (BS)
CN113259999B (zh) * 2020-02-10 2022-08-26 华为技术有限公司 一种网络资源配置的方法和装置
CN113810959B (zh) * 2020-06-15 2022-04-29 大唐移动通信设备有限公司 一种小区切换方法及设备
US11812316B2 (en) * 2020-10-09 2023-11-07 Qualcomm Incorporated Handover optimization based on UE mobility prediction
JP2022158831A (ja) 2021-03-31 2022-10-17 スターライト テクノロジーズ リミテッド ハンドオーバーおよびターゲットセル選択のためのユーザー機器識別方法
WO2023168645A1 (fr) * 2022-03-10 2023-09-14 Qualcomm Incorporated Techniques de détection de haute mobilité et d'amélioration des performances d'un modem

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006101308A (ja) 2004-09-30 2006-04-13 Fujitsu Ltd 無線基地局装置及びパスサーチ方法
WO2009099247A1 (fr) 2008-02-08 2009-08-13 Nec Corporation Station mobile, système de radiocommunication mobile, procédé de radiocommunication mobile et programme de radiocommunication mobile
EP2224658B1 (fr) 2009-02-27 2015-07-29 Telefonaktiebolaget L M Ericsson (publ) Correction d'une erreur de fréquence qui est plus grande que la fréquence Nyquist
CN101932052B (zh) 2009-06-23 2016-08-24 华为技术有限公司 一种切换方法、用户终端及网络侧设备
WO2012112098A1 (fr) 2011-02-15 2012-08-23 Telefonaktiebolaget L M Ericsson (Publ) Synchronisation de nœuds pico dans un déploiement de réseau cellulaire hétérogène
US8892103B2 (en) 2011-05-06 2014-11-18 Telefonaktiebolaget L M Ericsson (Publ) Methods and nodes supporting cell change
US20150079991A1 (en) * 2011-09-12 2015-03-19 Nokia Corporation Method and apparatus for mobile terminal connected mode mobility
US20150215830A1 (en) * 2012-01-30 2015-07-30 Nokia Solutions And Networks Oy Mobility with Discontinuous Reception Using Mobility State
US9596629B2 (en) 2012-03-15 2017-03-14 Kyocera Corporation Systems and methods for transparent point-to-point handovers of a mobile relay
US9661516B2 (en) * 2012-03-18 2017-05-23 Lg Electronics Inc. Method and apparatus for performing measurement in wireless communication system
WO2013177778A1 (fr) * 2012-05-31 2013-12-05 Nokia Corporation Procédé, appareil et produit programme d'ordinateur pour changement de cellule autonome par un ue dans un réseau
US9173151B2 (en) * 2012-08-07 2015-10-27 Marvell World Trade Ltd. User mobility control for heterogeneous wireless networks
CN103781136B (zh) 2012-08-07 2017-10-31 诺基亚通信公司 用于终端设备的自主移动的控制机制
WO2014047929A1 (fr) 2012-09-29 2014-04-03 华为技术有限公司 Procédé et dispositif associé permettant de réinitialiser une entité de commande d'accès à un support à grande vitesse
WO2014089051A1 (fr) 2012-12-03 2014-06-12 Interdigital Patent Holdings, Inc. Commande de mobilité de connexion améliorée pour réseaux à petites cellules
US20160021585A1 (en) 2013-04-04 2016-01-21 Nokia Solutions And Networks Oy Avoiding Secondary Cell Configuration for High Speed User Equipment
RU2657249C1 (ru) 2014-10-07 2018-06-09 Телефонактиеболагет Лм Эрикссон (Пабл) Мобильность в сетях с плотным расположением узлов

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112118607A (zh) * 2020-10-12 2020-12-22 中国联合网络通信集团有限公司 小区切换方法、终端和基站
CN112118607B (zh) * 2020-10-12 2023-04-18 中国联合网络通信集团有限公司 小区切换方法、终端和基站

Also Published As

Publication number Publication date
WO2016119876A1 (fr) 2016-08-04
US9860807B2 (en) 2018-01-02
US20160345222A1 (en) 2016-11-24
EP3251406A1 (fr) 2017-12-06

Similar Documents

Publication Publication Date Title
EP3251406B1 (fr) Transfert dans un scenario à grande vitesse
US11558801B2 (en) Handover management based on speeds of wireless communication devices
JP7388480B2 (ja) 無線局、無線局において行われる方法、及び無線端末
US9848362B2 (en) Radio cell arrangement in high speed scenario
EP2880913B1 (fr) Procédé et agencement pour procédures de mobilité
US9706450B2 (en) Wireless communication system with adjacent base stations transmitting a common group cell identifier
EP2567556B1 (fr) Appareil et procédé pour commander la collecte de données de mesure dans un système de communication
US20210068029A1 (en) Mobile telecommunications system transmission and reception points and methods for switching transmission and reception points between active and inactive states
US20130072192A1 (en) Method and system for implementing mobile relay
US20120282932A1 (en) Apparatus and Method
US10231222B2 (en) Method and apparatus for handling carrier aggregation and related signaling
EP3363236B1 (fr) Franchissement de frontière de cellule dans un sfn unidirectionnel pour trains à grande vitesse
EP2810481B1 (fr) Amélioration de la mobilité au moyen d'un nombre plus élevé de mesures de la mobilité durant une période de temps
US10306584B2 (en) User equipment, computer readable medium, and method to determine the mobility of user equipment in a long-term evolution network
US10341926B2 (en) Handover in high speed scenario
CN106792557B (zh) 一种lte轨道交通场景下数据调度方法
US20160029252A1 (en) Mobile communication method

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

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

Free format text: ORIGINAL CODE: 0009012

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20170731

AK Designated contracting states

Kind code of ref document: A1

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

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015045553

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0036000000

Ipc: H04W0036040000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 36/00 20090101ALI20190219BHEP

Ipc: H04W 36/30 20090101ALI20190219BHEP

Ipc: H04W 36/04 20090101AFI20190219BHEP

Ipc: H04W 36/36 20090101ALI20190219BHEP

Ipc: H04W 36/32 20090101ALI20190219BHEP

Ipc: H04W 8/02 20090101ALI20190219BHEP

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

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

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

INTG Intention to grant announced

Effective date: 20190325

INTG Intention to grant announced

Effective date: 20190403

INTC Intention to grant announced (deleted)
GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

INTG Intention to grant announced

Effective date: 20190628

INTC Intention to grant announced (deleted)
GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAJ Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted

Free format text: ORIGINAL CODE: EPIDOSDIGR1

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

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

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20191011

INTC Intention to grant announced (deleted)
INTG Intention to grant announced

Effective date: 20191023

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

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

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

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

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015045553

Country of ref document: DE

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1226253

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200215

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20200115

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

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

Ref country code: PT

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

Effective date: 20200607

Ref country code: NO

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

Effective date: 20200415

Ref country code: FI

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

Effective date: 20200115

Ref country code: RS

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

Effective date: 20200115

Ref country code: NL

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

Effective date: 20200115

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

Ref country code: BG

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

Effective date: 20200415

Ref country code: SE

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

Effective date: 20200115

Ref country code: LV

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

Effective date: 20200115

Ref country code: IS

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

Effective date: 20200515

Ref country code: HR

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

Effective date: 20200115

Ref country code: GR

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

Effective date: 20200416

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20200131

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015045553

Country of ref document: DE

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

Ref country code: CZ

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

Effective date: 20200115

Ref country code: MC

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

Effective date: 20200115

Ref country code: RO

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

Effective date: 20200115

Ref country code: ES

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

Effective date: 20200115

Ref country code: LT

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

Effective date: 20200115

Ref country code: EE

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

Effective date: 20200115

Ref country code: SM

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

Effective date: 20200115

Ref country code: SK

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

Effective date: 20200115

Ref country code: LU

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

Effective date: 20200130

Ref country code: DK

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

Effective date: 20200115

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1226253

Country of ref document: AT

Kind code of ref document: T

Effective date: 20200115

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

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

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

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

Ref country code: LI

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

Effective date: 20200131

Ref country code: CH

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

Effective date: 20200131

Ref country code: BE

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

Effective date: 20200131

26N No opposition filed

Effective date: 20201016

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

Ref country code: FR

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

Effective date: 20200315

Ref country code: IE

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

Effective date: 20200130

Ref country code: AT

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

Effective date: 20200115

Ref country code: IT

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

Effective date: 20200115

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

Ref country code: PL

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

Effective date: 20200115

Ref country code: SI

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

Effective date: 20200115

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

Ref country code: TR

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

Effective date: 20200115

Ref country code: MT

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

Effective date: 20200115

Ref country code: CY

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

Effective date: 20200115

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

Ref country code: MK

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

Effective date: 20200115

Ref country code: AL

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

Effective date: 20200115

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

Ref country code: DE

Payment date: 20240129

Year of fee payment: 10

Ref country code: GB

Payment date: 20240129

Year of fee payment: 10