WO2014135061A1 - 一种进行rrc连接重建的方法及用户设备 - Google Patents

一种进行rrc连接重建的方法及用户设备 Download PDF

Info

Publication number
WO2014135061A1
WO2014135061A1 PCT/CN2014/072845 CN2014072845W WO2014135061A1 WO 2014135061 A1 WO2014135061 A1 WO 2014135061A1 CN 2014072845 W CN2014072845 W CN 2014072845W WO 2014135061 A1 WO2014135061 A1 WO 2014135061A1
Authority
WO
WIPO (PCT)
Prior art keywords
cell
rrc connection
network side
information related
connection failure
Prior art date
Application number
PCT/CN2014/072845
Other languages
English (en)
French (fr)
Inventor
刘爱娟
吴昱民
Original Assignee
电信科学技术研究院
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 电信科学技术研究院 filed Critical 电信科学技术研究院
Priority to US14/772,075 priority Critical patent/US10356834B2/en
Priority to EP14760904.4A priority patent/EP2966928A4/en
Publication of WO2014135061A1 publication Critical patent/WO2014135061A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • SON Self-organizing Networks
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • 3GPP Third-generation partner program
  • SON technology includes self-configuration, self-optimization and self-healing, and self-optimization is one of the important features.
  • the SON self-optimization function needs to monitor some network and system performance parameters as input, such as network performance indicator statistics, fault alarms, notifications, etc. After analyzing the input data, the optimization algorithm makes a decision, and finally automatically triggers the adjustment of the relevant network node. operating.
  • MRO Mobility Robustness Optimization
  • Improper switching is usually caused by unreasonable switching parameter settings, including the following:
  • a User Equipment (UE, also called a terminal) generates an RLF before the handover trigger, and then the UE attempts connection reestablishment in another cell different from the source cell.
  • UE User Equipment
  • the RLF occurs quickly or a handover failure (HOF) occurs during the handover, and then the UE attempts connection reestablishment in the source cell.
  • HAF handover failure
  • the criteria for judging handover to the wrong cell are as follows:
  • the UE generates RLF in the RLF (whether in the source cell or the target cell) during handover or after switching to the target cell, and then the UE is in a third-party cell (neither the source cell nor the target cell). Try to connect to rebuild.
  • the RLF of the UE mainly includes the following two reasons: First, the handover parameter is inappropriate, so that the serving cell of the UE is not changed in time, and the signal shield of the serving cell is low enough to provide services, resulting in RLF; the other is the network. Coverage vulnerability or shadow fading in the middle, when the UE moves to a hole or shadow, the RLF is caused by a sharp deterioration of the radio link conditions.
  • the UE needs to obtain information related to the connection failure (RLF or HOF), including the following contents:
  • Measurement information RSRP/RSRQ of the serving cell when RLF occurs and RSRP/RSRQ of the neighboring area.
  • the UE records the above 1, 3, 4, 5, and 6.
  • the RRC RE-ESTABLISHMENT REQUEST message is sent, 2 is recorded.
  • the UE reports the information related to the connection failure that is recorded by the UE to the network side.
  • the network side judges according to the information related to the connection failure reported by the UE. Is the coverage problem or the switching too early/switching too late/switching to the wrong cell due to unreasonable switching parameter settings.
  • the UE records the cell as a reestablished cell.
  • RLF connection failure
  • the UE may not meet the criteria for cell selection or the UE does not receive the RRC reestablishment command sent by the network side after initiating the RRC connection reestablishment request.
  • the UE still carries the identification information of the reestablished cell in the information related to the connection failure reported to the network side, and the network side still considers the rebuilt cell as a suitable cell, and performs MRO judgment and optimization, thereby Optimization of the switching parameters that caused the error.
  • the UE records the cell as a rebuilt cell, and the identification information of the rebuilt cell is 4 ⁇ .
  • the network side performs optimization of the wrong handover parameter.
  • the embodiments of the present application provide a method for performing RRC connection reestablishment, and a user equipment, which is used to solve the problem that a UE that has failed to connect in a RRC connection reestablishment process in a certain cell in the prior art
  • the network side is caused to optimize the erroneous handover parameters.
  • the embodiment of the present application provides a method for performing RRC connection reestablishment, including:
  • the UE that failed the connection initiates an RRC connection reestablishment request in the selected reestablished cell;
  • the UE determines that the information related to the connection failure is saved by itself.
  • the identification information of the reconstructed cell is not carried, or information related to the connection failure is not saved by itself.
  • the UE saves the identifier information of the re-established cell in information related to a connection failure; the UE determines that the re-established cell does not meet the set cell selection.
  • the identifier information of the reestablished cell stored in the information related to the connection failure is deleted.
  • the UE when the re-established cell initiates an RRC connection reestablishment request, the UE does not save the identification information of the re-established cell in the information related to the connection failure.
  • the UE saves the identity information of the reconstructed cell in the information related to the connection failure when the re-established cell initiates the RRC connection reestablishment request; the UE determines that the re-established cell does not meet the set cell selection criterion or When the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received, all information related to the connection failure saved by itself is deleted. Based on any of the foregoing method embodiments, the UE determines that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received by the UE according to the following steps:
  • the UE When the UE initiates an RRC connection reestablishment request to the network side device to which the reestablished cell belongs, the UE starts the configured timer.
  • the UE determines that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received.
  • the embodiment of the present application provides a user equipment, where the user equipment fails to connect, and the user equipment includes:
  • a first processing module configured to initiate an RRC connection reestablishment request in the selected reestablished cell
  • a second processing module configured to determine that the saved and failed connection are determined when the reestablished cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs
  • the related information does not carry the identification information of the reconstructed cell, or does not save any information related to the connection failure.
  • the first processing module is specifically configured to: when the re-establishment cell initiates an RRC connection re-establishment request, save the identifier information of the re-established cell in the information related to the connection failure; the second processing module is specifically configured to: After the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, the identifier information of the reestablished cell saved in the information related to the connection failure is deleted.
  • the first processing module is specifically configured to: when the re-establishment cell initiates the RRC connection reestablishment request, save the identification information of the re-established cell in the information related to the connection failure.
  • the first processing module is specifically configured to: when the re-establishment cell initiates an RRC connection re-establishment request, save the identifier information of the re-established cell in the information related to the connection failure; the second processing module is specifically configured to: After the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, it deletes all information related to the connection failure saved by itself.
  • the second processing module determines that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received by the second processing module according to the following steps:
  • the configured timer is enabled; and when the timer expires, it is determined that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received.
  • the embodiment of the present application provides another user equipment, where the user equipment includes a processor and a radio frequency unit:
  • the processor is configured to: after determining that the UE has failed to connect, initiate an RRC connection reestablishment request by using the radio unit in the selected reestablished cell; determining that the rebuilt cell does not meet the set cell selection criterion or does not receive the
  • the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is determined, the connection saved and the connection are determined to be failed.
  • the related information does not carry the identification information of the reconstructed cell, or does not save any information related to the connection failure.
  • the UE that fails the connection initiates an RRC connection reestablishment request in the selected reestablished cell, and the UE determines that the reestablished cell does not meet the set cell selection criterion or does not receive the network side device to which the reestablished cell belongs.
  • the RRC connection reestablishment command is sent, it is determined that the information related to the connection failure that is saved by the user does not carry the identification information of the reestablished cell, or does not save any information related to the connection failure, thereby avoiding the wrong handover parameter of the network side. optimization.
  • FIG. 1 is a flowchart of a method for performing RRC connection reestablishment according to the present application;
  • Embodiment 1 is a schematic flow chart of Embodiment 1 provided by the present application.
  • Embodiment 3 is a schematic flowchart of Embodiment 2 provided by the present application.
  • Embodiment 4 is a schematic flow chart of Embodiment 3 provided by the present application.
  • FIG. 5 is a schematic flowchart diagram of Embodiment 4 provided by the present application.
  • Embodiment 6 is a schematic flowchart of Embodiment 5 provided by the present application.
  • FIG. 7 is a schematic flowchart of Embodiment 6 provided by the present application.
  • FIG. 8 is a schematic diagram of a user equipment provided by the present application.
  • FIG. 9 is a schematic diagram of another user equipment provided by the present application.
  • the UE that fails the connection initiates an RRC connection reestablishment request in the reestablished cell, and the UE determines that the reestablished cell does not meet the set cell selection criterion or does not receive the network side device to which the reestablished cell belongs.
  • the RRC connection re-establishment command it is determined that the information related to the connection failure is not carried in the information about the connection failure, or the information related to the connection failure is not saved by itself, thereby preventing the network side from making errors in the above scenario. Optimization of the switching parameters.
  • a method for performing RRC connection reestablishment includes the following steps: Step 11. A UE that fails to initiate a connection initiates an RRC connection reestablishment request in a selected reestablished cell.
  • Step 12 When determining that the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, the UE determines that the information related to the connection failure is not saved in the information. Carrying the identification information of the reconstructed cell, or does not save any information related to the connection failure.
  • the connection failure indicates that the connection between the user equipment and the cell to which it is connected is disconnected, such as RLF, HOF, and the like.
  • the identifier information of the reconstructed cell may be an E-UTRAN Cell Global ID (E-UTRAN Cell Global ID; Evolved UMTS Terrestrial Radio Access Network, E-UTRAN; Universal Mobile Telecommunications System , UMTS; Identifier, ID), etc.
  • the UE when determining that the connection failure (RLF or HOF) occurs, the UE records one or a combination of the following information in the information related to the connection failure:
  • the identifier of the cell in which the connection fails is reported, wherein, if it is an RLF, the ID of the last serving cell of the UE is reported; if it is a HOF, the ID of the target cell to which the UE is handed over is reported;
  • the measurement information includes the RSRP/RSRQ of the serving cell of the UE when the connection fails, and the RSRP/RSRQ of the neighboring cell.
  • the UE after determining that the transmission connection fails, the UE performs cell selection according to the set cell selection criterion, and initiates an RRC connection reestablishment process.
  • the cell selection criteria related to the setting in the embodiment of the present application can be referred to the 3GPP 36.304 protocol.
  • the UE to determine whether the reconstructed cell meets the set cell selection criteria refer to the 3GPP 36.304 protocol.
  • step 12 the UE determines, according to the following steps, that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received:
  • the UE When the UE sends an RRC connection reestablishment request to the network side device to which the reestablished cell belongs, the UE starts the configured timer (such as timer T301);
  • the UE determines that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received.
  • the UE determines that the information related to the connection failure saved by the UE does not carry the identification information of the reconstructed cell.
  • the saving of the information related to the connection failure includes the following two implementation methods:
  • the method A1 the UE, when the re-establishment cell initiates the RRC connection re-establishment request, saves the identifier information of the re-established cell in the information related to the connection failure, and the information related to the connection failure saved by the UE includes the UE in the information. Determining the information recorded when the connection failure occurs, and including the identification information of the reconstructed cell;
  • the UE When the UE determines that the reestablished cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, the UE deletes the reestablished cell saved in the information related to the connection failure.
  • Identification information at this time, the information related to the connection failure saved by the UE includes only information recorded by the UE when it determines that the connection failure has occurred; In this method, if the UE subsequently connects to the network through the RRC connection establishment process, and the information related to the connection failure is saved to the network side, the information related to the connection failure does not carry the identification information of the reconstructed cell. .
  • the method A2 when the re-establishment cell initiates the RRC connection re-establishment request, the UE does not save the identification information of the re-established cell in the information related to the connection failure. At this time, the information related to the connection failure saved by the UE includes only the UE. Information recorded when a connection failure occurs on its own;
  • the information related to the connection failure does not carry the identification information of the reconstructed cell.
  • the UE when the re-establishment cell initiates an RRC connection reestablishment request, the UE does not store the identity information of the reestablished cell in the information related to the connection failure; if the RRC connection re-establishment process, the UE determines the RRC The connection is successfully reestablished (that is, the UE receives the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs) or the RRC connection reestablishment is rejected (that is, the UE receives the RRC connection reestablishment sent by the network side device to which the reestablished cell belongs.
  • the UE saves the information about the reestablished cell in the information related to the connection failure.
  • the information related to the connection failure saved by the UE includes the UE determining that the connection failure has occurred.
  • the recorded information further includes identification information of the reconstructed cell.
  • the saving of the information related to the connection failure includes the following implementation manner:
  • the UE When the re-establishment cell initiates the RRC connection re-establishment request, the UE saves the identity information of the re-established cell in the information related to the connection failure. At this time, the information related to the connection failure saved by the UE includes the UE determining that it is happening. The information recorded when the connection fails, and the identification information of the reconstructed cell;
  • the UE When the UE determines that the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, the UE deletes all information related to the connection failure saved by the UE, that is, the The UE does not save any information related to the connection failure.
  • the UE if the UE is connected to the network side through the RRC connection establishment process, the UE does not report any information related to the connection failure to the network side.
  • the network side performs the following steps:
  • the network side After determining that the information related to the connection failure does not carry the identification information of the reconstructed cell, the network side does not perform the mobility robustness optimization process.
  • the network side After receiving the information related to the connection failure sent by the UE, the network side first determines whether the cause of the UE connection failure is an overlay vulnerability according to the measurement information (ie, RSRP/RSRQ) in the information related to the connection failure. If not, and it is determined that the identification information of the reconstructed cell in the information related to the connection failure does not exist, then ignore this time. Reported, and will not optimize the mobile robustness parameters based on the information reported this time;
  • the measurement information ie, RSRP/RSRQ
  • the network side determines whether the cause of the failure of the UE connection is a coverage vulnerability according to the measurement information (ie, RSRP/RSRQ) in the information related to the connection failure, and the 3GPP 36.300 protocol.
  • the measurement information ie, RSRP/RSRQ
  • cell A provides services for UEs in a connected state, and cell A has three neighboring cells, cell B, cell C, and cell D;
  • the UE separately measures the RSRQ values of the serving cell (ie, cell A) and the neighboring cell (ie, cell B, cell C, and cell D) when the connection fails, and assumes that the measured cell A, cell B,
  • the RSRQ values of cell C and cell D are further divided into RSRQA, RSRQ B , RSRQc and RSRQ D , and RSRQc > RSRQB > RSRQ D > RSRQ a ; if the UE selects cell B for RRC connection reestablishment request, but in the RRC During the connection reestablishment process, the UE measures that the signal of the cell B does not meet the cell selection criterion or the UE does not receive the RRC connection reestablishment command sent by the network side device to which the cell B belongs after the UE initiates the RRC connection reestablishment request.
  • the RRC connection re-establishment process is continued, but the IDLE (idle) state is returned. Then, the UE initiates an RRC connection setup in the cell C, and carries the self-saved in the RRC connection setup complete message sent to the network side device to which the cell C belongs.
  • the information related to the RLF ie, the RLF REPORT, the RLF report), so that the network side device to which the cell C belongs acquires the RLF REPORT of the UE;
  • the UE carries the identifier information of the cell B that is the reconstructed cell ID in the RLF REPORT; correspondingly, when the network side analyzes the RLF REPORT data recorded by the UE, it considers that the UE occurs in the cell A. Failure, and RRC connection reestablishment in cell B is a typical handover too late scenario.
  • the network side considers that the connection failure is caused by the late handover of cell A to cell B. When the statistic reaches the set threshold, The network side adjusts the handover parameters from cell A to cell B, so that the UE can switch from cell A to cell B earlier.
  • cell B is not the most suitable cell;
  • the network side determines, according to the RSRP/RSRQ of the local cell and the neighboring cell reported by the UE, that the connection failure reason is not an overlay vulnerability, The network side will not count the current 4 ⁇ as a coverage vulnerability.
  • the network side since the RLF REPORT does not carry the reconstructed cell ID, the network side will not use this as a reference for mobile robustness optimization.
  • the network side does not adjust the handover parameters from the cell to the cell B;
  • the RLF REPORT will not be reported to the network side; accordingly, since the network side does not receive the upper 4 ⁇ of the UE, the failure will not occur. As an input to cover vulnerabilities or mobile robustness optimization.
  • the method for performing RRC connection reestablishment includes the following steps: Step 21: The UE determines that RLF occurs by itself, and records RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs. And information such as the failed cell ID (ie, the ID of the last serving cell of the UE);
  • Step 22 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 (Cell 1) for RRC connection reestablishment, and records the reconstructed cell ID as CELL1;
  • Step 23 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 24 In the RRC connection re-establishment process, the UE finds that CELL1 does not meet the cell selection criterion, and the UE deletes the reconstructed cell ID saved by itself;
  • Step 25 The UE enters an IDLE state.
  • Step 26 The UE receives the RRC connection reestablishment command sent by the network side device to which the CELL1 belongs.
  • Step 27 The UE initiates an RRC connection establishment process to the CELL2. After the RRC connection is successfully established, the network side device to which the CELL2 belongs acquires the UE. RLF REPORT, and the reconstructed cell ID in the RLF REPORT is empty;
  • the RLF REPORT includes RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs, and information such as the failed cell ID;
  • the network side device after receiving the RLF REPORT, the network side device first determines whether it is a coverage vulnerability according to RSRP/RSRQ in the RLF REPORT; if it is not a coverage vulnerability, and the reestablished cell ID does not exist, the network side device does not The optimization of the mobility robustness parameter is performed according to the RLF REPORT.
  • the method for performing RRC connection reestablishment includes the following steps: Step 31: The UE determines that RLF occurs by itself, and records the location of the serving cell and the neighboring cell when the RLF occurs.
  • RSRP/RSRQ and information such as the failed cell ID
  • Step 32 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 for RRC connection reestablishment, and records the reconstructed cell ID as CELL1;
  • Step 33 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 34 Until the timer T301 times out, the UE does not receive the RRC connection reestablishment command delivered by the network side device to which the CELL1 belongs.
  • Step 35 The UE enters an IDLE state.
  • Step 36 The UE initiates an RRC connection establishment process to the CELL2. After the RRC connection is successfully established, the network side device to which the CELL2 belongs acquires the RLF REPORT saved by the UE, and the reconstructed cell ID in the RLF REPORT is empty.
  • the RLF REPORT includes RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs, and information such as the failed cell ID.
  • the network side device after receiving the RLF REPORT, the network side device first according to the RLF REPORT The RSRP/RSRQ determines whether it is an overlay vulnerability. If it is not an overlay vulnerability and the reestablished cell ID does not exist, the network side device does not perform the optimization of the mobility robustness parameter according to the RLF REPORT.
  • the method for performing RRC connection reestablishment includes the following steps: Step 41: The UE determines that RLF occurs by itself, and records RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs. And information such as the failed cell ID;
  • Step 42 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 to perform RRC connection reestablishment. At this time, the UE does not record the reestablished cell ID.
  • Step 43 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 44 During the RRC connection reestablishment process, the UE finds that CELL1 does not meet the cell selection criterion; Step 45: The UE enters the IDLE state;
  • Step 46 The UE receives the RRC connection reestablishment command sent by the network side device to which the CELL1 belongs.
  • Step 47 The UE initiates an RRC connection establishment process to the CELL2. After the RRC connection is successfully established, the network side device to which the CELL2 belongs acquires the UE to save. RLF REPORT, and the reconstructed cell ID in the RLF REPORT is empty;
  • the RLF REPORT includes RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs, and information such as the failed cell ID.
  • the network side device after receiving the RLF REPORT, the network side device first determines whether it is a coverage vulnerability according to RSRP/RSRQ in the RLF REPORT; if it is not a coverage vulnerability, and the reestablished cell ID does not exist, the network side device does not The optimization of the mobility robustness parameter is performed according to the RLF REPORT.
  • the method for performing RRC connection reestablishment includes the following steps: Step 51: The UE determines that RLF occurs by itself, and records RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs. And information such as the failed cell ID;
  • Step 52 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 to perform RRC connection reestablishment. At this time, the UE does not record the reestablished cell ID.
  • Step 53 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 54 Until the timer T301 times out, the UE does not receive the RRC connection reestablishment command delivered by the network side device to which the CELL1 belongs.
  • Step 55 The UE enters an IDLE state.
  • Step 56 The UE initiates an RRC connection establishment process to CELL2. After the RRC connection is successfully established, the network side device to which the CELL2 belongs may obtain the RLF REPORT saved by the UE, and the reconstructed cell ID in the RLF REPORT is empty.
  • the RLF REPORT includes information such as RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs, and a failed cell ID. Based on this embodiment, after receiving the RLF REPORT, the network side device first determines whether it is a coverage vulnerability according to RSRP/RSRQ in the RLF REPORT; if it is not a coverage vulnerability, and the reestablished cell ID does not exist, the network side device does not The optimization of the mobility robustness parameter is performed according to the RLF REPORT.
  • Step 61 The UE determines that RLF occurs by itself, and records the location of the serving cell and the neighboring cell when the RLF occurs.
  • RSRP/RSRQ and information such as the failed cell ID
  • Step 62 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 for RRC connection reestablishment, and records the reconstructed cell ID as CELL1;
  • Step 63 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 64 During the RRC connection reestablishment process, the UE finds that CELL1 does not meet the cell selection criterion, and the UE deletes the recorded information related to the RLF.
  • Step 65 The UE enters an IDLE state.
  • Step 66 The UE receives the RRC connection reestablishment command sent by the network side device to which the CELL1 belongs.
  • Step 67 The UE initiates an RRC connection establishment process to the CELL2, and after the RRC connection is successfully established, the UE does not go to the network to which the CELL2 belongs.
  • the side device reports RLF REPORT.
  • Step 71 The UE determines that RLF occurs by itself, and records RSRP/RSRQ of the serving cell and the neighboring cell when the RLF occurs. And information such as the failed cell ID;
  • Step 72 The UE performs cell selection according to the set cell selection criterion, and selects CELL1 for RRC connection reestablishment, and records the reconstructed cell ID as CELL1;
  • Step 73 The UE sends an RRC connection reestablishment request to the network side device to which the CELL1 belongs.
  • Step 74 Until the timer T301 times out, the UE does not receive the RRC connection reestablishment command sent by the network side device to which the CELL1 belongs, and the UE deletes the recorded information related to the RLF.
  • Step 75 The UE enters an IDLE state.
  • Step 76 The UE initiates an RRC connection establishment process to CELL2, and after the RRC connection is successfully established, the
  • the UE does not report the RLF REPORT to the network side device to which CELL2 belongs.
  • the above method processing flow can be implemented by a software program, which can be stored in a storage medium shield, and when the stored software program is called, the above method steps are performed.
  • the user equipment is also provided in the embodiment of the present application.
  • the principle of the user equipment is similar to the method for performing the RRC connection reestablishment. Therefore, the implementation of the user equipment can refer to the implementation of the method, and the method is repeated. I won't go into details here.
  • the user equipment provided by the embodiment of the present application is applied to a scenario in which a connection failure occurs, and the user equipment includes:
  • the first processing module 81 is configured to initiate an RRC connection reestablishment request in the selected reestablished cell;
  • the second processing module 82 is configured to determine, when the reestablished cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, determine that the saved cell is related to the connection failure.
  • the information does not carry the identification information of the reconstructed cell, or does not save any information related to the connection failure.
  • the first processing module 81 is specifically configured to: when the selected reestablishment cell initiates the RRC connection reestablishment request, save the identifier information of the reestablishment cell in the information related to the connection failure;
  • the second processing module 82 is specifically configured to: after determining that the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, delete the information related to the connection failure. The identification information of the saved reconstructed cell.
  • the first processing module 81 is specifically configured to: when the selected reestablishment cell initiates the RRC connection reestablishment request, save the identifier information of the rebuilt cell in the information related to the connection failure.
  • the first processing module 81 is specifically configured to: when the selected reestablishment cell initiates the RRC connection reestablishment request, save the identifier information of the reestablishment cell in the information related to the connection failure;
  • the second processing module 82 is specifically configured to: after determining that the reconstructed cell does not meet the set cell selection criterion or does not receive the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs, delete all the saved information related to the connection failure. Information.
  • the second processing module 82 determines, according to the following steps, that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received:
  • the configured timer is enabled; and when the timer expires, it is determined that the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is not received.
  • the embodiment of the present application provides another user equipment.
  • the user equipment includes a processor 91 and a radio frequency unit 92:
  • the processor 91 is configured to: after determining that the UE has failed to connect, initiate an RRC connection reestablishment request by using the radio unit 92 in the selected reestablished cell; determining that the rebuilt cell does not meet the set cell selection criterion or not
  • the RRC connection reestablishment command sent by the network side device to which the reestablished cell belongs is determined, the information related to the connection failure that is saved by the self-recovery does not carry the identification information of the re-established cell, or does not save any information related to the connection failure. .
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the application can be in the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware.
  • the application can be applied to one or more computers in which computer usable program code is included.
  • a form of computer program product embodied on a storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.).
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本申请实施例公开了一种进行RRC连接重建的方法及用户设备，用于解决现有技术中存在的发生连接失败的UE在某个小区进行RRC连接重建过程中，该小区不符合设定的小区选择标准或该UE未收到网络侧发送的RRC连接重建命令的场景下，导致网络侧进行错误的切换参数的优化的问题。本申请实施例的方法包括：发生连接失败的UE在选定的重建小区发起RRC连接重建请求；以及UE在确定该重建小区不符合设定的小区选择标准或自身未收到该重建小区所属的网络侧设备发送的RRC连接重建命令时，确定自身保存的与连接失败相关的信息中不携带该重建小区的标识信息，或者自身不保存任何与连接失败相关的信息。

