WO2013167204A1 - Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies - Google Patents
Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies Download PDFInfo
- Publication number
- WO2013167204A1 WO2013167204A1 PCT/EP2012/058815 EP2012058815W WO2013167204A1 WO 2013167204 A1 WO2013167204 A1 WO 2013167204A1 EP 2012058815 W EP2012058815 W EP 2012058815W WO 2013167204 A1 WO2013167204 A1 WO 2013167204A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- event
- information element
- access technology
- communication link
- case
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- 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/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- the present invention relates to methods, devices and computer program products for improvements for cellular communication based on communication links enabled on at least two different access technologies.
- the present invention relates to such methods, devices, and computer program products applicable in mobile communication systems operating in cellular network environments, in which a terminal is configured for communication based on multiple radio access technologies, RAT, in relation to mobility robustness optimization.
- a terminal apparatus such as a user equipment UE (or mobile station MS, or the like; different names may apply for respective different standards) is capable of communicating within a cellular network environment.
- a terminal device UE communicates within the network environment in which it is deployed or "camping" based on an available system configuration, generally adopted by a serving network transceiver station (e.g. base station BS or NodeB, or evolved NodeB, eNB) and related network architecture.
- a serving network transceiver station e.g. base station BS or NodeB, or evolved NodeB, eNB
- terminals need to be "backward compatible" as in some areas, the most recent communication network technology is not yet installed to provide for seamless coverage using that technology.
- terminals need to be able to support different radio access technologies, e.g. one or more of GSM (2G), UMTS (3G), LTE (4G), LTE-A, or the like, or also WiMax, WLAN, etc.
- Those terminals are hereinafter referred to as multi-RAT capable terminals.
- the terminal may be served by different network transceiver devices eNBs of potentially different RATs over time.
- the terminal needs to be handed over (HO, Handover) from an initially serving network transceiver device (source RAT) to a target network transceiver device of potentially another RAT (which, upon handover, becomes the new serving network transceiver device).
- SON Self Optimizing Networks
- MRO Mobility Robustness Optimization
- the target of MRO is to automate the optimization of those network configuration parameters, which are triggering a handover (e.g. events, event thresholds used to conclude on a presence of an "event", timers, etc.) such that radio link failures (RLF) and handover failures (HOF) are reduced.
- a handover e.g. events, event thresholds used to conclude on a presence of an "event", timers, etc.
- RLF radio link failures
- HAF handover failures
- the MRO procedure consists of two phases: 1 ) root cause analysis (RCA) phase,
- radio link failure or handover failure (RLF/HOF) is analyzed in detail, and the cell which is responsible for this failure is detected. Finally, this "guilty" cell is collecting the failure events and generates cell or cell-pair specific key
- KPI performance indicator
- the KPI statistics built over certain time interval are evaluated and based on that the corresponding mobility parameters of this cell are adjusted.
- the present invention deals with the root cause analysis phase for the inter-RAT MRO procedure, considering solutions currently discussed in 3GPP, where RLF reporting and root cause analysis should be carried on LTE side only (one optional solution discussed in R3-1 20912, LS to
- RAN2 "Report email#04 Inter-RAT mobility failure", 3GPP TSG-RAN WG3#75-bis, San Jose del Cabo, Mexico, March 2012.) That is, another network/other RAT is not intended to be involved in MRO.
- the MRO concept as specified in Rel'9 and Rel'10 is based on information elements provided with the "RRC connection re-establishment request" message where connection can easily be re-activated, and based on the RLF report which contains additional information to allow the identification of coverage holes and mobility failures without a subsequent "RRC connection re-establishment request" but reconnection from RRCJDLE state.
- RRCConnectionReestablishmentComplete only; but with Rel'10, rlf-lnfoAvailable is sent by the UE also in RRCConnectionSetupComplete and
- the RLF report contains following information: failedPCellld (ECGI(1 )), i.e. the ID of the cell where RLF/HOF occurred reestablishmentCellld (ECGI(2)), i.e. the ID of the cell in which the re- establishment attempt was made after connection failure
- connectionFailureType i.e. one or both of ⁇ RLF / HOF ⁇
- timeConnFailure i.e. the time elapsed since the last HO initialization until connection failure (RLF/HOF) previousPCellld (ECGI(3)), i.e. the ECGI of the source cell from where the UE received last HO command (i.e. RRCConnectionReconfiguration w/ mobilityControllnfo)
- RLF/HOF connection failure
- ECGI(3) i.e. the ECGI of the source cell from where the UE received last HO command
- RRCConnectionReconfiguration w/ mobilityControllnfo
- the most prominent inter-RAT mobility failure cases are "Late inter-RAT LTE-to- 3G" and "Too early 3G-to-LTE", which are related to the limited LTE coverage deployment scenario mentioned above. For both cases, the connection failure occurs in LTE, and the UE is re-connecting to a 3G cell after failure and
- a problem is that the information about re-connection to another RAT in between (before reconnecting to LTE/4G) and the corresponding cell ID of the cell to which reconnection is performed in the other RAT, is missing in RLF report. Though it contains the information about reestablishmentCellld, this does not help, since re-establishment is an intra-LTE process that obviously failed or was not executed.
- the RLF report does not have information that the UE was connected to another RAT in between.
- Measurements provided with the RLF report can be checked and if there are good signal strength measurements relating to such another RAT, there is a certain probability that the connection failure was caused by a missed inter-RAT HO.
- the other-RAT related measurements recorded in the RLF report can be used to conclude that the other RAT's coverage continuity has been missed.
- a multi-mode terminal is enabled in terms of multiple RATs. Each of such modes may thus be considered as representing a RAT.
- each other RAT or mode is sometimes also referred to as "other-RAT.
- so-called other-RAT measurements pertain to
- a computer program product as defined in claim 9, comprising computer-executable components which, when the program is run on a computer, are configured to perform the method aspects as indicated above.
- the above computer program product/products may be embodied as a computer-readable storage medium.
- changes to be applied can be limited to terminals mainly, and can be configured easily as software/firmware to the terminals;
- FIGURE 1 illustrates a block circuit diagram of a multi-RAT capable terminal UE
- FIGURE 2 illustrates an example of flowchart of processing as performed in an example embodiment by the terminal UE.
- FIGURE 1 illustrates a block circuit diagram of a multi-RAT capable terminal UE. It has to be noted that aspects of this invention are implemented in, at least under an exemplary aspect, a terminal apparatus such as a UE 10a, or in a part thereof such as a device 1 1 a of the UE. A corresponding block circuit diagram of a terminal UE is shown in Fig. 1 .
- Such device 1 1 a can be a chip or chipset, or another subunit of the apparatus 10a, or the like.
- the device 1 1 a comprises at least a memory module, MEM, 1 1 1 a in which software code portions and/or data (e.g. measurement data, event data, etc.) is stored or are stored.
- the memory module 1 1 1 a is connected to a control module 1 12a such as a processor, or CPU, or ASIC.
- the control module 1 12a comprises a timer and the module 1 12a is connected to a transceiver module 1 13a.
- the transceiver module 1 13a is configured for communication based on multiple RATs, i.e. configured for the associated service such as LTE, or LTE-A, UMTS, GSM, via network entities such as network transceiver devices with other terminals.
- the present invention can be represented as a device or method or computer program product.
- such method comprises to provide for cellular communication based on communication links enabled on at least two different access technologies, e.g. LTE and non-LTE (such as UMTS, GSM, WLAN, etc.). It is detected a first event, i.e. a connection failure, e.g. RLF, on a communication link established using a first, i.e. LTE, access technology.
- a counting of time is started. This can be software based or in a hardware implementation rely on the timer shown in Fig. 1 .
- a second event i.e. a first re- connection after the first (failure) event is discerned or discovered.
- the counting of time/the timer is stopped or suspended.
- a report i.e. RLF report, is composed, wherein the report includes at least an information element indicative of the counted time.
- the report in case the second event relates to a communication link established using (again) the first access technology (i.e. again LTE) and in case the counted time is smaller than a threshold value (timer did not expire), the report includes an information element indicative that the second event occurred with a tolerable delay.
- the second event in case the second event relates to a communication link established using (again) the first access technology (i.e. again LTE) and in case the counted time is smaller than a threshold value (timer did not expire), the report includes an information element indicative that the second event occurred with a tolerable delay.
- This also represents a situation that an intra-LTE failure and reconnection occurred "immediately", i.e. within tolerable delay.
- the report in case the counted time is greater than or equal than a threshold value (timer expired), the report includes an information element indicative that the second event occurred with an intolerable delay. This also represents a situation that an intra-LTE failure and reconnection occurred "late", i.e. not within a tolerable delay. And, in a further scenario, in case the second event relates to a communication link established using the second access technology, i.e. e.g. UMTS / 3G (rather than LTE), the report includes an information element indicative of the counted time and an (additional) information element indicative of a network and/or corresponding cell in which the second event occurred.
- the second access technology i.e. e.g. UMTS / 3G (rather than LTE
- IE additional information element
- a corresponding device comprising a transceiver module providing for cellular communication based on communication links enabled on at least two different access technologies, and a control module, wherein the control module is configured to achieve the above outlined method aspects.
- the present invention in a first example embodiment may basically consist of two aspects:
- a timer is provided for on UE side which measures the time elapsed between RLF and a first reconnection after RLF. Normally the UE sends a RRC Connection Request message to perform a Tracking Area Update (TAU) initiated by the NAS signaling connection recovery. This will be requested by the UE's lower layers after an "RRC Connection failure", if no signaling link is available or if user uplink data is pending.
- TAU Tracking Area Update
- the timer enables to detect if reconnection was not done immediately and in that case other-RAT coverage continuity cannot be assumed, i.e. it helps in terms of RCA to reveal that the connection failure was not an inter- RAT mobility failure.
- a RRC connection with UTRAN after connection failure (called “reconnection” for sake of simplicity) can be interpreted as successful already with the ability to send the RRC Connection Request message to a UMTS cell and UE takes this as trigger to stop the timer or UE waits also for reaction from UTRAN, namely getting either the RRC Connection Setup or RRC Connection Reject message that indicates a successful reconnection and takes this as trigger to stop the timer.
- an RLF report is extended by the UE by inserting, in this example embodiment, two additional information elements (IE):
- firstReconnectionCellld which contains Cell information (incl. RAT/PLMN info, etc.) where UE has reconnected first after the RLF.
- the present invention in a second example embodiment may basically consist of the following aspects:
- aspects of the invention are implemented in a multi mode LTE/3G/2G-capable UE.
- the UE starts a new timer "t unconn" when it experiences a RLF.
- UE checks if the timer t_unconn is still running. If yes, the timer is stopped and an immediate re-connection after connection failure can be concluded.
- the UE has two options to record the information of an immediate reconnection, namely either by storing the elapsed time or by storing an information element which expresses the matter of reconnection, e.g. ENUM ⁇ immediately; late ⁇ insofar representing a reconnection type; "Immediate” denoting that the timer was not elapsed when reconnection happened, and "late” denoting that the timer elapsed upon reconnection.
- ENUM ⁇ immediately
- late ⁇ insofar representing a reconnection type
- “Immediate” denoting that the timer was not elapsed when reconnection happened
- late denoting that the timer elapsed upon reconnection.
- the RLF report needs only be extended if the UE has reconnected first after the RLF to a non-LTE RAN, and "failedPCellld" is a LTE cell. In that case, UE adds the lEs
- FIG. 2 One potential implementation for the above third example embodiment is represented in the flow chart of Fig. 2, illustrating a processing as performed by the terminal UE.
- Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic.
- the software, application logic and/or hardware generally reside on a memory module.
- a memory module may be a volatile or non-volatile memory module, such as a RAM, ROM, EPROM, EEPROM, or harddisk, or the like.
- a "computer-readable medium” may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or smart phone, or user equipment, or network device such as an evolved NodeB eNB, whether macro or pico eNB.
- the present invention relates in particular but without limitation to mobile communications, for example to environments under LTE, LTE-A, and 3G/UMTS and subsequent releases thereof and can advantageously be implemented in user equipments or smart phones, or personal computers connectable to such networks.
- Particular usefulness will be exhibited for terminals or devices that are multi-RAT enabled, i.e. can operate using multiple radio access technologies. That is, it can be implemented as/in chipsets to connected devices, and/or modems thereof. More generally, all products which are subject to a similar environment will see performance improvement with the invention being
- the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.
- the present invention proposes, under a terminal device aspect, a device, a transceiver module providing for cellular communication based on communication i o links enabled on at least two different access technologies, and a control module, wherein the control module is configured to detect a first event (connection failure, e.g. RLF) on a communication link established using a first (LTE) access technology, start, triggered by the detection, a timer, discern a second event (reconnect) related to a communication link established after the first event and using
- a first event connection failure, e.g. RLF
- LTE first
- RLF report a report
- the report includes at least an information element indicative of the time counted by the timer.
- the present invention encompasses corresponding methods and respective computer program products.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
METHOD, DEVICE AND COMPUTER PROGRAM FOR REPORTING RADIO LINK FAILURES (RLF) FOR CELLULAR COMMUNICATION BASED ON COMMUNICATION LINKS ENABLED ON AT LEAST TWO DIFFERENT ACCESS TECHNOLOGIES
Field of the invention
The present invention relates to methods, devices and computer program products for improvements for cellular communication based on communication links enabled on at least two different access technologies. In particular, the present invention relates to such methods, devices, and computer program products applicable in mobile communication systems operating in cellular network environments, in which a terminal is configured for communication based on multiple radio access technologies, RAT, in relation to mobility robustness optimization.
Background Mobile data transmission and data services are constantly making progress. With the increasing penetration of such services, a terminal apparatus such as a user equipment UE (or mobile station MS, or the like; different names may apply for respective different standards) is capable of communicating within a cellular network environment. For example, a terminal device UE communicates within the network environment in which it is deployed or "camping" based on an available system configuration, generally adopted by a serving network transceiver station (e.g. base station BS or NodeB, or evolved NodeB, eNB) and related network architecture. Also, with the progress in communication, terminals need to be "backward compatible" as in some areas, the most recent communication network technology is not yet installed to provide for seamless coverage using that technology. Insofar, terminals need to be able to support different radio access technologies, e.g. one or more of GSM (2G), UMTS (3G), LTE (4G), LTE-A, or the like, or also WiMax, WLAN, etc. Those terminals are hereinafter referred to as multi-RAT capable terminals.
In the following, aspects of the invention will be exemplarily described with reference to such a scenario. In order to enhance legibility and understandability of the invention, for explanatory purposes only, reference is made to the
communication system of LTE or LTE-A (Long Term Evolution, LTE-Advanced). However, reference to such specific system and use of specific signaling names or channel names or names of entities constituting such a communication network or partial network environment is not intended to limit the present invention to those specific examples. Rather, the principles of the present invention can be transferred to any other communication system adopting different
channel/signaling/entity names as compared to LTE/LTE-A.
In case of a (multi-RAT capable) terminal such as a UE communicating in such an environment while being "mobile" and thus moving within the network environment and the coverage of one or more radio access networks (RANs) being based on different radio access technologies (RAT), and respective cells thereof, the terminal may be served by different network transceiver devices eNBs of potentially different RATs over time. In order to change the serving network transceiver device, the terminal needs to be handed over (HO, Handover) from an initially serving network transceiver device (source RAT) to a target network transceiver device of potentially another RAT (which, upon handover, becomes the new serving network transceiver device). More precisely, the technical field is mobile radio communications with focus on SON (Self Optimizing Networks), and in particular MRO (Mobility Robustness Optimization). SON has become a standard relevant aspect with 3GPP Rel 8 (standardization of E-UTRA, evolved universal terrestrial radio access) and is now with Rel'1 1 focusing on inter-RAT MRO, i.e. MRO between different RATs.
Traditionally, the optimization of network configuration parameters is based on labor- and cost-intensive drive testing. For the first roll-out, network-wide default configuration parameters are used, and if performance management (PM) counters are accumulating radio link failures (RLFs) or even call drops in certain service areas of a network, several optimization loops with drive testing are started to adapt parameters in a cell-specific manner.
The target of MRO is to automate the optimization of those network configuration parameters, which are triggering a handover (e.g. events, event thresholds used to conclude on a presence of an "event", timers, etc.) such that radio link failures (RLF) and handover failures (HOF) are reduced.
The MRO procedure consists of two phases:
1 ) root cause analysis (RCA) phase,
In which radio link failure or handover failure (RLF/HOF) is analyzed in detail, and the cell which is responsible for this failure is detected. Finally, this "guilty" cell is collecting the failure events and generates cell or cell-pair specific key
performance indicator (KPI) statistics.
2) correction phase,
The KPI statistics built over certain time interval are evaluated and based on that the corresponding mobility parameters of this cell are adjusted.
The present invention to be described herein below deals with the root cause analysis phase for the inter-RAT MRO procedure, considering solutions currently discussed in 3GPP, where RLF reporting and root cause analysis should be carried on LTE side only (one optional solution discussed in R3-1 20912, LS to
RAN2 "Report email#04 Inter-RAT mobility failure", 3GPP TSG-RAN WG3#75-bis, San Jose del Cabo, Mexico, March 2012.) That is, another network/other RAT is not intended to be involved in MRO. The MRO concept as specified in Rel'9 and Rel'10 is based on information elements provided with the "RRC connection re-establishment request" message where connection can easily be re-activated, and based on the RLF report which contains additional information to allow the identification of coverage holes and mobility failures without a subsequent "RRC connection re-establishment request" but reconnection from RRCJDLE state.
In Rel'9, the availability of an RLF report is indicated by the UE with
RRCConnectionReestablishmentComplete only; but with Rel'10, rlf-lnfoAvailable is sent by the UE also in RRCConnectionSetupComplete and
RRCConnectionReconfigurationComplete.
In addition to the measurements, the RLF report contains following information: failedPCellld (ECGI(1 )), i.e. the ID of the cell where RLF/HOF occurred reestablishmentCellld (ECGI(2)), i.e. the ID of the cell in which the re- establishment attempt was made after connection failure
connectionFailureType , i.e. one or both of {RLF / HOF}
timeConnFailure, i.e. the time elapsed since the last HO initialization until connection failure (RLF/HOF)
previousPCellld (ECGI(3)), i.e. the ECGI of the source cell from where the UE received last HO command (i.e. RRCConnectionReconfiguration w/ mobilityControllnfo) The most prominent inter-RAT mobility failure cases are "Late inter-RAT LTE-to- 3G" and "Too early 3G-to-LTE", which are related to the limited LTE coverage deployment scenario mentioned above. For both cases, the connection failure occurs in LTE, and the UE is re-connecting to a 3G cell after failure and
RRCJDLE.
A problem, however, is that the information about re-connection to another RAT in between (before reconnecting to LTE/4G) and the corresponding cell ID of the cell to which reconnection is performed in the other RAT, is missing in RLF report. Though it contains the information about reestablishmentCellld, this does not help, since re-establishment is an intra-LTE process that obviously failed or was not executed.
If an RLF report is to be fetched on LTE when UE is coming back (solution with RLF reporting on LTE side only as mentioned above), the RLF report does not have information that the UE was connected to another RAT in between.
Therefore, no information about failed inter-RAT HO is available.
Measurements provided with the RLF report can be checked and if there are good signal strength measurements relating to such another RAT, there is a certain probability that the connection failure was caused by a missed inter-RAT HO.
As mentioned above, the other-RAT related measurements recorded in the RLF report can be used to conclude that the other RAT's coverage continuity has been missed. Note that a multi-mode terminal is enabled in terms of multiple RATs. Each of such modes may thus be considered as representing a RAT. With reference to a particular RAT, each other RAT or mode is sometimes also referred to as "other-RAT. Thus, so-called other-RAT measurements pertain to
measurements conducted with reference to another mode or RAT. But if these measurements are missing in the RLF report, since the inter-RAT measurements have not been triggered, this approach cannot be used.
Namely, inter-RAT measurements are not carried out all the time, since they require transmission gaps to serving cell causing losses in throughput.
The problem to get more detailed knowledge about the RRCJDLE period (e.g. how long was the UE in RRCJDLE after the connection failure) has been also discussed in former standardization meetings with respect to intra-LTE mobility, in particular to avoid sending RLF Indication twice.
The problem which is addressed in this invention report, however, results primarily from the requirement that RLF reporting is done on the LTE side only and up to 48 hours might pass between RLF occurrence and RLF reporting, i.e. there is no information whether and when the UE has been re-connected to another RAT, for instance. Though, it is important to know if a re-connection to another RAT occurred immediately after RLF, since this would indicate that other-RAT coverage was there and inter-RAT mobility should have been happened.
This time aspect, namely the "time elapsed between the connection failure and first successful RRC connection setup after failure", which is considered in this invention, has been already addressed - even though for other reasons - in R3- 102342, Information to be reported in the UE-originated RLF reporting in case of RRC connection setup, 3GPP TSG-RAN3#69, Madrid, August 2010, and R3- 103102, Way forward for RLF reporting in Rel 10, 3GPP TSG-RAN3#69bis, Xian, October 2010.
Thus, there is still a need to further improve such systems in relation to inter-RAT connection failures, so as to enable proper operation of terminals in such scenarios, and hence a need to provide improved methods, devices and computer program products for corresponding terminals.
Summary
Various aspects of examples of the invention are set out in the claims.
According to a first aspect of the present invention, there is provided
a method as defined in claim 1 , and a device as defined in claim 5.
Advantageous further developments of the respective devices / methods are as set out in respective dependent claims.
According to a further aspect of the present invention, there is provided a computer program product as defined in claim 9, comprising computer-executable components which, when the program is run on a computer, are configured to perform the method aspects as indicated above. The above computer program product/products may be embodied as a computer-readable storage medium. Thus, performance improvement is based on methods, devices and computer program products which, in at least exemplary embodiments, adopt an UE which is configured to add additional information to the RLF report, provided there is one, when getting back to the connected mode firstly after the RLF. According to at least exemplary aspects of the invention, one or more of the following advantages can be accomplished:
detection of some inter-RAT mobility failures which otherwise cannot be detected is enabled, and this by virtue of introducing new information elements belonging to a RLF report;
changes to be applied can be limited to terminals mainly, and can be configured easily as software/firmware to the terminals;
a properly working root cause analysis on LTE NW side is allowed for, and an inter-RAT mobility failure can be uniquely detected based on the additional information.
Brief description of drawings
For a more complete understanding of example embodiments of the present invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:
FIGURE 1 illustrates a block circuit diagram of a multi-RAT capable terminal UE;
FIGURE 2 illustrates an example of flowchart of processing as performed in an example embodiment by the terminal UE.
Description of exemplary embodiments
Exemplary aspects / embodiments of the invention will be described herein below.
FIGURE 1 illustrates a block circuit diagram of a multi-RAT capable terminal UE. It has to be noted that aspects of this invention are implemented in, at least under an exemplary aspect, a terminal apparatus such as a UE 10a, or in a part thereof such as a device 1 1 a of the UE. A corresponding block circuit diagram of a terminal UE is shown in Fig. 1 . Such device 1 1 a can be a chip or chipset, or another subunit of the apparatus 10a, or the like. The device 1 1 a comprises at least a memory module, MEM, 1 1 1 a in which software code portions and/or data (e.g. measurement data, event data, etc.) is stored or are stored. The memory module 1 1 1 a is connected to a control module 1 12a such as a processor, or CPU, or ASIC. The control module 1 12a comprises a timer and the module 1 12a is connected to a transceiver module 1 13a. The transceiver module 1 13a is configured for communication based on multiple RATs, i.e. configured for the associated service such as LTE, or LTE-A, UMTS, GSM, via network entities such as network transceiver devices with other terminals.
Note that under an implementation aspect of the invention that is software "centric" rather than hardware "centric", respective modules may even be implemented as corresponding functional means (without departing from the gist of the invention).
Generally, the present invention can be represented as a device or method or computer program product. Generally, such method comprises to provide for cellular communication based on communication links enabled on at least two different access technologies, e.g. LTE and non-LTE (such as UMTS, GSM, WLAN, etc.). It is detected a first event, i.e. a connection failure, e.g. RLF, on a communication link established using a first, i.e. LTE, access technology.
Triggered by the detection, a counting of time is started. This can be software based or in a hardware implementation rely on the timer shown in Fig. 1 . Related to a communication link established after the first event, and using or relying on a first (LTE) or second (non-LTE) access technology, a second event, i.e. a first re- connection after the first (failure) event is discerned or discovered. Triggered by this, the counting of time/the timer is stopped or suspended. Then, a report, i.e. RLF report, is composed, wherein the report includes at least an information element indicative of the counted time.
In one scenario, for example, in case the second event relates to a communication link established using (again) the first access technology (i.e. again LTE) and in case the counted time is smaller than a threshold value (timer did not expire), the report includes an information element indicative that the second event occurred with a tolerable delay. This also represents a situation that an intra-LTE failure and reconnection occurred "immediately", i.e. within tolerable delay.
In another scenario, in case the second event relates to a communication link established using the first access technology and
in case the counted time is greater than or equal than a threshold value (timer expired), the report includes an information element indicative that the second event occurred with an intolerable delay. This also represents a situation that an intra-LTE failure and reconnection occurred "late", i.e. not within a tolerable delay. And, in a further scenario, in case the second event relates to a communication link established using the second access technology, i.e. e.g. UMTS / 3G (rather than LTE), the report includes an information element indicative of the counted time and an (additional) information element indicative of a network and/or corresponding cell in which the second event occurred. The mere presence of the additional information element (IE) can thus be exploited to conclude that an inter RAT reconnection occurred, i.e. after RLF in a first RAT network such as LTE, a reconnection occurred in a second RAT network such as UMTS.
Likewise, the above holds for a corresponding device, comprising a transceiver module providing for cellular communication based on communication links enabled on at least two different access technologies, and a control module, wherein the control module is configured to achieve the above outlined method aspects.
More particularly, the present invention, in a first example embodiment may basically consist of two aspects:
First, a timer is provided for on UE side which measures the time elapsed between RLF and a first reconnection after RLF. Normally the UE sends a RRC Connection Request message to perform a Tracking Area Update (TAU) initiated by the NAS signaling connection recovery. This will be requested by the UE's lower layers after an "RRC Connection failure", if no signaling link is available or if user uplink data is pending. The timer enables to detect if reconnection was not done immediately and in that case other-RAT coverage continuity cannot be assumed,
i.e. it helps in terms of RCA to reveal that the connection failure was not an inter- RAT mobility failure. A RRC connection with UTRAN after connection failure (called "reconnection" for sake of simplicity) can be interpreted as successful already with the ability to send the RRC Connection Request message to a UMTS cell and UE takes this as trigger to stop the timer or UE waits also for reaction from UTRAN, namely getting either the RRC Connection Setup or RRC Connection Reject message that indicates a successful reconnection and takes this as trigger to stop the timer. Second, an RLF report is extended by the UE by inserting, in this example embodiment, two additional information elements (IE):
1 . firstReconnectionCellld, which contains Cell information (incl. RAT/PLMN info, etc.) where UE has reconnected first after the RLF.
2. T unconn (or reconnType)
Indicating the time that elapsed between RLF and reconnection (or alternatively information indicating if predefined timer expired at the UE - this either is a form of an optional flag or enumerated IE)
When UE comes back to LTE and is providing the RLF report there, based on this additional information an inter-RAT mobility failure can be uniquely detected.
Further, the present invention, in a second example embodiment may basically consist of the following aspects:
Aspects of the invention are implemented in a multi mode LTE/3G/2G-capable UE.
The UE starts a new timer "t unconn" when it experiences a RLF. When the UE re-connects from idle mode, UE checks if the timer t_unconn is still running. If yes, the timer is stopped and an immediate re-connection after connection failure can be concluded.
If the timer has already expired before, there was no opportunity to follow TAU requirement and to re-connect as soon as possible, i.e. it can be concluded that there is no inter-RAT mobility failure
In all example embodiments (the general, this first and/or the second), the UE has two options to record the information of an immediate reconnection, namely either
by storing the elapsed time or by storing an information element which expresses the matter of reconnection, e.g. ENUM {immediately; late} insofar representing a reconnection type; "Immediate" denoting that the timer was not elapsed when reconnection happened, and "late" denoting that the timer elapsed upon reconnection.
In a further modification (third example embodiment), the RLF report needs only be extended if the UE has reconnected first after the RLF to a non-LTE RAN, and "failedPCellld" is a LTE cell. In that case, UE adds the lEs
"firstReconnectionCellld" and "T unconn" (or "reconnType").
One potential implementation for the above third example embodiment is represented in the flow chart of Fig. 2, illustrating a processing as performed by the terminal UE.
Other systems can benefit also from the principles presented herein as long as they adopt identical or similar properties, e.g. in relation to RLF reports in multi- RAT HO scenarios, Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and/or hardware generally reside on a memory module. A memory module may be a volatile or non-volatile memory module, such as a RAM, ROM, EPROM, EEPROM, or harddisk, or the like. In an example
embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or smart phone, or user equipment, or network device such as an evolved NodeB eNB, whether macro or pico eNB.
The present invention relates in particular but without limitation to mobile communications, for example to environments under LTE, LTE-A, and 3G/UMTS and subsequent releases thereof and can advantageously be implemented in user equipments or smart phones, or personal computers connectable to such networks. Particular usefulness will be exhibited for terminals or devices that are multi-RAT enabled, i.e. can operate using multiple radio access technologies.
That is, it can be implemented as/in chipsets to connected devices, and/or modems thereof. More generally, all products which are subject to a similar environment will see performance improvement with the invention being
implemented thereto.
If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined.
Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.
It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.
List of exemplary abbreviations/acronyms used:
UE user equipment
MS mobile station
BS base station
eNB evolved NodeB / enhanced NodeB
LTE Long Term Evolution
LTE-A LTE-Advanced
HO Handover
DL Downlink
UL Uplink
3GPP 3rd Generation Partnership Project
RRC Radio Resource Control
SON Self Optimizing Networks
MRO Mobility Robustness Optimization
RLF Radio Link Failure
HOF Handover Failure
RCA Root Cause Analysis
IE Information Element
TAU Tracking Area Update
KPI Key Performance Indicator
RAT Radio Access Technology
5 OAM Operation, Administration and Maintenance
ECGI E-UTRAN Cell Global Identification
The present invention proposes, under a terminal device aspect, a device, a transceiver module providing for cellular communication based on communication i o links enabled on at least two different access technologies, and a control module, wherein the control module is configured to detect a first event (connection failure, e.g. RLF) on a communication link established using a first (LTE) access technology, start, triggered by the detection, a timer, discern a second event (reconnect) related to a communication link established after the first event and using
15 a first (LTE) or second (non-LTE) access technology, stop, triggered by the
discerning, the timer, compose a report (RLF report), wherein the report includes at least an information element indicative of the time counted by the timer.
Likewise, the present invention encompasses corresponding methods and respective computer program products.
20
Claims
1 . A method, comprising:
providing for cellular communication based on communication links enabled on at least two different access technologies,
detecting a first event on a communication link established using a first access technology,
starting, triggered by the detecting, a counting of time,
discerning a second event related to a communication link established after the first event and using a first or second access technology,
stopping, triggered by the discerning, the counting of time,
composing a report, wherein the report includes at least an information element indicative of the counted time.
2. A method according to claim 1 , wherein
in case the second event relates to a communication link established using the first access technology and
in case the counted time is smaller than a threshold value,
the report includes an information element indicative that the second event occurred with a tolerable delay.
3. A method according to claim 1 , wherein
in case the second event relates to a communication link established using the first access technology and
in case the counted time is greater than or equal than a threshold value, the report includes an information element indicative that the second event occurred with an intolerable delay.
4. A method according to claim 1 , wherein
in case the second event relates to a communication link established using the second access technology,
the report includes an information element indicative of the counted time and an information element indicative of a network and/or corresponding cell in which the second event occurred.
5. A device, comprising
a transceiver module providing for cellular communication based on
communication links enabled on at least two different access technologies, and
a control module,
wherein the control module is configured to
detect a first event on a communication link established using a first access technology,
start, triggered by the detection, a timer,
discern a second event related to a communication link established after the first event and using a first or second access technology,
stop, triggered by the discerning, the timer,
compose a report, wherein the report includes at least an information element indicative of the time counted by the timer.
6. A device according to claim 5, wherein
in case the second event relates to a communication link established using the first access technology and
in case the time counted by the timer is smaller than a threshold value,
the report is composed to include an information element indicative that the second event occurred with a tolerable delay.
7. A device according to claim 5, wherein
in case the second event relates to a communication link established using the first access technology and
in case the time counted by the timer is greater than or equal than a threshold value,
the report is composed to include an information element indicative that the second event occurred with an intolerable delay.
8. A device according to claim 5, wherein
in case the second event relates to a communication link established using the second access technology,
the report is composed to include an information element indicative of the time counted by the timer and an information element indicative of a network and/or corresponding cell in which the second event occurred.
9. A computer program product comprising computer-executable components which, when the program is run on a computer, are configured to perform the method steps according to any of claims 1 to 4.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP12721809.7A EP2848076A1 (en) | 2012-05-11 | 2012-05-11 | Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies |
| CN201280073094.4A CN104303584A (en) | 2012-05-11 | 2012-05-11 | Method, device and computer program for reporting radio link failures (RLF) for cellular communication based on communication links enabled on at least two different access technologies |
| US14/399,236 US20150131454A1 (en) | 2012-05-11 | 2012-05-11 | Method, Device and Computer Program for Reporting Radio Link Failures (RLF) for Cellular Communication Based on Communication Links Enabled on at Least Two Different Access Technologies |
| PCT/EP2012/058815 WO2013167204A1 (en) | 2012-05-11 | 2012-05-11 | Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/EP2012/058815 WO2013167204A1 (en) | 2012-05-11 | 2012-05-11 | Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2013167204A1 true WO2013167204A1 (en) | 2013-11-14 |
Family
ID=46124324
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/EP2012/058815 Ceased WO2013167204A1 (en) | 2012-05-11 | 2012-05-11 | Method, device and computer program for reporting radio link failures (rlf) for cellular communication based on communication links enabled on at least two different access technologies |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US20150131454A1 (en) |
| EP (1) | EP2848076A1 (en) |
| CN (1) | CN104303584A (en) |
| WO (1) | WO2013167204A1 (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015075501A1 (en) * | 2013-11-19 | 2015-05-28 | Nokia Technologies Oy | Apparatuses, methods, and computer program products for identifying handover failure modes |
| CN107864487A (en) * | 2017-10-20 | 2018-03-30 | 广东欧珀移动通信有限公司 | The method and Related product of detection terminal call |
| WO2019079020A3 (en) * | 2017-10-18 | 2019-12-05 | Qualcomm Incorporated | Voice call management techniques in wireless communications |
| WO2021051406A1 (en) * | 2019-09-20 | 2021-03-25 | Nokia Shanghai Bell Co., Ltd. | Failure detection in wireless system |
| CN115088297A (en) * | 2022-05-16 | 2022-09-20 | 北京小米移动软件有限公司 | Reporting method and device |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9661510B2 (en) * | 2012-03-30 | 2017-05-23 | Mediatek Inc. | Failure event report extension for inter-RAT radio link failure |
| CN104039023B (en) * | 2013-03-05 | 2018-05-22 | 电信科学技术研究院 | A kind of method and user equipment for carrying out RRC connection reconstructions |
| WO2016003199A1 (en) * | 2014-07-01 | 2016-01-07 | 엘지전자 주식회사 | Method for performing d2d communication in wireless communication system and device therefor |
| WO2017025773A1 (en) * | 2015-08-07 | 2017-02-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Root cause analysis of call failures in a communication network |
| US10165457B2 (en) | 2015-08-07 | 2018-12-25 | Telefonaktiebolaget Lm Ericsson (Publ) | System and method for root cause analysis of call failures in a communication network |
| CN110972177B (en) * | 2018-09-28 | 2022-10-11 | 华为技术有限公司 | Link detection method and device |
| CN112399503B (en) * | 2019-08-16 | 2022-05-13 | 华为技术有限公司 | Method and device for transmitting link failure report |
| US12342411B2 (en) * | 2019-12-18 | 2025-06-24 | Qualcomm Incorporated | Fast connection release after paging response |
| CN113498104A (en) * | 2020-04-08 | 2021-10-12 | 大唐移动通信设备有限公司 | Method for reporting and acquiring radio link failure information, terminal and network side equipment |
| US12143836B2 (en) * | 2022-05-10 | 2024-11-12 | T-Mobile Innovations Llc | Optimization of device configuration relating to wireless access technologies |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100165836A1 (en) * | 2007-06-13 | 2010-07-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for Handling Radio Link Failure in a Communication Network |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6611867B1 (en) * | 1999-08-31 | 2003-08-26 | Accenture Llp | System, method and article of manufacture for implementing a hybrid network |
| JP4433001B2 (en) * | 2007-06-15 | 2010-03-17 | 株式会社カシオ日立モバイルコミュニケーションズ | Communication terminal device and program |
| CN102348254B (en) * | 2011-10-11 | 2014-06-04 | 电信科学技术研究院 | Access control method, system and device |
-
2012
- 2012-05-11 EP EP12721809.7A patent/EP2848076A1/en not_active Withdrawn
- 2012-05-11 US US14/399,236 patent/US20150131454A1/en not_active Abandoned
- 2012-05-11 CN CN201280073094.4A patent/CN104303584A/en active Pending
- 2012-05-11 WO PCT/EP2012/058815 patent/WO2013167204A1/en not_active Ceased
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100165836A1 (en) * | 2007-06-13 | 2010-07-01 | Telefonaktiebolaget Lm Ericsson (Publ) | Technique for Handling Radio Link Failure in a Communication Network |
Non-Patent Citations (2)
| Title |
|---|
| ALCATEL-LUCENT: "3GPP TSG RAN WG3 Meeting #74; R3-112973; Options and prioritisation of Rel-11 MRO enhancements", 3GPP DRAFT; R3-112973, 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; 20111114 - 20111118, 4 November 2011 (2011-11-04), pages 1 - 3, XP050566145 * |
| NOKIA SIEMENS NETWORKS: "3GPP TSG RAN WG3 Meeting #68; R3-101644; Enabling MRO in case of re-establishment request in unprepared eNB", 3GPP DRAFT; R3-101644 SON_MRO_IDLE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Montreal, Canada; 20100510, 1 May 2010 (2010-05-01), pages 1 - 4, XP050425385 * |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10791483B2 (en) | 2013-11-19 | 2020-09-29 | Nokia Technologies Oy | Apparatuses, methods and computer program products for identifying handover failure modes |
| WO2015075501A1 (en) * | 2013-11-19 | 2015-05-28 | Nokia Technologies Oy | Apparatuses, methods, and computer program products for identifying handover failure modes |
| CN105745960A (en) * | 2013-11-19 | 2016-07-06 | 诺基亚技术有限公司 | Apparatuses, methods, and computer program products for identifying handover failure modes |
| CN105745960B (en) * | 2013-11-19 | 2019-05-28 | 诺基亚技术有限公司 | Apparatus, method, and computer-readable storage medium for identifying switching failure modes |
| CN111226495B (en) * | 2017-10-18 | 2024-05-28 | 高通股份有限公司 | Voice call management techniques in wireless communications |
| CN111226495A (en) * | 2017-10-18 | 2020-06-02 | 高通股份有限公司 | Techniques for voice call management in wireless communications |
| WO2019079020A3 (en) * | 2017-10-18 | 2019-12-05 | Qualcomm Incorporated | Voice call management techniques in wireless communications |
| US11006327B2 (en) | 2017-10-18 | 2021-05-11 | Qualcomm Incorporated | Voice call management techniques in wireless communications |
| CN107864487B (en) * | 2017-10-20 | 2021-04-23 | Oppo广东移动通信有限公司 | Method for detecting terminal call and related products |
| CN107864487A (en) * | 2017-10-20 | 2018-03-30 | 广东欧珀移动通信有限公司 | The method and Related product of detection terminal call |
| CN114287167A (en) * | 2019-09-20 | 2022-04-05 | 上海诺基亚贝尔股份有限公司 | Fault detection in wireless systems |
| WO2021051406A1 (en) * | 2019-09-20 | 2021-03-25 | Nokia Shanghai Bell Co., Ltd. | Failure detection in wireless system |
| CN114287167B (en) * | 2019-09-20 | 2024-05-28 | 上海诺基亚贝尔股份有限公司 | Fault Detection in Wireless Systems |
| CN115088297A (en) * | 2022-05-16 | 2022-09-20 | 北京小米移动软件有限公司 | Reporting method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104303584A (en) | 2015-01-21 |
| US20150131454A1 (en) | 2015-05-14 |
| EP2848076A1 (en) | 2015-03-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20150131454A1 (en) | Method, Device and Computer Program for Reporting Radio Link Failures (RLF) for Cellular Communication Based on Communication Links Enabled on at Least Two Different Access Technologies | |
| US9167447B2 (en) | Failure event report for initial connection setup failure | |
| US11665599B2 (en) | Light-weight RRC connection setup in multi-rat network | |
| US9661510B2 (en) | Failure event report extension for inter-RAT radio link failure | |
| US9596616B2 (en) | Enhancement on radio link failure report to record necessary timing details for a dual-threshold handover trigger event | |
| EP2474183B1 (en) | Method for providing information in a cellular wireless communication system | |
| US8412181B2 (en) | Mobile station | |
| US20140050197A1 (en) | Method for Providing Information in a Cellular Wireless Communication System | |
| US20220377630A1 (en) | Method and apparatus for performing mobility robustness optimization in a handover procedure | |
| CN116648952A (en) | Method and apparatus for mobility robustness optimization | |
| CN112042226A (en) | Base station switching method, equipment and storage medium | |
| CN106465246B (en) | Method and wireless communication device for idle mode mobility management | |
| US20250097797A1 (en) | Methods and apparatuses for mro for pscell change or cpac in nr-u | |
| CN116325905A (en) | Method and device for mobility robustness optimization mechanism for conditional handover process | |
| US20120040673A1 (en) | Method of Handling Measurement Procedure and Related Communication Device | |
| EP3248407B1 (en) | Improvement of coverage hole analysis | |
| CN105072644A (en) | Method of providing information in cellular wireless communication system | |
| US20250212082A1 (en) | Method and apparatus for mobility robustness optimization | |
| CN119032583A (en) | Method and device for evaluating downlink wireless link quality |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12721809 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2012721809 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 14399236 Country of ref document: US |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |