Method and apparatus for a master cell group

Abstract

Embodiments of the present application relate to a method and apparatus for a master cell group, e.g., a radio link failure (RLF) reporting mechanism associated with a source link and a dual active protocol stack (DAPS) handover procedure during a DAPS handover procedure under a 3GPP (3rd Generation Partnership Project) 5G New Radio (NR) system. According to one embodiment of the present application, the method may include the steps of: receiving configuration information including a timer associated with high-speed MCG link recovery; receiving a radio resource control (RRC) reconfiguration message including DAPS configuration information; and initiating an MCG failure information procedure based on a condition of whether or not a timer for handover is running in response to an RLF of the source link for the MCG. Additionally, an RLF report may be reported to the target cell after the UE has successfully accessed the target cell.

Description

Technology Field

[0001] The embodiments of the present application generally relate to wireless communication technology, and in particular, to a radio link failure (RLF) reporting mechanism associated with a source link to an MCG during a DAPS handover procedure for a master cell group (MCG), for example, and to a method and apparatus for a dual active protocol stack (DAPS) handover procedure. Background Technology

[0002] When a Radio Link Failure (RLF) or Handover Failure (HOF) occurs for a User Equipment (UE), the UE may perform a Radio Resource Control (RRC) re-establishment procedure. The UE may access the cell via a successful RRC re-establishment procedure or via a connection setup procedure in response to an unsuccessful 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. Accordingly, the UE will transmit a failure report to the network.

[0003] In 3GPP (3rd Generation Partnership Project) standard documents, after a UE receives a handover command associated with a DAPS handover procedure, the connection with the source base station (BS) will still be maintained until the UE successfully completes the random access procedure to the target BS and releases the source cell of the source BS.

[0004] Currently, details regarding how to resolve the issue of coexistence between the RLF reporting mechanism for MCG and the DAPS handover procedure in 3GPP 5G NR (New Radio) systems have not yet been specifically discussed.

[0005] Some embodiments of the present application provide a method for wireless communications. The method may be performed by a UE. The method comprises receiving configuration information including a timer associated with Fast Master Cell Group (MCG) link recovery; receiving a Radio Resource Control (RRC) reconfiguration message including Dual Active Protocol Stack (DAPS) configuration information; performing a DAPS handover procedure; starting a timer for handover; in response to a Radio Link Failure (RLF) of the source link to the MCG during the DAPS handover procedure, initiating an MCG failure information procedure when the timer for handover is running; and starting a timer associated with Fast MCG link recovery.

[0006] Some embodiments of the present application also provide a device for wireless communications. The device comprises a non-transient computer-readable medium storing computer-executable instructions; a receiving circuit; a transmitting circuit; and a processor coupled to the non-transient computer-readable medium, the receiving circuit, and the transmitting circuit, wherein the computer-executable instructions enable the processor to implement the above-mentioned method performed by a UE.

[0007] Some embodiments of the present application provide additional methods for wireless communications. The method may be performed by a UE. The method includes receiving configuration information including a timer associated with Fast Master Cell Group (MCG) link recovery; and initiating an MCG failure information procedure in response to a radio link failure (RLF) of the source link to the MCG during a Dual Active Protocol Stack (DAPS) handover procedure, when the timer associated with Fast MCG link recovery is not running and the timer for the handover is not running.

[0008] Some embodiments of the present application also provide a device for wireless communications. The device comprises a non-transient computer-readable medium storing computer-executable instructions; a receiving circuit; a transmitting circuit; and a processor coupled to the non-transient computer-readable medium, the receiving circuit, and the transmitting circuit, wherein the computer-executable instructions enable the processor to implement the additional method mentioned above performed by the UE.

[0009] Some embodiments of the present application provide additional methods for wireless communications. The method may be performed by a UE. The method includes receiving a radio resource control (RRC) reconfiguration message comprising a reconfiguration having a synchronization information element (IE) and dual active protocol stack (DAPS) configuration information; performing a DAPS handover procedure; and transmitting an RLF report associated with the RLF after successfully completing the DAPS handover procedure in response to a radio link failure (RLF) of the source link for a master cell group (MCG) during the DAPS handover procedure.

[0010] Some embodiments of the present application also provide a device for wireless communications. The device comprises a non-transient computer-readable medium storing computer-executable instructions; a receiving circuit; a transmitting circuit; and a processor coupled to the non-transient computer-readable medium, the receiving circuit, and the transmitting circuit, wherein the computer-executable instructions enable the processor to implement the additional method mentioned above performed by the UE.

[0011] Some embodiments of the present application provide additional methods for wireless communications. The method may be performed by a BS. The method comprises the steps of: transmitting a request for user equipment (UE) information; receiving a UE information response including a radio link failure (RLF) report, wherein the RLF report includes information regarding a radio link failure (RLF) of a source link to a master cell group (MCG) during a dual active protocol stack (DAPS) handover procedure; and transmitting a failure indication, wherein the failure indication includes an information element (IE) regarding the successful completion of a DAPS handover procedure.

[0012] Some embodiments of the present application also provide a device for wireless communications. The device comprises a non-transient computer-readable medium storing computer-executable instructions; a receiving circuit; a transmitting circuit; and a processor coupled to the non-transient computer-readable medium, the receiving circuit and the transmitting circuit, wherein the computer-executable instructions cause the processor to implement the additional method mentioned above performed by BS.

[0013] Details of one or more examples are disclosed in the accompanying drawings and the following descriptions. Other features, objects, and advantages will be apparent from the descriptions and drawings, and from the claims. Brief explanation of the drawing

[0014] To explain how the advantages and features of the present application can be obtained, the description of the present application is made with reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings illustrate only exemplary embodiments of the present application and should not be construed as limiting its scope. FIG. 1 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application. FIG. 2 illustrates an exemplary flowchart of a failure information procedure according to some embodiments of the present application. FIG. 3 illustrates an exemplary flowchart of an intra-AMF (access and mobility management function) handover procedure according to some embodiments of the present application. FIG. 4 illustrates an exemplary timeline of an RLF having a high-speed MCG link recovery procedure according to some embodiments of the present application. FIG. 5a illustrates a flowchart of a method for a DAPS handover procedure according to some embodiments of the present application. FIG. 5b illustrates a flowchart of a method for an MCG failure information procedure according to some embodiments of the present application. FIG. 6 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application. FIG. 7 illustrates an exemplary signal transmission procedure according to some embodiments of the present application. FIG. 8 illustrates a flowchart of a method for a failure reporting procedure according to some embodiments of the present application. FIG. 9 illustrates an additional exemplary signal transmission procedure according to some embodiments of the present application. FIG. 10 illustrates an additional flowchart of a method for a failure indication procedure according to some embodiments of the present application. FIG. 11 illustrates a simplified block diagram of an apparatus (1100) for an enhanced failure reporting mechanism according to some embodiments of the present application. Specific details for implementing the invention