Description

一种进行 RRC连接重建的方法及用户设备 本申请要求在 2013年 03月 05日提交中国专利局、 申请号为 201310069100.5、发明名称为
"一种进行 R RC连接重建的方法及用户设备"的中国专利申请的优先权，其全部内容通过 I用结 合在本申请中。 技术领域 本申请涉及通信技术领域， 特别涉及一种进行 RRC连接重建的方法及用户设备。 背景技术 减少操作管理工作的复杂性， 降低运营维护成本， 是通信运营商的迫切要求。 在下一 代的网络中， 希望通过引入网络自组织的机制， 减少网络规划和操作维护的人工参与， 降 低网络的建设和运营成本。 正是在这样的背景下， 演进型通用陆地无线接入（Evolved Universal Terrestrial Radio Access, E-UTRA )系统的自组织网络 ( Self Organizing Networks, SON )特性作为第三代合作伙伴计划 （3rd Generation Partnership Project, 3GPP )一个工作 议题进行研究。 SON技术包括了自配置、 自优化和自治愈， 自优化是其中一项重要特性。
SON 自优化功能需要监测一些网络和系统性能参数作为输入， 如网络性能指标的统 计、 故障告警、 通知等， 在对输入数据进行分析后， 优化算法做出决策， 最后自动触发相 关网络节点的调整操作。
在移动网络中， 切换参数设置不合适会严重影响系统性能， 最严重的情况是导致用户 掉话。 因此切换参数自优化是 E-UTRA系统的 SON所要解决的最重要问题之一， 要能够 减少切换失败的发生， 减少不当切换导致的用户掉话， 以及减少不必要的切换， 避免这些 切换对系统资源的无效使用。 移动健壮性优化（ Mobility Robustness Optimization, MRO ) 首先要做的， 是要准确地判断问题的根本原因。
不当的切换通常是由于切换参数设置不合理导致的， 包括以下几种情况：
a )终端没有及时切换到一个无线信号较好的小区， 而原来的服务小区信号不断恶化直 至用户掉话， 这种情况称为 "过迟切换"， 意味着切换应当更早进行， 但由于参数设置得 不合适使得切换被延迟了；
b ) 终端从源小区切换到目标小区， 但是目标小区信号并不稳定， 导致切换后很快就 发生无线链路失败（Radio Link Failure, RLF ), 随后终端再选择一个新的小区进行重建连 接， 这种情况称为 "切换到错误小区"， 意味着重建连接的那个小区才是一个合适的目标 小区， 而原来选择的目标小区并不合适； C )终端从源小区切换到目标小区， 但很快发生了无线链路失败， 随后终端选择了源小 区进行重建连接， 这种情况称为 "过早切换"。
判断过迟切换的准则如下：
用户设备 ( User Equipment, UE, 又称终端 )在切换触发之前发生 RLF , 然后该 UE 在不同于源小区的另一个小区尝试连接重建。
判断过早切换的准则如下：
UE在切换到目标小区后 4艮快发生 RLF或者在切换过程中发生了切换失败（ Handover Failure, HOF ), 然后该 UE在源小区尝试连接重建。
判断切换到错误小区的准则如下：
UE在切换过程中发生 RLF (无论是在源小区还是在目标小区）或者在切换到目标小 区后 4艮快发生 RLF , 然后该 UE在一个第三方小区 （既非源小区， 亦非目标小区） 尝试连 接重建。
在实际网络中， UE发生 RLF主要包括以下两种原因： 一是切换参数不合适使得没有 及时变更 UE的服务小区， 服务小区的信号盾量低到不足以提供服务， 导致 RLF; 另一个 是网络中的覆盖漏洞或者阴影衰落， 当 UE移动到空洞或阴影处时， 由于无线链路条件急 剧恶化， 导致 RLF。
只有第一种原因属于切换问题， 第二种原因属于覆盖问题， 需要排除在 MRO的检测 范围之外。 这两种原因的判断是根据 UE在失败时刻测量的本小区和邻区的参考信号接收 功率 （Reference Signal Received Power , RSRP ) /参考信号接收盾量 （Reference Signal Received Quality, RSRQ ) 实现的。 如果在失败时刻， UE测量的所有小区的 RSRP/RSRQ 都很差， 说明是覆盖漏洞； 否则， 说明是切换问题。 为了辅助网络侧进行 MRO的判断， UE需要上 4艮与连接失败（ RLF或者 HOF )相关的信息， 包括如下内容：
1、 如果是 RLF , 上报该 UE 的最后的服务小区的 ID; 如果是 HOF , 上报该 UE切换 的目标小区的 ID;
2、 进行无线资源控制 （Radio Resource Control , RRC )连接重建的小区的标识；
3、 发起切换的小区的标识；
4、 从最后一次切换发起到发生连接失败的时间；
5、 指示本次失败是 RLF还是 HOF;
6、 测量信息： 包括发生 RLF时服务小区的 RSRP/RSRQ以及邻区的 RSRP/RSRQ。 在 3GPP规范中， UE在发生 RLF或者 HOF时， 会将上述 1 , 3 , 4 , 5以及 6记录下 来， 在发送 RRC连接重建请求（ RRC RE-ESTABLISHMENT REQUEST ) 消息时， 会将 2 记录下来。 UE在 RRC连接重建成功或者 RRC连接建立成功之后， 将自身记录的这些与 连接失败相关的信息上报给网络侧。 网络侧根据 UE上报的与连接失败相关的信息， 判断 是覆盖问题还是由于切换参数设置不合理而导致的切换过早 /切换过迟 /切换到错误小区。 目前， 只要发生连接失败（ RLF或 HOF ) 的 UE准备向某个小区发起 RRC连接重建 请求， 该 UE就会把该小区记录为重建小区。 但是， 很有可能发生如下情况： UE在发起 RRC连接重建请求后， 该小区可能又不符合小区选择的标准或者 UE在发起 RRC连接重 建请求后没有收到网络侧发送的 RRC重建命令。 在上述场景下， UE仍然在上报给网络侧 的与连接失败相关的信息中携带该重建小区的标识信息， 网络侧仍会认为该重建小区是合 适的小区， 并进行 MRO的判断和优化， 从而导致错误的切换参数的优化。
综上所述， 现有规范中， 只要发生连接失败的 UE准备向某个小区发起 RRC连接重建请 求， 该 UE就会把该小区记录为重建小区， 并将该重建小区的标识信息上 4艮给网络侧， 在该 小区不符合设定的小区选择标准或该 UE未收到网络侧发送的 RRC连接重建命令的场景下， 导致网络侧进行错误的切换参数的优化。 发明内容 本申请实施例提供了一种进行 RRC 连接重建的方法及用户设备， 用于解决现有技术 中存在的发生连接失败的 UE在某个小区进行 RRC连接重建过程中，该小区不符合设定的 小区选择标准或该 UE未收到网络侧发送的 RRC连接重建命令的场景下，导致网络侧进行 错误的切换参数的优化的问题。
本申请实施例提供了一种进行 RRC连接重建的方法， 包括：
发生连接失败的 UE在选定的重建小区发起 RRC连接重建请求；
所述 UE在确定所述重建小区不符合设定的小区选择标准或自身未收到所述重建小区 所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败相关的信息 中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的信息。
较佳地， 上述 UE在所述重建小区发起 RRC连接重建请求时， 将上述重建小区的标识 信息保存在与连接失败相关的信息中； 该 UE在确定所述重建小区不符合设定的小区选择 标准或者自身未收到该重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 删除上 述与连接失败相关的信息中保存的该重建小区的标识信息。
较佳地， 上述 UE在上述重建小区发起 RRC连接重建请求时， 不在与连接失败相关的 信息中保存该重建小区的标识信息。
较佳地， 上述 UE在上述重建小区发起 RRC连接重建请求时， 将该重建小区的标识信 息保存在与连接失败相关的信息中； 该 UE在确定该重建小区不符合设定的小区选择标准 或者自身未收到该重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 删除自身保 存的所有与连接失败相关的信息。 基于上述任意方法实施例， 较佳地， UE根据以下步骤确定自身未收到上述重建小区 所属的网络侧设备发送的 RRC连接重建命令：
UE在向该重建小区所属的网络侧设备发起 RRC连接重建请求时， 开启已配置的定时 器；
在该定时器超时时， UE确定未收到该重建小区所属的网络侧设备发送的 RRC连接 重建命令。
本申请实施例提供了一种用户设备， 该用户设备发生了连接失败， 且该用户设备包 括：
第一处理模块， 用于在选定的重建小区发起 RRC连接重建请求；
第二处理模块， 用于在确定所述重建小区不符合设定的小区选择标准或自身未收到所 述重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败 相关的信息中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的信 息。
较佳地， 第一处理模块具体用于： 在上述重建小区发起 RRC 连接重建请求时， 将该 重建小区的标识信息保存在与连接失败相关的信息中； 第二处理模块具体用于： 在确定该 重建小区不符合设定的小区选择标准或者自身未收到该重建小区所属的网络侧设备发送 的 RRC连接重建命令后， 删除该与连接失败相关的信息中保存的该重建小区的标识信息。
较佳地， 第一处理模块具体用于： 在上述重建小区发起 RRC 连接重建请求时， 不在 与连接失败相关的信息中保存该重建小区的标识信息。
较佳地， 第一处理模块具体用于： 在上述重建小区发起 RRC 连接重建请求时， 将该 重建小区的标识信息保存在与连接失败相关的信息中； 第二处理模块具体用于： 在确定该 重建小区不符合设定的小区选择标准或者自身未收到该重建小区所属的网络侧设备发送 的 RRC连接重建命令后， 删除自身保存的所有与连接失败相关的信息。
基于上述任意用户设备实施例， 较佳地， 第二处理模块根据以下步骤确定自身未收到 上述重建小区所属的网络侧设备发送的 RRC连接重建命令：
在向该重建小区所属的网络侧设备发起 RRC连接重建请求时， 开启已配置的定时器； 以及在该定时器超时时， 确定未收到该重建小区所属的网络侧设备发送的 RRC 连接重建 命令。
基于与方法同样的发明构思， 本申请实施例提供了另一种用户设备， 该用户设备包括 处理器和射频单元：
该处理器被配置为， 确定 UE发生了连接失败后， 在选定的重建小区通过射频单元发 起 RRC 连接重建请求； 在确定所述重建小区不符合设定的小区选择标准或自身未收到所 述重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败 相关的信息中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的信 息。
本申请实施例中，发生连接失败的 UE在选定的重建小区发起 RRC连接重建请求， 该 UE在确定重建小区不符合设定的小区选择标准或自身未收到该重建小区所属的网络侧设 备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败相关的信息中不携带重建小 区的标识信息， 或者自身不保存任何与连接失败相关的信息， 从而避免了网络侧进行错误 的切换参数的优化。 附图说明 图 1为本申请提供的一种进行 RRC连接重建的方法流程图；
图 2为本申请提供的实施例一的流程示意图；
图 3为本申请提供的实施例二的流程示意图；
图 4为本申请提供的实施例三的流程示意图；
图 5为本申请提供的实施例四的流程示意图；
图 6为本申请提供的实施例五的流程示意图；
图 7为本申请提供的实施例六的流程示意图；
图 8为本申请提供的一种用户设备的示意图；
图 9为本申请提供的另一种用户设备的示意图。 具体实施方式 本申请实施例发生连接失败的 UE在重建小区发起 RRC连接重建请求， 该 UE在确定 该重建小区不符合设定的小区选择标准或自身未收到该重建小区所属的网络侧设备发送 的 RRC 连接重建命令时， 确定自身保存的与连接失败相关的信息中不携带该重建小区的 标识信息， 或者自身不保存任何与连接失败相关的信息， 从而避免了网络侧在上述场景下 进行错误的切换参数的优化。
下面结合说明书附图对本申请实施例作进一步详细描述。
参见图 1所示，本申请实施例提供的一种进行 RRC连接重建的方法， 包括以下步骤： 步骤 11、 发生连接失败的 UE在选定的重建小区发起 RRC连接重建请求；
步骤 12、 UE在确定该重建小区不符合设定的小区选择标准或自身未收到该重建小区 所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败相关的信息 中不携带该重建小区的标识信息， 或者自身不保存任何与连接失败相关的信息。
在实施中，连接失败表示用户设备与其接入的小区之间的连接断开，如 RLF、 HOF等。 在实施中， 重建小区的标识信息可以为演进通用移动通信系统陆地无线接入网小区全 球标识 E-CGI ( E-UTRAN Cell Global ID; Evolved UMTS Terrestrial Radio Access Network, E-UTRAN; Universal Mobile Telecommunications System, UMTS; Identifier, ID )等。
在实施中， UE在确定自身发生连接失败（RLF或 HOF ) 时， 会将下列信息中的一种 或组合记录在与连接失败相关的信息中：
发生连接失败的小区的标识， 其中， 如果是 RLF, 上报该 UE 的最后的服务小区的 ID; 如果是 HOF, 上报该 UE切换的目标小区的 ID;
发起切换的小区的标识；
从最后一次切换发起到发生连接失败的时间；
指示信息， 用于指示本次连接失败是 RLF还是 HOF; 以及
测量信息， 包括发生连接失败时该 UE 的服务小区的 RSRP/RSRQ 以及邻区的 RSRP/RSRQ。
在实施中， UE在确定自身发送连接失败后， 根据设定的小区选择标准， 进行小区选 择， 并发起 RRC连接重建过程。
需要说明的是， 本申请实施例中涉及设定的小区选择标准可参见 3GPP 36.304协议中 的规定， UE判断重建小区是否符合设定的小区选择标准的过程请参见 3GPP 36.304协议。
在实施中， 步骤 12中， UE根据以下步骤确定自身未收到重建小区所属的网络侧设备 发送的 RRC连接重建命令：
UE在向重建小区所属的网络侧设备发送 RRC连接重建请求时， 开启已配置的定时器 (如定时器 T301 ); 以及
在该定时器超时时， UE确定未收到重建小区所属的网络侧设备发送的 RRC连接重建 命令。
在实施中， 如果 UE保存有与连接失败相关的信息， 则步骤 12中， UE确定自身保存 的与连接失败相关的信息中不携带重建小区的标识信息。
如果 UE保存有与连接失败相关的信息， 进一步， 对与连接失败相关信息的保存又包 括以下两种实现方法：
方法 Al、 UE在重建小区发起 RRC连接重建请求时， 将该重建小区的标识信息保存 在与连接失败相关的信息中， 此时， 该 UE保存的与连接失败相关的信息中既包括该 UE 在确定自身发生连接失败时记录的信息， 又包括重建小区的标识信息； 以及
该 UE在确定该重建小区不符合设定的小区选择标准或者自身未收到该重建小区所属 的网络侧设备发送的 RRC 连接重建命令时， 删除该与连接失败相关的信息中保存的该重 建小区的标识信息， 此时， 该 UE保存的与连接失败相关的信息中仅包括该 UE在确定自 身发生连接失败时记录的信息； 该方法下， 若 UE后续通过 RRC连接建立过程连接到网络侧， 并向网络侧上 4艮自身保 存的与连接失败相关的信息时， 该与连接失败相关的信息中不携带重建小区的标识信息。
方法 A2、 UE在重建小区发起 RRC连接重建请求时， 不在与连接失败相关的信息中 保存该重建小区的标识信息， 此时， 该 UE保存的与连接失败相关的信息中仅包括该 UE 在确定自身发生连接失败时记录的信息；
该方法下， 若 UE后续通过 RRC连接建立过程连接到网络侧， 并向网络侧上 4艮自身保 存的与连接失败相关的信息时， 该与连接失败相关的信息中不携带重建小区的标识信息。
需要说明的是， 该方法下， 该 UE在重建小区发起 RRC连接重建请求时， 不在与连接 失败相关的信息中保存该重建小区的标识信息； 若在 RRC连接重建过程中， 该 UE确定该 RRC连接重建成功 （即该 UE接收到该重建小区所属的网络侧设备发送的 RRC连接重建 命令）或该 RRC连接重建被拒绝（即该 UE接收到该重建小区所属的网络侧设备发送的 RRC连接重建拒绝消息）， 则该 UE将该重建小区的标识信息保存在该与连接失败相关的 信息中，该场景下， UE保存的与连接失败相关的信息中既包括该 UE在确定自身发生连接 失败时记录的信息， 又包括重建小区的标识信息。
在实施中， 如果步骤 12中， UE确定不保存任何与连接失败相关的信息， 优选的， 对 与连接失败相关信息的保存包括以下实现方式：
UE在重建小区发起 RRC连接重建请求时， 将该重建小区的标识信息保存在与连接失 败相关的信息中， 此时， 该 UE保存的与连接失败相关的信息中既包括该 UE在确定自身 发生连接失败时记录的信息， 又包括重建小区的标识信息； 以及
该 UE在确定该重建小区不符合设定的小区选择标准或者自身未收到该重建小区所属 的网络侧设备发送的 RRC连接重建命令时， 删除自身保存的所有与连接失败相关的信息， 即该 UE不保存任何与连接失败相关的信息。
该方法下， 若 UE后续通过 RRC连接建立过程连接到网络侧， 该 UE不会向网络侧上 报任何与连接失败相关的信息。
进一步， 如果 UE保存有与连接失败相关的信息， 且该与连接失败相关的信息中不携 带重建小区的标识信息， 若 UE后续通过 RRC连接建立过程连接到了网络侧， 并向网络侧 上报了自身保存的与连接失败相关的信息， 则该网络侧执行以下步骤：
该网络侧接收 UE上报的与连接失败相关的信息； 以及
该网络侧在确定该与连接失败相关的信息中不携带重建小区的标识信息后， 不进行移 动健壮性优化处理。
具体的， 该网络侧收到 UE发送的与连接失败相关的信息后， 先根据该与连接失败相 关的信息中的测量信息 （即 RSRP/RSRQ ), 判断该 UE连接失败的原因是否是覆盖漏洞； 若不是， 且确定该与连接失败相关的信息中的重建小区的标识信息也不存在， 则忽略本次 上报， 且不会根据本次上报的信息进行移动健壮性参数的优化；
需要说明的是， 网络侧获取 UE保存的与连接失败相关的信息的过程请参见 3GPP 36.331协议;
网络侧根据该与连接失败相关的信息中的测量信息 （即 RSRP/RSRQ ), 判断该 UE连 接失败的原因是否是覆盖漏洞的过程请参见 3GPP 36.300协议。
举例说明， 假设小区 A为连接态的 UE提供服务， 且小区 A有三个邻区， 小区 B、 小 区 C及小区 D;
若 UE发生了 RLF , 则该 UE分别测量在连接失败时服务小区（即小区 A )和邻区（即 小区 B、 小区 C及小区 D )的 RSRQ值， 假设测量得到的小区 A、 小区 B、 小区 C及小区 D 的 RSRQ 值分另' J为 RSRQA、 RSRQB、 RSRQc 及 RSRQD , 且 RSRQc > RSRQB >RSRQD>RSRQa; 若 UE选择了小区 B进行 RRC连接重建请求， 但在该 RRC连 接重建过程中，该 UE测量到小区 B的信号不符合小区选择标准或者该 UE在发起 RRC连 接重建请求后没有接收到小区 B所属的网络侧设备发送的 RRC连接重建命令， 此时， UE 不会继续该 RRC连接重建过程， 而是返回 IDLE (空闲）状态； 随后， UE在小区 C发起 RRC连接建立， 并在向小区 C所属的网络侧设备发送的 RRC连接建立完成消息中携带自 身保存的与 RLF相关的信息（即 RLF REPORT , RLF报告 ), 从而小区 C所属的网络侧设 备获取了该 UE的 RLF REPORT;
作为一种实现方式， 若该 UE在 RLF REPORT中携带了作为重建小区 ID的小区 B的 标识信息； 相应的， 网络侧在分析本次 UE记录的 RLF REPORT数据时， 考虑到 UE在小 区 A发生失败， 并在小区 B进行 RRC连接重建是一个典型的切换过迟的场景， 该网络侧 会认为连接失败的原因是小区 A到小区 B的切换过迟， 当统计量达到设定的阈值后， 网络 侧会调整从小区 A到小区 B的切换参数， 使 UE能更早的从小区 A切换到小区 B。 然而， 实际上， 小区 B并不是最合适的小区；
作为另一种实现方式， 若该 UE在 RLF REPORT中不携带重建小区 ID; 相应的， 网 络侧根据该 UE上报的本小区和邻小区的 RSRP/RSRQ判断本次连接失败原因不是覆盖漏 洞， 则该网络侧不会将本次上 4艮统计为覆盖漏洞， 同时， 由于 RLF REPORT中不携带重建 小区 ID , 则网络侧也不会将本次上 ·ί艮作为移动健壮性优化的参考， 因此， 网络侧不会调整 从小区 Α到小区 B的切换参数；
作为再一种实现方式，若该 UE从 IDLE状态连接到网络侧后，不会向网络侧上报 RLF REPORT; 相应的， 由于网络侧没有收到 UE的上 4艮， 因此， 本次失败不会作为覆盖漏洞 或者移动健壮性优化的输入。
下面以 UE的连接失败是 RLF为例， 对本申请实施例提供的进行 RRC连接重建的方 法进行说明， 其他连接失败的情况与此类似， 此处不再——举例说明。 实施例一、 参见图 2所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 21、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的 RSRP/RSRQ, 以及失败小区 ID (即该 UE的最后的服务小区的 ID )等信息；
步骤 22、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1 (小区 1 ) 进行 RRC连接重建， 且记录重建小区 ID为 CELL1 ;
步骤 23、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 24、 在 RRC连接重建过程中， UE发现 CELL1不符合小区选择标准， 则该 UE 删除自身保存的重建小区 ID;
步骤 25、 UE进入 IDLE状态；
步骤 26、 UE接收到 CELL1所属的网络侧设备下发的 RRC连接重建命令； 步骤 27、 UE向 CELL2发起 RRC连接建立过程， 在该 RRC连接建立成功后， CELL2 所属的网络侧设备获取该 UE保存的 RLF REPORT, 且该 RLF REPORT中的重建小区 ID 为空；
其中， 该 RLF REPORT包括发生 RLF时服务小区和邻区的 RSRP/RSRQ, 以及失败小 区 ID等信息；
基于本实施例 , 网络侧设备在接收到该 RLF REPORT后， 先根据 RLF REPORT中的 RSRP/RSRQ判断是否是覆盖漏洞； 如果不是覆盖漏洞， 且重建小区 ID也不存在， 则该网 络侧设备不会根据该 RLF REPORT进行移动健壮性参数的优化。
实施例二、 参见图 3所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 31、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的
RSRP/RSRQ, 以及失败小区 ID等信息；
步骤 32、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1进行 RRC 连接重建， 且记录重建小区 ID为 CELL1 ;
步骤 33、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 34、 直到定时器 T301超时时， 该 UE都没有接收到 CELL1所属的网络侧设备下 发的 RRC连接重建命令；
步骤 35、 UE进入 IDLE状态；
步骤 36、 UE向 CELL2发起 RRC连接建立过程， 在该 RRC连接建立成功后， CELL2 所属的网络侧设备获取该 UE保存的 RLF REPORT, 且该 RLF REPORT中的重建小区 ID 为空；
其中， 该 RLF REPORT包括发生 RLF时服务小区和邻区的 RSRP/RSRQ, 以及失败小 区 ID等信息。
基于本实施例 , 网络侧设备在接收到该 RLF REPORT后， 先根据 RLF REPORT中的 RSRP/RSRQ判断是否是覆盖漏洞； 如果不是覆盖漏洞， 且重建小区 ID也不存在， 则该网 络侧设备不会根据该 RLF REPORT进行移动健壮性参数的优化。
实施例三、 参见图 4所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 41、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的 RSRP/RSRQ, 以及失败小区 ID等信息；
步骤 42、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1进行 RRC 连接重建， 此时， 该 UE不记录重建小区 ID;
步骤 43、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 44、 在 RRC连接重建过程中， UE发现 CELL1不符合小区选择标准； 步骤 45、 UE进入 IDLE状态；
步骤 46、 UE接收到 CELL1所属的网络侧设备下发的 RRC连接重建命令； 步骤 47、 UE向 CELL2发起 RRC连接建立过程， 在该 RRC连接建立成功后， CELL2 所属的网络侧设备获取该 UE保存的 RLF REPORT, 且该 RLF REPORT中的重建小区 ID 为空；
其中， 该 RLF REPORT包括发生 RLF时服务小区和邻区的 RSRP/RSRQ, 以及失败小 区 ID等信息。
基于本实施例 , 网络侧设备在接收到该 RLF REPORT后， 先根据 RLF REPORT中的 RSRP/RSRQ判断是否是覆盖漏洞； 如果不是覆盖漏洞， 且重建小区 ID也不存在， 则该网 络侧设备不会根据该 RLF REPORT进行移动健壮性参数的优化。
实施例四、 参见图 5所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 51、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的 RSRP/RSRQ, 以及失败小区 ID等信息；
步骤 52、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1进行 RRC 连接重建， 此时， 该 UE不记录重建小区 ID;
步骤 53、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 54、 直到定时器 T301超时时， 该 UE都没有接收到 CELL1所属的网络侧设备下 发的 RRC连接重建命令；
步骤 55、 UE进入 IDLE状态；
步骤 56、 UE向 CELL2发起 RRC连接建立过程， 在该 RRC连接建立成功后， CELL2 所属的网络侧设备可以获取该 UE保存的 RLF REPORT,且该 RLF REPORT中的重建小区 ID为空；
其中， 该 RLF REPORT包括发生 RLF时服务小区和邻区的 RSRP/RSRQ, 以及失败小 区 ID等信息。 基于本实施例 , 网络侧设备在接收到该 RLF REPORT后， 先根据 RLF REPORT中的 RSRP/RSRQ判断是否是覆盖漏洞； 如果不是覆盖漏洞， 且重建小区 ID也不存在， 则该网 络侧设备不会根据该 RLF REPORT进行移动健壮性参数的优化。
实施例五、 参见图 6所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 61、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的
RSRP/RSRQ, 以及失败小区 ID等信息；
步骤 62、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1进行 RRC 连接重建， 且记录重建小区 ID为 CELL1 ;
步骤 63、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 64、 在 RRC连接重建过程中， UE发现 CELL1不符合小区选择标准， 则该 UE 删除已记录的与 RLF相关的信息；
步骤 65、 UE进入 IDLE状态；
步骤 66、 UE接收到 CELL1所属的网络侧设备下发的 RRC连接重建命令； 步骤 67、 UE向 CELL2发起 RRC连接建立过程， 且在该 RRC连接建立成功后， 该 UE不会向 CELL2所属的网络侧设备上报 RLF REPORT。
实施例六、 参见图 7所示， 本实施例提供的进行 RRC连接重建的方法包括以下步骤： 步骤 71、 UE 确定自身发生 RLF , 并记录发生 RLF 时自身服务小区和邻区的 RSRP/RSRQ, 以及失败小区 ID等信息；
步骤 72、 UE根据设定的小区选择标准， 进行小区选择， 并选择了 CELL1进行 RRC 连接重建， 且记录重建小区 ID为 CELL1 ;
步骤 73、 UE向 CELL1所属的网络侧设备发送 RRC连接重建请求；
步骤 74、 直到定时器 T301超时时， 该 UE都没有接收到 CELL1所属的网络侧设备下 发的 RRC连接重建命令， 则该 UE删除记录的与 RLF相关的信息；
步骤 75、 UE进入 IDLE状态；
步骤 76、 UE向 CELL2发起 RRC连接建立过程， 且在该 RRC连接建立成功后， 该
UE不会向 CELL2所属的网络侧设备上报 RLF REPORT。
上述方法处理流程可以用软件程序实现， 该软件程序可以存储在存储介盾中， 当存储 的软件程序被调用时， 执行上述方法步骤。
基于同一发明构思， 本申请实施例中还提供了一种用户设备， 由于该用户设备解决问 题的原理与上述进行 RRC 连接重建的方法相似， 因此该用户设备的实施可以参见方法的 实施， 重复之处不再赘述。
参见图 8所示， 本申请实施例提供的用户设备， 应用于发生了连接失败的场景下， 该 用户设备包括： 第一处理模块 81 , 用于在选定的重建小区发起 RRC连接重建请求；
第二处理模块 82,用于在确定该重建小区不符合设定的小区选择标准或自身未收到该 重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败相 关的信息中不携带该重建小区的标识信息， 或者自身不保存任何与连接失败相关的信息。
作为一种实现方式，
第一处理模块 81具体用于： 在选定的重建小区发起 RRC连接重建请求时， 将重建小 区的标识信息保存在与连接失败相关的信息中； 以及
第二处理模块 82具体用于： 在确定重建小区不符合设定的小区选择标准或者自身未 收到重建小区所属的网络侧设备发送的 RRC 连接重建命令后， 删除该与连接失败相关的 信息中保存的重建小区的标识信息。
作为另一种实现方式，
第一处理模块 81具体用于： 在选定的重建小区发起 RRC连接重建请求时， 不在与连 接失败相关的信息中保存重建小区的标识信息。
作为再一种实现形式，
第一处理模块 81具体用于： 在选定的重建小区发起 RRC连接重建请求时， 将重建小 区的标识信息保存在与连接失败相关的信息中； 以及
第二处理模块 82具体用于： 在确定重建小区不符合设定的小区选择标准或者自身未 收到重建小区所属的网络侧设备发送的 RRC 连接重建命令后， 删除自身保存的所有与连 接失败相关的信息。
在实施中， 第二处理模块 82根据以下步骤确定自身未收到重建小区所属的网络侧设 备发送的 RRC连接重建命令：
在向重建小区所属的网络侧设备发送 RRC 连接重建请求时， 开启已配置的定时器； 以及在定时器超时时， 确定未收到重建小区所属的网络侧设备发送的 RRC连接重建命令。
基于与方法同样的发明构思， 本申请实施例提供了另一种用户设备， 如图 9所示， 该 用户设备包括处理器 91和射频单元 92:
该处理器 91被配置为， 确定 UE发生了连接失败后，在选定的重建小区通过射频单元 92发起 RRC连接重建请求； 在确定所述重建小区不符合设定的小区选择标准或自身未收 到所述重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接 失败相关的信息中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关 的信息。
本领域内的技术人员应明白， 本申请的实施例可提供为方法、 系统、 或计算机程序产 品。 因此， 本申请可釆用完全硬件实施例、 完全软件实施例、 或结合软件和硬件方面的实 施例的形式。 而且， 本申请可釆用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介盾 （包括但不限于磁盘存储器、 CD-ROM、 光学存储器等）上实施的计算机程 序产品的形式。
本申请是参照根据本申请实施例的方法、 设备（系统）、 和计算机程序产品的流程图 和 /或方框图来描述的。 应理解可由计算机程序指令实现流程图和 /或方框图中的每一流 程和 /或方框、 以及流程图和 /或方框图中的流程和 /或方框的结合。 可提供这些计算机 程序指令到通用计算机、 专用计算机、 嵌入式处理机或其他可编程数据处理设备的处理器 以产生一个机器， 使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用 于实现在流程图一个流程或多个流程和 /或方框图一个方框或多个方框中指定的功能的 装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方 式工作的计算机可读存储器中， 使得存储在该计算机可读存储器中的指令产生包括指令装 置的制造品， 该指令装置实现在流程图一个流程或多个流程和 /或方框图一个方框或多个 方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理， 从而在计算机或其他 可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和 /或方框图一个 方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例， 但本领域内的技术人员一旦得知了基本创造性概 念， 则可对这些实施例作出另外的变更和修改。 所以， 所附权利要求意欲解释为包括优选 实施例以及落入本申请范围的所有变更和修改。
显然， 本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和 范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内， 则本申请也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种进行 RRC连接重建的方法， 其特征在于， 该方法包括：
发生连接失败的用户设备 UE在选定的重建小区发起无线资源控制 RRC连接重建请 求；
所述 UE在确定所述重建小区不符合设定的小区选择标准或自身未收到所述重建小区 所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败相关的信息 中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的信息。
2、 如权利要求 1所述的方法， 其特征在于，
所述 UE在所述重建小区发起 RRC连接重建请求时，将所述重建小区的标识信息保存 在与连接失败相关的信息中；
所述 UE在确定所述重建小区不符合设定的小区选择标准或者自身未收到所述重建小 区所属的网络侧设备发送的 RRC 连接重建命令时， 删除所述与连接失败相关的信息中保 存的所述重建小区的标识信息。
3、 如权利要求 1所述的方法， 其特征在于，
所述 UE在所述重建小区发起 RRC连接重建请求时，不在与连接失败相关的信息中保 存所述重建小区的标识信息。
4、 如权利要求 1所述的方法， 其特征在于，
所述 UE在所述重建小区发起 RRC连接重建请求时，将所述重建小区的标识信息保存 在与连接失败相关的信息中；
所述 UE在确定所述重建小区不符合设定的小区选择标准或者自身未收到所述重建小 区所属的网络侧设备发送的 RRC 连接重建命令时， 删除自身保存的所有与连接失败相关 的信息。
5、如权利要求 1~4任一项所述的方法， 其特征在于， 所述 UE根据以下步骤确定自身 未收到所述重建小区所属的网络侧设备发送的 RRC连接重建命令：
所述 UE在向所述重建小区所属的网络侧设备发起 RRC连接重建请求时，开启已配置 的定时器；
在所述定时器超时时， 所述 UE 确定未收到所述重建小区所属的网络侧设备发送的 RRC连接重建命令。
6、 一种用户设备， 其特征在于， 该用户设备发生了连接失败， 且该用户设备包括： 第一处理模块， 用于在选定的重建小区发起无线资源控制 RRC连接重建请求； 第二处理模块， 用于在确定所述重建小区不符合设定的小区选择标准或自身未收到所 述重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失败 相关的信息中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的信 息。
7、 如权利要求 6所述的用户设备， 其特征在于，
所述第一处理模块具体用于： 在所述重建小区发起 RRC 连接重建请求时， 将所述重 建小区的标识信息保存在与连接失败相关的信息中；
所述第二处理模块具体用于： 在确定所述重建小区不符合设定的小区选择标准或者自 身未收到所述重建小区所属的网络侧设备发送的 RRC 连接重建命令后， 删除所述与连接 失败相关的信息中保存的所述重建小区的标识信息。
8、 如权利要求 6所述的用户设备， 其特征在于， 所述第一处理模块具体用于： 在所述重建小区发起 RRC 连接重建请求时， 不在与连接失败相关的信息中保存所述 重建小区的标识信息。
9、 如权利要求 6所述的用户设备， 其特征在于，
所述第一处理模块具体用于： 在所述重建小区发起 RRC 连接重建请求时， 将所述重 建小区的标识信息保存在与连接失败相关的信息中；
第二处理模块具体用于： 在确定所述重建小区不符合设定的小区选择标准或者自身未 收到所述重建小区所属的网络侧设备发送的 RRC 连接重建命令后， 删除自身保存的所有 与连接失败相关的信息。
10、 如权利要求 6~9任一项所述的用户设备， 其特征在于， 所述第二处理模块根据以 下步骤确定自身未收到所述重建小区所属的网络侧设备发送的 RRC连接重建命令：
在向所述重建小区所属的网络侧设备发起 RRC 连接重建请求时， 开启已配置的定时 器； 以及在所述定时器超时时， 确定未收到所述重建小区所属的网络侧设备发送的 RRC 连接重建命令。
11、 一种用户设备， 其特征在于， 该用户设备发生了连接失败， 且该用户设备包括处 理器和射频单元：
所述处理器被配置为， 确定 UE发生了连接失败后， 在选定的重建小区通过射频单元 发起 RRC 连接重建请求； 在确定所述重建小区不符合设定的小区选择标准或自身未收到 所述重建小区所属的网络侧设备发送的 RRC 连接重建命令时， 确定自身保存的与连接失 败相关的信息中不携带所述重建小区的标识信息， 或者自身不保存任何与连接失败相关的 信息。
PCT/CN2014/072845 2013-03-05 2014-03-04 一种进行rrc连接重建的方法及用户设备 WO2014135061A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/772,075 US10356834B2 (en) 2013-03-05 2014-03-04 Method and user equipment for reestablishing RRC connection
EP14760904.4A EP2966928A4 (en) 2013-03-05 2014-03-04 METHOD AND USER DEVICE FOR RECOVERING A RRC CONNECTION

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310069100.5A CN104039023B (zh) 2013-03-05 2013-03-05 一种进行rrc连接重建的方法及用户设备
CN201310069100.5 2013-03-05

