Method and apparatus for fast MCG link recovery procedure and MRO mechanism for unbalanced UL and DL coverage scenarios

Abstract

[0003] Embodiments of the present application relate to a method and apparatus for a fast master cell group (MCG) link recovery procedure and a mobility robustness optimization (MRO) mechanism for unbalanced uplink (UL) and downlink (DL) coverage scenarios, such as under a 3rd Generation Partnership Project (3GPP) 5G New Radio (NR) system. According to one embodiment of the present application, the method may include receiving configuration information related to a fast master cell group (MCG) link recovery procedure for a user equipment (UE); performing a fast MCG link recovery procedure and starting a timer associated with the fast MCG link recovery in response to an occurrence of a radio link failure (RLF) on the MCG; storing information associated with the fast MCG link recovery procedure in response to successful completion of the fast MCG link recovery procedure or in response to failure to complete the fast MCG link recovery procedure; and reporting the stored information to a base station (BS) in response to the UE accessing the BS. In addition, the UE may report auxiliary information (e.g., transmit power) to the BS. The BS may use the auxiliary information to identify whether there is a problem in the uplink.

Description

[Technical field]

[0001] Embodiments of the present application generally relate to wireless communication technologies, and more particularly, to a method and apparatus for a mobility robustness optimization (MRO) mechanism for fast master cell group (MCG) link recovery procedures and unbalanced uplink (UL) and downlink (DL) coverage scenarios. [Background technology]

[0002] A base station (BS) may have several cells (or areas) to provide communication services. When a user equipment (UE) moves from a serving cell of a source BS to a target cell of a target BS, a handover procedure is performed.

[0003] When a Radio Link Failure (RLF) or Handover (HO) failure occurs for a UE, the UE may perform a Radio Resource Control (RRC) re-establishment procedure. The UE may access a cell through a successful RRC re-establishment procedure. The accessed network will request UE information including the UE's RLF report so that the network can optimize mobility issues based on the UE information from the UE. Therefore, the UE will send a failure report to the network.

[0004] The 3rd Generation Partnership Project (3GPP) 5G system or network adopts an MRO mechanism. However, details regarding the fast MCG link recovery procedure and the MRO mechanism for UL and DL coverage scenarios have not yet been considered in the 3GPP 5G technology. Summary of the Invention [Means for solving the problem]

[0005] Some embodiments of the present application provide a method for wireless communication. The method may be executed by a UE. The method includes receiving configuration information regarding a fast MCG link recovery procedure for the UE, performing a fast MCG link recovery procedure in response to an occurrence of an RLF on the MCG and starting a timer associated with the fast MCG link recovery, storing information associated with the fast MCG link recovery procedure in response to successful completion of the fast MCG link recovery procedure or in response to a failure to complete the fast MCG link recovery procedure, and reporting the stored information to the BS in response to an access by the UE to the BS.

[0006] Some embodiments of the present application also provide an apparatus for wireless communication, the apparatus including a non-transitory computer-readable medium storing computer-executable instructions, a receiving circuit, a transmitting circuit, and a processor coupled to the non-transitory computer-readable medium, the receiving circuit, and the transmitting circuit, the computer-executable instructions causing the processor to perform the above-mentioned method executed by the UE.

[0007] Some embodiments of the present application provide a further method for wireless communication. The method may be executed by a UE. The method includes entering an RRC connected state of the UE, storing uplink transmission parameters of the UE in response to an occurrence of a failure, reporting the stored uplink transmission parameters to the BS in response to an access by the UE to the BS, and performing an RRC re-establishment procedure to a target cell based on a cell selection procedure, where the failure is at least one of an RLF, an HO failure, a conditional handover (CHO) failure, and a dual active protocol stack (DAPS) failure.

[0008] Some embodiments of the present application also provide an apparatus for wireless communication, the apparatus including a non-transitory computer-readable medium storing computer-executable instructions, a receiving circuit, a transmitting circuit, and a processor coupled to the non-transitory computer-readable medium, the receiving circuit, and the transmitting circuit, the computer-executable instructions causing the processor to perform the above-mentioned further method executed by the UE.

[0009] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will become apparent from the description and drawings, and from the claims.

[0010] To describe how the advantages and features of the present application may be obtained, the application will be described by reference to specific embodiments thereof that are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and are therefore not to be considered limiting of its scope. [Brief description of the drawings]

