Conditional pscell addition type indication as part of selective activation
The target SN's ability to determine and indicate the type of PSCell change in 5G New Radio networks addresses the challenge of resource reservation and flexibility in selective activation, enhancing UE throughput and reducing signaling overload by adapting configurations based on PSCell Change Type Indicators.
Patent Information
- Application Number
- PCT/EP2024/060480
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-04-18
- Publication Date
- 2024-11-21
AI Technical Summary
In 5G New Radio networks with Multi-RAT Mobility, there is a need for improved resource reservation and flexibility in selective activation of PSCells to avoid signaling overload and ensure high UE throughput during cell changes, particularly when target SNs do not support selective activation, leading to potential disruptions in dual connectivity.
The target SN is configured to receive SN addition requests, select candidate PSCells, determine whether to perform selective activation or Conditional PSCell Change (CPC) without selective activation, and transmit a PSCell Change Type Indicator to the Master Node (MN), allowing the MN to configure the UE accordingly, thereby reducing unnecessary signaling and maintaining high throughput.
This solution reduces signaling overhead, ensures efficient PSCell changes, and maintains high UE throughput by allowing the MN to adapt configurations based on the PSCell Change Type Indicator, ensuring seamless dual connectivity even when selective activation is not supported by the target SN.
Smart Images

