Method and apparatus for primary cell group

Abstract

Embodiments of the present application relate to a method and apparatus for a master cell group, for example, a dual active protocol stack (DAPS) handover process under a third generation partnership project (3GPP) 5G new radio (NR) system and a radio link failure (RLF) reporting mechanism associated with a source link during the DAPS handover process. According to an embodiment of the present application, a method may include: receiving configuration information including a timer associated with fast MCG link recovery; receiving a radio resource control (RRC) reconfiguration message including DAPS configuration information; in response to RLF of a source link for the MCG, initiating an MCG failure information process based on a condition of whether the timer for handover is running. In addition, an RLF report may be reported to the target cell after the UE successfully accesses the target cell.

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technology, and more particularly to methods and apparatus for a master cell group (MCG), for example, for a dual active protocol stack (DAPS) handover process and a radio link failure (RLF) reporting mechanism associated with a source link for the MCG during the DAPS handover process. Background Art

[0002] When a radio link failure (RLF) or handover failure (HOF) occurs to a user equipment (UE), the UE may perform a radio resource control (RRC) reestablishment procedure. The UE may access a cell through a successful RRC reestablishment procedure, or access a cell through a connection establishment procedure in response to an unsuccessful RRC reestablishment 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 transmit a failure report to the network.

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

[0004] Currently, in 3GPP 5G New Radio (NR) systems or similar, the details of how to solve the coexistence problem of the DAPS handover process of MCG and the RLF reporting mechanism have not been clearly discussed. Summary of the invention

[0005] Some embodiments of the present application provide a method for wireless communication. The method may be performed by a UE. The method includes: receiving configuration information including a timer associated with a 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 process; starting a timer for handover; in response to a radio link failure (RLF) of a source link for an MCG during the DAPS handover process, when the timer for handover is running, initiating an MCG failure information process; and starting the timer associated with a fast MCG link recovery.

[0006] Some embodiments of the present application also provide a device for wireless communication. The device includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above method performed by the UE.

[0007] Some embodiments of the present application provide a further method for wireless communication. The method may be performed by a UE. The method includes: receiving configuration information including a timer associated with a fast master cell group (MCG) link recovery; and in response to a radio link failure (RLF) of a source link for the MCG during a dual active protocol stack (DAPS) handover process, when the timer associated with the fast MCG link recovery is not running and the timer for handover is not running, initiating an MCG failure information process.

[0008] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above-mentioned further method performed by the UE.

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

[0010] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above-mentioned further method performed by the UE.

[0011] Some embodiments of the present application provide a further method for wireless communication. The method may be performed by a BS. The method includes: transmitting a user equipment (UE) information request; receiving a UE information response including a radio link failure (RLF) report, wherein the RLF report includes information related to a radio link failure (RLF) of a source link for 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 successful completion of the DAPS handover procedure.

[0012] Some embodiments of the present application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium having computer-executable instructions stored thereon; a receiving circuit system; a transmitting circuit system; and a processor coupled to the non-transitory computer-readable medium, the receiving circuit system, and the transmitting circuit system, wherein the computer-executable instructions cause the processor to implement the above-mentioned further method performed by the BS.

[0013] The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented by reference to specific embodiments of the present application illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered limiting of its scope.

[0015] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application;

[0016] Figure 2 An exemplary flow chart illustrating a fault information process according to some embodiments of the present application;

[0017] Figure 3 An exemplary flow chart illustrating a handover process within an AMF (Access and Mobility Management Function) according to some embodiments of the present application;

[0018] Figure 4 An exemplary timeline illustrating RLF with a fast MCG link recovery procedure according to some embodiments of the present application;

[0019] Figure 5A A flowchart illustrating a method for a DAPS handover process according to some embodiments of the present application;

[0020] Figure 5BA flowchart illustrating a method for MCG fault information processing according to some embodiments of the present application;

[0021] Figure 6 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application;

[0022] Figure 7 Describe an exemplary signal transmission process according to some embodiments of the present application;

[0023] Figure 8 A flowchart illustrating a method for a fault reporting process according to some embodiments of the present application;

[0024] Fig. 9 Describe further exemplary signal transmission processes according to some embodiments of the present application;

[0025] Fig.10 a further flow chart illustrating a method for a fault indication process according to some embodiments of the present application; and

[0026] Fig.11 A simplified block diagram illustrating an apparatus 1100 for an enhanced fault reporting mechanism according to some embodiments of the present application. DETAILED DESCRIPTION

[0027] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application, and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be implemented by different embodiments intended to be included in the spirit and scope of the present application.

[0028] 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, embodiments are provided in specific network architectures and new service scenarios, such as 3GPP 5G, 3GPP LTE Release 8, etc. It is considered that, with the development of network architectures and new service scenarios, all embodiments in the present application are also applicable to similar technical problems; and in addition, the terms cited in the present application may change, which should not affect the principles of the present application.

[0029] The next generation radio access network (NG-RAN) supports multi-radio dual connectivity (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 a non-ideal backhaul. One of the nodes can provide NR access, and the other node can provide Evolved 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 the SN are connected via a network interface (e.g., an Xn interface specified in a 3GPP standard document), and at least the MN is connected to the core network.

[0030] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0031] like Figure 1 As shown in FIG. 1 , the wireless communication system 100 may be a dual-connectivity system 100, which includes at least one UE 101, at least one MN 102, and at least one SN 103. Specifically, for illustrative purposes, Figure 1 The dual-connectivity system 100 in FIG. 1 includes a UE 101, a MN 102, and a SN 103. Figure 1 A specific number of UE 101, MN 102, and SN 103 are depicted in the figure, but it is contemplated that any number of UE 101, MN 102, and SN 103 may be included in the wireless communication system 100.

[0032] refer to Figure 1 UE 101 may be connected to MN 102 and SN 103 via a network interface (e.g., a Uu interface specified in a 3GPP standard document). MN 102 and SN 103 may be connected to each other via a network interface (e.g., an Xn interface specified in a 3GPP standard document). MN 102 may be connected to SN 103 via a network interface (e.g., an Xn interface specified in a 3GPP standard document). Figure 1 UE 102 may be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

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