[0011] [Figure 1] 1 is a schematic diagram of a wireless communication system according to some embodiments of the present application. [Diagram 2] 1 is an exemplary flow chart of a fault information procedure according to some embodiments of the present application. [Diagram 3] 11 is a further exemplary flow chart of a fault information procedure according to some embodiments of the present application. [Figure 4] FIG. 2 illustrates an example UE information procedure according to some embodiments of the present application. [Diagram 5] FIG. 1 illustrates an example fault indication procedure according to some embodiments of the present application. [Figure 6] 1 is a flowchart of a method for storing information associated with a fast MCG link recovery procedure according to some embodiments of the present application. [Figure 7]4 is a flowchart of a method for storing uplink transmission parameters of a UE according to some embodiments of the present application. [Figure 8] 1 is an exemplary block diagram of an apparatus according to some embodiments of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] The detailed description of the accompanying drawings is intended as an illustration of the preferred embodiment of the present application, and does not represent the only form in which the present application may be practiced. It is to be understood that the same or equivalent function may be accomplished by different embodiments that are within the spirit and scope of the present application.

[0013] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. For ease of understanding, the embodiments are provided under specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. With the development of network architectures and new service scenarios, it is contemplated that all the embodiments in the present application are also applicable to similar technical problems, and further, the terms described in the present application may be changed, which should not affect the principles of the present application.

[0014] Next Generation Radio Access Networks (NG-RANs) support multi-radio dual connectivity (MR-DC) operation. In MR-DC operation, a UE with multiple transceivers may be configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, where one node may provide NR access and another node may provide either Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node may act as a Master Node (MN) and the other node may act as a Secondary Node (SN). The MN and SN are connected via a network interface (e.g., the Xn interface defined in 3GPP standard documents) to connect at least the MN to the core network.

[0015] FIG. 1 shows a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0016] As shown in Figure 1, the wireless communication system 100 may be a dual connectivity system 100 including at least one UE 101, at least one MN 102, and at least one SN 103. In particular, the dual connectivity system 100 in Figure 1 includes, for purposes of illustration, one illustrated UE 101, one illustrated MN 102, and one illustrated SN 103. Although a particular number of UEs 101, MNs 102, and SNs 103 are shown in Figure 1, it is contemplated that any number of UEs 101, MNs 102, and SNs 103 may be included within the wireless communication system 100.

[0017] Referring to Fig. 1, the UE 101 may be connected to the MN 102 and the SN 103 via a network interface, for example, a Uu interface defined in a 3GPP standard document. The MN 102 and the SN 103 may be connected to each other via a network interface, for example, an Xn interface defined in a 3GPP standard document. The MN 102 may be connected to a core network via a network interface (not shown in Fig. 1). The UE 101 may be configured to utilize resources provided by the MN 102 and the SN 103 to perform data transmission.

[0018] The MN 102 may refer to a radio access node that provides a control plane connection to a core network. In one embodiment of the present application, in an E-UTRA-NR DC (EN-DC) scenario, the MN 102 may be an eNB. In another embodiment of the present application, in a next generation E-UTRA-NR DC (NGEN-DC) scenario, the MN 102 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or an NR-E-UTRA DC (NE-DC) scenario, the MN 102 may be a gNB.

[0019] The MN 102 may be associated with an MCG. The MCG may refer to a group of serving cells associated with the MN 102 and may include a primary cell (PCell) of the MCG and possibly one or more secondary cells (SCells). The PCell may provide a control plane connection to the UE 101.

[0020] The SN 103 may refer to a radio access node without a control plane connection to a core network but providing additional resources to the UE 101. In one embodiment of the present application, in an EN-DC scenario, the SN 103 may be an en-gNB. In another embodiment of the present application, in a NE-DC scenario, the SN 103 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or an NGEN-DC scenario, the SN 103 may be a gNB.

[0021] The SN 103 may be associated with a secondary cell group (SCG). The SCG may refer to a group of serving cells associated with the SN 103 and may include a primary secondary cell (PSCell) and possibly one or more secondary cells (SCells).

[0022] The PCell of the MCG and the PSCell of the SCG may also be referred to as a special cell (SpCell).

[0023] In some embodiments of the present application, the UE 101 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart television (e.g., a television connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle-mounted computer, a network device (e.g., a router, a switch, and a modem). In some other embodiments of the present application, the UE 101 may include a portable wireless communication device, a smartphone, a cellular phone, a flip phone, a device having a subscriber identity module, a personal computer, selective call receiving circuitry, or any other device capable of sending and receiving communication signals over a wireless network. In some other embodiments of the present application, the UE 101 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. Additionally, the UE 101 may be referred to as a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or may be described using other terms used in the art.

[0024] 2 shows an exemplary flow chart of a fault information procedure according to some embodiments of the present application. The fault information procedure may be referred to as a fault information reporting procedure. The embodiment of FIG. 2 includes the following embodiments of the SCG fault information procedure:

[0025] In detail, as shown in FIG. 2, in operation 201, UE 210 (e.g., UE 101 shown and illustrated in FIG. 1) and MN 220 (e.g., MN 102 shown and illustrated in FIG. 1) may communicate RRC reconfiguration information. In operation 202, UE 210 may initiate an SCG failure information procedure and transmit a message associated with the failure for the SCG to MN 220. The message associated with the failure for the SCG in operation 202 may be an SCGFailureInformation message defined in the 3GPP standard document. MN 220 may then process the SCGFailureInformation message and determine whether to keep the SN or SCG, change the SN or SCG, or release the SN or SCG. The SN may be SN 103 shown and illustrated in FIG. 1.

[0026] In the above-described embodiment of the SCG failure information procedure, the UE 210 may initiate an SCG failure information procedure to report a failure to the SCG when one of the following conditions is met, i.e., upon detection of a failure to the SCG: For example, a failure to the SCG may refer to an RLF occurring in a PSCell of the SCG upon reconfiguration with SCG synchronization failure, upon SCG configuration failure, upon an integrity check failure indication from lower layers of the SCG related to signaling radio bearer (SRB) 3.

[0027] 3 shows a further exemplary flow chart of a fault information procedure according to some embodiments of the present application. The embodiment of FIG. 3 includes the following embodiments of the MCG fault information procedure:

[0028] In the embodiment of FIG. 3 of the present application, when a failure to the MCG occurs, the UE 310 may initiate (or trigger) a fast MCG link recovery procedure, i.e., an MCG failure information procedure. In some embodiments of the MCG failure information procedure, as shown in FIG. 3, in operation 301, the UE 310 (e.g., the UE 101 shown and illustrated in FIG. 1) and the MN 330 (e.g., the MN 102 shown and illustrated in FIG. 1) may communicate RRC reconfiguration information via the SN 320 (e.g., the SN 103 shown and illustrated in FIG. 1). In operation 302, the UE 310 may initiate an MCG failure information procedure and transmit a message associated with the failure to the MCG to the MN 330 via the SN 320. For example, the failure to the MCG may refer to an RLF occurring in the PCell of the MCG. The message associated with the failure to the MCG in operation 302 may be an MCGFailureInformation message specified in a 3GPP standard document.

[0029] In an embodiment of the MCG failure information procedure, the UE 310 may not directly transmit a message associated with the failure for the MCG to the MN 330. Instead, the UE 310 may transmit a message associated with the failure for the MCG to the SN 320 (e.g., the SN 103 shown and illustrated in FIG. 1), which may then forward the message received from the UE 310 to the MN 330.

[0030] For example, the UE 310 may be configured with a split SRB1 or SRB3 to report MCG failure information when a failure to the MCG occurs. If a split SRB1 is configured, the UE 310 may submit an MCGFailureInformation message to lower layers, e.g., for transmission via SRB1. If an SRB3 is configured, the UE 310 may submit an MCGFailureInformation message to lower layers, e.g., for transmission via SRB3. For example, the MCGFailureInformation message may be embedded in the NR RRC message "ULInformationTransferMRDC" specified in the 3GPP standard documents for transmission via SRB3.

[0031] When or after transmitting the message in operation 302, the UE 310 may start a timer associated with the Fast MCG Link Recovery procedure. In one embodiment of the present application, the timer associated with the Fast MCG Link Recovery procedure may be timer T316 defined in the 3GPP standard document.

[0032] After receiving the message associated with the failure for the MCG, the MN 330 may further transmit a response message to the UE 310. The response message may be an RRC reconfiguration message including a handover (HO) command for the cell. The response message may be an RRC release message. In one embodiment of the present application, the handover command may be a reconfigurationWithSync configuration defined in the 3GPP standard document. The MN 330 may not transmit the response message directly to the UE 310. Instead, the MN 330 may transmit the response message to the SN 320 (e.g., the SN 103 shown and illustrated in FIG. 1), which may then forward the response message to the UE 310.

[0033] If SRB3 is configured to send a message associated with a failure to the MCG, after receiving a response message from MN330, SN320 may encapsulate the response message in a DLInformationTransferMRDC message defined in the 3GPP standard document and then send the DLInformationTransferMRDC message to UE310.

[0034] In 3GPP Release 16, a Fast MCG Link Recovery procedure is introduced for MR-DC scenarios. The Fast MCG Link Recovery procedure is sometimes called the MCG Failure Information procedure. The purpose of this procedure is to inform the MN of the RLF towards the MCG via the SN connected to the UE, so that the UE in RRC_CONNECTED state may initiate the Fast MCG Link Recovery procedure to quickly continue the RRC connection without performing a re-establishment procedure.

[0035] The following table provides an introduction to some of the timers defined in the 3GPP standard documents, including the start conditions, stop conditions, actions on expiration, and possible common names for each of these timers. [Table 1]

[0036] As specified in the 3GPP standard document TS 38.321, the Power Headroom (PH) reporting procedure is used to provide the serving BS with the following information: - Type 1 Power Headroom (PH) value: The difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission per activated serving cell. - Type 2 PH value: The difference between the nominal UE maximum transmit power and the estimated power for UL-SCH and PUCCH transmissions on the SpCell of other MAC entities (i.e. the E-UTRA MAC entity in case of EN-DC, NE-DC and NGEN-DC). - Type 3PH value: The difference between the nominal UE maximum transmit power and the estimated power for SRS transmission per activated serving cell.

[0037] The types of UE power headroom reports are: ·The Type 1 UE power headroom PH that is valid for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c. If the UE determines that the type 1 power headroom report for the activated serving cell is based on the actual PUSCH transmission, then for PUSCH transmission occasion i on active UL BWP b of carrier f of serving cell c, the UE calculates a type 1 power headroom report P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c at PUSCH transmission occasion i according to the formula defined in 3GPP standard document TS38.101. ·The Type 3 UE power headroom PH that is valid for SRS transmission occasion i on active UL BWP b of carrier f of serving cell c. If the UE determines that the type 3 power headroom report for an activated serving cell is based on an actual SRS transmission, for an SRS transmission occasion i on an active UL BWP b of carrier f of serving cell c, and if the UE is not configured for PUSCH transmission on carrier f of serving cell c and resources for the SRS transmission are provided by SRS-Resource, the UE calculates a type 3 power headroom report P CMAX,f,c (i) is the maximum output power configured by the UE for carrier f of serving cell c at SRS transmission occasion i according to the formula defined in 3GPP standard document TS38.101.

[0038] In general, a UE may be equipped with multiple antenna panels, each panel having a set of antenna ports for DL ​​reception and UL transmission. The number of panels equipped by the UE may be reported as part of the UE capabilities, and the BS may assign a unique identification (ID) for each UE panel. When two or more UE panels are activated, only one of them may be used for UL transmission at a time instance. Any one of the activated panels may be used for UL transmission, and different panels may have different PHRs since beam-specific or panel-specific power control is supported. Therefore, the panel ID associated with each PHR should be reported for per-panel PHR reporting in the handover procedure.

[0039] 4 illustrates an exemplary UE information procedure according to some embodiments of the present application. The embodiment of FIG. 4 illustrates a procedure in which a UE (e.g., UE 410) communicates with a MN (e.g., MN 420). In some examples, the UE 410 may function as the UE 101 in FIG. 1. The MN 420 may function as the MN 102 in FIG. 1.

[0040] As shown in FIG. 4, in operation 401, the MN 420 (e.g., the MN 102 illustrated and shown in FIG. 1) transmits a UEInformationRequest message to the UE 410 (e.g., the UE 101 illustrated and shown in FIG. 1). The MN 420 may be a source BS that controls a serving cell of the UE 410. In operation 402, the UE 410 transmits a UEInformationResponse message including an RLF report to the MN 420. The MN 420 can optimize the mobility issue based on the response transmitted from the UE 410.

[0041] In a 3GPP 5G NR system, etc., a failure indication may be initiated after a UE attempts to re-establish a radio link connection at a NG-RAN node B (e.g., BS 520 in FIG. 5) after a failure at a NG-RAN node A (e.g., BS 510 in FIG. 5). The NG-RAN node B (e.g., BS 520 in FIG. 5) may initiate a failure indication procedure toward multiple NG-RAN nodes if the multiple NG-RAN nodes control a cell that uses a physical cell identity (PCI) signaled by the UE during the RRC re-establishment procedure. The failure indication may also be sent to the node that last serves the UE when the NG-RAN node fetches an RLF report from the UE. An example of a failure indication procedure is described in FIG. 5.

[0042] The purpose of the failure indication procedure is to transfer information about the RRC re-establishment attempt or the received RLF report between NG-RAN nodes. The signaling is done from the NG-RAN node at which the re-establishment attempt is made or the RLF report is received to the NG-RAN node to which the concerned UE may have been previously attached prior to the connection failure. This may help to detect the RLF case or the HO failure case.

[0043] 5 illustrates an exemplary fault indication procedure according to some embodiments of the present application. The embodiment of FIG. 5 illustrates a procedure in which one BS (e.g., BS 510) communicates with another BS (e.g., BS 520).

[0044] In some embodiments, BS 510 in Figure 5 may function as a source BS, and BS 520 in Figure 5 may function as a target BS. If there is a need for handover, the UE may perform a handover procedure from the serving cell of BS 510 to the target cell of BS 520, which depends on the result of the cell selection procedure. The handover procedure performed by the UE may be a CHO procedure.

[0045] As shown in FIG. 5, in operation 501, BS 520 transmits a failure indication message to BS 510. BS 510 is a source BS that controls an original serving cell of a UE (e.g., UE 101 illustrated and shown in FIG. 1). BS 520 is a target BS or a new BS that controls a target cell or a CHO candidate cell of the UE. The failure indication message may be transmitted over an Xn interface or an X2 interface. For example, the failure indication message includes a container of an RLF report. The container of the RLF report may be transmitted over an Xn interface or an X2 interface.

[0046] Currently, according to the 3GPP Release 16 dual connectivity carrier aggregation (DCCA) agreement, if timer T316 is configured at RLF on MCG, a fast MCG link recovery procedure will be triggered. Then, the UE needs to send an MCGFailureInformation message to the MN via the SN. If timer T316 expires or RLF on SCG link occurs, the UE performs a re-establishment procedure. The legacy RLF-report cannot indicate whether a fast MCG link recovery procedure is performed or not. However, it is necessary to distinguish whether a fast MCG link recovery is performed or not. Moreover, according to the 3GPP Release 16 DCCA agreement, if timer T316 is configured at RLF on MCG, a fast MCG link recovery will be triggered. Then, the UE needs to send an MCGFailureInformation message to the MN via the SN. If timer T316 expires or RLF on SCG link occurs, the UE performs a re-establishment procedure. In addition, according to the 3GPP RAN2 agreement, the detected RLF may be caused by UL coverage problems, which may be classified as pure UL coverage problems, or mixed cases where the DL also disappears.

[0047] In view of the above, the following problems need to be solved in 3GPP 5G NR systems, etc., namely, (1) what information should be added in the MRO mechanism for fast MCG link recovery procedure to indicate whether the fast MCG link recovery procedure is performed and why a fast MCG link recovery failure occurs, and (2) how to identify which link of UL and DL causes RLF in unbalanced UL and DL coverage scenarios. The embodiments of the present application provide a fast MCG link recovery procedure and an MRO mechanism for unbalanced UL and DL coverage scenarios in 3GPP 5G NR systems, etc., to solve the above problems. Further details are provided in the following text in combination with the accompanying drawings.

[0048] 6 illustrates a flowchart of a method for storing information associated with a fast MCG link recovery procedure according to some embodiments of the present application. The method 600 may be performed by a UE (e.g., UE 101, UE 210, UE 310, or UE 410 shown and illustrated in any of FIGS. 1-4). Although described with respect to a UE, it should be understood that other devices may be configured to perform a method similar to that of FIG. 6.

[0049] In the example method 600 shown in FIG. 6, in operation 601, a UE (eg, the UE 101 shown and illustrated in FIG. 1) receives configuration information regarding a fast MCG link recovery procedure for the UE.

[0050] In operation 602, when a radio link failure (RLF) on the MCG occurs, the UE performs a fast MCG link recovery procedure and starts a timer associated with fast MCG link recovery, for example, the timer associated with fast MCG link recovery is timer T316 specified in the 3GPP standard document.

[0051] In operation 603, in response to successful completion of the Fast MCG link recovery procedure or in response to failure to complete the Fast MCG link recovery procedure, the UE stores information associated with the Fast MCG link recovery procedure, i.e., if the Fast MCG link recovery procedure is completed successfully or fails to complete the Fast MCG link recovery procedure, information associated with the Fast MCG link recovery procedure is stored.

[0052] In operation 604, when the UE accesses a BS (e.g., the MN 102 shown and illustrated in FIG. 1), the UE reports stored information associated with a fast MCG link recovery procedure to the BS. The BS may also be referred to as a serving BS.

[0053] According to some embodiments of the present application, if the Fast MCG Link Recovery procedure fails to complete, upon expiration of a timer (e.g., timer T316) associated with the Fast MCG Link Recovery or upon occurrence of an RLF on the SCG link, the UE performs an RRC re-establishment procedure and stores failure information for the SCG link. For example, the UE stores an RLF cause for the SCG link, i.e., an RLF cause for the SCG link.

[0054] In one embodiment, the RLF cause for an SCG link is: (1) expiration of a physical layer problem timer (e.g., expiration of timer T310); (2) expiration of a timer for initiating fault recovery based on triggering a measurement report (e.g., expiration of timer T312); (3) Random access problem, (4) Reaching the Radio Link Control (RLC) maximum retransmission number (e.g., rlc-MaxNumRetx as specified in the 3GPP standard documents); (5) SCG configuration failure, and (6) Integrity check failure indication from the SCG lower layer related to SRB3 It can be at least one of:

[0055] According to some other embodiments of the present application, if the fast MCG link recovery procedure fails to complete, the UE receives a UE information request message (e.g., a UE Information Request message) from the target BS and sends a UE information response message (e.g., a UE information response message) to the target BS. The UE information response message may include auxiliary information associated with the fast MCG link recovery procedure.

[0056] In one embodiment, the auxiliary information includes: An indication as to whether a timer associated with fast MCG link recovery (e.g. timer T316) is configured for the UE, or An indication as to whether Fast MCG Link Recovery is configured for the UE, or Fast MCG link recovery failure indication Includes.

[0057] In a further embodiment, the auxiliary information comprises: An indication of the expiration of a timer associated with fast MCG link recovery (for example, timer T316), or Includes an indication of RLF on the link of the SCG. For example, this indication may include an RLF cause for the link of the SCG. The RLF cause may be: (1) expiration of a physical layer problem timer (e.g., expiration of timer T310); (2) expiration of a timer for initiating fault recovery based on triggering a measurement report (e.g., expiration of timer T312); (3) Random access problem, (4) Reaching the Radio Link Control (RLC) maximum retransmission number (e.g., rlc-MaxNumRetx as specified in the 3GPP standard documents); (5) SCG configuration failure, and (6) Integrity check failure indication from the SCG lower layer related to SRB3 It can be at least one of:

[0058] In another embodiment, the auxiliary information includes a container, which includes an SCG fault information message, for example, the SCG fault information message may include a fault type of the SCG link and a measurement result based on the configuration information.

[0059] In an additional embodiment, if the UE successfully completes the Fast MCG Link Recovery procedure, the aiding information includes an indication of successful completion of the Fast MCG Link Recovery procedure.

[0060] The following text describes a particular embodiment 1 of the method depicted and illustrated in FIG. 6 for solving the above problem.

[0061] According to embodiment 1, a UE (e.g., the UE 101 illustrated and illustrated in FIG. 1) and a BS (e.g., the MN 102 illustrated and illustrated in FIG. 1) perform the following operations in an MRO mechanism for a fast MCG link recovery procedure. (1) Step 1: A UE accesses a network (e.g., a BS) via DC operation. (2) Step 2: The UE is configured with the fast MCG link recovery procedure. (3) Step 3: When an RLF of the MCG link occurs, the UE starts a timer T316 and sends an MCGfailureinformation message to the MN via the SN. (4) Step 4: When timer T316 expires or an RLF on the SCG link occurs, the UE selects one suitable cell and performs an RRC re-establishment procedure. When an RLF on an SCG link occurs, the UE stores the RLF cause for the SCG link. The RLF cause can be at least one of timer T310 expiry, timer T312 expiry, randomAccessProblem, rlc-MaxNumRetx, SCG configuration failure, and integrity check failure indication from the SCG lower layers related to SRB3. (5) Step 5: The UE sends an RRCReestablishmentRequest message to the selected target cell. After the UE successfully accesses the selected target cell, the UE sends an RRCReestablishmentComplete message to the target BS in the selected target cell. The RRCReestablishmentComplete message includes an indication to indicate that auxiliary information is available. (6) Step 6: After the target BS receives the instruction, the target BS sends a UE Information Request message to the UE. (7) Step 7: The UE sends a UE information response message to the target BS. · Case 1: The UE information response message includes at least one of the following: - Information to indicate whether timer T316 (associated with the fast MCG link recovery procedure) is configured or not. If the information indicates that timer T316 is configured, the network (e.g., BS) may infer that a fast MCG link recovery failure is performed by the UE. - One indication of a Fast MCG Link Recovery failure procedure if the failure occurs during execution of a Fast MCG Link Recovery procedure by the UE or the UE fails to complete a Fast MCG Link Recovery procedure. - One indication of successful Fast MCG Link Recovery procedure if the UE successfully completes the Fast MCG Link Recovery procedure. · Case 2: The UE information response message includes at least one of the following: - expiration of timer T316. - RLF for SCG links. When the RLF on the SCG link causes a fast MCG link recovery failure, the UE may generate an SCGfailureinformation message as a container in the RLF-report. - An RLF cause for an SCG link, which may be at least one of: timer T310 expiry, timer T312 expiry, randomAccessProblem, rlc-MaxNumRetx, SCG configuration failure, and an integrity check failure indication from the SCG lower layers related to SRB3. (8) Step 8: After the target BS receives the UE information response message from the UE, the target BS will send a failure indication message to the source BS using the Xn interface.

[0062] Details described in all other embodiments of the present application (e.g., details of how to implement the MRO mechanism for fast MCG link recovery procedure) are applicable to the embodiment of Figure 6. Moreover, details described in the embodiment of Figure 6 are applicable to all embodiments of Figures 1-5, 7, and 8.

[0063] 7 illustrates a flowchart of a method for storing uplink transmission parameters of a UE according to some embodiments of the present application. The method 700 illustrated in FIG. 7 may be performed by a UE (e.g., UE 101, UE 210, UE 310, or UE 410 shown and illustrated in any of FIGS. 1-4). Although described with respect to a UE, it should be understood that other devices may be configured to perform a method similar to that of FIG. 7.

[0064] In the example method 700 shown in Figure 7, a UE (e.g., UE 101 shown and illustrated in Figure 1) enters an RRC connected state in operation 701. The RRC connected state may also be referred to as an RRC connection state, an RRC CONNECTION state, an RRC_CONNECTION state, an RRC_CONNECTED state, an RRC_Connected state, etc.

[0065] In operation 702, the UE stores uplink transmission parameters of the UE when a failure occurs. The failure may be at least one of a radio link failure (RLF), a handover (HO) failure, a conditional handover (CHO) failure, and a dual active protocol stack (DAPS) failure.

[0066] In operation 703, when the UE accesses a BS (eg, the MN 102 shown and illustrated in FIG. 1), the UE reports the stored uplink transmission parameters to the BS.

[0067] In operation 704, the UE performs an RRC re-establishment procedure to the target cell based on the cell selection procedure.

[0068] According to some embodiments of the present application, the UE further receives a UE information request message from the target BS, and sends a UE information response message to the target BS. The UE information response message may include auxiliary information associated with the uplink transmission.

[0069] In one embodiment, the auxiliary information includes: (1) the transmit power value of the UE at the time instance when the failure occurs, or (2) The number of uplink retransmissions of a packet at the UE’s RLC layer. Includes.

[0070] In a further embodiment, when RLF occurs, the aiding information includes a power headroom (PH) value in a power headroom report (PHR). In one example, the PH value in the PHR is per beam of the UE. In another example, the PH value in the PHR is per panel of the UE.

[0071] For example, the pH value in PHR is: (1) A PH value for the UE's primary cell (Pcell) and a configured maximum transmit power value for the Pcell; (2) a PH value for the UE's primary secondary cell (PSCell) and a configured maximum transmit power value for the PSCell; and (3) A PH value for a secondary cell (SCell) of the UE's master cell group, and a configured maximum transmit power value for the SCell Includes at least one of the following:

[0072] The following text describes a particular embodiment 2 of the method depicted and illustrated in FIG. 7 for solving the above problem.

[0073] According to embodiment 2, a UE (e.g., UE 101 shown and illustrated in FIG. 1) and a BS (e.g., MN 102 shown and illustrated in FIG. 1) perform the following operations in an MRO mechanism for a fast MCG link recovery procedure. (1) Step 1: The UE remains in the RRC_Connected state. One of the following three failures may occur in the UE: RLF, HO failure, and CHO failure. · The UE remembers its transmit power when a failure occurs. ·UE stores the PH value for each panel. (2) Step 2: When a failure occurs, the UE performs an RRC re-establishment procedure and selects a suitable cell. The UE may be configured with a fast MCG link recovery procedure. If the fast MCG link recovery procedure is configured, it is considered that a fast MCG link recovery failure occurs. (3) Step 3: The UE sends an RRCReestablishmentRequest message to the selected target cell. After the UE successfully accesses the selected target cell, the UE sends an RRCReestablishmentComplete message to the target BS in the selected target cell. The RRCReestablishmentComplete message includes an indication to indicate that auxiliary information is available. (4) Step 4: After receiving the instruction, the target BS sends a UE Information Request message to the UE. (5) Step 5: The UE sends a UE information response message to the target BS. To identify which link (DL or UL) causes the RLF, the UE information response message includes at least one of the following: - An indication to indicate whether the current UL transmit power of the UE has reached the maximum UL transmit power value. - The value of the UE's current UL transmit power. · When DC is configured, the UE's UL transmit power is associated with the MCG. - PH value for the PHR when RLF is detected. The PH value may be a per-beam and / or per-panel identification (ID). The PH value may be at least one of the following: 1) PH value for PCell and corresponding P for PH calculation cmax,f,c . - P cmax,f,c denotes the nominal UE maximum transmit power (per carrier f of serving cell c). - The PH value for the PCell may be a Type 1 PH value, a Type 2 PH value, or a Type 3 PH value. 2) PH value for PSCell and the corresponding P for PH calculation cmax,f,c . - The PH value for the PSCell may be a Type 1 PH value, a Type 2 PH value, or a Type 3 PH value. 3) PH value for SCell and the corresponding P for PH calculation cmax,f,c . - The PH value for the SCell may be a Type 1 PH value, a Type 2 PH value, or a Type 3 PH value. 4) The number of retransmissions of one packet at the RLC layer.