[0015] The detailed description of the accompanying drawings is intended to describe preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that identical or equivalent functions may be achieved by different embodiments intended to be included within the spirit and scope of the present application.

[0016] Some embodiments of the present application will now be referred to in detail, and examples are illustrated in the accompanying drawings. For ease of understanding, 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, all embodiments of the present application are also applicable to similar technical problems; furthermore, it is considered that terms cited in the present application may be modified, and this should not affect the principles of the present application.

[0017] The Next Generation Radio Access Network (NG-RAN) supports Multi-Radio Duplex Access (MR-DC) operation. In MR-DC operation, a UE with multiple transceivers can be configured to utilize resources provided by two different nodes connected via non-ideal backhauls. Here, one node can provide NR access, and the other node can provide Advanced Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA) (E-UTRA) or NR access. One node can act as a master node (MN), and the other node can act as a secondary node (SN). The MN and SN are connected via a network interface (e.g., an Xn interface as specified in 3GPP standard documents), and at least the MN is connected to the core network.

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

[0019] As illustrated in FIG. 1, the wireless communication system (100) may be a dual access system (100) comprising at least one UE (101), at least one MN (102), and at least one SN (103). In particular, the dual access system (100) of FIG. 1 comprises one illustrated UE (101), one illustrated MN (102), and one illustrated SN (103) for the purpose of illustration. Although a specific number of UEs (101), MNs (102), and SNs (103) are illustrated in FIG. 1, it is considered that any number of UEs (101), MNs (102), and SNs (103) may be included in the wireless communication system (100).

[0020] Referring to FIG. 1, the UE (101) may be connected to the MN (102) and SN (103) through a network interface, for example, a Uu interface as specified in 3GPP standard documents. The MN (102) and SN (103) may be connected to each other through a network interface, for example, an Xn interface as specified in 3GPP standard documents. The MN (102) may be connected to a core network through a network interface (not shown in FIG. 1). The UE (102) may be configured to use resources provided by the MN (102) and SN (103) to perform data transmission.

[0021] MN (102) may refer to a radio access node that provides control plane access to a core network. In an embodiment of the present application, in an E-UTRA-NR DC (EN-DC) scenario, MN may be an eNB. In another embodiment of the present application, in a next-generation E-UTRA-NR DC (NGEN-DC) scenario, MN 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, MN may be a gNB.

[0022] MN (102) may be associated with MCG. MCG may refer to a group of serving cells associated with MN (102) and may include a primary cell (PCell) of MCG and optionally one or more secondary cells (SCell). PCell may provide control plane connections to UE (101).

[0023] SN (103) may refer to a radio access node that does not have control plane access to the core network but provides additional resources to the UE (101). In an embodiment of the present application, in an EN-DC scenario, SN (103) may be an en-gNB. In another embodiment of the present application, in an NE-DC scenario, 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, SN (103) may be a gNB.

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

[0025] PCells of MCG and PSCells of SCG may also be referred to as special cells (SpCells).

[0026] In some embodiments of the present application, the UE (101) may include computing devices such as desktop computers, laptop computers, PDAs (personal digital assistants), tablet computers, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, and modems), etc. 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, an optional call receiving circuit, or any other device capable of transmitting and receiving communication signals over a wireless network. In some other embodiments of the present application, the UE (101) may include wearable devices such as smartwatches, fitness bands, optical head-mounted displays, etc. Furthermore, the UE (101) may be referred to as a subscriber unit, mobile, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or may be described using other terms used in the art.

[0027] FIG. 2 illustrates an exemplary flowchart of a failure information procedure according to some embodiments of the present application. The failure information procedure may also be referred to as a failure information reporting procedure. The embodiments of FIG. 2 include the following embodiments of an SCG failure information procedure or an MCG failure information procedure.

[0028] Specifically, in some embodiments of the SCG failure information procedure, in operation (201) as illustrated in FIG. 2, the UE (101) and the MN (102) may communicate RRC reconfiguration information. In operation (202) as illustrated in FIG. 2, the UE (101) may initiate the SCG failure information procedure and transmit a message associated with the failure of the SCG to the MN (102). The message associated with the failure of the SCG in operation (202) may be an SCGFailureInformation message as specified in 3GPP standard documents. Next, the MN (102) may handle the SCGFailureInformation message and decide whether to retain the SN or SCG, change the SN or SCG, or release the SN or SCG. The SN may be an SN (103) as illustrated and exemplified in FIG. 1.

[0029] In the aforementioned embodiments of the SCG failure information procedure, the UE (101) may initiate the SCG failure information procedure to report a failure to the SCG when one of the following conditions is met:

[0030] ● When detecting a failure regarding the SCG. For example, a failure regarding the SCG may refer to an RLF occurring in the SCG's PSCell.

[0031] ● When reconfiguring with SCG synchronization failure.

[0032] ● In case of SCG configuration failure.

[0033] ● When an integrity check failure is indicated from the lower layer(s) of the SCG regarding Signaling Radio Bearer (SRB)3.

[0034] In 3GPP Release 16, the Fast MCG Link Recovery Procedure is introduced for MR-DC scenarios. The Fast MCG Link Recovery Procedure may also be referred to as the MCG Failure Information Procedure. The purpose of this procedure is to notify the MN of an RLF regarding the MCG through the SN connected to the UE, thereby enabling the UE in the RRC_CONNECTED state to initiate the Fast MCG Link Recovery Procedure to quickly resume RRC connectivity without performing a re-establishment procedure.

[0035] In some other embodiments of FIG. 2 of the present application, when a failure to the MCG occurs, the UE (101) may initiate (or trigger) a high-speed MCG link recovery procedure, i.e., an MCG failure information procedure.

[0036] Specifically, in some embodiments of the MCG failure information procedure, as illustrated in FIG. 2, in operation (201), the UE (101) and the MN (102) can communicate RRC reconfiguration information. In operation (202), the UE (101) can initiate the MCG failure information procedure and transmit a message associated with a failure of the MCG to the MN (102). For example, a failure of the MCG may refer to an RLF occurring in the PCell of the MCG. In operation (202), the message associated with the failure of the MCG may be an MCGFailureInformation message as specified in 3GPP standard documents.

[0037] In embodiments of the MCG failure information procedure, the UE (101) may not directly transmit a message associated with the failure of the MCG to the MN (102). Instead, the UE (101) may transmit a message associated with the failure of the MCG to the SN (e.g., SN (103) as illustrated and exemplified in FIG. 1), and then the SN may transmit the message received from the UE (101) to the MN (102).

[0038] For example, the UE (101) may be configured as 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 (101) may submit an MCGFailureInformation message to the lower layer(s) for transmission, for example, via SRB1. If SRB3 is configured, the UE (101) may submit an MCGFailureInformation message to the lower layer(s) for transmission, for example, via SRB3. For example, the MCGFailureInformation message may be embedded in an NR RRC message ULInformationTransferMRDC, as specified in 3GPP standard documents, for transmission via SRB3.