[0034] MN 102 may be associated with an MCG. MCG may refer to a set of serving cells associated with MN 102 and may include a primary cell (PCell) and optionally one or more secondary cells (SCells) of the MCG. PCell may provide control plane connectivity to UE 101.

[0035] SN 103 may refer to a radio access node that does not have a control plane connection to the core network but provides additional resources to 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 a NE-DC scenario, SN 103 may be an ng-eNB. In yet another embodiment of the present application, in an NR-DC scenario or a NGEN-DC scenario, SN 103 may be a gNB.

[0036] SN 103 may be associated with a secondary cell group (SCG). 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 (SCells).

[0037] The PCell of MCG and the PSCell of SCG can also be called special cells (SpCell).

[0038] In some embodiments of the present application, 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 TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, and a modem), etc. In some other embodiments of the present application, UE 101 may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a subscriber identity module, a personal computer, a selective call receiving circuit system, or any other device capable of sending and receiving communication signals on a wireless network. In some other embodiments of the present application, UE 101 may include a wearable device, such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, UE 101 may be referred to as a subscriber unit, a mobile device, 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 described using other terms used in the art.

[0039] Figure 2 An exemplary flow chart illustrating a fault information process according to some embodiments of the present application. The fault information process may be referred to as a fault information reporting process. Figure 2 Embodiments include the following embodiments of the SCG fault information process or the MCG fault information process.

[0040] Specifically, in some embodiments of the SCG fault information process, Figure 2 In operation 201 shown in FIG. 1 , UE 101 and MN 102 may communicate RRC reconfiguration information. Figure 2 In operation 202 shown in FIG. 1 , UE 101 may initiate an SCG failure information process and transmit a message associated with a failure of the SCG to MN 102. The message associated with the failure of the SCG in operation 202 may be an SCGFailureInformation message specified in a 3GPP standard document. MN 102 may then process 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 Figure 1 SN 103 shown and described in .

[0041] In the above-described embodiment of the SCG Failure Information procedure, UE 101 may initiate the SCG Failure Information procedure to report a failure of the SCG when one of the following conditions is met:

[0042] When a failure of the SCG is detected. For example, the failure of the SCG may refer to a RLF occurring in the PSCell of the SCG.

[0043] During reconfiguration with synchronization failure of the SCG.

[0044] When the SCG configuration fails.

[0045] • Upon integrity check failure indication on Signalling Radio Bearer (SRB) 3 from lower layers of the SCG.

[0046] In 3GPP Release 16, a fast MCG link recovery procedure is introduced for the MR-DC scenario. The fast MCG link recovery procedure may also be referred to as the MCG fault information procedure. The purpose of this procedure is to notify the MN of the RLF of the MCG via the SN connected to the UE, so that the UE in the RRC_CONNECTED state can initiate a fast MCG link recovery procedure to quickly continue the RRC connection without performing a reestablishment procedure.

[0047] In this application Figure 2 In some other embodiments, in the event of a failure of the MCG, the UE 101 may initiate (or trigger) a fast MCG link recovery procedure, ie, an MCG failure information procedure.

[0048] Specifically, in some embodiments of the MCG fault information process, such as Figure 2As shown in FIG. 2 , in operation 201, UE 101 and MN 102 may communicate RRC reconfiguration information. In operation 202, UE 101 may initiate an MCG failure information process and transmit a message associated with a failure of the MCG to MN 102. For example, the failure of the MCG may refer to an RLF occurring in a PCell of the MCG. The message associated with the failure of the MCG in operation 202 may be an MCGFailureInformation message specified in a 3GPP standard document.

[0049] In an embodiment of the MCG Failure Information procedure, UE 101 may not directly transmit a message associated with the failure of the MCG to MN 102. Instead, UE 102 may transmit a message associated with the failure of the MCG to the SN (e.g., Figure 1 SN 103 shown and described in ), and then the SN can transmit the message received from UE 101 to MN 102.

[0050] For example, UE 101 may be configured with a split SRB1 or SRB3 to report MCG failure information when a failure of the MCG occurs. In the case where a split SRB1 is configured, UE 101 may submit a MCGFailureInformation message to a lower layer, for example, for transmission via SRB1. In the case where SRB3 is configured, UE 101 may submit a MCGFailureInformation message to a lower layer for transmission via SRB3. For example, the MCGFailureInformation message may be embedded in an NR RRC message ULInformationTransferMRDC as specified in a 3GPP standard document for transmission via SRB3.

[0051] When or after transmitting the message in operation 202, UE 101 may start a timer associated with the fast MCG link recovery procedure. In an embodiment of the present application, the timer associated with the fast MCG link recovery procedure may be T316 as specified in the 3GPP standard document.

[0052] After receiving the message associated with the 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, including a handover (HO) command of 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 a 3GPP standard document. The MN 102 may not directly transmit the response message to the UE 101. Instead, the MN 102 may transmit the response message to the SN (e.g., Figure 1SN 103 shown and described in ), and then the SN can transmit a response message to UE 101.

[0053] In the case where SRB3 is configured for transmitting messages associated with the failure of the MCG, after receiving the response message from MN 102, SN 103 may encapsulate the response message in a DLInformationTransferMRDC message as specified in the 3GPP standard document, and then transmit the DLInformationTransferMRDC message to UE 101.

[0054] In the above embodiment of the MCG Failure Information procedure, UE 101 may set the MCG failure type (referred to as "failureType") as follows:

[0055] If UE 101 initiates transmission of the MCGFailureInformation message as shown in operation 202, due to expiration of timer T310 (which may be referred to as a physical layer problem timer) as specified in the 3GPP standard document, UE 101 sets failureType to t310-Expiry as specified in the 3GPP standard document.

