RU2797683C1 - Wireless network performance analysis - Google Patents

Abstract

FIELD: wireless communication.

SUBSTANCE: wireless communication method includes receiving, by the network node, the first message including information related to the radio link connection from the terminal and performing, by the network node, of analysis the network performance based on the information related to the radio link connection.

EFFECT: ensuring higher quality of communication services by analyzing the performance of the wireless network.

12 cl, 16 dwg

Description

The field of technology to which the invention belongs

[0001] This patent document is generally directed to wireless communication.

State of the art

[0002] Mobile communication technologies are moving the world towards an increasingly connected and networked society. The rapid development of mobile communications and advances in technology are leading to increased demand for bandwidth and connectivity. Other aspects such as power consumption, device costs, spectral efficiency and latency are also important to meet the needs of different communication scenarios. Various technologies are explained, including new methods for providing a higher quality of service.

The essence of the invention

[0003] This document discloses methods, systems, and devices associated with digital wireless communications, and more specifically, technologies associated with wireless network performance analysis.

[0004] In one exemplary aspect, a wireless communication method includes receiving, by a network node, a first message including information associated with a radio link connection from a terminal. The method may also include performing, by the network node, a network performance analysis based on information associated with the radio link connection.

[0005] In another exemplary aspect, wireless communication equipment comprising a processor is disclosed. The processor is configured to implement the method described herein.

[0006] In yet another exemplary aspect, the various technologies described herein may be implemented as a processor-executable code and stored on a computer-readable program medium.

[0007] Some embodiments may preferably implement the following solutions written in a format based on parts of the claims.

[0008] 1. A method for wireless communication, comprising:

[0009] - receiving, by a network node, a first message including information related to a radio link connection from a terminal; And

[0010] - Performing, by a network node, network performance analysis based on information associated with a radio link connection.

[0011] 2. The method of claim 1, wherein the information associated with a radio link connection includes information associated with a conditional handover.

[0012] 3. The method of claim 2, wherein the conditional handover-related information includes one or more conditional handover cell candidate identifiers.

[0013] 4. The method of claim 2, wherein the information associated with the conditional handover includes a triggering condition forced by the conditional handover.

[0014] 5. The method of claim 2, wherein the conditional handover-related information includes a conditional handover execution target reference parameter from one or more conditional handover candidate cells.

[0015] 6. The method of claim 1, wherein the information associated with a radio link connection includes information associated with a secondary cell group (SCG).

[0016] 7. The method of claim 6, wherein the information associated with the SCG includes an indicator that the primary SCG cell of the secondary node (SN) for the SN addition is a conditional handover cell candidate.

[0017] 8. The method of claim 6, wherein the information associated with the SCG includes:

[0018] - An indication that the secondary node's target primary SCG cell for SN change is a conditional handoff candidate cell.

[0019] 9. The method of claim 1, wherein the information associated with a radio link connection includes information associated with a master cell group (MCG).

[0020] 10. The method of claim 9, wherein the MCG-related information includes an indicator of whether the target primary cell for the host handoff is or is not a cell candidate.

[0021] 11. The method of claim 1, wherein the information associated with a radio link connection includes information associated with a connection failure.

[0022] 12. The method of claim 11, wherein the connection failure information includes an indicator of whether or not the target cell for handover is a candidate cell for conditional handover.

[0023] 13. The method of claim 11, wherein the connection failure information includes an indicator of whether or not the host handoff target primary cell is a conditional handoff cell candidate.

[0024] 14. The method of claim 11, wherein the connection failure information includes an indicator of whether the secondary node's target PSCell for SN change is or is not a conditional handoff cell candidate.

[0025] 15. The method of claim 11, wherein the connection failure information includes a connection failure type, and the connection failure type value indicates a master cell group recovery failure.

[0026] 16. The method of claim 11, wherein the connection failure information includes a radio link failure reason, and the radio link failure cause value indicates a master cell group recovery failure.

[0027] 17. The method of claim 11, wherein the connection failure information includes an indicator of whether or not a master cell group recovery failure occurs.

[0028] 18. The method of claim 11, wherein the connection failure information includes a reason for the failure to restore the leader cell group.

[0029] 19. The method of claim 11, wherein the connection failure information includes the duration of a master cell group recovery timer.

[0030] 20. The method of claim 11, wherein the connection failure information includes an indicator of whether or not the target handover cell during the master cell group recovery process is a candidate cell for conditional handover.

[0031] 21. The method of claim 11, wherein the connection failure information includes a decision reported by a leading cell group (MCG) failure information.

[0032] 22. The method of claim 11, wherein the connection failure information includes a service radio bearer (SRB) signaled by the MCG failure information.

[0033] 23. The method of claim 11, wherein the connection failure information includes an indicator of whether or not the reestablishment cell is a conditional handoff cell candidate.

[0034] 24. The method of claim 1, wherein the information associated with a radio link connection includes information associated with a random access channel (RACH) procedure including one or more RACH attempts.

[0035] 25. The method of claim 24, wherein the information associated with the RACH procedure includes the number of failovers between the two-stage RACH attempt and the four-stage RACH attempt per RACH procedure.

[0036] 26. The method of claim 24, wherein the information associated with the RACH procedure includes the number of failovers between the two-stage RACH attempt and the four-stage RACH attempt, per beam.

[0037] 27. The method of claim 24, wherein the information associated with the RACH procedure includes an indicator of whether or not the maximum transmit power is used to transmit working PUSCH data for the two-stage RACH attempt per RACH procedure. .

[0038] 28. The method of claim 24, wherein the information associated with the RACH procedure includes an indication of whether or not the maximum transmit power is being used to transmit PUSCH service data for the two-stage RACH attempt per beam.

[0039] 29. The method of claim 24, wherein the information associated with the RACH procedure includes a maximum power level for transmitting working PUSCH data for a two-stage RACH attempt per RACH procedure.

[0040] 30. The method of claim 24, wherein the information associated with the RACH procedure includes a maximum power level used to transmit PUSCH payload data for a two-stage RACH attempt per beam.

[0041] 31. The method of claim 24, wherein the information associated with the RACH procedure includes the number of preamble transmit power ramps per beam.

[0042] 32. The method of claim 1, wherein the first message is a secondary cell group failure information message that includes information associated with the secondary cell group and/or information associated with conditional handover.

[0043] 33. The method of claim 1, wherein the first message is a leading cell group failure information message that includes information related to the leading cell group and/or information related to conditional handover.

[0044] 34. The method of claim 1, wherein the first message is a user equipment (UE) information response message that includes at least one of connection failure related information, information related to conditional handover, information related to the RACH procedure.

[0045] 35. The method of claim. 1, further comprising: in response to receiving the first message, redirecting, through the network node, the second message to the secondary node, including information associated with a group of secondary cells, and/or information associated with conditional handover, wherein the network node includes a master node.

[0046] 36. The method of claim 1, further comprising: in response to receiving the first message, redirecting, by the network node, a second message including at least one of information related to a connection failure, information related to with conditional handover, and information related to the RACH procedure, to another network node serving the source cell associated with the handover.

[0047] 37. The method of claim 1, further comprising: in response to receiving the first message, redirecting, by the network node, a second message including at least one of information related to a connection failure, information related to with conditional handover, and information related to the RACH procedure, to another network node serving the cell in which the connection fails.

[0048] 38. The method of claim 37, wherein the network node serving the cell in which the connection fails forwards received information including at least one of information related to connection failure, information related to conditional handover, and information related to the RACH procedure, to another network node serving the source cell associated with the handover.

[0049] 39. The method of claim 1, wherein the network node includes a secondary node, wherein the secondary node performs network performance analysis.

[0050] 40. The method of claim 1, wherein the network performance analysis is performed by the network node serving the source cell associated with the handover.

[0051] 41. Wireless communications equipment, comprising a processor that is configured to perform the method of any one of methods 1-40.

[0052] 42. A non-volatile computer-readable medium storing code, wherein the code, when executed by the processor, instructs the processor to implement the method of any one of methods 1-40.

[0053] Details of one or more implementations are set forth in the attached attachments, in the drawings, and in the description below. Other features should become apparent from the description and drawings and from the sections of the claims.

Brief description of the drawings

[0054] FIG. 1 illustrates a block diagram of an exemplary 5G network architecture.

[0055] FIG. 2 illustrates a block diagram for a schematic view of the dual connection (DC) mode.

[0056] FIG. 3 illustrates the signaling process for generating messages with measurement results.

[0057] FIG. 4 illustrates a signaling process for performing network analysis according to the first exemplary embodiment.

[0058] FIG. 5 illustrates a signaling process for performing network analysis according to the second exemplary embodiment.

[0059] FIG. 6 illustrates a signaling process for performing network analysis according to the third exemplary embodiment.

[0060] FIG. 7 illustrates a signaling process for performing network analysis according to the fourth exemplary embodiment.

[0061] FIG. 8 illustrates a signaling process for performing network analysis according to the fifth exemplary embodiment.

[0062] FIG. 9 illustrates a signaling process for performing network analysis according to the sixth exemplary embodiment.

[0063] FIG. 10 illustrates a signaling process for performing network analysis according to the seventh exemplary embodiment.

[0064] FIG. 11 illustrates a signaling process for performing network analysis according to an eighth exemplary embodiment.

[0065] FIG. 12 illustrates a signaling process for performing network analysis according to the ninth exemplary embodiment.

[0066] FIG. 13 illustrates a signaling process for performing network analysis according to the tenth exemplary embodiment.

[0067] FIG. 14 illustrates a flow diagram of a method for analyzing network performance.

[0068] FIG. 15 shows an example of a wireless communication system that may employ technologies in accordance with one or more embodiments of the present technology.

[0069] FIG. 16 is a block diagram representation of a part of the hardware platform.

Detailed description of the invention

[0070] Section headings are used herein for ease of understanding only and do not limit the scope of the embodiments to the section in which they are described. In addition, although the embodiments are described with reference to 5G examples, the disclosed technologies can be applied to wireless systems that use protocols other than 5G or 3GPP protocols.

[0071] The development of a new generation of wireless communication - communication based on the new 5G radio standard (NR) - is part of the ongoing development of a broadband communication standard for mobile devices that meets the requirements of increasing network demand. NR must provide more bandwidth to enable more users to connect at the same time. Other aspects such as power consumption, device costs, spectral efficiency and latency are also important to meet the needs of different communication scenarios.

General view

[0072] FIG. 1 illustrates a block diagram 100 of an exemplary 5G network architecture. As shown in FIG. 1, a fifth generation (5G) network architecture may include a 5G core network (5GC) and a next generation radio access network (NG-RAN).

[0073] The 5GC may include any Access Mobility Function (AMF), Session Management Function (SMF), and User Plane Function (UPF). The NG-RAN may include base stations with various radio access technologies (RATs), such as 4G evolved base station (ng-eNB) and 5G base station (gNB). The NG-RAN base station can connect to the 5GC via the NG interface, and the NG-RAN base stations can connect via the Xn interface.

[0074] FIG. 2 illustrates a block diagram 200 for a schematic view of a dual connected (DC) mode. As shown in FIG. 2, various networks (such as 4G and 5G systems) may support Dual Connectivity (DC) functionality. A DC-enabled UE may remain connected to two base stations simultaneously, with the first base station being a master node (MN) and the second base station being a secondary node (SN). The participation of a DC-enabled cell located in the MN may include a master cell group (MCG) including a primary cell (PCell), and a secondary station may include a secondary cell group (SCG) including a primary SCG. cell (PSCell). The base station and the terminal (UE) may be connected via the Uu air interface.

[0075] FIG. 3 illustrates a signaling process 300 for generating measurement results messages. The UE may provide measurement message generation information to a base station (eg, RAN node).

[0076] As shown in FIG. 3, UE 302 may send an uplink RRC message 306 to RAN node 304. The uplink RRC message may include an availability indicator. RAN node 304 may send a UE information request 308 to UE 302. UE 302 may send a UE information response 310 to RAN node 304 in response to receiving the UE information request.

System overview

[0077] The present embodiments relate to wireless network performance analysis. The network node may receive information associated with at least one message reported by the UE. The message may include at least one of conditional handover (CHO) related information, SCG related information, MCG related information, connection failure related information, RACH procedure related information. The CHO related information may include at least one of one or more CHO cell candidate identifiers, the number of CHO cell candidates, the CHO execution trigger condition, the CHO target selection reference condition.

[0078] The triggering CHO execution condition may include at least one of identification data of a reference signal, a reference signal type (RS-type) (e.g., a block of synchronization signals/physical broadcast channels (SSB), a reference signal of state information channel (CSI-RS)), measurement value (eg received reference signal power (RSRP), received reference signal quality (RSRQ), signal-to-interference-and-noise ratio (SINR)), threshold value.

[0079] The CHO target selection reference condition (i.e., the reference condition that the UE considers when the UE selects a CHO execution target from multiple CHO cell options) may include at least one of a reference beam identifier , reference beam type (e.g. SSB, CSI-RS), reference beam measurement values (e.g. RSRP values, RSRQ values, SINR values), comparison rules (e.g. compare best beam only, compare multiple beams above threshold , threshold value, number of rays above the threshold value).

[0080] The SCG related information may include at least one of a PSCell ID in the case of an SN add process, an indication of whether or not the PSCell is a CHO cell candidate in the case of an SN add process, a target PSCell ID for the SN change and an indicator of whether the target PSCell is or is not a CHO candidate cell in the case of the SN change process.

[0081] The MCG related information may include at least one of an MCG failure cause (such as an MN handoff failure, RLF), an identity of the MN handover target PCell, and an indication of whether the handover target PCell represents MN itself or not is a possible CHO cell.

[0082] The connection failure related information may include at least one of the identity of the handover target cell, an indication of whether or not the handover target cell is a CHO cell candidate, the cause of the MCG failure (such as MN handover failure, RLF), MN handover target PCell identity, indicator of whether the MN handoff target PCell is a CHO cell candidate or not, target PSCell ID for SN change, indicator of whether the target PSCell SN is - changes by itself or not the CHO cell possibility, type of connection failures (such as MCG recovery failure), RLF cause (eg MCG recovery failure), an indicator of whether or not an MCG recovery failure occurs, MCG failure reasons; recovery (e.g., the handover initiated by the MN during the MCG recovery process fails, the MCG recovery timer expires), the length of the MCG recovery timer, the identity of the handover target cell during the MCG recovery process, the indication of whether handover target cell during MCG recovery process itself or not CHO cell opportunity reported by decision failure MCG information reported by path failure MCG information reported by SRB MCG failure information, cell identity to re-establish, an indicator of whether or not the cell is a candidate CHO cell for re-establishment.

[0083] The solution reported by the MCG failure information may include using a single message or using duplicate messages (eg, sending two identical messages).

[0084] The path reported by the MCG failure information may include generating messages in the MN only via the MCG SCell, generating messages in the MN only via the SN, or generating messages in the MN via both the MCG Scell and via the SN.

[0085] The SRB reported by the MCG failure information may include only via SRB1, only via SRB3, via SRB1 and SRB3 (may indicate that one message is sent on SRB1 and another identical message is sent on SRB3), via MCG only -branch of broken SRB1, via SCG branch of broken SRB1 only, via MCG branch of broken SRB1 and SRB3 (may indicate that one message is sent on MCG branch of broken SRB1 and another identical message is sent on SRB3), via SCG branch split SRB1 and SRB3 (may indicate that one message is sent on the SCG leg of the split SRB1 and another identical message is sent on SRB3), through the MCG leg of the split SRB1 and the SCG leg of the split SRB1 (may indicate that one message is sent over the MCG leg of the broken SRB1 and another identical message is sent over the SCG leg of the broken SRB1), or over the MCG leg of the broken SRB1 and the SCG leg of the broken SRB1 and SRB3 (may indicate that one message is sent over the MCG leg of the broken SRB1 , another identical message is sent on the SCG leg of the broken SRB1, and another identical message is sent on SRB3).

