WO2011131221A1 - Procédé et dispositif de traitement de données dans un réseau sans fil - Google Patents

Procédé et dispositif de traitement de données dans un réseau sans fil Download PDF

Info

Publication number
WO2011131221A1
WO2011131221A1 PCT/EP2010/055106 EP2010055106W WO2011131221A1 WO 2011131221 A1 WO2011131221 A1 WO 2011131221A1 EP 2010055106 W EP2010055106 W EP 2010055106W WO 2011131221 A1 WO2011131221 A1 WO 2011131221A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
access technology
radio access
mobile terminal
message
Prior art date
Application number
PCT/EP2010/055106
Other languages
English (en)
Inventor
Richard Waldhauser
Bernhard Wegmann
Ingo Viering
Dirk Rose
Cinzia Gesuina Elena Sartori
Original Assignee
Nokia Siemens Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Priority to PCT/EP2010/055106 priority Critical patent/WO2011131221A1/fr
Publication of WO2011131221A1 publication Critical patent/WO2011131221A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the invention relates to a method and to a device for data processing in a wireless network. Also, a communication system comprising at least one such device is suggested.
  • Radio link failures (RLFs) in an inter-RAT mobility context may have different root causes.
  • the root cause In order to trigger a suitable countermeasure, e.g., in terms of configuration parameter update, the root cause has to be determined.
  • the source base station and the target base station may have different information with regard to the RLF.
  • performance monitoring is merely counting the number of RLFs that are reported by a base station.
  • 2G and 3G networks provide the following means for root cause analysis :
  • dropped call can be traced or stored. Hence, an analysis of such dropped call can be conducted (off-line) at a later time.
  • a handover is prepared by passing all necessary information to the target base station (eNodeB) (e.g., E-RAB attributes and RRC context) .
  • eNodeB target base station
  • the mobile terminal also referred to as user equipment, UE keeps the
  • 3GPP Rel.9 establishes additional messages between the eNodeBs via an X2 interface, which are directed to root cause analysis triggered by an RRC re-establishment request message. This message is sent by the UE and contains information about the physical cell identity (PCI) and the UE identity that was assigned to the UE by the last eNodeB that was serving this UE before the radio link failure occurred.
  • PCI physical cell identity
  • the eNodeB receives the RRC reestablishment request message with a PCI that belongs to a neighbor eNodeB, an "RLF Indication"- message will be sent to the neighbor eNodeB. If the root cause analysis results in a "handover too early" or a
  • the LTE approach cannot be used, because there is no X2 interface and no RRC re-establishment request message.
  • a message is conveyed from a node of a first radio access technology to a node of a second radio access technology.
  • radio access technologies could be: 2G, 3G, LTE access technologies or any access technology as defined in an existing or upcoming mobile communication standard.
  • first radio access technology and the second radio access technology are different.
  • the message can be conveyed between different radio access technologies via a core network.
  • inter-RAT operation may be based on coverage driven, service driven or load balancing driven handover between overlaying radio access networks.
  • the approach provided in particular enables self optimizing networks (SONs) and/or mobility robustness optimization (MRO) for inter-RAT mobility.
  • SONs self optimizing networks
  • MRO mobility robustness optimization
  • One aspect of MRO comprises optimizing network configuration parameters (e.g., handover trigger parameters, handover thresholds or timers) in a way that radio link failures
  • network configuration parameters e.g., handover trigger parameters, handover thresholds or timers
  • the approach suggested further provides a more detailed root cause information.
  • the mobile terminal is connected to the node of the first radio access technology .
  • the mobile terminal may have been connected to the node of the second radio access technology prior to said radio link failure.
  • one of the first or second radio access technology is an LTE access technology and the other is in particular a legacy radio access technology.
  • the legacy radio access technology may be a 2G or a 3G access technology.
  • a root cause analysis of the radio link failure is conducted by the node of the first radio access technology based on information provided by the mobile terminal.
  • the root cause analysis or a portion of a root cause analysis can be conducted by a processing algorithm implemented at the node of the first radio access technology.
  • the root cause analysis referred to herein may be a part of a root cause analysis conducted in a distributed way on
  • the information provided by the mobile terminal comprises at least one of the following:
  • the message conveyed from the node of the first radio access technology to the node of the second radio access technology comprises at least one of the following:
  • the additional information may comprise a result of a pre ⁇ analysis of the root cause conducted by the node of the first radio access technology in particular based on information locally available at this node and/or information provided by the mobile terminal (e.g., measurement results).
  • a root cause analysis is conducted by the node of the second radio access technology based on the message provided.
  • At least one of the following steps is conducted:
  • radio access technology indicating that a handover of the mobile terminal occurred too early
  • radio access technology or to a node of a third radio access technology indicating that a handover of the mobile terminal occurred to the wrong radio access technology;
  • the root cause analysis is conducted by the node of the second radio access technology based on the message provided and based on information locally available.
  • receiving the message from the mobile terminal may use information conveyed by the message and information that is locally available at the node of the first radio access technology, e.g., statistics based on the information of previous radio link failures, in order to decide whether or not the node where the radio link failure occurred (e.g., the node of the second radio access technology) needs to be involved in the root cause analysis.
  • information that is locally available at the node of the first radio access technology e.g., statistics based on the information of previous radio link failures
  • the node of the first radio access technology or the node of the second radio access technology informs at least one other node that served the mobile terminal about a result of the root cause analysis.
  • the node of the first radio access technology may send a message to the node of the second radio access technology (where the radio link failure occurred) if the root cause analysis cannot be conducted merely with
  • the node of the second radio access technology may send a message to another node (e.g., the node of the first access technology or a separate node (which may of the first, the second or a third access technology) if the root cause analysis concluded that the handover was either too late or directed to the wrong radio access technology. If the node of the second radio access technology concludes that the
  • no message may be conveyed to a node of the first, second or third radio access technology .
  • counter measures could be initiated or triggered by any of the nodes and/or a central node or any centralized component, e.g., a management system.
  • a serving radio node can be made aware that there exists a problem that needs to be corrected, but also the information of the cause of the problem can be conveyed to other radio nodes in adjacent radio access technologies RATs within the communication system.
  • mobility parameters of the wireless network are set or changed based on the root cause analysis provided.
  • a processing algorithm can be provided with the node of the respective radio access technology and such processing algorithm may, e.g., update counters for a management plane's monitoring function or issue a notification to a centralized OAM node via interfaces of the management plane.
  • the problem stated above is also solved by a device for data processing in a wireless network comprising a processing unit that is arranged
  • said device is a device of the wireless network, in particular a network node, a base station or a base station controller.
  • processing unit can comprise at least one, in particular several, means that are arranged to execute the steps of the method described herein.
  • the means may be logically or physically separated; in particular several logically separate means could be combined in at least one physical unit.
  • Said processing unit may comprise at least one of the
  • a processor a microcontroller, a hard-wired circuit, an ASIC, an FPGA, a logic device.
  • the solution provided herein further comprises a computer program product directly loadable into a memory of a digital computer, comprising software code portions for performing the steps of the method as described herein.
  • computer-readable medium e.g., storage of any kind, having computer-executable instructions adapted to cause a computer system to perform the method as described herein.
  • Fig.l shows a schematic diagram visualizing a root cause analysis conducted between different RATs based on a radio link failure (RLF)
  • Fig.2 shows a schematic diagram visualizing a next step of the root cause analysis depicted in Fig.l.
  • RLF radio link failure
  • the approach provided herein in particular comprises a root cause analysis for failures occurring in an inter-RAT scenario or operation regarding, e.g., inter-RAT mobility.
  • the root cause analysis can be conducted in a distributed manner by exchanging information between the nodes of the different RATs. Exchanging and combining available information distributed among the nodes involved helps identifying the root cause of a failure and thus initiating a suitable countermeasure .
  • Fig.l shows a schematic diagram visualizing a root cause analysis conducted between different RATs based on a radio link failure (RLF) .
  • RLF radio link failure
  • a UE 101 has an active connection with a RAN node 102. Based on measurement reports from the UE 101 or because of other mobility triggers, the RAN node 102 may decide to initiate a handover procedure for this UE 101 from the RAN node 102 towards a RAN node 103. The reason for such handover may be the UE 101 moving away from the RAN node 102 and approaching the RAN node 103.
  • the UE 10 lexperiences an RLF on the connection with the RAN node 102.
  • the RLF may be caused by any problem during an inter-RAT mobility procedure, e.g., a wrong configuration of inter-RAT handover parameters. Due to the RLF, the active connection between the UE 101 and the RAN node 102 drops. The UE 101 recognizes a strong signal received from the RAN node 103 and selects the RAN node 103 to establish the connection, which has been interrupted by the RLF at the RAN node 102.
  • the UE 101 may then transfer information referred to as
  • the RAN node 102 is a network element of an RAT 104 and the RAN node 103 is a network element of an RAT 105, wherein both RATs 104, 105 are different .
  • the RAN node 103 then conveys a message 107 via a core network 106 to the RAN node 102.
  • the UE 101 further conveys information, referred to as
  • INF_CONTEXT_ACCESS that can be used to identify "UE specific context", referred to as INF_UE_CONTEXT" at the RAN node 102.
  • UE specific context could have been stored at the RAN node 102, wherein the RAN node 102 can be identified by an information (or address) referred to as INF_ADDR_RAT_RLF, which is also conveyed from the UE 101 to the RAN node 103.
  • the information INF_CONTEXT_ACCESS may comprise a cell identity and the identity of the UE 101 that has been assigned to this UE 101 when it was served by that cell.
  • the information INF_CONTEXT_ACCESS may comprise a physical cell identity (PCI) or an evolved cell global identity (ECGI) and a cell radio network
  • PCI physical cell identity
  • ECGI evolved cell global identity
  • C-RNTI temporary identifier
  • the UE 101 may also provide further information, referred to as INF_ADDITIONAL, to the RAN node 103. Such further information
  • INF_ADDITIONAL could be used for analyzing the root cause of the RLF.
  • the information INF_ADDR_RAT_RLF, INF_CONTEXT_ACCESS and INF_ADDITIONAL may be added to an already existing message of a connection establishment or a connection re-establishment procedure or to another (e.g., newly defined) procedure.
  • the information transfer between the UE 101 and RAN node 103 may be conducted by different, in particular separate, messages and/or procedures.
  • the root cause analysis may (at least partially) be conducted by a processing algorithm 108 located at the RAN node 103 based on the information INF_ADDR_RAT_RLF, INF_CONTEXT_ACCESS and (optionally) INF_ADDITIONAL transferred by the UE 101 and information that may be locally available at the RAN node 103, e.g., statistical data from previous root cause analysis in particular related to other UEs.
  • the processing algorithm 108 can conduct a (partial) root cause analysis without the need of further processing algorithms located in other RAT nodes being involved.
  • the processing algorithm may thus, e.g., update counters for a management plane's monitoring function or issue a
  • the processing algorithm 103 may - based on the available information - reach to the conclusion that a processing algorithm 109 located at another RAT's controlling radio node (here: the RAN node 102) is required to perform an efficient root cause analysis with regard to the particular RLF.
  • This RAN node 102 can be identified and thus addressed by the information
  • the information that has to be transferred from the RAN node 103 (i.e. the controlling radio node of the RAT to which the UE 101 established a connection) to the RAN node 102 (i.e. the controlling radio node to which the UE 101 was connected before the RLF occurred) may comprise at least the address information of the sender INF_ADDR_RAT_EST and the
  • the processing algorithm 108 of the RAN node 103 may also add further information INF_ADDITIONAL_0THER_RAT to such message 107 conveyed to the RAN node 102. Said further information
  • INF_ADDITIONAL_0THER_RAT may help analyzing the root cause of the RLF.
  • the information INF_ADDITIONAL conveyed by the UE 101 to the RAN node 103 could be a part of this information INF_ADDITIONAL_0THER_RAT .
  • the processing algorithm 109 in the RAN node 102 (the
  • analyzing node may thus access the UE ' s context
  • INF_CONTEXT_ACCESS conveyed by the message 107.
  • the context information INF_UE_CONTEXT may comprise a set of information, which was needed when the UE 101 was being served by the RAN node 102.
  • INF_UE_CONTEXT was stored at the RAN node 102 when the UE 101 entered (was connected to) the RAN node 102 based on a connected mode mobility activity. As this context information INF_UE_CONTEXT is stored for some time at the RAN node 102 before being deleted, it may still be available when the message 107 arrives from the RAN node 103. The processing algorithm 109 may thus use this context information
  • Fig.2 shows a schematic diagram visualizing a next step of the root cause analysis depicted in Fig.l. Depending on the result of the root cause analysis, it may be necessary
  • the RAT 205 can be the same radio access technology as either the RAT 104 or the RAT 105. Also, the RAT 205 can be different from both RATs 104, 105.
  • the address information INF_ADDRESS_RAT of this RAN node 201 can be retrieved from the UE context INF_UE_CONTEXT .
  • INF_ADDRES_RAT_EST can be informed by the RAN node 102 in case the root cause analysis (conducted by the processing algorithm 109) detects that the handover has been conducted too early.
  • the RAN node 201 identified by the address information INF_ADDRESS_RAT can be informed in case the root cause analysis (conducted by the processing algorithm 109) detects that the handover has been conducted to the wrong RAT.
  • the processing algorithm 109 may decide not to convey any message to another node in case the root cause analysis indicates that the handover has been conducted too late .
  • the processing algorithm 108 at the RAN node 103 may provide a pre-analysis of the root cause of the RLF. Based on this pre-analysis, the processing algorithm 108 may conclude that a local root cause analysis is feasible. In this case, no message 107 needs to be sent.
  • the RAN node 103 conveys the message 107 to the RAN node 102.
  • the processing algorithm 109 of the RAN node 102 performs the root cause analysis using the information conveyed by the message 107 and the (locally available) context information INF_UE_CONTEXT associated with the UE 101.
  • the RAN node which served the UE 101 before the RAN node 102 via a different RAT (compared to the RAT of the RAN node 102), may have to be informed about the result of the root cause analysis (see Fig.2) . Pursuant to such information, countermeasures , e.g., to avoid future RLFs, can be initiated.
  • the messages 107, 203 and 204 shown in Fig.l and Fig.2 are conveyed via the core network 106.
  • RIM RAN Information Management
  • a procedure may comprise one or more messages that can be conveyed between network nodes of the wireless network.
  • the blocks shown in Fig.l and Fig.2 could be implemented by a person skilled in the art as various physical units, wherein the mobile terminal 101 or the RAN nodes 102, 103, 201 could be realized each as at least one logical entity that may be deployed as hardware, program code, e.g., software and/or firmware, running on a processing unit, e.g., a computer, microcontroller, ASIC, FPGA and/or any other logic device.
  • the functionality described herein may be based on an
  • the RAN node mentioned herein could also be referred to as any base station, base transceiver station or base station controller pursuant to any communication standard.
  • the RAN node shown may comprise at least one logical or physical processing unit that is arranged for conveying a message to a node of another radio access technology; this message may be provided pursuant to a radio link failure of a mobile terminal.

Landscapes

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

Abstract

Procédé et dispositif de traitement de données dans un réseau sans fil, caractérisés en ce que, suite à une défaillance de liaison radio d'un terminal mobile, un message est acheminé d'un nœud d'une première technologie d'accès radio (RAT) à un nœud d'une deuxième technologie d'accès radio. Un système de communication muni dudit dispositif est en outre suggéré.
PCT/EP2010/055106 2010-04-19 2010-04-19 Procédé et dispositif de traitement de données dans un réseau sans fil WO2011131221A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/055106 WO2011131221A1 (fr) 2010-04-19 2010-04-19 Procédé et dispositif de traitement de données dans un réseau sans fil

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2010/055106 WO2011131221A1 (fr) 2010-04-19 2010-04-19 Procédé et dispositif de traitement de données dans un réseau sans fil

Publications (1)

Publication Number Publication Date
WO2011131221A1 true WO2011131221A1 (fr) 2011-10-27

Family

ID=43416618

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2010/055106 WO2011131221A1 (fr) 2010-04-19 2010-04-19 Procédé et dispositif de traitement de données dans un réseau sans fil

Country Status (1)

Country Link
WO (1) WO2011131221A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102625365A (zh) * 2012-03-20 2012-08-01 华为技术有限公司 一种用于移动鲁棒性优化和移动负载均衡的方法及基站
WO2013066235A1 (fr) * 2011-11-04 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Procédé et appareil pour exclure des données non de mobilité d'indicateurs de performance clé de mobilité
WO2014019138A1 (fr) * 2012-07-31 2014-02-06 富士通株式会社 Procédé pour l'identification du contexte d'un équipement utilisateur, équipement utilisateur et station de base
CN103686673A (zh) * 2012-09-21 2014-03-26 北京三星通信技术研究有限公司 一种支持指示失败事件给源接入系统的方法
EP2806677A4 (fr) * 2012-01-20 2015-12-09 Fujitsu Ltd Procédé d'analyse d'une cause de défaillance de liaison, et procédé et dispositif d'optimisation du réseau associés
WO2021091298A1 (fr) 2019-11-08 2021-05-14 Samsung Electronics Co., Ltd. Procédé et appareil de prise en charge de l'auto-optimisation dans un système de communication sans fil

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 9)", 3GPP STANDARD; 3GPP TS 36.300, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V9.2.0, 7 January 2010 (2010-01-07), pages 1 - 178, XP050401821 *
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Self-configuring and self-optimizing network (SON) use cases and solutions (Release 9)", 3GPP STANDARD; 3GPP TR 36.902, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V9.1.0, 6 April 2010 (2010-04-06), pages 1 - 22, XP050402483 *
GERAN: "Response to LS on feasibility of using RLF recovery to aid neighbour discovery", 3GPP DRAFT; R3-080023_GP-072012, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Sorrento, Italy; 20080104, 4 January 2008 (2008-01-04), XP050163259 *
QUALCOMM EUROPE: "RLF-based neighbour list optimization", 3GPP DRAFT; R2-080346, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sevilla, Spain; 20080108, 8 January 2008 (2008-01-08), XP050138201 *
RAN3 (HUAWEI ET AL: "Clarification of definitions of HO failure cases", 3GPP DRAFT; 36300_CR0202_(REL-9)_R2-101906_R3-100635, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. San Francisco, USA; 20100222, 4 March 2010 (2010-03-04), XP050422194 *

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013066235A1 (fr) * 2011-11-04 2013-05-10 Telefonaktiebolaget L M Ericsson (Publ) Procédé et appareil pour exclure des données non de mobilité d'indicateurs de performance clé de mobilité
US8738004B2 (en) 2011-11-04 2014-05-27 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for excluding non-mobility data from mobility key performance indicators
EP2806677A4 (fr) * 2012-01-20 2015-12-09 Fujitsu Ltd Procédé d'analyse d'une cause de défaillance de liaison, et procédé et dispositif d'optimisation du réseau associés
CN102625365B (zh) * 2012-03-20 2014-07-30 华为技术有限公司 一种用于移动鲁棒性优化和移动负载均衡的方法及基站
CN102625365A (zh) * 2012-03-20 2012-08-01 华为技术有限公司 一种用于移动鲁棒性优化和移动负载均衡的方法及基站
US9913176B2 (en) 2012-07-31 2018-03-06 Fujitsu Limited UE context identification method, UE and base station
WO2014019138A1 (fr) * 2012-07-31 2014-02-06 富士通株式会社 Procédé pour l'identification du contexte d'un équipement utilisateur, équipement utilisateur et station de base
CN104255057A (zh) * 2012-07-31 2014-12-31 富士通株式会社 用户设备上下文的识别方法、用户设备以及基站
US10609603B2 (en) 2012-09-21 2020-03-31 Samsung Electronics Co., Ltd. Method for supporting indication of a failure event to a source access system
CN110191491B (zh) * 2012-09-21 2022-12-23 北京三星通信技术研究有限公司 一种支持指示失败事件给源接入系统的方法
EP2898722A4 (fr) * 2012-09-21 2016-06-01 Samsung Electronics Co Ltd Procédé de prise en charge de l'indication d'un événement d'échec à un système d'accès source
US10219185B2 (en) 2012-09-21 2019-02-26 Samsung Electronics Co., Ltd. Method for supporting indication of a failure event to a source access system
CN103686673B (zh) * 2012-09-21 2019-06-04 北京三星通信技术研究有限公司 一种支持指示失败事件给源接入系统的方法
CN110191491A (zh) * 2012-09-21 2019-08-30 北京三星通信技术研究有限公司 一种支持指示失败事件给源接入系统的方法
CN103686673A (zh) * 2012-09-21 2014-03-26 北京三星通信技术研究有限公司 一种支持指示失败事件给源接入系统的方法
US9730115B2 (en) 2012-09-21 2017-08-08 Samsung Electronics Co., Ltd. Method for supporting indication of a failure event to a source access system
US11039343B2 (en) 2012-09-21 2021-06-15 Samsung Electronics Co., Ltd. Method for supporting indication of a failure event to a source access system
EP3972341A1 (fr) * 2012-09-21 2022-03-23 Samsung Electronics Co., Ltd. Procédé de prise en charge de l'indication d'un événement d'échec à un système d'accès source
US11659450B2 (en) 2012-09-21 2023-05-23 Samsung Electronics Co., Ltd. Method for supporting indication of a failure event to a source access system
WO2021091298A1 (fr) 2019-11-08 2021-05-14 Samsung Electronics Co., Ltd. Procédé et appareil de prise en charge de l'auto-optimisation dans un système de communication sans fil
EP4038971A4 (fr) * 2019-11-08 2022-11-30 Samsung Electronics Co., Ltd. Procédé et appareil de prise en charge de l'auto-optimisation dans un système de communication sans fil
US11968585B2 (en) 2019-11-08 2024-04-23 Samsung Electronics Co., Ltd. Method and apparatus for supporting self-optimization in a wireless communication system

Similar Documents

Publication Publication Date Title
US11665599B2 (en) Light-weight RRC connection setup in multi-rat network
US8903399B2 (en) Methods and network nodes for detecting short stay handover
EP2783532B1 (fr) Procédé et appareil pour exclure des données de non-mobilité d'indicateurs de performance clé de mobilité
US9479984B2 (en) Method for providing information in a cellular wireless communication system
US20140050197A1 (en) Method for Providing Information in a Cellular Wireless Communication System
JP5978515B2 (ja) 無線リンク障害統計方法、関連する装置、および通信システム
EP2601804B1 (fr) Procédé pour un interfonctionnement auto-optimisé entre des réseaux d'accès radio
US9516533B2 (en) Method for reporting radio link failure information
US9578549B2 (en) Method and apparatus for supporting RLF reason detection or handover failure reason detection
US9867092B2 (en) Detection and inhibition of multiple consecutive inter-RAT ping-pong handovers
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
WO2011131221A1 (fr) Procédé et dispositif de traitement de données dans un réseau sans fil
KR20170121877A (ko) 무선 통신 시스템에서 핸드오버를 지원하는 방법 및 장치
CN103517322B (zh) 用于在蜂窝式无线通信系统中提供信息的方法和装置

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: 10715216

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10715216

Country of ref document: EP

Kind code of ref document: A1