[0056] • If UE 101 initiates transmission of MCGFailureInformation message as shown in operation 202 to provide a random access problem indication from the medium access control (MAC) layer of the MCG, then UE 101 sets failureType to randomAccessProblem as specified in the 3GPP standard document.

[0057] • If UE 101 initiates transmission of a MCGFailureInformation message as shown in operation 202 to provide an indication from the MCG Radio Link Control (RLC) that the maximum number of retransmissions has been reached, then UE 101 sets failureType to rlc-MaxNumRetx as specified in the 3GPP standard documents.

[0058] In the case of 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 transmit uplink user data to the source BS until the random access procedure to the target BS is successfully completed. When the DAPS handover procedure fails, if the source link has not been released, the UE may report the DAPS handover (HO) failure via the source BS without triggering the RRC connection reestablishment procedure.

[0059] In the control plane handling of the handover associated with the DAPS handover procedure, messages are exchanged directly between the BSs. Specific examples are shown below. Figure 3 Displayed in.

[0060] Figure 3 An exemplary flow chart illustrating the intra-AMF handover process according to some embodiments of the present application. Figure 3 The embodiments depict a basic condition handover scenario in which neither the Access and Mobility Management Function (AMF) nor the User Plane Function (UPF) is changed.

[0061] refer to Figure 3 In operation 301, the source BS may transmit measurement configuration information to the UE. The UE may report a measurement result to the source BS based on the measurement configuration information. In operation 302, the source BS may decide to hand over the UE based on the measurement result reported by the UE.

[0062] The source BS may transmit a HANDOVER REQUEST message to the target BS in operation 303. For example, the HANDOVER REQUEST message may transfer a transparent RRC container having information necessary to prepare a handover procedure at the target BS side.

[0063] In operation 304, the target BS may perform admission control based on a load of a target cell of the target BS to decide whether to allow a handover procedure of the UE after receiving the handover request message from the source BS.

[0064] In operation 305, based on the admission control result, the target BS may prepare handover resources for the UE and send a HANDOVER REQUEST ACKNOWLEDGE including an RRC reconfiguration message to the source BS.

[0065] In operation 306, RAN handover initiation is performed. The source BS may transmit an RRC reconfiguration message to the UE. The RRC reconfiguration message may include a reconfiguration with a synchronization information element (IE). The RRC reconfiguration message may contain information required to access a target cell of the target BS.

[0066] In operation 307, the source BS may transmit an SN STATUS TRANSFER message to the target BS.

[0067] In operation 308, the UE may access the target cell and complete the handover process by sending an RRCReconfigurationComplete message to the target BS. In some embodiments of implementing the DAPS handover process, the UE does not detach from the source cell upon receiving the RRCReconfiguration message. For example, the UE may release the source resources upon receiving an explicit release indication from the target BS.

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

[0069] In operation 310, the 5GC network may switch the DL data path to the target BS. The UPF may send one or more "end marker" packets to the source BS on the old (source) data path according to the packet data unit (PDU) session or PDU tunnel. The UPF may then release any user plane or transport network layer (TNL) resources to the source BS.

[0070] In operation 311, the AMF may acknowledge the PATHSWITCH REQUEST message using a PATH SWITCH REQUEST ACKNOWLEDGE message.

[0071] In operation 312, in response to receiving the 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 process. The source BS may then release the radio and control plane related resources associated with the UE context. Any ongoing data forwarding may continue.