[0086] The RACH procedure related information may include at least one of the number of failovers between the two-stage RACH and the four-stage RACH per RACH procedure, the number of failovers between the two-stage RACH and the four-stage RACH per path, an indicator that indicates a failover between a two-way RACH and a four-way RACH per RACH procedure (which may be set to true if the two-way RACH at least fails over to the four-way RACH as soon as during the RACH -procedure), an indicator that indicates failover between a two-stage RACH and a four-stage RACH per beam (which may be set to true if the two-stage RACH at least fails over to the four-stage RACH once associated with the beam during the RACH procedure), the number of PUSCH transmission periods (PO) selected per beam, the PO index selected per beam (listed in chronological order of attempts), an indicator that indicates whether or not the maximum power is being used transmission for transmitting 2-stage RACH PUSCH traffic data per RACH procedure, an indicator that indicates whether or not the maximum transmit power for transmitting 2-stage RACH PUSCH traffic data per PO is used, and an indicator that indicates whether or not there is no maximum transmit power for transmitting 2-stage RACH PUSCH traffic data per beam (for example, if the maximum transmit power is used to transmit 2-stage RACH PUSCH traffic data in at least one PO mapped to that beam, the maximum transmit power used for this beam), the maximum power level used for transmitting 2-stage RACH PUSCH traffic data per RACH procedure, the maximum power level used for transmitting 2-stage RACH PUSCH traffic data per PO, the maximum power level used for 2-stage RACH PUSCH traffic per beam (in case multiple POs are mapped to one beam, this can be a list of the maximum power level in each PO or the maximum power level for all POs), the number of power ramps in each PO for transmitting PUSCH payload data of the two-stage RACH, the number of preamble transmit power ramps per beam, and the maximum preamble transmit power per beam.

[0087] The RACH procedure related information may include 2-way RACH related information and/or 4-way RACH related information.

[0088] The two-stage RACH related information may include at least one of the number of failovers between the two-stage RACH and the four-stage RACH per RACH procedure, the number of failovers between the two-stage RACH and the four-stage RACH per beam , an indicator that indicates failover between the two-way RACH and the four-way RACH per RACH procedure (which may be set to true if the two-way RACH at least fails over to the four-way RACH as soon as during the RACH- procedure), an indicator that indicates failover between the two-stage RACH and the four-stage RACH per beam (which may be set to true if the two-stage RACH at least fails over to the four-stage RACH once associated with the beam during RACH procedure time), number of PUSCH transmission periods (PO) selected per beam, PO index selected per beam (listed in chronological order of attempts), an indicator that indicates whether or not the maximum transmit power is being used for transmitting 2-stage RACH PUSCH traffic data per RACH procedure, an indicator that indicates whether or not the maximum transmission power for transmitting 2-stage RACH PUSCH traffic data per PO is used, and an indicator that indicates whether or not maximum transmit power for transmitting 2-stage RACH PUSCH traffic data per beam (e.g., if maximum transmit power is used to transmit 2-stage RACH PUSCH traffic data in at least one PO mapped to that beam, with the maximum transmit power being used for this beam), the maximum power level used to transmit 2-stage RACH PUSCH traffic data per RACH procedure, the maximum power level used to transmit 2-stage RACH PUSCH traffic data per PO, the maximum power level used to transmit 2-stage RACH PUSCH data per beam (in case multiple POs are mapped to one beam, this can be a list of maximum power level in each PO or maximum power level for all POs), number of power ramps in each PO for 2-stage RACH PUSCH data transmission, number of preamble transmit power ramps per beam and maximum preamble transmit power per beam, number of failure recovery between 2-stage CFRA and 2-stage CBRA per RACH procedure, number of failure recovery between 2-stage CFRA and two-stage CBRA per beam, the number of preambles sent on each beam and the beam indices, the probe beam indices and the number of preambles sent on each probe beam, listed in chronological order of attempts, an indicator of detected contention per beam (whereby the indicator contention detected is set to "true" if at least one failed contention-based collision resolution is detected in this beam) associated with backoff information (e.g., the number of backoffs with a value greater than 0 used during RACH -attempts using a RACH resource configured for 2-stage RACH, or a list of fallback values used during a RACH attempt using a RACH resource configured for 2-stage RACH, or a maximum fallback value used during a RACH attempt using the RACH resource configured for 2-stage RACH), the number of preambles sent in each preamble group per RACH procedure, the number of preambles sent in each preamble group per beam, an indicator that indicates which preamble group is selected per RACH procedure (eg, group A, group B, or both), an indicator that indicates which preamble group is selected per beam (eg, group A, group B, or both), an indicator that indicates which beam type is selected per RACH procedure (eg, SSB, CSI-RS, or both), a list of beam types selected in chronological order per RACH procedure.

[0089] Four-round RACH related information may include at least one of preamble transmit power ramps per beam, maximum preamble transmit power per beam, number of failovers between CFRA and four-round CBRA per RACH. -procedure, number of failovers between CFRA and four-way CBRA per beam, number of preambles sent on each beam and beam indices, probed beam indices and number of preambles sent on each beam tried, listed in chronological order of attempts, indicator of detected contention per beam (whereby the contention detected indicator is set to true if at least one failed contention-based collision resolution is detected in that beam) associated with the backoff information (e.g., number of backoffs). a value greater than 0 used during a RACH attempt using a RACH resource configured for 4-way RACH, or a fallback list of fallback values used during a RACH attempt using a RACH resource configured for 4-way RACH, or a maximum backoff value with return used during a RACH attempt using a RACH resource configured for 4-hop RACH), number of preambles sent in each preamble group per RACH procedure, number of preambles sent in each preamble group per beam, indicator , which indicates which preamble group is selected per RACH procedure (eg, group A, group B, or both), an indicator which indicates which preamble group is selected per beam (eg, group A , group B, or both), an indicator that indicates which beam type is selected per RACH procedure (e.g., SSB, CSI-RS, or both), a list of beam types selected chronologically in the calculation to the RACH procedure.

[0090] The network node may perform wireless network performance analysis according to the received information. Wireless network performance analysis may include analyzing CHO configuration parameters, determining whether or not the MCG recovery timer configuration has a reasonable length, whether or not there is a problem that the uplink signal is not good, and determining whether whether or not the RACH configuration parameter is valid.

[0091] An SCG failure information message may be received that includes SCG related information and/or CHO related information.

[0092] An MCG failure information message may be received that includes MCG related information and/or CHO related information.

[0093] The base station may receive a UE information response message from the UE reporting connection failure related information and/or CHO related information and/or RACH procedure related information.

[0094] The base station (eg, MN) may forward the received SCG related information and/or CHO related information reported by the UE to the SN (eg, via an SCG failure indicator message).

[0095] Connection failure related information and/or CHO related information and/or RACH procedure related information reported by the UE received by the base station may be redirected to another base station to which the original handover cell belongs (e.g. , via a message with an RLF indicator).

[0096] Connection failure related information and/or CHO related information and/or RACH procedure related information reported by the UE received by the base station may be redirected to another base station serving the cell where the connection failure occurs (for example, via a message with an RLF indicator).

[0097] A base station serving a cell in which a connection failure occurs may forward the connection failure related information and/or CHO related information and/or RACH procedure related information to another base station that owns the original handover cell. (for example, through a message with a HO report).

[0098] Wireless network performance analysis may be performed at the SN.

[0099] The wireless network performance analysis may be performed in the base station to which the source handover cell belongs.

[00100] An analysis of the performance of a wireless network may be performed in a base station serving a cell in which a connection failure occurs.

[00101] Wireless network performance analysis may be performed in a base station that receives related information reported by the UE.

[00102] The network node, according to the received information reported by the UE, can perform wireless network performance analysis (e.g., analysis of CHO configuration parameters, MCG recovery timer configuration length, whether or not there is a problem that the uplink signal is not a good RACH configuration parameter).

Exemplary Embodiment 1

[00103] FIG. 4 illustrates a signaling process 400 for performing network analysis according to the first exemplary embodiment. As shown in FIG. 4, both RLF and CHO can fail.

[00104] At 410, UE 402 may experience a radio link failure (RLF) in cell 1 of base station 1 404.

[00105] At 412, UE 402 may send a UE handover initiation to second base station 406. UE may select cell 2 of base station 2 406 for cell selection. Cell 2 of base station 2 406 may be an exemplary CHO cell configured to initiate conditional handoff at UE 402. UE 402 may initiate handover to cell 2 of base station 2 406.

[00106] At 414, the UE may fail to handover base station 2 406 such that it enters an idle state. The UE may experience a handover failure and the UE may enter an RRC dormant state.

[00107] In step 416, the UE may successfully access the third base station 408. The UE may select cell 3 of base station 3 to select a cell, the UE may successfully access cell 3 of base station 3 and transition to an RRC connected state.

[00108] At 418, UE 402 may send an RLF information availability instruction to base station 3 408 via an uplink RRC message.

[00109] At 420, base station 3 408 may send a UEInformationRequest message to UE 402 that carries the rlf-ReportReq indicator.

[00110] At 422, the UE may send an RLF report to base station 3 408. The RLF report may include any of the cell identity to reestablish (in this case: cell 2 of base station 2 406), an indicator indicating then, whether or not the cell to reestablish is a CHO cell candidate (in this case: "Yes"), one or more CHO cell candidate identifiers, the number of CHO cell candidates triggering CHO execution conditions (e.g., reference signal identification data, type for RS reference signal type (SSB, CSI-RS), quantity to measure (RSRP, RSRQ, SINR), threshold value), CHO target selection reference condition (i.e., reference condition that considers UE, when the UE selects a CHO execution target from multiple possible CHO cells) (such as reference beam identifier, reference beam type (SSB, CSI-RS), reference beam measurement values (RSRP values, RSRQ values, SINR- values), comparison rules (comparison of only the best ray, comparison of multiple rays above threshold, threshold value, number of rays above threshold)).

[00111] At 424, base station 3 408 may send an RLF indicator to base station 1 404, which carries the RLF report content.

Exemplary Embodiment 2

[00112] FIG. 5 illustrates a signaling process 500 for performing network analysis according to the second exemplary embodiment. As shown in FIG. 5, both handover failure and CHO can fail.

[00113] At 512, a UE handover failure (HOF) occurs. During handover of UE 502 from cell 1 of base station 1 504 to cell 2 of base station 2 506, a HOF failure occurs. Cell 2 of base station 2 506 may be an example of a CHO cell, and handover of the UE from cell 1 of base station 1 to cell 2 of base station 2 may be a conditional handover.

[00114] In step 514, UE 502 may send a UE Handover Initiation message to base station 3 508. The UE may select cell 3 of base station 3 508 for cell selection, where cell 3 of base station 3 may be a candidate CHO cell, and the UE may initiate handover to cell 3 of base station 3.

[00115] At step 516, the handover of the UE fails, so that it enters an idle state. The UE may experience a handover failure and the UE may enter an RRC dormant state.

[00116] At 518, UE 502 may successfully access base station 4 510. The UE may select and successfully access cell 4 of base station 4, and the UE may transition to an RRC connected state.

[00117] At 520, the UE may send the rlf-InfoAvailable indicator to base station 4 510 via an uplink RRC message.

[00118] At 522, base station 4 510 may send a UEInformationRequest message to the UE that carries the rlf-ReportReq indicator.

[00119] In step 524, the UE to the base station 4 may send a UEInformationResponse message carrying an RLF report.

[00120] The RLF report may include at least one of the following: an indicator of whether the handover target cell (in this case: cell 2 of base station 2) is or is not a CHO cell candidate (in the present example : "Yes"), the identifier of the cell to be reestablished (in this example: cell 3 of the base station 3), an indicator of whether the cell to be reestablished is or not a CHO cell candidate (in this example: "Yes"), one or more CHO cell candidates, number of CHO cell candidates, CHO execution trigger condition, CHO target selection reference condition.

[00121] At step 526, the base station 4 may send an RLF indicator message to the base station 2 that carries the content of the RLF report.

[00122] At 528, base station 2 may send a message (eg, HO report) to base station 1 that carries the content of the RLF report.

Exemplary Embodiment 3

[00123] FIG. 6 illustrates a signaling process 600 for performing network analysis according to the third exemplary embodiment. As shown in FIG. 6, HOF, RLF and CHO may fail.

[00124] At 610, the UE handover may succeed, but RLF may occur immediately. A UE from cell 1 of base station 1 may have a successful handoff to cell 2 of base station 2, cell 2 of base station 2 being a possible CHO cell. The handover of a UE from cell 1 of base station 1 to cell 2 of base station 2 is a conditional handover. However, the UE may immediately go into radio link failure (RLF) (ie, RLF occurs within a predetermined time period after the handover).

[00125] In step 612, UE 602 sends a UE handover initiation to base station 606. The UE may perform cell selection, selects cell 3 of base station 2, and cell 3 of base station 2 is a candidate CHO cell, and the UE initiates the transmission cell 3 of base station 2.

[00126] At 614, the handover of the UE fails such that it enters the dormant state. The UE may experience a handover failure and the UE may enter an RRC dormant state.

[00127] In step 616, the UE may successfully access base station 3. The UE may perform cell selection and select cell 4 of base station 3, and the UE may successfully access cell 4 and transition to an RRC connected state.

[00128] At 618, the UE may send the rlf-InfoAvailable indicator to the base station 3 via an uplink RRC message.

[00129] At 620, the base station 3 may send a UEInformationRequest message to the UE that carries the rlf-ReportReq indicator.

[00130] In step 622, the UE sends a UEInformationResponse message to the base station 3 carrying an RLF report. The RLF report may include at least one of the following: an indicator of whether the handover target cell (in this case: cell 2 of base station 2) is or is not a CHO cell candidate (in the present example: "Yes "), the identifier of the cell to be reestablished (in this example: cell 3 of base station 2), an indicator of whether or not the cell to be reestablished is a CHO cell candidate (in this example: "Yes"), one or more candidate CHO cell options, number of possible CHO cell options, CHO execution trigger condition, CHO target selection reference condition.

[00131] At step 624, the base station 3 sends a message (eg, an RLF indicator) to the base station 2 that carries the content of the RLF report.

[00132] In step 626, base station 2 sends a message (eg, HO report) to base station 1 that carries the content of the RLF report.

Exemplary Embodiment 4

[00133] FIG. 7 illustrates a signaling process 700 for performing network analysis according to the fourth exemplary embodiment. As shown in FIG. 7, SN addition fails.

[00134] In step 708, SN add at UE, at the UE, an SCG failure occurs during the addition of the PSCell, or an SCG failure occurs immediately after the successful addition of the PSCell. The current serving cell of the UE is cell 1 of base station 1, cell 2 of base station 2 is a candidate CHO cell, the UE tries to add cell 2 of base station 2 as a PSCell for SN addition, the UE experiences an SCG failure during addition PSCell, or the UE successfully adds the PSCell, but at the UE immediately, at the base station 2 instead of an SCG failure (ie, an SCG failure occurs within a predetermined period of time after the PSCell is added).

[00135] In step 710, UE 702 sends SCG failure information to base station 1 704. The SCG failure information may include at least one of the following: an indicator that represents PSCell SN additions (in this case: base station cell 2 2) itself or not CHO cell candidate (in this example: "Yes"), one or more CHO cell IDs, number of CHO cell candidates, triggering CHO execution condition, selection reference condition CHO goals.

Exemplary Embodiment 5

[00136] FIG. 8 illustrates a signaling process 800 for performing network analysis according to a fifth exemplary embodiment. As shown in FIG. 8, SN change fails.

[00137] In step 810, SN change at UE, an SCG failure occurs at the UE during the SN change process, or immediately after the successful completion of the SN change at the UE, an SCG failure occurs. UE may be in DC state, cell 1 of base station 1 may be a PSCell, cell 2 of base station 2 may be a PSCell, cell 3 of base station 3 is a candidate CHO cell, the UE attempts to access cell 3 of the base station 3 as target PSCell for SN change. The UE experiences an SCG failure during the SN change, or the UE successfully completes the SN change, but the UE immediately in the base station 3 instead of the SCG failure, i.e. An SCG fault occurs after an SN change within a preset time.

