WO2023098811A1

WO2023098811A1 - Connection establishment failure reporting method, and user equipment

Info

Publication number: WO2023098811A1
Application number: PCT/CN2022/135902
Authority: WO
Inventors: 常宁娟; 刘仁茂
Original assignee: 夏普株式会社; 常宁娟
Priority date: 2021-12-03
Filing date: 2022-12-01
Publication date: 2023-06-08
Also published as: CN116233917A

Abstract

Provided in the present disclosure are a connection establishment failure (CEF) reporting method, and a user equipment (UE). The connection establishment failure reporting method comprises: a UE determining whether a connection failure event, which serves as a CEF, occurs, and when the connection failure event occurs, the UE determining, on the basis of the downlink quality of a failed cell, whether to record information of the connection failure event in a CEF report.

Description

Connection establishment failure reporting method and user equipment

technical field

The present disclosure relates to a connection establishment failure reporting method and user equipment in the technical field of wireless communication.

Background technique

In a wireless network, network optimization can achieve the purpose of optimizing network performance. Generally, data collection and data analysis are carried out on the existing deployed and operating networks to find out the reasons that affect the network quality, and to improve network performance by modifying the configured network parameters, adjusting the network structure and deployed equipment, etc. For Self-configuration and Self-Optimization Network (SON), it refers to the process of automatically adjusting the network based on measurements/performance measurements of user equipment and/or base stations. The network side may configure user equipment (User Equipment, UE) to perform SON measurement. The SON function includes many aspects, such as the Automatic Neighbor Relation Function (ANR, Automatic Neighbor Relation Function) used to reduce the operator’s neighbor management burden, and the Mobile Load Balancing function (MLB, Mobility Load Function) used to balance the responsibility between different cells. Balancing), mobile robustness optimization function (MRO, Mobility Robustness Optimization) for optimizing mobile performance, random access channel optimization function for optimizing random access channel parameters and radio link failure for optimizing coverage and MRO reporting functions, etc.

In addition, Minimization of Drive Tests (MDT) technology is also an important means for operators to optimize their networks. The related parameters of network optimization are obtained from the drive test data obtained by the UE, and based on the analysis of these data, the status of network deployment and operation is obtained, so as to make decisions on how to improve the operation status of the network. The main application scenarios of MDT are coverage optimization, capacity optimization, mobility management optimization, Quality of Service (QoS) parameter optimization, and public channel parameter configuration optimization.

The 3rd Generation Partnership Project (3rd Generation Partnership Project: 3GPP) RAN plenary meeting approved a version 17 new work item on the further enhancement of the new radio technology (NR, New Radio) (see RP-201281: New WID on enhancement of data collection for SON/MDT in NR and EN-DC). One of the goals of its research project is to further enhance the functions of SON/MDT for NR systems of version 16 and earlier, including the coverage optimization problem in MDT.

The connection establishment failure (Connection Establishment Failure, CEF) report is the UE's record of the network status when the initial connection establishment occurs, so as to be used by the network side to optimize the network coverage problem.

This disclosure aims to realize the CEF reporting problem in the MDT function in the next-generation wireless (New generation Radio Access, NR) network, and further, to realize the multiple problems introduced in the case of solving the mismatch between the uplink coverage and the downlink coverage of the network. CEF reporting issues.

Contents of the invention

The main purpose of the present disclosure is to provide a connection establishment failure reporting method and user equipment, so that in a system that supports multiple CEF reports, the recording and reporting of redundant CEF information can be reduced, thereby reducing the number of UEs due to record redundancy. The UE memory consumption caused by CEF information and the resulting signaling overhead.

According to the first aspect of the present disclosure, there is provided a connection establishment failure reporting method, including: a user equipment UE judges whether a connection failure event occurs as a connection establishment failure, and if the connection failure event occurs, the UE Whether to record the connection failure event information in the connection establishment failure CEF report is determined based on the downlink quality of the failed cell.

