CN116233917A

CN116233917A - Connection establishment failure reporting method and user equipment

Info

Publication number: CN116233917A
Application number: CN202111471782.3A
Authority: CN
Inventors: 常宁娟; 刘仁茂
Original assignee: Sharp Corp
Current assignee: Sharp Corp
Priority date: 2021-12-03
Filing date: 2021-12-03
Publication date: 2023-06-06
Also published as: WO2023098811A1

Abstract

The disclosure provides a connection establishment failure reporting method and user equipment. The connection establishment failure reporting method comprises the following steps: the user equipment UE determines whether a connection failure event occurs as a connection establishment failure, and in case the connection failure event occurs, the UE determines whether to record information of the connection failure event in a connection establishment failure CEF report based on downlink quality of a failed cell.

Description

Connection establishment failure reporting method and user equipment

Technical Field

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

Background

The aim of optimizing the network performance can be achieved through network optimization in the wireless network. The method generally performs means such as data acquisition and data analysis on the existing deployed and operated network, finds out reasons influencing the network quality, and improves the network performance by means such as modifying configured network parameters, adjusting network structures and deployed devices. For Self-configuring and Self-optimizing networks (Self-configuration and Self-Optimization Network, SON), a process is referred to that automatically adjusts the network based on measurements/performance measurements of user equipment and/or base stations. The network side may configure a User Equipment (UE) to perform measurements for SON. The SON functions include many aspects such as an automatic neighbor relation function (ANR, automatic Neighbour Relation Function) for reducing the neighbor management burden of operators, a mobility load balancing function (MLB, mobility Load Balancing) for balancing the responsibility between different cells, a mobility robustness optimization function (MRO, mobility Robustness Optimization) for optimizing mobility performance, a random access channel optimization function for optimizing random access channel parameters, and a radio link failure reporting function for optimizing coverage and MRO, etc.

Furthermore, minimization of drive tests (Minimization of Drive Tests, MDT) technology is also an important means for operators to optimize networks. Relevant parameters of network optimization are obtained from the drive test data obtained by the UE, and based on analysis of the data, the state of network deployment and operation is obtained, so that a decision is made on how to improve the operation state of the network. The main application scenarios of MDT are coverage optimization, capacity optimization, mobility management optimization, quality of service (Quality of Service, qoS) parameter optimization, common channel parameter configuration optimization, etc.

The third generation partnership project (3rd Generation Partnership Project:3GPP) RAN has approved a release 17 New work item (see RP-201281:New WID on enhancement of data collection for SON/MDT in NR and EN-DC) for further enhancements to New wireless technology (NR). One of the targets of its research projects is a further enhancement of the function of SON/MDT for the NR system of release 16 and previous versions, including coverage optimization problems in MDT.

Connection establishment failure (Connection Establishment Failure, CEF) reporting is a record of network conditions for the UE when initial connection establishment occurs, for network side optimization of network coverage problems.

The present disclosure is directed to implementing the CEF reporting problem in MDT functions in next generation wireless (New generation Radio Access, NR) networks, and further to implementing multiple CEF reporting problems introduced in cases for solving network uplink and downlink coverage mismatch.

Disclosure of Invention

The main objective of the present disclosure is to provide a connection establishment failure reporting method and a user equipment, so as to reduce the recording and reporting of redundant CEF information in a system supporting multiple CEF reporting, thereby reducing UE memory consumption and signaling overhead caused by the UE recording the redundant CEF information.

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

In the connection establishment failure reporting method of the first aspect, when the cell identifier of the current failure cell is equal to the cell identifier of one or more failure cells in the CEF report and the UE determines that the difference between the downlink quality of the failure cell of the current connection failure and the downlink quality recorded by the cell identifier of the same one or more failure cells in the CEF report exceeds a threshold value, the UE may record the information of the connection failure event in the CEF report.

In the connection establishment failure reporting method of the first aspect, when the UE determines that a difference between the downlink quality of the failed cell of the current connection failure and the downlink quality recorded by the cell identifier of the same one or more failed cells in the CEF report does not exceed a threshold value, the UE may not record the information of the connection failure event.

In the connection establishment failure reporting method of the first aspect, the UE may add an entry in a CEF variable of a CEF report, in which information of the connection failure event is recorded.

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 to interference plus noise ratio SINR, reference signal strength indication RSSI.

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