[0039] When transmitting a message in operation (202) or thereafter, the UE (101) may start a timer associated with a high-speed MCG link recovery procedure. In an embodiment of the present application, the timer associated with a high-speed MCG link recovery procedure may be a T316 as specified in 3GPP standard documents.

[0040] After receiving a message associated with a failure of the MCG, the MN (102) may further transmit a response message to the UE (101). The response message may be an RRC reconfiguration message containing a handover (HO) command for the cell. The response message may be an RRC release message. In an embodiment of the present application, the handover command may be a reconfigurationWithSync configuration as specified in 3GPP standard documents. The MN (102) may not transmit the response message directly to the UE (101). Instead, the MN (102) may transmit the response message to an SN (e.g., an SN (103) as illustrated and exemplified in FIG. 1), and then the SN may transmit the response message to the UE (101).

[0041] If SRB3 is configured to transmit a message associated with a failure of MCG, after receiving a response message from MN (102), SN (103) can encapsulate the response message into a DLInformationTransferMRDC message as specified in 3GPP standard documents and then transmit the DLInformationTransferMRDC message to UE (101).

[0042] In the aforementioned embodiments of the MCG failure information procedure, the UE (101) can set the MCG failure type (referred to as "failureType") as follows:

[0043] ● When UE (101) initiates the transmission of the MCGFailureInformation message as described in operation (202), due to the expiration of timer T310 (which may be referred to as the physical layer problem timer) as specified in 3GPP standard documents, UE (101) sets the failureType to t310-Expiry as specified in 3GPP standard documents.

[0044] ● When UE (101) initiates the transmission of an MCGFailureInformation message as described in operation (202) and provides a random access problem indication from the Media Access Control (MAC) layer of the MCG, UE (101) sets the failureType to randomAccessProblem as specified in 3GPP standard documents.

[0045] ● When UE (101) initiates the transmission of an MCGFailureInformation message as described in operation (202) and receives an indication from the MCG radio link control (RLC) that the maximum number of retransmissions has been reached, UE (101) sets the failureType to rlc-MaxNumRetx as specified in the 3GPP standard documents.

[0046] When implementing the DAPS handover procedure, the UE continues to receive downlink user data from the source BS until the source cell of the source BS is released, and the UE continues to send uplink user data transmission(s) to the source BS until the random access procedure to the target BS is successfully completed. When the DAPS handover procedure fails, the UE may report the DAPS handover (HO) failure through the source BS without triggering the RRC connection re-establishment procedure if the source link is not released.

[0047] In the control plane handling during handover associated with the DAPS handover procedure, messages are exchanged directly between BSs. A specific example is illustrated in Figure 3 below.

[0048] FIG. 3 illustrates an exemplary flowchart of an intra-AMF handover procedure according to some embodiments of the present application. The embodiments of FIG. 3 illustrate a basic conditional handover scenario in which neither the access and mobility management function (AMF) nor the user plane function (UPF) is changed.

[0049] Referring to FIG. 3, in operation (301), the source BS can transmit measurement configuration information to the UE. The UE can report measurement results to the source BS based on the measurement configuration information. In operation (302), the source BS can decide to hand over the UE, which may be based on the measurement results reported by the UE.

[0050] In operation (303), the source BS can send a HANDOVER REQUEST message to the target BS. For example, the HANDOVER REQUEST message can convey a transparent RRC container containing information necessary for the target BS to prepare the handover procedure.

[0051] In operation (304), the target BS performs approval control based on the load of the target cell of the target BS and can determine whether to allow the handover procedure of the UE after receiving a handover request message from the source BS.

[0052] In operation (305), based on the result of the acknowledgment control, the target BS can prepare handover resource(s) for the UE and send a HANDOVER REQUEST ACKNOWLEDGE containing an RRC reconfiguration message to the source BS.

[0053] In operation (306), a RAN handover is initiated. The source BS may send an RRC reconfiguration message to the UE. The RRC reconfiguration message may include a reconfiguration having a synchronization information element (IE). The RRC reconfiguration message may include information necessary to access the target cell of the target BS.

[0054] In operation (307), the source BS can send an SN STATUS TRANSFER message to the target BS.

[0055] In operation (308), the UE can complete the handover procedure by accessing the target cell and sending an RRCReconfigurationComplete message to the target BS. In some embodiments implementing the DAPS handover procedure, the UE is not detached from the source cell upon receiving the RRCReconfiguration message. For example, the UE can release the source resource(s) upon receiving an explicit release indication from the target BS.

[0056] In operation (309), the target BS can send a PATH SWITCH REQUEST message to the AMF to trigger the 5G core (5GC) network to switch the downlink (DL) data path toward the target BS.

[0057] In operation (310), the 5GC network can switch the DL data path toward the target BS. The UPF(s) can transmit one or more "end marker" packets on the previous (source) data path to the source BS per packet data unit (PDU) session or PDU tunnel. Afterward, the UPF(s) can release any user plane or transport network layer (TNL) resources toward the source BS.

[0058] In operation (311), the AMF can check the PATH SWITCH REQUEST message with the PATH SWITCH REQUEST ACKNOWLEDGE message.

[0059] In operation (312), in response to receiving a PATH SWITCH REQUEST ACKNOWLEDGE message from the AMF, the target BS may send a UE CONTEXT RELEASE message to notify the source BS of the success of the handover procedure. Afterward, the source BS may release the radio and control plane related resource(s) associated with the UE context. Any ongoing data forwarding may continue.

[0060] FIG. 4 illustrates an exemplary timeline of an RLF having a high-speed MCG link recovery procedure according to some embodiments of the present application. The embodiments of FIG. 4 can be performed by a UE (e.g., a UE (101) as illustrated and exemplified in FIG. 1).

[0061] As illustrated in FIG. 4, the UE first performs data transmission in the normal operation stage. For example, if the UE's MAC layer receives a N310 consecutive out-of-sync indication from the UE's physical layer, this indicates that a radio link problem has occurred, and the UE detects the radio link problem. The UE then starts a timer, for example, timer T310, as specified in 3GPP standard documents. During the duration of timer T310, if the UE's MAC layer receives a N311 consecutive sync indication from the physical layer, this indicates that the UE has successfully connected to the network, and the UE can stop timer T310.

[0062] When Timer T310 expires, this signifies no recovery during Timer T310, and the UE initiates the Fast MCG link recovery procedure. Specifically, the UE transmits MCG failure information to the MN (e.g., MN (102) as illustrated and exemplified in FIG. 1) via the SN (e.g., SN (103) as illustrated and exemplified in FIG. 1) and starts Timer T316 as specified in 3GPP standard documents, as illustrated in FIG. 4. If the UE receives RRC reconfiguration from the MN via the SN, the UE stops Timer T316, which signifies that the Fast MCG link recovery procedure is terminated. Otherwise, in response to the expiration of Timer T316, which signifies no recovery during Timer T316, the UE performs the RRC re-establishment procedure and starts Timer T311 for cell selection as specified in 3GPP standard documents.