[00138] At 812, UE 802 may send SCG failure information to base station 1 804. The SCG failure information may include at least one of the following: an indicator of whether the target PSCell for SN change (in in this case: cell 3 of the base station 3) whether or not the CHO cell (in this example: "Yes"), one or more CHO cell identifiers, the number of CHO cell candidates triggering the CHO execution condition, reference condition for choosing a CHO target.

[00139] At 814, base station 1 804 may send an SCG failure indicator to base station 2 806. When an SN change is triggered by the SN, base station 1 may send a message (eg, SCG failure indicator) carrying the SCG information content failure, to base station 2.

Exemplary Embodiment 6

[00140] FIG. 9 illustrates a signaling process 900 for performing network analysis according to the sixth exemplary embodiment. As shown in FIG. 9, MN handover with SN change may fail.

[00141] At 912, the UE may be in the DC state, cell 1 of base station 1 may be a PSCell, cell 2 of base station 2 is a PSCell, cell 3 of base station 3 and cell 4 of base station 4 may be options. CHO-cell. The UE may perform an MN handover with SN change, and cell 3 of base station 3 may be a PCell and cell 4 of base station 4 may be a PSCell. The UE may have an SCG failure during the SN change, or the UE may successfully complete the SN change, but the UE may immediately have an SCG failure in base station 4. The UE may have an MCG failure during the MN handover, or the UE may successfully complete the handover of the MN, but the UE immediately has an MCG failure that occurs in the base station 3, and the MCG failure may occur within a predetermined time after the handover of the MN.

[00142] At 914, UE 902 may send a re-establishment message to base station 4 910 to successfully access cell 5 of base station 4 910.

[00143] At 916, UE 902 may receive an RLF report request from base station 4 910.

[00144] In step 918, the UE may send an RLF report to base station 4 910. The RLF report may include at least one of the following: an indicator of whether the target PCell for the MN handover represents (in this case: cell 3 of base station 3) is or is not a CHO cell (in this example: "Yes"), an indicator of whether the target PSCell SN changes (in this example: cell 4 of base station 4) is or is not a CHO opportunity -cells (in this example: "Yes"), cell ID to re-establish (in this example: cell 5 of base station 4), an indicator of whether or not the cell to re-establish itself is a candidate CHO cell (in this example: "No"), one or more CHO cell identifiers, number of CHO cell candidates, triggering CHO execution condition, CHO target selection reference condition.

[00145] At 920, base station 4 may send a message (eg, an RLF indicator) to base station 1 that carries the content of the RLF report.

Exemplary Embodiment 7

[00146] FIG. 10 illustrates a signaling process 1000 for performing network analysis according to the seventh exemplary embodiment. As shown in FIG. 10, CHO and MCG recovery may fail.

[00147] At 1012, the UE may be in a DC state, cell 1 of base station 1 may be a PSCell, cell 2 of base station 2 may be a PSCell, cell 3 of base station 3 may be a CHO cell candidate, the UE for handover, the MN without SN change may consider cell 3 as the target PCell, and the UE may have a HOF during the handover of the MN.

[00148] At step 1014, UE 1002 may send a message with MCG failure information to base station 2 1006, with the message redirected to base station 1 1004. The MCG failure information may carry at least one of the following: failure (in this case: MN handover failure), MN handover target (in this example: base station cell ID 3 3), an indication of whether the handover target PCell MN is or is not a CHO cell candidate (in this example, example: "Yes"), one or more CHO cell candidate identifiers, number of CHO cell candidates, CHO execution trigger condition, CHO target selection reference condition.

[00149] At 1016, the UE may start the configured timer.

[00150] In step 1018, the UE may initiate a handover to cell 4 of base station 3 (a handover command sent by base station 1 through base station 2) but fails, the UE may stop the timer, and the UE's MCG failure may not recover.

[00151] In step 1020, the UE may initiate re-establishment to cell 5 of base station 3, but fails and the UE may enter an RRC dormant state.

[00152] In step 1022, the UE may perform cell selection, select cell 6 of base station 4, the UE accesses cell 6, and the UE transitions to an RRC connected state.

[00153] At 1024, the UE may report an RLF report to the base station 4. The RLF report contains at least one of the following: the type of connection failures (in this case: MCG restore failure), the reason for the MCG restore failure (in this case: during the MCG restore process, the execution of the MN-issued failure when handover), MCG failure reason (in this case: MN handover failure), identity of the target PCell for MN handover (in this case: cell 3 of base station 3), an indication of whether the Pcell of the MN handover target is or no CHO cell option (in this example: "Yes"), length of MCG recovery timer, handover target cell identity (in this example: cell 4 of base station 3) during MCG recovery process, MCGFailureInformation-reported solution (in this example: using a single message), MCGFailureInformation-reported path (in this example: message to MN via SN only), MCGFailureInformation-reported SRB (in this example: via SCG-branch of broken SRB1).

[00154] In some embodiments, the RLF report may include any of the reestablishment cell identity (in this example: cell 5 of base station 3), an indicator of whether or not the reestablishment cell is a CHO- cell (in this example: "None"), one or more CHO cell candidate IDs, number of CHO cell candidates, CHO execution trigger conditions, CHO target selection reference condition.

[00155] At 1026, base station 4 1010 may send an RLF indicator to base station 3 1008, which carries the RLF report content.

[00156] At 1028, base station 3 1008 may send a message (eg, HO report) to base station 1 that carries the content of the RLF report.

Exemplary Embodiment 8

[00157] FIG. 11 illustrates a signaling process 1100 for performing network analysis according to an eighth exemplary embodiment. As shown in FIG. 11, RLF and MCG recovery may fail.

[00158] At 1110, the UE may be in the DC state, cell 1 of base station 1 may be a PSCell, cell 2 of base station 2 may be a PSCell, and at the UE in cell 1 may be RLF instead. The UE may be in a DC state and the UE may have an MCG failure.

[00159] At 1112, UE 1102 may send an MCG failure information message to base station 1 1004 via base station 2 1006. The MCG failure information may include at least one of the following: MCG failure reason ( in this case: RLF), one or more CHO candidate cell identities, number of CHO cell candidates, CHO execution trigger condition, CHO target selection reference condition.

[00160] At 1114, the UE may start the configured timer.

[00161] In step 1116, the UE initiates a CHO for cell 3 and cell 4 of base station 3. The UE may trigger a CHO failure for two cells of base station 3.

[00162] At step 1118, when the timer expires, the UE MCG failure may not recover.

[00163] In step 1120, the UE may initiate re-establishment in cell 5 of base station 3 and succeed.

[00164] In step 1122, the UE may report an RLF report to the base station 3. The RLF report may include at least one of the following: connection failure type (in this case: MCG recovery failure), RLF- cause (in this case: MCG restore failure), indicator of whether or not an MCG restore failed (in this case: "Yes"), reason for MCG restore failure (in this case: MCG restore timer timed out) , the reason for the MCG failure (in this case: RLF), the length of the MCG recovery timer, the identity of the handover target cell during MCG recovery (in this case: cell 3 and cell 4 of base station 3), an indicator of whether the target represents the handover cell during MCG recovery itself or not CHO cell option (in this case: cell 3 and cell 4 are "Yes"), MCGFailureInformation-reported decision (in this case: using duplicate messages), MCGFailureInformation- reported SRB (in this case: via MCG leg of broken SRB1 and SRB3), cell ID to re-establish (in this example: cell 5 of base station 3), indicator of whether or not the cell to re-establish itself is a candidate CHO cell (in this example: "None"), one or more CHO cell identifiers, number of CHO cell candidates, triggering CHO execution condition, CHO target selection reference condition.

[00165] At 1124, base station 3 may send a message (eg, RLF indicator) to base station 1 that carries the content of the RLF report.

Exemplary Embodiment 9

[00166] FIG. 12 illustrates a signaling process 1200 for performing network analysis according to the ninth exemplary embodiment.

[00167] At 1206, base station 1 1202 may receive an RLF report reported by the UE.