In the connection establishment failure reporting method of the first aspect, the information of the connection failure event may include: at least one of a measurement result of a failed cell, location information, a measurement result of a neighbor cell, a number of connection failures, random access information, and a time elapsed from the occurrence of a connection failure event to reporting.

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

According to a second aspect of the present disclosure, there is provided a connection establishment failure reporting method, including: the UE judges whether a connection failure event which is the connection establishment failure occurs or not, and in the case of the connection failure event, the UE judges whether the cell identification of the current failure cell is equivalent to one or more failure cell identifications stored in a CEF report of the connection establishment failure, and in the case of judging that the cell identification is not equivalent to one or more failure cell identifications stored in the 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 comprising: a processor; and a memory storing instructions; the instructions, when executed by the processor, perform the connection establishment failure reporting method described above.

Effects of the invention

According to the connection establishment failure reporting method and the user equipment, in a system supporting multiple CEF reports, the recording and reporting of redundant CEF information can be reduced, so that the UE memory consumption and the signaling overhead caused by the recording of the redundant CEF information can be reduced.

Drawings

The above and other features of the present disclosure will become more apparent from the following detailed description when taken 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 device according to an embodiment of the present disclosure.

Detailed Description

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

In the present disclosure, the terms "include" and "comprise," along with their derivatives, are intended to be inclusive, rather than limiting; the term "or" is inclusive, meaning and/or.

In this specification, the various embodiments described below for the purpose of describing the principles of the present disclosure are illustrative only and should not be construed in any way as limiting 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 defined by the claims and their equivalents. The following description includes numerous specific details to aid in understanding, but these details should be construed as exemplary 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 present disclosure. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness. Furthermore, the same reference numerals are used for similar functions and operations throughout the drawings.

Various embodiments according to the present disclosure are specifically described below with an NR mobile communication system as an example application environment. However, it should be noted that the present disclosure is not limited to the following embodiments, but is applicable to many other wireless communication systems, such as an LTE system connected to a 5G core network, and the like.

The base station in the present disclosure may be any type of base station, including a Node B, an enhanced base station eNB, and a 5G communication system base station gNB; or a micro base station, a pico base station, a macro base station, a home base station, etc.; the cell may also be a cell under any of the above base stations, the cell may also be a beam, a transmission point (Transmission point, TRP), the base station may also be a Central Unit (gNB-Central Unit, gNB-CU) or a Distributed Unit (gNB-Distributed Unit, gNB-DU) constituting the base station. Unless specifically stated otherwise, in the present disclosure, concepts of cells and base stations may be interchanged; the LTE system is also used to refer to the 5G and later LTE systems (e.g. called the LTE system, or the LTE system that may be connected to the 5G core network), while LTE may be replaced with evolved universal terrestrial radio access (Evolved Universal Terrestrial Radio Access, E-UTRA) or evolved universal terrestrial radio access network E-UTRAN. Different embodiments may work in combination as well, such as the same variables/parameters/nouns in different embodiments are explained identically. Cancel, release, delete, empty, clear, etc. may be replaced. Execution, use, and application alternatives. Configuration and reconfiguration may be replaced. Monitoring (monitor) and detection (detect) may be substituted.

Some of the existing mechanisms to which this disclosure relates are described first below. It is noted that some of the designations in the description below are illustrative only and not limiting, and other designations are possible.

Mobility state judgment criterion of UE idle state/inactive state

In the current 3GPP specifications, a UE in an RRC idle state or an RRC inactive state may estimate its mobility state based on the number of occurrences of cell reselection over a period of time. The UE obtains the relevant parameters TCrmax, ncr_ H, NCR _m and TCrmaxHyst from the system information of the serving cell in which it resides. When the number of cell reselections within a period of time TCrmax is less than ncr_m, the UE determines that it meets a constant speed state criterion, and enters a constant speed state; when the number of cell reselections within a period of time TCrmax is greater than or equal to ncr_m but less than or equal to ncr_h, the UE determines that it meets a medium speed state criterion, and enters a medium speed state; when the number of cell reselections over a period of time is greater than ncr_h, the UE determines that it satisfies the high speed state criterion and enters a high speed state.

CEF report:

connection establishment failure (Connection Establishment Failure, CEF) reporting is supported in the NR system of release 16. The network side evaluates the coverage condition of the network, such as whether the coverage of the cell is enough or not, whether coverage holes exist in the network deployment or not, and the like, by collecting the information in the CEF report reported by the UE.

When a connection fails (e.g., a radio resource control (Radio Resource Control, RRC) connection establishment procedure fails or an RRC connection recovery procedure fails), the UE saves information corresponding to the failure event in the UE variable VarConnEstFailReport corresponding to the CEF report. Generally, when the RRC connection setup procedure monitoring timer (e.g., T300) expires, the UE considers the RRC connection setup procedure to fail; when the RRC connection recovery procedure monitoring timer (e.g., T319) expires, the UE considers the RRC connection recovery procedure to fail. When the UE has a saved CEF report in the variable VarConnEstFailReport, the UE includes a connestfailimable information element in the RRC message (e.g., RRC resume complete message, RRC setup complete message, RRC reconfiguration complete message) to inform the base station that there is a saved CEF report. The base station issues a ueincarnationrequest message to the UE, where the UE includes a CEF report request indication (connEstFailReportReq information element) for requesting the UE to report the saved CEF report information. After receiving the UEinformationRequest message containing the indication, the UE reports the saved CEF report (ConnEstFailReport information element) to the base station in a ueinformationreport message. The connection failure event in release 16 NR system includes RRC connection establishment procedure failure or RRC connection recovery procedure failure, but the connection failure event in this disclosure is not limited to these two cases, such as failure of RRC reestablishment procedure (e.g., timer T301 timeout or T311 timeout) or failure of small data transfer (Small Data Transmission, SDT) procedure (RRC timer timeout related to small data transfer)

The CEF report supported in the NR system of release 16 contains the following: the measurement result of the failed cell, the location information, the measurement result of the neighbor cell, the number of connection failures, the random access information, and the time elapsed from the occurrence of the connection failure event to the reporting. Wherein the measurement result of the failed cell refers to the measurement result of the serving cell/camping cell (such as reference signal measurement power (Reference Signal Received Power, RSRP), reference signal measurement quality (Reference Signal Received Quality, RSRQ), reference signal strength indication (Received Signal Strength Indicator, RSSI), signal-to-interference and noise ratio (Signal Interference Noise Radio, SINR), etc.) when the connection failure occurs; the measurement results of the neighbor cells refer to the measurement results of one or more neighbor cells when a connection failure event occurs; the location information refers to the absolute location where the connection failure event occurs, and the UE with the positioning function can record the 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 of a random access procedure performed in a connection failure procedure (including information of each random access attempt such as perrainfoslist information element).

Only detailed information on the last connection establishment/restoration failure is stored in the CEF report of the version 16, i.e. the above-mentioned information in the CEF report except for the connection failure number is for the last connection failure. Although the number of connection failures (number ofconnfail information element) records information of other failures in the same cell except for the connection failure occurring last time, it is also just a simple number of failures, and does not contain detailed network status information such as measurement results or random access information when a failure event occurs. In the discussion of 3GPP, it is considered that such CEF reporting causes that failure information of other connection establishment attempts except for the last failure event is lost, so that the network side cannot obtain failure information corresponding to other connection establishment attempts, which is disadvantageous to solve coverage problems, especially uplink and downlink coverage mismatch problems, on the network side.

One possible approach is to introduce multiple CEF reports, i.e. the UE may save and report detailed information of multiple failure events to the network side, each CEF report may correspond to one or more failure events. One problem with such multiple CEF reports (also referred to as a CEF report list) is the overhead that it introduces, such as the UE requiring more memory to hold the multiple CEF report information, and the CEF report reporting also incurs more signaling overhead. For example, in one scenario, after a connection establishment/restoration attempt fails, the UE typically initiates a connection attempt again immediately, taking into account the data transmission requirements of the UE, i.e., the UE may initiate multiple connection attempts at the same or similar location, which may be a failure if coverage of the area is problematic. If the detailed information of these failure events is recorded in the CEF report, unnecessary UE memory space occupation and signaling overhead are generated, because these failure events are actually for coverage problems of the same location/area, and if all the failure events are recorded and reported to the network side, they are actually unnecessary information redundancy.

