EP2617237A1 - Method for providing information in a cellular wireless communication system - Google Patents
Method for providing information in a cellular wireless communication systemInfo
- Publication number
- EP2617237A1 EP2617237A1 EP10855783.6A EP10855783A EP2617237A1 EP 2617237 A1 EP2617237 A1 EP 2617237A1 EP 10855783 A EP10855783 A EP 10855783A EP 2617237 A1 EP2617237 A1 EP 2617237A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- cell
- rlf
- link failure
- radio link
- establishment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 90
- 238000004891 communication Methods 0.000 title claims abstract description 49
- 230000001413 cellular effect Effects 0.000 title claims abstract description 45
- 238000004590 computer program Methods 0.000 claims abstract description 13
- 238000005259 measurement Methods 0.000 claims description 17
- 230000005540 biological transmission Effects 0.000 claims description 5
- 230000001960 triggered effect Effects 0.000 claims description 5
- 238000013468 resource allocation Methods 0.000 claims description 4
- 230000006399 behavior Effects 0.000 description 22
- 230000011664 signaling Effects 0.000 description 15
- 239000000284 extract Substances 0.000 description 9
- 238000002360 preparation method Methods 0.000 description 8
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 description 5
- 238000001514 detection method Methods 0.000 description 4
- 230000007704 transition Effects 0.000 description 4
- 238000012384 transportation and delivery Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000001419 dependent effect Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 241000700159 Rattus Species 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000008094 contradictory effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
Definitions
- the present invention relates to a method for providing information in a cellular wireless communication system, or more particularly to a method according to the preamble of claim 1. Furthermore, the invention also relates to a method in a mobile station, a method in a base station, a computer program, a computer program product, a mobile station device and a base station device.
- MS mobile station
- a handover (HO) procedure can consist of many steps.
- a HO is: 1) network controlled, i.e. the MS is commanded by the network when to connect to another cell; 2) prepared, i.e. the target cell to which the MS is moving to is prepared; and 3) MS assisted, i.e. the MS provides measurement reports before HO to the serving cell to assist the decision to do HO preparation of target cell(s), and when to leave the serving cell/connect to the target cell.
- the serving cell before HO is often referred to as the source cell. After successful HO the target cell becomes the new serving cell.
- LTE Long Term Evolution
- UMTS Universal Mobile Telecommunications System
- hard handovers are used exclusively for TDD mode, but may also be used for FDD mode.
- the focus is on the intra frequency LTE HO procedure, but the procedures are similar for the LTE inter Radio Access Technology (RAT) and LTE inter frequency HO procedures.
- the intra E-UTRAN in RRC CONNECTED state is a User Equipment (UE) assisted network controlled HO, with HO preparation signalling in E- UTRAN.
- UE User Equipment
- a HO is initially triggered by a measurement report sent from a UE to a serving eNB (E- UTRAN NodeB).
- the serving eNB configures how the UE shall take measurements, and under what conditions a measurement report shall be triggered and sent to the eNB.
- the UE can measure several different cells and report the results to the network.
- Different networks and network deployments can have different detailed behaviour, but in most systems it is natural to trigger HO when signal reception from a target cell is better than from a source cell.
- the UE includes the reason for the trigger of a HO, e.g. target cell signal stronger than serving cell signal, and measurements of a Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) of the serving cell and several neighbour cells including the target cell.
- RSRP Reference Signal Received Power
- RSRQ Reference Signal Received Quality
- FIG. 1 shows a typical scenario in which a UE performs mobility measurements.
- a serving eNB receives a measurement report from a UE and if the eNB wishes to HO the UE to another cell, the eNB performs a HO preparation to that cell.
- HO preparation involves a signalling exchange between one (serving) eNB and another (target) eNB.
- the source cell requests the HO ⁇ Handover Request) and passes over UE context information; and the target cell decides if it can admit the UE ⁇ Call Admission Control) and either accepts or rejects the HO.
- the target cell includes parameters required by the UE to allow it to communicate to the target cell - these parameters being grouped into a transparent container.
- the source cell may prepare multiple cells for HO. Following a successful preparation, the HO execution takes place. The source cell issues a HO Command to the UE - this is the RRCConnectionReconfiguration message and carries the transparent container.
- the UE If, and when, the UE receives this message correctly the UE synchronises to the new target cell and sends a synchronisation message on the Random Access Channel (RACH).
- the target cell then issues an allocation to the UE so that the UE can send a HO confirmation message to the target cell (RRCConnectionReconfiguration- Complete message).
- the source e B serving the source cell
- the target eNB serving the source cell
- the Sl-U interface from the Serving Gateway (S-GW) must be switched from the source to the target cell ("path switch").
- the target eNB issues a UE Context Release message to the source eNB.
- RLF RACH failure
- Handover Failure 3GPP TS36.331, but for the remainder of this disclosure the term HO failure is used to comprise both RLF and RACH failures.
- the UE After a HO failure, the UE attempts a RRC re-establishment which is described in
- the UE firstly tries to find the strongest cell that it can detect ("cell selection"), and then the UE sends a RRCConnection- ReestablishmentRequest to the cell that it has selected. If this selected cell has prior
- the cell can send a RRCConnectionReestablishment and the re-establishment will succeed which means that the UE remains in Radio Resource
- RRC Remote Control
- the "UE Context" may be passed to a cell during the HO procedure or at some other point in time. This transfer is called HO Preparation.
- the RRCConnectionReestablishmentRequest carries three fields, the Cell Radio Network Temporary Identifier (C-RNTI) of the UE in the serving cell where failure occurred, the Physical Cell Identity (PCI) of this cell, and the shortMAC-I calculated using the Identity (ID) of the re-establishment cell.
- C-RNTI Cell Radio Network Temporary Identifier
- PCI Physical Cell Identity
- the hard HO in the Universal Mobile Telecommunications System is very similar in many respects to the above description - i.e. also being UE assisted but network controlled, which means that the UE is configured to send triggered measurement reports but the network decides when to execute the HO; exploits preparation (using Radio Link Setup procedure); is "backward" HO, which means that the source cell sends the HO command to the UE and the UE replies to the target cell; and is completed by inter-node signalling.
- UMTS Universal Mobile Telecommunications System
- RLF is described in specifications 3GPP TS36.300 and 3GPP TS36.331.
- One form of RLF is driven by out-of-sync detection by Layer 1.
- a radio problem detection procedure is started when a UE receives a certain number of consecutive "out-of-sync" indications from lower layers. The number of consecutive indications is specified by the threshold N310. When this happens, the UE starts a timer T310. In case the UE receives a certain (N311) consecutive "in-sync" indications from lower layers while T310 is running, the UE shall stop the timer and return to normal operation. If T310 expires then RLF is recognised to have occurred ("declared”) by the UE.
- the UE attempts cell selection. If the UE manages to find a cell to connect to within the cell selection phase, the UE will attempt to re-establish RRC to this cell. If, on the other hand, the UE does not find a cell within the cell selection phase (T311), the UE goes back to idle mode and may start looking for cells on other RATs, examples of which are LTE, UMTS, WiMaX and GSM EDGE Radio Access Network (GERAN).
- RLF can also be declared by the Radio Link Control (RLC) layer of the UE when a maximum number of transmissions have been reached for transmission of an uplink RRC signalling packet, but the packet has still not been delivered successfully. Additionally, if the random access during the HO fails (T304 timeout) the UE behaves as if a RLF had occurred. In the present discourse the term RLF relates to any of the above mentioned events.
- a RLF report was introduced in 3 GPP Rel-9 to enable an eNB receiving a RLF indication message to distinguish between Mobility Robustness Optimisation (MRO) related problems and coverage problems. This was done by including a set of neighbour cell measurements indicating the signal strength at the time of failure. With the help of this, the eNB is able to see if there is an alternative neighbour cell that might have been used, or if there is no neighbour detected in the case of a coverage hole.
- MRO Mobility Robustness Optimisation
- the RLF report carries information about:
- Rel-9 if a RLF during a handover is followed by a successful RRC Re-establishment, it is possible to include a RLF Report in a RLF INDICATION message that is sent from a eNB where re-establishment takes place to a eNB that was serving the UE at the point of RLF.
- the capability of the UE to provide the RLF Report is indicated by a flag in the RCConnectionReestablishmentComplete message.
- the RLF Report is then provided to the eNB where re-establishment took place using the UE Information procedure.
- HO parameters shall be optimised, but examples include the HO hysteresis (also called offset) and the Time to Trigger (TTT) parameters.
- TTT Time to Trigger
- the aims of the optimisation are to reduce HO failures whilst at the same time not having more HOs than are necessary.
- the MRO functionality is distributed in the Evolved-UTRAN (E-UTRAN), i.e. every eNB has its own MRO optimisation function.
- E-UTRAN Evolved-UTRAN
- signalling has also been defined between e Bs to help identify HO failure events.
- Mobility Robustness Optimization is to detect RLFs that occur due to Too Early or Too Late Handovers, or Handover to Wrong Cell. This detection mechanism is carried out through the following procedures:
- eNB B may report this RLF event to eNB A by means of the
- eNB B may send a HANDOVER REPORT message indicating a Too Early HO event to eNB A when eNB B receives an RLF Indication from eNB A and if eNB B has sent the UE Context Release message to eNB A related to the completion of an incoming HO for the same UE within the last Tstore_UE_cntxt seconds.
- eNB B may send a HANDOVER REPORT message indicating a HO To Wrong Cell event to eNB A when eNB B receives an RLF Indication from eNB C, and if eNB B has sent the UE Context Release message to eNB A related to the completion of an incoming HO for the same UE within the last T tore _ UE _cntxt seconds.
- the indication may also be sent if eNB B and eNB C are the same and the RLF report is internal to this eNB.
- the detection of the above events is enabled by the RLF Indication and Handover
- the RLF Indication procedure may be initiated after a UE attempts to re-establish the radio link at eNB B after a RLF at eNB A.
- the RLF INDICATION message sent from eNB B to eNB A shall contain the following information elements:
- - Reestablishment Cell ID ECGI of the cell where RL re-establishment attempt is made;
- C-RNTI C-RNTI of the UE in the cell where RLF occurred.
- - shortMAC-I (optionally): the 16 least significant bits of the MAC-I calculated using the security configuration of the source cell and the re-establishment cell identity.
- eNB B may initiate RLF Indication towards multiple eNBs if they control cells which use the PCI signalled by the UE during the re-establishment procedure.
- the eNB A selects the UE context that matches the received Failure cell PCI and C-RNTI, and, if available, uses the shortMAC-I to confirm this identification, by calculating the shortMAC-I and comparing it to the received IE.
- the Handover Report procedure is used in the case of recently completed handovers, when an RLF occurs in the target cell (in eNB B) shortly after it sent the UE Context Release message to the source eNB A.
- the HANDOVER REPORT message contains the following information:
- a problem facing the MRO algorithm is how to distinguish between a failure from a coverage hole and a too late HO failure because of inappropriate HO parameters.
- a UE may suffer RLF when it enters a coverage hole that lies between the coverage of one cell and another cell.
- lack of coverage implies that the UE cannot detect any cells, or if it can, the signalling radio bearer performance is not good enough to deliver messages to or from the UE.
- RLF may occur with or without an attempt to perform a HO between the two cells.
- the UE may attempt RRC re-establishment in the second cell and if the re-establishment request message is received correctly an X2 message, such as a RLF indication message, will be sent between the two cells (assuming they belong to separate eNBs).
- the MRO algorithm may react to such a failure report by reducing the offset by increasing the Cell Individual Offset (CIO) - this is the normal response to too late HOs.
- CIO Cell Individual Offset
- the MRO is expected to: a) meet a specified HO failure rate target, and b) minimize the number of HO events whilst meeting this target value.
- HO failure rate reduction and HO count reduction are contradictory requirements; if the failure rate is reduced the HO count increases, and vice versa.
- the RLF report was introduced in 3GPP Rel-9 to enable an eNB receiving the RLF indication (carrying the RLF report) to distinguish between Mobility Robustness Optimisation (MRO) related problems and coverage problems. This was done by including a set of neighbour cell measurements indicating the signal strength at the time of failure. With the help of this, the eNB is able to see if there is an alternative neighbour cell that might have been used, or if there is no neighbour detected in the case of a coverage hole.
- MRO Mobility Robustness Optimisation
- the RLF report carries information about:
- Rel-9 when a RLF during a HO is followed by a successful RRC Re-establishment, it is possible to include a RLF Report in a RLF INDICATION message that is sent from an eNB where re-establishment takes place to a eNB that was serving the UE at the point of RLF.
- the capability of the UE to provide the RLF Report is indicated by a flag in the RCConnectionReestablishmentComplete message.
- the RLF Report is then provided to the eNB where re-establishment took place using the UE Information procedure.
- the Rel-9 solution is only able to deliver the RLF report to the original source cell if the re- establishment is successful.
- a RLF indication is generated when a UE attempts RRC re-establishment (it may be sent as soon as the RRCConnectionRequest is received and the eNB notes that it does not hold a context for the UE) - this is a primary indication. • When the UE then attempts RRC establishment from idle mode it indicates it has a RLF Report available.
- the e B where the UE connects, extracts the report from the UE and sends a secondary RLF indication to the cell where the UE was previously attached (the source cell).
- the UE provides additional information together with radio measurements in the RLF Report such as the CRNTI, PCI and short MAC-I; these allow the recipient to determine where to send the secondary RLF indication to, and additionally they allow the recipient of the secondary RLF indication to tally this with the original primary RLF indication (recognizing that they belong to the same failure event).
- the eNB that receives a primary indication does not know if there will be a secondary indication
- the eNB must therefore keep the primary RLF indication and wait to see if a secondary RLF indication arrives; it is difficult to set a value for this waiting time. Whilst waiting no action by MRO is possible since the action is dependent upon the content of the (possible) RLF Report
- the eNB receives the secondary RLF indication before the primary RLF indication, since they may be sent from different eNBs over different communication links (e.g. X2 links). This type of scenario needs to be managed by the communication system.
- the object of the present invention is to provide a method which mitigates and/or solves the disadvantages of prior art solutions.
- Another object of the invention is to provide a method which reduces un-necessary signalling and is easy to implement in existing communication system.
- a yet another object of the invention is to provide an alternative method for providing information in a cellular wireless communication system.
- the objects are achieved with a method for providing information in a cellular wireless communication system, wherein each cell in said cellular wireless communication system is served by a base station, and said cellular wireless communication system employs a procedure in which a mobile station suffering from a radio link failure (RLF) while being connected to a cell may attempt to re-establish a connection in another cell, comprising the steps of:
- RLF radio link failure
- RLF radio link failure
- RRC radio resource control
- Embodiments of the method in a cellular wireless communication system above are disclosed in the dependent claims 2-26.
- the objects are also achieved with a method in a mobile station for providing information in a cellular wireless communication system, wherein each cell in said cellular wireless communication system is served by a base station, and said cellular wireless communication system employs a procedure in which a mobile station suffering from a radio link failure (RLF) while being connected to a cell may attempt to re-establish a connection in another cell, comprising the steps of:
- RLF radio link failure
- RLF radio link failure
- RRC radio resource control
- the objects are also achieved with a method in a base station for providing information in a cellular wireless communication system, wherein each cell in said cellular wireless communication system is served by a base station, and said cellular wireless communication system employs a procedure in which a mobile station suffering from a radio link failure (RLF) while being connected to a cell may attempt to re-establish a connection in another cell, comprising the steps of:
- RRC radio resource control
- RLF radio link failure
- RRC radio resource control
- RLF radio link failure
- RLF radio link failure
- the invention also relates to a computer program and a computer program product when run in a computer causes the computer to execute the method in a mobile station and the method in a base station described above.
- a mobile station device for providing information in a cellular wireless communication system, wherein each cell in said cellular wireless communication system is arranged to be served by a base station, and said cellular wireless communication system employs a procedure in which a mobile station suffering from a radio link failure (RLF) while being connected to a cell may attempt to re-establish a connection in another cell, being configured to:
- RLF radio link failure
- RLF radio link failure
- RRC radio resource control
- RLF radio link failure
- RLF radio link failure
- a base station device for providing information in a cellular wireless communication system, wherein each cell in said cellular wireless communication system is arranged to be served by a base station, and said cellular wireless communication system employs a procedure in which a mobile station suffering from a radio link failure (RLF) while being connected to a cell may attempt to re-establish a connection in another cell, being configured to:
- RLF radio link failure
- RRC radio resource control
- RLF radio link failure
- RRC radio resource control
- RLF radio link failure
- the present invention enables delivery of a single RLF indication carrying a RLF report (if available at the UE) to the source cell when the RRC re-establishment following a RLF is unsuccessful and the UE establishes an RRC connection from idle mode. Delivery is also possible if the UE does not generate any RRC re-establishment signalling because cell selection after RLF fails.
- the method addresses different e B capabilities, and cases when source cell, re-establishment cell and establishment cell are different cells.
- signalling may be reduced in the system compared to prior art solutions. Further, complexity of receivers, such as base stations, receiving the information may be reduced. Further, the impact on some of the current communication systems is minimized.
- FIG. 1 shows a typical cell scenario with cell measurement
- Figure 3 shows a failure RRC connection re-establishment
- Figure 4 shows an example of a too late HO failure followed by a successful RRC re- establishment
- Figure 5 shows an example of a too late HO failure followed by an unsuccessful RRC re-establishment.
- the present invention relates to a method for providing information in a cellular wireless communication system, in which each cell is served by at least one Base Station (BS) serving a particular cell.
- BS Base Station
- a BS may serve more than one cell.
- the system employs a procedure in which a MS suffering from a RLF while being connected to a cell may attempt to re-establish a connection in another cell.
- the RLF may result from a HO failure for a MS.
- the method comprises the steps of: detecting a RLF for a MS while connected to a first cell; requesting a RRC re-establishment for the MS in a second cell after the RLF; and providing a single RLF indication message to the first cell.
- the RLF report is produced by the MS, and may according to another embodiment comprise a cell Identity (ID) of an establishment cell and a value representing a time period from the RRC re-establishment request to a RRC establishment.
- ID cell Identity
- the RRC re-establishment request comprises a first flag indicating whether the RLF report is available or not.
- the first flag is preferably contained in a RRCConnectionReestablishmentRequest message.
- a RLF indication message is generated by a cell in which a RRC establishment subsequently takes place if the first flag indicates that the RLF report is available and the re-establishment request is unsuccessful.
- the cell where re-establishment is attempted can determine that when the flag is set (to true) a neighbouring base station may extract a RLF report from a MS after RRC establishment and send it in a RLF indication to the first cell. If the flag is set to false, the cell where re- establishment is attempted can immediately generate the RLF indication.
- the second cell indicates to the MS whether the MS shall attempt to deliver the RLF report at RRC establishment.
- the indication is preferably contained in a RRCConnectionReestablishmentReject message.
- the MS sets a second flag indicating whether the RLF report is available during a RRC establishment if the RRC establishment is performed in the same cell as a cell in which the RRC re-establishment was requested.
- the second flag is preferably contained in a RRCConnectionRequest or a RRCConnection- SetupComplete message.
- the step of providing the RLF report involves, according to an embodiment of the invention: transmitting the RLF report to a first BS serving the first cell. Hence, if the RRC
- the RLF report is transmitted by a second
- the RLF report is contained in the RLF indication message or in a HO report message and may be transmitted via one or more X2 interfaces or any other suitable interface between different network nodes (e.g. BSs) in the system.
- the first BS serving the first cell may copy the RLF report into the HO report message.
- the HO report is employed in "HO too early” and “HO to wrong cell” when failure occurs immediately after a successful HO. In these cases, the first BS sends the HO report to the cell to which the UE was connected prior to the first cell.
- the RLF indication message is generated if a cell to which the MS reconnects after the RLF is the same cell as a cell in which the radio resource control (RRC) re-establishment was requested.
- RRC radio resource control
- a radio resource allocation grant and a time offset value T offset is provided to the MS by the cell in which the
- the radio resource allocation grant is used after the time offset value T 0ffset by the MS to send a RRC connection request message.
- the RLF indication message is generated after waiting a second time period T Wait in a cell in which RRC re-establishment was requested, wherein:
- the generation of the RLF indication message or the HO report message is cancelled if a cancellation message is received from a cell to which the MS reconnects after the RLF;
- the RLF indication message is triggered if a RLF report from a successful RRC
- the RLF indication message is generated if a cell to which the MS performs cell establishment after the RLF belongs to the same BS as a cell in which the RRC re-establishment was requested.
- the MS can judge whether this condition is true according to signalling from the cell where re-establishment is attempted, preferably in the
- the cell where RRC establishment takes place does not generate a RLF indication message if the first time period T in the RLF report exceeds the second time period T Wait .
- the present invention enables delivery of a single RLF indication message carrying a RLF report - if available at the UE - to the source cell when the RRC re-establishment following a RLF is unsuccessful and the UE establishes an RRC connection from idle. Delivery is also possible if the UE does not generate any RRC re-establishment signalling because cell selection after RLF fails.
- the present method addresses different e B capabilities, and cases when source eNB, re-establishment eNB and establishment eNB are all different.
- the present invention includes mechanisms to avoid generation of multiple RLF indications following a RRC re-establishment rejection by an eNB There arc different failure cases/modes for a UE in connection with a RLF such as that after a RLF:
- a UE may have different capabilities so that the UE may or may not be able to provide a RLF report after connection from idle state.
- the eNB to which the UE connects from idle state may or may not support RLF Report extraction and sending in a RLF indication message.
- cell S an original serving cell
- cell R a cell where re-establishment is attempted
- cell / a cell where the UE connects from idle state
- the UE is able to store details of a RLF event, such as signal strength measurements on serving and neighbour cells prior to failure, after the UE has transitioned to RRC idle state following a RRC re-establishment failure. These details (information) may be packed into a RLF report message which the UE can deliver to the cell to which it next performs RRC establishment. Additional information elements may be provided within the RLF report, which may differ between different embodiments as detailed below. Mode (i) of the present invention
- a solution which places no restrictions on the relationship between cell R and cell / is first described, hence they can be different cells, and/or they can belong to different e Bs. It addresses failure cases (T), (TT) and (TTT) above, and different UE and eNB capabilities. Tn this mode the UE provides the identity of the RRC re-establishment cell (the cell where re- establishment was attempted) and the identity of the cell where RLF took place in the RLF report the UE provides after RRC establishment. The latter identity is required to allow the recipient to route a RLF indication to the correct eNB (i.e. the eNB serving the failure cell). The latter identity is included in the RLF indication (within or outside the RLF report information element) to indicate the failure cell. The former identity may be signalled similarly and can be useful when analysing the failure since the failure sequence is then known (failure cell - re-establishment cell - establishment cell).
- the UE includes a flag to indicate the availability of a RLF Report that may be sent after a transition to RRC Idle in the RRCConnectionReestablishmentRequest; the eNB serving cell R determines to generate a RLF indication immediately or to do nothing according to the presence and setting of the flag, together with knowledge of the support for RLF Indication following RRC establishment in other eNBs.
- the eNB serving cell / where establishment takes place shall always generate a RLF indication message (with RLF report) if the UE indicates that it has a RLF report to send.
- the flag discussed above indicating the availability of a RLF report that may be sent after a transition to RRC idle state in the RRCConnectionReestablishmentRequest, therefore indicates that the UE has information available, but may also indicate that the UE is capable of sending this information after transition to idle.
- the e B shall behave differently if the other eNBs in the network do not support the RLF indication following RRC establishment. This can either be achieved by configuration (from OAM). Another solution is to let each eNB discover the capability of the neighbour eNB by including this capability in the X2 signalling between the eNBs.
- An important aspect with this embodiment is that a UE includes a flag to indicate the availability of a RLF report that may be sent after a transition to RRC idle state in the
- o eNB generates an RLF indication immediately, because there is no
- ⁇ eNB generates RLF indication immediately, because there is no possibility that a RLF indication could be generated after the UE does RRC establishment,
- ⁇ ⁇ eNB does nothing (there is a possibility that an eNB could generate a RLF Indication so to avoid two RLF indications for the same event a RLF Indication cannot be generated at this point in time) ⁇ .
- the e B If the flag is not present, the e B generates a RLF indication message since there is no possibility that a RLF indication could be generated after the UE does RRC establishment.
- an optimisation of the exemplary embodiment A is also to include a flag in the RRC- ConnectionReestablishmentReject message to indicate whether the UE is expected to try sending the RLF -report again in RRC establishment or not.
- this solution gives the eNB the possibility to also tell the UE not to send the RLF report again, thereby eliminating the risk for duplicate RLF indications being generated in the system.
- cell R where if cell R is not certain whether other cell / will support the generation of a RLF indication after RRC establishment it may wait for a defined time before generating a RLF Indication. The generation is cancelled if cell / signals to cell R that it has generated a RLF Indication. This requires that the UE tells cell / the time since the re-establishment attempt in cell R.
- Cell R behaviour • Cell R starts a second timer T Wait (value max_wait_time) and keeps a record of the rc-cstablishmcnt attempt (time, message contents).
- o Cell R sends a RLF indication (with no RLF report but with an indication of the time since Re-establishment attempt).
- Cell R starts a second timer T Wait (value max_wait_time) and keeps a record of the re-establishment attempt (time, message contents).
- o Cell R sends a RLF indication (with no RLF report but with an indication of the time since Re-establishment attempt).
- Value max waitjime controls how long the time from re-establishment attempt to establishment is permitted so that a RLF indication with a RLF report can be generated.
- the re-establishment in the same cell as re-establishment was attempted is a very likely scenario since during the re-establishment the UE already chose the best cell, cell R, and this will be the best cell for RRC establishment unless the UE has moved significantly, or there are two cells of approximately equal signal strength and uncertainty in the UE measurements can favour one or the other.
- the behaviour of the nodes can be simplified.
- the UE provides the identity of the failure cell, for the same reasons as in mode (i) above.
- the embodiments in this mode include mechanisms, described below, to identify that re-establishment cell is equal to establishment cell.
- Cell / recognizes this event by comparing contents of RLF report, sent to cell / after establishment there, with previously recorded re-establishment requests.
- Cell R receives a RRC re-establishment request and determines to reject it.
- T Wait value equals max_wait_time
- T Wait keeps a record of the re-establishment attempt (time, message contents) - IF T Wait expires: Send a RLF indication (with no RLF report but with some indication of time since Re- establishment attempt).
- PCI Physical Cell Identity
- ECGI global cell id values
- This embodiment may be extended to cover failure cases (I) and (II) by allowing the UE to indicate it has a report in these circumstances. Cell / would then be unable to stop a timer but this would be OK.
- Cell R receives a RRC rc-cstablishmcnt request and determines to reject it.
- Cell R provides a particular resource grant to the UE and a time offset for which it can be used in the RRCConnectionReestablishmentReject.
- Cell R decodes the transmission in the granted resource at the specified time.
- Cell R can extract a RLF report, if available.
- the UE behaviour is modified in this embodiment so that the UE can exploit the special granted resource for the establishment request message.
- the RLF indication generation is only allowed following a RRC establishment if the UE connects to the same e B (BS) as where re- establishment was attempted.
- This solution offers more coverage of possible outcomes than mode (ii) and exploits internal signalling within the common eNB of cell / and cell R. By restricting the solution, the behaviour of the nodes can be simplified.
- UE information elements to identify cells in this mode are the same as mode (i) above.
- Cell R receives a RRC re-establishment request and determines to reject it.
- Cell R advertises the other cells of its eNB parent in the RRCConnection- ReestablishmentReject (PCI values or ECGI).
- ⁇ Cell R starts a second timer T Wait (value equals max_wait_time) and keeps a record of the re-establishment attempt (time, message contents).
- eNB serving cell 1 eNB serving cell R.
- the cellular wireless communication system may be any relevant cellular system, such as LTE, UMTS, CDMA2000, WiMaX and GERAN.
- the BS may be any of a e B, NodeB and BTS; and the MS any of UE, MS and SS; or any relevant MS or BS having the corresponding functions.
- the ability to send information comprising a RLF report, in a single RLF indication message, after a UE has passed to idle mode greatly improves the ability of a MRO algorithm to identify failure events arising from e.g. coverage holes.
- the invention provides the means so that this can happen whenever possible (even when the UE has not attempted RRC re-establishment), whilst avoiding unnecessary complexity for the receiver of the message which would occur through duplicate messages for the same event.
- a BS serving the first cell may tune one or more mobility parameters and/or provide one or more performance measurements. Further, signalling in the system may be reduced with the present invention.
- the invention also relates to a method in a MS and a method in a BS.
- the method in a MS comprises the steps of: detecting a RLF while being connected to a first cell; requesting a RRC re-establishment in a second cell after the RLF; indicating whether information comprising a RLF report is available or not to the second cell; and providing the RLF report to a cell where a RRC establishment is performed after receiving a rejection of the RRC re-establishment request.
- the method in a BS comprises the steps of: receiving a RRC re-establishment request from a mobile station; registering a RLF for the mobile station while connected to a first cell; rejecting the RRC re-establishment request; determining whether a RLF indication message is generated by a cell in which a RRC establishment is performed by the mobile station; and providing a single RLF indication message to the first cell if the cell in which the RRC establishment is performed does not generate the RLF indication message.
- a method in a MS and a method in a BS according to the present invention may be implemented in a computer program, having code means, which when run in a computer causes the computer to execute the steps of the method.
- the computer program is included in a computer readable medium of a computer program product.
- the computer readable medium may consist of essentially any memory, such as a ROM (Read-Only Memory), a PROM (Programmable Read-Only Memory), an EPROM (Erasable PROM), a Flash memory, an EEPROM (Electrically Erasable PROM), or a hard disk drive.
- the invention further relates to a MS device and a BS device arranged accordingly.
- the MS device is being configured to: detect a RLF while being connected to a first cell; request a RRC re-establishment in a second cell after the RLF in a second cell; indicate whether information comprising a RLF report is available or not to the second cell; and providing the RLF report to a cell where a RRC establishment is performed after receiving a rejection of the RRC re-establishment request.
- the BS device is being configured to: receive a RRC re-establishment request from a mobile station; register a RLF for the mobile station while connected to a first cell; reject the RRC re- establishment request; determine whether a RLF indication message is generated by a cell in which a RRC establishment is performed by the mobile station; and provide a single RLF indication message to the first cell.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2010/075980 WO2012019362A1 (en) | 2010-08-13 | 2010-08-13 | Method for providing information in a cellular wireless communication system |
Publications (3)
Publication Number | Publication Date |
---|---|
EP2617237A1 true EP2617237A1 (en) | 2013-07-24 |
EP2617237A4 EP2617237A4 (en) | 2014-01-08 |
EP2617237B1 EP2617237B1 (en) | 2017-12-13 |
Family
ID=45567290
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP10855783.6A Active EP2617237B1 (en) | 2010-08-13 | 2010-08-13 | Methods and devices for providing information in a cellular wireless communication system |
Country Status (2)
Country | Link |
---|---|
EP (1) | EP2617237B1 (en) |
WO (1) | WO2012019362A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015017975A1 (en) * | 2013-08-06 | 2015-02-12 | 华为技术有限公司 | Indication information sending and receiving method and apparatus |
CN110831260A (en) * | 2018-08-10 | 2020-02-21 | 电信科学技术研究院有限公司 | RRC connection recovery processing method and device and terminal |
CN111954314A (en) * | 2013-08-09 | 2020-11-17 | 华为技术有限公司 | Message transmission method and device |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2013141544A1 (en) * | 2012-03-18 | 2013-09-26 | Lg Electronics Inc. | Method and apparatus for performing measurement in wireless communication system |
JP5835485B2 (en) * | 2012-07-18 | 2015-12-24 | 日本電気株式会社 | Wireless base station, mobile communication system, handover control method, and program |
WO2014101171A1 (en) * | 2012-12-31 | 2014-07-03 | 富士通株式会社 | Method, device and system for restoring connection failure |
ES2769858T3 (en) | 2013-04-01 | 2020-06-29 | Innovative Sonic Corp | Method and apparatus for adding service cells in a wireless communication system |
CN105453649A (en) * | 2013-05-10 | 2016-03-30 | 诺基亚技术有限公司 | Mobility handling for dual connectivity |
WO2015027381A1 (en) * | 2013-08-26 | 2015-03-05 | 华为技术有限公司 | Radio link failure handling method, user equipment and base station |
KR102167019B1 (en) * | 2013-10-01 | 2020-10-16 | 삼성전자주식회사 | Method and apparatus for controlling handover in a wireless communication system |
WO2015140848A1 (en) | 2014-03-18 | 2015-09-24 | 日本電気株式会社 | Control apparatus, base station apparatus, radio terminal, and method for updating neighbour relation table |
KR102191372B1 (en) | 2014-07-18 | 2020-12-15 | 삼성전자 주식회사 | Method and apparatus for increasing handover success rate |
WO2016090609A1 (en) * | 2014-12-11 | 2016-06-16 | Qualcomm Incorporated | Neighbor cell measurements for high-speed user equipment |
CN106937338B (en) * | 2015-12-31 | 2020-01-10 | 中国电信股份有限公司 | Link reconstruction method and system |
WO2018214052A1 (en) | 2017-05-24 | 2018-11-29 | Qualcomm Incorporated | Uplink small data transmission in inactive state |
CN111480389B (en) * | 2018-03-22 | 2021-11-19 | Oppo广东移动通信有限公司 | Information transmission method and device and computer storage medium |
KR20200127405A (en) * | 2019-05-02 | 2020-11-11 | 삼성전자주식회사 | Method and apparatus for performing radio link failure reporting in next generation mobile communication system |
CN114079989A (en) * | 2020-08-21 | 2022-02-22 | 中兴通讯股份有限公司 | Method for processing failure cause value, electronic device and computer readable storage medium |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9060316B2 (en) * | 2007-01-10 | 2015-06-16 | Qualcomm Incorporated | Radio resource connection (RCC) establishment for wireless systems |
CN101400088B (en) * | 2007-09-30 | 2011-04-20 | 华为技术有限公司 | Switching method and device for evolution network |
ES2368874T3 (en) * | 2008-02-04 | 2011-11-23 | Alcatel Lucent | METHOD AND APPLIANCE FOR RECOVERY AFTER A RADIO LINK FAILURE IN A WIRELESS COMMUNICATIONS NETWORK. |
CN101562851B (en) * | 2009-06-02 | 2011-05-04 | 中国科学技术大学 | Fast recovery method of multiple preparation district RLFs based on movement pattern and system |
-
2010
- 2010-08-13 EP EP10855783.6A patent/EP2617237B1/en active Active
- 2010-08-13 WO PCT/CN2010/075980 patent/WO2012019362A1/en active Application Filing
Non-Patent Citations (5)
Title |
---|
HUAWEI ET AL: "Inclusion of UE RLF Report in RLF INDICATION message", 3GPP DRAFT; R3-101225_UE_RLF_REPORT_CR36423_0358, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. San Francisco, USA; 20100222, 1 March 2010 (2010-03-01), XP050424992, [retrieved on 2010-03-01] * |
HUAWEI: "UE RLF report for Mobility Robustness Optimisation", 3GPP DRAFT; R3-100899 UE RLF REPORT FOR MOBILITY ROBUSTNESS OPTIMISATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. San Francisco, USA; 20100222, 12 February 2010 (2010-02-12), XP050424645, [retrieved on 2010-02-12] * |
HUAWEI: "UE RLF report", 3GPP DRAFT; R2-102913 UE RLF REPORT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Montreal, Canada; 20100510, 3 May 2010 (2010-05-03), XP050423056, [retrieved on 2010-05-03] * |
HUAWEI: "UE RLF report", 16 February 2010 (2010-02-16), 3GPP DRAFT; R2-101265 UE RLF REPORT, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, XP050421784, [retrieved on 2010-02-16] * the whole document * * |
See also references of WO2012019362A1 * |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015017975A1 (en) * | 2013-08-06 | 2015-02-12 | 华为技术有限公司 | Indication information sending and receiving method and apparatus |
CN111954314A (en) * | 2013-08-09 | 2020-11-17 | 华为技术有限公司 | Message transmission method and device |
CN110831260A (en) * | 2018-08-10 | 2020-02-21 | 电信科学技术研究院有限公司 | RRC connection recovery processing method and device and terminal |
CN110831260B (en) * | 2018-08-10 | 2022-04-22 | 大唐移动通信设备有限公司 | RRC connection recovery processing method and device and terminal |
Also Published As
Publication number | Publication date |
---|---|
EP2617237A4 (en) | 2014-01-08 |
EP2617237B1 (en) | 2017-12-13 |
WO2012019362A1 (en) | 2012-02-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2617237B1 (en) | Methods and devices for providing information in a cellular wireless communication system | |
US11388766B2 (en) | Method and arrangement for connection re-establishment in a telecommunication system | |
US9479984B2 (en) | Method for providing information in a cellular wireless communication system | |
US11665599B2 (en) | Light-weight RRC connection setup in multi-rat network | |
US20140050197A1 (en) | Method for Providing Information in a Cellular Wireless Communication System | |
US9980159B2 (en) | RRC re-establishment on secondary eNodeB for dual connectivity | |
US9504082B2 (en) | Method of enhanced connection recovery and loss-less data recovery | |
US9661510B2 (en) | Failure event report extension for inter-RAT radio link failure | |
CN105379324A (en) | Method for transmitting cell visited history and wireless equipment thereof | |
WO2020113576A1 (en) | Base station switching method and device and storage medium | |
AU2014307257A1 (en) | Method for processing radio link failure in multiple base station connectivity based radio communication system, and apparatus for same | |
CN105072644B (en) | Method for providing information in a cellular wireless communication system | |
JP6672410B2 (en) | Method and arrangement for connection recovery in telecommunications system | |
JP2017135717A (en) | Method and arrangement for connection re-establishment in telecommunication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
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 |
|
17P | Request for examination filed |
Effective date: 20130528 |
|
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 SE SI SK SM TR |
|
DAX | Request for extension of the european patent (deleted) | ||
A4 | Supplementary search report drawn up and despatched |
Effective date: 20131211 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 28/04 20090101ALI20131205BHEP Ipc: H04W 76/02 20090101ALI20131205BHEP Ipc: H04W 36/24 20090101ALI20131205BHEP Ipc: H04W 8/24 20090101ALI20131205BHEP Ipc: H04W 88/08 20090101ALI20131205BHEP Ipc: H04W 36/08 20090101ALI20131205BHEP Ipc: H04W 36/34 20090101AFI20131205BHEP |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 28/06 20090101ALN20170314BHEP Ipc: H04W 88/08 20090101ALN20170314BHEP Ipc: H04W 8/24 20090101ALN20170314BHEP Ipc: H04W 36/24 20090101AFI20170314BHEP Ipc: H04W 76/02 20090101ALN20170314BHEP Ipc: H04W 36/08 20090101ALN20170314BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 76/02 20090101ALN20170406BHEP Ipc: H04W 36/24 20090101AFI20170406BHEP Ipc: H04W 36/08 20090101ALN20170406BHEP Ipc: H04W 88/08 20090101ALN20170406BHEP Ipc: H04W 28/06 20090101ALN20170406BHEP Ipc: H04W 8/24 20090101ALN20170406BHEP |
|
INTG | Intention to grant announced |
Effective date: 20170424 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
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 |
|
GRAL | Information related to payment of fee for publishing/printing deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR3 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Ref document number: 602010047422 Country of ref document: DE Free format text: PREVIOUS MAIN CLASS: H04W0036340000 Ipc: H04W0036240000 |
|
INTC | Intention to grant announced (deleted) | ||
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 28/06 20090101ALN20170921BHEP Ipc: H04W 88/08 20090101ALN20170921BHEP Ipc: H04W 76/02 20090101ALN20170921BHEP Ipc: H04W 8/24 20090101ALN20170921BHEP Ipc: H04W 36/08 20090101ALN20170921BHEP Ipc: H04W 36/24 20090101AFI20170921BHEP |
|
GRAR | Information related to intention to grant a patent recorded |
Free format text: ORIGINAL CODE: EPIDOSNIGR71 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
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 SE SI SK SM TR |
|
INTG | Intention to grant announced |
Effective date: 20171106 |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 955435 Country of ref document: AT Kind code of ref document: T Effective date: 20171215 Ref country code: CH Ref legal event code: EP |
|
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: 602010047422 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20171213 |
|
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: 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: 20171213 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: 20171213 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: 20171213 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: 20180313 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 955435 Country of ref document: AT Kind code of ref document: T Effective date: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 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: 20171213 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: 20180313 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: 20180314 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 |
|
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: 20171213 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: 20171213 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: 20171213 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: 20171213 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: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 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: 20171213 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: 20180413 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: 20171213 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: 20171213 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: 20171213 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602010047422 Country of ref document: DE |
|
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 |
|
26N | No opposition filed |
Effective date: 20180914 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
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: 20180831 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180831 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180813 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20180831 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180813 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180831 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180831 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180813 |
|
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: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20100813 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: 20171213 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20171213 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20171213 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240702 Year of fee payment: 15 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240701 Year of fee payment: 15 |