Method and apparatus for enhanced fault reporting mechanism for primary cell group and secondary cell group

Abstract

Embodiments of the present application relate to a method and apparatus for an enhanced fault reporting mechanism for a master cell group (MCG) or a secondary cell group (SCG) in accordance with a third generation partnership project (3GPP) 5G new radio (NR) system, etc. According to an embodiment of the present application, a method may include: in response to operating in a radio resource control (RRC) connected state, receiving an RRC reconfiguration message including a reconfiguration and synchronization information element (IE); starting a timer associated with a handover, wherein a timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE; and in response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, performing a random access procedure and synchronizing to a target primary cell of the master cell group. If the reconfiguration and synchronization IE includes a DAPS configuration, the UE is not allowed to initiate a measurement report. In response to initiating a fault information procedure, the UE may stop a timer for initiating fault recovery based on triggering a measurement report.

Description

Technical Field

[0001] Embodiments of the present application generally relate to wireless communication technology, and more particularly, to a method and apparatus for an enhanced fault reporting mechanism for a master cell group (MCG) or a secondary cell group (SCG). Background Art

[0002] When a user equipment (UE) experiences a radio link failure (RLF) or a handover failure (HOF), 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 setup procedure in response to an unsuccessful RRC reestablishment procedure. The accessed network will request UE information including an RLF report of the UE 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] Currently, in the 3rd Generation Partnership Project (3GPP) 5G New Radio (NR) system, etc., the details on how to provide an enhanced fault reporting mechanism for MCG and SCG have not been specifically discussed in 3GPP 5G NR technology. Summary of the invention

[0004] Some embodiments of the present application provide a method for wireless communication. The method may be performed by a UE. The method includes: in response to operating in an RRC connected state, receiving an RRC reconfiguration message including a reconfiguration and synchronization information element (IE); starting a timer associated with a handover, wherein a timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE; and in response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, performing a random access procedure and synchronizing to a target primary cell of a primary cell group.

[0005] 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 method performed by the UE mentioned above.

[0006] Some embodiments of the present application provide another wireless communication method. The method may be performed by a UE. The method includes: in response to detecting that an RLF occurs in an MCG or an SCG, initiating a fault information procedure; in response to a physical layer problem timer being running, stopping the physical layer problem timer when another stop condition is met; and in response to a timer for initiating fault recovery based on a triggered measurement report being running, stopping the timer for initiating fault recovery based on a triggered measurement report when another stop condition is met.

[0007] 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 another method performed by the UE mentioned above.

[0008] 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

[0009] In order to describe the manner in which the advantages and features of the present application can be obtained, the description of the present disclosure is presented by reference to specific embodiments of the present disclosure, which are illustrated in the accompanying drawings. These drawings depict only example embodiments of the present application and therefore should not be considered to limit the scope of the present disclosure.

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

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

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

[0013] Figure 4A An exemplary vehicle-to-everything (V2X) communication system 400 is illustrated according to some embodiments of the present application;

[0014] Figure 4B An exemplary flow chart illustrating a sidelink RRC reconfiguration procedure according to some embodiments of the present application;

[0015] Figure 4CAn exemplary timeline of RLF and fast MCG link recovery procedures is illustrated in accordance with some embodiments of the present application.

[0016] Figure 5 A flowchart illustrating a method for switching programs according to some embodiments of the present application;

[0017] Figure 6 Another flow chart illustrating a method for a fault information program according to some embodiments of the present application; and

[0018] Figure 7 Illustrated is a simplified block diagram of an apparatus 700 for an enhanced fault reporting mechanism according to some embodiments of the present application. DETAILED DESCRIPTION

[0019] The detailed description of the accompanying drawings is intended to be 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 achieved by different embodiments intended to be included in the spirit and scope of the present application.

[0020] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP LTE Release 8, etc.). Please consider that, along with the development of network architectures and new service scenarios, all embodiments in the present application can also be applied to similar technical problems; and in addition, the terms described in the present application can be changed, which should not affect the principles of the present application.

[0021] 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 is connected to the SN 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.

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

[0023] like Figure 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 illustration purposes, Figure 1 The dual connectivity system 100 in FIG. 1 includes one UE 101 shown, one MN 102 shown, and one SN 103 shown. Figure 1 A specific number of UEs 101, MNs 102, and SNs 103 are depicted in FIG. 1 , but please consider that any number of UEs 101, MNs 102, and SNs 103 may be included in the wireless communication system 100.

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

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

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

[0027] 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 for 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.

[0028] SN 103 may be associated with an SCG. SCG may refer to a serving cell group associated with SN 103, and may include a primary supplementary cell (PSCell) and optionally one or more supplementary cells (SCells).

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

[0030] 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 vehicle onboard 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 identification 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.

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

[0032] Specifically, in some embodiments of the SCG fault information program, in the Figure 2 In step 201 shown in FIG. 1 , UE 101 and MN 102 may communicate RRC reconfiguration information. Figure 2 In step 202 shown in FIG. 1 , UE 101 may initiate an SCG failure information procedure and transmit a message associated with a failure of the SCG to MN 102. In step 202, the message associated with the failure of the SCG may be an SCGFailureInformation message specified in a 3GPP standard document. Then, MN 102 may process the SCGFailureInformation message and decide whether to keep the SN or SCG, change the SN or SCG, or release the SN or SCG. The SN may be Figure 1SN 103 as shown and illustrated in FIG.