[0074] Details described in all other embodiments of this application (e.g., details of how to implement MRO mechanisms for unbalanced UL and DL coverage scenarios) are applicable to the embodiment of Figure 7. Moreover, details described in the embodiment of Figure 7 are applicable to all embodiments of Figures 1-6 and 8.

[0075] 8 shows an exemplary block diagram of an apparatus according to some embodiments of the present application. In some embodiments of the present application, the apparatus 800 may be a UE capable of at least performing the method illustrated in FIG. 6 or FIG.

[0076] As shown in FIG. 8, the apparatus 800 may include at least one receiver 802, at least one transmitter 804, at least one non-transitory computer-readable medium 806, and at least one processor 808 coupled to the at least one receiver 802, the at least one transmitter 804, and the at least one non-transitory computer-readable medium 806.

[0077] 8, elements such as at least one receiver 802, at least one transmitter 804, at least one non-transitory computer-readable medium 806, and at least one processor 808 are described in the singular, but the plural is contemplated unless limitation to the singular is expressly stated. In some embodiments of the present application, the at least one receiver 802 and the at least one transmitter 804 are combined into a single device, such as a transceiver. In some embodiments of the present application, the apparatus 800 may further include an input device, a memory, and / or other components.

[0078] In some embodiments of the present application, at least one non-transitory computer-readable medium 806, together with at least one receiver 802, at least one transmitter 804, and at least one processor 808, may store computer-executable instructions programmed to implement operations of a method such as those described with reference to any of Figures 6 and 7, for example.