[0063] When timer T311 expires, this means there is no recovery during timer T311, and the UE returns to an idle state, for example, the RRC_IDLE state. Before timer T311 expires, the UE is in the RRC_CONNECTED state as shown in FIG. 4. After timer T311 expires, the UE enters the RRC_IDLE state as shown in FIG. 4.

[0064] The above description regarding the embodiments of FIG. 4 does not take into account Timer T312. Some embodiments assume that Timer T312 is configured as specified in 3GPP standard documents. In these embodiments, Timer T310 is running, and when a measurement report for a measurement identity configured for Timer T312 is triggered, the UE will start Timer T312. After Timer T312 expires, the UE can declare a failure and trigger a failure recovery procedure, for example, a configured high-speed MCG link recovery procedure.

[0065] Embodiments of the present application provide coexistence scenarios of an RLF reporting mechanism and a DAPS handover procedure for MCG. More details regarding the embodiments of the present application will be illustrated in the following text together with the accompanying drawings.

[0066] Embodiments of the present application may solve problems relating to the following: (1) a method for handling cases where an RLF occurs on the source link of an MCG while a UE is performing a DAPS handover procedure and a high-speed MCG link recovery procedure is configured for the UE; and (2) a method for handling cases where a timer associated with high-speed MCG link recovery is running and a DAPS handover procedure is in progress and the UE receives a response from an MN via an SN. Specific examples are described and illustrated in FIGS. 5a and 5b.

[0067] FIG. 5a illustrates a flowchart of a method for a DAPS handover procedure according to some embodiments of the present application.

[0068] The method (500A) as illustrated in FIG. 5a can be performed by a UE (e.g., UE (101) as illustrated and exemplified in FIG. 1 and 2). For example, the UE can be configured as a DC, where the UE is connected to an MN (e.g., MN (102) as illustrated and exemplified in FIG. 1 and 2) and an SN (103) (e.g., SN (103) as illustrated and exemplified in FIG. 1).

[0069] In the embodiments of FIG. 5a, when the UE is performing the DAPS handover procedure, the UE may be allowed to initiate or trigger a high-speed MCG link recovery procedure (e.g., an MCG failure information procedure).

[0070] In one example, if a high-speed MCG link recovery procedure is triggered while the UE is performing a DAPS handover procedure (e.g., when timer T316 is running), the UE may report MCG failure information to the source MN via the SN. The source MN may send an RRC reconfiguration message containing a handover command or send a release message to the UE. In this case, if the DAPS handover procedure is in progress, the RRC connection re-establishment procedure must not be triggered by the UE when the timer associated with the high-speed MCG link recovery (e.g., timer T316) expires.

[0071] In an additional example, when a timer for handover is triggered (e.g., when timer T304 is running), the UE does not initiate the RRC connection re-establishment procedure after the timer associated with high-speed MCG link recovery (e.g., timer T316) has expired.

[0072] In another example, if the timer for the handover is not triggered (e.g., timer T304 is not running), the UE may initiate the RRC connection re-establishment procedure after the timer associated with the high-speed MCG link recovery (e.g., timer T316) has expired.

[0073] Specifically, as illustrated in FIG. 5a, in operation (501), the UE may receive configuration information including a timer associated with high-speed MCG link recovery. For example, the timer associated with high-speed MCG link recovery may be timer T316 as specified in 3GPP standard documents.

[0074] In operation (503), the UE may receive an RRC reconfiguration message. The RRC reconfiguration message includes DAPS configuration information. The DAPS configuration information may be a DAPS bearer. In operation (505), the UE may perform a DAPS handover procedure.

[0075] In operation (507), the UE may start a timer for handover. The timer value of the timer for handover may be included in a reconfiguration having a synchronized IE. In an embodiment of the present application, the timer for handover is timer T304 as specified in 3GPP standard documents.

[0076] In operation (509), in response to the RLF of the source link to the MCG during the DAPS handover procedure, the MCG failure information procedure is initiated when the timer for the handover is running. In operation (511), the UE may start a timer (e.g., timer T316) associated with high-speed MCG link recovery included in the configuration information received in operation (501).

[0077] In an embodiment of the present application, the UE may transmit an MCG failure information message in response to initiating an MCG failure information procedure. When transmitting the MCG failure information message or thereafter, if the timer associated with high-speed MCG link recovery expires, the UE may not initiate an RRC connection re-establishment procedure when performing a DAPS handover procedure.

[0078] When transmitting an MCG failure information message or thereafter, the UE may receive another RRC reconfiguration message. For example, the UE may receive this RRC reconfiguration message after transmitting an MCG failure information message. The UE may receive this RRC reconfiguration message when the timer associated with fast MCG link recovery is running. For example, this RRC reconfiguration message may include a reconfiguration with a sync IE. The reconfiguration with a sync IE may be a reconfigurationWithSync IE as specified in 3GPP standard documents.

[0079] In one example, after receiving the aforementioned other RRC reconfiguration message, the UE may execute a reconfiguration with a synchronization procedure, and the UE may stop the execution of the ongoing DAPS handover procedure. In another example, after receiving the aforementioned other RRC reconfiguration message, the UE may ignore this RRC reconfiguration message but continue the ongoing DAPS handover procedure.

[0080] In an embodiment of the present application, the UE may receive an RRC release message. For example, the UE may receive an RRC release message after transmitting an MCG failure information message. The UE may receive an RRC release message while a timer associated with fast MCG link recovery is running. After receiving the RRC release message, the UE may release the resource(s) associated with the source link where the RLF occurred and continue the DAPS handover procedure. Alternatively, the UE may ignore the RRC release message and continue the DAPS handover procedure.

[0081] The following text describes a specific embodiment 1 of the method as illustrated and exemplified in FIG. 5a for solving the above problems.

[0082] According to Example 1, a UE (e.g., a UE (101) as illustrated and exemplified in FIGS. 1 and 2) performs the following operations:

[0083] (1) The UE accesses the network through DC operation.

[0084] ● Configuration for MCG and SCG can be configured for the UE.

[0085] ● High-speed MCG link recovery procedure, for example, the value of timer T316 can be configured in the UE.

[0086] (2) The UE reports the measurement results to a network (e.g., PCell or PSCell).

[0087] (3) The source BS sends a handover request message to the target BS.

[0088] (4) The target BS prepares the handover resource(s) for the UE and sends a HANDOVER REQUEST ACKNOWLEDGE containing an RRC reconfiguration message to the source BS.