It is proposed in 3GPP reference R2-2101253 to introduce a prohibit timer to control how often a UE records CEF information, i.e. when the time between the occurrence of a new CEF event and the last CEF event exceeds the value of the timer, the UE allows recording failure information of the new CEF event in the CEF report. One approach, other than time-based, is presented in references R2-2108543, namely location-based CEF recording, recording failure information of a connection failure event only once for connection failure events with similar or identical location information, without recording other failure event information. A possible problem with time-based (or prohibit timer or periodic timer) schemes is that for a UE moving faster, if two consecutive connection failure events occur, even if the time of the two failure events is less than the defined time (timer duration), there is a possibility that the two failure events are actually for coverage of different places or areas, and then the event-based scheme may lead to a missed record of the latter connection failure information. However, for the CEF recording method based on the location information, the capability of supporting the location function is dependent on the UE, but not all UEs have the location/positioning function, so that the method cannot be implemented on such UEs.

The present disclosure mainly proposes a solution to the above problem of how to reduce the recording and reporting of redundant CEF information in a system supporting multiple CEF reports, and the following embodiments of the present disclosure provide a specific implementation manner for the problem.

Example 1

The present embodiment provides a CEF report logging method under a multi-term CEF report mechanism executed on a UE. By the method described in this embodiment, the UE can avoid recording redundant information in the CEF report for the information of multiple failure events occurring in the same location/area.

Hereinafter, embodiment 1 of the present invention will be described with reference to 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, as shown in fig. 1, in step S101, the UE determines whether a connection failure event occurs as a connection establishment failure. In case that a connection failure event occurs, the UE determines whether to record information of the connection failure event in the CEF report based on the downlink quality of the failed cell in step S102. Specifically, for example, the UE determines, based on the downlink quality (or downlink signal measurement) of the failed cell, whether or not it is necessary to record information of a connection failure event that occurs in its CEF variable for that failure event. Specifically, when a connection failure event occurs (such as a failure in the RRC connection establishment procedure or a failure in the RRC connection recovery procedure), if the cell identity of the currently failed cell is equal to the cell identity of one or more failed cells in the CEF variable (such as the cell identity in the measresultfailport or the varconnesportlist), the UE further determines whether the downlink quality of the failed cell in this connection failure differs from the downlink quality recorded by the cell identity of the same one or more failed cells in the CEF variable by more than a threshold value. If yes, the UE records the failure information of the failure event in the CEF variable, if one item is added in the CEF variable, the information of the failure is recorded in the item, and if not, the UE does not record the information related to the failure.

That is, when a new connection failure event occurs in the same cell, the UE determines whether a difference between the downlink quality of the cell when the new connection failure event occurs and the downlink quality of the cell in the information related to other failure events of the cell that have been recorded in the CEF report before exceeds a threshold value, and when the difference between the downlink qualities does not exceed a threshold value (the downlink quality of the failed cell corresponding to the current connection failure event is greater than or less than the downlink quality of the failed cell corresponding to other failure events of the cell that have been recorded but not more than a threshold value), it is generally considered that the place/area where the current failure event occurs is the same as or similar to the place/area where other failure events that have been recorded, and the UE does not record the information of the new connection failure event in the CEF report at this time, so as to avoid recording unnecessary redundant information.

The downlink quality may also be referred to as a downlink signal measurement for the failed cell, and may be, for example, one or more of a reference signal received power, RSRP, a reference signal received quality, RSRQ, or a signal to interference and noise ratio, SINR, or a reference signal strength indication, RSSI, or other value characterizing link quality. For example, when the downlink qualities are RSRP and RSRQ, then when the difference between the downlink qualities RSRP does not exceed a threshold THl and the difference between the downlink qualities RSRQ does not exceed a threshold TH2, then the UE does not record information of the newly occurring connection failure event in the CEF report.

The threshold value or differential value on the UE may be configured by the network side, for example, configured to the UE by the base station through system information or dedicated RRC message, or may be a default value that is preconfigured, or may be obtained from the core network side.

The recorded failure information includes the measurement result of the failed cell, the location information, the measurement result of the neighbor cell, the number of connection failures, the random access information, the time elapsed from the occurrence of the connection failure event to the reporting, and the like, as described above.