[0033] In the above-mentioned embodiment of the SCG fault information procedure, the UE 101 may initiate the SCG fault information procedure to report a fault of the SCG when one of the following conditions is met:

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

[0035] When a reconfiguration and synchronization failure occurs in the SCG.

[0036] In case of SCG configuration failure.

[0037] • Upon an integrity check failure indication related to Signalling Radio Bearer (SRB) 3 from the lower layers of the SCG.

[0038] In 3GPP Release 16, a fast MCG link recovery procedure was introduced for the MR-DU scenario. 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 the RLF in the MCG via the SN connected to the UE, so that the UE in the RRC_CONNECTED state can initiate the fast MCG link recovery procedure to quickly continue the RRC connection without performing the reestablishment procedure.

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

[0040] Specifically, in Figure 2 In some embodiments of the MCG failure information procedure shown in , in step 201, UE 101 and MN 102 may communicate RRC reconfiguration information. In step 202, UE 101 may initiate the MCG failure information procedure and transmit a message associated with the 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. In step 202, the message associated with the failure of the MCG may be a MCGFailureInformation message specified in a 3GPP standard document.

[0041] 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 101 may transmit a message associated with the failure of the MCG to the SN (e.g., Figure 1), and then the SN can transmit the message received from UE 101 to MN 102.

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

[0043] When or after transmitting the message in step 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 specified in the 3GPP standard document.

[0044] 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 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 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 1 SN 103 shown and illustrated in ), and then the SN can transmit a response message to UE 101.

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

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

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

[0048] • If UE 101 initiates transmission of MCGFailureInformation message as shown in step 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 documents.

[0049] • If UE 101 initiates transmission of a MCGFailureInformation message as shown in step 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.

[0050] As specified in the 3GPP standard documents, a dual active protocol stack (DAPS) handover procedure is introduced to maintain a source BS connection after the UE receives a handover command associated with the DAPS handover procedure and until the UE releases the source cell of the source BS after successfully completing a random access procedure to a target base station (BS).

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

[0052] In the control plane handling of handovers associated with the DAPS handover procedure, messages are exchanged directly between the BSs. A specific example is shown below. Figure 3 middle.

[0053] Figure 3An exemplary flow chart illustrating an intra-AMF switching procedure according to some embodiments of the present application. Figure 3 The embodiments depict a basic conditional handover scenario in which both the Access and Mobility Management Function (AMF) and the User Plane Function (UPF) are unchanged.

[0054] refer to Figure 3 In step 301, the source BS may transmit measurement configuration information to the UE. The UE may report measurement results to the source BS based on the measurement configuration information. In step 302, the source BS may decide to handover the UE, which may be based on the measurement results reported by the UE.

[0055] The source BS may transmit a HANDOVER REQUEST message to the target BS in step 303. For example, the HANDOVER REQUEST message may convey a transparent RRC container with necessary information to prepare a handover procedure at the target BS side.

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

[0057] In step 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.

[0058] In step 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 and synchronization information element (IE). The RRC reconfiguration message may contain information required to access the target cell of the target BS.

[0059] In step 307, the source BS may send an SN STATUS TRANSFER message to the target BS.

[0060] In step 308, the UE may access the target cell and complete the handover procedure by sending an RRCReconfigurationComplete message to the target BS. In some embodiments implementing the DAPS handover procedure, the UE does not immediately leave 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.

[0061] In step 309, the target BS may 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.

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

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

[0064] In step 312, upon 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 procedure. The source BS may then release the radio and control plane related resources associated with the UE context. Any ongoing data forwarding may continue.

[0065] Table 1 below shows an introduction to some timers specified in 3GPP standard documents, including the start condition, stop condition, operation upon expiration, and possible general name for each of these timers.

[0066]

[0067]

[0068]

[0069]

[0070] Figure 4A An exemplary V2X communication system 400 is illustrated in accordance with some embodiments of the present application.

[0071] like Figure 4A As shown in FIG. 4 , the V2X communication system includes a gNB 402, an ng-eNB 403, and some V2X UEs, namely, UE 401-A, UE 401-B, and UE 401-C. Each of these UEs may refer to Figure 1 and 2 UE 101 shown and illustrated in FIG.

[0072] Specifically, UE 401-A is within the coverage of gNB 402, UE 401-B is within the coverage of ng-eNB 403, and UE 401-C is outside the coverage of gNB 402 and ng-eNB 403. Support for V2X services via the PC5 interface may be provided through NR sidelink communication and / or V2X sidelink communication. NR sidelink communication may support one of three types of transmission modes for a pair of source layer-2 ID and destination layer-2 ID: unicast transmission, multicast transmission, and broadcast transmission. Sidelink transmission and reception via the PC5 interface is supported when the UE is within the NG-RAN coverage or outside the NG-RAN coverage.

[0073] UE 401-A within the coverage of gNB 402 may perform sidelink unicast transmission, sidelink multicast transmission, or sidelink broadcast transmission via the PC5 interface. UE 401-C outside the coverage may also perform sidelink transmission and reception via the PC5 interface. Please consider that, according to some other embodiments of the present application, the V2X communication system may include more or fewer BSs and more or fewer V2X UEs. In addition, please consider that Figure 4A The names of the V2X UEs (which represent TxUE, Rx UE, etc.) illustrated and shown in FIG. 4 may be different, for example, UE 401c, UE 404f, UE 408g, etc.