[0072] Figure 4 An exemplary timeline illustrating RLF with a fast MCG link recovery procedure according to some embodiments of the present application. Figure 4 Embodiments of the present invention may be implemented by a UE (e.g., Figure 1 Executed by UE 101 shown and described in .

[0073] like Figure 4 As shown in FIG. 1 , the UE first performs data transmission in the normal operation phase. For example, if the MAC layer of the UE receives N310 continuous out-of-sync indication from the physical layer of the UE (which means that a radio link problem occurs), the UE detects a radio link problem. Then, the UE starts a timer, for example, timer T310 specified in the 3GPP standard document. During the period of timer T310, if the MAC layer of the UE receives N311 continuous in-sync indication from the physical layer (which means that the UE is successfully connected to the network), the UE may stop timer T310.

[0074] When the timer T310 expires (which means there is no recovery during the timer T310), the UE initiates the fast MCG link recovery procedure. Specifically, the UE initiates the fast MCG link recovery procedure via the SN (e.g., Figure 1 SN103) as shown and described in the figure transmits the MCG fault information to the MN (e.g., Figure 1 MN 102 shown and described in FIG. 1 ), and starts timer T316 as specified in the 3GPP standard document, such as Figure 4 As shown in . If the UE receives the RRC reconfiguration from the MN via the SN, the UE stops the timer T316, which means that the fast MCG link recovery process is terminated. Otherwise, in response to the expiration of the timer T316 (which means that there is no recovery during the timer T316), the UE performs the RRC reestablishment process and starts the timer T311 as specified in the 3GPP standard document for cell selection.

[0075] If the timer T311 expires (which means that there is no recovery during the timer T311), the UE returns to the idle state, for example, the RRC_IDLE state. Before the timer T311 expires, the UE is in the RRC_CONNECTED state, for example. Figure 4 After the timer T311 expires, the UE enters the RRC_IDLE state. Figure 4 As shown in .

[0076] about Figure 4 The above description of the embodiments does not take into account timer T312. Some embodiments assume that timer T312 specified in the 3GPP standard document is configured. In these embodiments, if timer T310 is running and triggers a measurement report for a measurement identifier for which timer T312 has been configured, the UE will start timer T312. After timer T312 expires, the UE may declare a failure and trigger a failure recovery procedure, such as a fast MCG link recovery procedure that has been configured.

[0077] The embodiment of the present application provides a coexistence scenario of the DAPS handover process and the RLF reporting mechanism for MCG. More details about the embodiment of the present application will be described below in conjunction with the accompanying drawings.

[0078] Embodiments of the present application can solve the following problems: (1) how to handle the situation where RLF occurs on the source link of the MCG when the UE is performing a DAPS handover procedure and the fast MCG link recovery procedure is configured for the UE; and (2) how to handle the situation where the UE receives a response from the MN via the SN when the timer associated with the fast MCG link recovery is running and the DAPS handover procedure is in progress. Specific examples are in Figure 5A and 5B Describe and show in.

[0079] Figure 5A A flow chart illustrating a method for a DAPS handover procedure according to some embodiments of the present application.

[0080] like Figure 5A The method 500A shown in FIG. 5 may be performed by a UE (eg, Figure 1 and 2 For example, the UE may be configured with a DC, wherein the UE is connected to a MN (e.g., Figure 1 and 2 MN 102) and SN 103 (e.g., as shown and described in Figure 1 SN 103 shown and described therein).

[0081] exist Figure 5A In an embodiment, when the UE is performing a DAPS handover process, the UE may be allowed to initiate or trigger a fast MCG link recovery process (eg, an MCG failure information process).

[0082] In one example, if the fast MCG link recovery process is triggered when the UE is performing a DAPS handover process (e.g., timer T316 is running), the UE may report MCG failure information to the source MN via the SN. The source MN may transmit an RRC reconfiguration message containing a handover command or a release message to the UE. In this case, if the DAPS handover process is in progress, the UE should not trigger the RRC connection reestablishment process when the timer associated with the fast MCG link recovery (e.g., timer T316) expires.

[0083] In a further example, if a timer for handover is triggered (eg, timer T304 is running), the UE does not initiate the RRC connection reestablishment procedure after a timer associated with fast MCG link recovery (eg, timer T316) expires.

[0084] In another example, if a timer for handover is not triggered (eg, timer T304 is not running), the UE may initiate the RRC connection reestablishment procedure after a timer associated with fast MCG link recovery (eg, timer T316) expires.

[0085] Specifically, if Figure 5A As shown in FIG. 5 , in operation 501, the UE may receive configuration information including a timer associated with fast MCG link recovery. For example, the timer associated with fast MCG link recovery may be timer T316 as specified in the 3GPP standard document.

[0086] 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.

[0087] In operation 507, the UE may start a timer for handover. The timer value of the timer for handover may be included in the reconfiguration with synchronization IE. In an embodiment of the present application, the timer for handover is the timer T304 specified in the 3GPP standard document.

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

[0089] 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 or after transmitting the MCG failure information message, if a timer associated with fast MCG link recovery expires, the UE may not initiate an RRC connection reestablishment procedure when performing a DAPS handover procedure.

[0090] The UE may receive another RRC reconfiguration message while or after transmitting the MCG Failure Information message. For example, the UE may receive this RRC reconfiguration message after transmitting the MCG Failure Information message. The UE may receive this RRC reconfiguration message while a timer associated with fast MCG link recovery is running. For example, this RRC reconfiguration message may include a reconfiguration with synchronization IE. The reconfiguration with synchronization IE may be a reconfigurationWithSync IE as specified in a 3GPP standard document.

[0091] In one example, after receiving the above-mentioned another RRC reconfiguration message, the UE may perform reconfiguration with synchronization process, and the UE may stop performing the ongoing DAPS handover process. In another example, after receiving the above-mentioned another RRC reconfiguration message, the UE may ignore this RRC reconfiguration message, but continue to perform the ongoing DAPS handover process.

[0092] 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 when a timer associated with fast MCG link recovery is running. After receiving the RRC release message, the UE may release resources associated with the source link on which the RLF occurs and continue to perform the DAPS handover process. Alternatively, the UE may ignore the RRC release message and continue to perform the DAPS handover process.

[0093] The following text describes how to solve the above problems Figure 5ASpecific embodiment 1 of the method shown and described therein.

[0094] According to embodiment 1, a UE (e.g. Figure 1 and 2 The UE 101 shown and described in FIG. 1 performs the following operations:

[0095] (1) UE accesses the network via DC operation.

[0096] • Configuration for MCG and SCG may be configured to the UE.

[0097] • Fast MCG link recovery procedure, for example, the value of timer T316 may be configured to the UE.

[0098] (2) The UE reports the measurement results to the network (eg, PCell or PSCell).

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

[0100] (4) The target BS prepares handover resources for the UE and sends a HANDOVER REQUESTACKNOWLEDGE message containing an RRC reconfiguration message to the source BS.

[0101] (5) The source BS sends an RRC reconfiguration message including the ReconfigurationWithSync IE to the UE. The message contains the information required for accessing the target cell of the target BS.

[0102] ·This operation of BS is the same as Figure 3 The RRC reconfiguration message including the reconfigurationWithSync IE may be used for mobility purposes. For example, the RRC reconfiguration message including the reconfigurationWithSync IE may be used for a normal handover procedure, a conditional handover procedure, a DAPS handover procedure, and / or a PScell ​​change procedure.

[0103] • Configuration information for the DAPS handover procedure (eg, dapsConfig as specified in 3GPP standard documents) may be configured for a data radio bearer (DRB).

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

[0105] In case of DAPS handover procedure, the UE does not detach from the source cell upon receiving the RRC reconfiguration message. The UE continues to monitor the source cell.

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

[0107] (8) The UE transmits the MCG Failure Information message to the MN via the SN and starts the timer T316.

[0108] (9) UE takes different actions in different scenarios:

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

[0110] -If the UE receives an RRC reconfiguration message containing the reconfigurationWithSync IE:

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

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

[0113] - If the UE receives an RRC Release message:

[0114] Option B-1: The UE may release the source connection and continue the ongoing DAPS handover procedure.

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

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

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

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

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

[0120] Figure 5B A flowchart illustrating a method for MCG fault information processing according to some embodiments of the present application. Figure 5B The method 500B shown in FIG. 5 may be performed by a UE (eg, Figure 1 and 2 101) shown and described in FIG. 101). The UE may be configured with a DC, wherein the UE is connected to a MN (e.g., Figure 1 and 2MN 102) and SN 103 (e.g., as shown and described in Figure 1 SN 103 shown and described therein).

[0121] exist Figure 5B In an embodiment, when the UE is performing a DAPS handover process, the UE may not be allowed to initiate or trigger a fast MCG link recovery process (e.g., an MCG fault information process). Under certain conditions, the UE may initiate or trigger a fast MCG link recovery process (e.g., an MCG fault information process).

[0122] like Figure 5B , in operation 502, the UE may receive configuration information including a timer associated with fast MCG link recovery, for example, timer T316 as specified in the 3GPP standard document. In operation 504, if RLF occurs on the source link for MCG during the DAPS handover process, the UE may initiate the MCG Failure Information process when the timer associated with fast MCG link recovery (e.g., timer T316) is not running and the timer for handover is not running.

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

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

[0125] The following text describes how to solve the above problems Figure 5B Specific embodiment 2 of the method shown and described therein.

[0126] According to Embodiment 2, a UE (e.g. Figure 1 and 2 UE 101) and MN (e.g., Figure 1 and 2 The MN 102 shown and described in FIG. 100 ) performs the following operations:

[0127] (1) UE accesses the network via DC operation.

[0128] • Configuration for MCG and SCG may be configured to the UE.

[0129] • The fast MCG link recovery procedure (eg, the value of timer T316) may be configured to the UE.

[0130] (2) The UE detects RLF in the source link for the MCG (eg, Pcell).

[0131] (3) UE takes different actions in different scenarios:

[0132] • Upon detecting RLF of an MCG, if timer T316 is not running and timer T304 is not running, the UE may initiate the MCG Failure Information procedure.

[0133] • Upon detecting RLF of an MCG, if timer T316 is not running and DAPS configuration is not configured for any DRB, the UE may initiate the MCG Failure Information procedure.

[0134] • After initiating the MCG Failure Information procedure, the UE may suspend SCG transmission for all signaling radio bearers (SRBs) except signaling radio bearer (SRB) 0 and DRBs.

[0135] (4) The UE transmits the MCG Failure Information message to the MN via the SN and starts the timer T316. The fault type and available measurement results will be included in the MCG Failure Information message.

[0136] (5) After receiving the MCG Failure Information message via the SN, the MN may transmit a response (eg, RRC reconfiguration with reconfigurationWithSync IE) to the UE.

[0137] (6) The UE receives a response (eg, RRC reconfiguration with reconfigurationWithSync IE) from the MN via the SN. The UE may then perform a handover procedure and a synchronization procedure to the target cell.

[0138] The details described in all other embodiments of this application (e.g., details on how to solve the coexistence problem of the DAPS handover process of the MCG and the RLF reporting mechanism) are applicable to Figure 5A and 5B In addition, Figure 5A and 5B The details described in the embodiments apply to Figures 1 to 4 and all embodiments 6 to 11.

[0139] Figure 6 A schematic diagram illustrating a wireless communication system according to some embodiments of the present application.

[0140] like Figure 6 As described and shown in FIG. 6 , the wireless communication system 600 includes at least one user equipment (UE) 601 and at least one base station (BS) 602. Specifically, for illustrative purposes, the wireless communication system 600 includes one UE 601 (e.g., UE 601a) and two BSs 602 (e.g., BS 602a and BS 602b). Figure 6 A specific number of UEs 601 and BSs 602 are depicted in FIG. 6 , but it is contemplated that any number of UEs 601 and BSs 602 may be included in the wireless communication system 600 .

[0141] like Figure 6 The UE 601 shown and described in FIG. Figure 1 101 has similar functions and features as shown and described in . Figure 1 The above description of the embodiments.

[0142] BS 602 may be distributed over a geographic area. In certain embodiments of the present application, each of BS 602 may also be referred to as an access point, an access terminal, a base station, a base unit, a macro cell, a node-B, an evolved node B (eNB), a gNB, an NG-RAN (next generation radio access network) node, a home node-B, a relay node or a device, or described using other terms used in the art. BS 602 is typically part of a radio access network, which may include one or more controllers communicatively coupled to one or more corresponding BS 602. BS 602 may communicate directly with each other. For example, BS 602 may communicate directly with each other via an Xn interface or an X2 interface.

[0143] The wireless communication system 600 may be compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 600 is 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, a long term evolution (LTE) network, a 3GPP-based network, a 3GPP 5G-based network, a satellite communication network, a high altitude platform network, and / or other communication networks.

[0144] In some embodiments of the present application, the wireless communication system 600 is compatible with the 5G NR of the 3GPP protocol, wherein the BS 602 transmits data using an OFDM modulation scheme on the DL, and the UE 601 transmits data using a single carrier frequency division multiple access (SC-FDMA) or OFDM scheme on the UL. However, more generally, the wireless communication system 600 may implement some other open or proprietary communication protocols, such as WiMAX and other protocols.

[0145] In some embodiments of the present application, BS 602 may communicate using other communication protocols, such as the IEEE 802.11 series of wireless communication protocols. Further, in some embodiments of the present application, BS 602 may communicate on a licensed spectrum, while in other embodiments, BS 602 may communicate on an unlicensed spectrum. The present application is not intended to be limited to implementations of any particular wireless communication system architecture or protocol. In still other embodiments of the present application, BS 602 may communicate with UE 601 using 3GPP 5G protocols.

[0146] Each BS 602 may include one or more cells. Each UE 601 may perform a cell selection process between different cells of different BSs. Each UE 601 may be handed over from a serving cell of a source BS to a target cell of a target BS. Figure 6 In the wireless communication system 600 described and shown in FIG. 1 , BS 602a may be used as a source BS and BS 602b may be used as a target BS. If a handover is required, then Figure 6 UE 601a illustrated and shown in FIG. 6A 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 UE 601a may be a CHO procedure.

[0147] Currently, in 3GPP 5G NR systems and the like, radio access operating with shared spectrum channel access may operate in different modes, for example, a mode in which a PCell, a PSCell, or a SCell may be in a shared spectrum, or a mode in which a SCell may be configured or not configured with an uplink. The BS may operate in a dynamic access mode or a semi-static channel access mode as described in 3GPP standard document TS37.213. In both channel access modes, the BS and the UE may apply listen before talk (LBT) before performing transmission on a cell configured with shared spectrum channel access. When LBT is applied, the transmitter listens or senses the channel to determine whether the channel is idle or busy, and performs transmission only when the channel is sensed to be idle.

[0148] When the UE detects a persistent uplink LBT failure, the UE takes actions as specified in the 3GPP standard document TS38.321. Detection is based on each bandwidth part (BWP) and on all uplink transmissions within this BWP. When a persistent uplink LBT failure is detected on an SCell, the UE reports this situation to the corresponding BS (MN of the MCG or SN of the SCG) via a MAC CE on a serving cell different from the SCell where the failure was detected. If no resources are available for transmitting the MAC CE, the UE can transmit a scheduling request (SR). When a persistent uplink LBT failure is detected on the SpCell, the UE switches to another UL BWP with configured RACH resources on the cell, starts RACH, and reports the failure via MAC CE. When multiple UL BWPs are available for switching, which one is selected depends on the UE implementation. For PSCell, if a persistent uplink LBT failure is detected on all UL BWPs with configured RACH resources, the UE declares an SCG RLF and reports the failure to the MN via SCGFailureInformation. For PCell, if uplink LBT failure is detected on all ULBWPs with configured RACH resources, the UE declares RLF.

[0149] Embodiments of the present application can solve the following problems: (1) what additional information should be added to the RLF-report when RLF occurs in the source while the UE is performing a DAPS handover procedure; and (2) what information should be sent to the source cell after the target cell receives the RLF-report from the UE. Figures 7 to 10 Describe and show.

[0150] Figure 7 An exemplary signal transmission process according to some embodiments of the present application is described.

[0151] Specifically, if Figure 7 As shown in FIG. 7 , in operation 701, a UE (e.g., Figure 1 UE101 as described and shown in Figure 6 The UE 601a described and shown in FIG. 6 transmits a message associated with the failure of the MCG to a target BS (eg, Figure 6 BS 602b as described and shown in FIG. 7 ). The target BS controls the target cell of the UE. For example, in operation 701, the message associated with the failure of the MCG may be a RLF-report message as specified in the 3GPP standard document.

[0152] Specifically, the RLF-report message as specified in the 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.

[0153] Figure 8 A flow chart illustrating a method of a fault reporting process according to some embodiments of the present application. Figure 8 The method 800 shown in FIG. 8 may be performed by a UE (eg, Figure 6 Executed by UE 601a) shown and described in .

[0154] like Figure 8 As shown in , in operation 802, the UE may receive an RRC reconfiguration message including a reconfiguration with synchronization IE and DAPS configuration information. In operation 804, the UE may perform a DAPS handover procedure. If the RLF of the source link of the MCG occurs during the DAPS handover procedure, then after successfully completing the DAPS handover procedure, the UE may transmit an RLF report related to the RLF, as shown in operation 806.

[0155] For example, the UE transmits an RLF-report message to the target BS (eg, Figure 6 In some embodiments of the present application, the RLF-report message may include at least one of the following new information:

[0156] a) A new indication on the successful completion of the DAPS handover procedure. For example, the indication may be set to "successful DAPS handover". This new indication indicates that the DAPS handover procedure was completed successfully, rather than "failed". Otherwise, the network considers that a handover failure occurred during the DAPS handover procedure.

[0157] b) Previous cell identifier (ID), ie, the cell ID of the source cell.

[0158] c) Connection Failure Type: The connection failure type is configured as RLF in the source.

[0159] d) The reason for the RLF of the source link. This reason can be set to one of the following:

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

