Methods and apparatus for deactivating and activating a secondary cell group (SCG) in a multi-radio dual connectivity (MR-DC) scenario

Abstract

Embodiments of the present application relate to methods and apparatus for deactivating and activating a secondary cell group (SCG) in a multi-radio dual connectivity (MR-DC) scenario under a 3rd Generation Partnership Project (3GPP) 5G New Radio (NR) system or the like. According to embodiments of the present application, a method can include, in response to determining to activate a SCG, transmitting state information of one or more secondary cells (SCells), wherein the one or more SCells are associated with the SCG, and in response to determining to deactivate the SCG, transmitting the state information of the one or more SCells and transmitting configuration information regarding behavior of a user equipment (UE).

Description

Technical Field

[0001] Embodiments of this application generally relate to wireless communication technology, and more particularly to methods and apparatus for deactivating and activating secondary cell groups (SCGs) in a multiple radio dual connectivity (MR-DC) scenario. Background Technology

[0002] Next-Generation Radio Access Networks (NG-RAN) support MR-DC scenarios. In MR-DC scenarios, User Equipment (UEs) with multiple transceivers can be configured to utilize resources provided by two different nodes via a non-ideal backhaul connection. One node can provide New Radio (NR) access, while the other can provide Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) (E-UTRA) or NR access. One node can act as the primary node (MN), and the other can act as the secondary node (SN). The MN and SN are connected via a network interface (e.g., the Xn interface as specified in the 3GPP standards document), and at least the MN is connected to the core network.

[0003] Currently, 3GPP 5G technology does not discuss the details of SCG deactivation and activation mechanisms in MR-DC scenarios. Summary of the Invention

[0004] Some embodiments of this application provide a method for wireless communication. The method can be performed by an MN or a SN. The method includes: in response to determining that an SCG is activated, transmitting status information of one or more auxiliary cells (SCells), wherein the one or more SCells are associated with the SCG; and in response to determining that the SCG is deactivated, transmitting the status information of the one or more SCells and transmitting configuration information regarding the behavior of the UE.

[0005] Some embodiments of this application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium storing computer-executable instructions thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform the methods described above, executed by the MN or SN.

[0006] Some embodiments of this application provide another method for wireless communication. The method can be performed by a UE. The method includes: receiving a Radio Resource Control (RRC) reconfiguration message, wherein the RRC reconfiguration message contains status information of one or more SCells, and wherein the one or more SCells are associated with an SCG; and transmitting an RRC reconfiguration complete message.

[0007] Some embodiments of this application also provide an apparatus for wireless communication. The apparatus includes: a non-transitory computer-readable medium storing computer-executable instructions thereon; a receiving circuitry; a transmitting circuitry; and a processor coupled to the non-transitory computer-readable medium, the receiving circuitry, and the transmitting circuitry, wherein the computer-executable instructions cause the processor to perform the methods described above, executed by the UE.

[0008] Details of one or more examples are set forth in the accompanying drawings and the following description. Other features, objects, and advantages will become apparent from this description, the accompanying drawings, and the claims. Attached Figure Description

[0009] To describe how the advantages and features of this application can be obtained, the description of this application is provided with reference to specific embodiments thereof, which are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of this application and should therefore not be considered as limiting its scope.

[0010] Figure 1 This application illustrates a schematic diagram of a wireless communication system according to some embodiments of the present application.

[0011] Figure 2 A flowchart illustrating a method for transmitting status information of (several) SCells according to some embodiments of this application;

[0012] Figure 3 An exemplary flowchart illustrating an SCG deactivation procedure initiated by an MN according to some embodiments of this application is provided.

[0013] Figure 4 An exemplary flowchart illustrating an SCG activation procedure initiated by an MN according to some embodiments of this application;

[0014] Figure 5 An exemplary flowchart illustrating an SCG deactivation procedure initiated by an SN according to some embodiments of this application is provided.

[0015] Figure 6 An exemplary flowchart illustrating an SCG activation procedure initiated by an SN according to some embodiments of this application;

[0016] Figure 7 A flowchart illustrating a method for receiving status information of (a number of) SCells according to some embodiments of this application; and

[0017] Figure 8 An exemplary block diagram illustrating some embodiments of the device according to this application is provided. Detailed Implementation

[0018] The detailed description of the accompanying drawings is intended to illustrate preferred embodiments of the present application and is not intended to represent the only form in which the present application may be practiced. It should be understood that the same or equivalent functionality may be achieved through different embodiments intended to be covered within the spirit and scope of the present application.

[0019] Reference will now be made in detail to some embodiments of this 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.). It should be understood that all embodiments in this application are applicable to similar technical problems as network architectures and new service scenarios evolve; furthermore, the terminology used in this application may vary, which should not affect the principles of this application.

[0020] Figure 1 A schematic diagram illustrating a wireless communication system according to some embodiments of this application.

[0021] like Figure 1 As shown, the wireless communication system 100 can be a dual-connectivity system 100, including 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 includes a shown UE 101, a shown MN 102, and a shown SN 103. Although in Figure 1 A specific number of UEs 101, MN 102 and SN 103 are depicted, but it should be considered that the wireless communication system 100 may contain any number of UEs 101, MN 102 and SN 103.

[0022] refer to Figure 1 UE 101 can connect to MN 102 and SN 103 via a network interface (e.g., the Uu interface as specified in the 3GPP standard document). MN 102 and SN 103 can connect to each other via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). MN 102 can connect to MN 102 and SN 103 via a network interface (e.g., the Xn interface as specified in the 3GPP standard document). Figure 1 (Not shown in the image) Connects to the core network. UE 102 can be configured to utilize resources provided by MN 102 and SN 103 to perform data transmission.

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

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