[0074] In addition, although the mobile phone is used as the illustration Figure 4A , but please consider that according to some other embodiments of the present application, the V2X communication system may include any type of UE (e.g., a roadmap device, a mobile phone, a computer, a laptop, an IoT (Internet of Things) device, or other type of device).

[0075] according to Figure 4AIn some embodiments, UE 401-A is used as a Tx UE, and UE 401-B and UE 401-C are used as Rx UEs. UE 401-A may exchange V2X messages with UE 401-B or UE 401-C via a side link (e.g., a PC5 interface specified in 3GPP TS23.303). UE 401-A may transmit information or data to other UEs within the V2X communication system via side link unicast, side link multicast, or side link broadcast. Side link communications include NR side link communications and V2X side link communications. For example, UE 401-A may transmit data to UE 401-C in an NR side link unicast session, and UE 401-B may transmit data to UE 401-C in a V2X side link unicast session. UE 401-A may transmit data to UE 401-B and UE 401-C in a multicast group through a sidelink multicast transmission session.

[0076] Sidelink communication includes NR sidelink communication and V2X sidelink communication. Figure 4A Demonstration of NR sidelink communications as specified in TS 38.311. V2X sidelink communications are specified in TS 36.311.

[0077] V2X UE can operate in different modes. At least two sidelink resource allocation modes are defined for sidelink communication, namely: Mode 1: the base station schedules the sidelink resources to be used by the UE for sidelink transmission; and Mode 2: the UE determines the sidelink resources configured by the base station or the network or the sidelink transmission resources within the pre-configured sidelink resources. In Mode 2, the base station does not dynamically schedule the sidelink resources for the UE, and the UE determines the sidelink transmission resources and the timing in the resource pool based on the measurement results and sensing results. Figure 4A In the present disclosure, UE 101-A and UE 101-B are in mode 1, and UE 101-C is in mode 2, and in the present disclosure, UE 101-A is used to represent a transmitting UE in mode 1, and UE 101-C is used to represent another transmitting UE in mode 2.

[0078] In Mode 1, in order to transmit data, the UE needs to be in the RRC_CONNECTED state. The base station can dynamically schedule resources for the UE via the Physical Downlink Control Channel (PDCCH) for NR sidelink communication. In addition, the base station can allocate sidelink resources to the UE using two types of configured sidelink grants:

[0079] - Type 1: RRC directly provides a configured sidelink grant for NR sidelink communications only; and

[0080] - Type 2, RRC defines the periodicity of the configured sidelink grant, while PDCCH may signal and activate or deactivate the configured sidelink grant.

[0081] In order for a UE to perform NR sidelink communications, more than one configured sidelink grant may be active at a time on a carrier configured for sidelink transmission.

[0082] When beam failure or physical layer issues occur on NR Uu, the UE may continue to use the configured sidelink grant type 1. During handover, the UE may be provided with a configured sidelink grant via the handover command. If provided, the UE activates the configured sidelink grant type 1 immediately upon receiving the handover command.

[0083] When the UE is in Mode 2, the UE may transmit data within or outside the coverage of the BS (i.e., within the NG-RAN coverage or outside the NG-RAN coverage). The UE autonomously selects a sidelink grant from a resource pool provided through system information or dedicated signaling when it is within the BS coverage or through pre-configuration when it is outside the BS coverage.

[0084] For NR sidelink communications, a resource pool may be provided for a given validity zone, wherein the UE does not need to acquire a new resource pool when moving within the validity zone, at least when this pool is provided by the SIB (e.g., reusing the validity zone of the NR SIB). The UE is allowed to temporarily use UE autonomous resource selection and random selection for sidelink transmission based on the configuration of the superior transmit resource pool specified in TS 38.331.

[0085] Figure 4B An exemplary flow chart of a sidelink RRC reconfiguration procedure according to some embodiments of the present application is illustrated. UE 1 and UE 2 refer to two V2X UEs. Each of UE 1 and UE 2 may refer to Figure 1 and 2 UE 101 shown and illustrated in Figure 4A One of the V2X UEs shown and illustrated in (e.g., UE 401-A, UE 401-B, or UE 401-C).

[0086] Specifically, in Figure 4B In step 404 shown in , UE 1 may transmit RRC reconfiguration sidelink information to UE 2. For example, UE 1 transmits an RRCReconfigurationSidelink message specified in a 3GPP standard document to UE 2.

[0087] In such Figure 4BIn step 406 shown in , UE 2 may transmit RRC reconfiguration complete sidelink information to UE 1. For example, UE 2 transmits the RRCReconfigurationCompleteSidelink message specified in the 3GPP standard document to UE 1.

[0088] The purpose of the sidelink RRC reconfiguration procedure is to establish, modify or release a sidelink DRB or configure NR sidelink measurements and reporting for a PC5-RRC connection. Figure 4B The UE shown and illustrated in 1) may start a timer T400 specified in the 3GPP standard document for a destination associated with a sidelink DRB when the UE transmits an RRCReconfigurationSidelink message.

[0089] In addition, the UE may initiate the sidelink RRC reconfiguration procedure and perform the operations in subclause 5.8.9.1.2 of TS 38.331 to its sidelink peer UE in any of the following situations:

[0090] (1) Release the sidelink DRB associated with the peer UE, as specified in subclause 5.8.9.1.4 of TS 38.331.

[0091] (2) Establish a sidelink DRB associated with the peer UE, as specified in subclause 5.8.9.1.5 of TS 38.331.