[0089] (5) The source BS sends an RRC reconfiguration message to the UE containing ReconfigurationWithSync IE, which contains information necessary for the source BS to access the target cell of the target BS.

[0090] ● This operation of BS is related to the contents associated with the operation (306) in FIG. 3. An RRC reconfiguration message including reconfigurationWithSync IE can be used for mobility purposes. For example, an RRC reconfiguration message including reconfigurationWithSync IE can be used in a normal handover procedure, a conditional handover procedure, a DAPS handover procedure, and / or a PScell ​​change procedure.

[0091] ● Configuration information for the DAPS handover procedure (e.g., dapsConfig as specified in 3GPP standard documents) can be configured for the data radio bearer (DRB).

[0092] (6) The UE accesses the target cell.

[0093] ● In the case of the DAPS handover procedure, the UE is not detached from the source cell upon receiving the RRC reconfiguration message. The UE continues to monitor the source cell.

[0094] (7) When the UE performs the DAPS handover procedure, the UE detects RLF in the source Pcell.

[0095] (8) UE sends an MCG failure information message to MN via SN and starts timer T316.

[0096] (9) UE adopts different actions under different scenarios:

[0097] (a) If the UE receives a response from the MN via the SN before timer T316 expires:

[0098] - When the UE receives an RRC reconfiguration message containing reconfigurationWithSync IE:

[0099] Option A-1: ​​The UE can perform a reconfiguration with a synchronization procedure and stop the ongoing DAPS handover procedure.

[0100] Option A-2: The UE ignores the received RRC reconfiguration message and continues the ongoing DAPS handover procedure.

[0101] - When the UE receives an RRC release message:

[0102] Option B-1: The UE can disconnect from the source and continue the ongoing DAPS handover procedure.

[0103] Option B-2: The UE can ignore the received RRC reconfiguration message and continue the ongoing DAPS handover procedure.

[0104] (b) If the UE does not receive a response from the MN via the SN before timer T316 expires. That is, if timer T316 expires:

[0105] - Option (1): If timer T304 is running, the re-establishment procedure should not be triggered in response to the expiration of timer T316.

[0106] - Option (2): The UE may initiate a re-establishment procedure in response to the expiration of timer T316 only if timer T304 is not running.

[0107] (10) The UE continues the DAPS handover procedure and accesses the target cell.

[0108] FIG. 5b illustrates a flowchart of a method for an MCG failure information procedure according to some embodiments of the present application. A method (500B) as illustrated in FIG. 5b may be performed by a UE (e.g., a UE (101) as illustrated and exemplified in FIG. 1 and 2). The UE may be composed of a DC, wherein the UE is connected to an MN (e.g., an MN (102) as illustrated and exemplified in FIG. 1 and 2) and an SN (103) (e.g., an SN (103) as illustrated and exemplified in FIG. 1).

[0109] In the embodiments of FIG. 5b, when the UE is performing a DAPS handover procedure, the UE may not be allowed to initiate or trigger a high-speed MCG link recovery procedure (e.g., an MCG failure information procedure). Under certain condition(s), the UE may initiate or trigger a high-speed MCG link recovery procedure (e.g., an MCG failure information procedure).

[0110] As illustrated in FIG. 5b, in operation (502), the UE may receive configuration information including a timer associated with high-speed MCG link recovery, e.g., timer T316 as specified in 3GPP standard documents. In operation (504), when an RLF occurs on the source link to the MCG during the DAPS handover procedure, and the timer associated with high-speed MCG link recovery (e.g., timer T316) is not running and the timer for the handover is not running, the UE may initiate an MCG failure information procedure.

[0111] In an embodiment of the present application, the timer for the handover is timer T304 as specified in 3GPP standard documents. In this embodiment, when an RLF occurs on the source link of the MCG, when timer T316 is not running, and when timer T304 is not running, the UE may initiate an MCG failure information procedure.

[0112] In another embodiment of the present application, a timer for handover is associated with DAPS configuration information. For example, DAPS configuration information is included in an RRC reconfiguration message received by the UE. In this embodiment, if an RLF occurs on the source link of the MCG, if timer T316 is not running, and if DAPS configuration is not configured for any DRB, the UE may initiate an MCG failure information procedure.

[0113] The following text describes a specific embodiment 2 of the method as illustrated and exemplified in FIG. 5b for solving the above problems.

[0114] According to Example 2, the UE (e.g., UE (101) as illustrated and exemplified in FIGS. 1 and 2) and the MN (e.g., MN (102) as illustrated and exemplified in FIGS. 1 and 2) perform the following operations:

[0115] (1) The UE accesses the network through DC operation.

[0116] ● Configuration for MCG and SCG can be configured for the UE.

[0117] ● High-speed MCG link recovery procedure, for example, the value of timer T316 can be configured in the UE.

[0118] (2) The UE detects RLF in the source link to the MCG (e.g., Pcell).

[0119] (3) UE adopts different actions under different scenarios:

[0120] ● When RLF of MCG is detected, if Timer T316 is not running and Timer T304 is not running, the UE may initiate the MCG failure information procedure.

[0121] ● When RLF of MCG is detected, if timer T316 is not running and DAPS configuration is not configured for any DRB, the UE may initiate the MCG failure information procedure.

[0122] ● After initiating the MCG failure information procedure, the UE may stop transmitting SCG to all signaling radio bearers (SRBs) and DRBs, excluding signaling radio bearer (SRB)0.

[0123] (4) The UE sends an MCG failure information message to the MN via the SN and starts timer T316. The failure type and available measurement results will be included in the MCG failure information message.

[0124] (5) After receiving an MCG failure information message through SN, MN can send a response (e.g., RRC reconfiguration with reconfigurationWithSync IE) to UE.

[0125] (6) The UE receives a response from the MN via the SN (e.g., RRC reconfiguration with reconfigurationWithSync IE). After that, the UE can perform a handover procedure and a synchronization procedure for the target cell.

[0126] The details described in all other embodiments of the present application (e.g., details of the RLF reporting mechanism for MCG and the method for resolving the coexistence problem of the DAPS handover procedure) are applicable to the embodiments of FIGS. 5a and 5b. Additionally, the details described in the embodiments of FIGS. 5a and 5b are applicable to all embodiments of FIGS. 1 through 4 and FIGS. 6 through 11.

[0127] FIG. 6 illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0128] As illustrated and depicted in FIG. 6, the wireless communication system (600) includes at least one user equipment (UE) (601) and at least one base station (BS) (602). In particular, for the purpose of illustration, the wireless communication system (600) includes one UE (601) (e.g., UE (601a)) and two BSs (602) (e.g., BS (602a) and BS (602b)). Although a specific number of UEs (601) and BSs (602) are depicted in FIG. 6, it is considered that any number of UEs (601) and BSs (602) may be included in the wireless communication system (600).