[00168] In step 1208, when the RLF report contains the handover source cell, base station 1 forwards the RLF report (eg, by an RLF indicator message) to the base station serving the handover source cell (referred to as "base station 2" ).

Exemplary Embodiment 10

[00169] FIG. 13 illustrates a signaling process 1300 for performing network analysis according to the tenth exemplary embodiment.

[00170] In step 1308, the UE for cell 1 of base station 1 may initiate a random access channel (RACH) based procedure in which the UE may perform a two-stage RACH attempt on SSB1 and fail.

[00171] At 1310, the UE may have SSB1 failover, perform a four-way RACH attempt, and fail.

[00172] At 1312, the UE may have a two-stage RACH attempt on SSB2 and fail.

[00173] At 1314, the UE may have SSB2 failover, perform a four-way RACH attempt, and fail.

[00174] In step 1316, the UE may perform a four-way RACH attempt on SSB3 and fail, and the UE may experience RLF in cell 1.

[00175] In step 1318, the UE may select cell 2 of base station 2 for cell selection, the UE may initiate re-establishment and successfully access base station 2.

[00176] At 1320, the UE RLF report may include at least one of the following: number of failovers between two-stage RACH and four-stage RACH per RACH procedure (in this example: 3 times), number 2-stage RACH to 4-stage RACH failure recovery per beam (in this example: 1x SSB1, 1x SSB2, 1x SSB3), an indicator that indicates the failure recovery between 2-stage RACH and 4-stage RACH per beam RACH procedure (in this example: true), and an indicator that indicates failure recovery between two-stage RACH and four-stage RACH per beam (in this example: true on SSB1, true on SSB2, true on "over SSB3).

[00177] FIG. 14 illustrates a flow diagram of a method for analyzing network performance. The method may include receiving, by the network node, a first message including information associated with a radio link connection from the terminal (block 1402). The first message may be an SCG failure information message, an MCG failure information message, or a UE information response message, as described in the present embodiments.

[00178] The method may also include performing, by the network node, analyzing network performance based on the information included in the first message (block 1404).

[00179] In some embodiments, the first message includes information related to the conditional handover.

[00180] In some embodiments, conditional handover-related information includes one or more conditional handover candidate cell identifiers.

[00181] In some embodiments, the conditional handover-related information includes the number of candidate cells for the conditional handover.

[00182] In some embodiments, the conditional handoff information includes a CHO execution trigger.

[00183] In some embodiments, the conditional handoff information includes a CHO target selection reference condition (i.e., a reference condition that the UE considers when the UE selects a CHO execution target from multiple CHO-options). hundred).

[00184] In some embodiments, the first message includes information associated with a secondary cell group (SCG).

[00185] In some embodiments, the information associated with the SCG includes an indicator that the secondary node's primary SCG cell for SN-add is a conditional handoff cell candidate.

[00186] In some embodiments, the information associated with the SCG includes the identifier of the primary SCG cell of the secondary node.

[00187] In some embodiments, the information associated with the SCG includes an indicator that the secondary node's target primary SCG cell for the SN change is a conditional handoff candidate cell.

[00188] In some embodiments, the information associated with the SCG includes the ID of the target primary SCG cell of the secondary node.

[00189] In some embodiments, the first message includes information associated with a Master Cell Group (MCG).

[00190] In some embodiments, the MCG related information includes an indicator of whether the target primary cell for the host handover is or is not a cell candidate.

[00191] In some embodiments, the MCG related information includes the cause of the MCG failure.

[00192] In some embodiments, the MCG-related information includes a target primary cell identifier for the host handoff.

[00193] In some embodiments, the first message includes information related to a connection failure.

[00194] In some embodiments, the connection failure information includes a target cell identifier for handover.

[00195] In some embodiments, the information associated with the connection failure includes an indicator of the reason for the failure of the group of leading cells.

[00196] In some embodiments, the connection failure information includes a target primary cell identifier for the host handover.

[00197] In some embodiments, the connection failure information includes an indicator of whether or not the target cell for handover is a candidate cell for conditional handover.

[00198] In some embodiments, the connection failure information includes an indicator of whether the target primary cell for handover of the lead node is or not a cell candidate for conditional handover.

[00199] In some embodiments, the connection failure information includes a primary secondary cell group target cell (PSCell) identifier of the secondary node.

[00200] In some embodiments, the connection failure information includes an indicator of whether the secondary node's target PSCell for SN change is or is not a conditional handoff cell candidate.

[00201] In some embodiments, the connection failure information includes the type of connection failures, and the value of the connection failure type indicates a failure to restore the leader cell group.

[00202] In some embodiments, the connection failure information includes a radio link failure reason, and the radio link failure cause value indicates a master cell group recovery failure.

[00203] In some embodiments, the connection failure information includes an indicator of whether or not a master cell group recovery failure occurs.

[00204] In some embodiments, the connection failure information includes a reason for the failure to restore the leader cell group.

[00205] In some embodiments, the information associated with the connection failure includes the length of the master cell group recovery timer.

[00206] In some embodiments, the connection failure information includes the handover target cell identity during the master cell group recovery process.

[00207] In some embodiments, the connection failure information includes an indicator of whether the target handover cell during the master cell group recovery process is or is not a candidate cell for conditional handover.

[00208] In some embodiments, the connection failure information includes a decision reported by the Master Cell Group (MCG) failure information.

[00209] In some embodiments, the connection failure information includes a path reported by the MCG failure information.

[00210] In some embodiments, the information associated with a connection failure includes a cell identifier for re-establishment.

[00211] In some embodiments, connection failure information includes a service radio bearer (SRB) signaled by the MCG failure information.

[00212] In some embodiments, the connection failure information includes an indicator of whether or not the reestablishment cell is a conditional handoff cell candidate.

[00213] In some embodiments, the first message includes information associated with a random access channel (RACH) procedure including one or more RACH attempts.

[00214] In some embodiments, the information associated with the RACH procedure includes the number of failovers between a two-stage RACH attempt and a four-stage RACH attempt, per RACH procedure.

[00215] In some embodiments, where the information associated with the RACH procedure includes the number of failovers between a two-stage RACH attempt and a four-stage RACH attempt, per beam.

[00216] In some embodiments, the information associated with the RACH procedure includes an indicator indicating failure recovery between a two-stage RACH attempt and a four-stage RACH attempt per RACH procedure.

[00217] In some embodiments, the information associated with the RACH procedure includes an indicator indicating failure recovery between a two-stage RACH attempt and a four-stage RACH attempt per beam.

[00218] In some embodiments, the information associated with the RACH procedure includes the number of transmission periods on the Physical Uplink Shared Channel (PUSCH) (PO) selected per beam.

[00219] In some embodiments, the information associated with the RACH procedure includes a PO index selected per beam.

[00220] In some embodiments, the information associated with the RACH procedure includes an indicator of whether or not the maximum transmit power is being used to transmit PUSCH payload data for a two-stage RACH attempt per RACH procedure.

[00221] In some embodiments, the information associated with the RACH procedure includes an indication of whether or not the maximum transmit power is being used to transmit PUSCH traffic data for a two-stage RACH attempt per beam.

[00222] In some embodiments, the information associated with the RACH procedure includes a maximum power level for transmitting PUSCH payload data for a two-stage RACH attempt per RACH procedure.

[00223] In some embodiments, the information associated with the RACH procedure includes the maximum power level used to transmit PUSCH payload data for a two-stage RACH attempt per beam.

[00224] In some embodiments, the information associated with the RACH procedure includes an indicator of whether or not the maximum transmit power is being used to transmit PUSCH payload data for a two-stage RACH attempt per PO.

[00225] In some embodiments, the information associated with the RACH procedure includes the number of power ramps in each PO for transmitting two-stage RACH PUSCH traffic data.

[00226] In some embodiments, the information associated with the RACH procedure includes the number of preamble transmit power ramps per beam.

[00227] In some embodiments, the information associated with the RACH procedure includes a maximum power level for transmitting two-stage RACH attempt PUSCH payload data per PUSCH transmission period.

[00228] In some embodiments, the information associated with the RACH procedure includes the maximum preamble transmit power on each beam.