[0092] (3) Modify the parameters contained in the SLRB-Config of the sidelink DRB associated with the peer UE, as specified in subclause 5.8.9.1.5 of TS 38.331.

[0093] (4) Configure the peer UE to perform NR sidelink measurements and reporting.

[0094] Figure 4C An exemplary timeline of RLF and fast MCG link recovery procedures is illustrated in accordance with some embodiments of the present application. Figure 4C Embodiments of the present invention may be implemented by a UE (e.g., Figure 1 Executed by UE 101 shown and illustrated in FIG.

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

[0096] When the timer T310 expires (which means that it is not recovered 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 SN 103 shown and illustrated in FIG. 103) transmits MCG failure information to the MN (e.g., Figure 1 MN 102 shown and illustrated in FIG. 102 ) and starts timer T316 specified in the 3GPP standard document, such as Figure 4C 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 procedure is terminated. Otherwise, when the timer T316 expires (which means that it is not recovered during the timer T316), the UE performs the reestablishment procedure and starts the timer T311 specified in the 3GPP standard document for cell selection.

[0097] If the timer T311 expires (which means that it is not resumed 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 4C After the timer T311 expires, the UE enters the RRC_IDLE state. Figure 4C As shown in .

[0098] The above about Figure 4C The 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 a measurement report of a measurement identity for which timer T312 has been configured is triggered, the UE will start timer T312. Once timer T312 expires, the UE may declare a failure and trigger a configured failure recovery procedure, such as a fast MCG link recovery procedure.

[0099] Embodiments of the present application provide an enhanced fault reporting mechanism for MCG and SCG in various scenarios (for example, for failures that occur when configuring the MCG link recovery procedure and / or the SCG link recovery procedure for the UE). More details about the embodiments of the present application will be illustrated in the following text in conjunction with the accompanying drawings.

[0100] Figure 5 The flowchart of the method for handover procedure according to some embodiments of the present application is illustrated. The method may be performed by a UE (e.g., Figure 1 and 2 UE 101 shown and illustrated in Figure 4A and 4B For example, the UE may be configured with a DC, wherein the UE is connected to a MN (e.g., Figure 1 MN 102) and SN 103 (e.g., as shown and illustrated in Figure 1 SN 103 as shown and illustrated in FIG.

[0101] like Figure 5 As shown in FIG. 5 , in step 502, the UE may receive an RRC reconfiguration message including a reconfiguration and synchronization information element (IE). In an embodiment of the present application, the RRC reconfiguration message may be received in response to the UE operating in an RRC connected state. The reconfiguration and synchronization IE may be the reconfigurationWithSyncIE specified in the 3GPP standard document.

[0102] In step 504, the UE may start a timer associated with the handover. The timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE. In an embodiment of the present application, the timer associated with the handover is the timer T304 specified in the 3GPP standard document.

[0103] In an embodiment of the present application, the DAPS configuration is included in the RRC reconfiguration message received by the UE. When the UE performs the DAPS handover procedure, the UE may maintain both the source connection and the target connection. The UE is not allowed to initiate the measurement report procedure in the source cell. The measurement report procedure is specified in subclause 5.5.5 of TS38.331. The source cell may be a cell in the source BS, for example, a SpCell of an MCG or SCG.

[0104] In another embodiment of the present application, the DAPS configuration is included in the RRC reconfiguration message received by the UE, the UE maintains measurement configuration information in the source cell, and the UE is not allowed to initiate a measurement reporting procedure in the source cell.

[0105] In response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, the UE performs a random access procedure and synchronizes to a target primary cell of the primary cell group in step 506. Configuration information of the target primary cell (e.g., PCell) of the primary cell group may be included in the reconfiguration and synchronization IE in the RRC reconfiguration message.

[0106] In an embodiment of the present application, in response to successfully synchronizing to the target primary cell of the primary cell group, the UE may further complete the handover procedure, and in response to successfully completing the handover procedure, continue to use the timer for transmitting the RRC reconfiguration for the side link. The timer for transmitting the RRC reconfiguration for the side link may be the timer T400 specified in the 3GPP standard document.

[0107] In another embodiment of the present application, in response to successfully synchronizing to the target primary cell of the primary cell group, the UE may further complete the switching procedure, and in response to successfully completing the switching procedure, the UE may stop all timers running in the source cell, except for the timer used to transmit the RRC reconfiguration for the side link (for example, timer T400 specified in the 3GPP standard document).

[0108] In an embodiment of the present application, sidelink communication information may be configured for a UE. In this embodiment, the UE may transmit RRC reconfiguration information of a sidelink message to a peer UE of its sidelink; and the UE may start a timer (e.g., timer T400 specified in a 3GPP standard document) for transmitting RRC reconfiguration for the sidelink.

[0109] For example, if the timer for transmitting the RRC reconfiguration for the side link expires, the UE may further perform the reestablishment procedure. The UE may enter the RRC idle state in response to the reestablishment failure. The UE may continue the timer for transmitting the RRC reconfiguration for the side link in response to entering the RRC idle state.

[0110] Figure 5 The embodiments can solve the following problems: (1) when the UE is configured with sidelink communication information, if the UE goes to RRC idle state, whether the UE should start or continue the timer for transmitting RRC reconfiguration for the sidelink; and (2) when the UE is configured with sidelink communication information, if the UE successfully completes the random access procedure and synchronizes to the target primary cell of the primary cell group, whether the UE should start or continue the timer for transmitting RRC reconfiguration for the sidelink.

[0111] The following text describes Figure 5 A specific embodiment 1 of the method for solving the above problems is shown and illustrated in FIG.

[0112] According to embodiment 1, a UE (e.g. Figure 1 and 2 UE 101 shown and illustrated in Figure 4A and 4B ) and the BS perform the following steps:

[0113] (1) The UE may access the BS. Dual Connectivity (DC) operation may be configured for the UE. Sidelink communication information may be configured for the UE. If the UE is configured with sidelink communication information, the UE may transmit RRC reconfiguration information of the sidelink message to its sidelink peer UE and start timer T400 specified in the 3GPP standard document.

[0114] (2) The BS (or Pcell) may then transmit an RRC reconfiguration message including the reconfigurationWithSync IE to the UE. This step of the BS is associated with 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.

[0115] (3) The UE receives an RRC reconfiguration message including the reconfigurationWithSync IE from the BS.

[0116] (4) The UE may then perform a reconfiguration and synchronization procedure. The UE may trigger a random access procedure based on the received RRC reconfiguration message. More specifically:

[0117] If the received RRC reconfiguration message includes the reconfigurationWithSync IE, the UE may start the timer T304 specified in the 3GPP standard document. The UE may perform a random access procedure and synchronize to the target PCell of the MCG in response to receiving the RRC reconfiguration message including the reconfigurationWithSync IE.

[0118] If the reconfigurationWithSync IE is included in the spCellConfig IE of the MCG or SCG and the spCellConfig IE is included in the received RRC reconfiguration message, when the MAC layer of the NR cell group successfully completes the random access procedure triggered by the UE, if the timer T312 for the source cell is running, the UE may stop the timer T312.

[0119] If the timer T304 for the cell group and the timer T310 for the source cell are running, the UE may also stop the timer T304 and stop the timer T310.

[0120] • If the DAPS configuration is included in the RRC reconfiguration message and if the UE maintains both the source connection and the target connection when performing the DAPS handover procedure, the UE is not allowed to start the measurement reporting procedure in the source cell. The source cell may be a cell in the source BS.

[0121] If the RRC reconfiguration message contains the DAPS configuration and if the UE maintains the measurement configuration information in the source cell, the UE is not allowed to start the measurement reporting procedure.

[0122] If the configuration information of the DAPS switching procedure (e.g., dapsConfig specified in the 3GPP standard document) is not configured for any data radio bearer (DRB), if the timer T312 for the corresponding SpCell is running, the UE may stop the timer T312. And if the timer T310 for the corresponding SpCell is running, the UE may stop the timer T310.

[0123] • The UE may start timer T304 for the corresponding SpCell with the timer value set to t304 contained in the reconfigurationWithSync IE.

[0124] (5) After successfully completing the triggered random access procedure, the UE will apply the corresponding configuration information. For example, the corresponding configuration information includes:

[0125] The part of the channel state information (CSI) report configuration, scheduling request configuration and sounding RS configuration that does not require the UE to know the system frame number (SFN) (if any) of the corresponding target SpCell.

[0126] The part of measurement and radio resource configuration that requires the UE to know the SFN of the corresponding target SpCell (if any, after acquiring the SFN of the target SpCell).

[0127] (6) If the UE is successfully synchronized to the target PCell of the MCG, the UE may perform any of the following actions. For example:

[0128] The UE completes the handover procedure; and in response to successfully completing the handover procedure, the UE continues the timer T400 specified in the 3GPP standard document.

[0129] The UE completes the handover procedure; and in response to successfully completing the handover procedure, the UE stops all timers running in the source cell, except for timer T400 specified in the 3GPP standard document.

[0130] (7) If the UE fails to successfully synchronize to the target PCell of the MCG when timer T304 expires, the UE may perform any of the following actions.

[0131] ·UE performs re-establishment procedure.

[0132] • The UE enters the RRC_IDLE state in response to a re-establishment failure occurring during the re-establishment procedure (ie, the RRC re-establishment procedure is unsuccessful).

[0133] • The UE continues timer T400 in response to entering the RRC idle state.

[0134] The details described in all other embodiments of this application (e.g., details of how to provide an enhanced fault reporting mechanism for MCG or SCG) apply to Figure 5 In addition, Figure 5 The details described in the embodiments apply to Figures 1 to 4C , 6 and 7 of all embodiments.

[0135] Figure 6 Another flow chart illustrating a method for a fault information procedure according to some embodiments of the present application is shown. The method may be performed by a UE (e.g., Figure 1 and 2 UE 101 shown and illustrated in Figure 4A and 4B For example, the UE may be configured with a DC, wherein the UE is connected to a MN (e.g., Figure 1 MN 102) and SN 103 (e.g., as shown and illustrated in Figure 1 SN 103 as shown and illustrated in FIG.

[0136] like Figure 6As shown in FIG. 6 , in step 602, the UE may initiate a fault information procedure in response to detecting that a radio link failure (RLF) occurs in an MCG or an SCG. For example, after the UE detects that an RLF occurs in a PCell in an MCG or a PScell ​​in an SCG, the UE may initiate a fault information procedure. The fault information procedure may refer to Figure 2 The SCG fault information procedure or MCG fault information procedure shown and illustrated in the embodiments.

[0137] In an embodiment of the present application, if the UE detects that RLF occurs in the MCG or SCG, the RLF is associated with the SpCell.

[0138] According to some embodiments of the present application, if the UE detects that the SCG has RLF, the fault information procedure may be an SCG fault information procedure. The SCG fault information procedure may be initiated when one of the following conditions is met:

[0139] (1) When RLF is detected in SCG;

[0140] (2) When reconfiguration and synchronization failure occurs in SCG;

[0141] (3) In the event of an SCG configuration failure; or

[0142] (4) When an integrity check failure indication related to SRB3 occurs from the lower layer of the SCG.

[0143] In such Figure 6 In step 604 shown in , if the physical layer problem timer is running, then when the stop condition is met, the UE may stop the physical layer problem timer. The physical layer problem timer may be the timer T310 specified in the 3GPP standard document.

[0144] According to some embodiments of the present application, a physical layer problem timer (e.g., timer T310) is started when a start condition is met. The start condition may include one of the following conditions:

[0145] (1) Upon receiving a preconfigured number of consecutive "out-of-sync" indications for a primary cell (SpCell) of a primary cell group or a secondary cell group. The preconfigured number of consecutive "out-of-sync" indications may be N310 as specified in the 3GPP standard document.

[0146] (2) When it is determined that the timer for fast MCG link recovery is not running. The timer for fast MCG link recovery may be timer T316 specified in the 3GPP standard document.

[0147] (3) When it is determined that any of the following timers is not running:

[0148] A timer for an RRC setup request (e.g., timer T300 specified in a 3GPP standard document);

[0149] A timer for an RRC reestablishment request (e.g., timer T301 specified in a 3GPP standard document);

[0150] A handover timer (eg, timer T304 specified in the 3GPP standard document);

[0151] A timer for RRC connection reestablishment (e.g., timer T311 specified in 3GPP standard documents); and

[0152] A timer for the RRC restart request (eg, timer T319 specified in the 3GPP standard document).

[0153] After the UE starts the physical layer problem timer (e.g., timer T310), a measurement report of the measurement identity configured T312 is triggered. If the DAPS configuration is not configured and the timer for initiating failure recovery based on the triggered measurement report is not running, the UE may start the timer for initiating failure recovery based on the triggered measurement report.

[0154] According to some embodiments of the present application, if the UE detects that the SCG has an RLF, the fault information procedure is the SCG fault information procedure, and the stop condition for stopping the physical layer problem timer in step 604 includes starting the SCG fault information procedure. Specifically, for example, after detecting that the SCG has an RLF, the UE may start the SCG fault information procedure and stop the timer T310 after starting the SCG fault information procedure.

[0155] In an embodiment of the present application, a timer for fast MCG link recovery may be configured. The timer for fast MCG link recovery may be T316 specified in the 3GPP standard document. In this embodiment, since the timer for fast MCG link recovery is configured, if the UE detects that RLF occurs in the MCG, the fault information procedure may be the MCG fault information procedure. The stop condition for stopping the physical layer problem timer in step 604 may include starting the MCG fault information procedure.

[0156] In such Figure 6 In step 606 shown in FIG. 1 , if the timer for initiating failure recovery based on triggered measurement report is running, the UE may stop the timer for initiating failure recovery based on triggered measurement report when another stop condition is met. The timer for initiating failure recovery based on triggered measurement report may be timer T312 specified in the 3GPP standard document.

[0157] According to some embodiments of the present application, if the UE detects that the SCG has an RLF, the fault information procedure is the SCG fault information procedure, and the other stop condition mentioned above in step 606 for stopping the timer for starting fault recovery based on the triggering of the measurement report includes starting the SCG fault information procedure. For example, after detecting that the SCG has an RLF, the UE may start the SCG fault information procedure and stop the timer T312 after starting the SCG fault information procedure.

[0158] In an embodiment of the present application, a timer for fast MCG link recovery may be configured. The timer for fast MCG link recovery may be T316 specified in the 3GPP standard document. In this embodiment, since the timer for fast MCG link recovery is configured, if the UE detects that RLF occurs in the MCG, the fault information procedure may be an MCG fault information procedure. Another stop condition mentioned above in step 606 for stopping the timer for initiating fault recovery based on triggering a measurement report may include initiating an MCG fault information procedure.

[0159] Figure 6 The embodiments can solve the following problems: (1) if the UE initiates the SCG fault information procedure, should the UE stop the timer (e.g., timer T312) or the physical layer problem timer (e.g., timer T310) used to initiate fault recovery based on triggered measurement report; (2) if the UE initiates the MCG fault information procedure, should the UE stop the timer (e.g., timer T312) or the physical layer problem timer (e.g., timer T310) used to initiate fault recovery based on triggered measurement report; and (3) if the timer for fast MCG link recovery (e.g., timer T316) is running, should the UE stop the physical layer problem timer (e.g., timer T310).

[0160] The following text describes how to solve the above problems Figure 6 Three specific embodiments of the method shown and illustrated in FIG.

[0161] Example 2

[0162] According to Embodiment 2, a UE (e.g. Figure 1 The UE 101) and the BS shown and illustrated in FIG. 101 perform the following steps:

[0163] (1) The UE can access the network via DC operation. MCG and SCG can be configured for the UE.

[0164] (2) When neither MCG transmission nor SCG transmission is suspended and one of the following conditions is met, the UE may initiate the SCG Failure Information procedure to report a failure of the SCG:

[0165] -When RLF is detected in SCG;

[0166] -When SCG reconfiguration and synchronization failure occurs;

[0167] - in the event of an SCG configuration failure; or

[0168] -When an integrity check failure indication related to SRB3 occurs from the lower layers of the SCG.

[0169] (3) When initiating the SCG Failure Information procedure, the UE may:

[0170] - If the timer T310 for SCG is running, stop the timer T310;

[0171] - If the timer T312 for SCG is running, then stop the timer T312;

[0172] -Suspend SCG transmission of all SRBs and DRBs;

[0173] - Reset the MAC layer of the SCG; and / or

[0174] - If timer T304 for SCG is running, stop timer T304.

[0175] (4) The UE reports the SCGFailureInformation message to the MN (for example, Figure 1 MN 102 as shown and illustrated in FIG.

[0176] Example 3

[0177] According to Embodiment 3, a UE (e.g. Figure 1 The UE 101) and the BS shown and illustrated in FIG. 101 perform the following steps:

[0178] (1) The UE can access the network via DC operation. The MCG and SCG can be configured for the UE. The timer T316 can be configured.

[0179] (2) When both MCG transmission and SCG transmission are not suspended and when RLF of MCG is detected and timer T316 is not running, the UE may initiate the MCG Failure Information procedure to report the RLF of MCG.

[0180] (3) When initiating the MCG Failure Information procedure, the UE may:

[0181] - If the timer T310 for MCG is running, then stop the timer T310;

[0182] - If the timer T312 for MCG is running, then stop the timer T312;

[0183] - suspend MCG transmissions for all SRBs and DRBs except SRB0; or

[0184] -Reset the MAC layer of MCG.

[0185] (4) The UE receives the data from the SN (e.g. Figure 1 SN 103 shown and illustrated in FIG. 103 ) reports the MCGFailureInformation message to the MN (e.g., Figure 1 MN 102 as shown and illustrated in FIG.

[0186] Example 4

[0187] According to Embodiment 4, a UE (e.g. Figure 1 The UE 101) and the BS shown and illustrated in FIG. 101 perform the following steps:

[0188] (1) The UE can access the BS and the DC operation can be configured for the UE.

[0189] (2) The UE (eg, the physical layer of the UE) may detect the physical channel and transmit an indication (eg, an "out-of-sync" indication) to the MAC layer of the UE.

[0190] (3) Upon receiving N310 continuous “out-of-sync” indication for SpCell from lower layers, the UE may start timer T310 for the corresponding SpCell when none of the timers T300, T301, T304, T311, T316 and T319 described in Table 1 above is running.

[0191] (4) When the UE receives the N311 continuous "in sync" indication for the SpCell from the lower layer, if the timer T310 for the corresponding SpCell is running, it should stop the timer T310. Otherwise, the UE declares RLF when the timer T310 expires.

[0192] (5) After the UE starts the timer T310 for the SpCell, a measurement report of the measurement identity configured with the timer T312 is triggered. If the DAPS configuration is not configured and the timer T312 is not running, the UE may start a timer for initiating failure recovery based on the triggered measurement report.

[0193] The details described in all other embodiments of this application (e.g., details of how to provide an enhanced fault reporting mechanism for MCG or SCG) apply to Figure 6 In addition, Figure 6 The details described in the embodiments apply to Figures 1 to 5 And all embodiments of 7.

[0194] Figure 7 A simplified block diagram of an apparatus 700 for an enhanced fault reporting mechanism according to some embodiments of the present application is illustrated. The apparatus 700 may be Figure 1 UE 101 shown in .

[0195] refer to Figure 7 , the device 700 may include at least one non-transitory computer-readable medium 702, at least one receiving circuit system 704, at least one transmitting circuit system 706, and at least one processor 708. In a certain embodiment of the present application, the at least one receiving circuit system 704 and the at least one transmitting circuit system 706 may be integrated into at least one transceiver. The at least one non-transitory computer-readable medium 702 may have computer-executable instructions stored therein. The at least one processor 708 may be coupled to the at least one non-transitory computer-readable medium 702, the at least one receiving circuit system 704, and the at least one transmitting circuit system 706. The computer-executable instructions may be programmed to implement a method using the at least one receiving circuit system 704, the at least one transmitting circuit system 706, and the at least one processor 708. The method may be a method according to an embodiment of the present application, for example Figure 5 or Figure 6 The corresponding method shown in .

[0196] 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, and the like. In general, any device on which resides a finite state machine capable of implementing the flow chart shown in the figure can be used to implement the processor function of the present application. For example, an embodiment of the present application provides a device for emotion recognition from speech comprising a processor and a memory. Computer programmable instructions for implementing the method for emotion recognition from speech are stored in a memory, and the processor is configured to execute the computer programmable instructions to implement the method for emotion recognition from speech. The method may be a method as stated above or other methods according to an embodiment of the present application.

[0197] 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, which is preferably integrated with a network security system. The non-transitory computer-readable storage medium can 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 can 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 having computer programmable instructions stored therein. The computer programmable instructions are configured to implement the method for emotion recognition from speech as stated above or other methods according to the embodiments of the present application.

[0198] Although the present application has been described by the specific embodiments of the present application, it is obvious that many alternatives, modifications and variations can be understood by those skilled in the art. For example, the various components of the embodiments can be interchanged, added or substituted in other embodiments. And, the elements of each figure do not have to be all used 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 technical solutions. Therefore, the embodiments of the present application as stated herein are intended to be illustrative and not restrictive. Various changes can be made without departing from the spirit and scope of the present application.

Claims

1. A device comprising: Transceiver; as well as a processor coupled to the transceiver, the processor configured to cause the apparatus to: In response to operating in a radio resource control (RRC) connected state, receiving an RRC reconfiguration message including a reconfiguration and synchronization information element (IE); starting a timer associated with the handover, wherein a timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE; and In response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, performing a random access procedure and synchronizing to a target primary cell of a primary cell group, wherein sidelink communication information is configured, and the processor is configured to cause the apparatus to: transmitting RRC reconfiguration information for the sidelink message to a peer user equipment UE of the sidelink; and starting a timer for transmitting an RRC reconfiguration for the sidelink, and wherein in response to expiration of the timer associated with the switching, the processor is configured to cause the apparatus to: Perform reconstruction procedures; In response to a re-establishment failure, entering an RRC idle state; and The timer for transmitting an RRC reconfiguration for a sidelink is continued in response to entering the RRC idle state.

2. The apparatus of claim 1 , wherein a dual active protocol stack (DAPS) configuration is included in the RRC reconfiguration message, and the processor is configured to cause the apparatus to: Initiation of the measurement reporting procedure in the source cell is not allowed.

3. The apparatus of claim 1 , wherein a dual active protocol stack (DAPS) configuration is included in the RRC reconfiguration message; and the processor is configured to cause the apparatus to: Maintaining measurement configuration information in the source cell; and The transmission of measurement result reports is not permitted.

4. The apparatus of claim 1 , wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the processor is configured to cause the apparatus to: Complete the switching process; and The timer for transmitting the RRC reconfiguration for the sidelink is continued in response to successfully completing the handover procedure.

5. The apparatus of claim 1 , wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the processor is configured to cause the apparatus to: Complete the switching process; and In response to successfully completing the handover procedure, all timers running in the source cell except the timer for transmitting the RRC reconfiguration for the sidelink are stopped.

6. A method comprising: In response to operating in a radio resource control (RRC) connected state, receiving an RRC reconfiguration message including a reconfiguration and synchronization information element (IE); starting a timer associated with the handover, wherein a timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE; and In response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, performing a random access procedure and synchronizing to a target primary cell of a primary cell group, Wherein the sidelink communication information is configured, and the method further comprises: transmitting RRC reconfiguration information for the sidelink message to a peer user equipment UE of the sidelink; and starting a timer for transmitting an RRC reconfiguration for the sidelink, and In response to the expiration of the timer associated with the handover, the method further comprises: Perform reconstruction procedures; In response to a re-establishment failure, entering an RRC idle state; and The timer for transmitting an RRC reconfiguration for a sidelink is continued in response to entering the RRC idle state.

7. The method of claim 6, wherein the RRC reconfiguration message includes a dual active protocol stack (DAPS) configuration, and the method further comprises not allowing a measurement reporting procedure to be initiated in a source cell.

8. The method according to claim 6, wherein the RRC reconfiguration message includes a dual active protocol stack (DAPS) configuration; and the method further comprises: Maintaining measurement configuration information in the source cell; and Transmission of measurement result reports is not permitted.

9. The method of claim 6, wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the method further comprises: Complete the switching procedure; and A timer for transmitting an RRC reconfiguration for a sidelink is continued in response to successfully completing the handover procedure.

10. The method of claim 6, wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the method further comprises: Complete the switching procedure; and In response to successfully completing the handover procedure, all timers running in the source cell except the timer for transmitting the RRC reconfiguration for the sidelink are stopped.

11. A processor of a user equipment (UE) for wireless communication, the processor being arranged to: In response to operating in a radio resource control (RRC) connected state, receiving an RRC reconfiguration message including a reconfiguration and synchronization information element (IE); starting a timer associated with the handover, wherein a timer value of the timer associated with the handover is included in the reconfiguration and synchronization IE; and In response to receiving the RRC reconfiguration message including the reconfiguration and synchronization IE, performing a random access procedure and synchronizing to a target primary cell of a primary cell group, Wherein the side link communication information is configured, and the processor is further configured to: transmitting RRC reconfiguration information for the sidelink message to a peer user equipment UE of the sidelink; and starting a timer for transmitting an RRC reconfiguration for the sidelink, and In response to the expiration of the timer associated with the switching, the processor is further configured to: Perform reconstruction procedures; In response to a re-establishment failure, entering an RRC idle state; and The timer for transmitting an RRC reconfiguration for a sidelink is continued in response to entering the RRC idle state.

12. The processor of claim 11, wherein a dual active protocol stack (DAPS) configuration is included in the RRC reconfiguration message, and the processor is further configured to: Initiation of the measurement reporting procedure in the source cell is not allowed.

13. The processor of claim 11, wherein a dual active protocol stack (DAPS) configuration is included in the RRC reconfiguration message; and the processor is further configured to: Maintaining measurement configuration information in the source cell; and Transmission of measurement result reports is not permitted.

14. The processor of claim 11, wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the processor is further configured to: Complete the switching process; and The timer for transmitting the RRC reconfiguration for the sidelink is continued in response to successfully completing the handover procedure.

15. The processor of claim 11, wherein in response to successfully synchronizing to the target primary cell of the primary cell group, the processor is further configured to: Complete the switching process; and In response to successfully completing the handover procedure, all timers running in the source cell except the timer for transmitting the RRC reconfiguration for the sidelink are stopped.

Images