In the connection establishment failure reporting method of the first aspect, when the connection failure event occurs, the cell identity of the current failed cell is equal to the cell identity of one or more failed cells in the CEF report, and the When the UE determines that the difference between the downlink quality of the failed cell that failed to connect this time and the downlink quality recorded in the cell identifiers of the same one or more failed cells in the CEF report exceeds a threshold value, the The UE records the information of the connection failure event in the CEF report.

In the connection establishment failure reporting method of the first aspect, it may be determined that the downlink quality of the failed cell whose connection failed this time is the same as the cell identity of the one or more failed cells in the CEF report. When the recorded downlink quality difference does not exceed the threshold value, the UE does not record the connection failure event information.

In the connection establishment failure reporting method of the first aspect, the UE may add an item in the CEF variable of the CEF report, and record the information of the connection failure event in this item.

In the connection establishment failure reporting method of the first aspect, the downlink quality may include at least one of Reference Signal Received Power RSRP, Reference Signal Received Quality RSRQ, Signal Interference and Noise Ratio SINR, and Reference Signal Strength Indicator RSSI.

In the connection establishment failure reporting method of the first aspect, the threshold value can be configured by the base station to the UE through system information or a dedicated radio resource control RRC message, or it can be a pre-configured default value, or it can be obtained from the core network side acquired.

In the connection establishment failure reporting method of the first aspect, the information of the connection failure event may include: measurement results of failed cells, location information, measurement results of neighboring cells, number of connection failures, random access information, and secondary connection failure events At least one of the elapsed times from occurrence to reporting.

In the connection establishment failure reporting method of the first aspect, when the connection failure event occurs, the UE further determines whether to record the connection failure event in the CEF report based on the downlink quality of the neighboring cell information.

According to the second aspect of the present disclosure, there is provided a connection establishment failure reporting method, including: a user equipment UE judges whether a connection failure event occurs as a connection establishment failure, and if the connection failure event occurs, the UE Judging whether the cell ID of the current failed cell is equal to one or more failed cell IDs stored in the connection establishment failure CEF report; The UE directly records the information of the connection failure event in the CEF report.

According to a third aspect of the present disclosure, there is provided a user equipment, including: a processor; and a memory storing instructions; wherein, when the instructions are executed by the processor, the above connection establishment failure reporting method is executed.

Invention effect

According to the connection establishment failure reporting method and the user equipment disclosed in the present disclosure, it is possible to reduce the recording and reporting of redundant CEF information in a system that supports multiple CEF reports, thereby reducing the UE caused by recording redundant CEF information. Memory consumption and the resulting signaling overhead.

Description of drawings

The above and other features of the present disclosure will become more apparent from the following detailed description in conjunction with the accompanying drawings, in which:

FIG. 1 is a flowchart showing a connection establishment failure reporting method in Embodiment 1 as an example of the present disclosure.

FIG. 2 is a flowchart showing a connection establishment failure reporting method in Embodiment 2 as an example of the present disclosure.

Fig. 3 shows a block diagram of a user equipment according to an embodiment of the present disclosure.

Detailed ways

Other aspects, advantages and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description of exemplary embodiments of the present disclosure in conjunction with the accompanying drawings.

In this disclosure, the terms "include" and "comprising" and their derivatives mean to include but not to limit; the term "or" is inclusive, meaning and/or.

In this specification, the various embodiments described below to describe the principles of the present disclosure are illustrative only and should not be construed in any way to limit the scope of the disclosure. The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes numerous specific details to aid in understanding, but these should be considered as examples only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness. In addition, the same reference numerals are used for similar functions and operations throughout the drawings.

In the following, the NR mobile communication system is taken as an example application environment, and multiple implementations according to the present disclosure are described in detail. However, it should be pointed out that the present disclosure is not limited to the following embodiments, but is applicable to more other wireless communication systems, such as an LTE system connected to a 5G core network.

