WO2022141491A1 - Method, device and computer program product for wireless communication - Google Patents

Method, device and computer program product for wireless communication Download PDF

Info

Publication number
WO2022141491A1
WO2022141491A1 PCT/CN2020/142355 CN2020142355W WO2022141491A1 WO 2022141491 A1 WO2022141491 A1 WO 2022141491A1 CN 2020142355 W CN2020142355 W CN 2020142355W WO 2022141491 A1 WO2022141491 A1 WO 2022141491A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
scg
cell
target
target cell
Prior art date
Application number
PCT/CN2020/142355
Other languages
English (en)
French (fr)
Inventor
Mengjie ZHANG
He Huang
Jing Liu
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to CN202080106704.0A priority Critical patent/CN116349387A/zh
Priority to EP20967830.9A priority patent/EP4218308A4/en
Priority to PCT/CN2020/142355 priority patent/WO2022141491A1/en
Publication of WO2022141491A1 publication Critical patent/WO2022141491A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00698—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using different RATs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • This document is directed generally to wireless communications.
  • MR-DC Multi-Radio Dual Connectivity
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • the present disclosure relates to methods, devices, and computer program products for wireless communication, which can acquire a more accurate terrestrial network location of the terminal.
  • the wireless communication method includes: receiving, by a wireless communication terminal, a radio resource control, RRC, message including conditional reconfiguration from a wireless communication node; wherein the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell; wherein the candidate cell configuration includes a first indication of a secondary cell group, SCG, activation state of the candidate cell; selecting, by the wireless communication device, based on one or more execution conditions, a target cell, to apply a cell configuration of the target cell in the conditional reconfiguration; and determining, by the wireless communication device, the SCG activation state of the target cell, according to the first indication of an SCG activation state of the target cell.
  • RRC radio resource control
  • the wireless communication method includes: transmitting, by a wireless communication node, a radio resource control, RRC message including conditional reconfiguration to a wireless communication terminal; wherein the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell; wherein the candidate cell configuration includes a first indication of a secondary cell group, SCG, activation state of the candidate cell; and wherein the first RRC message causes the wireless communication terminal to: select, based on one or more execution conditions, a target cell of a wireless communication node, to apply a cell configuration of the target cell in the conditional reconfiguration; and determining the SCG activation state of the target cell according to the first indication of an SCG activation state of the target cell.
  • the wireless communication method includes: transmitting, by a target secondary wireless communication node, SN, a cell configuration of a target cell served by the target SN to a wireless communication terminal via a wireless communication node; wherein the cell configuration includes a first indication of a secondary cell group, SCG, activation state of the target cell.
  • the cell configuration is applied by the wireless communication terminal in response to one or more execution conditions for the target cell is met.
  • the wireless communication terminal includes a communication unit and a processor.
  • the processor is configured for: receiving, through the communication unit, a radio resource control, RRC, message including conditional reconfiguration from a wireless communication node; wherein the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell; wherein the candidate cell configuration includes a first indication of a secondary cell group, SCG, activation state of the candidate cell; and selecting based on one or more execution conditions, a target cell, to apply a cell configuration of the target cell in the conditional reconfiguration; and determining, by the wireless communication device, the SCG activation state of the target cell, according to the first indication of an SCG activation state of the target cell.
  • RRC radio resource control
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured for transmitting, through the communication unit, a radio resource control, RRC message including conditional reconfiguration to a wireless communication terminal; wherein the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell; wherein the candidate cell configuration includes a first indication of a secondary cell group, SCG, activation state of the candidate cell, wherein the first RRC message causes the wireless communication terminal to: select, based on one or more execution conditions, a target cell of a wireless communication node, to apply a cell configuration of the target cell in the conditional reconfiguration; and determining the SCG activation state of the target cell according to the first indication of an SCG activation state of the target cell.
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured for transmitting, through the communication unit, a cell configuration of a target cell served by the target SN to a wireless communication terminal via a wireless communication node; wherein the cell configuration includes a first indication of a secondary cell group, SCG, activation state of the target cell.
  • the cell configuration is applied by the wireless communication terminal in response to one or more execution conditions for the target cell is met.
  • the wireless communication method further includes: receiving, by the wireless communication terminal, an SCG deactivation command from the wireless communication node; and considering, by the wireless communication device, the SCG activation state of the target cell as deactivated state, based on the SCG deactivation command.
  • conditional reconfiguration refers to at least one of: a conditional handover configuration including SCG configuration, a conditional PSCell addition/change configuration, or a conditional handover configuration including a conditional PSCell addition/change configuration.
  • the candidate cell configuration includes at least one of: RRC reconfiguration from the wireless communication node or RRC reconfiguration from the target secondary wireless communication node, SN.
  • the first indication of an SCG activation state of the candidate cell is configured by at least one of: the wireless communication node, or the target SN.
  • a cell configuration of the target cell in the conditional reconfiguration is applied by the wireless communication terminal in response to at least one of: one or more execution conditions for the target cell is met or an activation of the SCG of the target cell.
  • an SCG activation state of the target cell is considered as deactivated, and the method further including: performing, by the wireless communication terminal, a random access, RA, procedure to the target cell in response to at least one of: one or more execution conditions of the target cell is met or an activation of the SCG of the target cell.
  • an activation of the SCG is in response to at least one of: a reception of an activation command from the wireless communication node or an arrival of UL data transmission to the SN.
  • the wireless communication method includes transmitting, by the wireless communication terminal, a first RRC response message to the wireless communication node including an embedded second RRC response message to the target SN serving the target cell.
  • the second RRC response message includes a second indication of an SCG activation state of the target cell to a target SN serving the target cell in response to at least one of: the first indication of an SCG activation state in the target cell configuration is configured by the wireless communication node, or a reception of the SCG deactivation command from the wireless communication node.
  • the first RRC response message includes a second indication of an SCG activation state of the target cell to the wireless communication node in response to at least one of: the first indication of an SCG activation state in the target cell configuration is configured by the target SN, or a reception of the SCG deactivation command from the wireless communication node.
  • a radio link failure is detected for the master cell group, MCG, a fast MCG recovery is configured, and an SCG activation state of the cell is deactivated, the method further including: performing, by the wireless communication terminal, an activation of the SCG; and reporting, by the wireless communication terminal, the radio link failure to the wireless communication node via the SCG.
  • the method further including transmitting, by the wireless communication node, an SCG deactivation command to the wireless communication terminal.
  • the SCG deactivation command causes the wireless communication terminal to consider, the SCG activation state of the target cell as deactivated state.
  • the first indication of an SCG activation state of the candidate cell is configured by the wireless communication node, or the target secondary wireless communication node, SN.
  • the method further including receiving, by the wireless communication node, a first RRC response message from the wireless communication terminal including an embedded second RRC response message to the target SN serving the target cell; and transmitting, by the wireless communication node, an Xn/X2 message including an embedded second RRC response message to the target SN serving the target cell.
  • the second RRC response message includes a second indication of an SCG activation state of the target cell to a target SN serving the target cell in response to at least one of: the first indication of an SCG activation state in the target cell configuration is configured by the wireless communication node, or a reception of the SCG deactivation command from the wireless communication node.
  • the first RRC response message includes a second indication of an SCG activation state of the target cell to the wireless communication node in response to at least one of: the first indication of an SCG activation state in the target cell configuration is configured by the target SN, or a reception of the SCG deactivation command from the wireless communication node.
  • the Xn/X2 message includes a third indication of an SCG activation state of the target cell to the target SN in response to at least one of: the first indication of an SCG activation state in the target cell configuration is configured by the wireless communication node, or a reception of the SCG deactivation command from the wireless communication node.
  • the first indication of an SCG activation state of the target cell causes the wireless communication terminal to: determine, the SCG activation state of the target cell.
  • the method further including: receiving, by the target SN, a second RRC response message from the wireless communication terminal via the wireless communication node; wherein the second RRC response message is embedded in a first RRC response message from the wireless communication terminal to the wireless communication node.
  • the first RRC response message includes a second indication of an SCG activation state of the target cell to the wireless communication node in response to the first indication of an SCG activation state in the cell configuration.
  • the present disclosure relates to a computer program product including a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method recited in any one of foregoing methods.
  • the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
  • FIG. 1 shows a scenario of SN change according to an embodiment of the present disclosure.
  • FIG. 2 shows a MN initiated Conditional PSCell addition/change (CPAC) procedure according to an embodiment of the present disclosure.
  • CPAC Conditional PSCell addition/change
  • FIG. 3 shows an example of a schematic diagram of a wireless communication terminal according to an embodiment of the present disclosure.
  • FIG. 4 shows an example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure.
  • FIG. 5 shows an example of a schematic diagram of another wireless communication node according to another embodiment of the present disclosure.
  • FIG. 6 illustrates a wireless communication method according to an embodiment of the present disclosure.
  • FIG. 7 illustrates another wireless communication method according to an embodiment of the present disclosure.
  • FIG. 8 illustrates another wireless communication method according to an embodiment of the present disclosure.
  • the CHO is defined as a handover that is executed by the UE when execution condition (s) is met.
  • the UE starts evaluating the execution condition (s) upon receiving the CHO configuration, and stops evaluating the execution condition (s) once handover is triggered.
  • the CHO configuration includes the candidate primary cell (PCell) configuration generated by the candidate target node and the corresponding execution condition (s) for the candidate cell.
  • a UE in the wireless network can operate in Dual Connectivity (DC) , including intra Evolved Universal Terrestrial Radio Access (intra-E-UTRA) DC or Multi-Radio DC (MR-DC) .
  • DC Dual Connectivity
  • intra-E-UTRA Evolved Universal Terrestrial Radio Access
  • MR-DC Multi-Radio DC
  • intra-E-UTRA DC both of the MN and the SN provide E-UTRA access.
  • NR new radio
  • NR new radio
  • One or multiple serving cells can be configured both on the MN and the SN.
  • Serving cells configured on (or served by) an MN are defined as a Master Cell Group (MCG) while serving cells configured on (or served by) an SN are defined as a Secondary Cell Group (SCG) .
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • a Radio Bearer can be configured to utilize either the MCG resources (e.g., MCG bearer) or SCG resources (e.g., SCG bearer) or both MCG and SCG resources (e.g., split bearer) .
  • FIG. 1 illustrates one possible scenario of SN change according to an embodiment of the present disclosure.
  • There are three network nodes e.g., three Base Stations (BSs) ) in FIG. 1, which are MN, SN1 and SN2.
  • Cell 1 Cell 2 and Cell 3 are the corresponding cells generated/served by MN, SN1 and SN2, respectively.
  • Cell 2 and Cell 3 are cells of the secondary cell group (SCG) , defined as primary SCG cell (PSCell) .
  • SCG secondary cell group
  • PSCell primary SCG cell
  • the interfaces X are deployed between MN and SN1, and between MN and SN2, respectively.
  • the UE is operating in DC with MN and SN1.
  • the SN serving the UE is changed from SN1 to SN2, which is referred to as SN change.
  • SN change can be initiated either by MN or source SN (i.e., SN1) .
  • CPAC Conditional PSCell Addition/Change
  • the CPAC is defined as a PSCell addition/change that is executed by the UE when execution condition (s) is met.
  • the UE starts evaluating the execution condition (s) upon receiving the CPAC configuration, and stops evaluating the execution condition (s) once the PSCell addition/change is triggered.
  • the CPAC configuration includes the candidate PSCell configuration generated by the candidate SN and the corresponding execution condition (s) for the candidate PSCell.
  • the CPAC procedure can be triggered by either the MN or the SN, so it can be categorized as MN initiated CPAC and SN initiated CPAC. Besides, the CPAC procedure can be involved with MN or without MN, so it can be classified as CPAC with MN involvement and CPAC without MN involvement (i.e., intra-SN CPC (Conditional PSCell Change) without MN involvement) as well.
  • FIG 2 illustrates the MN initiated CPAC procedure according to an embodiment of the present disclosure.
  • the execution condition (s) is decided by the MN.
  • the source SN is denoted as S-SN
  • the target SN is denoted as T-SN_1.
  • the MN sends an SN addition request message to the target SN.
  • the MN may include measurement results related to the target SN and a CPAC indication to indicate the it is a conditional based procedure.
  • the target SN responds an SN addition request acknowledge to the MN, including the candidate PSCell (s) configuration.
  • the MN determines the execution condition (s) for the candidate PSCell.
  • the MN sends an RRCReconfiguration message including a CPAC configuration to the UE.
  • the CPAC configuration includes at least the candidate PSCell configuration (i.e., an RRCReconfiguration message generated by the target SN) and the corresponding execution condition (s) .
  • the UE replies to an RRCReconfigurationComplete message to the MN to confirm the reception of the RRCReconfiguration message.
  • the UE keeps connection with the source SN and starts evaluating the execution condition (s) .
  • the UE selects the related cell as the target PSCell and triggers the execution of CPAC to access to the target SN.
  • the UE sends an RRCReconfigurationComplete message to the MN.
  • the RRCReconfigurationComplete for the MN message includes an embedded RRCReconfigurationComplete for the target SN.
  • the MN transfers the SN Reconfiguration Complete message (i.e., the embedded RRCReconfigurationComplete) to the target SN.
  • the UE performs a Random Access (RA) procedure towards the target PSCell of the SN. Note that the order the UE sends the RRCReconfigurationComplete message and performs the Random Access procedure towards the SCG is not defined (i.e., the order of S270, S280 and S290 is not defined and/or can be changed) .
  • RA Random Access
  • the execution condition (s) is decided by the SN.
  • the procedure is similar to MN initiated CPAC procedure except that the source SN firstly sends an SN change required message to the MN to request the initiation of the conditional SN change procedure.
  • the SN change required message may include the execution condition (s) generated by the source SN.
  • the SN can send the RRCReconfiguration including CPC configurations to the UE via SRB3 directly if SRB3 is configured.
  • SRB3 is a signaling radio bearer between the UE and the SN.
  • the SN sends the RRCReconfiguration to the MN, and the MN transfers the message to the UE transparently.
  • NR UE power consumption is 3 to 4 times higher than UE power consumption in long term evolution (LTE) .
  • LTE long term evolution
  • a MN provides the basic coverage.
  • deactivating and activating the SN may be applied to reduce power consumption of the UE and the network devices.
  • the network can send a deactivation command to the UE to deactivate the SCG. Accordingly, the UE may suspend data transmission on the deactivated SCG, stop Physical Downlink Control Channel (PDCCH) monitoring on the PSCell, etc., to reduce power consumption.
  • the NW can send an activation command to the UE to active the SCG again.
  • Aspect 1 the coexistence of conditional reconfiguration and SCG deactivation/activation
  • the conditional reconfiguration includes the conditional handover (CHO) and the conditional PSCell addition/change (CPAC) .
  • the CHO is defined as a PCell change that is executed by the UE when execution condition (s) is met.
  • the CPAC is defined as a PSCell addition/change that is executed by the UE when execution condition (s) is met.
  • the CHO configuration may also include SCG configuration for PSCell addition/change, so that the target node can have conditional PCell change with PSCell addition/change. The following embodiments may be considered to have PSCell addition/change in conditional reconfiguration:
  • Embodiment A CPAC
  • the conditional reconfiguration for CPAC includes execution condition (s) for the candidate PSCell and the RRC container (e.g., the CPAC container, the field condRRCReconfig in RRCReconfiguration message) including the candidate PSCell configuration generated by the candidate SN, and may also including some MN-part configurations (e.g., Data Radio Bearer (DRB) level configuration, and corresponding cell group level configuration, including the reconfiguration for the purpose of capability coordination) .
  • DRB Data Radio Bearer
  • the UE upon the execution condition (s) is met, the UE triggers the conditional PSCell addition/change.
  • Embodiment B CHO with MR-DC
  • the conditional reconfiguration for CHO includes execution condition (s) for the candidate PCell or/and PSCell and the RRC container (e.g., the CHO container, the field condRRCReconfig in RRCReconfiguration message) including both the MCG and SCG configurations for the candidate PCell and PSCell.
  • execution condition s
  • the RRC container e.g., the CHO container, the field condRRCReconfig in RRCReconfiguration message
  • the UE upon the execution condition (s) is met, performs the conditional PCell change with/without PSCell change.
  • Embodiment C CHO with cascaded CPAC
  • the conditional reconfiguration for CHO includes execution condition (s) for the candidate PCell and the RRC container (e.g., the CHO container, the field condRRCReconfig in RRCReconfiguration message) including candidate PCell configuration.
  • the RRC container also includes a cascaded CPAC configuration, which contains execution condition (s) for the candidate PSCell and the RRC container (e.g., the CPAC container, the field condRRCReconfig in RRCReconfiguration message) including the candidate PSCell configuration.
  • the UE upon the execution condition (s) for the candidate PCell is met, the UE performs conditional PCell change.
  • PCell change is executed successfully, the UE starts evaluating the execution condition (s) for the candidate PSCell.
  • CPAC execution condition (s) is met, the UE performs conditional PSCell change/addition.
  • conditional reconfiguration e.g., for PSCell addition/change or PCell change with PSCell addition/change
  • SCG activation state when combining the conditional reconfiguration (e.g., for PSCell addition/change or PCell change with PSCell addition/change) with the SCG activation state, the following cases can be considered:
  • Aspect 1 -Case 1 SCG activation state (activated/deactivated) is configured in the conditional reconfiguration
  • the NW can directly configure the SCG activation state for the candidate PSCell (s) when configuring/preparing the conditional reconfiguration (e.g., CPAC, CHO with MR-DC, CHO with cascaded CPAC) .
  • conditional reconfiguration e.g., CPAC, CHO with MR-DC, CHO with cascaded CPAC
  • conditional reconfiguration with MN involvement procedure e.g., CPAC with MN involvement, CHO with MR-DC
  • the RRC container e.g., the condRRCReconfig
  • the SCG activation state in the conditional reconfiguration container e.g., the condRRCReconfig
  • the MN decides the SCG activation state (e.g., deactivated or activated) for the candidate cell in the conditional reconfiguration container, and the MN includes the SCG state indication (e.g., scgState) in the MN RRC reconfiguration message.
  • the SCG activation state e.g., deactivated or activated
  • the MN includes the SCG state indication (e.g., scgState) in the MN RRC reconfiguration message.
  • the MN informs the source SCG state to the target SN via an Xn/X2 message.
  • the MN includes an indication of source SCG state in an Xn/X2 message (e.g., an SN addition request message) or an inter-node RRC message (e.g., a CG-ConfigInfo message) .
  • the target SN may decide the SCG activation state (e.g., deactivated or activated) for the candidate cell in the conditional reconfiguration container based on the source SCG state.
  • the target SN includes the SCG state indication (e.g., the scgState) in the SN RRC reconfiguration message.
  • the MN above refers to the target MN.
  • the candidate cell in this specification refers to candidate PSCell in case of CPAC; the candidate cell in this specification refers to candidate PCell or/and PSCell in case of CHO (e.g. CHO with MR-DC) .
  • the source SN In the procedure of conditional reconfiguration without MN involvement (e.g., intra-SN CPC without MN involvement) , the source SN generates the conditional reconfiguration and sends to the UE via SRB3 directly, or via the MN transparently. According to the current SCG state, the source SN decides the SCG activation state (e.g., deactivated or activated) at conditional reconfiguration container. For example, the source SN includes the SCG state indication (e.g., the scgState) in the SN RRC reconfiguration message.
  • the SCG state indication e.g., the scgState
  • the UE configures lower layers to regard/consider the SCG to be in the deactivated state when applying the RRC reconfiguration message above. Otherwise, the UE configures lower layers to regard/consider the SCG to be in activated state when applied the RRC reconfiguration message above.
  • the UE receives the SCG deactivation command (e.g., an RRC reconfiguration message, or a Medium Access Control (MAC) Control Element (CE) ) when the conditional reconfiguration is configured (i.e., the UE stores candidate cell configuration) , regardless of whether the candidate cell configuration contained in the conditional reconfiguration includes an indication of SCG state or not, there are two alternatives can be considered for the handling of the conditional reconfiguration operation:
  • the SCG deactivation command e.g., an RRC reconfiguration message, or a Medium Access Control (MAC) Control Element (CE)
  • Alt. 1 the UE stops evaluating the execution condition (s) and deletes the stored candidate cell configuration (e.g. remove all the entries within VarConditionalReconfig) and related measurement configurations.
  • Alt. 2 the UE continues evaluating the execution condition (s) , i.e., the reception of SCG deactivation command has no impact on the conditional reconfiguration operation.
  • Aspect 1 -Case 2 -Issue 1 How to consider the SCG state in the conditional reconfiguration container when receiving the SCG deactivation command from the NW?
  • the SCG configured in the conditional reconfiguration container is initially activated when adding the candidate PSCell configuration.
  • the UE receives the SCG deactivation command (e.g., an RRC reconfiguration message or a MAC CE) from the NW (e.g., the MN or the SN)
  • the NW e.g., the MN or the SN
  • the UE regards/considers the current SCG (i.e., the source SCG) to be in deactivated state.
  • the SCG configuration of candidate cell in the conditional reconfiguration container there are two alternatives can be considered for the UE to regard/consider the SCG state of candidate cell:
  • Alt. 1 the UE regards/considers the SCG of candidate cell in all stored conditional reconfiguration container to be configured as deactivated state.
  • Alt. 2 the UE regards/considers the SCG of candidate cell in the stored conditional reconfiguration container as indicated. For example, if the indication of SCG state is configured as deactivated, then regard/consider the SCG of candidate cell as deactivated; otherwise, regard/consider the SCG as activated.
  • Aspect 1 -Case 2 -Issue 2 the UE behavior when the execution condition (s) is met
  • Option 1 the UE applies the selected candidate cell configuration when the execution condition (s) is met.
  • the UE applies the selected candidate cell configuration when the execution condition (s) is met and SCG is activated again.
  • the UE receives the SCG activation command (e.g., an RRC reconfiguration message or a MAC CE) from the NW (e.g., the MN or the SN) , or the UE automatically initiates the RA procedure towards the target PSCell when UL data sent to the SN is arrived.
  • the SCG activation command e.g., an RRC reconfiguration message or a MAC CE
  • the candidate cell configuration refers to both the candidate PCell and PSCell configurations.
  • the candidate cell configuration refers to the candidate PSCell configuration.
  • the UE performs the RA procedure to the selected/target PSCell immediately (i.e., when the execution condition (s) is met) .
  • SCG activation state for the selected/target PSCell is configured/regarded as deactivated, there are several options:
  • Option 2-1 the UE performs the RA procedure to the selected/target PSCell immediately when the execution condition (s) is met.
  • Option 2-2 the UE performs the RA procedure to the selected/target PSCell when SCG is activated again.
  • the UE receives the SCG activation command (e.g., RRC reconfiguration message or MAC CE) from the NW (e.g., the MN or the SN) , or the UE automatically initiates the RA procedure towards the target PSCell when the UL data sent to the SN is arrived.
  • the SCG activation command e.g., RRC reconfiguration message or MAC CE
  • Option 2-3 the UE skips the RA procedure to the selected/target PSCell if the UE maintains the valid UL timing (e.g., the timeAlignmentTimer for the SCG is running) .
  • Option 2-2-1 the UE replies to an RRC response message (e.g., an RRCConnectionReconfigurationComplete, an RRCReconfigurationComplete, or an ULInformationTransferMRDC message) including an embedded SN RRC response message (e.g., RRCReconfigurationComplete message) to the MN to inform the execution of conditional reconfiguration immediately when the execution condition (s) is met.
  • RRC response message e.g., an RRCConnectionReconfigurationComplete, an RRCReconfigurationComplete, or an ULInformationTransferMRDC message
  • embedded SN RRC response message e.g., RRCReconfigurationComplete message
  • Option 2-2-2 the UE replies to an RRC response message (e.g., an RRCConnectionReconfigurationComplete, an RRCReconfigurationComplete, or an ULInformationTransferMRDC message) including an embedded SN RRC response message (e.g., RRCReconfigurationComplete message) to the MN to inform the execution of conditional reconfiguration when SCG is activated again.
  • RRC response message e.g., an RRCConnectionReconfigurationComplete, an RRCReconfigurationComplete, or an ULInformationTransferMRDC message
  • an embedded SN RRC response message e.g., RRCReconfigurationComplete message
  • the UE receives the SCG activation command (e.g., RRC reconfiguration message or MAC CE) from the NW (e.g., the MN or the SN) , or the UE automatically initiates the RA procedure towards the target PSCell when the UL data sent to the SN is arrived.
  • the MN above refers to the target MN.
  • the UE replies to the ULInformationTransferMRDC message including an embedded SN RRC reconfiguration complete message to the MN, and the MN transfers an RRC reconfiguration complete message to the SN (i.e., similar as the case where SRB3 is not configured) since SRB3 is suspended when SCG is deactivated.
  • the target SN may need to be informed about the SCG state for the selected/target PSCell.
  • the MN configures the SCG state of candidate cell when preparing conditional reconfiguration or the MN or the source SN sends the SCG deactivation command to the UE after the conditional reconfiguration is configured
  • Alt. 1 the UE directly informs the target SN by including an SCG state indication in the SN RRC reconfiguration complete message, which is embedded in the MN RRC response message.
  • the MN Upon the MN receives the RRC response message, the MN transfers the SN RRC reconfiguration complete message to the target SN via an Xn/X2 message (e.g., an SN Reconfiguration Complete, or an SN Change Confirm message) .
  • an Xn/X2 message e.g., an SN Reconfiguration Complete, or an SN Change Confirm message
  • the MN Upon receiving the RRC response message, the MN informs the SCG state for the selected/target PSCell to the target SN via an Xn/X2 message.
  • the MN includes an SCG state indication in the Xn/X2 message (e.g., an SN Reconfiguration Complete, or an SN Change Confirm message) or send an Activity Notification message to the target SN.
  • the MN may need to be informed about the SCG state for the selected/target PSCell.
  • the UE can directly inform the MN by including an SCG state indication in the RRC response message (e.g., an RRCConnectionReconfigurationComplete, or an RRCReconfigurationComplete, ULInformationTransferMRDC message) to the MN.
  • an SCG state indication in the RRC response message (e.g., an RRCConnectionReconfigurationComplete, or an RRCReconfigurationComplete, ULInformationTransferMRDC message) to the MN.
  • the MN above refers to the target MN.
  • the UE releases all stored candidate cell configurations. Also, the UE stops evaluating the execution condition (s) once PCell/PSCell change is triggered. Thus, in the case of option 2-2 described above, the UE would keep the stored candidate cell configurations and continue evaluating the execution condition (s) after the execution condition (s) is met and the selected one candidate cell configuration is applied. Thus, in order to avoid UE selecting another candidate cell to trigger another PCell/PSCell change after one candidate cell configuration is applied, there are two alternatives can be considered:
  • Alt. 1 The UE releases all stored candidate cell configurations and related measurement configurations, and stops evaluating the execution condition (s) after applies one candidate cell configuration.
  • Alt. 2 The NW transmits a RRC message to the UE to release the stored candidate cell configurations.
  • the UE can continue to perform RRM measurement for the SCG when the SCG is deactivated.
  • the NW may configure conditional reconfiguration (e.g., CHO or CPAC) for the UE according to the measurement reports from the UE.
  • the NW can decide the SCG state in the conditional reconfiguration container as discussed in Aspect 1 -Case 1.
  • the UE When the UE receives the RRC reconfiguration message including conditional reconfiguration, the UE starts evaluating the execution condition (s) . Upon the execution condition (s) is met, the UE behavior is similar as that discussed in Aspect 1 -Case 2.
  • Embodiment 1-1 is a diagrammatic representation of Embodiment 1-1:
  • Step 1 The MN generates and sends the RRC reconfiguration message including conditional reconfiguration to the UE.
  • the conditional reconfiguration includes the execution condition (s) and the corresponding candidate cell configuration encapsulated in the RRC container.
  • the RRC container includes an MN RRC reconfiguration message, which includes an RRC reconfiguration message generated by the candidate SN encapsulated in an RRC container.
  • the MN RRC reconfiguration message also includes an SCG state indication (e.g., the scgState) .
  • a signaling structure is shown as follows:
  • the MN RRCReconfiguration message contains a conditionalReconfiguration, in which the conditionalReconfiguration contains a condExecutionCond and a condRRCReconfig.
  • condRRCReconfig contains an embedded RRCReconfiguration, which is generated by MN.
  • the RRCReconfiguration generated by the MN contains an SCG state indication and an MR-DC-SecondaryCellGroupConfig.
  • the MR-DC-SecondaryCellGroupConfig contains nr-SCG, which containing an RRCReconfiguration generated by SN.
  • Step 2 Upon reception of this message, the UE starts evaluating the execution condition (s) of candidate cell (s) .
  • Step 3 When the execution condition (s) is met, the UE applies the RRC Reconfiguration message included in the conditional reconfiguration container (e.g., the condRRCReconfig) .
  • the UE replies to an RRC response message to the MN including an embedded RRC reconfiguration complete message to the target SN.
  • the SN RRC reconfiguration complete message includes an SCG state indication (e.g., the scgState) to indicate the SCG activation state of the target PSCell.
  • Step 4 The MN transfers the SN RRC reconfiguration complete message to the target SN via an Xn/X2 message (e.g., an SN Reconfiguration Complete, or an SN Change Confirm message) .
  • an Xn/X2 message e.g., an SN Reconfiguration Complete, or an SN Change Confirm message
  • Step 5 The UE initiates the RA procedure to the target PSCell immediately, or the UE initiates the RA procedure to the target PSCell when SCG is activated again.
  • Embodiment 1-2
  • Steps 1 to 2 similar to the Steps 1 to 2 in embodiment 1-1.
  • Step 3 When the execution condition (s) is met, the UE applies the RRC Reconfiguration message included in the conditional reconfiguration container (e.g., the condRRCReconfig) .
  • the UE responses an RRC response message to the MN including an SN RRC reconfiguration complete message to the target SN.
  • Step 4 The MN transfers the SN RRC reconfiguration complete message to the target SN via an Xn/X2 message (e.g., an SN Reconfiguration Complete, or an SN Change Confirm message) .
  • the MN also includes an SCG state indication in the Xn/X2 message to indicate the SCG activation state of the target PSCell.
  • Step 5 Similar to Step 5 in embodiment 1-1.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • Step 1 The MN generates and sends the RRC reconfiguration message including the conditional reconfiguration to the UE.
  • the conditional reconfiguration includes the execution condition (s) and the corresponding candidate cell configuration encapsulated in the RRC container.
  • the RRC container includes an MN RRC reconfiguration message and an RRC reconfiguration message generated by the candidate SN encapsulated in an RRC container.
  • the SN RRC reconfiguration message includes an SCG state indication (e.g., the scgState) .
  • a signaling structure is shown as follows:
  • the MN RRCReconfiguration message contains a conditionalReconfiguration.
  • the conditionalReconfiguration contains a condExecutionCond and a condRRCReconfig.
  • condRRCReconfig contains an embedded RRCReconfiguration, which is generated by MN.
  • the RRCReconfiguration generated by MN contains an MR-DC-SecondaryCellGroupConfig.
  • the MR-DC-SecondaryCellGroupConfig contains nr-SCG, which contains an RRCReconfiguration generated by SN.
  • the SN RRCReconfiguration message contains an SCG state indication.
  • Step 2 Similar to Step 2 in embodiment 1-1.
  • Step 3 When the execution condition (s) is met, the UE applies the RRC Reconfiguration message included in the conditional reconfiguration container (e.g., the condRRCReconfig) .
  • the UE responses an RRC response message to the MN including an SN RRC reconfiguration complete message to the target SN.
  • the MN RRC response message also includes an SCG state indication (e.g., the scgState) to indicate the SCG activation state of the target PSCell.
  • Steps 4 to 5 Similar to steps 4 to 5 in embodiment 1-1.
  • Embodiment 3-1 is a diagrammatic representation of Embodiment 3-1:
  • Step 1 The MN generates and sends the RRC reconfiguration message including conditional reconfiguration to the UE.
  • the conditional reconfiguration includes the execution condition (s) and the corresponding candidate cell configuration encapsulated in the RRC container.
  • the RRC container includes an MN RRC reconfiguration message and an RRC reconfiguration message generated by the candidate SN encapsulated in an RRC container.
  • the RRC reconfiguration message generated by MN or/and candidate SN may not include (or include) an SCG state indication (e.g., the scgState) .
  • Step 2 Upon reception of this RRC reconfiguration message, the UE starts evaluating the execution condition (s) of candidate cell (s) .
  • Step 3 The MN sends the SCG deactivation command (e.g., an RRC reconfiguration message or a MAC CE) to the UE.
  • the SCG deactivation command e.g., an RRC reconfiguration message or a MAC CE
  • Step 4 Upon reception of this SCG deactivation command, the UE considers the state of the current SCG as deactivated.
  • Step 5 When the execution condition (s) is met, the UE applies the RRC Reconfiguration message included in the conditional reconfiguration container (e.g., a condRRCReconfig) and regards/considers the SCG of target PSCell to be deactivated.
  • the UE responses an RRC response message to the MN including an SN RRC reconfiguration complete message to the target SN.
  • the SN RRC reconfiguration complete message includes an SCG state indication (e.g., the scgState) to indicate the SCG activation state of the target PSCell.
  • Steps 6 to 7 Similar to Steps 4 to 5 in embodiment 1-1.
  • Embodiment 3-2
  • Steps 1 to 4 Similar to Steps 1 to 4 in embodiment 3-1.
  • Step 5 When the execution condition (s) is met, the UE applies the RRC Reconfiguration message included in the conditional reconfiguration container (e.g., the condRRCReconfig) and regards/considers the SCG to be deactivated. And the UE responses an RRC response message to the MN including an SN RRC reconfiguration complete message to the target SN.
  • the conditional reconfiguration container e.g., the condRRCReconfig
  • Steps 6 to 7 Similar to Steps 4 to 5 in embodiment 1-2.
  • Aspect 2 the coexistence of fast MCG recovery and SCG deactivation/activation
  • the UE suspends the SCG transmission.
  • an MCG Radio Link Failure (RLF) is detected when SCG transmission is suspended, the UE triggers the legacy RRC re-establishment procedure, instead of a fast MCG recovery procedure even if it is configured by the NW (i.e., the timer T316 is configured for the UE) .
  • the time for data interruption during re-establishment procedure is much longer, compared to the fast MCG recovery procedure.
  • the UE can activate the SCG (e.g., initiate the RA procedure to the PSCell) and initiate MCG failure information procedure to report the MCG RLF to the NW via SCG in the case that the MCG RLF is detected and fast MCG recovery is configured.
  • SCG e.g., initiate the RA procedure to the PSCell
  • MCG failure information procedure to report the MCG RLF to the NW via SCG in the case that the MCG RLF is detected and fast MCG recovery is configured.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the UE activates the SCG (e.g., initiate the RA procedure to the PSCell) and initiates the MCG failure information procedure to report the MCG RLF. That is, the UE transmits an MCGFailureInformation message to the NW via split SRB1 or SRB3, in which SRB1 is a signaling radio bearer between the UE and the MN, while SRB3 is a signaling radio bearer between the UE and the SN.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the arrival of the MCGFailureInformation message triggers the UE activates SCG (e.g., initiates the RA procedure to the PSCell) .
  • both the MN and the source SN may initiate the inter-SN CPC procedure towards the same candidate SN. Then, the candidate SN may select the same candidate PSCell (s) for the same UE in two procedures. However, the execution condition (s) is set by the MN and the SN, respectively corresponding to the MN initiated case and the SN initiated case.
  • Aspect 3 -Issue 1 -Case 1 MN initiated inter-SN CPC and SN initiated inter-SN CPC towards the same candidate SN are configured via one SN addition procedure
  • the MN needs to consider how to link the candidate PSCell configuration with execution condition (s) which are set by the MN and the source SN respectively, i.e., includes which execution condition (s) in the final RRC message for CPAC.
  • execution condition (s) which are set by the MN and the source SN respectively, i.e., includes which execution condition (s) in the final RRC message for CPAC.
  • Option 1 Only include the execution condition (s) generated by the MN or the source SN into the final RRC message for CPAC.
  • the MN can decide which condition (s) is used.
  • Option 2 Include both execution condition (s) generated by the MN and the source SN into the final RRC message for CPAC.
  • the MN may inform the source SN that the SN initiated CPAC procedure is rejected via an Xn/X2 message.
  • the MN may be not able to include the candidate cell information (e.g., measurement results) form both the MN (e.g., candidateCellInfoListMN) and the SN (e.g., candidateCellInfoListSN) into one CG-ConfigInfo message included in the SN addition request message.
  • the candidate cell information e.g., measurement results
  • the MN e.g., candidateCellInfoListMN
  • the SN e.g., candidateCellInfoListSN
  • Aspect 3 -Issue 1 -Case 2 MN initiated inter-SN CPC and SN initiated inter-SN CPC towards the same candidate SN are configured via different SN addition procedures
  • the candidate SN can reply two SN addition request acknowledge messages (i.e., respectively corresponding to MN initiated procedure and SN initiated procedure) to the MN, but those two messages may include the same candidate PSCell configuration.
  • SN addition request acknowledge messages i.e., respectively corresponding to MN initiated procedure and SN initiated procedure
  • Option 1 If the candidate SN selects the same candidate PSCell (s) for the same UE which has been configured via the previous CPAC procedure, the candidate SN replies to the selected candidate PSCell identification information (e.g., Physical Cell ID (PCI) and frequency; Cell Global Identity (CGI) ; and/or the index of RRC container including the PSCell configuration) to the MN via the SN addition request acknowledge message, but the SN addition request acknowledge message does not include the corresponding RRC container including the PSCell configuration.
  • PCI Physical Cell ID
  • CGI Cell Global Identity
  • Option 2 If the MN finds the candidate PSCell for the same UE is configured vian SN initiated inter-SN CPC (e.g., the PCI and frequency of candidate PSCell has been received from the previous SN addition procedure) , the MN does not send the measurement results on this cell to the candidate SN in MN initiated procedure.
  • SN initiated inter-SN CPC e.g., the PCI and frequency of candidate PSCell has been received from the previous SN addition procedure
  • Embodiment 1 (for Option 1 above):
  • Step 1 The source SN sends SN change required message to the MN including candidate cell information (e.g., measurement results) to the candidate SN.
  • This message may include the execution condition (s) for the candidate PSCell (s) .
  • Step 2 The MN sends the SN addition request message to the candidate SN including candidate cell information (e.g., measurement results) from the source SN.
  • candidate cell information e.g., measurement results
  • Step 3 The candidate SN selects the candidate PSCell (s) based on the measurement results from the source SN and replies to the SN addition request acknowledge message to the MN.
  • the SN addition request acknowledge message includes the selected candidate PSCell information identification (e.g., PCI and frequency; CGI; and the index of RRC container including the candidate PSCell configuration) and the corresponding RRC container including the candidate PSCell configuration.
  • Step 4 The MN sends the RRC reconfiguration message including conditional reconfiguration for CPAC, which includes the execution condition (s) and candidate PSCell configuration (s) , to the UE.
  • Step 5 The MN sends SN addition request message to the candidate SN, which includes the candidate cell information (e.g., the measurement results) from the MN, to trigger the MN initiated CPAC procedure for the same UE (e.g., the NG-RAN node UE Xn Application Protocol (XnAP) ID in the SN addition request message is the same as the SN addition request message sent in Step 2) .
  • the candidate cell information e.g., the measurement results
  • XnAP Xn Application Protocol
  • Step 6 The candidate SN selects the same candidate PSCell (s) as the one being selected in SN initiated CPAC procedure according to the measurement results from the MN. Then, the candidate SN replies to the SN addition request acknowledge message to the MN.
  • the SN addition request acknowledge message includes the selected candidate PSCell information identification (e.g., PCI and frequency; CGI; and the index of RRC container including the candidate PSCell configuration) , but the SN addition request acknowledge does not include the corresponding RRC container for the candidate PSCell configuration.
  • Step 7 The MN decides the execution condition (s) for the selected PSCell, and sends the RRC reconfiguration message including conditional reconfiguration for CPAC, which includes the execution condition (s) , to the UE.
  • the execution condition (s) can be configured as a new execution condition (s) for the previous PSCell (e.g., via delta configuration to replace the previous execution condition (s) ) or as an additional execution condition (s) for the previous PSCell (e.g., include it as a second condExecutionCond in the RRC reconfiguration message) .
  • the MN initiated CPAC procedure may be configured before the SN initiated CPAC procedure (e.g. the Step 5 is performed firstly. )
  • Embodiment 2 (for Option 2 above):
  • Steps 1 to 4 are similar to Steps 1 to 4 in Embodiment 1.
  • Step 5 The MN sends the SN addition request message to the candidate SN including the candidate cell information (e.g., the measurement results) from the MN, to trigger the MN initiated CPAC procedure.
  • the candidate cell information does not include the measurement results on cell (s) which is configured as PSCell in the previous SN initiated CPAC procedure.
  • Step 6 The candidate SN selects the candidate PSCell (s) based on the measurement results from the MN, and replies to the SN addition request acknowledge message to the MN.
  • the subsequent step is similar to the conventional CPAC procedure.
  • both the initiation node (i.e., MN or source SN) and the target node (i.e., target SN) can trigger the modification or cancel of CPAC configuration.
  • the CPAC modification may be triggered by the update of source SN configuration.
  • the modification of source SN configuration can be sent to the UE via SRB3, which is transparent to the MN.
  • the MN may have no idea of whether the candidate PSCell configuration added via MN initiated CPAC procedure is required to be updated or not.
  • some inter-node coordinate between MN and source/target SN can be considered to ensure timely update of candidate PSCell configuration:
  • the MN informs the source SN when MN initiated CPAC procedure is configured.
  • the MN includes an indication of MN initiated CPAC (e.g., set the value as true) in an Xn/X2 message to the source SN.
  • the source SN modifies the source SN configuration, the SN always sends the updated SCG configuration to the MN regardless of whether SRB3 is configured or not.
  • the MN informs the source SN.
  • the MN includes an indication of MN initiated CPAC (e.g., set the value as false) in an Xn/X2 message.
  • the SN performs the legacy procedure in the case that the source SN configuration is modified (e.g., send RRCReconfiguration via SRB3, if configured) .
  • the indication above transferred to the source SN can be configured by one of the following options:
  • Option 1 Include the indication directly in an Xn/X2 message. For example, include the “MN initiated CPAC” as one information element in the SN/SgNB modification request message.
  • Option 2 Include the indication in an RRC message, for example, a CG-ConfigInfo message.
  • the RRC message is included as one information element in an Xn/X2 message (e.g., SN/SgNB modification request message) .
  • CHO is configured (i.e., the UE is configured with the conditionalReconfiguration)
  • handover failure e.g., a normal HO or CHO
  • the UE upon handover failure (e.g., a normal HO or CHO) is detected, the UE will perform the CHO if the selected cell is a CHO candidate cell and it is the first time of recovery and the network allows the CHO based recovery (i.e., the attemptCondReconfig is configured) .
  • the UE in the case that the UE fails to perform a previous handover (e.g., a normal HO or CHO) without key change (i.e., the masterKeyUpdate was not included in the RRCReconfiguration for the reconfiguration with sync) and selects a CHO candidate cell without key change during the RRC re-establishment, it may cause key the stream reuse issue due to reuse the same COUNT value in the transmission of different RRC messages (e.g., RRCReconfigurationComplete messages for the first and second handover) or user data to the different target cells.
  • a previous handover e.g., a normal HO or CHO
  • RRCReconfigurationComplete messages for the first and second handover
  • Alt. 1 upon a handover failure (e.g., a normal HO or CHO) is detected, the UE can perform the CHO if the selected cell is a CHO candidate cell and it is the first time of recovery, the network allows CHO based recovery, and the previous/failed handover is configured with key change (i.e., the masterKeyUpdate was included in the RRCReconfiguration for the previous reconfiguration with sync) , i.e., the UE can perform the legacy RRC re-establishment procedure if the previous/failed handover is a handover without key change (i.e., the masterKeyUpdate was not included in the RRCReconfiguration for the previous reconfiguration with sync) .
  • a handover failure e.g., a normal HO or CHO
  • the UE can perform the CHO if the selected cell is a CHO candidate cell and it is the first time of recovery, the network allows CHO based recovery, and the previous/failed handover is configured with key change (
  • Alt. 2 upon a handover failure (e.g., a normal HO or CHO) is detected, the UE can perform CHO if the selected cell is a CHO candidate cell with key change (i.e., the masterKeyUpdate is included in the RRCReconfiguration contained in condRRCReconfig) and it is the first time of recovery and if the network allows a CHO based recovery, i.e., the UE can perform the legacy RRC re-establishment procedure if the selected cell is a CHO candidate cell without key change (i.e., masterKeyUpdate is not included in the RRCReconfiguration contained in condRRCReconfig) .
  • a handover failure e.g., a normal HO or CHO
  • the UE can perform CHO if the selected cell is a CHO candidate cell with key change (i.e., the masterKeyUpdate is included in the RRCReconfiguration contained in condRRCReconfig) and it is the first time of recovery and if the network allows
  • Alt. 3 upon a handover failure (e.g., a normal HO or CHO) is detected, the UE can perform the legacy RRC re-establishment procedure if the previous/failed handover is a handover without key change (i.e., masterKeyUpdate was not included in the RRCReconfiguration for the previous reconfiguration with sync) and the selected cell is a CHO candidate cell without key change (i.e., masterKeyUpdate is not included in the RRCReconfiguration contained in condRRCReconfig) during RRC re-establishment.
  • a handover failure e.g., a normal HO or CHO
  • the UE can perform the legacy RRC re-establishment procedure if the previous/failed handover is a handover without key change (i.e., masterKeyUpdate was not included in the RRCReconfiguration for the previous reconfiguration with sync) and the selected cell is a CHO candidate cell without key change (i.e., masterKeyUpdate is not included in
  • Alt. 4 all CHO can be configured with key change, i.e., The RRCReconfiguration message contained in the condRRCReconfig always contains the field masterKeyUpdate.
  • Embodiment 1 (for Alt. 1 above)
  • the UE Upon selecting a suitable NR cell, the UE shall:
  • Embodiment 2 (for Alt. 2 above)
  • the UE Upon selecting a suitable NR cell, the UE shall:
  • the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG, and if the attemptCondReconfig is configured, and if the selected cell is one of the candidate cells for which the reconfiguration WithSync is included in the masterCellGroup in the VarConditionalReconfig and the masterKeyUpdate is included in the RRCReconfiguration in the VarConditionalReconfig:
  • FIG. 3 relates to a schematic diagram of a wireless communication terminal 30 (e.g., a terminal node or a terminal device) according to an embodiment of the present disclosure.
  • the wireless communication terminal 30 may be a user equipment (UE) , a mobile phone, a laptop, a tablet computer, an electronic book or a portable computer system and is not limited herein.
  • the wireless communication terminal 30 may include a processor 300 such as a microprocessor or Application Specific Integrated Circuit (ASIC) , a storage unit 310 and a communication unit 320.
  • the storage unit 310 may be any data storage device that stores a program code 312, which is accessed and executed by the processor 300.
  • Embodiments of the storage code 312 include but are not limited to a subscriber identity module (SIM) , read-only memory (ROM) , flash memory, random-access memory (RAM) , hard-disk, and optical data storage device.
  • SIM subscriber identity module
  • ROM read-only memory
  • RAM random-access memory
  • the communication unit 320 may a transceiver and is used to transmit and receive signals (E.g., messages or packets) according to processing results of the processor 300. In an embodiment, the communication unit 320 transmits and receives the signals via at least one antenna 322.
  • the storage unit 310 and the program code 312 may be omitted and the processor 300 may include a storage unit with stored program code.
  • the processor 300 may implement any one of the steps in exemplified embodiments on the wireless communication terminal 30, e.g., by executing the program code 312.
  • the communication unit 320 may be a transceiver.
  • the communication unit 320 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals to and from a wireless communication node.
  • the wireless communication terminal 30 may be used to perform the operations of the UE described above.
  • the processor 300 and the communication unit 320 collaboratively perform the operations described above. For example, the processor 300 performs operations and transmit or receive signals, message, and/or infroamtion through the communication unit 320.
  • FIG. 4 relates to a schematic diagram of a wireless communication node 40 (e.g., a network device) according to an embodiment of the present disclosure.
  • the wireless communication node 40 may be a satellite, a base station (BS) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) , a next generation RAN (NG-RAN) , a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • RNC Radio Network Controller
  • the wireless communication node 40 may include (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a location management function (LMF) , a location retrieve function (LRF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless communication node 40 may include a processor 400 such as a microprocessor or ASIC, a storage unit 410 and a communication unit 420.
  • the storage unit 410 may be any data storage device that stores a program code 412, which is accessed and executed by the processor 400.
  • the storage unit 412 examples include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 420 may be a transceiver and is used to transmit and receive signals (E.g., messages or packets) according to processing results of the processor 400. In an example, the communication unit 420 transmits and receives the signals via at least one antenna 422.
  • the storage unit 410 and the program code 412 may be omitted.
  • the processor 400 may include a storage unit with stored program code.
  • the processor 400 may implement any steps described in exemplified embodiments on the wireless communication node 40, e.g., via executing the program code 412.
  • the communication unit 420 may be a transceiver.
  • the communication unit 420 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals, messages, or information to and from a wireless communication terminal.
  • the wireless communication node 40 may be used to perform the operations of the MN described above.
  • the processor 400 and the communication unit 420 collaboratively perform the operations described above. For example, the processor 400 performs operations and transmit or receive signals through the communication unit 420.
  • FIG. 5 relates to a schematic diagram of a wireless communication node 50 (e.g., a network device) according to an embodiment of the present disclosure.
  • the wireless communication node 50 may be a satellite, a base station (BS) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) , a next generation RAN (NG-RAN) , a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • RNC Radio Network Controller
  • the wireless communication node 50 may include (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless communication node 50 may include a processor 500 such as a microprocessor or ASIC, a storage unit 510 and a communication unit 520.
  • the storage unit 510 may be any data storage device that stores a program code 512, which is accessed and executed by the processor 500. Examples of the storage unit 512 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 520 may be a transceiver and is used to transmit and receive signals (E.g., messages or packets) according to processing results of the processor 500.
  • the communication unit 520 transmits and receives the signals via at least one antenna 522.
  • the storage unit 510 and the program code 512 may be omitted.
  • the processor 500 may include a storage unit with stored program code.
  • the processor 500 may implement any steps described in exemplified embodiments on the wireless communication node 50, e.g., via executing the program code 512.
  • the communication unit 520 may be a transceiver.
  • the communication unit 520 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals, messages, or information to and from a wireless terminal (E.g., a user equipment) .
  • a wireless terminal E.g., a user equipment
  • the wireless communication node 50 may be used to perform the operations of the SN described above, such as the target SN and the source SN.
  • the processor 500 and the communication unit 520 collaboratively perform the operations described above. For example, the processor 500 performs operations and transmit or receive signals through the communication unit 520.
  • FIG. 6 illustrates a wireless communication method 600 according to an embodiment of the present disclosure.
  • the wireless communication method 600 may be performed by using a wireless communication terminal (e.g., a UE) .
  • the location management node may be implemented by using the wireless communication node 30 described above, but is not limited thereto.
  • the wireless communication method 600 includes operations 610, 620 and 630.
  • Operation 610 includes receiving, by a wireless communication terminal, a RRC message including conditional reconfiguration from a wireless communication node.
  • the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell.
  • the candidate cell configuration includes a first indication of a SCG activation state of the candidate cell.
  • Operation 620 includes selecting, by the wireless communication device, based on one or more execution conditions, a target cell, to apply a cell configuration of the target cell in the conditional reconfiguration.
  • Operation 630 includes determining, by the wireless communication device, the SCG activation state of the target cell, according to the first indication of an SCG activation state of the target cell.
  • the power consumption of the wireless communication terminal can be reduced, the SCG addition/change interruption time of the wireless communication terminal can be reduced, and the SCG addition/change reliability of the wireless communication terminal can be improved.
  • FIG. 7 illustrates a wireless communication method 700 according to an embodiment of the present disclosure.
  • the wireless communication method 700 may be performed by using a wireless communication node (e.g., a network device) .
  • the wireless communication node may be implemented by using the wireless communication node 40 described above, but is not limited thereto.
  • the wireless communication method 700 may be performed to serve the function of the MN described above.
  • the wireless communication method 700 includes operations 710 and 720.
  • Operation 710 includes transmitting, by a wireless communication node, a RRC message including conditional reconfiguration to a wireless communication terminal.
  • the conditional reconfiguration includes at least one candidate cell configuration, and one or more execution conditions for each candidate cell.
  • the candidate cell configuration includes a first indication of a secondary cell group, SCG, activation state of the candidate cell.
  • the first RRC message causes the wireless communication terminal to: select, based on one or more execution conditions, a target cell of a wireless communication node, to apply a cell configuration of the target cell in the conditional reconfiguration.
  • Operation 720 includes determining the SCG activation state of the target cell according to the first indication of an SCG activation state of the target cell.
  • the power consumption of the wireless communication terminal can be reduced, the SCG addition/change interruption time of the wireless communication terminal can be reduced, and the SCG addition/change reliability of the wireless communication terminal can be improved.
  • FIG. 8 illustrates a wireless communication method 800 according to an embodiment of the present disclosure.
  • the wireless communication method 800 may be performed by using a wireless communication node (e.g., a network device) .
  • the wireless communication node may be implemented by using the wireless communication node 50 described above, but is not limited thereto.
  • the wireless communication method 700 may be performed to serve the function of the MN described above.
  • the wireless communication method 800 includes operation 810.
  • Operation 810 includes transmitting, by a target SN, a cell configuration of a target cell served by the target SN to a wireless communication terminal via a wireless communication node.
  • the cell configuration includes a first indication of a secondary cell group (SCG) activation state of the target cell.
  • SCG secondary cell group
  • the power consumption of the wireless communication terminal can be reduced, the SCG addition/change interruption time of the wireless communication terminal can be reduced, and the SCG addition/change reliability of the wireless communication terminal can be improved.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a “software unit” ) , or any combination of these techniques.
  • a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/CN2020/142355 2020-12-31 2020-12-31 Method, device and computer program product for wireless communication WO2022141491A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202080106704.0A CN116349387A (zh) 2020-12-31 2020-12-31 用于无线通信的方法、设备和计算机程序产品
EP20967830.9A EP4218308A4 (en) 2020-12-31 2020-12-31 METHOD, DEVICE AND COMPUTER PROGRAM PRODUCT FOR WIRELESS COMMUNICATIONS
PCT/CN2020/142355 WO2022141491A1 (en) 2020-12-31 2020-12-31 Method, device and computer program product for wireless communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/142355 WO2022141491A1 (en) 2020-12-31 2020-12-31 Method, device and computer program product for wireless communication

Publications (1)

Publication Number Publication Date
WO2022141491A1 true WO2022141491A1 (en) 2022-07-07

Family

ID=82260131

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/142355 WO2022141491A1 (en) 2020-12-31 2020-12-31 Method, device and computer program product for wireless communication

Country Status (3)

Country Link
EP (1) EP4218308A4 (zh)
CN (1) CN116349387A (zh)
WO (1) WO2022141491A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024027981A1 (en) * 2022-08-05 2024-02-08 Nokia Technologies Oy Data forwarding for dual connectivity
WO2024060033A1 (zh) * 2022-09-20 2024-03-28 Oppo广东移动通信有限公司 通信方法及通信装置
WO2024074132A1 (zh) * 2022-10-08 2024-04-11 中国移动通信有限公司研究院 一种信息处理方法、装置、通信设备和存储介质
WO2024093934A1 (zh) * 2022-11-04 2024-05-10 中国移动通信有限公司研究院 配置方法、装置、相关设备及存储介质
WO2024145854A1 (zh) * 2023-01-04 2024-07-11 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
WO2024168805A1 (zh) * 2023-02-17 2024-08-22 Oppo广东移动通信有限公司 无线通信方法、终端设备及网络设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023102203A (ja) * 2022-01-11 2023-07-24 シャープ株式会社 端末装置、基地局装置、および方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019157637A1 (zh) * 2018-02-13 2019-08-22 华为技术有限公司 一种通信方法及装置
CN111225396A (zh) * 2020-01-07 2020-06-02 展讯通信（上海）有限公司 去激活和激活辅小区组的方法、通信装置和相关产品

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220312354A1 (en) * 2019-06-14 2022-09-29 Telefonaktiebolaget Lm Ericsson (Publ) Neighbor Cell Synchronization Upon State Transition

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019157637A1 (zh) * 2018-02-13 2019-08-22 华为技术有限公司 一种通信方法及装置
CN111225396A (zh) * 2020-01-07 2020-06-02 展讯通信（上海）有限公司 去激活和激活辅小区组的方法、通信装置和相关产品

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Support of SCG activation/de-activation mechanism", 3GPP DRAFT; R3-206497, vol. RAN WG3, 23 October 2020 (2020-10-23), pages 1 - 7, XP051945913 *
HUAWEI: "Discussion on support of efficient activation/de-activation mechanism for one SCG and SCells", 3GPP DRAFT; R3-206341, vol. RAN WG3, 23 October 2020 (2020-10-23), pages 1 - 5, XP051945807 *
See also references of EP4218308A4 *
VIVO: "Conditional PSCell addition and change", 3GPP DRAFT; R2-1912343 CONDITIONAL PSCELL ADDITION AND CHANGE, vol. RAN WG2, 4 October 2019 (2019-10-04), Chongqing, China, pages 1 - 2, XP051790389 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024027981A1 (en) * 2022-08-05 2024-02-08 Nokia Technologies Oy Data forwarding for dual connectivity
WO2024060033A1 (zh) * 2022-09-20 2024-03-28 Oppo广东移动通信有限公司 通信方法及通信装置
WO2024074132A1 (zh) * 2022-10-08 2024-04-11 中国移动通信有限公司研究院 一种信息处理方法、装置、通信设备和存储介质
WO2024093934A1 (zh) * 2022-11-04 2024-05-10 中国移动通信有限公司研究院 配置方法、装置、相关设备及存储介质
WO2024145854A1 (zh) * 2023-01-04 2024-07-11 北京小米移动软件有限公司 信息处理方法及装置、通信设备及存储介质
WO2024168805A1 (zh) * 2023-02-17 2024-08-22 Oppo广东移动通信有限公司 无线通信方法、终端设备及网络设备

Also Published As

Publication number Publication date
CN116349387A (zh) 2023-06-27
EP4218308A4 (en) 2024-06-26
EP4218308A1 (en) 2023-08-02

Similar Documents

Publication Publication Date Title
WO2022141491A1 (en) Method, device and computer program product for wireless communication
US20230097891A1 (en) System and method for mobility enhancements
EP3915301B1 (en) Method and apparatus for reporting master cell group failure
US11399326B2 (en) Methods and systems for handling conditional handover (CHO) in a wireless communication network
KR101969693B1 (ko) 수락 제어 및 로드 밸런싱
US20220167233A1 (en) Method, apparatus and system for mobility control
US20200163144A1 (en) Method and apparatus for transmitting and receiving signals in wireless communication system
KR20170043533A (ko) 인터/인트라 무선 액세스 기술 이동성 및 사용자 평면 스플릿 측정 구성
EP2720503A1 (en) Base station and communication method
US20240031253A1 (en) Method for radio access network visible quality of experience measurement of dual connectivity
US20230108725A1 (en) Method and apparatus for data transmission
RU2726870C1 (ru) Способ связи, устройство сети доступа и терминальное устройство
EP3381226A1 (en) Handover with postponed path switch
CN108029064A (zh) 第一和第二无线电网络节点以及在其中执行的方法
WO2023092485A1 (en) Service continuity of sidelink relay communication
WO2022151279A1 (en) Method, device and computer program product for wireless communication
WO2022227046A1 (en) Method, device and computer program product for wireless communication
WO2020010487A1 (zh) 一种小区切换方法以及相关设备
EP4415418A1 (en) Methods and apparatuses relating to reporting of user plane interruption times
EP4312452A1 (en) Handling conditional handover preparations in failure scenarios
WO2024156124A1 (en) Method of inter-donor migration and apparatus thereof
WO2024113615A1 (en) A method for selective activation of cell groups
US20240349376A1 (en) Method, device and computer program product for wireless communication
CA3188195A1 (en) System and method for selecting paging resources

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20967830

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2020967830

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2020967830

Country of ref document: EP

Effective date: 20230427

NENP Non-entry into the national phase

Ref country code: DE