Optionally, the UE determines whether it is necessary to record the CEF information of the failure event, based on the downlink quality of the neighbor cell in addition to the downlink quality of the failure cell. For example, when a connection failure event occurs, if the difference between the downlink qualities of the failed cells does not exceed a threshold (a first threshold) and the difference between the downlink qualities of the neighboring cells does not exceed another threshold (a second threshold) as described above, the UE does not record the information of the newly occurring connection failure event in the CEF report. The first threshold value and the second threshold value may be the same threshold value or different threshold values. For example, when a connection failure event occurs, if the difference between the downlink qualities of the failed cells does not exceed a threshold value as described above, and the best neighbor cells corresponding to the two failed events are the same neighbor cell (best neighbor cell identity is the same), the UE does not record the information of the newly occurring connection failure event in the CEF report. And the best neighbor cell refers to the neighbor cell with the best measurement result. The best neighbor Cell may also be two or more best neighbor cells, for example, the neighbor cells corresponding to the current failure event are n_cell1, n_cell2, n_cell3 in sequence from good to bad according to the measurement result, and the neighbor cells corresponding to the other primary failure event information of the failure Cell recorded in the cef variable are n_cell1, n_cell2, n_cell3 in sequence from good to bad according to the measurement result, which is equivalent to the foregoing "best neighbor Cell identifier". In this implementation, when determining whether to record the information of the current failure event, in addition to the downlink quality of the failure cell based on the current failure event and other failure events of the same recorded cell, the downlink quality of the same neighbor cell corresponding to the current failure event and other failure events of the same recorded cell is also based on the downlink quality of the same neighbor cell corresponding to the current failure event.

For convenience of description, the above method/criteria for avoiding the UE from recording unnecessary failure information is referred to as a limiting method/criteria, such as the above downlink quality based limiting method, and the corresponding configuration is referred to as a limiting configuration as a downlink quality threshold value.

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

In one implementation, when a connection failure event occurs, if the UE determines that the information of the connection failure event is to be recorded in the CEF variable, if the number of entries of the CEF report recorded in the CEF variable on the UE has exceeded a predefined maximum value, such as 8, the UE first removes the oldest entry of the CEF report from the CEF variable before recording the information of the connection failure event, and then adds a new entry to the CEF variable to record the information of the connection failure.

The UE may be configured with more than one restriction method at the same time, e.g., as a synchronization configuration downlink quality based restriction method and a time based restriction method (i.e., a prohibit timer/period timer based restriction method as described in the prior art). In this case, one method is that, when a connection failure event occurs, the UE records CEF information of the connection failure in the CEF variable only when the conditions of all the configured restriction methods are satisfied. Alternatively, when a connection failure event occurs, the UE records CEF information of the connection failure in the CEF variable whenever a condition of one of all the restriction methods configured is satisfied.

Example 2

The embodiment provides a CEF report logging method implemented on UE.

Hereinafter, embodiment 2 of the present invention will be described with reference to 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, in case a connection failure event occurs, the UE determines whether the cell identity of the current failed cell is equivalent to one or more failed cell identities stored in the connection establishment failure CEF report. In step S203, when it is determined that the cell identity is not identical to the one or more failed cell identities stored in the CEF report, the UE directly records information of a connection failure event in the CEF report.

Specifically, when a connection failure event occurs on the UE (such as a failure in the RRC connection establishment procedure or a failure in the RRC connection recovery procedure), the UE determines whether the cell identity of the current failed cell is equal to the failed cell identity (such as identified by a measresultfaildecell information element) in one or more CEF items stored in the CEF variable, and if not, the UE records 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, if no outdated information is recorded in the CEF variable before the current failed cell, the failed event is actually the first failed event experienced by the UE in the cell, and the UE does not need to perform the limiting method for recording CEF information (such as the limiting method described in embodiment 1) to determine whether to record the information, and directly records the failed information corresponding to the failed event of the cell in the CEF variable.

Example 3

The embodiment provides a method for reporting CEF report. By the method described in this embodiment, it may be determined, for a UE supporting the multiple CEF reports of release 17, 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 ueinfo request message from the network side, which includes request indication information for requesting the UE to report the saved CEF report.