[0161] (2) Problems with the random access process;

[0162] (3) The maximum number of retransmissions is reached;

[0163] (4) Failure of the beam failure recovery process;

[0164] (5) Expiration of a timer for initiating failure recovery based on a triggered measurement report;

[0165] (6) Receipt of a backhaul (BH) RLF indication; and

[0166] (7) Failure of LBT on the source link.

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

[0168] Fig. 9 A further exemplary signal transmission process according to some embodiments of the present application is described.

[0169] like Fig. 9 As shown in FIG. 9 , in operation 901, a target BS (e.g., Figure 6 602b) transmits a message associated with the failure of the MCG to a source BS (e.g., Figure 6 The source BS controls the UE (e.g., as shown in FIG. 6 ). Figure 1 The target BS controls the target cell of the UE.

[0170] For example, the target BS transmits a failure indication message to the source BS. This failure indication message is sent by the target BS to indicate an RRC re-establishment attempt or a RLF report is received from a UE that suffered a connection failure at the source BS. The purpose of transmitting the failure indication message is to convey information about the RRC re-establishment attempt or the received RLF report between NG-RAN nodes. Signaling occurs from the target BS at which the re-establishment attempt is made or the RLF report is received to the source BS to which the relevant UE may have been attached before the connection failure. This can help the detection of RLF.

[0171] The failure indication message in operation 901 may be a FAILURE INDICATION message as specified in the 3GPP standard document. The FAILURE INDICATION message may be transmitted via an Xn interface or an X2 interface.

[0172] Specifically, the FAILURE INDICATION message as specified in the 3GPP standard document TS 38.423

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

[0173] The failure indication message transmitted from the target BS to the source BS is associated with the RLF report transmitted from the UE in operation 701, such as Figure 7 As described and shown in the foregoing. For example, the fault indication message includes a container of an RLF report. The container of the RLF report may be transmitted via an Xn interface or an X2 interface.

[0174] Fig.10 A further flow chart illustrating a method for a fault indication process according to some embodiments of the present application. Fig.10 The method 1000 shown in FIG. 1 may be performed by a target BS (eg, Figure 6 BS602b and BS602b as described and shown in Fig. 9 The target BS) described and shown in the specification is executed.

[0175] like Fig.10 As shown in , in operation 1002, the target BS transmits a UE information request. In operation 1004, the target BS receives a UE information response including an RLF report. The RLF report includes information related to the RLF of the source link for the MCG during the DAPS handover process. In an embodiment of the present application, the RLF report may include at least one of: an indication of successful completion of the DAPS handover process; a cell identifier (ID) of the source cell; a connection failure type; and a cause of the RLF of the source link. The connection failure type may be configured as an RLF in the source.

[0176] 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 to "successful DAPS handover".

[0177] In some embodiments of the present application, the 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, an RLF cause of a source link, a container including an RLF-Report IE reported from a UE, and a cell radio network temporary identifier (C-RNTI) in the source.

[0178] In some embodiments of the present application, the cause of the RLF of the source link in the fault indication includes at least one of the following:

[0179] a) The physical layer problem timer expires;