[0079] Those skilled in the art will appreciate that the operations of the methods described with respect to the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. Furthermore, in some embodiments, the operations of the methods may reside as one or any combination or set of codes and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

[0080] Although the present disclosure has been described with its specific embodiments, it is apparent that numerous alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be exchanged, added, or substituted in other embodiments. Also, not all elements of each figure are necessary for the operation of the disclosed embodiments. For example, those skilled in the art will be enabled to make and use the teachings of the present disclosure by simply adopting the elements of the independent claims. Thus, the embodiments of the present disclosure described herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the present disclosure.

[0081] As used herein, the terms "includes," "including," or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements does not include only those elements, but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by "a," "an," etc., does not, without more constraints, preclude the existence of additional equivalent elements in the process, method, article, or apparatus that includes that element. Also, the term "another" is defined as at least a second or more. As used herein, terms such as "having" are defined as "including." [Explanation of symbols]

[0082] 100 Wireless Communication System, Dual Connectivity System 101, 210, 310, 410 UE 102, 220, 330, 420 MN 103, 320 SN 510, 520BS 800 equipment 802 Receiver 804 Transmitter 806 Non-transitory computer-readable medium 808 Processor

Claims

1. 1. A method comprising: receiving configuration information regarding a fast master cell group (MCG) link recovery procedure for a user equipment (UE); in response to an occurrence of a Radio Link Failure (RLF) on the MCG, performing said Fast MCG Link Recovery procedure and starting a timer associated with Fast MCG Link Recovery; storing information associated with the Fast MCG Link Recovery procedure based on a failure to complete the Fast MCG Link Recovery procedure; reporting the stored information to a base station (BS); Including, The method further comprising: based on a failure to complete the fast MCG link recovery procedure; receiving a UE information request message from a target BS; sending a UE information response message to the target BS, the UE information response message including auxiliary information associated with the Fast MCG Link Recovery procedure, the auxiliary information including an indication of expiration of a timer associated with the Fast MCG Link Recovery; The method further comprising:

2. based on a failure to complete the fast MCG link recovery procedure; performing a radio resource control (RRC) re-establishment procedure in response to expiration of a timer associated with the fast MCG link recovery or in response to an occurrence of the RLF on a link of a secondary cell group (SCG); storing an RLF cause for the link in the SCG, the RLF cause comprising: Expiration of the physical layer problem timer, expiry of a timer for initiating fault recovery based on triggering a measurement report; Random access problem, Reaching the Radio Link Control (RLC) maximum retransmission count; SCG configuration failure, and Integrity Check Failure Indication At least one of the steps The method of claim 1, further comprising:

3. The auxiliary information is an indication as to whether a timer associated with the Fast MCG Link Recovery is configured for the UE; an indication as to whether the Fast MCG Link Recovery is configured for the UE; and Fast MCG Link Recovery Fault Indication The method of claim 1 , further comprising one of:

4. The auxiliary information is RLF indication on SCG links 4. The method of claim 3, further comprising:

5. The indication of the RLF on the link of the SCG includes an RLF cause for the link of the SCG, the RLF cause comprising: Expiration of the physical layer problem timer, expiry of a timer for initiating fault recovery based on triggering a measurement report; Random access problem, Reaching the Radio Link Control (RLC) maximum retransmission count; SCG configuration failure, and Integrity Check Failure Indication The method of claim 4, wherein the at least one of

6. The method of claim 1 , wherein the auxiliary information includes a container containing an SCG fault information message.

7. The method of claim 1, wherein the step of reporting the stored information to the BS is in response to an access by the UE to a base station (BS).

8. An apparatus comprising: a non-transitory computer readable medium having computer executable instructions stored thereon; A receiving circuit; A transmission circuit; a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry; Equipped with 8. An apparatus, the computer-executable instructions causing the processor to perform the method of any one of claims 1 to 7.

Images