[00229] In some embodiments, the information associated with the RACH procedure includes information associated with the two-stage RACH and/or associated with the four-stage RACH information (in case two-stage RACH and four-stage RACH are supported simultaneously, two separated information elements ( IE) may be used to include 2-stage RACH associated information and 4-stage RACH-related information, wherein the 2-stage RACH-related IE includes RACH procedure-related information when a 2-stage RACH resource is used (if present), while 4-round RACH associated IE includes RACH procedure related information when a 4-hop RACH resource (if any) is used).

[00230] In some embodiments, the two-stage RACH-related information includes at least one of the number of failovers between the two-stage RACH and the four-stage RACH per RACH procedure, the number of failovers between the two-stage RACH and the four-stage RACH per path, an indicator that indicates failover between the two-stage RACH and the four-stage RACH per RACH procedure (which may be set to true if the two-stage RACH at least fails over to the four-stage RACH as soon as during the RACH procedure), an indicator that indicates failover between the two-stage RACH and the four-stage RACH per beam (which may be set to true if the two-stage RACH at least fails over to the four-stage RACH as soon as associated with the beam during the RACH procedure), the number of PUSCH transmission periods (PO) selected per beam, the PO index selected per beam (listed in chronological order of attempts), an indicator that indicates whether or not there is no maximum transmit power for transmitting 2-stage RACH PUSCH traffic data per RACH procedure, an indicator that indicates whether or not the maximum transmit power for transmitting 2-stage RACH PUSCH traffic data per PO is used, and an indicator that indicates whether whether or not the maximum transmit power is used to transmit the 2-stage RACH PUSCH traffic data per beam (eg, if the maximum transmit power is used to transmit the 2-stage RACH PUSCH traffic data in at least one PO mapped to that beam, where maximum transmit power used for this beam), maximum power level used to transmit 2-stage RACH PUSCH traffic data per RACH procedure, maximum power level used to transmit 2-stage RACH PUSCH traffic data per PO, maximum power level used to transmit PUSCH traffic data of the 2-stage RACH per beam (in case multiple POs are mapped to one beam, this can be a list of the maximum power level in each PO or the maximum power level for all POs), the number of power ramps in each PO for transmitting PUSCH traffic data of the 2-stage RACH, the number of preamble transmit power ramps per beam and the maximum preamble transmit power per beam, the number of failure recovery between 2-stage CFRA and 2-stage CBRA per RACH procedure, the number of recovery after failure between 2-stage CFRA and 2-stage CBRA per beam, number of preambles sent on each beam and beam indices, probed beam indices and number of preambles sent on each beam tried, listed in chronological order of attempts, contention detection indicator per beam (with the contention detected indicator set to "true" if at least one failed contention-based collision resolution is detected in this beam) associated with backoff information (e.g., number of backoffs with a value greater than 0, used during a RACH attempt using a RACH resource configured for 2-stage RACH, or a list of fallback values used during a RACH attempt using a RACH resource configured for 2-stage RACH, or a maximum fallback value used during RACH attempt time using the RACH resource configured for 2-stage RACH), the number of preambles sent in each preamble group per RACH procedure, the number of preambles sent in each preamble group per beam, an indicator that indicates whether which preamble group is selected per RACH procedure (eg, group A, group B, or both), an indicator that indicates which preamble group is selected per beam (eg, group A, group B, or both of them), an indicator that indicates which beam type is selected per RACH procedure (eg, SSB, CSI-RS, or both), a list of beam types selected in chronological order per RACH procedure.

[00231] In some embodiments, the information associated with the four-round RACH includes at least one of a number of per-beam preamble transmit power ramps, a per-beam maximum preamble transmit power, a number of failovers between a CFRA and a four-round CBRA per RACH procedure, number of failovers between CFRA and four-stage CBRA per beam, number of preambles sent on each beam and beam indices, probed beam indices and number of preambles sent on each beam tried, listed in chronological order attempts, a contention detected indicator per beam (with the contention detected indicator set to "true" if at least one failed contention-based collision resolution is detected in that beam) associated with backoff, returning information (e.g., a number backoff values greater than 0 used during a RACH attempt using a RACH resource configured for 4-way RACH, or a list of backoff values used during a RACH attempt using a RACH resource configured for 4-way RACH, or the maximum backoff value used during a RACH attempt using a RACH resource configured for 4-hop RACH), number of preambles sent in each preamble group per RACH procedure, number of preambles sent in each preamble group per RACH procedure, per beam, an indicator that indicates which preamble group is selected per RACH procedure (e.g., group A, group B, or both), an indicator that indicates which preamble group is selected per beam (to group A, group B, or both), an indicator that indicates which beam type is selected per RACH procedure (eg, SSB, CSI-RS, or both), a list of beam types to be selected in the chronological order per RACH procedure.

[00232] In some embodiments, the method includes receiving, by the network node, a secondary cell group failure information message from the terminal, the secondary cell group failure information message including information associated with the secondary cell group and/or information related to the conditional handover.

[00233] In some embodiments, the method includes receiving, by the network node, a message with information about the failure of the group of leading cells from the terminal, and the message with information about the failure of the group of leading cells includes information associated with the group of leading cells, and/or information related to the conditional handover.

[00234] In some embodiments, the first message is a user equipment (UE) information response message that includes connection failure related information, conditional handoff related information, and/or random access channel related information.

[00235] In some embodiments, the method includes, in response to receiving the first message, forwarding, by the network node, the second message to the secondary node, the second message including any of the secondary cell group information and/or conditional transmission information service, and the network node includes a master node.

[00236] In some embodiments, the method includes, in response to receiving the first message, forwarding, by the network node, a second message including any of connection failure related information, conditional handoff information, and channel related with an arbitrary information access, to another network node serving the source cell associated with the handover.

[00237] In some embodiments, the method includes, in response to receiving the first message, forwarding, by the network node, a second message including any of connection failure related information, conditional handoff information, and channel related with an arbitrary information access to another network node serving the cell where the connection fails.

[00238] In some embodiments, a network node serving a cell in which a connection failure occurs redirects received information including at least one of connection failure information, conditional handover information, and information associated with the RACH procedure to another network node serving the source cell associated with the handover.

[00239] In some embodiments, network performance analysis is performed by the network node serving the cell in which the connection fails.

[00240] In some embodiments, the network node includes a secondary node, wherein the secondary node performs network performance analysis.

[00241] In some embodiments, network performance analysis is performed by the network node serving the source cell associated with the handover.

Wireless communication system

[00242] FIG. 15 shows an example of a wireless communication system that may employ technologies in accordance with one or more embodiments of the present technology. Wireless communication system 1500 may include one or more base stations 1505a, 1505b (BS), one or more wireless devices 1510a, 1510b, 1510c, 1510d, and core network 1525. Base station 1505a, 1505b may provide wireless services to wireless devices 1510a, 1510b, 1510c and 1510d in one or more wireless sectors. In some implementations, base station 1505a, 1505b includes directional antennas to form two or more directional beams so as to provide wireless coverage in different sectors.

[00243] Core network 1525 may communicate with one or more base stations 1505a, 1505b. The core network 1525 provides connectivity to other wireless communication systems and wired communication systems. The core network may include one or more service subscriber databases to store information associated with subscribed wireless devices 1510a, 1510b, 1510c, and 1510d. The first base station 1505a may provide wireless services based on the first radio access technology, while the second base station 1505b may provide wireless services based on the second radio access technology. Base stations 1505a and 1505b may be co-located or may be separately installed in an area according to a deployment scenario. Wireless devices 1510a, 1510b, 1510c, and 1510d may support several different radio access technologies. In some embodiments, base stations 1505a, 1505b may be configured to implement some of the technologies described herein. Wireless devices 1510a-1510d may be configured to implement some of the technologies described herein.

[00244] In some implementations, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that can be used to connect to different wireless networks.

