WO2014023817A1 - Rapport d'événements de défaillance d'établissement de connexion (rcef) de commande de ressource radio (rrc) dans une minimalisation journalisée de tests de performances (mdt) - Google Patents

Rapport d'événements de défaillance d'établissement de connexion (rcef) de commande de ressource radio (rrc) dans une minimalisation journalisée de tests de performances (mdt) Download PDF

Info

Publication number
WO2014023817A1
WO2014023817A1 PCT/EP2013/066688 EP2013066688W WO2014023817A1 WO 2014023817 A1 WO2014023817 A1 WO 2014023817A1 EP 2013066688 W EP2013066688 W EP 2013066688W WO 2014023817 A1 WO2014023817 A1 WO 2014023817A1
Authority
WO
WIPO (PCT)
Prior art keywords
rcef
mdt
report
log
processor
Prior art date
Application number
PCT/EP2013/066688
Other languages
English (en)
Inventor
Gyula Bodog
Anatoly ANDRIANOV
Sean Kelley
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
Publication of WO2014023817A1 publication Critical patent/WO2014023817A1/fr

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
    • 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/18—Management of setup rejection or failure

Definitions

  • RRC RADIO RESOURCE CONTROL
  • RRCEF CONNECTION ESTABLISHMENT FAILURE
  • MDT EVENTS REPORTING IN LOGGED MINIMIZATION OF DRIVE TESTS
  • Embodiments of the invention generally relate to wireless communications networks, such as, but not limited to, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) and/or Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN).
  • UMTS Universal Mobile Telecommunications System
  • UTRAN Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • E-UTRAN Evolved UTRAN
  • Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) refers to a communications network including base stations, or Node Bs, and for example radio network controllers (RNC).
  • UTRAN allows for connectivity between the user equipment (UE) and the core network.
  • the RNC provides control functionalities for one or more Node Bs.
  • the RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS).
  • RNS Radio Network Subsystem
  • E-UTRAN enhanced UTRAN
  • eNodeB enhanced Node B
  • LTE Long Term Evolution
  • E-UTRAN refers to improvements of the UMTS through improved efficiency and services, lower costs, and use of new spectrum opportunities.
  • LTE is a 3GPP standard that provides for uplink peak rates of at least 50 megabits per second (Mbps) and downlink peak rates of at least 100 Mbps.
  • LTE supports scalable carrier bandwidths from 20 MHz down to 1 .4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD).
  • FDD Frequency Division Duplexing
  • TDD Time Division Duplexing
  • LTE is also expected to improve spectral efficiency in 3G networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill future needs for high-speed data and media transport in addition to high-capacity voice support. Advantages of LTE are, for example, high throughput, low latency, FDD and TDD support in the same platform, an improved end-user experience, and a simple architecture resulting in low operating costs.
  • LTE-A future international mobile telecommunications advanced
  • LTE-A is directed toward extending and optimizing the 3GPP LTE radio access technologies.
  • a goal of LTE-A is to provide significantly enhanced services by means of higher data rates and lower latency with reduced cost.
  • LTE-A will be a more optimized radio system fulfilling the international telecommunication union-radio (ITU-R) requirements for IMT-Advanced while keeping the backward compatibility.
  • ITU-R international telecommunication union-radio
  • One embodiment is directed to a method including logging, by a user equipment associated with a network, a radio resource control (RRC) connection establishment failure (RCEF) report when an RCEF event occurs.
  • the method may also include combining the RCEF report with a minimization of drive test (MDT) log when a logged MDT session is in progress.
  • RRC radio resource control
  • MDT minimization of drive test
  • Another embodiment is directed to an apparatus including at least one processor and at least one memory comprising computer program code.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to log a radio resource control (RRC) connection establishment failure (RCEF) report when an RCEF event occurs, and to combine the RCEF report with a minimization of drive test (MDT) log when a logged MDT session is in progress.
  • RRC radio resource control
  • MDT minimization of drive test
  • Another embodiment is directed to a computer program embodied on a computer readable medium.
  • the computer program when executed by a processor, is configured to control the processor to perform a process including logging a radio resource control (RRC) connection establishment failure (RCEF) report when an RCEF event occurs.
  • the process may also include combining the RCEF report with a minimization of drive test (MDT) log when a logged MDT session is in progress.
  • Another embodiment is directed to a method including receiving, by an eNB, a minimization of drive test (MDT) log from a user equipment.
  • the method may also include storing the MDT log in a MDT trace record.
  • MDT minimization of drive test
  • Another embodiment is directed to an apparatus including at least one processor and at least one memory comprising computer program code.
  • the at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to receive a minimization of drive test (MDT) log from a user equipment, and to store the MDT log in a MDT trace record.
  • MDT minimization of drive test
  • Another embodiment is directed to a computer program embodied on a computer readable medium.
  • the computer program when executed by a processor, is configured to control the processor to perform a process including receiving a minimization of drive test (MDT) log from a user equipment.
  • the process may also include storing the MDT log in a MDT trace record.
  • MDT minimization of drive test
  • Fig. 1 illustrates a signaling diagram according to one embodiment
  • Fig. 2 illustrates a signaling diagram according to an embodiment
  • Fig. 3 illustrates a signaling diagram according to an embodiment
  • Fig. 4 illustrates a signaling diagram according to an embodiment
  • Fig. 5 illustrates a signaling diagram according to an embodiment
  • Fig. 6 illustrates a block diagram of an apparatus according to one embodiment
  • Fig. 7 illustrates a flow diagram of a method according to one embodiment
  • Fig. 8 illustrates a flow diagram of a method according to another embodiment.
  • Accessibility key performance indicators defined in 3GPP TS 32.450 reflect the quality of the network and may have a clear effect on the user experience.
  • An important goal for operators is to maximize the call success rate and, in turn, minimize the connection establishment failures.
  • the radio resource control (RRC) connection establishment failures reported by the UE (described in section 5.1.6 of TS 37.320) contain the radio conditions and location information at the time the failure happened. Therefore, the RRC connection failure reports are an important input for operators to determine the reasons for degradation in accessibility KPIs.
  • connection failures For analysis of connection failures, the information about the radio conditions of the radio network may be needed when the connection failure occurs. In UTRAN or E- UTRAN, this data can be collected by utilizing the RRC connection establishment failure reports defined in section 5.1 .6 of TS 37.320.
  • the RRC connection establishment failure reports may contain the global cell identity, radio measurements and location information at the time of the connection failure.
  • MDT Minimization of Drive Test
  • CCO Coverage and Capacity Optimization
  • all the different pieces of information connected to the occurrence of the same incident may need to be combined by the CCO function.
  • the MDT, radio link failure (RLF), and connection establishment failure data are reported separately by the user equipment (UE) and collected in separate trace jobs.
  • SA5 implemented the 3GPP SA3 data anonymization requirements in TS 32.422 section 5.10.12, "Anonymization of MDT data.” According to the agreements in SA5, two levels of anonymization are possible: “no identity” (complete anonymization) and “TAC part of IMEI” (only UE type information is retained). Neither of these two levels of anonymization leaves any personally identifiable data required for correlation of multiple data types (such as MDT, RLF, RCEF), as illustrated in Figs. 1 and 2 discussed below.
  • multiple data types such as MDT, RLF, RCEF
  • the MDT has been enhanced by logging the RRC connection establishment failure events (RCEF).
  • RCEF RRC connection establishment failure events
  • the new log may be created whenever the RRC connection establishment procedure fails.
  • the log of RCEF events may contain the following information:
  • the global cell identity of the serving cell when the RRC connection establishment fails i.e., the cell which UE attempted to access.
  • the following information may be included in the log (currently tagged FFS):
  • V300 counter value after receiving ACK and AICH V300 counter value after receiving ACK and AICH
  • number of RRC Connection Request attempts for example, T300 expiry after receiving ACK and AICH
  • indication of probable contention such as mismatch of UE identity in RRC CONNECTION SETUP message
  • the failure cause of RRC CONNECTION establishment failure V300 counter value after receiving ACK and AICH
  • number of RRC Connection Request attempts for example, T300 expiry after receiving ACK and AICH
  • indication of probable contention such as mismatch of UE identity in RRC CONNECTION SETUP message
  • the failure cause of RRC CONNECTION establishment failure the failure cause of RRC CONNECTION establishment failure.
  • RAN WG2 uses an RLF-like reporting mechanism for LTE, where the UE stores just the latest failure and sends an indication in the RAT in which it was recorded so that the network may retrieve it.
  • the UE always logs failed RRC connection establishments, i.e., the network does not explicitly configure this log.
  • a RLF-like reporting mechanism may be used for RCEF data collection in LTE.
  • the RLF-like mechanism implies a new Trace Job type for RCEF data collection from the eNBs (or RNCs in UMTS). There is no configuration required for the UEs to log the RCEF data and no configuration for the eNBs to retrieve the RCEF data from the UEs. The retrieved data can be forwarded to the TCE by those eNBs where
  • RCEF collection Trace Job has been activated.
  • the RCEF collection Trace Job does not provide any personal identifiable information (IMSI is not recorded in RCEF report by the UE and is not available at the eNB) and the Trace Session / Trace Recording Session identifiers may not be sufficient for correlation with MDT data at the TCE.
  • IMSI personal identifiable information
  • Trace Session / Trace Recording Session identifiers may not be sufficient for correlation with MDT data at the TCE.
  • the new report content may have some valuable information for the Coverage and Capacity Optimization (CCO) and, therefore, it should be possible to collect these reports for centralized processing in a manner similar to the RLF collection.
  • CCO Coverage and Capacity Optimization
  • the correlation of MDT data and RLF data (and the new RRC connection failure data) is difficult or even impossible due to strict user privacy and data anonymization requirements imposed on MDT by 3GPP SA WG3, which in turn degrades the value of collected information for the CCO function.
  • embodiments of the invention enable the possibility of reporting the RCEF events as part of a logged MDT procedure. For example, when an RCEF event happens, the RCEF is logged by the UE. Then, according to an embodiment, if a logged MDT session is configured and ongoing at the UE, the UE may store the RCEF related information to the logged MDT (new MDT event) and can report it as part of the logged MDT. In some embodiments, the network can retrieve just the RCEF log from the UE, or can retrieve both the RCEF log and the logged MDT data.
  • RLF and MDT data are important for the area-based MDT jobs. Compared to RLF, RCEF data also has some valuable information for the CCO, and, therefore, correlation mechanisms for RCEF and MDT may also be needed.
  • the main difference between issues with RLF correlation vs. RCEF correlation is that RLF occurs while in connected mode, and RCEF occurs while in the idle mode.
  • the connected mode MDT is "Immediate MDT" where UE reports individual measurements to the eNB, and the eNB stores these in a MDT trace record - there is no opportunity to report the RLF within the Immediate MDT session since the session is interrupted at the RLF.
  • the idle mode MDT is where the UE performs the measurements and logs them in a local file which is later retrieved by the eNB when the UE transitions into connected mode. Accordingly, it is possible for the UE to add the RCEF report (as a new event) to the local UE MDT log if a Logged MDT session is already in progress.
  • the RCEF and MDT data from the same subscriber becomes linked together (in the same Logged MDT Trace Log File) and provides the full picture of the RF environment prior to and at the time of RCEF. Since there is no personally identifiable information present in the MDT log (and in turn in the combined MDT/RCEF log), the 3GPP SA3 requirement is not violated.
  • Embodiments provide several options for the control over the RCEF information reporting.
  • Example solutions include the following possibilities: - Configuration time decision:
  • the UE reports the RCEF event unconditionally in "RLF type" reporting;
  • the UE When logged MDT session is configured at the UE and RCEF type of event is specified in the MDT configuration, the UE reports RCEF event only as part of the MDT log (no duplicate reporting);
  • the UE stores the RCEF report independently of the MDT log. On successful RRC connection establishment, the UE indicates that both the MDT log and RCEF report are available.
  • the network node eNB
  • the network node makes a decision based on the currently configured trace job whether the RCEF report shall be retrieved as part of the MDT log or separately and informs the UE.
  • the UE based on the direction received from the eNB, either sends both the MDT log and RCEF report separately or includes the RCEF in the MDT log as an additional event and sends only MDT log.
  • the benefit of including the RCEF in the MDT log as an additional event is to avoid double reporting of the RCEF related information.
  • the UEInformationResponse message may need to be structured so that if both events are needed by the network, RCEF data is inserted only once and the network may need to have a functionality that the RCEF information is forwarded to the RCEF trace job function and also to the Logged MDT function.
  • a new combined Trace Job type - "RCEF collection + Logged MDT” and an absolute network timestamp (or time elapsed since RCEF event until retrieval) may be included in the RCEF report.
  • both MDT Log and RCEF report will be retrieved by the eNB simultaneously and merged into a single trace file by the eNB.
  • Fig. 1 illustrates an example of a signaling diagram in which the RCEF and MDT are retrieved by the same eNB separately, according to one embodiment.
  • eNB A receives the RCEF report from the UE in a UEInformationResponse.
  • eNB A stores the RCEF report in a trace record at 100.
  • eNB A also receives the MDT log from the UE in a UEInformationResponse.
  • eNB A stores the MDT log in a trace record at 1 10.
  • MDT/RCEF correlation is not possible.
  • Fig. 1 illustrate an eNB in LTE, embodiments are equally applicable to a RNC in UMTS.
  • Fig. 2 illustrates an example of a signaling diagram in which the RCEF and MDT are retrieved by different eNBs, according to an embodiment.
  • eNB A receives the RCEF report from the UE in a UEInformationResponse.
  • eNB A stores the RCEF report in a trace record at 200.
  • eNB B receives the MDT log from the UE in a UEInformationResponse.
  • eNB B stores the MDT log in a trace record at 210.
  • MDT/RCEF correlation is not possible.
  • FIG. 3 illustrates an example of a signaling diagram in which the RCEF and MDT are combined by the UE in the same logged MDT file, according to an embodiment.
  • the UE stores the RCEF report in the MDT log.
  • eNB A receives the MDT log from the UE in a UEInformationResponse and stores the MDT log in a trace record at 310.
  • the MDT/RCEF data are combined.
  • Fig. 4 illustrates an example of a signaling diagram in which the RCEF and MDT are combined by the UE in the same logged MDT file at the request of the eNB, according to an embodiment.
  • the UE in response to the UEInformationRequest from the eNB to retrieve the MDT log combined with RCEF, the UE stores the RCEF report in the MDT log at 400.
  • eNB A receives the MDT log in an UEInformationResponse from the UE and stores the MDT log in a trace record at 410.
  • the MDT/RCEF data are combined.
  • Fig. 5 illustrates an example of a signaling diagram in which the RCEF and MDT are combined by the eNB, according to one embodiment.
  • Fig. 5 illustrates an example of a signaling diagram in which the RCEF and MDT are combined by the eNB, according to one embodiment.
  • Fig. 5 illustrates an example of a signaling diagram in which the RCEF and MDT are combined by the eNB, according to one embodiment.
  • eNB A receives the MDT log from the UE in a UEInformationResponse and stores the MDT log in a MDT trace record at 500. According to this embodiment, eNB A also receives the RCEF report from the UE in a UEInformationResponse and stores the RCEF report in the MDT trace record at 500 thereby combining the RCEF report and MDT log. According to this embodiment, at 520, the MDT/RCEF data are combined.
  • Fig. 6 illustrates an apparatus 10 according to another embodiment.
  • apparatus 10 may be network element, such as an eNB or RNC.
  • apparatus 10 may be a mobile device such as user equipment (UE).
  • UE user equipment
  • Apparatus 10 includes a processor 22 for processing information and executing instructions or operations.
  • Processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 6, multiple processors may be utilized according to other embodiments.
  • processor 22 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors ("DSPs”), field-programmable gate arrays (“FPGAs”), application- specific integrated circuits (“ASICs”), and processors based on a multi-core processor architecture, as examples.
  • DSPs digital signal processors
  • FPGAs field-programmable gate arrays
  • ASICs application- specific integrated circuits
  • Apparatus 10 further includes a memory 14, coupled to processor 22, for storing information and instructions that may be executed by processor 22.
  • Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory.
  • memory 14 can be comprised of any combination of random access memory (“RAM”), read only memory (“ROM”), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media.
  • the instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.
  • Apparatus 10 may also include one or more antennas (not shown) for transmitting and receiving signals and/or data to and from apparatus 10.
  • Apparatus 10 may further include a transceiver 28 that modulates information on to a carrier waveform for transmission by the antenna(s) and demodulates information received via the antenna(s) for further processing by other elements of apparatus 10.
  • transceiver 28 may be capable of transmitting and receiving signals or data directly.
  • Processor 22 may perform functions associated with the operation of apparatus 10 including, without limitation, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources.
  • memory 14 stores software modules that provide functionality when executed by processor 22.
  • the modules may include an operating system 15 that provides operating system functionality for apparatus 10.
  • the memory may also store one or more functional modules 18, such as an application or program, to provide additional functionality for apparatus 10.
  • the components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.
  • apparatus 10 may be a UE as illustrated in Figs. 1 -5 discussed above.
  • apparatus 10 may be controlled by memory 14 and processor 22 to log a RCEF report when an RCEF event occurs.
  • apparatus 10 may then be controlled by memory 14 and processor 22 to add or combine the RCEF report into a MDT log if a logged MDT session is in progress.
  • Apparatus 10 may also be controlled by memory 14 and processor 22 to report the MDT log and/or RCEF report to the network, e.g., to an eNB.
  • the RCEF report is added to the MDT log in response to a request from the eNB (i.e., at the direction of the eNB).
  • apparatus 10 may be an eNB as illustrated in Figs. 1- 5 discussed above, or a RNC in UMTS.
  • apparatus 10 may be controlled by memory 14 and processor 22 to receive a MDT log from a UE, and to store the MDT log in a MDT trace record.
  • apparatus 10 may be further controlled by memory 14 and processor 22 to receive a RCEF report from the UE, and to store or combine the RCEF report in the MDT trace record.
  • Fig. 7 illustrates a flow diagram of a method according to one embodiment. In an embodiment, the method of Fig. 7 may be performed by a UE.
  • the method includes, at 700, logging a RCEF report when an RCEF event occurs.
  • the method may then include, at 710, adding or combining the RCEF report into a MDT log if a logged MDT session is in progress.
  • the method may also include, at 720, reporting the MDT log and/or RCEF report to the network, for example, to an eNB.
  • Fig. 8 illustrates a flow diagram of a method according to one embodiment.
  • the method of Fig. 8 may be performed by an eNB or RNC.
  • the method includes, at 800, receiving a MDT log from a UE, and, at 810, storing the MDT log in a MDT trace record.
  • the method may further include, at 820, receiving a RCEF report from the UE, and, at 830, storing or combining the RCEF report in the MDT trace record.
  • the functionality of any of the methods described herein may be implemented by software and/or computer program code stored in memory or other computer readable or tangible media, and executed by a processor.
  • the functionality may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software.
  • ASIC application specific integrated circuit
  • PGA programmable gate array
  • FPGA field programmable gate array

Landscapes

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

Abstract

La présente invention porte sur un procédé, un appareil, et un produit programme d'ordinateur pour un rapport d'événements de défaillance d'établissement de connexion (RCEF) de commande de ressource radio (RRC) dans une MDT journalisée. Un procédé comprend la journalisation, par un équipement utilisateur associé à un réseau, d'un rapport de défaillance d'établissement de connexion (RCEF) de commande de ressource radio (RRC) lorsqu'un événement RCEF se produit. Le procédé peut comprendre également la combinaison du rapport RCEF avec une minimalisation de journal de test de performances (MDT) lorsqu'une session MDT journalisée est en cours.
PCT/EP2013/066688 2012-08-10 2013-08-09 Rapport d'événements de défaillance d'établissement de connexion (rcef) de commande de ressource radio (rrc) dans une minimalisation journalisée de tests de performances (mdt) WO2014023817A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201261681858P 2012-08-10 2012-08-10
US61/681,858 2012-08-10

Publications (1)

Publication Number Publication Date
WO2014023817A1 true WO2014023817A1 (fr) 2014-02-13

Family

ID=48953394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2013/066688 WO2014023817A1 (fr) 2012-08-10 2013-08-09 Rapport d'événements de défaillance d'établissement de connexion (rcef) de commande de ressource radio (rrc) dans une minimalisation journalisée de tests de performances (mdt)

Country Status (1)

Country Link
WO (1) WO2014023817A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140133465A1 (en) * 2012-11-15 2014-05-15 Mediatek, Inc. Radio Link Failure Report Extensions in Mobile Communication Networks
WO2020125579A1 (fr) * 2018-12-20 2020-06-25 华为技术有限公司 Procédé et appareil de communication
WO2020226336A1 (fr) * 2019-05-03 2020-11-12 Samsung Electronics Co., Ltd. Procédé et ue pour rapporter une mesure d'accessibilité dans un système de communications sans fil
EP3886473A4 (fr) * 2018-12-20 2022-01-19 Huawei Technologies Co., Ltd. Procédé et appareil de communication et système

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110195668A1 (en) * 2010-02-09 2011-08-11 Sung Min Lee Apparatus and method of reporting logged measurement in wireless communication system
US20110250880A1 (en) * 2010-04-12 2011-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Ue-based mdt measuring and reporting in a cellular radio access network
US20120046985A1 (en) * 2007-10-02 2012-02-23 Emergency Response And Training Solutions, Inc. Method for the secure logging of correspondence and notification thereof
GB2487090A (en) * 2011-01-10 2012-07-11 Nec Corp Obtaining user consent for provision of location related data in association with measurement of communication conditions

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120046985A1 (en) * 2007-10-02 2012-02-23 Emergency Response And Training Solutions, Inc. Method for the secure logging of correspondence and notification thereof
US20110195668A1 (en) * 2010-02-09 2011-08-11 Sung Min Lee Apparatus and method of reporting logged measurement in wireless communication system
US20110250880A1 (en) * 2010-04-12 2011-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Ue-based mdt measuring and reporting in a cellular radio access network
GB2487090A (en) * 2011-01-10 2012-07-11 Nec Corp Obtaining user consent for provision of location related data in association with measurement of communication conditions

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "Discussion on RRC Connection Establishment log", 3GPP DRAFT; R2-122141, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Prague, Czech Republic; 20120521 - 20120525, 15 May 2012 (2012-05-15), XP050607149 *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140133465A1 (en) * 2012-11-15 2014-05-15 Mediatek, Inc. Radio Link Failure Report Extensions in Mobile Communication Networks
US9730090B2 (en) * 2012-11-15 2017-08-08 Mediatek, Inc. Radio link failure report extensions in mobile communication networks
US10257723B2 (en) 2012-11-15 2019-04-09 Hfi Innovation Inc. Radio link failure report extensions in mobile communication networks
WO2020125579A1 (fr) * 2018-12-20 2020-06-25 华为技术有限公司 Procédé et appareil de communication
EP3886473A4 (fr) * 2018-12-20 2022-01-19 Huawei Technologies Co., Ltd. Procédé et appareil de communication et système
JP2022515402A (ja) * 2018-12-20 2022-02-18 華為技術有限公司 通信方法、装置、およびシステム
JP7381586B2 (ja) 2018-12-20 2023-11-15 華為技術有限公司 通信方法、装置、およびシステム
WO2020226336A1 (fr) * 2019-05-03 2020-11-12 Samsung Electronics Co., Ltd. Procédé et ue pour rapporter une mesure d'accessibilité dans un système de communications sans fil
CN113796023A (zh) * 2019-05-03 2021-12-14 三星电子株式会社 无线通信系统中报告可接入性测量的方法和ue

Similar Documents

Publication Publication Date Title
US9532255B2 (en) Measurement triggers for customer care in a wireless network
EP2676470B1 (fr) Mesures centrées sur un service pour minimiser les essais de couverture radio
US11606781B2 (en) Method and apparatus for configuring a triggering condition of a beam failure event and a communication system
US20190364443A1 (en) Obtaining additional supported bands of neighbor cells via automatic neighbor relation (anr)
US10098031B2 (en) Reference signal receiving quality reporting method and device
WO2016078969A1 (fr) Signalisation de capacité pour une connectivité double
US20180007605A1 (en) Methods and arrangements for managing radio link failures in a wireless communication network
US20150208228A1 (en) Mobility state estimate (mse) or mobility history information reporting
EP3016312B1 (fr) Dispositif de gestion d'une transmission sur une porteuse de composante sans licence
US20150109939A1 (en) Minimization of drive tests uplink measurements
EP3166354B1 (fr) Changement de mode d'amélioration de couverture pour un équipement utilisateur de couverture améliorée
US20150109973A1 (en) Channel State Information (CSI) Report Subsets Under Flexible Time Division Duplex (TDD) UL/DL Configuration
WO2014023817A1 (fr) Rapport d'événements de défaillance d'établissement de connexion (rcef) de commande de ressource radio (rrc) dans une minimalisation journalisée de tests de performances (mdt)
EP4005282A1 (fr) Commutation de liaison de service de données intelligente entre des modules d'identité d'abonné
US9439117B2 (en) Handover to cell supporting multiple frequency bands
PH12016000353A1 (en) Wireless local area network (wlan) radio link failure (rlf) triggering
WO2017051078A1 (fr) Radiomessagerie pour équipement d'utilisateur à couverture améliorée
WO2022094995A1 (fr) Anonymisation de données permettant la minimisation "drive-test"
US20240187897A1 (en) Controlling of quality of experience measurement
US20220394609A1 (en) Preventing signaling based minimization of drive test configuration overwrite in dual connectivity
WO2022029901A1 (fr) Terminal

Legal Events

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

Ref document number: 13747844

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

Country of ref document: EP

Kind code of ref document: A1