[0129] The UE (601) as illustrated and exemplified in FIG. 6 has functions and characteristics similar to those of the UE (101) as illustrated and exemplified in FIG. 1. For details, refer to the above descriptions of the embodiments of FIG. 1.

[0130] BS(s) (602) may be distributed across a geographical area. In specific embodiments of this application, each BS(s) (602) may also be referred to as an access point, access terminal, base, base unit, macro cell, node-B, evolved node-B (eNB), gNB, NG-RAN (Next Generation-Radio Access Network) node, home node-B, relay node, or device, or may be described using other terms used in the art. A BS(s) (602) is generally part of a radio access network that may include one or more controllers communically coupled to one or more corresponding BS(s) (602). BS(s) (602) may communicate directly with each other. For example, BS(s) (602) may communicate directly with each other via an Xn interface or an X2 interface.

[0131] The wireless communication system (600) may be compatible with any type of network capable of transmitting and receiving wireless communication signals. For example, the wireless communication system (600) may be compatible with a wireless communication network, a cellular telephone network, a time division multiple access (TDMA) based network, a code division multiple access (CDMA) based network, an orthogonal frequency division multiple access (OFDMA) based network, an LTE network, a 3GPP based network, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0132] In some embodiments of the present application, the wireless communication system (600) is compatible with 5G NR of the 3GPP protocol, wherein the BS(s) (602) transmit data using OFDM modulation on DL and the UE(s) (601) transmit data using Single-Carrier Frequency Division Multiple Access (SC-FDMA) or OFDM on UL. However, more generally, the wireless communication system (600) may implement some other open or proprietary communication protocols, among other protocols, such as WiMAX.

[0133] In some embodiments of the present application, the BS(s) (602) may communicate using other communication protocols, such as IEEE 802.11 family wireless communication protocols. Furthermore, in some embodiments of the present application, the BS(s) (602) may communicate over licensed spectrum, whereas in other embodiments, the BS(s) (602) may communicate over unlicensed spectrum. The present application is not intended to be limited to any specific wireless communication system architecture or implementation of a protocol. In some other embodiments of the present application, the BS(s) (602) may communicate with the UE(s) (601) using 3GPP 5G protocols.

[0134] Each BS(s) (602) may include one or more cells. Each UE(s) (601) may perform a cell section procedure between different cell(s) of different BS(s). Each UE(s) (601) may perform a handover from a serving cell of a source BS to a target cell of a target BS. For example, in a wireless communication system (600) illustrated and depicted in FIG. 6, BS (602a) may function as a source BS, and BS (602b) may function as a target BS. If a handover is required, the UE (601a), as illustrated and depicted in FIG. 6, may perform a handover procedure from a serving cell of BS (602a) to a target cell of BS (602b), depending on the result of a cell selection procedure. The handover procedure performed by the UE (601a) may be a CHO procedure.

[0135] Currently, in 3GPP 5G NR systems and the like, radio access operating with shared spectrum channel access can operate in different modes, for example, modes where PCells, PSCells, or SCells may be in the shared spectrum, or modes where SCells may or may not be configured as uplinks. The BS can operate in dynamic access mode or semi-static channel access mode as described in 3GPP standard document TS37.213. In these two channel access modes, the BS and the UE may apply Listen-Before-Talk (LBT) before performing a transmission on a cell configured with shared spectrum channel access. When LBT is applied, the transmitter listens to or senses the channel to determine whether the channel is free or busy, and performs a transmission only if the channel is sensed to be free.

[0136] When the UE detects consistent uplink LBT failures, the UE takes the actions specified in 3GPP standard document TS38.321. Detection is performed per Bandwidth Part (BWP) and is based on all uplink transmissions within that BWP. When consistent uplink LBT failures are detected on SCell(s), the UE reports this to the corresponding BS (MN for the MCG, or SN for the SCG) via a MAC CE on a serving cell different from the SCell(s) where the failures were detected. If there are no available resources to transmit a MAC CE, a Scheduling Request (SR) may be transmitted by the UE. When consistent uplink LBT failures are detected on an SpCell, the UE switches to another UL BWP that has RACH resources configured on that cell, initiates RACH, and reports the failure via a MAC CE. When multiple UL BWPs are available for switching, the choice of which one to use depends on the UE implementation. For PSCell, if consistent uplink LBT failures are detected on all UL BWPs with configured RACH resources, the UE declares SCG RLF and reports the failure to the MN via SCGFailureInformation. For PCell, if uplink LBT failures are detected on all UL BWP(s) with configured RACH resources, the UE declares RLF.

[0137] Embodiments of the present application may solve the following problems: (1) what additional information should be added to an RLF-report when an RLF occurs from a source while a UE is performing a DAPS handover procedure; and (2) what information should be transmitted to a source cell after a target cell receives an RLF-report from the UE. Specific examples are described and illustrated in FIGS. 7 through 10.

[0138] FIG. 7 illustrates an exemplary signal transmission procedure according to some embodiments of the present application.

[0139] Specifically, as illustrated in FIG. 7, in operation (701), a UE (e.g., UE (101) as illustrated in FIG. 1 or UE (601a) as illustrated in FIG. 6) transmits a message associated with a failure of the MCG to a target BS (e.g., BS (602b) as illustrated in FIG. 6). The target BS controls the target cell of the UE. For example, the message associated with the failure of the MCG in operation (701) may be an RLF-report message as specified in 3GPP standard documents.

[0140] In particular, RLF-report messages as specified in 3GPP standard document TS38.331 may include the following fields: connectionFailureType, c-RNTI; failedCellId, failedPCellId, failedPCellId-EUTRA, previousPCellId; reestablishmentCellId, rlf-Cause, ssbRLMConfigBitmap, timeConnFailure, and timeSinceFailure.

[0141] FIG. 8 illustrates a flowchart of a method for a failure reporting procedure according to some embodiments of the present application. The method (800) illustrated in FIG. 8 may be performed by a UE (e.g., a UE (601a) as illustrated and exemplified in FIG. 6).

[0142] As illustrated in FIG. 8, in operation (802), the UE may receive an RRC reconfiguration message containing a reconfiguration with synchronization IE and DAPS configuration information. In operation (804), the UE may perform a DAPS handover procedure. If there is an RLF of the source link to the MCG during the DAPS handover procedure, after successfully completing the DAPS handover procedure, the UE may transmit an RLF report related to the RLF as illustrated in operation (806).

[0143] For example, the UE transmits an RLF-report message to a target BS (e.g., BS (602b) as illustrated and exemplified in FIG. 6). In some embodiments of the present application, the RLF-report message may include at least one of the following new information:

[0144] a) A new indicator regarding the successful completion of the DAPS handover procedure. For example, the indicator may be set to "Successful DAPS Handover". This new indicator indicates that the DAPS handover procedure was successfully completed rather than "Failure". Otherwise, the network considers that a handover failure occurred during the DAPS handover procedure.