[0025] 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 this application, in an EN-DC scenario, SN 103 may be an en-gNB. In another embodiment of this application, in an NE-DC scenario, SN 103 may be an ng-eNB. In yet another embodiment of this application, in an NR-DC scenario or an NGEN-DC scenario, SN 103 may be a gNB.

[0026] SN 103 may be associated with an SCG. An SCG may refer to the serving cell group associated with SN 103 and may include primary secondary cells (PSCells) and optionally one or more SCells. The PCell of the MCG and the PSCell of the SCG may also be referred to as a special cell (SpCell).

[0027] In some embodiments of this application, UE 101 may include a computing device, such as a desktop computer, laptop computer, personal digital assistant (PDA), tablet computer, smart TV (e.g., a TV connected to the Internet), set-top box, game console, security system (including security cameras), in-vehicle computer, network device (e.g., router, switch, and modem), or the like. In some other embodiments of this application, UE 101 may include a portable wireless communication device, smartphone, cellular phone, flip phone, device with a subscriber identity module, personal computer, selective call receiving circuitry system, or any other device capable of transmitting and receiving communication signals on a wireless network. In some other embodiments of this application, UE 101 may include a wearable device, such as a smartwatch, fitness tracker, optical head-mounted display, or the like. Furthermore, UE 101 may be referred to as a subscriber unit, mobile device, mobile station, user, terminal, mobile terminal, wireless terminal, fixed terminal, subscriber station, user terminal, or device, or described using other terms used in the art.

[0028] Currently, the 3GPP standard documents regarding SCell activation or deactivation procedures are as follows: To achieve reasonable UE battery consumption during carrier aggregation (CA) configuration, an SCell activation / deactivation mechanism is supported. When an SCell is deactivated, the UE is not required to receive the corresponding Physical Downlink Control Channel (PDCCH) or Physical Downlink Shared Channel (PDSCH), cannot transmit in the corresponding uplink, and is not required to perform Channel Quality Indicator (CQI) measurements. Conversely, when an SCell is active, the UE should receive both PDSCH and PDCCH (if the UE is configured to monitor PDCCH from this SCell) and is expected to be able to perform CQI measurements.

[0029] As specified in the 3GPP Release 17 work item on "NR support for efficient SCG activation or deactivation procedures in MR-DC scenarios," power consumption for both the UE and network is a significant issue in EN-DC deployments due to the simultaneous maintenance of two radio links. In some cases, the power consumption of an NR UE is 3 to 4 times higher than that of an LTE UE. In EN-DC deployments, the MN provides basic coverage. When the UE's data rate requirements change dynamically, such as from high to low, it is worth considering (de)activating the SN to save energy consumption for both the network and the UE.

[0030] For example, during the SCG deactivation procedure, there are issues related to Radio Link Monitoring (RLM) measurement operations and beam failure detection or recovery operations. For instance, when the SCG is deactivated, the UE will stop monitoring the associated PDCCH but continue performing Radio Resource Management (RRM) measurement operations. However, it remains unclear whether other operations (e.g., at least one of "RLM measurement operations" and "beam failure detection operations" and "beam failure recovery operations") are supported during the SCG deactivation procedure. On the one hand, RLM measurement operations and beam failure detection or recovery operations consume UE power and should therefore be avoided as much as possible. On the other hand, RLM measurement operations and beam failure detection or recovery operations are beneficial for the UE to monitor link quality in a timely manner and can reduce the likelihood of RLF when the SCG is reactivated.

[0031] Furthermore, when an SCG is activated or deactivated, there are issues related to the states (i.e., activated, deactivated, or dormant) of several SCells. Generally, three types of states are defined for several SCells: activated, deactivated, and dormant. When an SCG is activated or deactivated, it is unclear whether several associated SCells should remain in their old state or enter a new state. In one instance, for a dormant SCell, when the associated SCG is activated or deactivated, it is unclear whether the dormant SCell should remain dormant or enter an activated or deactivated state. In a further instance, when an SCG is activated, it is unclear whether all associated SCells should be activated or only a subset of SCells should be activated. Following the spirit of older 3GPP standards, when an SCG is activated, all associated SCells can be set to the activated state by default, and the SN can later use the SCell to activate the Media Access Control (MAC) Control Element (CE) or the SCell to deactivate the MAC CE to set a specific SCell to the deactivated or dormant state. However, this approach incurs signaling overhead and latency.

[0032] Generally, the SCG (deactivation) procedure can be initiated by the MN, SN, or UE. Currently, the exact mechanism supporting SCG (deactivation) procedures initiated by the MN, SN, or UE is unclear. A specific mechanism is needed to efficiently (deactivate) the SCG.

[0033] Some embodiments of this application provide an efficient SCG (deactivation) mechanism in MR-DC scenarios in 3GPP 5G NR systems or similar. Some embodiments of this application provide a mechanism to support flexible or configurable UE behavior during the SCG deactivation procedure to balance the trade-off between power assumptions and accurate or timely radio link monitoring. Some embodiments of this application provide a mechanism to support SCell state configuration during the SCG (deactivation) procedure to save signaling overhead and facilitate efficient SCG activation or deactivation procedures. Further details are described below in conjunction with the accompanying drawings.

[0034] Figure 2 A flowchart illustrating a method for transmitting status information of (a number of) SCells according to some embodiments of this application. Figure 2 The instance method 200 in the embodiments can be performed by the following:

[0035] -MN (for example, such as Figure 1 and 3 (MN 102, MN 320, MN 420, MN 520 or MN 620) shown and described in any of the six; or

[0036] -SN (for example, such as Figure 1 and 3 (SN 103, SN 330, SN 430, SN 530 or SN 630 shown and described in any of the six).

[0037] Although MN or SN are described, it should be understood that (several) other devices may be configured to perform such actions. Figure 2 The methods shown and explained in the document. Figure 2 The embodiments assume that MN and SN can be combined in any of the EN-DC, NGEN-DC, NE-DC, and NR-DC scenarios. Figure 2 In the embodiments, the following definitions are assumed:

[0038] • Fast MCG Link Recovery: In the MR-DC scenario, the RRC procedure, in which the UE sends an MCG failure information message to the MN via the SCG when a radio link failure on the MCG is detected.

[0039] • Primary cell group: In the MR-DC scenario, the serving cell group associated with the primary node, which consists of SpCell (PCell) and one or more SCells.

[0040] • Secondary Cell Group: In the MR-DC scenario, the serving cell group associated with the secondary node consists of SpCell (PSCell) and one or more SCells.

[0041] • Auxiliary Node: In MR-DC scenarios, a radio access node that does not have a control plane connection to the core network provides additional resources to the UE. It can be an en-gNB (in EN-DC), an auxiliary ng-eNB (in NE-DC), or an auxiliary gNB (in NR-DC and NGEN-DC).

[0042] • SCG Bearer: In MR-DC scenarios, a radio bearer that has only one RLC bearer in the SCG (or two RLC bearers in the case of CA packet replication in the E-UTRAN cell group, or up to four RLC bearers in the case of CA packet replication in the NR cell group).

[0043] •SpCell: The primary cell in a primary or secondary cell group.

[0044] • Signaling Radio Bearer (SRB) 3: Direct SRB between SN and UE in EN-DC, NGEN-DC and NR-DC.

[0045] • Separate bearer: In MR-DC scenarios, a radio bearer that has an RLC bearer in both MCG and SCG.

[0046] In such Figure 2 In the exemplary method 200 shown, in operation 201, in response to determining the activation of the SCG, MN, or SN, state information of (several) SCells is emitted. (Several) SCells indicate one or more SCells and are associated with the SCG.

[0047] According to some embodiments, the status information of (a number of) SCells includes at least one of the following:

[0048] (1) The activated state of SCells within (several) SCells;

[0049] (2) The deactivated states of several SCells; and

[0050] (3)(several) The dormant state of SCells within SCells.

[0051] In one instance, the state information of (a number of) SCells includes the activated state of one SCell within (a number of) SCells, the deactivated state of a further SCell within (a number of) SCells, and the dormant state of three other SCells within (a number of) SCells. In a further instance, the state information of (a number of) SCells includes the activated states of two SCells within (a number of) SCells and the deactivated state of one SCell within (a number of) SCells. In another instance, the state information of (a number of) SCells includes the activated states of four SCells within (a number of) SCells, the deactivated states of three SCells within (a number of) SCells, and the dormant state of one SCell within (a number of) SCells.

[0052] According to some embodiments, in operation 201, status information of (a number of) SCells may be transmitted in at least one of the following:

[0053] (1) Xn interface message containing configuration information about SCG ( Figure 3 and 4 (Specific embodiments are shown in the text);

[0054] (2) An Xn interface message that initiates the SCG deactivation process and contains configuration information about the SCG. Figure 5 (Specific embodiments are shown in the text);

[0055] (3) An Xn interface message that initiates the SCG activation process and contains configuration information about the SCG. Figure 6 (Specific embodiments are shown in the text); and

[0056] (4) RRC message Figures 3 to 6 (Specific embodiments are shown in the text). RRC messages can initiate an SCG deactivation procedure or an SCG activation procedure.

[0057] - In one instance, if Signaling Radio Bearer 3 (SRB3) is configured, then the RRC message is transmitted directly from the SN to the UE. In a further instance, if SRB3 is not configured, then the RRC message is transmitted from the MN to the UE.

[0058] - The RRC message can be an RRC reconfiguration message transmitted from the MN to the UE. In one embodiment, the RRC reconfiguration message is generated by the MN and contains information provided by the SN. In a further embodiment, the RRC reconfiguration message is generated by the SN as a container and forwarded from the SN to the MN. For example, the container is an OCTET string container.

[0059] Specifically, in an embodiment, in the case of an SCG (de)activation procedure initiated by MN, the state information of (a number of) SCells may be included in one of the following:

[0060] - The same Xn interface message (e.g., SN Modification Request Acknowledge Message), which provides the relevant SCG configuration, is sent from SN to MN.

[0061] - The same RRC message (e.g., RRCReconfiguration Message) is used to activate or deactivate the SCG.

[0062] Send from MN to UE.

[0063] - If SRB3 is configured, then it is the same RRC message (e.g., RRCReconfiguration Message) that is used to activate or deactivate SCG and is sent from SN to UE.

[0064] In a further embodiment, in the case of an SCG (de)activation procedure initiated by the SN, the status information of (a number of) SCells may be included in one of the following:

[0065] - The same Xn interface message (e.g., SN Modification Required message) that initiates the SCG activation or deactivation procedure and related SCG configuration is sent from SN to MN.

[0066] - The same RRC message (e.g., RRCReconfiguration Message), which is used to activate or deactivate the SCG, is sent from the MN to the UE.

[0067] - If SRB3 is configured, then it is the same RRC message (e.g., RRCReconfiguration Message) that is used to activate or deactivate SCG and is sent from SN to UE.

[0068] According to some embodiments, the status information of (a number of) SCells includes one of the following:

[0069] (1) The following mapping relationship: each SCell in (a number of) SCells and the target state of each SCell in (a number of) SCells after SCG activation.

[0070] (2) The following mapping relationships: each SCell in (a number of) SCells, the target state of each SCell in (a number of) SCells after deactivating the SCG, and the configuration information about (a number of) behaviors of the UE.

[0071] (3) The following mapping relationship: each SCell in a subset of (a number of) SCells and the target state of each SCell in a subset of (a number of) SCells after SCG activation.

[0072] (4) The following mapping relationships: each SCell in a further subset of (a few) SCells, the target state of each SCell in a further subset of (a few) SCells after deactivating the SCG, and configuration information about (a few) behaviors of the UE.

[0073] The terms “(several) subsets of SCells” and “(several) further subsets of SCells” may refer to the same subset of (several) SCells in some cases or to different subsets of (several) SCells in others.

[0074] In some embodiments, if MN or SN determines to activate SCG, then each SCell in a subset of SCGs changes from its state before SCG activation to the target state of each SCell in a subset of SCGs after SCG activation. In some other embodiments, if MN or SN determines to deactivate SCG, then each SCell in a further subset of SCGs changes from its state before SCG deactivation to the target state of each SCell in a further subset of SCGs after SCG deactivation. In short, in the above mapping, the target state of each SCell indicates a new state, and each SCell, after deactivation of SCG, aims to change from its current state before SCG activation to the new state. The target state of each SCell may also be named the new state or similar.

[0075] According to some embodiments, the status information of (a number of) SCells is determined by the SN. For example, when the SCG (de)activation procedure is initiated by the MN or the SN, the status information of (a number of) SCells is determined by the SN and provided to the UE in at least one of the following formats (or via the MN if SRB3 is not configured):

[0076] - A list or mapping of all SCells associated with SCG and the status of all SCells with their associated configurations (e.g., sCellDeactivationTimer).

[0077] - A subset of several SCells whose states are to be changed, and a list or mapping of the new states of these SCells to their associated configurations (e.g., sCellDeactivationTimer).

[0078] In an example, when the SN decides to activate the SCG, the SN can configure some SCells to remain in a deactivated or dormant state while the SCG is activated.

[0079] Return to reference Figure 2 In operation 202, in response to determining to deactivate the SCG, MN, or SN, state information of (several) SCells is transmitted and transmitted regarding the UE (e.g., UE 101, UE 310, UE 410, UE 510, or UE 610, such as...). Figure 1 and 3 Configuration information for (some) behaviors shown and described in any of the 6.

[0080] According to some embodiments, several behaviors of the UE are configurable during the SCG deactivation procedure. In embodiments, when the MN or SN deactivates the SCG, the MN or SN indicates to the UE at least one of the following configuration information regarding several behaviors of the UE:

[0081] (1) Information indicating whether the UE performs an RLM measurement operation when the SCG is deactivated.

[0082] (2) Configuration information for RLM measurement operations. For example, configuration information for RLM measurement operations includes information about the bandwidth portion (BWP) to be measured.

[0083] (3) Conditions for starting an RLM measurement operation (e.g., RLM_RSRP_threhold).

[0084] (4) Information indicating whether the UE performs beam failure detection operation when the SCG is deactivated.

[0085] (5) Configuration information regarding beam failure detection operation. For example, the configuration information regarding beam failure detection operation indicates that the beam failure detection operation is at least one of "beam failure detection operation based on synchronization signal block (SSB)" and "beam failure detection operation based on channel state information reference signal (CSI-RS)".

[0086] (6) Conditions for starting beam failure detection operation (e.g., BFD_RSRP_threshold).

[0087] (7) Information indicating whether the UE performs beam failure recovery operation when the SCG is deactivated.

[0088] (8) Configuration information regarding beam failure recovery operations.

[0089] (9) Conditions for starting beam failure recovery operation.

[0090] According to some embodiments, configuration information regarding several behaviors of the UE is transmitted in at least one of the following:

[0091] (1) Xn interface message containing configuration information about SCG ( Figure 3 and 4 (Specific embodiments are shown in the figure).

[0092] (2) An Xn interface message that initiates the SCG deactivation process and contains SCG configuration information. Figure 5 and 6 (Specific embodiments are shown in the figure).

[0093] (3) RRC message Figures 3 to 6 (Specific embodiments are shown in the diagram). RRC messages can initiate an SCG (de)activation procedure. In one instance, in response to SRB3 being configured, the RRC message is transmitted directly from the SN to the UE. In a further instance, in response to SRB3 not being configured, the RRC message is transmitted from the MN to the UE. The RRC message can be an RRC reconfiguration message (e.g., an RRCReconfiguration Message) transmitted from the MN to the UE. In one embodiment, the RRC reconfiguration message is generated by the MN and contains information provided by the SN. In a further embodiment, the RRC reconfiguration message is generated by the SN as a container and forwarded from the SN to the MN. For example, the container is an OCTET string container.

[0094] Specifically, in an embodiment, in the case of an SCG deactivation procedure initiated by the MN, configuration information regarding the behavior of the UE(s) is transmitted in at least one of the following:

[0095] - The same Xn interface message (e.g., SN Modification Request Acknowledge Message), which provides the relevant SCG configuration, is sent from SN to MN.

[0096] - The same RRC message (e.g., RRCReconfiguration Message) is used to deactivate the SCG and is sent from the MN to the UE.

[0097] - If SRB3 is configured, then it is the same RRC message (e.g., RRCReconfiguration Message) that is used to deactivate SCG and is sent from SN to UE.

[0098] In a further embodiment, in case of the SN-initiated SCG deactivation procedure, configuration information regarding the behavior(s) of the UE is transmitted in at least one of the following:

[0099] - The same Xn interface message (e.g., SN Modification Required message), which initiates the SCG deactivation procedure and associated SCG configuration information, sent from the SN to the MN.

[0100] - The same RRC message (e.g., RRCReconfiguration Message), which is used to deactivate the SCG, sent from the MN to the UE.

[0101] - If SRB3 is configured, the same RRC message (e.g., RRCReconfiguration Message), which is used to deactivate the SCG, sent from the SN to the UE.

[0102] In another embodiment, when the SCG is deactivated, the UE continues the RRM measurement operation by default. When the RRM measurement operation indicates that the current link quality is worse than a configured threshold (e.g., RSRP<RLM_RSRP_threshold), the UE starts the RLM measurement operation. When the RRM measurement operation indicates that the current link quality is equal to or better than the configured threshold (e.g., RSRP>RLM_RSRP_threshold), the UE stops the RLM measurement operation.

[0103] Similarly, when the RRM measurement operation indicates that the current link quality is worse than a configured threshold (e.g., RSRP<BFD_RSRP_threshold), the UE starts the beam failure detection operation. When the RRM measurement operation indicates that the current link quality is equal to or better than the configured threshold (e.g., RSRP>BFD_RSRP_threshold), the UE stops the beam failure detection operation or the beam failure recovery operation.

[0104] In a further embodiment, the RRC message (e.g., RRCReconfiguration Message) sent from the MN to the UE for deactivating the SCG may be:

[0105] - An RRC message generated by the MN, which contains information provided by the SN via the Xn interface; or

[0106] - An RRC message generated by the SN and sent to the MN as a container (i.e., an octet string). In this case, the MN only forwards the received RRC message container from the SN to the UE without performing any processing on the received RRC message container.

[0107] The details described in all other embodiments of this application (e.g., details of the SCG (de)activation mechanism in MR-DC scenarios) are applicable. Figure 2 Examples of implementations. Furthermore, Figure 2 The details described in the embodiments are applicable Figure 1 and 3 All embodiments up to 8.

[0108] Figure 3 An exemplary flowchart illustrating an SCG deactivation procedure initiated by an MN according to some embodiments of this application is provided.

[0109] like Figure 3 As shown in the diagram, in operation 301, MN 320 (e.g., as...) Figure 1 As described and shown in the document, MN 102) will send an SN Modification Request Message containing an SCG deactivation indicator to SN 330 (e.g., as...). Figure 1 (As explained and shown in SN 103). The SCG deactivation indicator is used to initiate the SCG deactivation procedure. In other words, the SCG deactivation indicator is used to deactivate the SCG.

[0110] In operation 302, SN 330 transmits a response message to MN 320. For example, the response message may include: confirmation of the SCG deactivation procedure; or rejection of the SCG deactivation procedure. If the response message includes confirmation of the SCG deactivation procedure, then MN 320 may transmit the status information of(several) SCells associated with the SCG and configuration information regarding(several) behaviors of UE 310 to UE 310 (e.g., such as...). Figure 1 (UE 101 as described and shown in the document).

[0111] In one instance, SN 330 sends an SN Modification Request Acknowledge Message to MN320 containing at least one of "status information of (several) SCells related to the SCG" and "SCG deactivation configuration information." The SN Modification Request Acknowledge Message indicates confirmation of the SCG deactivation procedure. For example, the SN Modification Request Acknowledge Message contains status information of (several) SCells, as described above... Figure 2The embodiments shown and illustrated herein. For example, the status information may include the deactivated status of SCell(s) within SCell(s). The SCG deactivation configuration information in the SN Modification Request Acknowledge Message is associated with the SCG deactivation procedure. The SCG deactivation configuration information may include configuration information regarding the behavior(s) of UE(s).

[0112] In operation 303, MN 320 transmits an RRCReconfiguration Message to UE 310. The RRCReconfiguration Message contains at least one of "status information of (several) SCells" and "SCG deactivation configuration information". For example, the RRCReconfiguration Message contains configuration information about (several) behaviors of UE 310.

[0113] According to an embodiment, the RRCReconfigurationMessage sent from MN 320 to UE 310 to deactivate SCG can be:

[0114] - An RRC message generated by MN 320, containing information provided by SN 330 via the Xn interface; or

[0115] - An RRC message generated by SN 330 and sent to MN 320 as a container (i.e., an octet string). In this case, MN 320 simply forwards the received RRC message container from SN 330 to UE 310 without performing any processing on the received RRC message container.

[0116] The details described in all other embodiments of this application (e.g., details of the SCG deactivation mechanism in MR-DC scenarios) are applicable. Figure 3 Examples of implementations. Furthermore, Figure 3 The details described in the embodiments are applicable Figure 1 , 2 And all embodiments from 4 to 8.

[0117] Figure 4 An exemplary flowchart illustrating an SCG activation procedure initiated by an MN according to some embodiments of this application is provided.

[0118] like Figure 4 As shown in the diagram, in operation 401, MN 420 (e.g., as...) Figure 1The MN 102 described and shown in the document will send an SN Modification Request Message containing an SCG activation indicator to SN 430 (e.g., as described in the document). Figure 1 (as described and shown in SN 103). The SCG activation indicator is used to initiate the SCG activation process. In other words, the SCG activation indicator is used to activate the SCG.

[0119] In operation 402, SN 430 transmits a response message to MN 420. For example, the response message may include confirmation of the SCG activation procedure or rejection of the SCG activation procedure. If the response message includes confirmation of the SCG activation procedure, then MN 420 may transmit the status information of (several) SCells associated with the SCG to UE 410 (e.g., such as...). Figure 1 (UE 101 as described and shown in the document).

[0120] In one instance, SN 430 transmits an SNModification Request Acknowledge Message containing status information of (several) SCells related to the SCG to MN 420. The SN Modification Request Acknowledge Message indicates confirmation of the SCG activation procedure. The SN Modification Request Acknowledge Message may contain status information of (several) SCells, as described above. Figure 2 The embodiments shown and illustrated herein. For example, the state information includes the activated state of SCell(s) within SCell(s).

[0121] In operation 403, MN 420 transmits an RRCReconfigurationMessage containing status information of(several) SCells to UE 410. Optionally, the RRCReconfigurationMessage may further contain an explicit indicator for activating the SCG (i.e., an indicator for initiating the SCG activation procedure).

[0122] The details described in all other embodiments of this application (e.g., details of the SCG activation mechanism in MR-DC scenarios) are applicable. Figure 4 Examples of implementations. Furthermore, Figure 4 The details described in the embodiments are applicable Figures 1 to 3 And all embodiments from 5 to 8.

[0123] Figure 5This document describes an example flowchart of an SCG deactivation procedure initiated by an SN according to some embodiments of this application.

[0124] like Figure 5 As shown in the diagram, in operation 501, SN 530 (e.g., as...) Figure 1 The SN 103 described and shown will send an SNModification Required Message containing at least one of "(several) SCell status information" and "SCG deactivation configuration information" to the MN 520 (e.g., as described). Figure 1 (As described and shown in the text, MN102). The SN Modification Required Message may contain status information of (several) SCells, as described above. Figure 2 The embodiments shown and illustrated herein. For example, the status information of (a plurality of) SCells includes the deactivated state of the SCells within (a plurality of) SCells. For example, SCG deactivation configuration information may include information about UE 510 (e.g., as shown in the example). Figure 1 Configuration information for (some) behaviors of UE 101 as described and shown in the document.

[0125] In operation 502, MN 520 transmits the RRCReconfiguration Message to UE 510. The RRCReconfiguration Message contains SCG deactivation configuration information and status information of (several) SCells.

[0126] In operation 503, UE 510 transmits the RRCReconfigurationComplete Message to MN 520. In operation 504, MN 520 transmits the SN Modification Confirm Message to SN 530.

[0127] According to an embodiment, the RRCReconfigurationMessage sent from MN 520 to UE 510 to deactivate SCG can be:

[0128] - An RRC message generated by MN 520, containing information provided by SN 530 via the Xn interface; or

[0129] - An RRC message generated by SN 530 and sent as a container (i.e., an octet string) to MN 520. In this case, MN 520 simply forwards the received RRC message container from SN 530 to UE 510 without performing any processing on the received RRC message container.

[0130] The details described in all other embodiments of this application (e.g., details of the SCG deactivation mechanism in MR-DC scenarios) are applicable. Figure 5 Examples of implementations. Furthermore, Figure 5 The details described in the embodiments are applicable Figures 1 to 4 And all embodiments 6 to 8.

[0131] Figure 6 An exemplary flowchart illustrating an SCG activation procedure initiated by an SN according to some embodiments of this application is provided.

[0132] like Figure 6 As shown in the diagram, in operation 601, SN 630 (e.g., as...) Figure 1 The SN 103 described and shown in the document will transmit an SN Modification Required Message containing the status information of (several) SCell activated SCGs to the MN620 (e.g., as shown in the document). Figure 1 As described and shown in MN 102). The SN Modification Required Message contains status information of (several) SCells, as described above. Figure 2 As shown and illustrated in the embodiments. Based on the received status information of one or more SCells, MN 620 can determine whether the SCG has been activated. For example, the status information includes the activation status of SCell(s) within SCell(s). Then, based on the activation status of SCell(s) within SCell(s), MN 620 can determine that the SCG has been activated.

[0133] Optionally, the SN Modification Required Message in operation 601 may further include an explicit indicator for activating the SCG. The explicit indicator for activating the SCG may also be named an indicator for initiating an SCG activation procedure or the like.

[0134] In operation 602, MN 620 transmits an RRCReconfiguration Message containing the status information of (several) SCell activated SCGs to UE 610 (e.g., as shown in the image). Figure 1 (as described and shown in UE 101). For example, the status information of (a number of) SCells includes the activated status of the SCells within (a number of) SCells. Optionally, the RRCReconfiguration Message may further include an explicit indicator for activating the SCG (i.e., an indicator for initiating the SCG activation procedure).

[0135] In operation 603, UE 610 transmits the RRCReconfigurationComplete Message to MN 620. In operation 604, MN 620 transmits the SN Modification Confirm Message to SN 630.

[0136] The details described in all other embodiments of this application (e.g., details of the SCG deactivation mechanism in MR-DC scenarios) are applicable. Figure 6 Examples of implementations. Furthermore, Figure 6 The details described in the embodiments are applicable Figures 1 to 5 All embodiments of 7 and 8.

[0137] Figure 7 This document describes a flowchart illustrating a method for receiving status information of (a number of) SCells according to some embodiments of this application. The exemplary method 700 may be provided by a UE (e.g., UE 101, UE 310, UE 410, UE 510, or UE 610, such as...). Figure 1 and 3 (As shown and described in any of 6). Although described with respect to the UE, it should be understood that (some) other devices may be configured to perform such... Figure 7 The methods shown and explained in the document.

[0138] In such Figure 7 In the instance method 700 shown, in operation 701, the UE (e.g., as...) Figure 1 The UE 101 shown and described receives an RRC reconfiguration message (e.g., an RRCReconfiguration Message). The RRC reconfiguration message contains status information for (several) SCells associated with the SCG. For example... Figure 2 The status information of (a few) SCells shown and described herein contains information applicable to the status information of (a few) SCells in operation 701.

[0139] In an embodiment, the state information of (a plurality of) SCells includes: the activated state of the SCell; the deactivated state of the SCell; or the dormant state of the SCell. The state information of (a plurality of) SCells may be derived from an SN (e.g., such as...). Figure 1 The SN 103 decision is explained and shown in the document. In the example, if SRB3 is configured, the status information of (several) SCells is transmitted directly from the SN to the UE. In a further example, if SRB3 is not configured, the status information of (several) SCells is transmitted from the SN to the UE via the master node (MN).

[0140] In one embodiment, the RRC reconfiguration message is sent by the MN (e.g., as...). Figure 1 The MN102 described and shown herein generates and includes components generated by SN (e.g., such as...). Figure 1 The information provided by SN 103, as described and shown in the document. In another embodiment, the RRC reconfiguration message is generated by the SN as a container (e.g., an octet string container) and forwarded from the SN to the MN.

[0141] In operation 702, the UE transmits an RRC reconfiguration complete message (e.g., RRC reconfigurationcomplete Message).

[0142] exist Figure 7 In some embodiments, if the SCG has been deactivated and if the UE receives configuration information about (some) behaviors of the UE, then the UE continues the RRM measurement operation.

[0143] In an embodiment, if the results of (a number of) measurements of an RRM measurement operation indicate that the current link quality of the UE is worse than a threshold, then the UE may initiate at least one of the following: an RLM measurement operation; a beam failure detection operation; and a beam failure recovery operation.

[0144] In a further embodiment, if the results of (a few) measurements of the RRM measurement operation indicate that the current link quality of the UE is equal to or better than a threshold, then the UE may stop at least one of the following: the RLM measurement operation; the beam failure detection operation; and the beam failure recovery operation.

[0145] exist Figure 7 In some embodiments, the UE may receive a message indicating that the SCell of the SCG is activated. After receiving the message, the UE may check whether the SCG has been deactivated. If the SCG has been deactivated, the UE may activate the SCG. For example, during SCG activation, the UE may begin a random access (RA) procedure for the SCG.

[0146] Specifically, in this embodiment, the MN or SN can activate a deactivated SCG by activating a SCell within the SCG (e.g., by setting the SCell state to "activated"). In this embodiment, it is not necessary to explicitly indicate the exact SCG activation or deactivation indicator. In conventional solutions, an explicit SCG activation / deactivation indicator is used when the MN or SN decides to activate (deactivate) the SCG. From the UE's perspective, after receiving an RRCReconfiguration Message from the MN indicating that a SCell belonging to the SCG is activated, the UE will first check whether the relevant SCG is currently deactivated. If the SCG is currently deactivated, the UE will activate the SCG, for example, by initiating a RA procedure for the SCG.

[0147] The details described in all other embodiments of this application (e.g., details of the SCG activation mechanism in MR-DC scenarios) are applicable. Figure 7 Examples of implementations. Furthermore, Figure 6 The details described in the embodiments are applicable Figures 1 to 6 All embodiments of 8.

[0148] Figure 8 This application illustrates exemplary block diagrams of a device according to some embodiments of the present application. In some embodiments of the present application, device 800 may be a UE, MN, or SN, which may at least perform... Figures 2 to 7 The method described in any of them.

[0149] like Figure 8 As shown, device 800 may include at least one receiver 802, at least one transmitter 804, at least one non-transitory computer-readable medium 806, and at least one processor 808, said processor 808 being coupled to at least one receiver 802, at least one transmitter 804, and at least one non-transitory computer-readable medium 806.

[0150] Despite Figure 8 In this application, elements such as at least one receiver 802, at least one transmitter 804, at least one non-transitory computer-readable medium 806, and at least one processor 808 are described in the singular, but plural forms are also contemplated unless explicitly stated to be limited to the singular. In some embodiments of this application, at least one receiver 802 and at least one transmitter 804 are combined into a single device, such as a transceiver. In some embodiments of this application, device 800 may further include input devices, memory, and / or other components.

[0151] In some embodiments of this application, at least one non-transitory computer-readable medium 806 may store computer-executable instructions programmed to perform the operation of the method using at least one receiver 802, at least one transmitter 804, and at least one processor 808, for example, as given... Figures 2 to 7 As described in any of them.

[0152] Those skilled in the art will understand that the operation of the methods described in connection with the aspects disclosed herein can be directly embodied in hardware, a software module executed by a processor, or a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. Additionally, in some aspects, the operation of the methods may reside as one or any combination or set of code and / or instructions on a non-transitory computer-readable medium, which may be incorporated into a computer program product.

[0153] While this disclosure has been described through specific embodiments, many alternatives, modifications, and variations will be apparent to those skilled in the art. For example, various components of the described embodiments may be interchanged, added, or substituted in other embodiments. Moreover, not all elements in each figure are essential to the operation of the disclosed embodiments. For example, those skilled in the art will be able to make and use the teachings of this disclosure by simply employing the elements of the independent claims. Therefore, the embodiments of this disclosure as set forth herein are intended to be illustrative and not restrictive. Various changes may be made without departing from the spirit and scope of this disclosure.

[0154] In this document, the terms “includes,” “including,” or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but may also include other elements not expressly listed or inherent to the process, method, article, or apparatus. Without further limitations, an element beginning with “a,” “an,” or the like does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element. Furthermore, the term “another” is defined as at least a second or more. As used herein, the terms “having” and the like are defined as “comprising.”

Claims

1. A radio access node for wireless communication, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory and configured such that the radio access node: In response to determining that an active secondary cell group (SCG) is activated, the corresponding status information of each SCell in a plurality of secondary cell SCells associated with the SCG is transmitted; and In response to determining that the SCG is deactivated, the corresponding status information is transmitted and configuration information regarding the behavior of the user equipment (UE) is transmitted, wherein the configuration information regarding the behavior of the UE includes information indicating whether the UE performs a beam failure detection operation when the SCG is deactivated.

2. The radio access node according to claim 1, wherein the radio access node includes a master node MN or an auxiliary node SN.

3. The radio access node according to claim 1, wherein the corresponding status information includes at least one of the following: The activated state of the SCells within the plurality of SCells; The deactivated state of the SCell; or The sleep state of the SCell.

4. The radio access node according to claim 1, wherein the corresponding status information includes at least one of the following: The following mapping relationship exists between each of the plurality of SCells and the target state of each of the plurality of SCells after the SCG is activated; The following mapping relationships exist: the target state of each of the plurality of SCells after deactivating the SCG, and the configuration information regarding the behavior of the UE; The following mapping relationship exists between each SCell in the first subset of the plurality of SCells and the target state of each SCell in the first subset after the SCG is activated; or The following mapping relationships exist: each SCell in the second subset of the plurality of SCells, the target state of each SCell in the second subset after deactivating the SCG, and the configuration information regarding the behavior of the UE.

5. The radio access node of claim 1, wherein the at least one processor is configured to cause the radio access node to: Receive the corresponding status information from the auxiliary node SN; Based on the corresponding status information, determine whether the SCG has been activated; and In response to the corresponding status information containing the activated status of SCells among the plurality of SCells, it is determined that the SCG has been activated.

6. The radio access node of claim 1, wherein the at least one processor is configured to cause the radio access node to transmit the corresponding status information to the UE in response to determining activation of the SCG, and wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

7. The radio access node of claim 1, wherein the at least one processor is configured to cause the radio access node to, in response to determining to deactivate the SCG: Receive at least one of the following from the auxiliary node SN: The configuration information regarding the behavior of the UE; or The corresponding status information; and At least one of the following will be transmitted to the UE: The configuration information regarding the behavior of the UE; or The corresponding status information.

8. The radio access node of claim 1, wherein in response to determining activation of the SCG, the at least one processor is configured to cause the radio access node to: transmit the corresponding status information to the master node MN, and wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

9. The radio access node of claim 1, wherein the at least one processor is configured to cause the radio access node to: In response to determining to deactivate the SCG, at least one of the following is emitted to the master node MN: The configuration information regarding the behavior of the UE; or The corresponding status information.

10. A method performed by a radio access node, comprising: In response to determining that an active secondary cell group (SCG) is activated, the corresponding status information of each of the multiple secondary cell SCells associated with the SCG is transmitted. and In response to determining that the SCG is deactivated, the corresponding status information is transmitted and configuration information regarding the behavior of the user equipment (UE) is transmitted, wherein the configuration information regarding the behavior of the UE includes information indicating whether the UE performs a beam failure detection operation when the SCG is deactivated.

11. The method of claim 10, wherein the method is executed by a master node MN or an auxiliary node SN.

12. The method of claim 10, wherein the corresponding status information comprises at least one of the following: The activated state of the SCells within the plurality of SCells; The deactivated state of the SCell; or The sleep state of the SCell.

13. The method of claim 10, wherein the corresponding status information comprises at least one of the following: The following mapping relationship exists between each of the plurality of SCells and the target state of each of the plurality of SCells after the SCG is activated; The following mapping relationships exist: the target state of each of the plurality of SCells after deactivating the SCG, and the configuration information regarding the behavior of the UE; The following mapping relationship exists between each SCell in the first subset of the plurality of SCells and the target state of each SCell in the first subset after the SCG is activated; or The following mapping relationships exist: each SCell in the second subset of the plurality of SCells, the target state of each SCell in the second subset after deactivating the SCG, and the configuration information regarding the behavior of the UE.

14. The method of claim 10, further comprising: Receive the corresponding status information from the auxiliary node SN; Based on the corresponding status information of the multiple SCells, determine whether the SCG has been activated; and In response to the corresponding status information containing the activated status of SCells among the plurality of SCells, it is determined that the SCG has been activated.

15. The method of claim 10, further comprising: In response to determining that the SCG is activated, the corresponding status information is transmitted to the UE, wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

16. The method of claim 10, further comprising: In response to determining to deactivate the SCG, at least one of the following is received from the auxiliary node SN: The configuration information regarding the behavior of the UE; or The corresponding status information; and At least one of the following will be transmitted to the UE: The configuration information regarding the behavior of the UE; or The corresponding status information.

17. The method of claim 10, further comprising: In response to determining that the SCG is activated, the corresponding status information is transmitted to the master node MN, wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

18. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured such that the processor: In response to determining that an active secondary cell group (SCG) is activated, the corresponding status information of each SCell in a plurality of secondary cell SCells associated with the SCG is transmitted; and In response to determining that the SCG is deactivated, the corresponding status information is transmitted and configuration information regarding the behavior of the user equipment (UE) is transmitted, wherein the configuration information regarding the behavior of the UE includes information indicating whether the UE performs a beam failure detection operation when the SCG is deactivated.

19. The processor of claim 18, wherein the processor comprises a master node MN or an auxiliary node SN.

20. The processor of claim 18, wherein the corresponding status information includes at least one of the following: The activated state of the SCells within the plurality of SCells; The deactivated state of the SCell; or The sleep state of the SCell.

21. The processor of claim 18, wherein the corresponding status information comprises at least one of the following: The following mapping relationship exists between each of the plurality of SCells and the target state of each of the plurality of SCells after the SCG is activated; The following mapping relationships exist: the target state of each of the plurality of SCells after deactivating the SCG, and the configuration information regarding the behavior of the UE; The following mapping relationship exists between each SCell in the first subset of the plurality of SCells and the target state of each SCell in the first subset after the SCG is activated; or The following mapping relationships exist: each SCell in the second subset of the plurality of SCells, the target state of each SCell in the second subset after deactivating the SCG, and the configuration information regarding the behavior of the UE.

22. The processor of claim 18, wherein the at least one controller is configured to cause the processor to: Receive the corresponding status information from the auxiliary node SN; Based on the corresponding status information of the multiple SCells, determine whether the SCG has been activated; and In response to the corresponding status information containing the activated status of SCells among the plurality of SCells, it is determined that the SCG has been activated.

23. The processor of claim 18, wherein the at least one controller is configured to cause the processor to: In response to determining that the SCG is activated, the corresponding status information is transmitted to the UE, wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

24. The processor of claim 18, wherein the at least one controller is configured to cause the processor to: In response to determining to deactivate the SCG, at least one of the following is received from the auxiliary node SN: The configuration information regarding the behavior of the UE; or The corresponding status information; and At least one of the following will be transmitted to the UE: The configuration information regarding the behavior of the UE; or The corresponding status information.

25. The processor of claim 18, wherein the at least one controller is configured to cause the processor to: In response to determining that the SCG is activated, the corresponding status information is transmitted to the master node MN, wherein the corresponding status information includes the activated status of the SCells among the plurality of SCells.

Images