[0180] b) Problems with random access process;

[0181] c) The maximum number of retransmissions is reached on the Radio Link Control (RLC);

[0182] d) Failure of the beam failure recovery process;

[0183] e) expiration of a timer for initiating failure recovery based on triggered measurement reporting;

[0184] f) receipt of a BH RLF indication; and

[0185] g) Listen-before-talk (LBT) failure of the source link.

[0186] In some embodiments of the present application, the cell ID of the target cell in the fault indication is a physical cell identifier (PCI) or an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) cell global identifier (ECGI).

[0187] The following text describes how to solve the above problems Figures 7 to 10 Specific embodiment 3 of the method shown and described therein.

[0188] According to Embodiment 3, a UE (e.g. Figure 6 UE 601a) and a target BS (e.g., Figure 6 BS 602b) described and shown in FIG. 602b) performs the following operations:

[0189] (1) When the UE is performing a DAPS handover procedure, RLF may occur in the source. After the DAPS handover procedure is successfully completed, the UE accesses the target cell.

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

[0191] (3) After receiving the indication from the UE, the target BS transmits a UE information request to the UE.

[0192] (4) After receiving the UE Information Request from the target BS, the UE transmits a UE Information Response containing an RLF-Report to the target BS. The RLF-Report may contain:

[0193] New indications, such as a successful DAPS handover process.