Figure EP2024060480_21112024_PF_FP_ABST
Abstract
Description
Conditional PSCell addition type indication as part of selective activationTECHNOLOGY
[0001] The present disclosure relates to conditional PSCell addition / change, in particular to Conditional PSCell change being related to selective activation.BACKGROUND
[0002] Any discussion of the background art throughout the specification should in no way be considered as an admission that such art is widely known or forms part of common general knowledge in the field.
[0003] Broadly speaking, in 5G New Radio and, in particular, with Multi-RAT Mobility (MRM) concept targeted for 3GPP Rel-18 and beyond, it is provided improved mobility / cellchanges in RAN where the Central-Unit - Distributed-Unit (CU-DU) structure is deployed, i.e., enabling operations between different DU (inter-DU) of different vendors via CU (involving the Control Plane or / and User Plane aspects of the Central-Unit, CU-CP, CU-UP).
[0004] Rel-18 work Item on mobility enhancements (RP -223520, RP -221799 , RP2-213565) includes one objective to support lower layer triggered mobility (LTM) to improve the interruption time and execution delay for switching between cells of same or different DU but controlled by same CU. Unlike L3 based mobility where the handover decision is based on L3 cell quality measurement results, the handover in LTM is triggered by the MAC layer in the DU based on LI beam measurement results.
[0005] Due to mobility of a UE, source Master Node (MN) chooses to prepare and enable Rel-18 Selective Activation behaviour for the UE; therefore, source MN requests at target Secondary Node (SN) to reserve resources in a target PSCell for the UE and target SN provides an SN addition response with reserved resources of a target PSCell.
[0006] With Rel. 18 selective activation being requested (for instance with a first SN Add Request message sent from the MN to the target SNs), there may be a case where a target SN does not support selective activation and sends to the MN as a response a rejection message, which may lead to the MN sending a second SN Add Request message. As the first SN Add Request message has been rejected, the MN may send the second SN Add Request message without requesting for selective activation (3GPP Rel. 18), that is, requesting for legacy Conditional PSCell Change (CPC) without the selective activation (3GPP Rel. 16 and Rel. 17).
[0007] To avoid a second SN Add Request / Response procedure between the source MN and the target SN, the target SN may want to reply with the reserved resources instead of rejecting the request. However, the source MN does not know whether the reserved resources are intended for Rel-18 Selective Activation or legacy PSCell switch / change.
[0008] Thus, there is a need to provide improved resource reservation at target SN, as well as more flexibility in applying Rel. 18 Selective Activation, to avoid overload and reduce signalling exchange between the SNs and the MN.
[0009] Further, there is a need to ensure that the UE can maintain a high throughput for a longer period of time in the dual connectivity, avoiding a case where the UE does not obtain the configuration for the conditional PSCell change for the target PSCells indicated by the target SNs.SUMMARY
[0010] In accordance with an aspect of the present disclosure, there is provided a target Secondary Node, SN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the target SN is further configured to connect to a User Equipment, UE, and the target SN comprises: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the target SN at least to: receive, from a Master Node, MN, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; select, among one or more PSCells on the basis of the SN addition request message, one or more candidate target PSCells; determine whether to perform the requested selective activation for said selected one or more candidate target PSCells or a Conditional PSCell Change, CPC, without the selective activation; and transmit, to the MN, an SN addition response message comprising a second indicator indicating a result of said determination.
[0011] In some examples, the target SN is further caused to: receive, via the MN, UE measurements; andestimate resource reservations for said selected one or more candidate target PSCells based on said received UE measurements, for determining whether to perform selective activation for said selected one or more candidate target PSCells.
[0012] In some examples, the target SN is further caused to perform at least one of the following estimations: evaluate said received UE measurements to estimate a time for the UE to establish a connection to the target SN; evaluate a probability that the UE will leave the current Primary Cell, PCell; and evaluate an amount of radio and backhaul resource reservation needed for the UE and compare said amount to a current load for said selected one or more candidate target PSCells.
[0013] In some examples, the target SN is further caused to: reject said selective activation request, when determining that the target SN does not support said selective activation; and preferably indicate to the MN said rejection.
[0014] In some examples, the target SN is further caused to: determine to perform CPC without selective activation for said selected one or more candidate target PSCells, when determining that the target SN does not support said selective activation.
[0015] In some examples, the target SN is further caused to: configure a capability indicator indicating a capability of the target SN to support a configuration of said second indicator.
[0016] In accordance with an aspect of the present disclosure, there is provided a Master Node, MN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the MN is further configured to connect to a User Equipment, UE, and the MN comprises: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the MN at least to: transmit, to one or more target SNs, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; receive, from said each target SN, an SN addition response message comprising a second indicator indicating whether said target SN performs selective activation or a Conditional PSCell Change, CPC, for said one or more candidate target PSCells; anddetermine to configure the UE for said PSCell change based on said received second indicator.
[0017] In some examples, the MN is further caused to: receive, from each of said one or more target SNs, identifications of one or more candidate target PSCells and more preferably CPC execution conditions for said one or more candidate target PSCells; transmit the second indicator to a source SN, and cause the source SN to provide updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the second indicator.
[0018] In some examples, in the MN is further caused to: transmit the second indicator, when receiving a selective activation indication from the source SN.
[0019] In some examples, the MN is further caused to: if the second indicator indicates that said target SN does not perform said selective activation for one candidate target PSCell, indicate to the UE to perform Conditional PSCell change, CPC, and a CPC execution condition and / or a candidate target PSCell configuration for said one candidate target PSCell, and preferably indicate to the UE to release said CPC execution condition and / or said candidate target PSCell configuration after PSCell change.
[0020] In some examples, the MN is further caused to: if the second indicator indicates that said target SN performs said selective activation for one candidate target PSCell, configure the UE with an CPC execution condition for each other candidate target PSCell, and preferably indicate the UE to keep candidate target PSCell configurations stored after each PSCell change and refraining from releasing or deleting the candidate target PSCell configurations.
[0021] In some examples, the MN is further caused to: configure a capability indicator indicating a capability of the MN to support a configuration of said first indicator.
[0022] In accordance with an aspect of the present disclosure, there is provided a source Secondary Node, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the source SN is further configured to connect to a User Equipment, UE, and the source SN comprises: at least one processor, andat least one memory storing instructions that, when executed by the at least one processor, cause the source SN at least to: transmit, to a Master Node, MN, identifications of one or more candidate target PSCells and preferably CPC execution conditions for said one or more candidate target PSCells; receive a PSCell Change Type Indicator from the MN; and transmit, to the MN, updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the PSCell Change Type Indicator.
[0023] In some examples, the source SN is further caused to: transmit a selective activation indication to the MN indicating, for said one or more candidate target PSCells, whether selective activation is supported.
[0024] In accordance with an aspect of the present disclosure, there is provided a system, configured for Primary Cell of a Secondary Cell Group, SCG, PSCell, change, the system comprising: a User Equipment, UE, one or more target Secondary Nodes, SNs, in accordance with the above aspects and examples, a Master Node, MN, in accordance with the above aspects and examples, and a source SN in accordance with the above aspects and examples, wherein said UE is connected to said MN and said SNs.
[0025] In some examples, the MN and / or the SNs are further caused to: transmit a capability indication message to the remaining nodes indicating a capability to support a configuration related to an indication related to selective activation.
[0026] In accordance with an aspect of the present disclosure, there is provided a method of a target Secondary Node, SN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the target SN is configured to connect to a User Equipment, UE, the method comprising: receiving, from a Master Node, MN, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; selecting, among one or more PSCells on the basis of the SN addition request message, one or more candidate target PSCells;determining whether to perform the requested selective activation for said selected one or more candidate target PSCells or a Conditional PSCell Change, CPC, without the selective activation; and transmitting, to the MN, an SN addition response message comprising a second indicator indicating a result of said determination.
[0027] In accordance with an aspect of the present disclosure, there is provided a method of a Master Node, MN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the MN is configured to connect to a User Equipment, UE, the method comprising: transmitting, to one or more target SNs, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; receiving, from said each target SN, an SN addition response message comprising a second indicator indicating whether said target SN performs selective activation or a Conditional PSCell Change, CPC, for said one or more candidate target PSCells; and determining to configure the UE for said PSCell change based on said received second indicator.
[0028] In accordance with an aspect of the present disclosure, there is provided a method of a source Secondary Node, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the source SN is configured to connect to a User Equipment, UE, the method comprising: transmitting, to a Master Node, MN, identifications of one or more candidate target PSCells and preferably CPC execution conditions for said one or more candidate target PSCells; receiving a PSCell Change Type Indicator from the MN; and transmitting, to the MN, updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the PSCell Change Type Indicator.
[0029] In accordance with an aspect of the present disclosure, there is provided a computer program comprising instructions for causing an apparatus to perform the method according to the above aspects and examples.
[0030] In accordance with an aspect of the present disclosure, there is provided a memory storing computer readable instructions for causing an apparatus to perform the method according to the above aspects and examples.
[0031] Furthermore, according to some example embodiments, there is provided a UE comprising respective suitable means configured for performing the respective steps as disclosed in the present disclosure.
[0032] Similarly, according to some example embodiments, there is also provided a CU and a DU comprising respective suitable means configured for performing the respective steps as disclosed in the present disclosure.
[0033] In addition, according to some other example embodiments, there is provided, for example, a computer program product for a wireless communication device comprising at least one processor, including software code portions for performing the respective steps disclosed in the present disclosure, when said product is run on the device. The computer program product may include a computer-readable medium on which said software code portions are stored. Furthermore, the computer program product may be directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.
[0034] While some example embodiments will be described herein with particular reference to the above application, it will be appreciated that the present disclosure is not limited to such a field of use, and is applicable in broader contexts.
[0035] Notably, it is understood that methods according to the present disclosure relate to methods of operating the apparatuses according to the above example embodiments and variations thereof, and that respective statements made with regard to the apparatuses likewise apply to the corresponding methods, and vice versa, such that similar description may be omitted for the sake of conciseness. In addition, the above aspects may be combined in many ways, even if not explicitly disclosed. The skilled person will understand that these combinations of aspects and features / steps are possible unless it creates a contradiction which is explicitly excluded.
[0036] Implementations of the disclosed apparatuses may include using, but not limited to, one or more processor, one or more application specific integrated circuit (ASIC) and / or one or more field programmable gate array (FPGA). Implementations of the apparatus may also include using other conventional and / or customized hardware such as software programmable processors, such as graphics processing unit (GPU) processors.
[0037] Other and further example embodiments of the present disclosure will become apparent during the course of the following discussion and by reference to the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS
[0038] Example embodiments of the disclosure will now be described, by way of example only, with reference to the accompanying drawings in which:
[0039] Figure 1 schematically illustrates an example of a signaling / messaging flowchart of an SN initiated Inter-SN Conditional Primary Secondary Cell Change;
[0040] Figure 2 schematically illustrates an example of a signaling / messaging flowchart of an SN initiated Inter-SN Conditional Primary Secondary Cell Change; and
[0041] Figure 3 schematically illustrates an example of a signaling / messaging flowchart of an SN initiated Inter-SN Conditional Primary Secondary Cell Change according to an example embodiment of the present disclosure.DESCRIPTION OF EXAMPLE EMBODIMENTS
[0042] In the following, different exemplifying embodiments will be described using, as an example of a communication network to which examples of embodiments may be applied, a communication network architecture based on 3 GPP standards for a communication network, such as a 5G / NR, without restricting the embodiments to such an architecture, however. It is apparent for a person skilled in the art that the embodiments may also be applied to other kinds of communication networks where mobile communication principles are integrated with a D2D (device-to-device) or V2X (vehicle to everything) configuration, such as SL (side link), e.g. Wi-Fi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc. Furthermore, without loss of generality, the description of some examples of embodiments is related to a mobile communication network, but principles of the disclosure can be extended and applied to any other type of communication network, such as a wired communication network.
[0043] The following examples and embodiments are to be understood only as illustrative examples. Although the specification may refer to “an”, “one”, or “some” example(s) or embodiment(s) in several locations, this does not necessarily mean that each such reference isrelated to the same example(s) or embodiment(s), or that the feature only applies to a single example or embodiment. Single features of different embodiments may also be combined to provide other embodiments. Furthermore, terms like “comprising” and “including” should be understood as not limiting the described embodiments to consist of only those features that have been mentioned; such examples and embodiments may also contain features, structures, units, modules, etc., that have not been specifically mentioned.
[0044] A basic system architecture of a (tele)communication network including a mobile communication system where some examples of embodiments are applicable may include an architecture of one or more communication networks including wireless access network subsystem(s) and core network(s). Such an architecture may include one or more communication network control elements or functions, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB), an eNB or a gNB, a distributed unit (DU) or a centralized / central unit (CU), which controls a respective coverage area or cell(s) and with which one or more communication stations such as communication elements or functions, like user devices or terminal devices, like a user equipment (UE), or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application capable of conducting a communication, such as a UE, an element or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are capable to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, core network elements or network functions, such as gateway network elements / functions, mobility management entities, a mobile switching center, servers, databases and the like may be included.
[0045] The following description may provide further details of alternatives, modifications and variances: a gNB comprises e.g., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC, e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2 incorporated by reference.
[0046] A gNB Central Unit (gNB-CU) comprises e.g., a logical node hosting e.g., RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs. The gNB-CU terminates the Fl interface connected with the gNB-DU.
[0047] A gNB Distributed Unit (gNB-DU) comprises e.g., a logical node hosting e.g., RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by the gNB- CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU.
[0048] A gNB-CU-Control Plane (gNB-CU-CP) comprises e.g., a logical node hosting e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP terminates the El interface connected with the gNB-CU-UP and the Fl-C interface connected with the gNB-DU.
[0049] A gNB-CU-User Plane (gNB-CU-UP) comprises e.g., a logical node hosting e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP terminates the El interface connected with the gNB-CU-CP and the Fl-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1 incorporated by reference.
[0050] Different functional splits between the central and distributed unit are possible, e.g., called options:Option 1 (lA-like split):• The function split in this option is similar to the 1 A architecture in DC. RRC is in the central unit. PDCP, RLC, MAC, physical layer and RF are in the distributed unit.Option 2 (3C-like split):• The function split in this option is similar to the 3C architecture in DC. RRC and PDCP are in the central unit. RLC, MAC, physical layer and RF are in the distributed unit.Option 3 (intra RLC split):• Low RLC (partial function of RLC), MAC, physical layer and RF are in the distributed unit. PDCP and high RLC (the other partial function of RLC) are in the central unit.Option 4 (RLC-MAC split):• MAC, physical layer and RF are in the distributed unit. PDCP and RLC are in the central unit.Or else, e.g., according to 3GPP TR 38.801 V14.0.0 (2017-03) section 11 incorporated by reference.
[0051] A gNB supports different protocol layers, e.g., Layer 1 (LI) - physical layer.
[0052] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where e.g. :• The physical layer offers to the MAC sublayer transport channels;• The MAC sublayer offers to the RLC sublayer logical channels;• The RLC sublayer offers to the PDCP sublayer RLC channels;• The PDCP sublayer offers to the SDAP sublayer radio bearers;• The SDAP sublayer offers to 5GC QoS flows;• Comp, refers to header compression and Segm. To segmentation;• Control channels include (BCCH, PCCH).
[0053] Layer 3 (L3) includes e.g., Radio Resource Control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6 incorporated by reference.
[0054] A RAN (Radio Access Network) node or network node like e.g. a gNB, base station, gNB CU or gNB DU or parts thereof may be implemented using e.g. an apparatus with at least one processor and / or at least one memory (with computer-readable instructions (computer program)) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (Radio Access Network), e.g. layer 2 and / or layer 3.
[0055] The gNB CU and gNB DU parts may e.g., be co-located or physically separated. The gNB DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A Central Unit (CU) may also be called BBU / REC / RCC / C- RAN / V-RAN, 0-RAN, or part thereof. A Distributed Unit (DU) may also be called RRH / RRU / RE / RU, or part thereof. Hereinafter, in various example embodiments of the present disclosure, the CU-CP (or more generically, the CU) may also be referred to as a (first) network node that supports at least one of central unit control plane functionality or a layer 3 protocol of a radio access network; and similarly, the DU may be referred to as a (second) network node that supports at least one of distributed unit functionality or the layer 2 protocol of the radio access network.
[0056] A gNB-DU supports one or multiple cells, and could thus serve as e.g., a serving cell for a user equipment (UE).
[0057] A user equipment (UE) may include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (Radio Access Network), a smartphone, an in-vehicleapparatus, an loT device, a M2M device, or else. Such UE or apparatus may comprise: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, like e.g. RRC connection to the RAN. A UE is e.g., configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). A UE may generate and transmit and receive RRC messages containing one or more RRC PDUs (Packet Data Units).
[0058] The UE may have different states (e.g., according to 3GPP TS 38.331 V16.5.0 (2021- 06) sections 42.1 and 4.4, incorporated by reference).
[0059] A UE is e.g., either in RRC CONNECTED state or in RRC INACTIVE state when an RRC connection has been established.
[0060] In RRC CONNECTED state a UE may:• store the AS context;• transfer unicast data to / from the UE;• monitor control channels associated with the shared data channel to determine if data is scheduled for the data channel;• provide channel quality and feedback information;• perform neighboring cell measurements and measurement reporting.
[0061] The RRC protocol includes e.g. the following main functions:• RRC connection control;• measurement configuration and reporting;• establishment / modification / release of measurement configuration (e.g. intrafrequency, inter-frequency and inter-RAT measurements);• setup and release of measurement gaps;• measurement reporting.
[0062] The general functions and interconnections of the described elements and functions, which also depend on the actual network type, are known to those skilled in the art and described in corresponding specifications, so that a detailed description thereof may omitted herein for the sake of conciseness. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network controlelement, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below.
[0063] A communication network architecture as being considered in examples of embodiments may also be able to communicate with other networks, such as a public switched telephone network or the Internet. The communication network may also be able to support the usage of cloud services for virtual network elements or functions thereof, wherein it is to be noted that the virtual network part of the telecommunication network can also be provided by non-cloud resources, e.g. an internal network or the like. It should be appreciated that network elements of an access system, of a core network etc., and / or respective functionalities may be implemented by using any node, host, server, access node or entity etc. being suitable for such a usage. Generally, a network function can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
[0064] Furthermore, a network element, such as communication elements, like a UE, a terminal device, control elements or functions, such as access network elements, like a base station / BS, a gNB, a radio network controller, a core network control element or function, such as a gateway element, or other network elements or functions, as described herein, and any other elements, functions or applications may be implemented by software, e.g., by a computer program product for a computer, and / or by hardware. For executing their respective processing, correspondingly used devices, nodes, functions or network elements may include several means, modules, units, components, etc. (not shown) which are required for control, processing and / or communication / signaling functionality. Such means, modules, units and components may include, for example, one or more processors or processor units including one or more processing portions for executing instructions and / or programs and / or for processing data, storage or memory units or means for storing instructions, programs and / or data, for serving as a work area of the processor or processing portion and the like (e.g. ROM, RAM, EEPROM, and the like), input or interface means for inputting data and instructions by software (e.g. floppy disc, CD-ROM, EEPROM, and the like), a user interface for providing monitor and manipulation possibilities to a user (e.g. a screen, a keyboard and the like), other interface or means for establishing links and / or connections under the control of the processor unit or portion (e.g. wired and wireless interface means, radio interface means including e.g. an antenna unit or the like, means for forming a radio communication part etc.) and the like, wherein respective means forming an interface, such as a radio communication part, can be also locatedon a remote site (e.g. a radio head or a radio station etc.). It is to be noted that in the present specification processing portions should not be only considered to represent physical portions of one or more processors, but may also be considered as a logical division of the referred processing tasks performed by one or more processors. It should be appreciated that according to some examples, a so-called “liquid” or flexible network concept may be employed where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. In other words, a “division of labor” between involved network elements, functions or entities may vary case by case.
[0065] As illustrated above, the present disclosure generally seeks to provide an efficient and flexible signaling between the (source) MN and the (source and target) SNs in the dual connectivity scenario where it is also an object to improve the UE throughput. The same principles apply to multi connectivity scenarios where the number of independent communication paths to the UE is greater than two.
[0066] According to a broad aspect, without a PSCell Change Type Indicator from the target SN, the source MN would assume that the requested Rel-18 Selective Activation has been confirmed by the target SN, but with the PSCell Change Type Indicator indicating either “legacy PSCell change (=legacy CP AC) mode (Rel. 16 and Rel. 17)” or “selective activation mode (Rel. 18)”, the source MN is enabled to adopt the measurements and cell change (execution) conditions according to the indicated type of PSCell change.
[0067] In more detail, it is proposed in accordance with the present application:- an SN change required message sent from source SN to MN;■ a new IE in the SN Add response message as an indicator for either the legacy CP AC = Rel-17 PSCell change, or the SCG Selective Activation=Rel-18 PSCell change;- target SN may partly acknowledge / reject the SN Add Request by reserving resources and providing PSCell configuration for legacy CP AC instead of requested Rel-18 Selective Activation;- target SN may choose which PSCell change behaviour it will apply to UE changing into a target PSCell; allows to consider available resources, user load, number of UE with mobility requests;- source MN may choose and request a PSCell Change Type to target SN;- the PSCell Change Type Indicator in the SN Add Response indicates whether the reserved resources are intended for legacy PSCell switch / change or Rel-18 Selective Activation behaviour and MN adapts the measurements and cell change configuration(s) accordingly;- Target SN may reject the Rel-18 selective activation request, because resources are reserved for a long time, but offers as alternative, namely the legacy PSCell switch for the UE by replying with SN Add Response to source MN -> target SN indicates to source MN which type of PSCell change has been configured for the UE (PSCell Change Indicator) in the SN Add Response; and- Source MN requests Rel-18 selective activation from target SN, but target SN may decide / choose to support the legacy CP AC mode instead of the Rel-18 selective activation.
[0068] With the above configurations proposed in accordance with the present application, with the (first) SN Add request message (requesting Rel. 18 selective activation) sent from the MN to the target SNs, one or more target SNs are configured to provide a response already indicating to the MN whether the requested Rel. 18 selective activation would be supported / performed. This enables the MN to accordingly configure the UE to carry out either the legacy CP(A)C according to Rel. 16-17 (e.g., releasing the related resource / configuration after PSCell change) and the selective activation according to Rel.18 (e.g., keeping the related resource / configuration after PSCell change). The selective activation thus enables the UE to perform multiple CP(A)Cs within a SCG because the resources and configurations are maintained in the cells of the SCG. Therefore, it is more efficient from the perspective of the signaling but may require more resources from the cells of the SCG.
[0069] As a result of using the selective activation, there is no need for a second (additional) SN Add request message, leading to reduced signaling overhead and therefore improved efficiency in PSCell change in dual connectivity.
[0070] Further, the UE would have improved throughput since it would be able to appropriately connect to a candidate target PSCell indicated by a target SN.
[0071] Further, it is proposed in accordance with the present application that: the MN is configured to transmit the PSCell Change Type Indicator (which e.g., the MN has received from a target SN) to the source SN; thereby, the source SN is triggered by the MN to transmit, to the MN, updated CPC execution conditions for one or morecandidate target PSCells selected by said target SN, based on the information indicated by the PSCell Change Type Indicator.
[0072] With the above configurations proposed in accordance with the present application, efficiency in the communication between the MN and the SNs, as well as the throughput of the UE is further improved, in that the conditional execution conditions and the related configurations depending on the PSCell Type Indicator are parallelly updated by the source SN to the MN, such that the UE obtains the updated related execution conditions and the related configurations in the meantime.
[0073] In addition, it is proposed in accordance with the present application: a network node / gNB capability indicator which indicates the support of the above proposed solution, namely the PSCell Change Indicator capability to other network nodes; therefore, network node applies and starts the proposed solution, when the network node receives a capability indicator from the other node to support the proposed solution.
[0074] In view thereof, the present disclosure generally proposes apparatuses (such as UE, DU, CU, or the like) as well as corresponding methods to address some or all of the aboveillustrated remarks, particularly in an efficient and flexible manner.
[0075] Before going into detail of the example embodiments of the present disclosure, it may also be worthwhile to provide a brief description - from a high / abstract level perspective - that could serve as a basis for understanding possible underlying technologies (and the terminologies used therein) that are described in the present disclosure. However, as has been indicated above, the techniques described in the present disclosure may be applicable to some other possible technologies, for example with suitable / appropriate adaptation wherever necessary, as can be understood and appreciated by the skilled person.
[0076] References are now made to the figures. In particular, it is to be noted that identical or like reference numbers used in the figures of the present disclosure may, unless indicated otherwise, indicate identical or like elements, such that repeated description thereof may be omitted for reasons of conciseness.
[0077] In 3GPP Rel. 16, Conditional PSCell Change (CPC) has been specified for intra-SN scenario (as provided e.g., in TS 37.340). CPC has been extended in Rel. 17 for inter-SNscenarios where it has two flavours: MN-initiated CPC and SN-initiated CPC (as provided e.g., in R2-2111640).
[0078] This is illustrated in Figure 1 which shows on high-level an exemplary signalling diagram for SN-initiated CPC:
[0079] In step 101, the source SN indicates to the MN the IDs of the target SNs that shall be contacted for preparing target PSCell(s). The source SN suggests a list of PSCell(s) to be prepared by each target SN and provides a CPC execution condition for each suggested target PSCell.
[0080] In step 102 / 103, the MN sends an SN / SgNB addition request to each target SN indicated by the source SN.
[0081] In step 104 / 105, the target SN decides on the candidate target PSCell(s) to prepare among the list of PSCells to be prepared.
[0082] In step 106 / 107, the target SN sends to the MN the CPC configuration for each prepared target PSCell and the IDs of the prepared target PSCell(s).
[0083] In step 108, the MN sends to the UE a conditional (re-)configuration containing the CPC configurations of the candidate target PSCell(s) along with the CPC execution conditions.
[0084] In step 109, the UE sends a message to MN confirming the reception of the conditional configuration and the MN confirms in turn to the source SN the SN change preparation in step 1010.
[0085] In step 1011, the UE evaluates the CPC execution conditions of the prepared target PSCell(s).
[0086] In step 1012, the CPC execution condition is met for e.g. a PSCell candidate in target SN 1.
[0087] The UE sends a message to the MN in step 1013 indicating the execution of the CPC configuration. The message includes an embedded SN RRC Reconfiguration Complete to the target SN 1 which is sent in step 1014.
[0088] The UE completes the random access in step 1015.
[0089] Further Enhanced mobility work item (RP -223520) as part of Release 18 has the following objective:
[0090] Objective 2:2. To specify mechanism and procedures ofNR-DC with selective activation of the cell groups (at least for SCG) via L3 enhancements:o To allow subsequent cell group change after changing CG without reconfiguration and re-initiation of CPC / CPA [RAN2, RAN3, RAN4]
[0091] Further, in 119e RAN2 August meeting the following agreement has been achieved on this topic: The selective activation of cell groups should correspond to support of subsequent conditional changes (CPC) after a cell group change (normal or conditional).
[0092] The objective covers the goal to avoid the releasing of the conditional PSCell addition. So the UE can execute the same conditional PSCell addition multiple times.
[0093] RAN3 119bise meeting in April came up with the following agreement:WA: Add a new indication as a sub IE of the Conditional PSCell Addition Information Request IE in the S-NODE ADDITION REQUEST message to indicate that the request is forSCG Selective Activation, it is FFS (up to RAN2 progress) what form the indication will have (an explicit IE or an RRC container).
[0094] This means that the above Steps 102, 103 in Figure 1 will indicate to the (candidate) target SN about the Conditional PSCell change being related to selective activation feature, and in more detail:• The UE will not release the CPC configuration after executing another CPC.• The candidate target SN will know that the Conditional PSCell change would imply a longer resource reservation. The resource reservation comprises: o the preamble resource, o radio resource reservation for SRB and DRBs and o backhaul resource reservation.• The candidate target SN will know that the UE may not access to the candidate target SN right away as the CPCs are prepared for a longer time scope.
[0095] In this case, when the candidate target SN receives the selective activation based request, the candidate target SN might want to not accept the selective activation request. Thus, it can indicate a SN addition reject message.
[0096] This however may result in UE not having the configuration for conditional PSCell change for the cells controlled by the candidate target SN. Thus, if the UE goes under the coverage of cells controlled by the candidate target SN, the UE may lose dual connectivity or if the network wants to add the PSCell through a legacy PSCell addition. Consequently, this might decrease the UE throughput as it will decrease the uptime of the dual connectivity.
[0097] The above issue is illustrated in Figure 2 which shows on high-level an other exemplary signalling diagram for SN-initiated CPC.
[0098] Steps 201 to 203 as shown in Figure 2 comprise the same operations as steps 101 to 103 as shown in Figure 1, to which reference is made. Optionally, the source SN can indicate that the PSCell change initiated by the source SN is for selective activation, similarly, if the source SN has provided any execution condition, this is for the related procedure.
[0099] Further, in steps 202 and 203, in comparison to steps 102 and 103, the SN / SgNB addition request transmitted from the MN to the target SNs includes a first indicator indicating a request for selective activation for the SCG. The selective activation indication can be optionally triggered by receiving the selective activation indication from the source SN in step 201.
[0100] Figure 2 further shows a case where, at steps 204 and 205, one or more of the (potential) target SNs determine that they cannot accept (support) selective activation.
[0101] In this case, in the further steps 206 and 207, the source MN receives a rejection for the transmitted SN / SgNB addition request. The source MN may then in step 208 decide to send another request without selective activation request, and more specifically send in steps 209 and 210, to the target SNs, another SN / SgNB addition request without selective activation request (i.e., request for legacy CP AC for the SCG).
[0102] However, as shown in step 2011, the target SN 1 (i.e., one of the target SNs) may reject the legacy CP AC request, which means that the second SN / SgNB addition request (without the request for selective activation) is sent unnecessarily to the (candidate) target SN 1. This rejection may be indicated to the MN as shown in step 2013.
[0103] Further, as shown in step 2012, another one of the target SNs (different from the above target SN 1) may accept the legacy CP AC request (for instance, the accpetance may be indicated to the MN as shown in step 2014). However, the legacy CP AC is provided with the additional SN addition request that can be avoided. This causes extra Xn signalling.
[0104] Steps 2015 to 2022 comprise the same operations as steps 108 to 1015 as shown in Figure 1, to which reference is made.
[0105] In view of the above unnecessary transmission of additional SN / SgNB request message(s) from the MN to the target SN(s) and the unnessary extra Xn signaling, it is proposed a solution for the network to indicate that the provided conditional PSCell change configuration can be used for selective activation or a legacy PSCell change.
[0106] To be more specific, it is proposed in accordance with the present application: After the (candidate) target SN(s) receive a request indicated for selective activation, the (candidate) target SNs evaluate for instance the (1) resource reservation possibility, (2) support of the selective activation feature, as a basis for determining whether the request for selective activation can be supported and indicating to the MN a result of this determination, for instance in the form of a second indicator (a PSCell Type Change Indicator) incuded in the SN Add Response Message.
[0107] In accordance with the present application, (candidate) target SN(s) then prepare a selective activation or a legacy conditional PSCell addition and indicates to the source MN for which kind of procedure the conditional configuration is prepared. The source MN accordingly configures the UE with respect to the indication provided by the candidate target SN.
[0108] The solution proposed in accordance with the present application guarantees that, in a case where the (candidate) target SN(s) cannot support the selective activation feature, a legacy PSCell change procedure can be configured to the UE. This guarantees that UE can maintain high throughput for a longer period of time.
[0109] Figure 3 shows on high-level an exemplary signalling diagram for SN-initiated CPC in accordance with an example embodiment provided by the present application.
[0110] Step 301 as shown in Figure 3 comprises the same operations as step 101 shown in Figure 1, to which reference is made. Optionally, the source SN can indicate the PSCell change initiated by SN is for selective activation, similarly, if the SN has provided any execution condition, this is for the selective activation procedure. Similarly in case the indication is lacking, the MN can understand that the execution conditions is for legacy conditional PSCell change.
[0111] In step 302 and 303, the MN indicates the selectivation activation request for conditional PSCell change to the candidate target SNs. Preferably, along with the request also the UE measurements are forwarded to the candidate target SNs. The selective activation indication can be optionally triggered by receiving the selective activation indication from the source SN in step 301.
[0112] In steps 304 and 305, the (candidate) target SN(s) evaluate if they can provide the configuration for selective activation, or provide a conditional PSCell change without the selective activation.
[0113] For the evaluation:The (candidate) target SN(s) estimate the resource reservation for PSCell change.Therein, the estimation comprises multiple aspects: o The (candidate) target SN(s) evaluate the UE measurements to estimate how long it will take the UE to reach (establish a connection to) the candidate target SN(s). o The (candidate) target SN(s) evaluate the probability that the UE will leave the current PCell. (Leaving the current PCell will cancel selective activation. Thus, ending the resource reservation.) o The (candidate) target SN(s) evaluate the amount of radio and backhaul resource reservation needed for the UE and compare to the current load situation for the candidate target PSCell.Parallelly, the (candidate) target SN(s) may reject the selective activation request as it does not support the selective activation feature.The (candidate) target SN(s) may determine to provide the configuration for a legacy CPC if the resource reservation is critical or if it does not support the feature. Criticality of the resource reservation is used in the sense that - the reservation may block a high amount of resources - which might decrease the service capability of the secondary node, leading to rejection of other UEs.
[0114] As shown in steps 306 and 307, the candidate target SN(s) indicate respetively whether the PSCell change configuration and / or the resource reservation is for legacy CPC or selective activation to the source MN. For example, in step 306, the target SN 1 indicates to the MN that the configuration is for selective activation, whereas in step 307, another target SN indicates to the MN that the configuration is for legacy CPC.
[0115] Accordingly, (source) MN is informed about the procedure consideration by the candidate target SN.
[0116] If the candidate target SN cannot fulfil the resource reservation related to the selective activation, the source MN indicates legacy CP AC behavior to the UE, a related CPC execution condition and an indication to release the related conditional PSCell change configuration and / or the related resource.
[0117] If the source MN is informed about the supported selective activation, the source MN configures the UE with an execution condition for each other selective activation candidate cells. The source MN also indicates UE to keep the candidate target PSCell configuration stored after each PSCell change and refraining from releasing or deleting the candidate target PSCell configuration. Optionally, the source MN may indicate to keep the configuration after PSCelladdition or release. In case the source SN has indicated a procedure for selective activation however, the configuration provided by the target SN is not for selective activation or a configuration is not provided. The MN can send a SN modification request and indicate to source SN that the target SN provided a configuration for legacy CP AC or no configuration. As a result the source SN can update the SCG measurement configuration and the related execution condition. The SCG measurement configuration update from selective activation to legacy CPC can comprise removing the execution condition related to PSCell change from the target PSCell to other target PSCells or from the other target PSCell to the target PSCell.
[0118] For instance, the PSCell Change Type Indicator may comprise one bit, wherein a value of “1” indicates selective activation and “0” indicates legacy CP AC.
[0119] Further, for example, in step 308, the MN indicates to the UE that the PSCell change configuration and the resource associated with the target SN 1 is for selective activation, whereas the PSCell change configuration and the resource associated with the other target SN is for legacy CPC. Source MN configures the UE with respect to the information provided to the source MN.
[0120] Steps 309 to 3011 as shown in Figure 3 comprise the same operations as steps 109 to 1011 as shown in Figure 1, to which reference is made.
[0121] In step 3012 as shown in Figure 3, similarly to step 1012 as shown in Figure 1, as an example, the UE determines that the CPC execution condition is met for e.g., a PSCell candidate in the target SN 1 that has indicated selective activation. Further, in step 3013, the UE releases the conditional PSCell change configuration for the legacy CP AC that has been indicated by the other target SN.
[0122] Although the above example is shown in the scenario of SN-initiated PSCell change, it is known to one skilled in the art that the proposed solution of applying a PSCell Change Type Indicator is analogously applicable to other scenarios of PSCell change, for instance, MN- initiated.
[0123] To summarize the above, the target SN Add Req Response provides the reserved resources of the PSCell of the target SN and additionally includes a Type Indicator related to the reserved resources which indicates whether the reserved resources are intended for the legacy CPAC / PSCell change or Rel-18 Selective Activation behavior.
[0124] Source MN is enabled to select between Legacy CPAC and Rel-18 Selective Activation in SN Add Request for a UE and is able to distinguish whether the target SN assigned the reserved resources for the legacy CPAC or Rel-18 Selective Activation behavior.
[0125] Source MN configures the UE with the corresponding measurements and UE behaviour according to the reserved resources in target SN because target SN attached a PSCell Change Type Indicator when sending the resource configuration to source MN.
[0126] Consequently, it is ensured in accordance with the present application that unnecessary signaling can be avoided as the MN and the UE can be directly informed of the intention of the target SNs to perform either legacy CPAC or selective activation. Further, the UE is maintained at an improved throughput since downtime is reduced due to failure to connect to a target SN.
[0127] Based on the above solution proposed in accordance with the present application, theXn interface text proposal has been amended as follows (amendments with underlining)
[0128] It is noted that, although in the above-illustrated example embodiments (with reference to the figures), the messages communi cated / exchanged between the network components / elements may appear to have specific / explicit names, depending on various implementations (e.g., the underlining technologies), these messages may have different names and / or be communi cated / exchanged in different forms / formats, as can be understood and appreciated by the skilled person.
[0129] According to some example embodiments, there are also provided corresponding methods suitable to be carried out by the apparatuses (network elements / components) as described above, such as the UE, the CU, the DU, etc.
[0130] It should nevertheless be noted that the apparatus (device) features described above correspond to respective method features that may however not be explicitly described, for reasons of conciseness. The disclosure of the present document is considered to extend also to such method features. In particular, the present disclosure is understood to relate to methods of operating the devices described above, and / or to providing and / or arranging respective elements of these devices.
[0131] Further, according to some further example embodiments, there is also provided a respective apparatus (e.g., implementing the UE, the CU, the DU, etc., as described above) that comprises at least one processing circuitry, and at least one memory for storing instructions to be executed by the processing circuitry, wherein the at least one memory and the instructions are configured to, with the at least one processing circuitry, cause the respective apparatus to at least perform the respective steps as described above.
[0132] Yet in some other example embodiments, there is provided a respective apparatus (e.g., implementing the UE, the CU, the DU, etc., as described above) that comprises respective means configured to at least perform the respective steps as described above.
[0133] It is to be noted that examples of embodiments of the disclosure are applicable to various different network configurations. In other words, the examples shown in the above described figures, which are used as a basis for the above discussed examples, are only illustrative and do not limit the present disclosure in any way. That is, additional further existing and proposed new functionalities available in a corresponding operating environment may be used in connection with examples of embodiments of the disclosure based on the principles defined.
[0134] It should also to be noted that the disclosed example embodiments can be implemented in many ways using hardware and / or software configurations. For example, the disclosed embodiments may be implemented using dedicated hardware and / or hardware in association with software executable thereon. The components and / or elements in the figures are examples only and do not limit the scope of use or functionality of any hardware, software in combination with hardware, firmware, embedded logic component, or a combination of two or more such components implementing particular embodiments of the present disclosure.
[0135] It should further be noted that the description and drawings merely illustrate the principles of the present disclosure. Those skilled in the art will be able to implement various arrangements that, although not explicitly described or shown herein, embody the principles of the present disclosure and are included within its spirit and scope. Furthermore, all examplesand embodiment outlined in the present disclosure are principally intended expressly to be only for explanatory purposes to help the reader in understanding the principles of the proposed method. Furthermore, all statements herein providing principles, aspects, and embodiments of the present disclosure, as well as specific examples thereof, are intended to encompass equivalents thereof.List of abbreviationsCP AC Conditional PSCell addition changeUE User equipmentRAN Radio access nodeSN Secondary nodeMN Master nodePSCell Primary cell of the secondary cell groupPCell Primary cellFFS For further studyIE Information elementRRC Radio resource controlRB Radio bearerSRB Signalling RBDRB Data RBCFRA Contention Free Random AccessLTM L 1 / 2 triggered mobilitySCG Secondary cell group
Claims
CLAIMS:
1. A target Secondary Node, SN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the target SN is further configured to connect to a User Equipment, UE, and the target SN comprises: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the target SN at least to: receive, from a Master Node, MN, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; select, among one or more PSCells on the basis of the SN addition request message, one or more candidate target PSCells; determine whether to perform the requested selective activation for said selected one or more candidate target PSCells or a Conditional PSCell Change, CPC, without the selective activation; and transmit, to the MN, an SN addition response message comprising a second indicator indicating a result of said determination.
2. The target SN according to claim 1, wherein the target SN is further caused to: receive, via the MN, UE measurements; and estimate resource reservations for said selected one or more candidate target PSCells based on said received UE measurements, for determining whether to perform selective activation for said selected one or more candidate target PSCells.
3. The target SN according to claim 2, wherein the target SN is further caused to perform at least one of the following estimations: evaluate said received UE measurements to estimate a time for the UE to establish a connection to the target SN; evaluate a probability that the UE will leave the current Primary Cell, PCell; and evaluate an amount of radio and backhaul resource reservation needed for the UE and compare said amount to a current load for said selected one or more candidate target PSCells.
4. The target SN according to any one of claims 1 to 3, wherein the target SN is further caused to: reject said selective activation request, when determining that the target SN does not support said selective activation; and preferably indicate to the MN said rejection.
5. The target SN according to any one of claims 1 to 4, wherein the target SN is further caused to: determine to perform CPC without selective activation for said selected one or more candidate target PSCells, when determining that the target SN does not support said selective activation.
6. The target SN according to any one of claims 1 to 5, wherein the target SN is further caused to: configure a capability indicator indicating a capability of the target SN to support a configuration of said second indicator.
7. A Master Node, MN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the MN is further configured to connect to a User Equipment, UE, and the MN comprises: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the MN at least to: transmit, to one or more target SNs, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; receive, from said each target SN, an SN addition response message comprising a second indicator indicating whether said target SN performs selective activation or a Conditional PSCell Change, CPC, for said one or more candidate target PSCells; and determine to configure the UE for said PSCell change based on said received second indicator.
8. The MN according to claim 7, wherein the MN is further caused to:receive, from each of said one or more target SNs, identifications of one or more candidate target PSCells and more preferably CPC execution conditions for said one or more candidate target PSCells; transmit the second indicator to a source SN, and cause the source SN to provide updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the second indicator.
9. The MN according to claim 8, where in the MN is further caused to: transmit the second indicator, when receiving a selective activation indication from the source SN.
10. The MN according to any one of claims 7 to 9, wherein the MN is further caused to: if the second indicator indicates that said target SN does not perform said selective activation for one candidate target PSCell, indicate to the UE to perform Conditional PSCell change, CPC, and a CPC execution condition and / or a candidate target PSCell configuration for said one candidate target PSCell, and preferably indicate to the UE to release said CPC execution condition and / or said candidate target PSCell configuration after PSCell change.
11. The MN according to any one of claims 7 to 9, wherein the MN is further caused to: if the second indicator indicates that said target SN performs said selective activation for one candidate target PSCell, configure the UE with an CPC execution condition for each other candidate target PSCell, and preferably indicate the UE to keep candidate target PSCell configurations stored after each PSCell change and refraining the from releasing or deleting the candidate target PSCell configurations.
12. The MN according to any one of claims 7 to 11, wherein the MN is further caused to: configure a capability indicator indicating a capability of the MN to support a configuration of said first indicator.
13. A source Secondary Node, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the source SN is further configured to connect to a User Equipment, UE, and the source SN comprises: at least one processor, andat least one memory storing instructions that, when executed by the at least one processor, cause the source SN at least to: transmit, to a Master Node, MN, identifications of one or more candidate target PSCells and preferably CPC execution conditions for said one or more candidate target PSCells; receive a PSCell Change Type Indicator from the MN; and transmit, to the MN, updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the PSCell Change Type Indicator.
14. The source SN according to claim 13, wherein the source SN is further caused to: transmit a selective activation indication to the MN indicating, for said one or more candidate target PSCells, whether selective activation is supported.
15. A system, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, the system comprising: a User Equipment, UE, one or more target Secondary Nodes, SNs, in accordance with any one of claims 1 to 6, a Master Node, MN, in accordance with any one of claims 7 to 12, and a source SN in accordance with claim 13 or 14, wherein said UE is connected to said MN and said SNs.
16. A method of a target Secondary Node, SN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the target SN is configured to connect to a User Equipment, UE, the method comprising: receiving, from a Master Node, MN, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; selecting, among one or more PSCells on the basis of the SN addition request message, one or more candidate target PSCells; determining whether to perform the requested selective activation for said selected one or more candidate target PSCells or a Conditional PSCell Change, CPC, without the selective activation; andtransmitting, to the MN, an SN addition response message comprising a second indicator indicating a result of said determination.
17. The method according to claim 16, wherein the target SN further performs the following: receiving, via the MN, UE measurements; and estimating resource reservations for said selected one or more candidate target PSCells based on said received UE measurements, for determining whether to perform selective activation for said selected one or more candidate target PSCells.
18. The method according to claim 17, wherein the target SN further performs at least one of the following estimations: evaluate said received UE measurements to estimate a time for the UE to establish a connection to the target SN; evaluate a probability that the UE will leave the current Primary Cell, PCell; or evaluate an amount of radio and backhaul resource reservation needed for the UE and compare said amount to a current load for said selected one or more candidate target PSCells.
19. The method according to any one of claims 16 to 18, wherein the target SN rejects said selective activation request, when determining that the target SN does not support said selective activation; and preferably indicate to the MN said rejection.
20. The method according to any one of claims 16 to 19, wherein the target SN determines to perform CPC without selective activation for said selected one or more candidate target PSCells, when determining that the target SN does not support said selective activation.
21. The method according to any one of claims 16 to 20, wherein the target SN configures a capability indicator indicating a capability of the target SN to support a configuration of said second indicator.
22. A method of a Master Node, MN, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the MN is configured to connect to a User Equipment, UE, the method comprising:transmitting, to one or more target SNs, an SN addition request message, wherein the SN addition request message comprises a first indicator indicating a request for selective activation for the SCG; receiving, from said each target SN, an SN addition response message comprising a second indicator indicating whether said target SN performs selective activation or a Conditional PSCell Change, CPC, for said one or more candidate target PSCells; and determining to configure the UE for said PSCell change based on said received second indicator.
23. The method according to claim 22, wherein the MN further performs the following: receiving, from each of said one or more target SNs, identifications of one or more candidate target PSCells and more preferably CPC execution conditions for said one or more candidate target PSCells; transmitting the second indicator to a source SN, and causing the source SN to provide updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the second indicator.
24. The method according to claim 22, where in the MN transmits the second indicator, when receiving a selective activation indication from the source SN.
25. The method according to any one of claims 22 to 24, wherein the MN indicates, if the second indicator indicates that said target SN does not perform said selective activation for one candidate target PSCell, to the UE to perform Conditional PSCell change, CPC, and a CPC execution condition and / or a candidate target PSCell configuration for said one candidate target PSCell, and preferably indicate to the UE to release said CPC execution condition and / or said candidate target PSCell configuration after PSCell change.
26. The method according to any one of claims 22 to 24, wherein the MN configures, if the second indicator indicates that said target SN performs said selective activation for one candidate target PSCell, the UE with an CPC execution condition for each other candidate target PSCell, and preferably indicate the UE to keep candidate target PSCell configurations stored after each PSCell change and refraining the from releasing or deleting the candidate target PSCell configurations.
27. The method according to any one of claims 22 to 26, wherein the MN configures a capability indicator indicating a capability of the MN to support a configuration of said first indicator.
28. A method of a source Secondary Node, configured for Primary Secondary Cell, PSCell, change of a Secondary Cell Group, SCG, wherein the source SN is configured to connect to a User Equipment, UE, the method comprising: transmitting, to a Master Node, MN, identifications of one or more candidate target PSCells and preferably CPC execution conditions for said one or more candidate target PSCells; receiving a PSCell Change Type Indicator from the MN; and transmitting, to the MN, updated CPC execution conditions for said one or more candidate target PSCells based on the information indicated by the PSCell Change Type Indicator.
29. The method of claim 28, wherein the source SN transmits a selective activation indication to the MN indicating, for said one or more candidate target PSCells, whether selective activation is supported.
30. A computer program comprising instructions for causing an apparatus to perform the method according to any one of claims 16 to 29.
Citation Information
Patent Citations
Activation / de-activation mechanism for one SCG and scells, and conditional pscell change / addition
WO2022212699A1
Enhanced signalling procedure for SCG mobility in deactivated state using conditional configuration
WO2023066807A1