Step 2: the UE judges whether to report a plurality of 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 CEF information corresponding to a last connection failure event in a ueinfomation response message, and reports the CEF information to the network side; if the indication information indicates that the UE reports multiple CEF reports (such as connEstFailReportReq-R17 information element), the UE includes all the multiple CEF information stored in the CEF variable in the UEInformationResponse message, and reports the multiple CEF information to the network side.

Example 4

This embodiment presents a method of recording time-based CEF reports by which the UE sets the time value according to the speed information for determining whether to record corresponding failure information in the CEF variable for a CEF failure event.

As mentioned above, when a connection failure event occurs in a cell CellA (e.g., denoted as CEF 3), if a CEF report item (e.g., denoted as CEF 1) of the same failed cell identified as CellA exists in a CEF variable of the UE, the UE determines whether a time between the occurrence of CEF3 and CEF1 is less than a time threshold, and if not, the UE adds a new CEF report item to the CEF variable to record CEF information of the CEF 3; if yes, the UE does not record CEF 3. Optionally, if there are multiple CEF report entries (e.g. CEF1 and CEF 2) of the same failed cell identifier of the CEF variable of the UE, the UE determines whether the time between the occurrence of the CEF event (e.g. CEF 2) and the occurrence of CEF3 of the latest CellA in the CEF variable is less than a time threshold, and if not, the UE adds a new CEF report entry in the CEF variable to record the CEF information of CEF 3.

In this embodiment, several different time thresholds are set taking into account the effects of different UE speeds. Preferably, a different time threshold is set for 3 stages, each stage corresponding to a different UE speed. For example, time threshold 1 corresponds to a high speed, time threshold 2 corresponds to a medium speed, time threshold 3 corresponds to a constant speed, etc. The UE applies a corresponding time threshold value for executing the above-described time-based CEF report recording method based on the determination of its own speed. In one implementation, the time threshold values corresponding to the several files are directly configured or predefined by the network side, such as explicitly configuring three threshold values TH, TH-high, TH-Medium. In another implementation manner, one of the threshold values and multiple scale factors are configured at the network side for the time threshold values corresponding to the several gears, for example, a constant speed threshold value TH, a scale factor-high corresponding to the high speed, and a scale factor-medium corresponding to the medium speed are configured. When the UE judges that the moving speed is in a high-speed state, a constant speed threshold value TH is used for obtaining a corresponding high-speed time threshold value by using a scale factor scalefactor-high; when the UE judges that the moving speed is in a medium speed state, a constant speed threshold value TH is used for obtaining a corresponding high speed time threshold value by using a scaling factor scalefactor-medium; when the UE judges that the moving speed is in a constant speed state, the constant speed threshold value TH is directly used.

The several different time thresholds may be configured to the UE by the network side through a system message or RRC dedicated signaling, or may be a predefined default value, or the UE may be acquired from the core network (e.g. acquired through non-access stratum (Non Access Stratum, NAS) signaling) as described above. In addition, the time may be implemented in various manners, for example, by a timer, where the time threshold may also be referred to as a maximum value/configuration value of the timer, and the name and the implementation of the time threshold are not limited in this disclosure. The determination of the UE mobility state may be based on the method of determining the UE mobility state 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 presents a method of managing timers in a time-based CEF report recording method.

In this embodiment, the time threshold value described in embodiment 4 is implemented by a CEF record correlation timer. When the UE generates a CEF event and determines that an item is added in a CEF variable to record CEF information corresponding to the CEF event, the UE starts the timer. In practice, the timer defines a minimum value of the difference between the times of occurrence of two CEF events (CEF report entries) in the CEF variable. Preferably, the two CEF events refer to CEF events of the same failed cell.

When the UE performs cell reselection, if the UE has a running CEF record related timer, the UE stops the timer. That is, only one CEF record related timer is maintained at the same time on the UE, and the UE stops running when the resident cell of the UE changes.

And when the RRC connection establishment process of the UE is successfully completed or the RRC connection recovery process is successfully completed, if the UE has a running CEF record related timer, stopping the timer by the UE. That is, the UE stops the timer running once the connection with the network side successfully enters the connected state. The successful completion of the RRC connection establishment procedure means that the UE successfully receives the RRC establishment message (at which time T300 is stopped), and the successful completion of the RRC connection recovery procedure means that the UE successfully receives the RRC recovery message (at which time T319 is stopped). Obviously, the method also comprises the steps that the UE initiates an RRC connection establishment or RRC connection recovery process, and an RRC establishment request message or an RRC recovery request message is sent to the network side.