The base station in this disclosure can be any type of base station, including Node B, enhanced base station eNB, 5G communication system base station gNB; or micro base station, pico base station, macro base station, home base station, etc.; the cell can also be any type of base station described above The cell can also be a beam (beam), a transmission point (Transmission point, TRP), and a base station can also be a central unit (gNB-Central Unit, gNB-CU) or a distributed unit (gNB-Distributed Unit, gNB-DU). Unless otherwise specified, in this disclosure, the concept of a cell and a base station can be interchanged; the LTE system is also used to refer to 5G and its subsequent LTE system (such as an eLTE system, or an LTE system that can be connected to the 5G core network ), and LTE can be replaced by Evolved Universal Terrestrial Radio Access (E-UTRA) or Evolved Universal Terrestrial Radio Access Network (E-UTRAN). Different embodiments can also work in combination, for example, the same variables/parameters/nouns in different embodiments are given the same explanation. Cancel, Release, Delete, Empty and Clear etc. can be substituted. Execution, use, and application are interchangeable. Configuration and reconfiguration can be replaced. Monitor and detect are interchangeable.

Some existing mechanisms involved in the present disclosure will be described first below. It should be noted that some names in the following description are only illustrative examples rather than limitations, and other names may also be used.

Mobile state judgment criteria for UE idle state/inactive state

In current 3GPP specifications, a UE in RRC idle state or RRC inactive state can estimate its mobility status based on the number of occurrences of cell reselection within a period of time. The UE acquires related parameters TCrmax, NCR_H, NCR_M and TCrmaxHyst from the system information of the serving cell where it camps. When the number of cell reselections within a certain period of TCrmax is less than NCR_M, the UE determines that it meets the normal speed state criterion and enters the normal speed state; when the number of cell reselections within a certain period of TCrmax is greater than or equal to NCR_M but less than or equal to When NCR_H, UE judges that it satisfies the medium-speed state criterion and enters the medium-speed state; when the number of cell reselections within a period of time is greater than NCR_H, the UE determines that it meets the high-speed state criterion and enters the high-speed state.

CEF report:

Connection Establishment Failure (CEF) reporting is supported in the NR system of version 16. The network side evaluates the coverage status of the network by collecting the information in the CEF report reported by the UE, such as whether the coverage of the cell is sufficient, whether there is a coverage hole in the network deployment, and so on.

When the connection fails (for example, the Radio Resource Control (RRC) connection establishment process fails or the RRC connection recovery process fails), the UE saves the information corresponding to the failure event in the UE variable VarConnEstFailReport corresponding to the CEF report. Generally speaking, when the RRC connection establishment process monitoring timer (such as T300) expires, the UE considers the RRC connection establishment process to fail; when the RRC connection recovery process monitoring timer (such as T319) expires, the UE considers the RRC connection recovery process to fail. When the UE has a saved CEF report in the variable VarConnEstFailReport, the UE will include a connEstFailInfoAvailable information element in the RRC message (such as RRC recovery complete message, RRC establishment complete message, RRC reconfiguration complete message) to inform the base station that there is a saved CEF report on it. CEF report. The base station sends a UEinformationRequest message to the UE, which includes a CEF report request indication (connEstFailReportReq information element), and is used to request the UE to report the stored CEF report information. After receiving the UEinformationRequest message containing the indication, the UE includes the stored CEF report (ConnEstFailReport information element) in the UEinformationReponse message to report to the base station. The connection failure event in the NR system of version 16 includes the failure of the RRC connection establishment process or the failure of the RRC connection recovery process, but the connection failure event described in this disclosure is not limited to these two cases, such as the RRC re-establishment process Failure (such as related timer T301 timeout or T311 timeout), it can also be small data transmission (Small Data Transmission, SDT) process failure (small data transmission related RRC timer timeout.)

The CEF report supported in the NR system of version 16 includes the following content: measurement results of failed cells, location information, measurement results of neighboring cells, number of connection failures, random access information, and the experience from the occurrence of connection failure events to reporting time. Among them, the measurement results of the failed cell refer to the measurement results of the serving cell/resident cell when the connection failure occurs (such as Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Reference Signal Strength Indicator (Received Signal Strength Indicator, RSSI) and Signal Interference Noise Ratio (Signal Interference Noise Radio, SINR), etc.); the measurement results of neighboring cells refer to the measurement of one or more neighboring cells when a connection failure event occurs Results; the location information refers to the absolute location when the connection failure event occurs, and the UE with the positioning function can record this information; the number of connection failures refers to the latest value of the continuous connection failure process in the same cell; the random access information refers to Information about the random access procedure executed during the connection failure (including information about each random access attempt such as the perRAInfoList information element).