[00245] FIG. 16 is a block diagram representation of a part of the hardware platform. A communication node as described herein may include a hardware platform as described with respect to FIG. 16. Hardware platform 1605, such as a network device or base station or wireless device (or UE), may include processor electronics 1610, such as a microprocessor, that implements one or more of the technologies presented herein. The hardware platform 1605 may include transceiver electronics 1615 for sending and/or receiving wired or wireless signals over one or more communication interfaces, such as an antenna 1620 or a wired interface. The hardware platform 1605 may implement other communication interfaces with defined protocols for transmitting and receiving data. The hardware platform 1605 may include one or more storage devices (not shown explicitly) configured to store information such as data and/or instructions. In some implementations, processor electronics 1610 may include at least a portion of transceiver electronics 1615. In some embodiments, at least some of the disclosed technologies, modules or functions, and network nodes are implemented using the hardware platform 1605.

[00246] From the foregoing, it should be appreciated that specific embodiments of the present disclosed technology are described herein for purposes of illustration, but that various modifications may be made without departing from the scope of the invention. Therefore, the present disclosed technology is not limited except by the appended claims.

[00247] The disclosed and other embodiments, modules, and functional operations described herein may be implemented in a digital electronic circuit, or in computer software, firmware, or hardware, including the structures disclosed in this document, and their structural equivalents, or in combinations of one or more of the foregoing. The disclosed and other embodiments may be implemented as one or more computer program products, i. one or more modules of computer program instructions encoded on a computer-readable medium for forced activation by or control of the operation of data processing equipment. The computer-readable medium may be a computer-readable storage device, a computer-readable storage card, a memory device, an article implementing a computer-readable signal to be distributed, or a combination of one or more of these. The term "data processing equipment" encompasses all items of data processing equipment, devices and machines, including by way of example a programmable processor, a computer, or multiple processors or computers. Hardware may include, in addition to hardware, code that creates a forced activation environment for the computer program in question, such as code that makes up the processor firmware, protocol stack, database management system, operating system, or a combination of one or more of signified. A propagated signal is an artificially generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiving equipment.

[00248] A computer program (also known as a program, software, application, script, or code) may be written in any form of a programming language, including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program, or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that stores other programs or data (for example, one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in several coordinated files (for example, in files that store one or more modules, subroutines, or parts of code). The computer program may be deployed to run on a single computer or on multiple computers that are located on a single Web site or distributed across multiple Web sites and interconnected via a communications network.

[00249] The processes and logics described herein may be executed by one or more programmable processors executing one or more computer programs to perform functions by processing input and generating output. Processes and logical workflows can also be executed by (and hardware can also be implemented as) special purpose logic circuitry such as an FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit).

[00250] Processors suitable for forced activation of a computer program include, by way of example, general purpose and special purpose microprocessors and any one or more processors of any type of digital computer. In general, a processor receives instructions and data from read-only memory or random access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. In general, the computer must also include or be operably coupled with the ability to receive data or transmit data, or both receive and transmit data, to one or more mass storage devices for storing data, such as magnetic, magneto-optical disks, or optical disks. . However, a computer does not need to have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and storage devices including, by way of example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard drives or removable drives; magneto-optical disks; and CD-ROMs and DVD-ROMs. The processor and storage device may be augmented by, or incorporated into, special purpose logic.

[00251] Although this patent document contains many specific details, they should not be construed as limitations on the scope of any invention or claims, but instead as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments may also be implemented in combination in one embodiment. Conversely, various features that are described in the context of one embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination. In addition, although the features may be described above as working in certain combinations and even initially set as such in the claims, one or more features from the claimed combination may in some cases be excluded from the combination, and the claimed combination may be directed to a subcombination or variation of the subcombination. .

[00252] Likewise, although the operations are illustrated in the drawings in a particular order, this should not be understood as a requirement that such operations must be performed in the particular order shown, or in sequential order, or that all illustrated operations must be performed in order to achieve desired results. In addition, the separation of the various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

[00253] Only a few implementations and examples are described, and other implementations, improvements, and variations may be made based on what is described and illustrated in this patent document.

Claims (21)

1. A method for wireless communication, comprising the steps of: transmitting, by means of the network node, a request for user equipment information; receiving, by the network node, a first message including information related to a radio link connection from the terminal, the first message corresponding to a request for user equipment information; And performing, by the network node, network performance analysis based on the information associated with the radio link connection, and wherein the radio link connection related information includes at least one of: 1) first conditional handover related information, which includes one or more conditional handoff candidate cell identifiers or selection reference condition CHO targets, 2) second information associated with a random access channel (RACH) procedure including one or more RACH attempts, wherein the information associated with the RACH procedure includes at least one from an indicator of whether or not the maximum transmit power is used to transmit PUSCH traffic data for a two-stage RACH attempt from an indicator of whether or not the maximum transmit power is used to transmit PUSCH traffic data for a two-stage RACH attempt per beam, the maximum power level to transmit PUSCH traffic data for a 2-stage RACH attempt per RACH procedure, the maximum power level used to transmit PUSCH traffic data for a 2-stage RACH attempt per beam, or the number of preamble transmit power ramps per beam, or 3) third information that includes at least one of: an indicator for indicating the number of failovers between a two-stage RACH and a four-stage RACH per beam, an indicator for indicating which preamble group is selected per RACH procedure, an indicator to indicate which preamble group is selected per beam, a list of beam types to be selected in chronological order per RACH procedure, the number of preambles sent on each beam and beam indices, the beam indices to be tried and the number of preambles sent on each to the beam being tried, listed in chronological order of attempts, an indicator of detected contention per beam, or information related to backtracking. 2. The method of claim 1, wherein the first message is a user equipment (UE) information response message that also includes connection failure related information. 3. The method according to claim 1, further comprising the step of: in response to receiving the first message, redirecting, by means of the network node, a second message to the secondary node including conditional handoff related information, the network node including the master node. 4. The method according to claim 1, further comprising the step of: in response to receiving the first message, redirecting, by means of the network node, the second message including connection failure related information to another network node serving the source cell associated with the handover, or to another network node serving the cell in which a connection failure occurs. 5. A method for wireless communication, comprising the steps of: receiving, by means of the network node from the terminal, an information message corresponding to a failure event of the group of leading cells; And performing, by the network node, network performance analysis based on the information associated with the radio link connection; And wherein the information associated with the radio link connection includes at least one of a type of connection failures with a value indicating failure to restore the leader cell group, reasons for radio link failure with a value indicating failure to restore the leader cell group, an indicator of whether whether or not the MC group recovery fails, the reasons for the failure of the MC group recovery, the duration of the MC recovery timer, an indication of whether the target handover cell during the recovery process of the MC group is itself or not a candidate cell for conditional handover, signaled by the MCG information, a service bearer (SRB) failure. 6. The method of claim 5, wherein the information message is a leading cell group (MCG) failure information or a user equipment (UE) information response to a request from the network node. 7. The method of claim 5, wherein the information associated with the radio link connection includes information relating to a master cell group (MCG) that includes an indicator of whether the target primary cell for the handover of the master node is or not possible honeycomb option. 8. The method of claim 5, wherein the network node includes a master node or a secondary node. 9. The method of claim 5, wherein the radio link connection-related information includes conditional handover (CHO) related information that includes at least one or more conditional handover cell candidate identifiers. service or reference condition for selecting a CHO target. 10. The method of claim 1 or 5, wherein the information associated with the radio link connection includes information associated with a conditional handover (CHO) including a CHO execution trigger condition that includes at least at least one of the reference signal type, the value for measuring the reference signal, or the comparison rule. 11. The method of claim 10, wherein the reference signal type includes a reference beam type indicating whether it is a synchronization signal block (SSB) or a channel state information (CSI-RS) reference signal, and the value for measuring the reference signal includes Received reference signal power (RSRP), received reference signal quality (RSRQ), or signal-to-interference-and-noise ratio (SINR) value. 12. The method of claim 1 or 5, wherein the information associated with the radio link connection includes information associated with a connection failure, which includes at least one of an indicator of whether the target cell for handover is or not conditional handover cell option, an indicator of whether the target primary cell for the master node handover represents itself or not the conditional handoff cell option, an indicator of whether the secondary node's target PSCell for SN change represents itself or not the option cell for conditional handover, or an indicator of whether or not the cell for re-establishment is a candidate cell for conditional handover.

Images