The UE variables in the above embodiments are UE variables or CEF variables (e.g. VarConnEstFailReport or VarConnEstFailReportList) for recording CEF reports.

Example 6

Fig. 3 is a block diagram illustrating a user device 30 according to an embodiment of the present disclosure. As shown in fig. 3, the user equipment 30 comprises a processor 301 and a memory 302. The processor 301 may include, for example, a microprocessor, microcontroller, embedded processor, or the like. The memory 302 may include, for example, volatile memory (such as random access memory RAM), a Hard Disk Drive (HDD), non-volatile memory (such as flash memory), or other memory. The memory 302 has stored thereon program instructions. The instructions, when executed by the processor 301, may perform the random access reporting method described above in the user equipment described in detail in the present disclosure.

The program running on the apparatus according to the present disclosure may be a program for causing 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 a volatile store such as a random access memory RAM, a Hard Disk Drive (HDD), a nonvolatile store such as a flash memory, or other memory system.

A program for realizing the functions of the embodiments of the present disclosure may 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 term "computer system" as used herein may be a computer system embedded in the device and may include an operating system or hardware (e.g., 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 program is stored dynamically at a short time, or any other recording medium readable by a computer.

The various features or functional modules of the apparatus used in the embodiments described above may be implemented or performed by circuitry (e.g., single-chip or multi-chip integrated circuits). Circuits designed to perform the functions described herein may include a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The circuit may be a digital circuit or an analog circuit. Where new integrated circuit technologies are presented as an alternative to 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.

Further, 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 devices installed indoors or outdoors may be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office devices, vending machines, and other home appliances, etc.

As above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-described embodiments, and the present disclosure also includes any design modifications without departing 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 the technical means disclosed in the different embodiments are also included in the technical scope of the present disclosure. Further, the components having the same effects described in the above embodiments may be replaced with each other.

Claims

1. A connection establishment failure reporting method, comprising:

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

in case the connection failure event occurs, the UE determines whether to record information of the connection failure event in a connection establishment failure CEF report based on a downlink quality of a failed cell.

2. The connection establishment failure reporting method as claimed in claim 1, wherein,

when the cell identification of the current failed cell is equal to the cell identification of one or more failed cells in the CEF report and the UE judges that the difference between the downlink quality of the failed cell of the current connection failure and the downlink quality recorded by the same cell identification of one or more failed cells in the CEF report exceeds a threshold value, the UE records the information of the connection failure event in the CEF report.

3. The connection establishment failure reporting method as claimed in claim 2, wherein,

and when the UE judges that the difference between the downlink quality of the failed cell of the connection failure and the downlink quality recorded by the cell identification of the same one or more failed cells in the CEF report does not exceed a threshold value, the UE does not record the information of the connection failure event.

4. The connection establishment failure reporting method according to claim 1 or 2, wherein,

the UE adds an entry in the CEF variable of the CEF report, in which the information of the connection failure event is recorded.

5. 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 to interference plus noise ratio SINR, reference signal strength indication RSSI.

6. The connection establishment failure reporting method as claimed in claim 2, wherein,

the threshold value is configured to the UE by a base station through system information or a special Radio Resource Control (RRC) message, or is a preset default value or is acquired from a core network side.

7. 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 a measurement result of a failed cell, location information, a measurement result of a neighbor cell, a number of connection failures, random access information, and a time elapsed from the occurrence of a connection failure event to reporting.

8. The connection establishment failure reporting method as claimed in claim 1, wherein,

in case the connection failure event occurs, the UE further determines whether to record information of the connection failure event in a CEF report based on a downlink quality of a neighbor cell.

9. A connection establishment failure reporting method, comprising:

in the event of the connection failure event, the UE determines whether the cell identity of the current failed cell is equivalent to one or more failed cell identities stored in a connection establishment failure CEF report,

upon determining that the cell identity is not equivalent to the one or more failed cell identities stored in the CEF report, the UE records the information of the connection failure event directly in the CEF report.

10. A user equipment, UE, comprising:

a processor; and

a memory storing instructions;

wherein the instructions, when executed by the processor, perform the connection establishment failure reporting method according to any one of claims 1 to 9.