The CEF report of version 16 only saves the detailed information of the latest connection establishment/restoration failure, that is, the information in the above CEF report except the number of connection failures is for the latest connection failure. Although the number of connection failures (numberOfConnFail information element) records information about other failures in the same cell except for the latest connection failure, it is only a simple number of failures and does not include the details of when the failure event occurred. Network status information such as measurement results or random access information. In the discussion of 3GPP, it is believed that this CEF report causes the failure information of other connection establishment attempts to be lost except for the latest failure event, causing the network side to be unable to obtain the failure information corresponding to other connection establishment attempts, thereby solving the problem for the network side. The coverage problem, especially the mismatch between uplink and downlink coverage is unfavorable.

A feasible method is to introduce multiple CEF reports, that is, the UE can store and report detailed information of multiple failure events to the network side, and each CEF report can correspond to one or more failure events. One problem with this multiple CEF report (also called CEF report list) is the overhead it brings, for example, the UE needs more storage space to save these multiple CEF report information, and at the same time, the CEF report will also Generate more signaling overhead. For example, in a scenario, after a connection establishment/resumption attempt fails, the UE will generally initiate a connection attempt again immediately in consideration of the UE's data transmission requirements, that is to say, the UE may initiate multiple connections at the same or similar location. Connection attempts, which may be failures if there are problems with coverage in the area. If all the details of these failure events are recorded in the CEF report, unnecessary UE storage space occupation and reporting signaling overhead will be generated, because these failure events are actually related to the coverage problem of the same location/area , if all are recorded and reported to the network side, it is actually unnecessary information redundancy.

3GPP reference R2-2101253 proposes to introduce a prohibition timer to control the frequency of UE recording CEF information, that is, when the time between the occurrence of a new CEF event and the time between the last CEF event exceeds the value of the timer, the UE allows Record the failure information of this new CEF event in the CEF report. Reference R2-2108543 proposes a method other than time-based, that is, location-based CEF recording. For connection failure events with similar or identical location information, only one failure information of the connection failure event is recorded without recording other failure event information. The possible problem with the time-based (or prohibit timer or periodic timer) scheme is that for a UE with a fast moving speed, if two consecutive connection failure events occur, even if the time between the two failure events is less than The defined time (timer duration), there is also a possibility that these two failure events are actually for the coverage of different locations or areas, then the event-based solution may cause the latter connection failure information omissions. As for the CEF recording method based on location information, it depends on the ability of the UE to support the location function, but not all UEs have this location/positioning function, which makes this method impossible to implement on such UEs.

This disclosure mainly proposes a solution to the above-mentioned problem of how to reduce the recording and reporting of redundant CEF information in a system that supports multiple CEF reports. The following examples of the disclosure provide specific implementation methods for this problem. Through this In the disclosed solution, the UE does not record unnecessary CEF event failure information in the CEF report, or does not report unnecessary CEF event failure information to the network side, thereby saving UE memory consumption and corresponding signaling overhead.

Example 1

This embodiment provides a method for recording CEF reports under multiple CEF reporting mechanisms executed on the UE. Through the method described in this embodiment, the UE can avoid recording redundant information in the CEF report for information about multiple failure events occurring in the same location/area.

Hereinafter, Embodiment 1 of the present invention will be described based on FIG. 1 . FIG. 1 is a flowchart showing a connection establishment failure reporting method in Embodiment 1 as an example of the present disclosure.