Publications (1)

Publication Number Publication Date
WO2014135061A1 true WO2014135061A1 (zh) 2014-09-12

Family

ID=51469567

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/072845 WO2014135061A1 (zh) 2013-03-05 2014-03-04 一种进行rrc连接重建的方法及用户设备

Country Status (4)

Country Link
US (1) US10356834B2 (zh)
EP (1) EP2966928A4 (zh)
CN (1) CN104039023B (zh)
WO (1) WO2014135061A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3248407A1 (en) * 2015-01-22 2017-11-29 Nokia Solutions and Networks Oy Improvement of coverage hole analysis

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9468035B2 (en) * 2014-07-21 2016-10-11 Verizon Patent And Licensing Inc. Intelligent radio resource control (RRC) connection re-establishment
EP3205169A1 (en) * 2014-10-08 2017-08-16 Nokia Solutions and Networks Oy Connection establishment robustness optimization
US10728854B2 (en) * 2016-12-30 2020-07-28 Huawei Technologies Co., Ltd. Cell handover method and terminal device
CN109246819B (zh) * 2017-05-24 2021-05-11 华为技术有限公司 一种通信方法和装置
EP3639560B1 (en) * 2017-06-15 2024-05-22 LG Electronics Inc. Method for performing a handover procedure in a wireless communication system and a device therefor
US10757618B2 (en) * 2018-02-07 2020-08-25 Lg Electronics Inc. Method and apparatus for performing handover
CN118102503A (zh) 2018-08-06 2024-05-28 三星电子株式会社 用于在移动通信系统中发送或接收信号的方法和装置
WO2020061931A1 (zh) 2018-09-27 2020-04-02 Oppo广东移动通信有限公司 一种切换上报的方法、终端设备及网络设备
EP3994915A4 (en) * 2019-07-05 2022-07-20 NEC Corporation COMMUNICATION METHOD, DEVICE AND COMPUTER READABLE MEDIA IN A WIRELESS COMMUNICATION SYSTEM
WO2021056403A1 (zh) * 2019-09-27 2021-04-01 北京小米移动软件有限公司 链路失败的信息处理方法和电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012019339A1 (en) * 2010-08-11 2012-02-16 Huawei Technologies Co., Ltd. Method for providing information in a cellular wireless communication system
CN102860078A (zh) * 2011-03-31 2013-01-02 联发科技股份有限公司 分布式无线接入自组网的失败事件报告相关
CN102932821A (zh) * 2011-08-11 2013-02-13 中兴通讯股份有限公司 一种终端上报无线链路失败报告的方法、系统和终端
WO2013020599A1 (en) * 2011-08-11 2013-02-14 Nokia Siemens Networks Oy Optimizing a handover behavior of a mobile radio communication network based on an extended report message comprising information about a performed handover

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US136331A (en) * 1873-02-25 Improvement in running-gears for vehicles
US7802015B2 (en) * 2004-01-26 2010-09-21 Tantalus Systems Corp. Communications system of heterogeneous elements
JP4334602B1 (ja) * 2008-06-17 2009-09-30 任天堂株式会社 情報処理装置、情報処理システム、および情報処理プログラム
KR101633936B1 (ko) * 2009-04-21 2016-06-28 엘지전자 주식회사 다중 반송파 시스템에서 무선연결의 설정장치 및 방법
CN102550068B (zh) * 2009-10-02 2016-02-10 三菱电机株式会社 移动通信系统
JP5429355B2 (ja) * 2010-02-26 2014-02-26 富士通株式会社 無線通信ネットワークシステム，無線通信装置，移動端末，接続先切替判定方法，および接続先変更判定方法
JP5429428B2 (ja) * 2010-08-17 2014-02-26 日本電気株式会社 ＨｅＮＢインバウンド・モビリティのためのアクセス制御失敗のハンドリング
JP5546688B2 (ja) * 2010-10-04 2014-07-09 京セラ株式会社 移動通信方法、無線端末、及びプロセッサ
US20130260766A1 (en) * 2011-01-06 2013-10-03 Lg Electronics Inc. Method for Recovering Connection Failure in Wireless Communication System and Device Therefor
US9432856B2 (en) * 2011-04-03 2016-08-30 Lg Electronics Inc. Method for deciding transmission of signal
US10660108B2 (en) * 2011-04-11 2020-05-19 Samsung Electronics Co., Ltd. Method and apparatus for efficiently transmitting information acquired by a terminal to a base station
US9591545B2 (en) * 2011-08-12 2017-03-07 Panasonic Intellectual Property Corporation Of America Handover control method, wireless communication terminal, and wireless communication device
WO2013115573A1 (en) * 2012-02-01 2013-08-08 Lg Electronics Inc. Method and apparatus for transmitting radio link failure information in wireless communication system
US9503319B2 (en) * 2012-04-12 2016-11-22 Lg Electronics Inc. Method and apparatus for transmitting configuration in wireless communication system
EP2848076A1 (en) * 2012-05-11 2015-03-18 Nokia Solutions and Networks Oy 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
US9344937B2 (en) * 2012-08-06 2016-05-17 Lg Electronics Inc. Method for reporting mobility information in wireless communication system and apparatus for supporting same
EP2912873B1 (en) * 2012-10-29 2019-04-10 Telefonaktiebolaget LM Ericsson (publ) A node and method for the connectivity management of a wireless terminal
KR20140066356A (ko) * 2012-11-23 2014-06-02 삼성전자주식회사 무선통신시스템에서 무선자원 제어 상태 불일치를 해결하기 위한 방법 및 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2012019339A1 (en) * 2010-08-11 2012-02-16 Huawei Technologies Co., Ltd. Method for providing information in a cellular wireless communication system
CN102860078A (zh) * 2011-03-31 2013-01-02 联发科技股份有限公司 分布式无线接入自组网的失败事件报告相关
CN102932821A (zh) * 2011-08-11 2013-02-13 中兴通讯股份有限公司 一种终端上报无线链路失败报告的方法、系统和终端
WO2013020599A1 (en) * 2011-08-11 2013-02-14 Nokia Siemens Networks Oy Optimizing a handover behavior of a mobile radio communication network based on an extended report message comprising information about a performed handover

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification", 3GPP TS 36.300 V11, 4, 0, 3 January 2013 (2013-01-03), XP050712024 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3248407A1 (en) * 2015-01-22 2017-11-29 Nokia Solutions and Networks Oy Improvement of coverage hole analysis