[0145] b) Previous cell identifier (ID), i.e., the cell ID of the source cell.

[0146] c) Connection failure type. The connection failure type is configured as RLF in the source.

[0147] d) Cause for the RLF in the source link. This cause can be set to one of the following:

[0148] (1) Expiration of physical layer problem timer;

[0149] (2) Problems with random access procedures;

[0150] (3) Reached the maximum number of retransmissions;

[0151] (4) Failure of the beam failure recovery procedure;

[0152] (5) Expiration of a timer to initiate failure recovery based on triggering a measurement report;

[0153] (6) Reception of backhaul (BH) RLF indication; and

[0154] (7) LBT failure for source link.

[0155] For example, an RLF-report message may contain the cause of the RLF on the source link, which is one of t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, t312-Expiry, receipt of BH RLF indication, and mcg-lbtFailure, as specified in 3GPP standard documents.

[0156] FIG. 9 illustrates an additional exemplary signal transmission procedure according to some embodiments of the present application.

[0157] As illustrated in FIG. 9, in operation (901), the target BS (e.g., BS (602b) illustrated and shown in FIG. 6) transmits a message associated with a failure to the MCG to the source BS (e.g., BS (602a) illustrated and shown in FIG. 6). The source BS controls the original serving cell of the UE (e.g., UE (101a) illustrated and shown in FIG. 1). The target BS controls the target cell of the UE.

[0158] For example, the target BS sends a failure indication message to the source BS. This failure indication message is transmitted by the target BS to indicate the receipt of an RLF report from a UE that experienced a connection failure or an attempt to re-establish RRC at the source BS. The purpose of transmitting the failure indication message is to convey information regarding RRC re-establishment attempts or received RLF reports among NG-RAN nodes. Signaling occurs from the target BS where the re-establishment attempt is made or the RLF report is received to the source BS to which the relevant UE may have previously attached prior to the connection failure. This can help detect RLF.

[0159] The failure indication message in operation (901) may be a FAILURE INDICATION message as specified in 3GPP standard documents. The FAILURE INDICATION message may be transmitted by the Xn interface or the X2 interface.

[0160] In particular, FAILURE INDICATION messages as specified in 3GPP standard document TS 38.423

[16] may include the following IEs or group names: Message Type, CHOICE Initiating condition, RRC Reestab, Failure Cell PCI, Reestablishment Cell CGI, C-RNTI; shortMAC-I (optionally), UE RLF Report Container (optionally), RRC Setup, and UE RLF Report Container.

[0161] A failure indication message transmitted from the target BS to the source BS is associated with an RLF report transmitted from the UE in operation (701) as exemplified and illustrated in FIG. 7. For example, the failure indication message includes a container of an RLF report. The container of the RLF report may be transmitted by the Xn interface or the X2 interface.

[0162] FIG. 10 illustrates an additional flowchart of a method for a failure indication procedure according to some embodiments of the present application. The method (1000) illustrated in FIG. 10 may be performed by a target BS (e.g., the BS (602b) illustrated and depicted in FIG. 6 and the target BS illustrated and depicted in FIG. 9).

[0163] As illustrated in FIG. 10, in operation (1002), the target BS transmits a UE information request. In operation (1004), the target BS receives a UE information response containing an RLF report. The RLF report contains information regarding the RLF of the source link to the MCG during the DAPS handover procedure. In an embodiment of the present application, the RLF report may include at least one of the following: an indication of the successful completion of the DAPS handover procedure; a cell identifier (ID) of the source cell; a type of connection failure; and a cause for the RLF of the source link. The type of connection failure may be configured as an RLF at the source.

[0164] In operation (1006), the target BS transmits a failure indication. The failure indication may include an IE regarding the successful completion of the DAPS handover procedure. For example, the failure indication includes an indication set as "successful DAPS handover".

[0165] In some embodiments of the present application, a failure indication transmitted in operation (1004) may include at least one of the following IEs: a cell ID of a source cell, a cell ID of a target cell, a cause for an RLF of a source link, a container including an RLF-reported IE reported from a UE, and a cell radio network temporary identifier (C-RNTI) at the source.

[0166] In some embodiments of the present application, the cause for the RLF of the source link in the failure indication comprises at least one of the following:

[0167] a) Expiration of physical layer problem timer;

[0168] b) Problems with random access procedures;

[0169] c) Reaching the maximum number of retransmissions in Radio Link Control (RLC);

[0170] d) Failure of the beam failure recovery procedure;

[0171] e) Expiration of a timer to initiate failure recovery based on triggering a measurement report;

[0172] f) Reception of BH RLF indication; and

[0173] g) Failure of Listen-Before-Talk (LBT) for the source link

[0174] In some embodiments of the present application, the cell ID of the target cell in the failure indication is a physical cell identifier (PCI) or an evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (ECGI).

[0175] The following text describes a specific embodiment 3 of the method as illustrated and exemplified in FIGS. 7 to 10 for solving the above problems.

[0176] According to Example 3, the UE (e.g., UE (601a) as illustrated and exemplified in FIG. 6) and the target BS (e.g., BS (602b) as illustrated and exemplified in FIG. 6) perform the following operations:

[0177] (1) While the UE is performing the DAPS handover procedure, an RLF may occur from the source. After the DAPS handover procedure is successfully completed, the UE accesses the target cell.

[0178] (2) The UE transmits the rlf-InfoAvailable indication to the target BS.

[0179] (3) After receiving a signal from the UE, the target BS sends a request for UE information to the UE.

[0180] (4) After receiving a UE information request from the target BS, the UE sends a UE information response to the target BS that includes an RLF report. The RLF report may include the following:

[0181] ● New indication, e.g., successful DAPS handover procedure.

[0182] ● Previous cell ID that can be set as the source cell.

[0183] ● Connection failure type that can be set as RLF in the source.

[0184] ● RLF cause for source, which can be set to one of t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, t312-Expiry, reception of BH RLF indication, and mcg-lbtFailure.

[0185] (5) After receiving a UE information response containing an RLF report from the UE, the target BS will send a failure indication to the source BS.

[0186] - The failure indicator may include a new IE set as "Successful DAPS Handover". The sub-IE of the new IE "Successful DAPS Handover" may be one of the following:

[0187] ● Source cell ID;

[0188] ● Target cell ID, e.g., PCI or ECGI;

[0189] ● Selective RLF Causes;

[0190] ● C-RNTI in the source; and

[0191] ● UE RLF-Report Container.

[0192] The details described in all other embodiments of the present application (e.g., details of the RLF reporting mechanism for MCG and the method for resolving the coexistence problem of the DAPS handover procedure) are applicable to the embodiments of FIGS. 7 through 10. Furthermore, the details described in the embodiments of FIGS. 7 through 10 are applicable to all embodiments of FIGS. 1 through 6 and FIG. 11.