In one implementation manner, as shown in FIG. 1 , in step S101 , the UE determines whether a connection failure event occurs as a connection establishment failure. When a connection failure event occurs, in step S102, the UE determines whether to record the information of the connection failure event in the CEF report based on the downlink quality of the failed cell. Specifically, for example, based on the downlink quality (or downlink signal measurement result) of the failed cell, the UE determines whether to record information about a connection failure event in its CEF variable. Specifically, when a connection failure event occurs (such as RRC connection establishment process failure or RRC connection recovery process failure), if the cell identity of the current failed cell is equal to the one or more failed cells in the CEF variable (such as VarConnEstFailReport or VarConnEstFailReportList) The cell identifier (such as the cell identifier in the measResultFailedCell information element), the UE further judges that the downlink quality of the failed cell whose connection failed this time is the same as the downlink quality recorded in the cell identifier of one or more failed cells in the CEF variable Whether the link quality difference exceeds a threshold. If yes, the UE records the failure information of the failure event in the CEF variable, such as adding an item to the CEF variable, and records the failure information in the item, if not, the UE does not record the failure related information information.

That is to say, for the same cell, when a new connection failure event occurs, the UE judges that the downlink quality of the cell at the time of the connection failure event is the same as that of the cell previously recorded in the CEF report Whether the difference of the downlink quality of the cell in the information related to other failure events exceeds a threshold value, when the difference of the downlink quality does not exceed a threshold value (the failure corresponding to this connection failure event The downlink quality of the cell is greater or lower than that of other recorded failure events of the cell (the downlink quality of the failed cell corresponding to the failed cell does not exceed a threshold value), it is generally considered that the failure event and other recorded failure events occurred at the location / area is the same or similar, at this time, the UE does not record the information of the newly occurred connection failure event in the CEF report, so as to avoid recording unnecessary redundant information.

The downlink quality can also be called the downlink signal measurement result of the failed cell, for example, it can be reference signal received power RSRP, reference signal received quality RSRQ, or signal-to-interference and noise ratio SINR, or reference signal strength indicator RSSI or other characterizations One or more of the link quality values. For example, when the downlink quality is RSRP and RSRQ, then when the difference between the downlink quality RSRP does not exceed a threshold value TH1 and the difference between the downlink quality RSRQ does not exceed a threshold value TH2, At this time, the UE does not record information about the newly occurred connection failure event in the CEF report.

The threshold or difference on the UE can be configured by the network side, such as configured by the base station to the UE through system information or a dedicated RRC message, or it can be a pre-configured default value, or it can be obtained from the core network side of.

The recorded failure information, as described above, includes measurement results of failed cells, location information, measurement results of neighboring cells, number of connection failures, random access information, and time elapsed from the occurrence of connection failure events to reporting, etc.

Optionally, when the UE determines whether to record the CEF information of the failure event, in addition to the downlink quality of the failed cell, it is also based on the downlink quality of neighboring cells. For example, when a connection failure event occurs, if the difference between the downlink quality of the failed cell does not exceed a threshold value (the first threshold value) as mentioned above, and the difference between the downlink quality of the neighboring cells does not exceed another threshold value When the limit value (the second threshold value), at this time, the UE does not record the information of the newly occurred connection failure event in the CEF report. The first threshold and the second threshold may be the same threshold or different thresholds. For example, when a connection failure event occurs, if the difference in the downlink quality of the failed cells does not exceed a threshold value as mentioned above, and the best neighboring cells corresponding to the two failure events are the same neighboring cell (best IDs of neighboring cells are the same), at this time, the UE does not record the information of the newly occurred connection failure event in the CEF report. The best neighbor cell refers to the neighbor cell with the best measurement result. The best neighbor cell can also be the best two or more neighbor cells. For example, the neighbor cells corresponding to this failure event are N_Cell 1, N_Cell 2, and N_Cell3 according to the measurement results from good to worse. The corresponding neighboring cells in the recorded information of another failure event of the failed cell are also N_Cell 1, N_Cell 2, and N_Cell 3 according to the measurement results from good to bad, which is equivalent to the aforementioned "identity of the best neighboring cell". In this implementation, when determining whether to record the information of this failure event, in addition to the downlink quality of the failed cell based on this failure event and other failure events of the same cell that have been recorded, the Based on the downlink quality of a neighboring cell corresponding to this failure event and the same neighboring cell corresponding to other recorded failure events of the same cell.

For the convenience of description, the above-mentioned methods/criteria for preventing UE from recording unnecessary failure information are called restriction methods/criteria, such as the aforementioned restriction method based on downlink quality, and the corresponding configuration is as follows: Downlink quality threshold value It is called a restricted configuration.

In an implementation method, when the UE is not configured with the restriction configuration, the UE does not execute the restriction method, that is, each time a connection failure event occurs, the UE records the connection failure corresponding to the event in the UE variable related information.

In one implementation method, when a connection failure event occurs, if the UE judges to record the information of the failure event in the CEF variable, if the number of items reported by CEF recorded in the CEF variable on the UE exceeds one If the predefined maximum value is 8, the UE should remove the oldest CEF report item from the CEF variable before recording the information of this connection failure event, and then add a new item to the CEF variable to record the connection failure event. Failed information.

The UE can be configured with more than one restriction method at the same time, such as configuring the restriction method based on downlink quality and the restriction method based on time at the same time (that is, the restriction method based on the prohibition timer/periodic timer described in the prior art) . In this case, one method is that when a connection failure event occurs, the UE records the CEF information of the connection failure in the CEF variable only when the conditions of all the configured restriction methods are satisfied. Another method is that when a connection failure event occurs, the UE records the CEF information of the connection failure in the CEF variable as long as the conditions of one of the configured restriction methods are met.

Example 2

This embodiment provides a method for recording a CEF report implemented on a UE.

Hereinafter, Embodiment 2 of the present invention will be described based on FIG. 2 . FIG. 2 is a flowchart showing a connection establishment failure reporting method in Embodiment 2 as an example of the present disclosure.

As shown in FIG. 2, in step S201, the UE determines whether a connection failure event occurs as a connection establishment failure. Next, in step S202, when a connection failure event occurs, the UE judges whether the cell ID of the current failed cell is equal to one or more failed cell IDs stored in the connection establishment failure CEF report. In step S203, when judging that they are not equal to one or more failed cell identifiers stored in the CEF report, the UE directly records the information of the connection failure event in the CEF report.

Specifically, when a connection failure event occurs on the UE (such as the failure of the RRC connection establishment process or the failure of the RRC connection recovery process), the UE judges whether the cell identity of the current failed cell is equal to one or more CEF items stored in the CEF variable If not, the UE records the failure information corresponding to the failure event in the CEF variable, such as adding a new item to record the failure information of the failure event. That is to say, if the current failed cell has not been recorded in the CEF variable before, then this failure event is actually the first failure event experienced by the UE in this cell, and at this time, the UE does not need to implement the restriction method of CEF information recording (such as the restriction method described in Embodiment 1) to determine whether to record its information, and directly record the failure information corresponding to the failure event of the cell in the CEF variable.

Example 3

This embodiment provides a method for reporting a CEF report. Through the method described in this embodiment, for a UE supporting multiple CEF reports of Release 17, it may be determined whether to report a single CEF report based on Release 16 or multiple CEF reports based on Release 17 to the network side.

Step 1: The UE receives a UEInformationRequest message from the network side, which includes request indication information for requesting the UE to report the stored CEF report.

Step 2: The UE judges whether to report multiple CEF reports to the network side based on the indication information. Specifically, if the indication information indicates that the UE reports a single CEF report (connEstFailReportReq-R16 information element), the UE includes the CEF information corresponding to the latest connection failure event in the UEInformationResponse message, and reports it to the network side; if the The above indication information instructs the UE to report multiple CEF reports (such as the connEstFailReportReq-R17 information element), then the UE includes all multiple CEF information stored in the CEF variable in the UEInformationResponse message, and reports it to the network side.

Example 4

This embodiment provides a method for recording a time-based CEF report. Through the method described in this embodiment, the UE sets the time value according to the speed information to determine whether to record a CEF failure event in the CEF variable The corresponding failure message.

The time-based CEF report recording method, as mentioned above, when a connection failure event occurs in a cell CellA (such as denoted as CEF3), if there is a CEF report item ( If denoted as CEF1), UE judges whether the time between CEF3 and CEF1 occurrence is less than a time threshold value, if not, then UE adds a new CEF report item in the CEF variable to record the CEF information of CEF3; If so, UE Not documented for CEF3. Optionally, if there is a plurality of CEF report items (such as denoted as CEF1 and CEF2) of the same failed cell identifier as CellA in the CEF variable of the UE, the UE judges the CEF event (such as CEF2) and CEF3 of the latest CellA in the CEF variable Whether the time between occurrences is less than a time threshold value, if not, the UE adds a new CEF report item in the CEF variable to record the CEF information of CEF3.

In this embodiment, considering the influence of different UE speeds, several different time thresholds are set. Preferably, three different time thresholds are set, each corresponding to a different UE speed. For example, a time threshold value of 1 corresponds to a high speed, a time threshold value of 2 corresponds to a medium speed, a time threshold value of 3 corresponds to a normal speed, and so on. Based on the judgment of its own speed, the UE applies a corresponding time threshold value to execute the above time-based CEF report recording method. In an implementation manner, the time thresholds corresponding to the several levels are directly configured or predefined by the network side, for example, three thresholds TH, TH-high, and TH-Medium are explicitly configured. In another implementation, the time thresholds corresponding to the several gears are configured by the network side with one of the thresholds and multiple scale factors, such as configuring the normal speed threshold TH and the scale factor scalefactor corresponding to the high speed -Scalefactor scalefactor-medium for high and medium speeds. When the UE judges that its moving speed is in a high-speed state, use the normal speed threshold value TH*scale factor-high to obtain the corresponding high-speed time threshold value; when the UE judges that its moving speed is in a medium-speed state, use the normal speed gate The limit value TH*scale factor-medium is used to obtain the corresponding high-speed time threshold value; when the UE judges that its moving speed is in the normal speed state, the normal speed threshold value TH is directly used.

As mentioned above, the different time threshold values of the several files may be configured to the UE by the network side through system messages or RRC dedicated signaling, or may be predefined default values, or obtained by the UE from the core network (such as through Non-access stratum (Non Access Stratum, NAS) signaling acquisition). In addition, the time can be implemented in multiple ways, such as through a timer. At this time, the time threshold value can also be called the maximum value/configuration value of the timer, which is not limited in the present disclosure. The name and implementation of the time threshold. The determination of the mobility state of the UE may be based on the method for determining the mobility state of the UE based on the number of cell reselections in the current 3GPP protocol as described above, which is not limited in this disclosure.

Example 5

This embodiment provides a timer management method in the time-based CEF report recording method.

In this embodiment, the time threshold value described in Embodiment 4 is realized by a CEF record-related timer. When the UE generates a CEF event and determines to add an item to the CEF variable to record the CEF information corresponding to the CEF event, the UE starts the timer. In fact, the timer defines the minimum value of the difference between the occurrence times of two CEF events (CEF report items) in the CEF variable. Preferably, the two CEF events refer to CEF events of the same failed cell.

When the UE undergoes cell reselection, if there is a running CEF record-related timer on the UE, the UE stops the timer. That is to say, only one CEF record-related timer is maintained on the UE at the same time, and when the cell where the UE resides changes, the UE stops the running timer.

When the RRC connection establishment procedure of the UE is successfully completed or the RRC connection recovery procedure is successfully completed, if there is a running CEF record-related timer on the UE, the UE stops the timer. That is to say, once the connection with the network side is successfully entered into the connected state, the UE stops the running timer. The successful completion of the RRC connection establishment process means that the UE successfully receives the RRC establishment message (at this time T300 stops), and the successful completion of the RRC connection recovery process means that the UE successfully receives the RRC recovery message (at this time T319 stops). Apparently, before this, the UE initiates an RRC connection establishment or RRC connection recovery process, and sends an RRC establishment request message or an RRC recovery request message to the network side.

The UE variables in the foregoing embodiments are UE variables used to record CEF reports, or CEF variables (such as VarConnEstFailReport or VarConnEstFailReportList).

Example 6

FIG. 3 is a block diagram representing a user equipment 30 according to an embodiment of the present disclosure. As shown in FIG. 3 , the user equipment 30 includes a processor 301 and a memory 302 . The processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, and the like. The memory 302 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories. Memory 302 has program instructions stored thereon. When the instruction is executed by the processor 301, it can execute the above random access reporting method in the user equipment described in detail in this disclosure.

The program running on the device according to the present disclosure may be a program that causes a computer to realize the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), nonvolatile memory (such as flash memory), or other memory systems.