Also Published As

Publication number Publication date
EP2966928A4 (en) 2016-06-15
CN104039023B (zh) 2018-05-22
CN104039023A (zh) 2014-09-10
US10356834B2 (en) 2019-07-16
US20160014839A1 (en) 2016-01-14
EP2966928A1 (en) 2016-01-13

Similar Documents

Publication Publication Date Title
WO2014135061A1 (zh) 一种进行rrc连接重建的方法及用户设备
JP6389221B2 (ja) 無線ネットワーク問題を突き止める方法、装置、およびシステム
US9661510B2 (en) Failure event report extension for inter-RAT radio link failure
JP5698843B2 (ja) 情報を提供するための方法、移動局装置、基地局装置及び通信装置
JP5302400B2 (ja) 無線通信ネットワークにおけるハンドオーバ方法およびハンドオーバ装置
US20150036512A1 (en) Method for reporting radio link failure information
WO2013152708A1 (zh) 无线链路失败报告处理方法、异常事件统计处理方法及设备和系统
WO2010105567A1 (zh) 切换优化方法、设备及系统
EP3205171B1 (en) Enhanced timer setting for mobility robustness optimization
WO2022057783A1 (zh) 无线链路失败报告方法以及用户设备
CN110831081B (zh) 切换信息上报、切换鲁棒性优化方法及装置、存储介质、用户设备、基站
EP4181568A1 (en) Handover information reporting method and user equipment
WO2013134955A1 (zh) 判定切换失败类型的方法及其装置
US20230262565A1 (en) Method performed by user equipment, and user equipment
WO2013113247A1 (zh) 一种提高移动健壮性的方法、系统和设备
WO2023134763A1 (zh) 信息报告方法以及用户设备
KR20160025028A (ko) 정보 처리 방법 및 그 장치 및 통신 시스템
WO2023040955A1 (zh) 切换信息报告方法以及用户设备
WO2023005967A1 (zh) 切换信息报告方法以及用户设备
WO2024008076A1 (zh) 切换信息报告方法以及用户设备
WO2024067624A1 (zh) 信息报告方法以及用户设备
WO2024056024A1 (zh) 由用户设备执行的方法以及用户设备
WO2023179677A1 (zh) 无线链路失败信息报告方法以及用户设备
WO2024017237A1 (zh) 由用户设备执行的方法以及用户设备
CN118338348A (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: 14760904

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14772075

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2014760904

Country of ref document: EP