[0194] • Previous cell ID, which can be set as the source cell.

[0195] • Connection Failure Type, which can be set to RLF in the source.

[0196] The RLF cause of the source, which can be set to one of t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, t312-Expiry, the reception of BHRLFindication, and mcg-lbtFailure.

[0197] (5) After receiving the UE Information Response containing the RLF-Report from the UE, the target BS shall transmit a failure indication to the source BS.

[0198] - The failure indication may include a new IE set to "Successful DAPS Handover". The sub-IE of the new IE "Successful DAPS Handover" may be one of the following:

[0199] Source cell ID;

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

[0201] Optional RLF reason;

[0202] C-RNTI from the source; and

[0203] UE RLF-Report Container.

[0204] The details described in all other embodiments of this application (for example, details on how to solve the coexistence problem of the DAPS handover process of the MCG and the RLF reporting mechanism) are applicable to Figures 7 to 10 In addition, Figures 7 to 10 The details described in the embodiments apply to Figures 1 to 6 And all embodiments of 11.

[0205] Fig.11 A simplified block diagram illustrating an apparatus 1100 for an enhanced fault reporting mechanism according to some embodiments of the present application.

[0206] In some embodiments, the device 1100 may be Figure 1 UE 101 shown in or Figure 6 UE 601a shown and described in .

[0207] In some other embodiments, the device 1100 may be a target BS, for example, Figure 6 BS602b shown and described in .

[0208] refer to Fig.11 , the device 1100 may include at least one non-transitory computer-readable medium 1102, at least one receiving circuit system 1104, at least one transmitting circuit system 1106, and at least one processor 1108. In some embodiments of the present application, the at least one receiving circuit system 1104 and the at least one transmitting circuit system 1106 may be integrated into at least one transceiver. The at least one non-transitory computer-readable medium 1102 may have computer-executable instructions stored therein. The at least one processor 1108 may be coupled to the at least one non-transitory computer-readable medium 1102, the at least one receiving circuit system 1104, and the at least one transmitting circuit system 1106. The computer-executable instructions may be programmed to implement a method using the at least one receiving circuit system 1104, the at least one transmitting circuit system 1106, and the at least one processor 1108. The method may be a method according to an embodiment of the present application, for example, Figure 5A , Figure 5B , Figure 8 or Fig.10 The corresponding method shown in .

[0209] The method according to the embodiment of the present application may also be implemented on a programmed processor. However, the controller, flow chart and module may also be implemented on a general or special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device, etc. In general, any device on which a finite state machine capable of implementing the flow chart shown in the figure resides can be used to implement the processor functions of the present application. For example, an embodiment of the present application provides a device for recognizing emotions from speech, comprising a processor and a memory. Computer programmable instructions for implementing the method for recognizing emotions from speech are stored in a memory, and the processor is configured to execute computer programmable instructions to implement the method for recognizing emotions from speech. The method may be a method as stated above or other methods according to an embodiment of the present application.

[0210] Alternative embodiments preferably implement the method according to the embodiments of the present application in a non-transitory computer-readable storage medium storing computer programmable instructions. The instructions are preferably executed by a computer executable component that is preferably integrated with a network security system. The non-transitory computer-readable storage medium may be stored on any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, optical storage device (CD or DVD), hard drive, floppy disk drive, or any suitable device. The computer executable component is preferably a processor, but the instructions may be executed alternatively or additionally by any suitable dedicated hardware device. For example, an embodiment of the present application provides a non-transitory computer-readable storage medium in which computer programmable instructions are stored. The computer programmable instructions are configured to implement the method for recognizing emotions from speech as stated above or other methods according to the embodiments of the present application.