A program for realizing the functions of the various embodiments of the present disclosure can be recorded on a computer-readable recording medium. The corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs. The so-called "computer system" here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices). The "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium in which a short-term dynamic storage program is stored, or any other recording medium readable by a computer.

Various features or functional modules of the devices used in the above-mentioned embodiments may be implemented or executed by circuits (for example, single-chip or multi-chip integrated circuits). Circuits designed to perform the functions described in this specification may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above. A general-purpose processor can be a microprocessor, or it can be any existing processor, controller, microcontroller, or state machine. The above-mentioned circuits may be digital circuits or analog circuits. Where new integrated circuit technologies have emerged to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

In addition, the present disclosure is not limited to the above-described embodiments. Although various examples of the embodiments have been described, the present disclosure is not limited thereto. Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

As above, the embodiments of the present disclosure have been described in detail with reference to the drawings. However, the specific structure is not limited to the above embodiments, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. In addition, components having the same effect described in the above embodiments can be substituted for each other.

Claims

A connection establishment failure reporting method, comprising:

The user equipment UE determines whether a connection failure event occurs as a connection establishment failure,

When the connection failure event occurs, the UE determines whether to record the connection failure event information in the connection establishment failure CEF report based on the downlink quality of the failed cell.
The connection establishment failure reporting method according to claim 1, wherein,