[0193] FIG. 11 illustrates a simplified block diagram of an apparatus (1100) for an enhanced failure reporting mechanism according to some embodiments of the present application.

[0194] In some embodiments, the device (1100) may be a UE (101) as shown in FIG. 1 or a UE (601a) as shown and illustrated in FIG. 6.

[0195] In some other embodiments, the device (1100) may be a target BS, for example, the BS (602b) illustrated and depicted in FIG. 6.

[0196] Referring to FIG. 11, the device (1100) may include at least one non-transient computer-readable medium (1102), at least one receiving circuit (1104), at least one transmitting circuit (1106), and at least one processor (1108). In some embodiments of the present application, at least one receiving circuit (1104) and at least one transmitting circuit (1106) are integrated into at least one transceiver. At least one non-transient computer-readable medium (1102) may store computer-executable instructions. At least one processor (1108) may be coupled to at least one non-transient computer-readable medium (1102), at least one receiving circuit (1104), and at least one transmitting circuit (1106). Computer-executable instructions may be programmed to implement a method with at least one receiving circuit (1104), at least one transmitting circuit (1106), and at least one processor (1108). The method may be a method according to an embodiment of the present application, for example, a corresponding method illustrated in FIG. 5a, FIG. 5b, FIG. 8, or FIG. 10.

[0197] The method according to the embodiments of the present application may also be implemented on a programmed processor. However, controllers, flowcharts, and modules may also be implemented on a general-purpose or special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, hardware electronic or logic circuits such as integrated circuits, discrete element circuits, programmable logic devices, etc. In general, any device inhabited by a finite state machine capable of implementing the flowcharts illustrated in the drawings may be used to implement the processor functions of the present application. For example, the embodiments of the present application provide an apparatus for recognizing emotions from speech, comprising a processor and memory. Computer programmable instructions for implementing the method for recognizing emotions from speech are stored in memory, and the processor is configured to execute computer programmable instructions to implement the method for recognizing emotions from speech. The method may be the method described above or other methods according to the embodiments of the present application.

[0198] Alternative embodiments preferably implement the methods according to the embodiments of the present application in a non-transient, computer-readable storage medium storing computer-programmable instructions. The instructions are preferably executed by computer-executable components preferably integrated with a network security system. The non-transient, computer-readable storage medium may be stored on any suitable computer-readable medium, such as RAMs, ROMs, flash memory, EEPROMs, optical storage devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a processor, but the instructions may alternatively or additionally be executed by any suitable dedicated hardware device. For example, embodiments of the present application provide a non-transient, computer-readable storage medium in which computer-programmable instructions are stored. The computer-programmable instructions are configured to implement a method for recognizing emotions from speech as described above or other methods according to the embodiments of the present application.

[0199] Although this application has been described by its specific embodiments, it is evident that many alternatives, modifications, and variations may be apparent to those skilled in the art. For example, various components of the embodiments may be interchangeable, added, or substituted in other embodiments. Furthermore, not all elements of each drawing are necessary for the operation of the disclosed embodiments. For example, those skilled in the art of the disclosed embodiments may make and utilize the teachings of this application simply by utilizing the elements of the independent claims. Accordingly, the embodiments of this application as disclosed herein are intended to be illustrative rather than restrictive. Various modifications may be made without departing from the spirit and scope of this application.

Claims

Claim 1 delete Claim 2 delete Claim 3 delete Claim 4 delete Claim 5 delete Claim 6 delete Claim 7 delete Claim 8 delete Claim 9 A method comprising: receiving a radio resource control (RRC) reconfiguration message including a reconfiguration having synchronization information elements (IE) and dual active protocol stack (DAPS) configuration information; performing a DAPS handover procedure; and transmitting an RLF report associated with the RLF after successfully completing the DAPS handover procedure in response to a radio link failure (RLF) of a source link to a master cell group (MCG) during the DAPS handover procedure. Claim 10 In claim 9, the method wherein the RLF report comprises at least one of: an indication of the successful completion of the DAPS handover procedure; a cell identifier (ID) of the source cell; a type of connection failure; and a cause for the RLF of the source link. Claim 11 In Clause 10, the above connection failure type is configured as RLF in the source, a method. Claim 12 In paragraph 10, the cause of the RLF of the source link comprises at least one of: expiration of a physical layer problem timer; a problem with a random access procedure; reaching a maximum number of retransmissions; failure of a beam failure recovery procedure; expiration of a timer for initiating failure recovery based on triggering a measurement report; reception of a backhaul (BH) RLF indication; and failure of a listen-before-talk (LBT) for the source link. Claim 13 A method comprising: transmitting a request for user equipment (UE) information; receiving a UE information response including a radio link failure (RLF) report, wherein the RLF report includes information regarding a radio link failure (RLF) of a source link to a master cell group (MCG) during a dual active protocol stack (DAPS) handover procedure; and transmitting a failure indication, wherein the failure indication includes an information element (IE) regarding the successful completion of the DAPS handover procedure. Claim 14 In paragraph 13, the method wherein the RLF report comprises at least one of: an indication of the successful completion of the DAPS handover procedure; a cell identifier (ID) of the source cell; a type of connection failure; and a cause for the RLF of the source link. Claim 15 In paragraph 13, the failure indication comprises at least one of: a cell identifier (ID) of a source cell; a cell identifier (ID) of a target cell; a cause for the RLF of the source link; a container including an RLF-reported IE reported from the UE; and a cell radio network temporary identifier (C-RNTI) in the source. Claim 16 A method according to claim 14 or 15, wherein the cause of the RLF of the source link comprises at least one of: expiration of a physical layer problem timer; a problem with a random access procedure; reaching a maximum number of retransmissions on radio link control (RLC); failure of a beam failure recovery procedure; expiration of a timer for initiating failure recovery based on triggering a measurement report; reception of a backhaul (BH) RLF indication; and failure of a listen-before-talk (LBT) for the source link. Claim 17 In paragraph 15, the cell ID of the target cell is one of a physical cell identifier (PCI); and an evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (ECGI). Claim 18 delete Claim 19 delete Claim 20 A device comprising: at least one non-transient computer-readable medium storing computer-executable instructions; at least one receiving circuit; at least one transmitting circuit; and at least one processor coupled to the at least one non-transient computer-readable medium, the at least one receiving circuit and the at least one transmitting circuit, wherein the computer-executable instructions enable the at least one processor to implement the method of any one of claims 9 to 12. Claim 21 A device comprising: at least one non-transient computer-readable medium storing computer-executable instructions; at least one receiving circuit; at least one transmitting circuit; and at least one processor coupled to the at least one non-transient computer-readable medium, the at least one receiving circuit and the at least one transmitting circuit, wherein the computer-executable instructions enable the at least one processor to implement the method of any one of claims 13 through 15 and 17.

Images