[0211] Although the present application has been described with its specific embodiments, it is obvious that many alternatives, modifications and variations are obvious to those skilled in the art. For example, the various components of the embodiments may be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, a person of ordinary skill in the art of the disclosed embodiments will be able to make and use the teachings of the present application by simply adopting the elements of the independent claims. Therefore, the embodiments of the application set forth herein are intended to be illustrative, not restrictive. Various changes may be made without departing from the spirit and scope of the present application.

Claims

1. A device for wireless communication, comprising: Transceiver; and a processor coupled to the transceiver, the processor configured to cause the apparatus to: Receiving configuration information including a timer associated with fast master cell group MCG link recovery; Receiving a first radio resource control RRC reconfiguration message including dual active protocol stack DAPS configuration information; Execute DAPS handover process; Starting a timer for handover; In response to a radio link failure RLF of a source link for the MCG during the DAPS handover procedure, while the timer for handover is running, initiating an MCG failure information procedure; and The timer associated with fast MCG link recovery is started.

2. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to: In response to initiating the MCG fault information process, transmitting an MCG fault information message; receiving a second RRC reconfiguration message, wherein the second RRC reconfiguration message includes a reconfiguration with a synchronization information element IE; and In response to receiving the second RRC reconfiguration message, reconfiguration with a synchronization procedure is performed and execution of the DAPS handover procedure is stopped.

3. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to: In response to initiating the MCG fault information process, transmitting an MCG fault information message; receiving a second RRC reconfiguration message, wherein the second RRC reconfiguration message includes a reconfiguration with a synchronization information element IE; and In response to receiving the second RRC reconfiguration message, ignoring the second RRC reconfiguration message and continuing to perform the DAPS handover procedure.

4. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to: receiving an RRC release message; and In response to receiving the RRC release message, resources associated with the source link are released and the DAPS handover procedure is continued.

5. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to: receiving an RRC release message; and In response to receiving the RRC release message, ignoring the RRC release message and continuing to perform the DAPS handover procedure.

6. The apparatus of claim 1, wherein the processor is configured to cause the apparatus to: In response to initiating the MCG fault information process, transmitting an MCG fault information message; and In response to the expiration of the timer associated with fast MCG link recovery, when performing the DAPS handover procedure, an RRC connection reestablishment procedure is not initiated.

7. A device for wireless communication, comprising: Transceiver; and a processor coupled to the transceiver, the processor configured to cause the apparatus to: receiving a radio resource control RRC reconfiguration message including reconfiguration with a synchronization information element IE and dual active protocol stack DAPS configuration information; Execute DAPS handover process; as well as In response to a radio link failure RLF of a source link for a master cell group MCG during the DAPS handover procedure, a report related to the RLF is transmitted after successfully completing the DAPS handover procedure.

8. The apparatus of claim 7, wherein the report includes at least one of: an indication of successful completion of the DAPS handover process; The cell identifier ID of the source cell; The type of connection failure; or The cause of the RLF of the source link.

9. The apparatus of claim 8, wherein the connection failure type is configured as RLF in a source.

10. The apparatus of claim 8, wherein the cause of the RLF of the source link comprises at least one of: Expiration of the physical layer problem timer; Problems with the random access process; The maximum number of retransmissions has been reached; Failure of beam failure recovery process; expiration of a timer for initiating failure recovery based on a triggered measurement report; Receipt of a return BH RLF indication; or The source link's listen-before-talk LBT fails.

11. The apparatus of claim 7, wherein the processor is configured to cause the apparatus to: receiving configuration information including timers associated with fast MCG link recovery; and In response to the RLF of the source link for the MCG during the DAPS handover procedure, an MCG Failure Information procedure is initiated when the timer associated with fast MCG link recovery is not running and the timer for handover is not running.

12. The apparatus of claim 11, wherein the timer for handover is associated with DAPS configuration information.

13. A device for wireless communication, comprising: Transceiver; and a processor coupled to the transceiver, the processor configured to cause the apparatus to: Transmitting user equipment UE information request; receiving a UE information response including a report, wherein the report includes information related to a radio link failure (RLF) of a source link for a master cell group (MCG) during a dual-active protocol stack (DAPS) handover procedure; as well as A failure indication is transmitted, wherein the failure indication comprises an information element IE regarding successful completion of the DAPS handover procedure.

14. The apparatus of claim 13, wherein the report includes at least one of: an indication of successful completion of the DAPS handover process; The cell identifier ID of the source cell; The type of connection failure; or The cause of the RLF of the source link.

15. The apparatus of claim 13, wherein the fault indication comprises at least one of: The cell identifier ID of the source cell; The cell identifier ID of the target cell; a cause of the RLF of the source link; A container containing the RLF-Report IE reported from the UE; or The cell radio network temporary identifier C-RNTI in the source.

16. The apparatus of claim 15, wherein the cause of the RLF of the source link comprises at least one of: Expiration of the physical layer problem timer; Problems with the random access process; The maximum number of retransmissions is reached on the Radio Link Control RLC; Failure of beam failure recovery process; expiration of a timer for initiating failure recovery based on a triggered measurement report; Receipt of a return BH RLF indication; or The source link's listen-before-talk LBT fails.

17. The apparatus of claim 15, wherein the cell ID of the target cell comprises at least one of: Physical cell identifier PCI; or Evolved Universal Terrestrial Radio Access Network E-UTRAN Cell Global Identifier ECGI.

18. The apparatus of claim 14, wherein the cause of the RLF of the source link comprises at least one of: Expiration of the physical layer problem timer; Problems with the random access process; The maximum number of retransmissions is reached on the Radio Link Control RLC; Failure of beam failure recovery process; expiration of a timer for initiating failure recovery based on a triggered measurement report; Receipt of a return BH RLF indication; or The source link's listen-before-talk LBT fails.

19. The apparatus of claim 13, wherein the apparatus comprises a target base station for the DAPS handover procedure.

20. The apparatus of claim 19, wherein the processor is configured to transmit the UE information request to a source base station to which the UE is connected.

Images