When the connection failure event occurs, the cell identity of the current failed cell is equal to the cell identity of one or more failed cells in the CEF report, and the UE determines that the downlink of the failed cell that failed to connect this time When the difference between the link quality and the downlink quality recorded by the cell identifiers of the same one or more failed cells in the CEF report exceeds a threshold value, the UE records the connection failure event in the CEF report information.
The connection establishment failure reporting method according to claim 2, wherein,

When the UE judges that the difference between the downlink quality of the failed cell that failed to connect this time and the downlink quality recorded in the cell identifiers of the same one or more failed cells in the CEF report does not exceed the threshold value When , the UE does not record the information of the connection failure event.
The connection establishment failure reporting method according to claim 1 or 2, wherein,

The UE adds an item to the CEF variable reported by the CEF, and records the information of the connection failure event in this item.
The connection establishment failure reporting method according to claim 1 or 2, wherein,

The downlink quality includes at least one of Reference Signal Received Power RSRP, Reference Signal Received Quality RSRQ, Signal Interference and Noise Ratio SINR, and Reference Signal Strength Indicator RSSI.
The connection establishment failure reporting method according to claim 2, wherein,

The threshold value is configured by the base station to the UE through system information or a dedicated radio resource control RRC message, or is a pre-configured default value, or is obtained from the core network side.
The connection establishment failure reporting method according to claim 1 or 2, wherein,

The information of the connection failure event includes: at least one of measurement results of the failed cell, location information, measurement results of neighboring cells, number of connection failures, random access information, and time elapsed from the occurrence of the connection failure event to reporting.
The connection establishment failure reporting method according to claim 1, wherein,

When the connection failure event occurs, the UE further determines whether to record the information of the connection failure event in the CEF report based on the downlink quality of the neighboring cell.
A connection establishment failure reporting method, comprising:

The user equipment UE determines whether a connection failure event occurs as a connection establishment failure,

When the connection failure event occurs, the UE judges whether the cell ID of the current failed cell is equal to one or more failed cell IDs stored in the connection establishment failure CEF report,

When judging that they are not equal to one or more failed cell identifiers stored in the CEF report, the UE directly records the information of the connection failure event in the CEF report.
A user equipment UE, comprising:

processor; and

a memory storing instructions;

Wherein, the instruction executes the connection establishment failure reporting method according to any one of claims 1-9 when executed by the processor.