MÉTODOS REALIZADOS POR UM EQUIPAMENTO DE USUÁRIO E POR UM NÓ DE REDE, EQUIPAMENTO DE USUÁRIO, NÓ DE REDE, PROGRAMA DE COMPUTADOR, E, PORTADORA CONTENDO O PROGRAMA DE COMPUTADOR

Abstract

A user equipment, UE, (12) is configured for re-using a conditional reconfiguration (40) both for conditional addition of a primary cell of a secondary cell group, PSCell, in multi- connectivity operation and for conditional change of a PSCell in multi-connectivity operation. The UE (12) receives (2000) conditional reconfigurations (40) for respective PSCell target candidate cells. The conditional reconfigurations (40) are either conditional PSCell addition, CPA, configurations or conditional PSCell change, CPC, configurations. Each of the conditional reconfigurations (40) includes a first execution condition (42) and further includes a PSCell target candidate configuration (44) to be applied towards the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed. Each of at least one of the conditional reconfigurations (40) also includes information (46) about how to, upon execution of the conditional reconfiguration (40), update the first execution condition (42) of, or add a second execution condition to, each of one or more others of the conditional reconfigurations (40).

Description

[001] This application relates generally to a communication network and more particularly to the reuse of a conditional reconfiguration in such a network. FUNDAMENTALS

[002] The robustness of multi-connectivity procedures against failures proves challenging, especially in New Radio (NR) systems, whose radio links are more prone to rapid fading due to their higher operating frequencies. Conditional reconfiguration is an approach to improve robustness in this regard. Under this approach, a communication device can be commanded to apply a reconfiguration, for example, a multi-connectivity reconfiguration, before the traditional command. But the communication device is commanded to wait to apply this reconfiguration until the communication device detects that a certain condition has been met. Once the device detects this condition, it can apply the reconfiguration autonomously, without receiving any other signaling on the source radio link, for example, so that the procedure proves robust to changes in channel conditions.

[003] However, these and other types of conditional configurations threaten to increase signaling overhead, resulting in wasted resources and / or reduced system performance. SUMMARY

[004] Some features in this document allow the reuse of a conditional reconfiguration, for example, for multiple Petition 870250081883, dated 11 / 09 / 2025, p. 13 / 236 / 183 different types of multi-connectivity procedures. Some modalities, for example, allow a communication device to reuse the same conditional reconfiguration to add a primary cell of a secondary cell group (SCG) (PSCell) in multi-connectivity operation and to change the primary cell of an SCG. The communication device can, for example, use the conditional reconfiguration to add a PSCell if the communication device is not yet configured with a PSCell or SCG, but use the conditional reconfiguration to change the PSCell if the communication device is already configured with a PSCell or SCG. The reuse of the same conditional reconfiguration advantageously reduces signaling overhead, which in turn reduces resource waste and / or improves system performance.

[005] More specifically, the embodiments described in this document include a method implemented by a user device, UE, to reuse a conditional reconfiguration both for the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation. The method comprises receiving conditional reconfigurations for the respective candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations, CPA, or PSCell alteration conditional configurations, CPC. In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration.In some modes, each of the conditional reconfigurations includes a target candidate PSCell configuration, which is a configuration to be applied to the target candidate PSCell cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some modes, each of at least one of the... Petition 870250081883, dated 11 / 09 / 2025, page 14 / 236 / 183 conditional reconfigurations also includes information on how, after executing the conditional reconfiguration, to update the first execution condition of, or add a second execution condition to, each or more of the other conditional reconfigurations.

[006] In some embodiments, the information included in each of at least one of the conditional reconfigurations is information about how, after the conditional reconfiguration is executed, to add a second execution condition to each or more other conditional reconfigurations. In some embodiments, the conditional reconfigurations are CPA configurations, and the information in each of at least one of the conditional reconfigurations is information about how, after the conditional reconfiguration is executed, to add a second execution condition to each or more other conditional reconfigurations to configure the other conditional reconfiguration to be reusable as a CPC configuration.In some embodiments, the information included in each of at least one of the conditional reconfigurations is information on how, after executing the conditional reconfiguration toward the target PSCell candidate cell of the conditional reconfiguration, to add a second execution condition to each of one or more other conditional reconfigurations to configure the other conditional reconfiguration to be reusable as a CPC configuration that is based on the target PSCell candidate cell of the conditional configuration being a server PSCell for the UE. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the first execution condition needs to be met to trigger the execution of the conditional reconfiguration when the UE is not configured with any server PSCell configuration or with any secondary cell group, SCG.In some modalities, for each of the one or more other conditional reconfigurations to which one. Petition 870250081883, dated 11 / 09 / 2025, page 15 / 236 / 183, the second execution condition is added; the second execution condition must be met to trigger the execution of the conditional reconfiguration when the UE is configured with a server PSCell configuration or with an SCG. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the first execution condition is associated with conditional event A4. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the second execution condition is associated with conditional event A3 or conditional event A5. In some embodiments, the information included in each of at least one of the conditional reconfigurations comprises the second execution condition to be added to each of the one or more other conditional reconfigurations.In some modes, for each of one or more other conditional reconfigurations to which a second execution condition is added, the second execution condition is added to a condExecutionCondSCG information element of the conditional reconfiguration.

[007] In some modes, for each of the conditional reconfigurations, the first execution condition is included in a condExecutionCond information element of the conditional reconfiguration.

[008] In some modes, receiving conditional reconfigurations includes receiving conditional reconfigurations when the UE is not configured with any server PSCell configuration or with any SCG.

[009] In some embodiments, the information included in each of at least one of the conditional reconfigurations is information about how, after the execution of the conditional reconfiguration, to update the first execution condition of each or more other conditional reconfigurations to change the other conditional reconfiguration of a Petition 870250081883, dated 11 / 09 / 2025, page 16 / 236 / 183 CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration.

[0010] In some embodiments, the information included in each of at least one of the conditional reconfigurations is included in the conditional reconfiguration outside the PSCell target candidate configuration of the conditional reconfiguration.

[0011] In some embodiments, receiving conditional reconfigurations involves receiving one or more Radio Resource Control Reconfiguration (RRC) messages, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more of the conditional reconfigurations.

[0012] In some embodiments, the method further comprises detecting the fulfillment of the execution condition included in a first conditional reconfiguration among said conditional reconfigurations. In some embodiments, the method further comprises executing the first conditional reconfiguration based on said detection. In some embodiments, the method further comprises, when executing the first conditional reconfiguration, updating the first execution condition of, or adding a second execution condition to, each or more of the other conditional reconfigurations according to the information included in the first conditional reconfiguration about how to perform said update or addition.In some embodiments, said update or addition comprises adding a second execution condition to each or more of the other conditional reconfigurations according to the information included in the first conditional reconfiguration on how to execute said update or addition. In some embodiments, the method further comprises, after said addition, for each of the one or more other conditional reconfigurations to which a second. Petition 870250081883, dated 11 / 09 / 2025, page 17 / 236 / 183, execution condition is added, determine whether the conditional reconfiguration should be executed by evaluating whether the second execution condition is met. In some embodiments, the method further comprises, after this addition, receiving a message that configures a release of a UE PSCell configuration. In some embodiments, the method further comprises, after said addition, after receiving the message, for each of one or more other conditional reconfigurations to which a second execution condition is added, determining whether to execute the conditional reconfiguration by evaluating whether the first execution condition is met.

[0013] Other embodiments in this document include a method implemented by a network node in a communication network to allow a user device (UE) to reuse a conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells (PSCell) in multi-connectivity operation and the conditional alteration of a PSCell in multi-connectivity operation. The method comprises transmitting conditional reconfigurations to the UE for the respective target candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations (CPA) or PSCell alteration conditional configurations (CPC). In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration.In some embodiments, each of the conditional reconfigurations includes a target candidate PSCell configuration that is a configuration to be applied to the target candidate PSCell cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some embodiments, each of at least one of the conditional reconfigurations also includes information on how, after the... Petition 870250081883, dated 11 / 09 / 2025, page 18 / 236 / 183 execution of the conditional reconfiguration, update the first execution condition of, or add a second execution condition to, each or more of the other conditional reconfigurations.

[0014] In some embodiments, the information included in each of at least one of the conditional reconfigurations is information about how, after the conditional reconfiguration is executed, to add a second execution condition to each or more other conditional reconfigurations. In some embodiments, the conditional reconfigurations are CPA configurations, and the information in each of at least one of the conditional reconfigurations is information about how, after the conditional reconfiguration is executed, to add a second execution condition to each or more other conditional reconfigurations to configure the other conditional reconfiguration to be reusable as a CPC configuration.In some embodiments, the information included in each of at least one of the conditional reconfigurations is information on how, after executing the conditional reconfiguration toward the target PSCell candidate cell of the conditional reconfiguration, to add a second execution condition to each of one or more other conditional reconfigurations to configure the other conditional reconfiguration to be reusable as a CPC configuration that is based on the target PSCell candidate cell of the conditional configuration being a server PSCell for the UE. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the first execution condition needs to be met to trigger the execution of the conditional reconfiguration when the UE is not configured with any server PSCell configuration or with any secondary cell group, SCG.In some modes, for each of one or more other conditional reconfigurations to which a second execution condition is added, the second execution condition. Petition 870250081883, dated 11 / 09 / 2025, page 19 / 236 / 183, needs to be fulfilled to trigger the execution of the conditional reconfiguration when the UE is configured with a server PSCell configuration or with an SCG. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the first execution condition is associated with conditional event A4. In some embodiments, for each of the one or more other conditional reconfigurations to which a second execution condition is added, the second execution condition is associated with conditional event A3 or conditional event A5. In some embodiments, the information included in each of at least one of the conditional reconfigurations comprises the second execution condition to be added to each of the one or more other conditional reconfigurations.In some modes, for each of one or more other conditional reconfigurations to which a second execution condition is added, the second execution condition is added to a condExecutionCondSCG information element of the conditional reconfiguration.

[0015] In some modes, for each of the conditional reconfigurations, the first execution condition is included in a condExecutionCond information element of the conditional reconfiguration.

[0016] In some modes, the transmission of conditional reconfigurations includes the transmission of conditional reconfigurations when the UE is not configured with any server PSCell configuration or with any SCG.

[0017] In some embodiments, the information included in each of at least one of the conditional reconfigurations is information about how, after the execution of the conditional reconfiguration, to update the first execution condition of each or more other conditional reconfigurations to change the other conditional reconfiguration from a CPA configuration to a CPC configuration or from a configuration Petition 870250081883, dated 11 / 09 / 2025, page 20 / 236 / 183 of CPC for a CPA configuration.

[0018] In some embodiments, the information included in each of at least one of the conditional reconfigurations is included in the conditional reconfiguration outside the PSCell target candidate configuration of the conditional reconfiguration.

[0019] In some embodiments, the transmission of conditional reconfigurations comprises the transmission of one or more radio resource control reconfiguration messages, RRC, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more of the conditional reconfigurations.

[0020] Other embodiments in this document include a user device, UE, configured to reuse a conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation. The UE is configured to receive conditional reconfigurations for the respective target candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations, CPA, or PSCell alteration conditional configurations, CPC. In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration.In some embodiments, each of the conditional reconfigurations includes a target candidate PSCell configuration that is a configuration to be applied to the target candidate PSCell cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some embodiments, each of at least one of the conditional reconfigurations also includes information about how, after the conditional reconfiguration is executed, ... Petition 870250081883, dated 11 / 09 / 2025, page 21 / 236 / 183 update the first execution condition of, or add a second execution condition to, each or more of the other conditional reconfigurations.

[0021] In some embodiments, the UE is configured to perform the steps described above for a UE for reuse of a conditional reconfiguration both for conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for conditional alteration of a PSCell in multi-connectivity operation.

[0022] Other embodiments in this document include a network node configured for use in a communication network to allow a user device (UE) to reuse a conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells (PSCell) in multi-connectivity operation and the conditional alteration of a PSCell in multi-connectivity operation. The network node is configured to transmit conditional reconfigurations to the UE for the respective target candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations (CPA) or PSCell alteration conditional configurations (CPC). In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration.In some embodiments, each of the conditional reconfigurations includes a PSCell target candidate configuration that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some embodiments, each of at least one of the conditional reconfigurations also includes information on how, after the conditional reconfiguration is executed, to update the first execution condition, or add a second one. Petition 870250081883, dated 11 / 09 / 2025, page 22 / 236 / 183 condition of execution a, each or more of the other conditional reconfigurations.

[0023] In some embodiments, the network node is configured to perform the steps described above for a network node in a communication network to allow a user device, UE, to reuse a conditional reconfiguration both for the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation.

[0024] In some embodiments, a computer program comprising instructions that, when executed by at least one processor of a user device, cause the user device to execute the steps described above for a UE for reuse of a conditional reconfiguration both for conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for conditional alteration of a PSCell in multi-connectivity operation.

[0025] In some embodiments, a computer program comprising instructions that, when executed by at least one processor of a user device, cause the user device to perform the steps described above for a network node in a communication network to enable a user device, UE, to reuse a conditional reconfiguration both for the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation.

[0026] In some embodiments, a carrier containing the computer program is an electronic signal, optical signal, radio signal, or computer-readable storage medium. Petition 870250081883, dated 11 / 09 / 2025, page 23 / 236 / 183

[0027] Other embodiments in this document include a user device, UE, configured to reuse a conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation. The UE comprises a set of communication circuits and a set of processing circuits. The processing circuit set is configured to receive conditional reconfigurations for the respective target candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations, CPA, or PSCell alteration conditional configurations, CPC. In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration.In some embodiments, each of the conditional reconfigurations includes a target candidate PSCell configuration that is a configuration to be applied to the target candidate PSCell cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some embodiments, each of at least one of the conditional reconfigurations also includes information on how, after the conditional reconfiguration is executed, to update the first execution condition of, or add a second execution condition to, each or more of the other conditional reconfigurations.

[0028] In some embodiments, the processing circuitry is configured to perform the steps described above for a UE for reuse of a conditional reconfiguration both for conditional addition of a primary cell from a group of secondary cells, PSCell, in multiconnectivity operation and for conditional alteration of a PSCell in multiconnectivity operation. Petition 870250081883, dated 11 / 09 / 2025, page 24 / 236 / 183

[0029] Other embodiments in this document include a network node configured for use in a communication network to allow a user device, UE, to reuse a conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for the conditional alteration of a PSCell in multi-connectivity operation. The network node comprises a communication circuit set and a processing circuit set. The processing circuit set is configured to transmit, through the communication circuit set, to the UE, conditional reconfigurations for the respective target candidate PSCell cells. In some embodiments, the conditional reconfigurations are PSCell addition conditional configurations, CPA, or PSCell alteration conditional configurations, CPC.In some embodiments, each of the conditional reconfigurations includes a first execution condition that needs to be met to trigger the execution of the conditional reconfiguration. In some embodiments, each of the conditional reconfigurations includes a PSCell target candidate configuration that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration when the conditional reconfiguration is executed. In some embodiments, each of at least one of the conditional reconfigurations also includes information on how, after the execution of the conditional reconfiguration, to update the first execution condition of, or add a second execution condition to, each or more of the other conditional reconfigurations.

[0030] In some embodiments, the processing circuitry is configured to perform the steps described above for a network node in a communication network to allow a user device, UE, to reuse a conditional reconfiguration for both the conditional addition of a primary cell to a group of secondary cells, Petition 870250081883, dated 11 / 09 / 2025, page 25 / 236 / 183 PSCell, in multi-connectivity operation as well as for conditional modification of a PSCell in multi-connectivity operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] Figure 1 is a block diagram of a communication network according to some modalities.

[0032] Figure 2 is a block diagram of a conditional reconfiguration transmitted from a network node to a communication device according to some modes.

[0033] Figure 3 is a block diagram of a conditional reconfiguration according to some modalities.

[0034] Figure 4 is a block diagram of a conditional reconfiguration according to other modalities.

[0035] Figure 5 is a block diagram of a conditional reconfiguration according to other modalities.

[0036] Figure 6 is a block diagram of a conditional reconfiguration according to other modalities.

[0037] Figure 7 is a block diagram of a conditional reconfiguration according to other modalities.

[0038] Figure 8 is a block diagram of conditional reconfigurations transmitted from a network node to a communication device in a communication network according to other modes.

[0039] Figure 9A is a block diagram of conditional reconfigurations according to some modalities.

[0040] Figure 9B is a block diagram of conditional reconfigurations according to other modalities.

[0041] Figure 10 is a block diagram of dual connectivity configured for a User Equipment, UE, according to some modalities. Petition 870250081883, dated 11 / 09 / 2025, page 26 / 236 / 183

[0042] Figure 11 is a block diagram of dual connectivity configured for a User Equipment, UE, according to other modalities.

[0043] Figure 12 is a dual connectivity block diagram configured for a User Equipment, UE, according to other modalities.

[0044] Figure 13 is a call flowchart for a server cell and a target cell, according to some modalities.

[0045] Figure 14 is a call flowchart for a server cell and a target cell, according to some modalities.

[0046] Figure 15 is a logical flowchart of a method performed by a communication device according to particular modalities.

[0047] Figure 16 is a logical flowchart of a method performed by a communication device according to particular modalities.

[0048] Figure 17 is a logical flowchart of a method performed by a communication device according to particular modalities.

[0049] Figure 18 is a logical flowchart of a method performed by a network node according to particular modalities.

[0050] Figure 19 is a logical flowchart of a method performed by a network node according to particular modalities.

[0051] Figure 20 is a logical flowchart of a method performed by a UE according to particular modalities.

[0052] Figure 21 is a logical flowchart of a method performed by a network node according to particular modalities.

[0053] Figure 22 is a block diagram of a communication device according to particular modes.

[0054] Figure 23 is a block diagram of a network node according to particular modalities.

[0055] Figure 24 is a block diagram of a system of Petition 870250081883, dated 11 / 09 / 2025, page 27 / 236 / 183 communication in accordance with some modalities.

[0056] Figure 25 is a block diagram of a user device according to some modalities.

[0057] Figure 26 is a block diagram of a network node according to some modalities.

[0058] Figure 27 is a block diagram of a host according to some modalities.

[0059] Figure 28 is a block diagram of a virtualization environment according to some modalities.

[0060] Figure 29 is a block diagram of a host communicating through a network node with a UE via a partially wireless connection according to some modes. DETAILED DESCRIPTION

[0061] Figure 1 shows a communication network 10 according to some embodiments. The communication network 10 is configured to provide communication service to a communication device 12, for example, a user equipment (UE). The network 10, as shown, includes radio network nodes 14A and 14B, for example, in the form of base stations. The radio network nodes 14A and 14B can be included in a radio access network (RAN) portion of the network 10, which, in turn, can connect to a core network (CN) portion (not shown).

[0062] Each 14A and 14B radio network node serves one or more cells. As shown, for example, a first 14A radio network node provides a first group of 16A cells which includes N cells 16A1,...16A-N, for N > 1. A second 14B radio network node provides a second group of 16B cells which includes M cells 16B-1,.16B-M, for M > 1. Different cells may, for example, be provided on different carrier frequencies, with different frequency bandwidths and / or using different radio access technologies. Petition 870250081883, dated 11 / 09 / 2025, page 28 / 236 / 183

[0063] In some embodiments, communication device 12 is configured with and / or is capable of multi-connectivity operation. In multi-connectivity operation, communication device 12 connects simultaneously, for example, at a radio resource control layer, RRC, to several different radio network nodes 14A, 14B, or to several different cells served by different radio network nodes 14A, 14B. The various different radio network nodes or cells may use the same radio access technology, for example, both may use Evolved Terrestrial Radio Universal Access (E-UTRA) or both may use New Radio (NR). Or, the various different radio network nodes or cells may use different radio access technologies, for example, one may use E-UTRA and another may use NR.

[0064] An example of multiconnectivity is dual connectivity (DC), in which communication device 12 is simultaneously connected to two different radio network nodes or to two different cells served by two different radio network nodes. In this case, communication device 12 can be configured with a so-called master cell group (MCG) and a secondary cell group (SCG). Here, the MCG includes one or more cells served by the radio network node acting as a master node, i.e., a group of server cells associated with the master node. The MCG may include a primary cell and, optionally, one or more secondary cells. The primary cell of the MCG is called a PCell. The SCG includes one or more cells served by the radio network node acting as a secondary node, i.e., a group of server cells associated with the secondary node. The SCG may include a primary cell and, optionally, one or more secondary cells.The primary cell of the SCG is called a PSCell.

[0065] The master node can be a master in the sense that it controls the secondary node. Alternatively or additionally, the master node can be a master in the sense that it is a radio access node that provides the connection. Petition 870250081883, dated 11 / 09 / 2025, page 29 / 236 / 183 of the control plane for communication device 12 with the core network, while the secondary node does not have a connection from the control plane to communication device 12 with the core network.

[0066] Different types of dual connectivity can be employed by different modes. In some modes, communication device 12 operates with E-UTRA-NR (EN) DC, where the master node uses E-UTRA and the secondary node uses NR. In other modes, communication device 12 operates with NR-E-UTRA (NE) DC, where the master node uses NR and the secondary node uses E-UTRA. In other modes, communication device 12 operates with NR-DC, where both the master and secondary nodes use NR. However, in general, communication device 12, in some modes, operates with multi-radio DC (MR), which refers to dual connectivity between E-UTRA and NR nodes, or between two NR nodes.Therefore, MR-DC can be seen as a generalization of Intra-U-UTRA DC, where a device capable of multiple receivers / transmitters is configured to utilize resources provided by two different nodes connected via a non-ideal backhaul, one providing NR access and the other providing E-UTRA or NR access. Regardless, in MR-DC, communication device 12 can have a single RRC state, based on the master node's RRC, and a single control plane connection to the core network. The RRC protocol data units (PDUs) generated by the secondary node can be transmitted by the master node to communication device 12.

[0067] In this context, Figure 2 shows that the communication device 12, in some modes, receives a conditional reconfiguration 20, for example, from a network node 14, which may be radio network node 14A or radio network node 14B in Figure 1. The conditional reconfiguration 20 may be received in a message, for example, an RRC message, in which case the message may include one or more Petition 870250081883, dated 11 / 09 / 2025, p. 30 / 236 / 183 conditional reconfigurations, including conditional reconfiguration 20.

[0068] Conditional reconfiguration 20, as shown, includes a configuration 22 of a candidate target cell. The candidate target cell may be a candidate to be the target of a multi-connectivity procedure, for example, a PSCell addition procedure or a PSCell alteration procedure. The configuration 22 may take the form of an RRC configuration that the communication device 12 must apply, for example, as part of the execution of a procedure, when a condition is met.

[0069] The conditional reconfiguration 20, in this sense, includes the first and second conditions 24-1, 24-2. In some cases, the first and second conditions 24-1, 24-2 are alternative conditions, where the fulfillment of either of them triggers the communication device 12 to apply the configuration 22 of the candidate target cell.

[0070] However, in some embodiments, communication device 12 is configured to evaluate the first and second conditions 24-1, 24-2 under different circumstances. Communication device 12 must evaluate the first condition 24-1, to determine whether to apply configuration 22, when communication device 12 is not configured with a server PSCell, for example, because communication device 12 is not configured with any SCG. Conversely, communication device 12 must evaluate the second condition 24-2, to determine whether to apply configuration 22, when communication device 12 is configured with a server PSCell.

[0071] In these and other modalities, the inclusion of the first and second conditions 24-1 and 24-2 may allow the reuse of conditional configuration 20. For example, the conditional reconfiguration may be reusable for adding or changing PSCell. In this case, the reconfiguration of condition 20 may correspond to a PSCell addition configuration. Petition 870250081883, dated 11 / 09 / 2025, page 31 / 236 / 183 conditional when communication device 12 is not configured with a server PSCell and corresponds to a conditional PSCell change configuration when communication device 12 is configured with a server PSCell.

[0072] In some modalities, as shown in Figure 3, the conditional reconfiguration 20 includes an execution condition field 26 that indicates the first and second conditions 24-1 and 24-2. The execution condition field 26 can do this directly or indirectly.

[0073] As an example, Figure 4 shows that, in some modes, the execution condition field 26 identifies a measurement configuration 28. The measurement configuration 28 is associated with a reporting configuration 30. And the reporting configuration 30 indicates the first and second conditions 24-1 and 24-2. For details on variations of these modes, see Figure 15 and its description, as well as Modes A4-A11 in GROUP A MODES described in this document.

[0074] Figure 5 shows another example. In this example, the execution condition field 26 also identifies a measurement configuration 28. But the measurement configuration 28 is associated with the first and second report configurations 30-1, 30-2. The first report configuration 30-1 indicates the first condition 24-1 and the second report configuration 30-2 indicates the second condition 24-2. For details on variations of these modes, see Figure 15 and its description, as well as Modes A13-A14 in GROUP A MODALITIES described in this document.

[0075] Figure 6 shows yet another example. In this example, the execution condition field 26 identifies the first and second measurement configurations 28-1, 28-2. The first measurement configuration 28-1 is associated with a first report configuration 30-1, and the Petition 870250081883, dated 11 / 09 / 2025, page 32 / 236 / 183, second measurement configuration 28-2 is associated with a second reporting configuration 30-2. The first reporting configuration 30-1 indicates the first condition 24-1 and the second reporting configuration 30-2 indicates the second condition 24-2. For details on variations of these modes, see Figure 15 and its description, as well as Modes A16-A19 in GROUP A MODALITIES described in this document.

[0076] Figure 7 shows other embodiments in which the conditional reconfiguration 20 includes the first and second execution condition fields 26-1 and 26-2, which indicate, respectively, the first and second conditions 24-1 and 24-2. In this example, the first execution condition field 26-1 identifies a first measurement configuration 28-1, and the second execution condition field 26-2 identifies a second measurement configuration 28-2. The first measurement configuration 28-1 is associated with a first report configuration 30-1, and the second measurement configuration 28-2 is associated with a second report configuration 30-2. The first report configuration 30-1 indicates the first condition 24-1 and the second report configuration 30-2 indicates the second condition 24-2. For details on the variations of these modalities, see Figure 15 and its description, as well as Modalities A22-A23 in GROUP A MODALITIES described in this document.

[0077] Figure 8 shows further other embodiments described in this document. As shown, the communication device 12, in some embodiments, receives multiple 401...40-N conditional reconfigurations, generally referred to as 40 conditional reconfigurations. The communication device 12 can receive the 40 conditional reconfigurations from a network node 14, which can be radio network node 14A or radio network node 14B in Figure 1. At least some of the reconfigurations Petition 870250081883, dated 11 / 09 / 2025, p. 33 / 236 / 183 conditional 40 may be received in the same message or in different messages, for example, in RRC message(s). In one of these modes, the communication device 12 may receive one or more radio resource control reconfiguration (RRC) messages, where each RRC reconfiguration message includes an information element (IE) condReconfigToAddModList comprising a list of one or more of the conditional reconfigurations 40-1.. ,40-N.

[0078] Conditional reconfigurations 40 are for candidate target cells, for example, that are candidates to be targeted by a multi-connectivity procedure, such as a PSCell addition procedure or a PSCell alteration procedure. For example, conditional reconfigurations 40 can be for PSCell candidate target cells. In this case, conditional reconfigurations 40 can be PSCell addition conditional configurations (CPA) or PSCell alteration conditional configurations (CPC).

[0079] Each of the conditional reconfigurations 40-1.40-N includes a corresponding execution condition 42-1.42-N and a corresponding candidate-target configuration 44-1.44-N. The execution condition 42 included in a conditional reconfiguration 40 is a condition that needs to be met to trigger the execution of the conditional reconfiguration 40. The candidate-target configuration 44 included in a conditional reconfiguration 40 is a configuration to be applied to the candidate-target cell of the conditional reconfiguration 40 when it is executed. When the candidate-target cells are candidate PSCells, then a candidate-target configuration 44 can be a candidate-target configuration of a PSCell. In any case, the candidate-target configuration 44 can take the form of an RRC configuration that the communication device 12 must apply, for example, as part of the execution of a procedure, when the conditional reconfiguration 40 is executed. Petition 870250081883, dated 11 / 09 / 2025, p. 34 / 236 / 183

[0080] Notably, each of at least one of the 40-1...40-N conditional reconfigurations also includes the 461...46-N information. In some cases, the 46-1.46-N information included in each of at least one of the 40-1.40-N conditional reconfigurations is information about how, after the execution of the 441.44-N conditional reconfiguration, to update the 42-1.42-N execution condition of each or more of the 44-1.44-N conditional reconfigurations. As shown, for example, the 46-1.46-N information included in each of at least one of the 40-1.40-N conditional reconfigurations can be included in conditional reconfiguration 40 outside of the target candidate configuration 44 of conditional reconfiguration 40. In modes where the target candidate cells are candidate PSCells, the 46-1.46-N information included in each of at least one of the 40-1.40N conditional reconfigurations can be information about how, after the execution of conditional reconfiguration 40-1.40-N, update the 42-1.42-N execution condition of each or more of the other 40-1.40-N conditional reconfigurations to change the other conditional reconfiguration from a CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration. Information about how to update a 42 execution condition may, for example, include an updated execution condition that should replace the existing execution condition.

[0081] Figure 9A, for example, shows a simple example for two conditional reconfigurations 40-1 and 40-2. In this example, conditional reconfiguration 40-1 includes information 46-1 about how, after the execution of conditional reconfiguration 40-1, to update the execution condition 42-2 of conditional reconfiguration 40-2. Similarly, in some embodiments, conditional reconfiguration 40-2 includes information 46-2 about how, after the execution of conditional reconfiguration 40-2, to update the execution condition 42-1 of conditional reconfiguration 40-1. Petition 870250081883, dated 11 / 09 / 2025, page 35 / 236 / 183

[0082] In some embodiments, for example, the conditional reconfigurations 40-1 and 40-2 received by communication device 12 are CPA configurations. This may be the case, for example, where communication device 12 receives the conditional reconfigurations 40-1 and 40-2 when communication device 12 is not configured with any server PSCell configuration. Regardless, in this case, the information 46-1 in the conditional reconfiguration 40-1 may be information on how, after the execution of the conditional reconfiguration 401, to update the execution condition 42-2 of the conditional reconfiguration 40-2 to change that conditional reconfiguration 40-2 to a CPC configuration, for example, which is based on the target candidate PSCell cell of the conditional configuration 40-1 being a server PSCell for communication device 12.Information 46-1 could be, for example, information on how to update the execution condition 42-2 of the conditional reconfiguration 40-2 from being associated with conditional event A4 to being associated with conditional event A3 or conditional event A5. This would allow the conditional reconfiguration 40-2 (originally a CPA configuration) to be reused as a CPC configuration, that is, the conditional reconfiguration 40-2 could be reused for both CPA and CPC. In other words, after communication device 12 detects the fulfillment of execution condition 42-1 and executes conditional reconfiguration 40-1 for CPA, the conditional reconfiguration 40-2 that was not executed for CPA is updated based on information 46-1, so as to convert that conditional reconfiguration 40-2 to be a candidate for CPC.

[0083] Similarly, information 46-2 in conditional reconfiguration 40-2 may be information about how, after the execution of conditional reconfiguration 40-2, to update the execution condition 42-1 of conditional reconfiguration 40-1 to transform it into a configuration of Petition 870250081883, dated 11 / 09 / 2025, page 36 / 236 / 183 CPC, for example, based on the target candidate cell of the conditional configuration 40-2 being a server PSCell for communication device 12. Information 46-2 could, for example, be information on how to update the execution condition 42-1 of the conditional reconfiguration 40-1, changing it from being associated with conditional event A4 to being associated with conditional event A3 or conditional event A5. This would similarly allow the conditional reconfiguration 40-1 (originally a CPA configuration) to be reused as a CPC configuration, i.e., so that the conditional reconfiguration 40-1 could be reused for both CPA and CPC.That is, after communication device 12 detects the fulfillment of execution condition 42-2 and executes conditional reconfiguration 40-2 for CPA, conditional reconfiguration 40-1, which was not executed for CPA, is updated based on information 46-2, in order to convert that conditional reconfiguration 40-1 into a candidate for CPC.

[0084] In other embodiments, as another example, the conditional reconfigurations 40-1 and 40-2 received by communication device 12 are CPC configurations. This may be the case, for example, where communication device 12 receives conditional reconfigurations 40-1 and 40-2 when communication device 12 is configured with a server PSCell configuration. Regardless, in this case, the information 46-1 in conditional reconfiguration 40-1 may be information on how, after the execution of conditional reconfiguration 40-1, to update the execution condition 42-2 of conditional reconfiguration 40-2 to transform that conditional reconfiguration 40-2 into a CPA configuration. The information 46-1 may, for example, be information on how to update the execution condition 42-2 of conditional reconfiguration 40-2 so that it is not associated with conditional event A3 or that conditional event A5 is associated with Petition 870250081883, dated 11 / 09 / 2025, page 37 / 236 / 183, conditional event A4. This would allow conditional reconfiguration 40-2 (originally a CPC configuration) to be reused as a CPA configuration, that is, conditional reconfiguration 40-2 could be reused for both CPA and CPC. In other words, after communication device 12 detects the fulfillment of execution condition 42-1 and executes conditional reconfiguration 40-1 for CPC, the conditional reconfiguration 40-2 that was not executed for CPC is updated based on information 46-1, so as to convert that conditional reconfiguration 40-2 into a candidate for CPA.

[0085] Similarly, in this case, information 46-2 in conditional reconfiguration 40-2 could be information about how, after the execution of conditional reconfiguration 40-2, to update the execution condition 42-1 of conditional reconfiguration 40-1 to transform that conditional reconfiguration 40-1 into a CPA configuration. Information 46-2 could be, for example, information about how to update the execution condition 42-1 of conditional reconfiguration 40-1 from being associated with conditional event A3 or conditional event A5 to being associated with conditional event A4. This would similarly allow conditional reconfiguration 40-1 (originally a CPC configuration) to be reused as a CPA configuration, that is, for conditional reconfiguration 40-1 to be reused for both CPA and CPC.That is, after communication device 12 detects the fulfillment of execution condition 42-2 and executes conditional reconfiguration 40-2 for CPC, conditional reconfiguration 40-1, which was not executed for CPC, is updated based on information 46-2, in order to convert that conditional reconfiguration 40-1 into a candidate for CPA.

[0086] In other modalities, the 46-1...46-N information included in each of at least one of the 40-1...40N conditional reconfigurations in Figure 8 is information about how, after the execution of the Petition 870250081883, dated 11 / 09 / 2025, page 38 / 236 / 183 conditional reconfiguration 44-1...44-N, add a new execution condition (not shown) to each or more of the conditional reconfigurations 44-1...44-N. Such information 46-1...46-N included in each of at least one of the conditional reconfigurations 40-1.40-N may be included in conditional reconfiguration 40 outside of the target candidate configuration 44 of conditional reconfiguration 40. In modes where the target candidate cells are candidate PSCells, the information 46-1.46-N included in each of at least one of the conditional reconfigurations 401.40-N may be information about how, after the execution of conditional reconfiguration 40-1.40-N, to add a new execution condition to each or more of the other conditional reconfigurations 401.40-N to configure the other conditional reconfiguration to be reused as a CPC configuration (if originally a CPA configuration) or as a CPA configuration (if originally a CPC configuration). Information on how to add a new execution condition may, for example, include the new execution condition that should be added.

[0087] Figure 9B, for example, shows a simple example for two conditional reconfigurations 40-1 and 40-2. Conditional reconfiguration 40-1, as received, includes execution condition 42-1, called first execution condition 42-1, while conditional reconfiguration 40-2, as received, includes execution condition 42-2, called first execution condition 42-2. Thus, the original execution conditions 42-1 and 42-2 included in conditional reconfigurations 40-1 and 40-2, as received, are called first execution conditions 42-1 and 42-2. In this example, conditional reconfiguration 40-1 includes information 46-1 on how, after the execution of conditional reconfiguration 40-1, to add a second execution condition 43-2 to conditional reconfiguration 40-2. Similarly, in some embodiments, the Petition 870250081883, dated 11 / 09 / 2025, page 39 / 236 / 183, conditional reconfiguration 40-2 includes information 46-2 on how, after the execution of conditional reconfiguration 40-2, to add a second execution condition 43-1 to conditional reconfiguration 40-1. The second execution conditions 43-1, 43-2 to be added to conditional reconfigurations 40-1, 40-2 are therefore new execution conditions, in the sense that they are added recently since the receipt of conditional reconfigurations 40-1, 40-2.

[0088] In some embodiments, for example, the conditional reconfigurations 40-1 and 40-2 received by communication device 12 are CPA configurations. This may be the case, for example, where communication device 12 receives the conditional reconfigurations 40-1 and 40-2 when communication device 12 is not configured with any server PSCell configuration or any SCG. Regardless, in this case, the information 46-1 in the conditional reconfiguration 40-1 may be information on how, after the execution of the conditional reconfiguration 40-1, to add the second execution condition 43-2 to the conditional reconfiguration 40-2 to configure that conditional reconfiguration 40-2 to be reused as a CPC configuration, for example, which is based on the target candidate PSCell cell of the conditional configuration 40-1 being a server PSCell for communication device 12.In some embodiments, for example, the first execution condition 42-2 of the conditional reconfiguration 40-2 can be associated with the conditional event A4 (which is usable for CPA, not CPC), but the second execution condition 43-2 of the conditional reconfiguration 40-2 can be associated with the conditional event A3 or the conditional event A5 (which is usable for CPC, not CPA). Adding the second execution condition 43-2 therefore allows the conditional reconfiguration 40-2 (originally a CPA configuration) to be reused as a CPC configuration. That is, after communication device 12 detects it. Petition 870250081883, dated 11 / 09 / 2025, page 40 / 236 / 183: Upon fulfillment of the first execution condition 42-1 of the conditional reconfiguration 40-1 and execution of the conditional reconfiguration 40-1 for CPA, communication device 12 uses the information 46-1 included in the conditional reconfiguration 40-1 that was executed for CPA to add the second execution condition 43-2 to the conditional reconfiguration 40-2 that was not executed for CPA. This allows the conditional reconfiguration 40-2 that was not executed for CPA to be reused for CPC, so that the conditional reconfiguration 40-2 becomes a candidate for CPC.

[0089] Similarly, information 46-2 in conditional reconfiguration 40-2 may be information about how, after executing conditional reconfiguration 40-2, to add the second execution condition 43-1 to conditional reconfiguration 40-1 to configure that conditional reconfiguration 40-1 to be reused as a CPC configuration, for example, which is based on the target candidate cell of PSCell from conditional configuration 40-2 being a server PSCell for communication device 12. In some embodiments, for example, the first execution condition 42-1 of conditional reconfiguration 40-1 may be associated with conditional event A4 (which is usable for CPA, not CPC), but the second execution condition 43-1 of conditional reconfiguration 40-1 may be associated with conditional event A3 or conditional event A5 (which is usable for CPC, not CPA).The addition of the second execution condition 43-1 therefore allows the conditional reconfiguration 40-1 (originally a CPA configuration) to be reused as a CPC configuration. That is, after communication device 12 detects the fulfillment of the first execution condition 42-2 of the conditional reconfiguration 40-2 and executes the conditional reconfiguration 40-2 for CPA, communication device 12 uses the information 46-2 included in the conditional reconfiguration 40-2 that was executed for CPA to add the second execution condition 43-1 to the conditional reconfiguration 40-1 that... Petition 870250081883, dated 11 / 09 / 2025, page 41 / 236 / 183, was not executed for CPA. This allows the 40-1 conditional reconfiguration that was not executed for CPA to be reused for CPC, so that the 40-1 conditional reconfiguration becomes a CPC candidate.

[0090] In the examples above, the conditional events A3, A4, and A5 can be described as follows.

[0091] CondEvent A3: The candidate for conditional reconfiguration becomes a better displacement amount than PCell / PSCell.

[0092] CondEvent A4: The candidate for conditional reconfiguration becomes better than the absolute limit.

[0093] CondEvent A5: PCell / PSCell becomes worse than absolute limit 1 AND the candidate for conditional reconfiguration becomes better than another absolute limit 2.

[0094] Some embodiments described in this document will now be considered applicable in the following context, where communication device 12 is exemplified as a UE and where communication network 10 is exemplified as a 5G network. Dual 3GPP connectivity

[0095] Some modalities described in this document are applicable to Dual Connectivity. In 3GPP Rel-12, the Long Term Evolution (LTE) Dual Connectivity (DC) feature was introduced to allow the UE to be connected in two cell groups, each controlled by an LTE access node (eNB), designated as Master eNB (MeNB) and Secondary eNB (SeNB). The UE still only has one RRC connection to the network. In 3GPP, the Dual Connectivity (DC) solution has since evolved and is now also specified for New Radio (NR), as well as between LTE and NR. Multiconnectivity (MC) occurs when more than two nodes are involved. With the introduction of 5G, the term MR-DC (Multi-Radio Dual Connectivity, see also 3GPP TS 37.340 V17.3.0) was defined as a generic term for all connectivity options. Petition 870250081883, dated 11 / 09 / 2025, page 42 / 236 / 183, double, which includes at least one NR access node. Using the generalized MR-DC terminology, the UE is connected to a Master Cell Group (MCG), controlled by the Master Node (MN), and a Secondary Cell Group (SCG), controlled by a Secondary Node (SN).

[0096] Furthermore, in MR-DC, when dual connectivity is configured for the UE, within each of the two cell groups, MCG and SCG, carrier aggregation can also be used. In this case, within the Master Cell Group, MCG, controlled by the master node (MN), the UE can use a PCell and one or more SCell(s). And within the Secondary Cell Group (SCG), controlled by the secondary node (SN), the UE can use a Primary SCell (PSCell, also known as the primary SCG cell in NR) and one or more SCell(s). This combined case is illustrated in Figure 10. In NR, the primary cell of a master or secondary cell group is sometimes also called a Special Cell (SpCell). Therefore, the SpCell in the MCG is the PCell and the SpCell in the SCG is the PSCell.

[0097] Some embodiments in this document are applicable in various ways to deploy a 5G network with or without interoperability with LTE (also known as E-UTRA) and evolved packet core (EPC). In principle, NR and LTE can be deployed without any interoperability, denoted by the autonomous operation (SA) of NR, also known as Option 2; that is, the gNB in ​​NR can be connected to the 5G core network (5GC) and the eNB in ​​LTE can be connected to the evolved packet core (EPC) without interconnection between the two, also known as Option 1.

[0098] On the other hand, the first supported version of NR uses dual connectivity, denoted as EN-DC (Dual Connectivity EUTRAN-NR), also known as Option 3, as illustrated in Figure 11. In such a deployment, dual connectivity is applied between NR and LTE, where the UE is connected both by the LTE radio interface (LTE Uu in the figure) Petition 870250081883, dated 11 / 09 / 2025, page 43 / 236 / 183 to an LTE access node as well as through the NR radio interface (NR Uu in the figure) to an NR access node. Furthermore, in EN-DC, the LTE access node acts as the master node (in this case known as eNB Master, MeNB), controlling the master cell group (MCG), and the NR access node acts as the secondary node (in this case, sometimes also known as gNB Secondary (SgNB)), controlling the secondary cell group (SCG). The SgNB may not have a control plane connection to the main network (EPC), which is instead provided by the MeNB and, in this case, by the NR. This is also called “non-standalone NR” ​​or, in short, “NSA NR”. Note that, in this case, the functionality of an NR cell is limited and would be used for UEs in connected mode as a booster and / or diversity segment, but an RRC_IDLE UE cannot camp in these NR cells.

[0099] Some modalities described in this document are also applicable to other valid options with the introduction of 5GC. As mentioned above, Option 2 supports the standalone deployment of NR, where gNB is connected to 5GC. Similarly, LTE can also be connected to 5GC using Option 5 (also known as eLTE, E-UTRA / 5GC or LTE / 5GC, and the node can be called ng-eNB). In these cases, both NR and LTE are seen as part of the NG-RAN (and both ng-eNB and gNB can be called NG-RAN nodes).

[00100] Some modalities described in this document are also applicable to other variants of dual connectivity between LTE and NR, which have been standardized as part of the NG-RAN connected to the 5GC. Under the scope of MR-DC, this includes: (i) EN-DC (Option 3) where LTE is the master node and NR is the secondary node (EPC core network (CN) employed, as illustrated in Figure 11); (ii) NE-DC (Option 4) where NR is the master node and LTE is the secondary node (5GCN employed); (iii) NGEN-DC (Option 7) where LTE is the master node and NR is the secondary node (5GCN employed); and / or (iv) NR-DC (variant of Option 2) which involves dual connectivity where both the master node, MN, Petition 870250081883, dated 11 / 09 / 2025, page 44 / 236 / 183, which controls the MCG, as well as the secondary node, SN, which controls the SCG, are NR (5GCN employed, as illustrated in Figure 12). In particular, Figure 12 shows a scenario where the master node, MN, which controls the MCG is a gNB connected to the 5GC and serving the UE via NR, and also the secondary node, SN, which controls the SCG is a gNB connected to the 5GC and serving the UE via NR. Conditional Handover (CHO)

[00101] Some modes have their roots in conditional transfer, as specified by 3GPP. In 3GPP Rel-16, conditional transfer was standardized as a solution to increase robustness in transfer. To avoid undesirable dependence of the server radio link on the time (and radio conditions) in which the UE must perform the transfer, the possibility of providing Radio Resource Control (RRC) signaling for the transfer to the latest UE was standardized. It is possible to associate the HO command with a condition, for example, based on radio conditions possibly similar to those associated with an A3 event, where a given neighbor becomes X dB better than the target. As soon as the condition is met, the UE performs the transfer according to the provided transfer command.

[00102] Such a condition could, for example, be that the quality of the target cell or beam becomes X dB stronger than that of the server cell. The Y threshold used in a previous measurement report event should then be chosen as lower than that of the handover execution condition. This allows the server cell to prepare the handover after receiving an advance measurement report and provide the RRCConnectionReconfiguration with mobilityControlInfo (or the RRCReconfiguration with reconfiguration WithSync) at a time when the radio link between the source cell and the UE is still stable. The handover execution is performed at a later (and threshold) time, considered optimal for handover execution. Petition 870250081883, dated 11 / 09 / 2025, page 45 / 236 / 183

[00103] Figure 13 illustrates an example with only one UE, one server cell, and one target cell. More specifically, in Figure 13, the gNB server can exchange user plane (UP) data with the UE. In step 1, the UE sends a measurement report with a “low” threshold to the gNB server. The gNB server makes a handover (HO) decision based on this initial report. In step 2, the gNB server sends an initial HO request to a gNB target. The gNB target accepts the HO request and creates an RRC configuration. The gNB target returns an HO confirmation, including the RRC configuration, to the gNB server in step 3. In step 4, a conditional HO command with a “high” threshold is sent to the UE. Subsequently, the UE measurements can meet the HO condition of the conditional HO command. The UE therefore triggers the pending conditional handover. The UE performs synchronization and random access with the target gNB in ​​step 5, and HO confirmation is exchanged in step 6.In step 7, the target gNB informs the server gNB that the HO has been completed. The target gNB can then exchange user plan (UP) data with the UE.

[00104] In practice, there may often be many cells or beams that the UE has reported as potential candidates based on its previous RRM measurements. The network should then have the freedom to issue conditional transfer commands for several of these candidates. The RRCConnectionReconfiguration / RRCReconfiguration message for each of these candidates may differ not only in relation to the target cell, but also, for example, in terms of the HO execution condition (RS to be measured and threshold to be exceeded), as well as in terms of the RA preamble to be sent when a condition is met.

[00105] While the UE evaluates the condition, it continues operating as its current RRC configuration, i.e., without applying the conditional HO command. When the UE determines that the condition has been met, it disconnects from the server cell, applies the conditional HO command, and then... Petition 870250081883, dated 11 / 09 / 2025, page 46 / 236 / 183 connects to the target cell. These steps are equivalent to executing the legacy handover.

[00106] When the UE successfully executes the random access procedure to the target cell during a conditional handover or a normal handover, it releases all stored conditional reconfigurations. The target cell can then configure new conditional reconfigurations for the UE, if it deems it useful. Conditional amendment of PSCell (CPC) in 3GPP Rel-16

[00107] Some embodiments in this document are applicable to a Conditional PSCell Change (CPC) procedure, for example, as standardized in Rel-16. In it, an UE operating in Multi-Radio Dual Connectivity (MR-DC) receives in a conditional reconfiguration one or more RRC Reconfigurations (e.g., an RRCReconfiguration message) containing an SCG configuration (e.g., a secondaryCellGroup of the IE CellGroupConfig) with a reconfigurationWithSync that is stored and associated with an execution condition (e.g., a condition such as an A3 / A5 event configuration), so that one of the stored messages is applied only after the execution condition is met, for example, associated with the server PSCell, in which the UE would execute the PSCell change (if it finds a neighboring cell that is better than the current SpCell of the SCG).Only intra-SN CPC without MN involvement is standardized in 3GPP Rel-16, that is, for cases where the target (candidate) PSCells are located in the current server SN.

[00108] Similar to conditional transfer, if a random access has been made to a target PSCell and the UE has been configured with CPC, the UE then releases all conditional reconfigurations that it has stored. CPA and inter-SN CPC in 3GPP Rel-17 Petition 870250081883, dated 11 / 09 / 2025, page 47 / 236 / 183

[00109] Some modalities described in this document are applicable to Conditional Addition of PSCell (CPA) and inter-SN CPC, for example, according to 3GPP Rel-17. The CPA procedure is used to add a PSCell / SCG to the configuration of a UE that is currently configured only with an MCG, when the associated execution conditions are met. The CPA is initiated by the MN requesting an SCG configuration, which must be provided as part of a conditional reconfiguration to the UE, from a target (candidate) SN (TSN), and then sending it in a conditional reconfiguration to the UE along with the associated execution conditions.

[00110] An inter-SN CPC can be initiated by the MN or the originating SN (S-SN), where signaling towards the originating SN and the SNsalvo (candidate) SNs, as well as towards the UE, in both cases, is controlled by the MN. One of the possible signaling sequences for setting up an inter-SN CPC, initiated by the originating SN, can be seen in the signaling flow in Figure 14.

[00111] Additionally, for the Conditional PSCell Change (CPC) / Conditional PSCell Addition (CPA) of Rel-17, the UE configured with CPC / CPA is expected to have to release the CPC / CPA settings upon completing random access to the target PSCell. Conditional (Re)configurations

[00112] In some modes, conditional configurations, or rather, reconfigurations, are configured for the UE as a configuration, for example, an RRC reconfiguration message, which should only be applied when the associated execution / trigger conditions are met.

[00113] The UE receives this conditional reconfiguration via an RRC reconfiguration message that includes the IEs for the conditional reconfiguration. In some modes, the IEs to configure the Petition 870250081883, dated 11 / 09 / 2025, page 48 / 236 / 183. Conditional reconfiguration is specified differently in TS 38.331 V17.3.0 (Rel-17A). Conditional reconfiguration is added or modified by including the corresponding CondReconfigToAddMod-r16 instance in condReconfigToAddModList-r16 within IE ConditionalReconfiguration. For each conditional reconfiguration, the configuration to be applied to the target cell when the execution conditions are met is included in condRRCReconfig-r16 (i.e., as an RRC Reconfiguration message, e.g., RRCReconfiguration) within CondReconfigToAddMod-r16. The associated execution conditions are included in condExecutionCondr16 or in condExecutionCondSCG-r17 in CondReconfigToAddMod-r16, depending on the type of conditional reconfiguration.

[00114] Conditional reconfiguration 20, shown in Figure 2 in this document, can be exemplified by an instance of CondReconfigToAddMod-r16 in condReconfigToAddModList-r16 within IE ConditionalReconfiguration. Conditional events

[00115] More specifically, each execution condition (as configured via condExecutionCond or condExecutionCondSCG) consists of one or two MeasId(s), where MeasId is associated with a measObjectId and a reportConfigId. The reportConfigId is then, in turn, associated with a report configuration (a ReportConfigToAddMod instance) that is configured as a conditional event, i.e., it includes a ReportConfigNR with a conditional event. This can be seen in TS 38.331 V17.3.0:

[00116] For some of the events defined to trigger a measurement report, there is therefore a corresponding conditional event defined, which must be used to determine whether an execution condition has been met, such as the conditional events A3, A4 and A5 (configured as condEventA3, condEventA4 and condEventA5, respectively). The events Petition 870250081883, dated 11 / 09 / 2025, p. 49 / 236 / 183, conditional events condEventA3, condEventA4, and condEventA5 are considered satisfied / fulfilled based on the same procedure used for normal events for A3, A4, and A5. Conditional event A3 is therefore satisfied / fulfilled when the candidate for conditional reconfiguration becomes a better offset value than the serving PCell / PSCell, conditional event A4 is satisfied / fulfilled when the candidate for conditional reconfiguration becomes better than an absolute limit, and conditional event A5 is satisfied / fulfilled when the serving PCell / PSCell becomes worse than an absolute limit AND the candidate for conditional reconfiguration becomes better than another absolute limit. NR-DC with selective activation of cell groups (at least for SCG) via L3 enhancements in 3GPP Rel-18

[00117] Some embodiments in this document are applicable to enhancements for different mobility procedures, for example, as specified in RP-213565, New WI: Further NR mobility enhancements, MediaTek, 3GPP TSG RAN Meeting No. 94e, December 6-17, 2021. Some embodiments in this regard facilitate NR-DC mechanisms and procedures with selective activation of cell groups (at least for SCG) via L3 enhancements, to allow subsequent cell group change after CG change without CPC / CPA reconfiguration and restart.

[00118] Some modes, therefore, allow a UE to perform a subsequent change in the cell group after a first change, without reconfiguring or resetting the Conditional PSCell Change (CPC) or Conditional PSCell Addition (CPA). This would be done to reduce the interruption time and signaling overhead for SCG changes, especially in the case of frequent SCG changes when operating in FR2 in NR, compared to releasing these settings when the UE completes random access to the target PSCell, as in previous versions. Petition 870250081883, dated 11 / 09 / 2025, p. 50 / 236 / 183

[00119] Some modes therefore allow the use of a conditional CPA configuration for CPC (but with different trigger conditions). A CPA configuration, or at least the condRRCReconfig (i.e., as an RRC reconfiguration message, e.g., RRCReconfiguration) within the CondReconfigToAddMod for the CPA configuration would then be used for CPC, but there would be different trigger / execution conditions for CPA and CPC.

[00120] Some features in this document in particular allow obtaining a Conditional PSCell Addition (CPA) configuration that can be used for Conditional PSCell Modification (CPC) with different trigger / execution conditions. A CPA configuration is configured as a CondReconfigToAddMod instance that includes a candidate target cell configuration (in condRRCReconfig) and an execution condition in condExecutionCond, where the execution condition is associated with the conditional event A4 (condEventA4).

[00121] Some approaches overcome a number of challenges to achieve this goal. One challenge is that the A4 event used for CPA only includes a check to see if the candidate target PSCell is good enough, that is, if it becomes better than an absolute threshold. This makes sense, since the UE is not configured with any server PSCell. A CPC configuration, which is used when the UE is already configured with a PSCell, should, however, compare the candidate target PSCell with the server PSCell, for example, so that a change in the PSCell is not triggered when the current server PSCell is still good and perhaps even better than the candidate target PSCell. The conditional A4 event, therefore, is not useful so far for CPC.This is especially true in the case of intrafrequency candidate target cells, where mobility to such a neighboring PSCell can lead to greater interference and worse performance if it is worse than the current serving PSCell or if the current serving PSCell is still in good coverage. Petition 870250081883, dated 11 / 09 / 2025, p. 51 / 236 / 183 For CPC, the execution conditions associated with conditional events A3 and A5 (condEventA3 and condEventA5) must therefore be used.

[00122] Another challenge is that the CPA is configured by the MN, including a target cell configuration (in condRRCReconfig) generated by the candidate target SN. It is then the MN that defines the execution condition for the CPA configuration to run (adding the PSCell). For the CPC, however, it can be either the MN or the SN that defines the execution condition. When the SN triggers the CPC configurations and defines the execution conditions for them, it controls the SCG mobility. Intra-SN CPC is configured only by the SN and therefore there is no MN involvement in configuration generation. Some modalities described in this document notably allow a CPA configuration to be used for CPC with a different trigger / execution condition, where only the MN can define the execution condition for CPC.

[00123] Some modes allow a UE to reuse the same conditional reconfiguration with a target PSCell candidate cell for CPA and for CPC, where the configuration is considered a CPA configuration when the UE is not configured with a server / SCG PSCell configuration and a CPC configuration when the UE is configured with a server / SCG PSCell configuration, and using different trigger / execution conditions for CPA and for CPC.

[00124] Alternatively, the UE conditional reconfiguration includes an execution condition that corresponds to event A5 (conditional event A5, i.e., CondEvent A5) and the UE is not configured with any server PSCell, i.e., the UE considers the conditional reconfiguration with a candidate target PSCell as corresponding to a CPA configuration. In other words, the UE does not consider aspects or measurements related to the SpCell (i.e., a server PSCell) when evaluating whether the conditions for the event are met. In other words, the UE does not consider aspects or measurements. Petition 870250081883, dated 11 / 09 / 2025, p. 52 / 236 / 183, relates to SpCell (i.e., a server PSCell) when evaluating whether the conditions for the event are met. Alternatively, a similar solution is used for the case where the conditional reconfiguration includes an execution condition that corresponds to event A3 (conditional event A3, i.e., CondEvent A3). In this case, the UE evaluates the condition for CPA using a separate setting of a threshold value, which is then used to check if the candidate target PSCell is good enough for the CPA setting to be applied and executed.

[00125] Some modalities also include methods in which new events, useful for both CPA and CPC, are introduced and in which the evaluation of conditions is done in a way that depends on whether it is done for CPC or CPA, that is, whether the UE is currently configured with a server PSCell / SCG or not.

[00126] Methods are also included where the configuration includes multiple reporting configurations for the same execution condition, and the UE uses the reporting configuration relevant to CPA in the case of assessment for CPA and the reporting configuration relevant to CPC in the case of assessment for CPC. In one option, the two measIDs that are part of the same execution condition are split into one for CPA (with conditional event A4) and one for CPC (with conditional event A3 or A5).

[00127] In some embodiments, the UE obtains an update of the other stored CPA configurations when applying a CPA configuration, so that the execution conditions of those CPA / CPC configurations are changed to be relevant to the CPC (e.g., conditional events A3 or A5). It is also included that the UE can obtain an update of the execution conditions for the CPA / CPC configurations that are stored when the PSCell / SCG is released, i.e., so that they are changed to be relevant to the CPA (e.g., conditional event A4). Petition 870250081883, dated 11 / 09 / 2025, p. 53 / 236 / 183

[00128] The modalities in this document also include corresponding methods for network configuration.

[00129] Some modes advantageously allow a UE to be configured with a single conditional reconfiguration, including alternatives with a single execution condition, which is useful for both CPA (when the UE is not configured with any server PSCell) and CPC (when the UE is configured with a server PSCell). Some modes allow the execution condition to take into account the intensity and / or quality of the radio only for the candidate target PSCell in the case of CPA and for both the server PSCell and the candidate target PSCell in the case of CPC.

[00130] Certain modes may provide one or more of the following technical advantages. Some modes allow a UE to be configured with a single conditional reconfiguration (including the UE being configured with a single execution condition) that can be used as both a CPA configuration and a CPC configuration, where the intensity and / or quality of the radio signal to the PSCell server is taken into account only when determining whether or not to trigger CPC execution.

[00131] Several modalities in this document will now be considered. Evaluation of event (conditional) A5 without considering the aspects of the SpCell server.

[00132] An alternative to having a conditional reconfiguration (CondReconfigToAddMod) with two separate trigger / execution conditions, depending on whether the configuration should be used for CPA or CPC, is to include two separate execution conditions, for example, the existing condExecutionCond and an additional conditional reconfiguration that is also defined by MN, in CondReconfigToAddMod, where one would be Petition 870250081883, dated 11 / 09 / 2025, page 54 / 236 / 183 used in the case of CPA and another in the case of CPC.

[00133] Other modalities, however, avoid the need for additional measurement configurations and measurement configuration identities (MeasIDs) for the same conditional reconfiguration. In fact, the different execution conditions would need to be configured with different measurement configuration identities to associate them with different conditional events, for example, CondEvent A4 for CPA and CondEvent A3 or A5 for CPC. These other modalities, then, avoid the need to configure multiple measurement configurations and the corresponding need for additional measurement configuration identities (MeasIDs) in order to achieve different trigger conditions for the conditional reconfiguration, depending on whether CPA or CPC is used.

[00134] These modes that exploit a single execution condition field 26 are exemplified in this document with Modes A3-A19 in GROUP A MODS IN THIS DOCUMENT, and with regard to Figures 3-6.

[00135] A first set of embodiments includes methods for a User Equipment (UE) to perform the evaluation of at least one conditional reconfiguration with a target candidate PSCell cell.

[00136] The method understands that the UE receives a message (e.g., RRCReconfiguration) including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a target SCG / candidate PSCell configuration). The conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional Add PSCell (CPA) configuration or a Conditional Change PSCell (CPC) configuration. For example, the conditional reconfiguration corresponds to a Conditional Add PSCell (CPA) configuration when the UE is not configured with a server / SCG PSCell configuration, but corresponds to a Change configuration. Petition 870250081883, dated 11 / 09 / 2025, page 55 / 236 / 183 of Conditional PSCell (CPC) when the UE is configured with a server / SCG PSCell configuration.

[00137] The method further includes the UE performing the execution condition assessment according to whether the conditional reconfiguration corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration, that is, whether the UE is configured with a server PSCell or not.

[00138] In some modes where the execution condition corresponds to / is associated with event A5 (conditional event A5, i.e., CondEvent A5) and the UE is not configured with any server PSCell, i.e., the method may understand that the UE considers the conditional reconfiguration with a candidate target PSCell to match a CPA configuration, where the UE considers the conditions for the event to be satisfied taking into account only aspects or measurements related to the neighboring cell (i.e., the candidate target PSCell of the conditional reconfiguration). In other words, the UE does not consider aspects or measurements related to the SpCell (i.e., a server PSCell) when evaluating whether the conditions for the event are met.

[00139] Alternatively, when checking whether the entry condition for the conditional event A5 (CondEvent A5) is met for a CPA configuration, i.e., a conditional reconfiguration with a candidate target PSCell configuration and the UE is not configured with a server PSCell, the UE only considers whether the measurement result of the candidate target PSCell is above the configured threshold (taking into account the hysteresis and offset parameter values, if any).

[00140] Below is an example implementation for TS 38.331, V17.3.0 (Rel-17), with the underlined additions: 5.5.4.6 Event A5 (SpCell becomes worse than the limit1 and a Petition 870250081883, dated 11 / 09 / 2025, p. 56 / 236 / 183 neighbor becomes better than the limit2)

[00141] The EU must: 1> If the event is a CondEvent A5 that is associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: 2> Consider that the entry condition for this event is satisfied when condition A5-2, as specified below, is met; 1> Otherwise, consider that the entry condition for this event will be satisfied when both conditions A5-1 and A5-2, as specified below, are met; 1> If the event is a CondEvent A5 that is associated with a Conditional PSCell Addition (CPA) configuration, i.e., where the UE is not configured with a server PSCell: 2> Consider that the exit condition for this event will be satisfied when condition A5-4, as specified below, is met; 1> Otherwise, consider that the exit condition for this event will be satisfied when condition A5-3 or condition A5-4, that is, at least one of the two, as specified below, is met; 1> Use SpCell for MP.

[00142] NOTE 1: The parameters of the reference signal(s) of the cell(s) that trigger(s) the event are indicated in the measObjectNR associated with the event, which may be different from the measObjectNR of the NR SpCell.

[00143] Inequality A5-1 (Input condition 1)

[00144] Mp + Hys < Threshl

[00145] Inequality A5-2 (Entry condition 2)

[00146] Mn + Ofn + Ocn - Hys > Thresh2

[00147] Inequality A5-3 (Exit condition 1)

[00148] Mp - Hys > Threshl

[00149] Inequality A5-4 (Exit condition 2) Petition 870250081883, dated 11 / 09 / 2025, page 57 / 236 / 183

[00150] Mn + Ofn + Ocn + Hys < Thresh2

[00151] The variables in the formula are defined as follows: Mp is the result of the SpCell measurement of NR, without taking into account any deviations.

[00152] Mn is the result of measuring the neighboring cell, without taking into account any displacements.

[00153] Ofn is the specific offset of the measurement object from the neighboring cell (i.e., offsetMO as defined in measObjectNR corresponding to the neighboring cell).

[00154] Ocn is the specific offset of the neighboring cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the neighboring cell) and is set to zero if it is not set for the neighboring cell.

[00155] Hys is the hysteresis parameter for this event (that is, hysteresis as defined in reportConfigNR for this event).

[00156] Thresh1 is the threshold parameter for this event (for example, a5-Threshold1 as defined in reportConfigNR for this event).

[00157] Thresh2 is the threshold parameter for this event (for example, a5-Threshold2 as defined in reportConfigNR for this event).

[00158] Mn, Mp are expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and RS-SINR.

[00159] Ofn, Ocn, Hys are expressed in dB.

[00160] Thresh1 is expressed in the same unit as Mp.

[00161] Thresh2 is expressed in the same unit as Mn.

[00162] NOTE 2: The definition of Event A5 also applies to CondEvent A5.

[00163] The method, in some modalities, also includes that Petition 870250081883, dated 11 / 09 / 2025, p. 58 / 236 / 183: The UE preserves the conditional reconfiguration with a candidate target PSCell after a PSCell addition procedure, where the same conditional configuration (including the same execution condition that corresponds to / is associated with the conditional event A5) is considered to correspond to a CPC configuration after the completion of the PSCell addition procedure. The UE then considers the conditions for the (conditional) event A5 to be satisfied, taking into account both aspects or measurements related to the neighboring cell (i.e., the candidate target PSCell of the conditional reconfiguration) and aspects or measurements related to the SpCell (i.e., the server PSCell) when considering whether the conditions for the event are satisfied. Evaluation of the (conditional) event A3 without considering the aspects of the SpCell server.

[00164] Alternatively, a method described herein understands that the execution condition corresponds to / is associated with event A3 (conditional event A3, i.e., CondEvent A3) and the UE is not configured with any server PSCell, i.e., the UE considers the conditional reconfiguration with a candidate target PSCell to match a CPA configuration. In this case, the UE considers the conditions for the event to be satisfied taking into account only aspects or measurements related to the neighboring cell (i.e., the candidate target PSCell of the conditional reconfiguration). In other words, the UE does not consider aspects or measurements related to the SpCell (i.e., a server PSCell) when evaluating whether the conditions for the event are met. Alternatively, the UE receives an additional configuration for the threshold (e.g., a cpa-threshold parameter) that the candidate target PSCell measurement must meet, similar to the a4-Threshold-r17 that is part of condEventA4-r17.This additional limit is received outside of the condEventA3 configuration, but is used as part of the procedure to evaluate whether the conditional event A3 is present. Petition 870250081883, dated 11 / 09 / 2025, page 59 / 236 / 183 fulfilled / satisfied.

[00165] In one example, the additional limit (e.g., cpathreshold) is included in CondReconfigToAddMod. In another example, it is included in CondTriggerConfig.

[00166] Below is an example implementation for TS 38.331, V17.3.0 (Rel-17), with the underlined additions: CondTriggerConfig-r16 ::= SEQUENCE { condEventId CHOICE { condEventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset, hysteresis Hysteresis, timeToTrigger TimeToTrigger}, condEventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, hysteresis Hysteresis, timeToTrigger TimeToTrigger}, ..., condEventA4-r17 SEQUENCE { a4-Threshold-r17 MeasTriggerQuantity, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger}, condEventD1-r17 SEQUENCE { distanceThreshFromReference1-r17 INTEGER (0.. 65525), distanceThreshFromReference2-r17 INTEGER (0.. Petition 870250081883, dated 11 / 09 / 2025, page 60 / 236 / 183 65525), referenceLocation1-r17 ReferenceLocation-r 17, referenceLocation2-r17 ReferenceLocation-r17, hysteresisLocation-r17 HysteresisLocation-r17, timeToTrigger-r17 TimeToTrigger}, condEventT1-r17 SEQUENCE { t1-Threshold-r17 INTEGER (0..549755813887), duration-r17 INTEGER (1..6000)}}, rsType-r16 NR-RS-Type, ..., cpa-Threshold-r18 MeasTriggerQuantity}

[00167] 5.5.4.4 Event A3 (The neighbor becomes more satisfactorily displaced than the SpCell)

[00168] The UE must: 1> If the event is a CondEvent A3 that is associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: 2> Consider that the entry condition for this event is satisfied when condition A3-3, as specified below, is met; 1> Otherwise, consider that the entry condition for this event will be satisfied when condition A3-1, as specified below, is met; 1> If the event is a CondEvent A3 that is associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: Petition 870250081883, dated 11 / 09 / 2025, p. 61 / 236 / 183 2> Consider that the exit condition for this event will be satisfied when condition A3-4, as specified below, is met; 1> Otherwise, consider that the exit condition for this event will be satisfied when condition A3-2, as specified below, is met; 1> use SpCell for Mp, Ofp and Ocp.

[00169] NOTE 1: The cell(s) that trigger(s) the event have reference signals indicated in the measObjectNR associated with this event, which may be different from the measObjectNR of the NR SpCell.

[00170] Inequality A3-1 (Entry condition)

[00171] Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

[00172] Inequality A3-2 (Exit condition)

[00173] Mn + Ofn + Ocn + Hys < Mp + Ofp + Ocp + Off

[00174] A3-3 Inequality (Entry Condition)

[00175] Mn + Ofn + Ocn - Hys > Cpa-thresh

[00176] Inequality A3-4 (Exit condition)

[00177] Mn + Ofn + Ocn + Hys < Cpa-thresh

[00178] The variables in the formula are defined as follows: Mn is the result of measuring the neighboring cell, without taking any displacements into account.

[00179] Ofn is the specific offset of the measurement object from the neighboring cell's reference signal (i.e., offsetMO as defined in measObjectNR corresponding to the neighboring cell).

[00180] Ocn is the specific offset of the neighboring cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the neighboring cell frequency) and is set to zero if it is not set for the neighboring cell.

[00181] Mp is the result of the SpCell measurement, without taking into account any displacements. Petition 870250081883, dated 11 / 09 / 2025, page 62 / 236 / 183

[00182] Ofp is the specific offset of the SpCell measurement object (i.e., offsetMO as defined in the SpCell-corresponding measObjectNR).

[00183] Ocp is the specific offset of the SpCell cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the SpCell) and is set to zero if not configured for the SpCell.

[00184] Hys is the hysteresis parameter for this event (that is, hysteresis as defined in reportConfigNR for this event).

[00185] Off is the offset parameter for this event (e.g., a3-Offset as defined in reportConfigNR for this event).

[00186] Cpa-threshold is the threshold parameter for this event if it is a CondEvent A3 associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell (i.e., as defined by cpa-Threshold within CondTriggerConfig).

[00187] Mn, Mp are expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and RS-SINR.

[00188] Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

[00189] Cpa-thresh is expressed in the same unit as Mn.

[00190] NOTE 2: The definition of Event A3 also applies to CondEvent A3. PAGE 33 OF THE PDF

[00191] Alternatively, the UE preserves the conditional reconfiguration with a candidate target PSCell after a PSCell add-on procedure, where the same conditional configuration (including the same execution condition that corresponds to conditional event A3) is considered to correspond to a CPC configuration after the PSCell add-on procedure is completed. The UE then considers the conditions for event (conditional) A3 to be satisfied, taking into account both Petition 870250081883, dated 11 / 09 / 2025, p. 63 / 236 / 183, regarding aspects or measurements related to the neighboring cell (i.e., the candidate target PSCell of the conditional reconfiguration) as well as aspects or measurements related to the SpCell (i.e., the serving PSCell) when considering whether the conditions for the event are met.

[00192] A set of modalities includes a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate PSCell cell. According to this method, the network node sends a message (e.g., RRCReconfiguration) to the UE, including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a SCG / target candidate PSCell configuration). In this document, the conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional Addition PSCell (CPA) configuration or a Conditional Change PSCell (CPC) configuration.

[00193] In some modes, the execution condition is associated with an A3 conditional event. In some modes, the message includes a new setting for the threshold that the candidate target PSCell measurement must reach for the A3 conditional event to be met / satisfied, for example, a cpa-threshold parameter. In one example, the new threshold parameter (e.g., cpa-threshold) is included in CondReconfigToAddMod. In another example, it is included in CondTriggerConfig.

[00194] In one example, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell. Petition 870250081883, dated 11 / 09 / 2025, p. 64 / 236 / 183 The evaluated event will change if SpCell (PSCell server) is not configured.

[00195] The methods described in this document also include a method for a User Equipment (UE) to perform the evaluation of at least one conditional reconfiguration with a target PSCell candidate cell. According to this method, the UE receives a message (e.g., RRCReconfiguration) including a conditional reconfiguration with a target PSCell candidate cell (with an execution condition and a PSCell target SCG / candidate configuration). The conditional reconfiguration with a target PSCell candidate cell corresponds to a PSCell Conditional Addition (CPA) configuration or a PSCell Conditional Change (CPC) configuration. The conditional reconfiguration corresponds to a PSCell Conditional Addition (CPA) configuration when the UE is not configured with a server / SCG PSCell configuration.Conditional reconfiguration corresponds to a Conditional PSCell Change (CPC) configuration when the UE is configured with a server / SCG PSCell configuration.

[00196] According to the method, the UE determines the event to be evaluated for the execution condition depending on whether the conditional reconfiguration corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration, that is, whether the UE is configured with a server PSCell or not.

[00197] In some modes, the execution conditions are configured to match event A5 (conditional event A5, i.e., CondEvent A5) or event A3 (conditional event A3, i.e., CondEvent A3), and the UE is not configured with any server PSCell; that is, the UE considers conditional reconfiguration with a candidate PSCell to match a CPA configuration. In one of these modes, the UE Petition 870250081883, dated 11 / 09 / 2025, page 65 / 236 / 183 evaluates event A4 (conditional event A4, i.e., CondEvent A4) instead of event A5 (conditional event A5, i.e., CondEvent A5) or event A3 (conditional event A3, i.e., CondEvent A3) for execution conditions. In other words, UE changes the evaluated event when it is configured with a CPA configuration, i.e., a conditional reconfiguration with a candidate target PSCell and there is no current SpCell (i.e., a server PSCell) configured.

[00198] In one example, the UE determines to evaluate according to conditional event A4, although the configuration consists of a conditional event A5 (condEventA5), based on the fact that the associated conditional reconfiguration is for CPA, that is, the configuration is for a candidate PSCell target and the UE is not configured with any server / SCG PSCell configuration.

[00199] Below is an example implementation for TS 38.331, V17.3.0 (Rel-17), with the underlined additions: 5.5.4.5 Event A4 (Neighbor becomes better than the boundary) The EU should: 1> Consider that the entry condition for this event is satisfied when condition A4-1, as specified below, is met; 1> Consider that the exit condition for this event will be satisfied when condition A4-2, as specified below, is met.

[00200] Inequality A4-1 (Entry Condition)

[00201] Mn + Ofn + Ocn - Hys > Thresh

[00202] Inequality A4-2 (Exit Condition)

[00203] Mn + Ofn + Ocn + Hys < Thresh

[00204] The variables in the formula are defined as follows: Mn is the result of measuring the neighboring cell, without taking any displacements into account.

[00205] Ofn is the specific displacement of the object being measured from Petition 870250081883, dated 11 / 09 / 2025, page 66 / 236 / 183 neighboring cell (i.e., offsetMO as defined in measObjectNR corresponding to the neighboring cell).

[00206] Ocn is the specific offset of the neighboring cell's measurement object (i.e., cellIndividualOffset as defined in measObjectNR corresponding to the neighboring cell) and is set to zero if it is not set for the neighboring cell.

[00207] Hys is the hysteresis parameter for this event (i.e., hysteresis as defined in reportConfigNR for this event or as hysteresis defined in condEventA5 in reportConfigNR, if the UE is configured with CondEvent A5 for a conditional reconfiguration with a candidate target PSCell that is associated with a Conditional PSCell Addition (CPA) configuration, i.e., where the UE is not configured with a server PSCell).

[00208] Thresh is the threshold parameter for this event (i.e., a4Threshold as defined in reportConfigNR for this event or as a5-Threshold2 defined in condEventA5 in reportConfigNR, if the UE is configured with CondEvent A5 for a conditional reconfiguration with a candidate target PSCell that is associated with a Conditional PSCell Addition (CPA) configuration, i.e., where the UE is not configured with a server PSCell).

[00209] Mn is expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and RS-SINR.

[00210] Ofn, Ocn, Hys are expressed in dB.

[00211] Thresh is expressed in the same unit as Mn.

[00212] NOTE 1: The definition of Event A4 also applies to CondEvent A4.

[00213] NOTE 2: The definition of Event A4 also applies to CondEvent A5, if the UE is configured with CondEvent A5 for a conditional reconfiguration with a candidate target PSCell that is Petition 870250081883, dated 11 / 09 / 2025, p. 67 / 236 / 183 associated with a Conditional PSCell Addition (CPA) configuration, i.e., where UE is not configured with a server PSCell. Introduction of new conditional events for CPA and CPC.

[00214] The modalities described in this document also include a method for a User Equipment (UE) to perform the evaluation of at least one conditional reconfiguration with a target candidate PSCell cell. According to this method, the UE receives a message (e.g., RRCReconfiguration) including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a PSCell target candidate / SCG configuration). The conditional reconfiguration with a target candidate PSCell cell corresponds to a PSCell Conditional Addition (CPA) configuration or a PSCell Conditional Change (CPC) configuration.For example, conditional reconfiguration corresponds to a Conditional Addition of PSCell (CPA) configuration when the UE is not configured with a server / SCG PSCell configuration, and conditional reconfiguration corresponds to a Conditional Change of PSCell (CPC) configuration when the UE is configured with a server / SCG PSCell configuration.

[00215] According to the method, the UE performs the execution condition evaluation according to whether the conditional reconfiguration corresponds to a Conditional PSCell Change (CPC) configuration or a Conditional PSCell Addition (CPA) configuration, that is, whether the UE is configured with a server PSCell or not.

[00216] In some embodiments, the method understands that the execution condition corresponds to / is associated with at least one new event specific to CPA / CPC, that is, that it can be used for CPA or CPC depending on whether the UE is configured with a server PSCell or not when evaluating the execution condition.

[00217] In one example, there is a new event that corresponds to Petition 870250081883, dated 11 / 09 / 2025, page 68 / 236 / 183 conditional event A3 for CPC, in this document referred to, for example, as conditional event A3-CPAC (i.e., CondEvent A3-CPAC). The conditional reconfiguration then includes the new event CondEvent A3-CPAC:

[00218] If the UE is configured with at least one server PSCell (SpCell for SCG), the UE considers the conditional reconfiguration with a candidate target PSCell to match a CPC configuration. In this case, the UE considers the conditions for the new event to be satisfied taking into account both the measurement result of the SpCell (i.e., a server PSCell) and the neighboring cells.

[00219] If the UE is not configured with any server PSCell (SpCell for SCG), the UE considers conditional reconfiguration with a candidate target PSCell to match a CPA configuration. In this case, the UE cannot take into account aspects or measurements related to the SpCell (i.e., a server PSCell) when considering whether the conditions for the new event are met, since there is no PSCell (SpCell for SCG). The UE then considers the conditions for the new event to be met, considering only aspects or measurements related to neighboring cells (i.e., the candidate target PSCell of the conditional reconfiguration), comparing it to a threshold received in the event configuration.

[00220] In one example, there is a new event that corresponds to the conditional event A5 for CPC, in this document called, for example, conditional event A5-CPAC (i.e., CondEvent A5-CPAC). The conditional reconfiguration then includes the new event CondEvent A5-CPAC:

[00221] If the UE is configured with one or more PSCell / SpCell server(s), the UE considers the conditional reconfiguration with a candidate target PSCell to match a CPC configuration. In this case, the UE considers the conditions for the new event to be satisfied taking into account both the result of the SpCell measurement Petition 870250081883, dated 11 / 09 / 2025, p. 69 / 236 / 183 (i.e., a PSCell server) as well as the neighboring cell, when comparing with the relevant boundaries.

[00222] If the UE is not configured with any server PSCell, the UE will consider conditional reconfiguration with a candidate target PSCell to match a CPA configuration. In this case, the UE considers that the conditions for the new event to be met take into account only aspects or measurements related to the neighboring cell (i.e., the candidate target PSCell of the conditional reconfiguration), comparing it to a threshold received in the event configuration. In other words, the UE does not consider aspects or measurements related to the SpCell (i.e., a server PSCell) when evaluating whether the conditions for the new event are met.

[00223] Below is an example of the implementation of ASN 1 and two new sections for procedure text for TS 38.331, V17.3.0 (Rel-17). The additions are underlined and the highlights in the procedures indicate the main changes compared to the existing corresponding procedures: CondTriggerConfig-r16 ::= SEQUENCE { condEventId CHOICE { condEventA3 SEQUENCE { a3-Offset MeasTriggerQuantityOffset, hysteresis Hysteresis, timeToTrigger TimeToTrigger}, condEventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, hysteresis Hysteresis, timeToTrigger TimeToTrigger}, Petition 870250081883, dated 11 / 09 / 2025, page. 70 / 236 / 183 condEventA4-r17 SEQUENCE { a4-Threshold-r17 MeasureTriggerQuantity, hysteresis-r17 Hysteresis, timeToTrigger-r17 TimeToTrigger}, condEventD1-r17 SEQUENCE { distanceThreshFromReference1-r17 INTEGER (0.. 65525), distanceThreshFromReference2-r17 INTEGER (0.. 65525), referenceLocation1-r17 ReferenceLocation-r17, referenceLocation2-r17 ReferenceLocation-r17, hysteresisLocation-r17 HysteresisLocation-r17, timeToTrigger-r17 TimeToTrigger}, condEventT1-r17 SEQUENCE { t1-Threshold-r17 INTEGER (0..549755813887), duration-r17 INTEGER (1..6000)}, condEventA3-CPAC-r18 SEQUENCE { a3-Offset-r18 MeasTriggerQuantityOffset, hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger a3-Threshold-CPA-r18 MeasTriggerQuantity,} condEventA5-CPAC-r18 SEQUENCE { a5-Threshold1-r18 MeasTriggerQuantity, a5-Threshold2-r18 MeasTriggerQuantity, Petition 870250081883, of 09 / 11 / 2025, p. 71 / 236 / 183 hysteresis-r18 Hysteresis, timeToTrigger-r18 TimeToTrigger}}, rsType-r16 NR-RS-Type, ... }

[00224] 5.5.4.x Event A3-CPAC (Neighbor becomes better offset than SpCell (for CPC) or better than a boundary (for CPA))

[00225] The UE must: 1> Consider that the entry condition for this event is satisfied when condition A3-CPAC-1, as specified below, is met; 1> Consider that the exit condition for this event will be satisfied when condition A3-CPAC-2, as specified below, is met; 1> use SpCell for Mp, Ofp and Ocp.

[00226] NOTE 1: The cell(s) that trigger(s) the event have reference signals indicated in the measObjectNR associated with this event, which may be different from the measObjectNR of the NR SpCell.

[00227] A3-CPAC-1 Inequality (Entry Condition)

[00228] If the event is a CondEvent A3-CPAC associated with a Conditional PSCell Change (CPC) configuration: Mn + Ofn + Ocn - Hys > Mp + Ofp + Ocp + Off

[00229] Otherwise, if the event is a CondEvent A3-CPAC associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: Mn + Ofn + Ocn - Hys > Thresh-CPA

[00230] A3-CPAC-2 Inequality (Exit Condition) Petition 870250081883, dated 11 / 09 / 2025, p. 72 / 236 / 183

[00231] If the event is a CondEvent A3-CPAC associated with a Conditional PSCell Change (CPC) configuration: Mn + Ofn + Ocn - Hys < Mp + Ofp + Ocp + Off

[00232] Otherwise, if the event is a CondEvent A3-CPAC associated with a Conditional PSCell Addition (CPA) configuration, i.e., where the UE is not configured with a server PSCell: Mn + Ofn + Ocn - Hys < Thresh-CPA

[00233] The variables in the formula are defined as follows: Mn is the result of measuring the neighboring cell, without taking any displacements into account.

[00234] Ofn is the specific offset of the measurement object from the neighboring cell's reference signal (i.e., offsetMO as defined in measObjectNR corresponding to the neighboring cell).

[00235] Ocn is the specific offset of the neighboring cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the neighboring cell frequency) and is set to zero if it is not set for the neighboring cell.

[00236] Mp is the result of the SpCell measurement, without taking into account any displacements.

[00237] Ofp is the specific offset of the SpCell measurement object (i.e., offsetMO as defined in the SpCell-corresponding measObjectNR).

[00238] Ocp is the specific offset of the SpCell cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the SpCell) and is set to zero if not configured for the SpCell.

[00239] Hys is the hysteresis parameter for this event (that is, hysteresis as defined in reportConfigNR for this event).

[00240] Off is the offset parameter for this event (e.g., a3-Offset as defined in reportConfigNR for this event). Petition 870250081883, dated 11 / 09 / 2025, page 73 / 236 / 183

[00241] Thresh-CPA is the threshold parameter for this event (for example, a3-Threshold-CPA as defined in reportConfigNR for this event).

[00242] Mn, Mp are expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and RS-SINR.

[00243] Ofn, Ocn, Ofp, Ocp, Hys, Off are expressed in dB.

[00244] 5.5.4.Y Event A5-CPAC (CPC: SpCell becomes worse than boundary 1 and neighbor becomes better than boundary 2; CPA: neighbor becomes better than boundary 2)

[00245] The EU must: 1> If the event is a CondEvent A5-CPAC that is associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: 2> Consider that the entry condition for this event is satisfied when condition A5-CPAC-2, as specified below, is met; 1> Otherwise, consider that the entry condition for this event will be satisfied when both conditions A5-CPAC-1 and A5CPAC-2, as specified below, are met; 1> If the event is a CondEvent A5-CPAC that is associated with a Conditional PSCell Addition (CPA) configuration, that is, where the UE is not configured with a server PSCell: 2> Consider that the exit condition for this event will be satisfied when condition A5-CPAC-4, as specified below, is met; 1> Consider that the exit condition for this event will be satisfied when condition A5-CPAC-3 or condition A5-CPAC-4, that is, at least one of the two, as specified below, is met; 1> Use SpCell for MP. Petition 870250081883, dated 11 / 09 / 2025, p. 74 / 236 / 183

[00246] NOTE 1: The parameters of the reference signal(s) of the cell(s) that trigger(s) the event are indicated in the measObjectNR associated with the event, which may be different from the measObjectNR of the NR SpCell.

[00247] Inequality A5-CPAC-1 (Entry condition 1)

[00248] Mp + Hys < Threshl

[00249] Inequality A5-CPAC-2 (Entry condition 2)

[00250] Mn + Ofn + Ocn - Hys > Thresh2

[00251] Inequality A5-CPAC-3 (Exit Condition 1)

[00252] Mp - Hys > Threshl

[00253] Inequality A5-CPAC-4 (Exit Condition 2)

[00254] Mn + Ofn + Ocn + Hys < Thresh2

[00255] The variables in the formula are defined as follows: Mp is the result of the SpCell measurement of NR, without taking into account any deviations.

[00256] Mn is the result of measuring the neighboring cell, without taking into account any displacements.

[00257] Ofn is the specific offset of the measurement object from the neighboring cell (i.e., offsetMO as defined in measObjectNR corresponding to the neighboring cell).

[00258] Ocn is the specific offset of the neighboring cell (that is, cellIndividualOffset as defined in measObjectNR corresponding to the neighboring cell) and is set to zero if it is not set for the neighboring cell.

[00259] Hys is the hysteresis parameter for this event (that is, hysteresis as defined in reportConfigNR for this event).

[00260] Threshold is the threshold parameter for this event (for example, a5-Threshold1 as defined in reportConfigNR for this event).

[00261] Thresh2 is the threshold parameter for this event (by Petition 870250081883, dated 11 / 09 / 2025, page 75 / 236 / 183 example, a5-Threshold2 as defined in reportConfigNR for this event).

[00262] Mn, Mp are expressed in dBm in the case of RSRP, or in dB in the case of RSRQ and RS-SINR.

[00263] Ofn, Ocn, Hys are expressed in dB.

[00264] Thresh1 is expressed in the same unit as Mp.

[00265] Thresh2 is expressed in the same unit as Mn.

[00266] Other embodiments in this document include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate PSCell cell. According to the method, the network node sends a message (e.g., RRCReconfiguration) to the UE, including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a SCG / target candidate PSCell configuration). The conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional Addition PSCell (CPA) configuration or a Conditional Change PSCell (CPC) configuration.For example, the execution condition is associated with a new conditional event, for example, CondEvent A3-CPAC or CondEvent A5-CPAC, used for CPA evaluation (considering only the neighboring / candidate target cell) or CPC evaluation (considering both the neighboring / candidate target cell and the current server cell).

[00267] In one example, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell, and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell. Petition 870250081883, dated 11 / 09 / 2025, page 76 / 236 / 183

[00268] In one example, it is a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE that generates (or provides input to) the configuration for the new conditional event.

[00269] Multiple report configurations for the same execution condition

[00270] In a set of modalities, the UE is configured with an execution condition (e.g., MeasId) that points to a measurement configuration (e.g., to the IE MeasIdToAddMod) that is associated with a first and a second report configuration (e.g., a first IE ReportConfigNR, a second instance of the IE ReportConfigNR), where the first report configuration includes parameters for an A3 event (e.g., conditional event A3, i.e., CondEvent A3) or an A5 event (e.g., conditional event A5, i.e., CondEvent A5) and the second report configuration includes parameters for an A4 event (e.g., conditional event A4, i.e., CondEvent A4). Then, depending on whether the UE is evaluating the condition for CPA or CPC, the UE selects the first or second report configuration.

[00271] In one mode, the UE receives an instance of IE MeasIdToAddMod (or another equivalent IE) that includes a measId (the same value that is configured in the execution condition for CPA or CPC) and the two reporting configurations, the first and the second, in the form of a first reporting configuration Id and a second reporting configuration Id. In some types, when the UE needs to evaluate the condition for CPC (for example, when the UE is configured with a server PSCell and / or when the UE is configured with an SCG), the UE uses the reporting configuration for the A3 / A5 events. In other modes, when the UE needs to evaluate the condition for CPA (for example, when the UE is NOT configured with a server PSCell and / or when the UE is NOT configured with an SCG), the UE uses the reporting configuration for the Petition 870250081883, dated 11 / 09 / 2025, page 77 / 236 / 183 event A4.

[00272] In one option, the report configuration(s) in this case are of a type associated with a conditional reconfiguration, CPC or CPA, for example, IE ReportConfigNR (or instance reportConfig in the UE variable VarMeasConfig) has a reportType defined as 'condTriggerConfig'.

[00273] In an alternative embodiment, the UE receives an instance of IE MeasIdToAddMod (or another equivalent IE) that includes a measId (the same value that is configured in the execution condition for the CPA / CPC configuration) and a measurement report configuration identity (reportConfigld), where the reportConfigld is included in a report configuration (a ReportConfigToAddMod instance) that includes two different report configurations, a first and a second, for example, in the form of two separate ReportConfigNR instances:

[00274] When the UE needs to evaluate the trigger / execution condition for CPC (for example, when the UE is configured with a server PSCell and / or when the UE is configured with an SCG), the UE uses the reporting configuration for event A3 (for example, conditional event A3, i.e., CondEvent A3) or event A5 (for example, conditional event A5, i.e., CondEvent A5).

[00275] When the UE needs to evaluate the condition for CPA (for example, when the UE is NOT configured with a server PSCell and / or when the UE is NOT configured with an SCG), the UE uses the reporting configuration for event A4 (for example, conditional event A4, i.e., CondEvent A4).

[00276] In one option, the report configuration(s) in this case are of a type associated with a conditional reconfiguration, CPC or CPA, for example, IE ReportConfigNR (or instance reportConfig in the UE variable VarMeasConfig) has a reportType defined as 'condTriggerConfig'.

[00277] In one option, ReportConfigToAddMod includes indication Petition 870250081883, dated 11 / 09 / 2025, page 78 / 236 / 183 regarding which reporting configuration should be used by the EU in assessing the triggering / execution conditions for CPA and CPC, respectively.

[00278] This solution means that the same identities for measurement configuration (MeasId) and for report configuration (ReportConfigId) can be used for CPA / CPC configuration, even if different trigger / execution conditions are used for CPA and CPC.

[00279] Below is an example implementation for TS 38.331, V17.3.0 (Rel-17), with the underlined additions: -- ASN1START -- TAG-REPORTCONFIGTOADDMODLIST-START ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod ReportConfigToAddMod ::= SEQUENCE { reportConfigId ReportConfigId, reportConfig CHOICE { reportConfigNR ReportConfigNR, ..., reportConfigInterRAT ReportConfigInterRAT, reportConfigNR-SL-r16 ReportConfigNR-SL-r16, reportConfigNR-CPAC-r18 SEQUENCE (SIZE (1..2)) DE ReportConfigNR}} -- TAG-REPORTCONFIGTOADDMODLIST-STOP -- ASN1STOP

[00280] 5.3.5.13.4 Conditional Reconfiguration Assessment

[00281] The EU must: 1> For each condReconfigld in VarConditionalReconfig: Petition 870250081883, dated 11 / 09 / 2025, page 79 / 236 / 183 2> If the RRCReconfiguration in the RRCReconfig includes the masterCellGroup, including reconfigurationWithSync: 3> Consider the cell that has a physical cell identity corresponding to the value indicated in ServingCellConfigCommon included in reconfigurationWithSync within the masterCellGroup in condRRCReconfig received as the applicable cell; 2> Otherwise, if the RRCReconfiguration within condRRCReconfig includes the secondaryCellGroup, including the reconfiguration WithSync: 3> Consider the cell that has a physical cell identity corresponding to the value indicated in ServingCellConfigCommon included in the WithSync reconfiguration within the secondaryCellGroup within the condRRCReconfig received as the applicable cell; 3> If the UE is currently configured with an SpCell for the SCG (i.e., a PSCell): 4> In the remainder of the procedure, consider conditional reconfiguration with condReconfigId to match a CPC configuration; 4> In the remainder of the procedure, consider configuring reports with a condEventId associated with condEventA3 or condEventA5; 3> Otherwise, (the UE is not currently configured with any SpCell for the SCG, i.e., PSCell): 4> In the remainder of the procedure, consider conditional reconfiguration with condReconfigId to match a CPA configuration; 4> In the remainder of the procedure, consider configuring reports with a condEventId associated with condEventA4; 2> if condExecutionCondSCG is configured: 3> In the remainder of the procedure, consider each measId Petition 870250081883, dated 11 / 09 / 2025, p. 80 / 236 / 183 indicated in condExecutionCondSCG as a measId in VarMeasConfig associated with SCG's measConfig; 2> If condExecutionCond is configured: 3> if configured by SRB3 or configured in nr-SCG or in nr-SecondaryCellGroupConfig (specified in TS 36.331

[10] ) by SRB1: 4> In the remainder of the procedure, consider each measId indicated in condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> otherwise: 4> In the remainder of the procedure, consider each measId indicated in condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 2> For each measId included in the measIdList within VarMeasConfig, as indicated in condExecutionCond or condExecutionCondSCG, associated with condReconfigId: 3> if the condEventId is associated with condEventT1, and if the applicable entry condition for this event associated with the condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within the VarConditionalReconfig, is met for the applicable cell; or 3> if condEventId is associated with condEventD1, and if the applicable entry conditions for this event associated with condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, are met for the applicable cell during the corresponding timeToTrigger defined for this event within VarConditionalReconfig; or 3> if condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the applicable entry condition(s) Petition 870250081883, dated 11 / 09 / 2025, p. 81 / 236 / 183 for this event associated with condReconfigld, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is fulfilled for the applicable cells for all measurements after layer 3 filtering performed during the corresponding timeToTrigger defined for this event within VarConditionalReconfig: 4> Consider the event associated with that measId as completed; 3> if the measId for this event associated with condReconfigld has been modified; or 3> if the condEventId is associated with the condEventTl, and if the applicable exit condition for this event associated with the condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within the VarConditionalReconfig, is met for the applicable cell; or 3> if condEventId is associated with condEventDl, and if the applicable exit condition(s) for this event associated with condReconfigId, that is, the event corresponding to condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is met for the applicable cell during the corresponding timeToTrigger defined for this event within VarConditionalReconfig; or 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the applicable input condition(s) for this event associated with condReconfigId, i.e., the event corresponding to the corresponding condEventId(s) of condTriggerConfig within VarConditionalReconfig, is met for applicable cells for all measurements after layer 3 filtering performed during the corresponding timeToTrigger defined for this event within VarConditionalReconfig: 4> Consider the event associated with that measId as not fulfilled; Petition 870250081883, dated 11 / 09 / 2025, p. 82 / 236 / 183 2> If the event(s) associated with all measId(s) within the condTriggerConfig for a target candidate cell within the stored condRRCReconfig is / are met: 3> Consider the target candidate cell within the stored condRRCReconfig, associated with that condReconfigId, as a triggered cell; 3> Start executing the conditional reconfiguration, as specified in 5.3.5.13.5; NOTE 1: Up to 2 MeasId can be configured for each condReconfigId. The conditional reconfiguration event of the 2 MeasId can have the same or different event conditions, number of triggers, trigger time and trigger limit

[00282] NOTE 2: Empty.

[00283] Other embodiments in this document include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate PSCell cell. According to the method, the network node sends a message (e.g., RRCReconfiguration) to the UE, including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a SCG / target candidate PSCell configuration). In this document, the conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration.

[00284] In some modes, the execution condition is associated with two separate conditional events, for example, one conditional event A4 and the other is conditional event A3 or A5. In one example, the two conditional events associated with the execution condition are provided as two measurement report settings (for example, Petition 870250081883, dated 11 / 09 / 2025, page 83 / 236 / 183 ReportConfigNR) within ReportConfigToAddMod. In another example, the two conditional events associated with the execution condition are provided as two measurement report configurations within MeasIdToAddMod. In some modalities, only one of the two separate conditional events associated with the execution condition is used by the UE, depending on whether the assessment is for CPA or CPC.

[00285] In one example, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell, and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell.

[00286] In one example, it is a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE that generates (or provides input to) the configuration for at least one of the measurement reporting configurations (or measurement configurations).

[00287] In a set of modalities, the UE is configured with an execution condition (e.g., MeasId) that points to a measurement identifier value (measId=X) in the measurement configuration (e.g., for IE MeasIdToAddMod). The UE receives two different configurations with the same measurement identifier in a measurement configuration; for example, the UE receives two instances of IE MeasIdToAddMod, where both instances have the same measurement identifier (e.g., MeasId=X), but one instance is pointing to a first reporting configuration (e.g., for CPC, configuring a Conditional Event A3 or A5), and the other instance is pointing to a second reporting configuration (e.g., for CPA, configuring a Conditional Event A4). Then, depending on whether the UE is evaluating the execution condition for CPA or for CPC, the UE selects the first or the second. Petition 870250081883, dated 11 / 09 / 2025, page 84 / 236 / 183 measurement configuration, for the same measId. The selection of the measurement configuration is then made based on whether the execution condition is evaluated for CPA or CPC, where the measurement configuration that is associated with (pointing to) a reporting configuration with a Conditional Event A3 or A5 is used if the evaluation is for CPC, and the measurement configuration that is associated with (pointing to) a reporting configuration with a Conditional Event A4 is used if the evaluation is for CPA.

[00288] In one option, the report configuration(s) in this case is / are of a type associated with a conditional reconfiguration, CPC or CPA, for example, IE ReportConfigNR (or instance reportConfig in the UE variable VarMeasConfig) has a reportType defined as 'condTriggerConfig'.

[00289] In one option, the reporting configuration (for example, within ReportConfigToAddMod) or the measurement configuration includes an indication of whether it should be used for CPA or CPC. In this case, the UE uses the indication to determine which reporting configuration and associated measurement configuration to use in evaluating the CPA or CPC configuration, respectively.

[00290] In an alternative embodiment, the UE is configured with an execution condition (e.g., MeasId) that points to a measurement identifier value in the measurement configuration (e.g., for IE MeasIdToAddMod), which then includes, for example, an identity of a measurement report configuration (reportConfigId) that is associated with the measurement configuration, and the UE receives two different measurement report configurations (ReportConfigToAddMod) with the same identity (reportConfigId). For example, the UE is configured with two separate instances of IE ReportConfigToAddMod, where both instances have the same identifier (e.g., reportConfigId=X), but one instance includes a report configuration for CPC, e.g., configuring a Conditional Event A3 or A5, and the other instance includes a Petition 870250081883, dated 11 / 09 / 2025, page 85 / 236 / 183 report configuration for CPA, for example, by configuring an A4 Conditional Event. Then, depending on whether the UE is evaluating the execution condition for CPA or for CPC, the UE selects the first or second measurement report configuration for the same reportConfigId. The selection of the measurement report configuration (e.g., instance ReportConfigToAddMod with the indicated reportConfigId, for example, with reportConfigId=X) is made based on the execution condition evaluated for CPA or for CPC, where the report configuration with an A3 or A5 Conditional Event is used if the evaluation is for CPC, and the report configuration with an A4 Conditional Event is used if the evaluation is for CPA.

[00291] In one option, the report configuration(s) in this case is(are) of a type associated with a conditional reconfiguration, CPC or CPA, for example, IE ReportConfigNR (or instance reportConfig in the UE variable VarMeasConfig) has a reportType defined as 'condTriggerConfig'.

[00292] In one option, the reporting configuration (for example, within ReportConfigToAddMod) or the measurement configuration includes an indication of whether it should be used for CPA or CPC. In this case, the UE uses the indication to determine which reporting configuration and associated measurement configuration to use in evaluating the CPA or CPC configuration, respectively.

[00293] Other embodiments include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate PSCell cell. According to the method, the network node sends a message (e.g., RRCReconfiguration) to the UE, including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition and a SCG / target candidate PSCell configuration). Petition 870250081883, dated 11 / 09 / 2025, p. 86 / 236 / 183

[00294] Conditional reconfiguration with a target candidate PSCell cell corresponds to a PSCell Conditional Addition (CPA) configuration or a PSCell Conditional Change (CPC) configuration.

[00295] The execution condition includes at least one measurement configuration identity (measId) that is included in two separate MeasIdToAddMods, i.e., the network node configures two separate MeasIdToAddMods with the same measId value. In one example, one of the MeasIdToAddMod instances includes / is associated with the measurement reporting configuration with a conditional event for CPA, for example, conditional event A4 (CondEvent A4), and the other MeasIdToAddMod instance includes / is associated with the measurement reporting configuration with a conditional event for CPC, for example, conditional event A3 (CondEvent A3) or A5 (CondEvent A5). In some modes, only one of the measurement configurations with the indicated measId is used by the UE at a time, where the configuration to be used depends on whether the evaluation of the execution condition, i.e., the conditional reconfiguration, is for CPA or for CPC.

[00296] In one example, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell.

[00297] Alternatively, the network configures two measurement reporting configurations (for example, two ReportConfigToAddMod instances) with the same reportConfigld. A measurement configuration with a measId included in the execution condition includes a reportConfigld included in two different ReportConfigToAddMod instances. In one example, one of the ReportConfigToAddMod instances includes / is associated with an event. Petition 870250081883, dated 11 / 09 / 2025, p. 87 / 236 / 183 conditional for CPA, for example, conditional event A4 (CondEvent A4) and the other instance ReportConfigToAddMod includes / is associated with a conditional event for CPC, for example, conditional event A3 (CondEvent A3) or A5 (CondEvent A5).

[00298] In some modes, only one of the measurement report configurations with the indicated reportConfigld is used by the UE at a time, where the configuration to be used depends on whether the evaluation of the execution condition, i.e., the conditional reconfiguration, is for CPA or for CPC.

[00299] In one example, it is a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE that generates (or provides input to) the configuration for at least one of the measurement reporting configurations (or measurement configurations).

[00300] Using different measIDs of the same execution condition for CPA and CPC, respectively

[00301] Other embodiments include a method for a User Equipment (UE) to perform the evaluation of at least one conditional reconfiguration with a target candidate PSCell cell. According to the method, the UE receives a message (e.g., RRCReconfiguration) including a conditional reconfiguration with a target candidate PSCell cell (with an execution condition that includes at least two different MeasIds and a SCG / target candidate PSCell configuration).

[00302] In some modes, conditional reconfiguration with a target PSCell candidate cell corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration. Conditional reconfiguration corresponds to a Conditional PSCell Addition (CPA) configuration when the UE is not configured with a server / SCG PSCell configuration, and conditional reconfiguration corresponds to a Conditional PSCell Change (CPC) configuration when the UE is configured with a Petition 870250081883, dated 11 / 09 / 2025, page 88 / 236 / 183 PSCell server configuration / SCG.

[00303] Also according to the method, the UE performs the execution condition evaluation of a subset of the MeasIds that are configured as part of the execution condition, where the subset used depends on whether the conditional reconfiguration corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration, that is, whether the UE is configured with a server PSCell or not.

[00304] In one example, the UE is configured with a conditional reconfiguration with a target PSCell candidate cell that is used for CPA or CPC, where the execution condition is configured with, for example, condExecutionCond, which includes two different measurement configuration identities (i.e., two different MeasIds). One of these MeasIds is associated with a conditional event for CPA (e.g., CondEvent A4) and the other is associated with a conditional event for CPC (e.g., CondEvent A3 or CondEvent A5). When the UE is not configured with any server PSCell, it evaluates the execution condition for the conditional reconfiguration (i.e., CPA configuration) using only the MeasId (measurement configuration identity) associated with the conditional event for CPA (CondEvent A4).When UE is configured with a server PSCell, it evaluates the execution condition for conditional reconfiguration (i.e., CPC configuration) using only the other MeasId (measurement configuration identity), that is, the one associated with the conditional event for CPC (CondEvent A3 or CondEvent A5).

[00305] Alternatively, the UE receives an indication from the network that the execution condition for the conditional reconfiguration is used for both CPA and CPC. In one example, it is explicitly indicated which MeasId is for CPA and which is for CPC. In another example, it is implicitly stated which MeasId is for CPA and which is for CPC, for example, based on the order in Petition 870250081883, dated 11 / 09 / 2025, page 89 / 236 / 183, which are included in the message / IE or based on the type of conditional events to which they are associated (so that, for example, CondEvent A4 is used for CPA and CondEvent A3 or CondEvent A5 is used for CPC).

[00306] Below is an example implementation for TS 38.331, V17.3.0 (Rel-17), where the additions are underlined: -- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddModr16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16, condExecutionCond-r16 SEQUENCE (SIZE (1..2)) FROM MeasId OPTIONAL, -- Requires M condRRCReconfig-r16 STRING OF OCTETS (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ..., [[ condExecutionCondSCG-r17 OCTET STRING (CONTAINING CondReconfigExecCondSCG-r17) OPTIONAL -- Requires M ]], U combinedCPAC-execCond-r18 ENUMERATED {true} OPTIONAL -- Requires M ]]} CondReconfigExecCondSCG-r17 ::= SEQUENCE Petition 870250081883, dated 11 / 09 / 2025, page 90 / 236 / 183 (SIZE (1..2)) OF MeasId -- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP

[00307] 5.3.5.13.4 Conditional Reconfiguration Assessment

[00308] The EU must: 1> For each condReconfigld in VarConditionalReconfig: 2> If the RRCReconfiguration in the RRCReconfig includes the masterCellGroup, including reconfigurationWithSync: 3> Consider the cell that has a physical cell identity corresponding to the value indicated in ServingCellConfigCommon included in reconfigurationWithSync within the masterCellGroup in condRRCReconfig received as the applicable cell; 2> Otherwise, if the RRCReconfiguration within condRRCReconfig includes the secondaryCellGroup, including the reconfiguration WithSync: 3> Consider the cell that has a physical cell identity corresponding to the value indicated in ServingCellConfigCommon included in the WithSync reconfiguration within the secondaryCellGroup within the condRRCReconfig received as the applicable cell; 3> If the UE is currently configured with an SpCell for the SCG (i.e., a PSCell): 4> In the remainder of the procedure, consider conditional reconfiguration with condReconfigId to match a CPC configuration; 3> Otherwise, (the UE is not currently configured with any SpCell for the SCG, i.e., PSCell): 4> In the remainder of the procedure, consider conditional reconfiguration with condReconfigId to match a CPA configuration; Petition 870250081883, dated 11 / 09 / 2025, page 91 / 236 / 183 2> if condExecutionCondSCG is configured: 3> For the remainder of the procedure, consider each measId indicated in condExecutionCondSCG as a measId in the VarMeasConfig associated with the SCG measConfig; 2> If condExecutionCond is configured: 3> if configured by SRB3 or configured in nr-SCG or in nr-SecondaryCellGroupConfig (specified in TS 36.331

[10] ) by SRB1: 4> In the remainder of the procedure, consider each measId indicated in condExecutionCond as a measId in the VarMeasConfig associated with the SCG measConfig; 3> otherwise: 4> In the remainder of the procedure, consider each measId indicated in condExecutionCond as a measId in the VarMeasConfig associated with the MCG measConfig; 2> For each measId included in the measIdList within the VarMeasConfig indicated in the condExecutionCond or condExecutionCondSCG associated with the condReconfigId: 3> if the condEventId is associated with condEventT1, and if the applicable entry condition for this event associated with the condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within the VarConditionalReconfig, is met for the applicable cell; or 3> if condEventId is associated with condEventD1, and if the applicable entry conditions for this event associated with condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, are met for the applicable cell during the corresponding timeToTrigger defined for this event within VarConditionalReconfig; or Petition 870250081883, dated 11 / 09 / 2025, p. 92 / 236 / 183 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the applicable input condition(s) for this event associated with condReconfigld, i.e., the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is met for applicable cells for all measurements after layer 3 filtering performed during the corresponding timeToTrigger defined for this event within VarConditionalReconfig: 4> Consider the event associated with that measId as completed; 3> if the measureId for this event associated with condReconfigId has been modified; or 3> if the condEventId is associated with condEventT1, and if the applicable exit condition for this event associated with the condReconfigId, that is, the event corresponding to the condEventId(s) of the corresponding condTriggerConfig within the VarConditionalReconfig, is met for the applicable cell; or 3> if condEventId is associated with condEventD1, and if the applicable exit condition(s) for this event associated with condReconfigId, that is, the event corresponding to condEventId(s) of the corresponding condTriggerConfig within VarConditionalReconfig, is met for the applicable cell during the corresponding timeToTrigger defined for this event within VarConditionalReconfig; or 3> If condEventId is associated with condEventA3, condEventA4, or condEventA5, and if the applicable input condition(s) for this event associated with condReconfigId, i.e., the event corresponding to the corresponding condEventId(s) of condTriggerConfig within VarConditionalReconfig, is met for applicable cells for all measurements after layer 3 filtering performed during the corresponding timeToTrigger defined for this event within VarConditionalReconfig: Petition 870250081883, dated 11 / 09 / 2025, p. 93 / 236 / 183 4> Consider the event associated with that measId as not fulfilled; 2> If combinedCPAC-execCond is configured: 3> if the conditional reconfiguration matches a CPC configuration and the conditional event A3 or A5 that is associated with one of the measId within condTriggerConfig for a target candidate cell within the stored condRRCReconfig is met; or 3> If the conditional reconfiguration matches a CPA configuration and the conditional event A4, which is associated with one of the measIds within condTriggerConfig for a target candidate cell within the stored condRRCReconfig, is met: 4> Consider the target candidate cell within the stored condRRCReconfig, associated with that condReconfigld, as a triggered cell; 4> Start executing the conditional reconfiguration, as specified in 5.3.5.13.5; 2> Otherwise, if the event(s) associated with all measId(s) within the condTriggerConfig for a target candidate cell within the stored condRRCReconfig is / are fulfilled: 3> Consider the target candidate cell within the stored condRRCReconfig, associated with that condReconfigId, as a triggered cell; 3> Start executing the conditional reconfiguration, as specified in 5.3.5.13.5; NOTE 1: Up to 2 MeasId can be configured for each condReconfigId. The conditional reconfiguration event of the 2 MeasId can have the same or different event conditions, number of triggers, trigger time and trigger limit

[00309] NOTE 2: Empty. Petition 870250081883, dated 11 / 09 / 2025, page 94 / 236 / 183

[00310] Alternatively, at least one new execution condition is introduced, for example, in CondReconfigToAddMod, where the execution condition, in one example, includes more than two MeasIds. A subset of the included MeasIds is then used for CPA evaluation and a subset is used for CPC, as described above. This allows more than one measurement configuration (MeasId) and associated reporting configuration to be defined for CPA and / or CPC, respectively. The measurement configurations included in the new execution conditions can refer to the MCG measConfig or the SCG measConfig. In one example, the MeasIds of the new execution condition can be defined (e.g., split) in a way that indicates what type of conditional reconfiguration they refer to, for example, whether they refer to (are associated with a conditional event for) CPA or CPC.

[00311] As an alternative to the above methods, different MeasIds for the same execution condition (as defined, for example, by condExecutionCond or condExecutionCondSCG or a new field or IE) are used to evaluate two other types of conditional reconfigurations, for example, a Conditional Handover (CHO) and a Conditional PSCell Addition (CPA), or CHO and CPC. In one example, the execution condition includes different MeasIds, where one or more is / are for CHO and the other MeasId(s) is / are for CPA or CPC. In this case, different MeasIds of the same execution condition refer to different measurement objects (measObjects).

[00312] Still other embodiments include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate cell of PSCell. According to the method, the network node sends a message (e.g., RRCReconfiguration) to the UE, including a conditional reconfiguration with a target candidate cell of Petition 870250081883, dated 11 / 09 / 2025, p. 95 / 236 / 183 PSCell (with an execution condition and a PSCell target / candidate SCG configuration).

[00313] In some modes, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration.

[00314] In some modes, the execution condition includes at least two measIds, that is, identities for at least two different measurement configurations, where one of these measurement configurations is associated with a conditional event for CPA, for example, conditional event A4 (CondEvent A4) and the other different measurement configuration is associated with a conditional event for CPC, for example, conditional event A3 (CondEvent A3) or A5 (CondEvent A5).

[00315] In some modes, only one of the measurement configurations (measIds) is used by the UE at a time, depending on whether the evaluation of the execution condition, i.e., the conditional reconfiguration, is for CPA or CPC. For example, the UE uses only the measurement configuration (measId) associated with conditional event A4 (CondEvent A4) when evaluating for CPA and only the measurement configuration (measId) associated with conditional event A3 or A5 (CondEvent A3 or CondEvent A5) when evaluating for CPC. In one example, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell.

[00316] Alternatively, the network provides an indication to the UE that the execution condition for conditional reconfiguration is used for both CPA and CPC. Petition 870250081883, dated 11 / 09 / 2025, page 96 / 236 / 183

[00317] Alternatively, at least one new execution condition is configured by the network node for the UE, for example, within CondReconfigToAddMod, where the execution condition, in one example, includes more than two MeasIds. A subset of the included MeasIds is then indicated to the UE to be used in the CPA assessment and a subset is used for the CPC. The measurement settings included in the new execution conditions can refer to the MCG measConfig or the SCG measConfig. In one example, the MeasIds of the new execution condition can be defined (e.g., split) in a way that indicates what type of conditional reconfiguration they refer to, for example, whether they refer to (are associated with a conditional event for) CPA or CPC.

[00318] In one example, it is a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE that generates (or provides input to) the configuration for at least one of the measurement configurations (or associated measurement reporting configurations).

[00319] Update of execution condition in addition to PSCell and / or release of PSCell

[00320] Other modalities include a method for a User Equipment (UE). According to the method, the UE receives one or more conditional reconfigurations, for example, through one or more RRCReconfiguration messages, which correspond to CPA configurations, i.e., they are conditional reconfigurations with a PSCell target candidate cell (including an execution condition and an SCG / PSCell target candidate configuration) and are received by the UE when it is not configured with any server PSCell / SCG configuration. In one example, the execution conditions and / or measurement configurations for the CPA configurations are associated with the conditional event A4.

[00321] In some modes, at least one of the configurations Petition 870250081883, dated 11 / 09 / 2025, page 97 / 236 / 183 of CPA includes, or is associated with, an indication of how to update the execution conditions and / or measurement settings for the other stored CPA settings that the UE maintains when executing the first CPA setting. When executing the CPA setting, the UE updates the execution conditions and / or measurement settings for other CPA settings that are maintained after the corresponding addition of a PSCell / SCG setting, i.e., which then correspond to the CPC settings.

[00322] Alternatively, the execution conditions and / or measurement settings for the stored CPA settings (which after CPA setting execution would correspond to CPC settings) are updated to be associated with conditional event A3 or conditional event A5. Through the information included or associated with updating the execution condition and / or measurement setting for other CPA / CPC settings upon CPA setting execution, the UE then receives trigger conditions that take into account a server SpCell (PSCell) when evaluating the setting for CPC. Furthermore, the UE can be configured with execution conditions and / or measurement settings for the different CPA / CPC settings (when used for CPC) that are relevant to the current server PSCell.For example, when performing a CPA configuration to add PSCell A, this CPA configuration includes updates to the execution condition and / or measurement configuration for the CPA / CPC configurations regarding other candidate target PSCells, which are based on the fact that PSCell A is the server PSCell for the UE, while the CPA configuration to add PSCell B includes or is associated with the execution condition and / or measurement configuration for the other CPA / CPC configurations that are based on the fact that PSCell B is the server PSCell for the UE.

[00323] In one example, the updated configuration for the others Petition 870250081883, dated 11 / 09 / 2025, p. 98 / 236 / 183 CPA / CPC settings are included in the SCG / candidataalvo configuration of PSCell (i.e., in the RRCReconfiguration message included in condRRCReconfig) of the CPA / CPC configuration that is executed.

[00324] In one example, the updated configuration for the other CPA / CPC settings is included in the IE CondReconfigToAddMod, but outside of the SCG / PSCell target candidate configuration (i.e., condRRCReconfig) that is applied.

[00325] Alternatively, the executed CPA configuration also includes, or is associated with, updates to the execution condition and / or measurement configuration for the CPA configuration itself, i.e., the one that is executed where the server PSCell (after CPA execution) is the candidate target PSCell. In one example, the updates to the execution condition and / or measurement configuration then correspond to the fact that they are associated with conditional events A3 or A5, i.e., to take into account a server SpCell (PSCell). This CPA / CPC configuration can then be stored in a subsequent PSCell change and then used for a subsequent CPC.

[00326] Alternatively, the UE receives instructions from the network on how to update the execution conditions and / or measurement settings to stored CPA settings that the UE maintains during the execution of a normal (i.e., unconditional) PSCell add-on procedure. In one example, the UE obtains information in the PSCell add-on command message, for example, an RRC reconfiguration message (such as RRCReconfiguration), on how to update the execution conditions and / or measurement settings to those CPA settings that now become CPC settings as part of the PSCell add-on procedure. In one example, the updates to the execution condition and / or measurement setting correspond to the fact that they are associated with conditional events A3 or A5, i.e., to take into account a SpCell. Petition 870250081883, dated 11 / 09 / 2025, page 99 / 236 / 183, employee (PSCell).

[00327] Alternatively, updating the execution condition and / or measurement configuration for a stored CPA / CPC configuration (i.e., a conditional reconfiguration that can be used for CPA or CPC) involves adding an execution condition to the conditional reconfiguration (the CPA / CPC configuration). For example, before updating the execution condition and / or measurement configuration, the UE has one execution condition for the conditional reconfiguration, and after the update, the UE has two execution conditions for the conditional reconfiguration. In one example, the two execution conditions consist of condExecutionCond and condExecutionCondSCG in the CondReconfigToAddMod that configures the CPA / CPC configuration. The condExecutionCond is then associated with conditional event A4 and used for CPA, and the condExecutionCondSCG is associated with conditional events A3 or A5 and used for CPC.The execution condition for CPA (condExecutionCond) is then, for example, generated by MN, and the execution condition for CPC (condExecutionCondSCG) is, for example, generated by an SN, such as the SN that generates the updated execution condition and / or measurement configuration, for example, the target SN of the CPA configuration (or normal PSCell change configuration) that is executed. In one example, UE only applies the updates or additions of the execution conditions and / or measurement configuration when the executed CPA / CPC configuration matches a CPA, i.e., only when it leads to a PSCell addition procedure.

[00328] In one embodiment, the UE receives, from the network, an indication of updates to the operating conditions and / or measurement settings for the (at least one) stored CPC configuration that is retained (i.e., not released) when the PSCell / SCG configuration is released. In one example, the UE receives a reconfiguration message. Petition 870250081883, dated 11 / 09 / 2025, page 100 / 236 / 183 RRC (e.g., RRCReconfiguration) configures the release of the PSCell / SCG configuration, and the message includes an update to the execution condition and / or measurement configuration for at least one CPC configuration that is retained and then used for CPA. In one example, the execution condition and / or measurement configuration are updated to become associated with an A4 conditional event.

[00329] Alternatively, the UE stores the execution conditions to be used for the CPA configuration that the UE received from the network, even if a PSCell / SCG configuration is added to the UE, and the execution condition and / or measurement configuration are changed to be associated with conditional events that should be used for CPC. When the PSCell / SCG configuration is released, the UE uses the stored execution conditions to be used again for CPA. Alternatively, the UE receives additional execution conditions and / or measurement configurations for the CPA / CPC configuration when it applies / executes another CPA / CPC configuration (or performs another normal PSCell change procedure). The UE then retains the original execution condition and / or measurement configuration (related to CPA) for the CPA / CPC configuration and uses this in the evaluation when the UE is (again) not configured with any PSCell / SCG.

[00330] Other embodiments include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least two conditional reconfigurations with a target candidate PSCell cell. According to the method, the network node sends at least one message (e.g., RRCReconfiguration) to the UE providing at least two conditional reconfigurations with a target candidate PSCell cell (each with an execution condition and a SCG / target candidate PSCell configuration).

[00331] In some modes, conditional reconfigurations Petition 870250081883, dated 11 / 09 / 2025, p. 101 / 236 / 183 with a target candidate cell of PSCell corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration.

[00332] In some embodiments, at least one of the conditional reconfigurations includes information relating to updates or additions of execution condition and / or measurement configuration for other conditional reconfigurations to be applied if / when the conditional reconfiguration is executed. In one example, the network node includes information about updates from other conditional reconfigurations within the applied / executed PSCell target candidate / SCG configuration. In another example, the network node includes information about updates from other conditional reconfigurations within the conditional reconfiguration (e.g., in CondReconfigToAddMod).

[00333] In one example, conditional reconfiguration with a target PSCell candidate cell corresponds to a Conditional PSCell Addition (CPA) configuration if / when the UE is not configured with any server / SCG PSCell, and corresponds to a Conditional PSCell Change (CPC) configuration if / when the UE is configured with a server / SCG PSCell. In one example, the network node provides the UE with an added / updated execution condition that must be applied on CPA execution or PSCell addition, which is associated with an SCG measurement configuration. It can, for example, be provided as an IE CondExecutionCondSCG.

[00334] In one example, it is a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE that generates (or provides input to) the run condition updates or additions and / or measurement configuration that are provided to the UE.

[00335] Alternatively, the network node includes information about updates to operating conditions and / or measurement settings for Petition 870250081883, dated 11 / 09 / 2025, page 102 / 236 / 183 conditional reconfigurations that the UE has stored, which correspond to the CPC settings, in a message (e.g., an RRC reconfiguration message, such as RRCReconfiguration) that is sent to the UE to release the SCG configuration (i.e., the PSCell) and where these stored conditional reconfigurations become corresponding to the CPA settings. In one example, the execution conditions and / or measurement settings are updated to be associated with the conditional event A4 (condEvent A4), instead of the conditional event A3 (condEvent A3) or the conditional event A5 (condEvent A5). In one example, the network node corresponds to a node that acts as a Master Node (MN) for the UE.

[00336] Combined execution condition for MCG measConfig and execution condition for SCG measConfig

[00337] Other embodiments include a method for a User Equipment (UE) to perform the evaluation of at least one conditional reconfiguration with a target PSCell candidate cell. According to the method, the UE receives a message (e.g., RRCReconfiguration) including a conditional reconfiguration with a target PSCell candidate cell (with two different execution conditions and a PSCell target SCG / candidate configuration).

[00338] In some modes, conditional reconfiguration with a target PSCell candidate cell corresponds to a Conditional PSCell Add (CPA) configuration or a Conditional PSCell Change (CPC) configuration. For example, conditional reconfiguration corresponds to a Conditional PSCell Add (CPA) configuration when the UE is not configured with a server / SCG PSCell configuration, and conditional reconfiguration corresponds to a Conditional PSCell Change (CPC) configuration when the UE is configured with a server / SCG PSCell configuration. Petition 870250081883, dated 11 / 09 / 2025, page 103 / 236 / 183

[00339] Also according to the method, the UE performs the conditional reconfiguration assessment by evaluating only one of the configured execution conditions, where the UE determines which of the execution conditions to evaluate according to whether the conditional reconfiguration corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration, that is, whether the UE is configured with a server PSCell or not.

[00340] Consider other modalities that exploit multiple execution condition fields 26-1, 26-3 that are exemplified in this document with modalities A20-A23 in GROUP A MODALITIES IN THIS DOCUMENT, and with respect to Figure 7.

[00341] Alternatively, the two execution conditions are configured using condExecutionCond and condExecutionCondSCG in the CondReconfigToAddMod that configures the CPA / CPC configuration. The UE then uses the execution condition configured in condExecutionCond for evaluation when the conditional reconfiguration matches a CPA configuration, and uses the execution condition configured in condExecutionCondSCG for evaluation when the conditional reconfiguration matches a CPC configuration. In one example, the execution condition for CPA is configured by a node acting as a Master Node (MN) for the UE, and the execution condition for CPC is configured by a node acting as a Secondary Node (SN) for the UE.

[00342] Alternatively, a new execution condition, for example, condExecutionCond-cpac, is included in the CondReconfigToAddMod that configures the CPA / CPC configuration, and the UE is configured with this new execution condition (condExecutionCond-cpac) and condExecutionCond. In one example, it is a node acting as a Master Node (MN) for the UE that generates both execution condition configurations, and the UE uses one of them in the case of CPA and the other in the case of CPC. Petition 870250081883, dated 11 / 09 / 2025, p. 104 / 236 / 183

[00343] Some embodiments include a method for a network node, for example, a node acting as a Master Node (MN) for a UE, to configure the UE with at least one conditional reconfiguration with a target candidate PSCell cell. According to the method, the network node sends at least one message (e.g., RRCReconfiguration) to the UE providing at least one conditional reconfiguration with a target candidate PSCell cell (with two different execution condition settings and one SCG / target candidate PSCell setting).

[00344] In some modes, conditional reconfiguration with a target candidate PSCell cell corresponds to a Conditional PSCell Addition (CPA) configuration or a Conditional PSCell Change (CPC) configuration.

[00345] In some modes, one of the provided execution condition settings must be used by the UE when the conditional reconfiguration matches a CPA configuration, i.e., when the UE is not configured with a server / SCG PSCell, and the other execution condition setting must be used by the UE when the conditional reconfiguration matches a CPC configuration, i.e., when the UE is configured with a server / SCG PSCell.

[00346] In one example, the two execution condition settings are configured using condExecutionCond and condExecutionCondSCG in the CondReconfigToAddMod that is used to configure conditional reconfiguration. The execution condition to be used for CPA is then configured with condExecutionCond and the execution condition to be used for CPC is configured with condExecutionCondSCG. The execution condition can also be associated with a corresponding measurement setting.

[00347] In one example, a node that is acting as, or is a candidate to become, a Secondary Node (SN) for the UE generates the condition of Petition 870250081883, dated 11 / 09 / 2025, page 105 / 236 / 183 execution and / or configuration of measurement for CPC.

[00348] Note that the description refers to a first network node operating as a Master Node (MN), for example, having a Master Cell Group (MCG) configured for the UE; this MN can be a gNodeB, or a Central Unit gNodeB (CU-gNB) or an eNodeB, or a Central Unit eNodeB (CU-eNB), or any network node and / or network function. The description also refers to a second network node operating as a Secondary Node (SN), or a Source Secondary Node (SSN), for example, having a pre-configured (i.e., unconnected) Secondary Cell Group (SCG) to the UE; this SN can be a gNodeB, or a Central Unit gNodeB (CU-gNB) or an eNodeB, or a Central Unit eNodeB (CU-eNB), or any network node and / or network function. Note that MN, S-SN, and T-SN may be from the same or different radio access technologies (and possibly associated with different nodes in the main network).

[00349] The text frequently refers to a “Secondary Node (SN)” or target SN. This is equivalent to saying that it is a target candidate SN or a network node associated with a target candidate PSCell that is being configured. If the UE were to connect to this cell, transmissions and receptions with the UE would be handled by this node, if the cell is associated with it.

[00350] The text says that a cell resides in a node, for example, a target candidate cell resides in SN-S or SN-t. This is equivalent to saying that a cell is managed by the node, or is associated with the node, or associated with the node, or that the cell belongs to the node, or that the cell is of the node.

[00351] “SN-initiated CPC” refers to a procedure where the Source SN for a UE configured with MR-DC determines the CPC configuration. When determining the source SN, one or more candidate cells (target candidate PSCell(s)) are selected, for example, based on reported measurements, in which at least one cell is Petition 870250081883, dated 11 / 09 / 2025, p. 106 / 236 / 183 associated with the Origin SN and at least one other cell is associated with a neighboring SN. It can be said that if all candidate target cells are associated with the Origin SN, this is an “intra-SN CPC initiated by SN”, which can be called a Release 16 solution. It can be said that if at least one candidate target cell is associated with a neighboring SN, this is an “inter-SN CPC initiated by SN”, which can be called a Release 17 solution.

[00352] The document refers to a candidate SN, or candidate SN, or an SN, as the network node (e.g., gNodeB) that is prepared during the CPA procedure and that can create an RRC Reconfiguration message with an SCG configuration (e.g., RRCReconfiguration**) to be provided to the UE and stored, with an execution condition, where the UE only applies the message after the execution condition is met. This candidate SN is associated with one or more candidate PSCell cells with which the UE can be configured. The UE can then execute the condition and access one of these candidate cells, associated with a candidate SN that becomes the SN or simply the SN after execution (i.e., after the execution condition is met).

[00353] The document refers to a Conditional PSCell Change (CPC) configuration and procedures (such as CPC execution), most often referring to the procedure from the UE perspective. Other terms may be considered synonymous, such as conditional reconfiguration or Conditional Configuration (since the message that is stored and applied after a condition is met is an RRCReconfiguration or RRCConnectionReconfiguration). In terms of terminology, it is also possible to interpret conditional transfer (CHO) in a broader sense, also encompassing CPA (Conditional PSCell Change) procedures. The document refers to a Conditional SN Change in Petition 870250081883, dated 11 / 09 / 2025, p. 107 / 236 / 183 most often refers to the procedure from the EU perspective, to refer to procedures between network nodes where a node requests a target candidate SN (which may be the same as the Origin SN or a neighboring SN) to set up a Conditional PSCell Change (CPC) for at least one of its associated cells (cell associated with the target candidate SN).

[00354] The document refers to CPAC as a way of referring to a Conditional PSCell Addition (CPA) or a Conditional PSCell Amendment (CPC).

[00355] The document refers to a neighboring SN and a Source SN as different entities, although both may be a target candidate SN for the CPC.

[00356] CPC configuration can be done using the same IEs as conditional transfer, which can be called at some point as conditional configuration or conditional reconfiguration. The configuration principle is the same, with the configuration of trigger / execution conditions and a reconfiguration message to be applied when the trigger conditions are met.

[00357] In the different description modalities, these IEs are used differently, for example, sometimes generated by the MN, sometimes generated by the originating SN, sometimes by a target candidate SN.

[00358] In the different modalities of the description, the CPC is said to be in MN format when the CPC configuration is not configured as an MR-DC configuration in mrdc-SecondaryCellGroup (as defined in TS 38.331 V17.3.0). In other words, the UE receives an RRCReconfiguration from MN that may contain the mrdcSecondaryCellGroup (for example, if the UE is also configured with an SCG MeasConfig for inter-SN CPC), but the CPC is not within that container. This means that the IEs to configure the CPC (by Petition 870250081883, dated 11 / 09 / 2025, page 108 / 236 / 183 example, the IE ConditionalReconfiguration) is not included in the mrdcSecondaryCellGroup. The CPA is also in MN format, but the UE is configured with CPA when it does not have any PSCell / SCG configured, i.e., it was not configured with mrdc-SecondaryCellGroup.

[00359] In the different modalities of the description, the CPC is said to be in SN format when the CPC configuration is configured as an MR-DC configuration in mrdc-SecondaryCellGroup (as defined in TS 38.331 V17.3.0). In other words, the UE receives an RRCReconfiguration from the MN that may contain the mrdc-SecondaryCellGroup, and the CPC is within that container. This means that the IEs to configure the CPC (e.g., the ConditionalReconfiguration IE) are included in the mrdc-SecondaryCellGroup (e.g., within a series of other nested IEs).

[00360] In the different embodiments of the description, a conditional reconfiguration with a PSCell target candidate cell is said to include an SCG / PSCell target candidate configuration. The SCG / PSCell target candidate configuration can then, in some instances, be interpreted as condRRCReconfig-r16 (containing an RRCReconfiguration message) within CondReconfigToAddMod-r16, which is the configuration (including a PSCell target / SCG configuration) that the UE applies when the associated execution conditions are met (and the conditional reconfiguration should be executed). Sometimes, it is also said that a conditional reconfiguration with a target candidate cell of PSCell includes an execution condition, where this can, in some examples, be interpreted as (but not limited to) condExecutionCond-r16 and / or condExecutionCondSCG-r17 within CondReconfigToAddMod-r16.

[00361] In a different modality from the description, it is said that an execution condition corresponds to or is associated with a given conditional event. This can be interpreted as (but is not limited to) Petition 870250081883, dated 11 / 09 / 2025, page 109 / 236 / 183, states that the execution condition includes a measurement configuration identity (measId), which is included in a MeasIdToAddMod instance that includes a measurement report configuration identity (ReportConfigId) that is included in a ReportConfigToAddMod instance with a configuration that includes this conditional event, for example, that an included ReportConfigNR has reportType set to condTriggerConfig and that condTriggerConfig includes configuration for the corresponding conditional event.

[00362] In view of the modifications and variations presented in this document, Figure 15 describes a method performed by a communication device 12 according to particular modalities. The method includes receiving, from a network node 14 in a communication network 10, a conditional reconfiguration 20 (Block 1500). The conditional reconfiguration 20 indicates a configuration 22 of a candidate target cell (Block 1500A). The conditional reconfiguration 20 also indicates a first condition 24-1 that the communication device 12 must evaluate, to determine whether to apply the configuration 22, when the communication device 12 is not configured with a Primary and Secondary Cell Group server, SCG, Cell, PSCell (Block 1500B).Conditional reconfiguration 20 further indicates a second condition 24-2 that communication device 12 must evaluate to determine whether to apply configuration 22 when communication device 12 is configured with a server PSCell (Block 1500C).

[00363] In some embodiments, the method also includes determining whether or not communication device 12 is configured with a server PSCell (Block 1530).

[00364] In some embodiments, the method also comprises, based on the determination, evaluating the first or second condition 24-2 to determine whether configuration 22 (Block 1540) should be applied. Petition 870250081883, dated 11 / 09 / 2025, page 110 / 236 / 183

[00365] In some embodiments, the method also comprises, in response to the determination of the application of configuration 22, applying configuration 22 (Block 1550).

[00366] In some embodiments, communication device 12 must evaluate the first condition 24-1, when communication device 12 is not configured with a server PSCell, to determine whether configuration 22 should be applied to add the candidate target cell as a server PSCell, and communication device 12 must evaluate the second condition 24-2, when communication device 12 is configured with a server PSCell, to determine whether configuration 22 should be applied to change a server PSCell from a source cell to the candidate target cell.

[00367] In some embodiment, the conditional reconfiguration 20 includes an execution condition field 26 that indicates the first and second conditions 24-1, 24-2.

[00368] In some modes, the execution condition field 26 identifies a measurement configuration 28. In some modes, the measurement configuration 28 is associated with a reporting configuration 30. In some modes, the reporting configuration 30 indicates the first and second conditions 24-1, 24-2.

[00369] In some modes, report configuration 30 indicates an event whose occurrence triggers communication device 12 to apply configuration 22. In some modes, the event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the event is also defined to occur when the second condition 24-2 is met while communication device 12 is configured with a server PSCell.

[00370] In some modalities, the first condition 24-1 is a Petition 870250081883, dated 11 / 09 / 2025, p. 111 / 236 100 / 183 is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements performed on a server PSCell. In some embodiments, the second condition 24-2 is a function of the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00371] In some embodiments, the event is defined to occur when an input condition is met and an output condition is not met. In some embodiments, the input condition is defined to be met when a first subcondition is met while communication device 12 is not configured with a PSCell server. In some embodiments, the input condition is defined to be met when the first subcondition and a second subcondition are met while communication device 12 is configured with a PSCell server. In some embodiments, the output condition is defined to be met when a third subcondition is met while communication device 12 is not configured with a PSCell server.In some embodiments, the exit condition is defined as satisfied when the third subcondition or a fourth subcondition is satisfied while communication device 12 is configured with a PSCell server. In some embodiments, the first condition 24-1 is satisfied when the first subcondition is satisfied and the third subcondition is not satisfied while communication device 12 is not configured with a PSCell server. In some embodiments, the second condition 24-2 is satisfied when the first and second subconditions are satisfied, and neither the third nor the fourth subcondition is satisfied, while communication device 12 is configured with a PSCell server.

[00372] In some modalities, the event is an A5 Event, a Petition 870250081883, dated 11 / 09 / 2025, p. 112 / 236 101 / 183 Event A4, Event A5-CPAC, or Event A4-CPAC.

[00373] In other modes, the event is defined to occur when an input condition is met and an output condition is not met. In some modes, the input condition is defined to be met when a first subcondition is met while communication device 12 is not configured with a PSCell server. In some modes, the input condition is defined to be met when a second subcondition is met while communication device 12 is configured with a PSCell server. In some modes, the output condition is defined to be met when a third subcondition is met while communication device 12 is not configured with a PSCell server. In some modes, the output condition is defined to be met when a fourth subcondition is met while communication device 12 is configured with a PSCell server.In some embodiments, the first condition 24-1 is satisfied when the first subcondition is satisfied and the third subcondition is not satisfied as long as communication device 12 is not configured with a server PSCell. In some embodiments, the second condition 24-2 is met when the second subcondition is met and the fourth subcondition is not met as long as communication device 12 is configured with a server PSCell.

[00374] In some modalities, the event is an A3 Event or an A3-CPAC Event.

[00375] In some modes, report configuration 30 indicates the first and second events whose occurrence triggers communication device 12 to apply configuration 22 while communication device 12 is and is not configured with a server PSCell, respectively. In some modes, the first condition 24-1 is Petition 870250081883, dated 11 / 09 / 2025, page 113 / 236 Condition 102 / 183 is fulfilled when the first event occurs, and the second condition 24-2 is fulfilled when the second event occurs.

[00376] In some modes, the execution condition field 26 identifies a measurement configuration 28. In some modes, the measurement configuration 28 is associated with the first and second report configurations 30. In some modes, the first report configuration 30 indicates the first condition 24-1 and the second report configuration 30 indicates the second condition 24-2.

[00377] In some modes, the first reporting configuration 30 indicates a first event whose occurrence is to trigger communication device 12 to apply configuration 22. In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the second reporting configuration 30 indicates a second event whose occurrence is to trigger communication device 12 to apply configuration 22.

[00378] In some embodiments, the second event is defined to occur when the second condition 24-2 is met while the communication device 12 is configured with a PSCell server. In some embodiments, the first and second report configurations 30 have the same report configuration identifier.

[00379] In some embodiments, the execution condition field 26 identifies the first and second measurement configurations 28.

[00380] In some embodiments, the first measurement configuration 28 is associated with a first report configuration 30, and the second measurement configuration 28 is associated with a second report configuration 30. In some embodiments, the first report configuration 30 indicates the first condition 24-1, and the second report configuration 30 indicates the second condition 24-2. In some embodiments, the first Petition 870250081883, dated 11 / 09 / 2025, page 114 / 236 103 / 183 report configuration 30 indicates a first event whose occurrence triggers communication device 12 to apply configuration 22.

[00381] In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the second reporting configuration 30 indicates a second event whose occurrence is to trigger communication device 12 to apply configuration 22. In some modes, the second event is defined to occur when the second condition 24-2 is met while communication device 12 is configured with a server PSCell.

[00382] In some embodiments, the first and second measurement configurations 28 have the same measurement configuration identifier.

[00383] In some modes, the execution condition field 26 identifies the first and second measurement configurations 28. In some modes, the first measurement configuration 28 is associated with a first report configuration 30 and the second measurement configuration 28 is associated with a second report configuration 30. In some modes, the first report configuration 30 indicates the first condition 24-1 and the second report configuration 30 indicates the second condition 24-2.

[00384] In some embodiments, the first and second measurement configurations 28 have different measurement configuration identifiers.

[00385] In some embodiments, the execution condition field 26 identifies the first and second sets of measurement settings. In some embodiments, the first set of measurement settings includes one or more first measurement settings 28 that are respectively associated with one or more first settings of Petition 870250081883, dated 11 / 09 / 2025, p. 115 / 236 104 / 183 report 30 and the second set of measurement configurations includes one or more second measurement configurations 28 that are respectively associated with one or more second report configurations 30. In some embodiments, one or more first report configurations 30 indicate the first condition 24-1 and one or more second report configurations 30 indicate the second condition 24-2.

[00386] In some modes, conditional reconfiguration 20 includes the first and second execution condition fields 26 which indicate, respectively, the first and second conditions 24-1 and 24-2. In some modes, the first and second execution condition fields 26 identify the first and second measurement configurations 28, respectively. In some modes, the first and second measurement configurations 28 are associated, respectively, with the first and second reporting configurations 30. In some modes, the first and second reporting configurations 30 indicate, respectively, the first and second conditions 24-1 and 24-2. In some modes, the first reporting configuration 30 indicates a first event whose occurrence triggers the communication device 12 to apply the configuration 22.In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the second reporting configuration 30 indicates a second event whose occurrence triggers communication device 12 to apply configuration 22. In some modes, the second event is defined to occur when the second condition 24-2 is met while communication device 12 is configured with a server PSCell.

[00387] In some embodiments, the first condition 24-1 is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements. Petition 870250081883, dated 11 / 09 / 2025, page 116 / 236 105 / 183 performed on a server PSCell, and the second condition 24-2 is a function of the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00388] In some embodiments, the condition reconfiguration corresponds to a conditional PSCell addition configuration when communication device 12 is not configured with a server PSCell and corresponds to a conditional PSCell change configuration when communication device 12 is configured with a server PSCell.

[00389] In some modes, conditional reconfiguration 20 is reusable for adding or changing PSCell.

[00390] In some embodiments, the method further comprises determining whether or not communication device 12 is configured with a server PSCell. In some embodiments, the method further comprises, based on the determination, evaluating the first or second condition 24-2 to determine whether to apply configuration 22. In some embodiments, the method specifically comprises determining whether to apply configuration 22 by applying configuration 22. In some embodiments, applying configuration 22 comprises adding the candidate target cell as a server PSCell or changing a server PSCell from a source cell to the candidate target cell, depending on whether or not communication device 12 is configured with a server PSCell.

[00391] In some embodiments, the method additionally comprises, after applying configuration 22 for adding PSCell, reusing configuration 22 for changing PSCell.

[00392] In some embodiments, the method additionally includes evaluating the first condition 24-1 when the communication device 12 is not configured with a server PSCell, for Petition 870250081883, dated 11 / 09 / 2025, page 117 / 236 106 / 183 determine whether configuration 22 should be applied to add the candidate target cell as a server PSCell. In other embodiments, the method additionally comprises the alternative or additional evaluation of the second condition 24-2 when the communication device 12 is configured with a server PSCell, to determine whether configuration 22 should be applied to change a server PSCell from a source cell to the candidate target cell.

[00393] Figure 16 describes a method performed by a communication device 12 according to other particular embodiments. The method includes receiving, from a network node 14 in a communication network 10, a conditional reconfiguration 20 that indicates a configuration 22 of a candidate target cell and a condition under which the communication device 12 must apply the configuration 22 (Block 1600). The method also includes, after receiving the conditional reconfiguration 20, receiving, from the network node 14, a signal that alters the condition under which the communication device 12 must apply the configuration 22 (Block 1610).

[00394] In some embodiments, the method further comprises, before receiving the signal, detecting the fulfillment of the condition and applying configuration 22 to add the candidate target cell as a server PSCell. In some embodiments, the signal is received after applying configuration 22 to add the candidate target cell as a server PSCell, by means of reception. In some embodiments, the method further comprises, after receiving the signal, detecting the fulfillment of the altered condition and applying configuration 22 to change a server PSCell from a source cell to the candidate target cell.

[00395] In some modes, conditional reconfiguration 20 includes an execution condition field 26 whose value indicates the condition. In some modes, the signaling changes the condition by indicating a value. Petition 870250081883, dated 11 / 09 / 2025, page 118 / 236 107 / 183 changed to execution condition field 26.

[00396] In some modes, conditional reconfiguration 20 includes an execution condition field 26, wherein the execution condition field 26 identifies a measurement configuration 28 that indicates the condition. In some modes, the signaling alters the condition indicating a different measurement configuration 28 for conditional reconfiguration 20.

[00397] Figure 17 describes a method performed by a communication device 12 according to other particular embodiments. The method includes receiving, from a network node 14 in a communication network 10, a conditional reconfiguration 20 that includes a configuration 22 of a candidate target cell (Block 1700). The method also includes determining whether or not the communication device 12 is configured with a Primary and Secondary Cell Group server, SCG, Cell, PSCell (Block 1710). The method also includes, based on whether or not the communication device 12 is configured with a server PSCell, applying the configuration 22 to add the candidate target cell as a server PSCell or to change a server PSCell from a source cell to the candidate target cell (Block 1720).

[00398] In some embodiments, the method further comprises determining which condition to evaluate in order to decide whether or not to apply configuration 22, based on whether or not the communication device 12 is configured with a server PSCell.

[00399] Figure 18 illustrates a method performed by a network node 14 in a communication network 10, according to particular modalities. The method includes the transmission, to a communication device 12, of a conditional reconfiguration 20 (Block 1800). In some cases, the conditional reconfiguration 20 indicates a configuration 22 of a candidate target cell (Block 1800A). The conditional reconfiguration 20 also Petition 870250081883, dated 11 / 09 / 2025, page 119 / 236 108 / 183 indicates a first condition 24-1 that communication device 12 must evaluate to determine whether to apply configuration 22 when communication device 12 is not configured with a Primary and Secondary Cell Group server, SCG, Cell, PSCell (Block 1800B). Conditional reconfiguration 20 further indicates a second condition 24-2 that communication device 12 must evaluate to determine whether to apply configuration 22 when communication device 12 is configured with a PSCell server (Block 1800C).

[00400] In some embodiments, communication device 12 must evaluate the first condition 24-1, when communication device 12 is not configured with a server PSCell, to determine whether configuration 22 should be applied to add the candidate target cell as a server PSCell, and communication device 12 must evaluate the second condition 24-2, when communication device 12 is configured with a server PSCell, to determine whether configuration 22 should be applied to change a server PSCell from a source cell to the candidate target cell.

[00401] In some embodiment, the conditional reconfiguration 20 includes an execution condition field 26 that indicates the first and second conditions 24-1, 24-2.

[00402] In some modes, the execution condition field 26 identifies a measurement configuration 28. In some modes, the measurement configuration 28 is associated with a reporting configuration 30. In some modes, the reporting configuration 30 indicates the first and second conditions 24-1, 24-2.

[00403] In some modes, report configuration 30 indicates an event whose occurrence triggers communication device 12 to apply configuration 22. In some modes, the event is defined to occur when the first condition 24-1 is met, while the device Petition 870250081883, dated 11 / 09 / 2025, pp. 120 / 236 Communication device 12 (109 / 183) is not configured with a PSCell server. In some modes, the event is also defined to occur when the second condition 24-2 is met while communication device 12 is configured with a PSCell server.

[00404] In some embodiments, the first condition 24-1 is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements performed on a server PSCell. In some embodiments, the second condition 24-2 is a function of the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00405] In some embodiments, the event is defined to occur when an input condition is met and an output condition is not met. In some embodiments, the input condition is defined to be met when a first subcondition is met while communication device 12 is not configured with a PSCell server. In some embodiments, the input condition is defined to be met when the first subcondition and a second subcondition are met while communication device 12 is configured with a PSCell server. In some embodiments, the output condition is defined to be met when a third subcondition is met while communication device 12 is not configured with a PSCell server.In some embodiments, the exit condition is defined as satisfied when the third subcondition or a fourth subcondition is satisfied while communication device 12 is configured with a PSCell server. In some embodiments, the first condition 24-1 is satisfied when the first subcondition is satisfied and the third subcondition is not satisfied while communication device 12 is not configured with a PSCell server. In some embodiments, the second... Petition 870250081883, dated 11 / 09 / 2025, pp. 121 / 236 110 / 183 condition 24-2 is satisfied when the first subcondition and the second subcondition are satisfied, and neither the third nor the fourth subcondition are satisfied, while communication device 12 is configured with a PSCell server.

[00406] In some modalities, the event is an A5 Event, an A4 Event, an A5-CPAC Event, or an A4-CPAC Event.

[00407] In other modes, the event is defined to occur when an input condition is met and an output condition is not met. In some modes, the input condition is defined to be met when a first subcondition is met while communication device 12 is not configured with a PSCell server. In some modes, the input condition is defined to be met when a second subcondition is met while communication device 12 is configured with a PSCell server. In some modes, the output condition is defined to be met when a third subcondition is met while communication device 12 is not configured with a PSCell server. In some modes, the output condition is defined to be met when a fourth subcondition is met while communication device 12 is configured with a PSCell server.In some embodiments, the first condition 24-1 is satisfied when the first subcondition is satisfied and the third subcondition is not satisfied as long as communication device 12 is not configured with a server PSCell. In some embodiments, the second condition 24-2 is met when the second subcondition is met and the fourth subcondition is not met as long as communication device 12 is configured with a server PSCell.

[00408] In some modalities, the event is an A3 Event or an A3-CPAC Event. Petition 870250081883, dated 11 / 09 / 2025, pp. 122 / 236 111 / 183

[00409] In some modes, report configuration 30 indicates the first and second events whose occurrence triggers communication device 12 to apply configuration 22 while communication device 12 is and is not configured with a server PSCell, respectively. In some modes, the first condition 24-1 is met when the first event occurs and the second condition 24-2 is met when the second event occurs.

[00410] In some modes, the execution condition field 26 identifies a measurement configuration 28. In some modes, the measurement configuration 28 is associated with the first and second report configurations 30. In some modes, the first report configuration 30 indicates the first condition 24-1 and the second report configuration 30 indicates the second condition 24-2.

[00411] In some modes, the first reporting configuration 30 indicates a first event whose occurrence is to trigger communication device 12 to apply configuration 22. In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the second reporting configuration 30 indicates a second event whose occurrence is to trigger communication device 12 to apply configuration 22.

[00412] In some embodiments, the second event is defined to occur when the second condition 24-2 is met while the communication device 12 is configured with a PSCell server. In some embodiments, the first and second report configurations 30 have the same report configuration identifier.

[00413] In some embodiments, the execution condition field 26 identifies the first and second measurement configurations 28.

[00414] In some modes, the first measurement configuration Petition 870250081883, dated 11 / 09 / 2025, pp. 123 / 236 112 / 183 is associated with a first reporting configuration 30, and the second measurement configuration 28 is associated with a second reporting configuration 30. In some modes, the first reporting configuration 30 indicates the first condition 24-1, and the second reporting configuration 30 indicates the second condition 24-2. In some modes, the first reporting configuration 30 indicates a first event whose occurrence triggers the communication device 12 to apply configuration 22.

[00415] In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a server PSCell. In some modes, the second reporting configuration 30 indicates a second event whose occurrence is to trigger communication device 12 to apply configuration 22. In some modes, the second event is defined to occur when the second condition 24-2 is met while communication device 12 is configured with a server PSCell.

[00416] In some embodiments, the first and second measurement configurations 28 have the same measurement configuration identifier.

[00417] In some modes, the execution condition field 26 identifies the first and second measurement configurations 28. In some modes, the first measurement configuration 28 is associated with a first report configuration 30 and the second measurement configuration 28 is associated with a second report configuration 30. In some modes, the first report configuration 30 indicates the first condition 24-1 and the second report configuration 30 indicates the second condition 24-2.

[00418] In some embodiments, the first and second measurement configurations 28 have different measurement configuration identifiers. Petition 870250081883, dated 11 / 09 / 2025, pp. 124 / 236 113 / 183

[00419] In some embodiments, the execution condition field 26 identifies the first and second sets of measurement configurations. In some embodiments, the first set of measurement configurations includes one or more first measurement configurations 28 that are respectively associated with one or more first report configurations 30, and the second set of measurement configurations includes one or more second measurement configurations 28 that are respectively associated with one or more second report configurations 30. In some embodiments, one or more first report configurations 30 indicate the first condition 24-1, and one or more second report configurations 30 indicate the second condition 24-2.

[00420] In some modes, conditional reconfiguration 20 includes the first and second execution condition fields 26 which indicate, respectively, the first and second conditions 24-1 and 24-2. In some modes, the first and second execution condition fields 26 identify the first and second measurement configurations 28, respectively. In some modes, the first and second measurement configurations 28 are associated, respectively, with the first and second reporting configurations 30. In some modes, the first and second reporting configurations 30 indicate, respectively, the first and second conditions 24-1 and 24-2. In some modes, the first reporting configuration 30 indicates a first event whose occurrence triggers the communication device 12 to apply the configuration 22.In some modes, the first event is defined to occur when the first condition 24-1 is met, while communication device 12 is not configured with a PSCell server. In some modes, the second reporting configuration 30 indicates a second event whose occurrence triggers communication device 12 to apply configuration 22. In some modes, the second event is... Petition 870250081883, dated 11 / 09 / 2025, pages 125 / 236 114 / 183 is set to occur when the second condition 24-2 is met while communication device 12 is configured with a PSCell server.

[00421] In some embodiments, the first condition 24-1 is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements performed on a server PSCell, and the second condition 24-2 is a function of the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00422] In some embodiments, the condition reconfiguration corresponds to a conditional PSCell addition configuration when communication device 12 is not configured with a server PSCell and corresponds to a conditional PSCell change configuration when communication device 12 is configured with a server PSCell.

[00423] In some modes, conditional reconfiguration 20 is reusable for adding or changing PSCell.

[00424] Figure 19 illustrates a method performed by a network node 14 in a communication network 10, according to other particular embodiments. The method includes transmitting, to a communication device 12, a conditional reconfiguration 20 that indicates a configuration 22 of a candidate target cell and a condition under which the communication device 12 must apply the configuration 22 (Block 1900). The method also includes, after transmitting the conditional reconfiguration 20, transmitting to the communication device 12 the signaling that alters the condition under which the communication device 12 must apply the configuration 22 (Block 1910).

[00425] In some modes, conditional reconfiguration 20 includes an execution condition field 26 whose value indicates the condition. In some modes, the signaling changes the condition by indicating a value. Petition 870250081883, dated 11 / 09 / 2025, pages 126 / 236 115 / 183 changed to execution condition field 26.

[00426] In some modes, conditional reconfiguration 20 includes an execution condition field 26. In some modes, the execution condition field 26 identifies a measurement configuration 22 that indicates the condition. In some modes, the signaling changes the condition indicating a different measurement configuration 22 for conditional reconfiguration 20.

[00427] Figure 20 illustrates a method implemented by a user device, UE, 12 for reusing a 401...40-N conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and the conditional alteration of a PSCell in multi-connectivity operation. The method comprises receiving 40-1...40-N conditional reconfigurations for the respective target candidate PSCell cells. In some embodiments, the 40-1.40-N conditional reconfigurations are PSCell addition conditional configurations, CPA, or PSCell conditional alteration configurations, CPC (Block 2000). In some embodiments, each of the 40-1.40-N conditional reconfigurations includes a first execution condition 42-1.42-2 that needs to be met to trigger the execution of the 40-1.40-N conditional reconfiguration. In some modes, each of the 40-1 conditional reconfigurations.40-N includes a PSCell target candidate configuration 44-1.44-N which is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration 40-1.40-N when the conditional reconfiguration 40-1.40-N is executed. In some embodiments, each of at least one of the conditional reconfigurations 40-1...40-N also includes information 46-1.46-N on how, after the execution of the conditional reconfiguration 40-1.40-N, to update the first execution condition 42-1.42-2 of, or add a second execution condition to each or more of the other conditional reconfigurations 40. Petition 870250081883, dated 11 / 09 / 2025, pp. 127 / 236. 116 / 183 1.40-N.

[00428] In some embodiments, the 46-1.46-N information included in each of at least one of the 40-1...40-N conditional reconfigurations is 46-1...46-N information about how, after the execution of the 40-1.40-N conditional reconfiguration, to add a second execution condition to each or more of the other 40-1.40-N conditional reconfigurations. In some embodiments, the 40-1.40-N conditional reconfigurations are CPA configurations, and the 46-1.46-N information in each of at least one of the 40-1.40-N conditional reconfigurations is 46-1.46-N information about how, after the execution of the 40-1.40-N conditional reconfiguration, to add a second execution condition to each or more of the 40-1.40-N conditional reconfigurations to configure the other 40-1.40-N conditional reconfiguration to be reusable as a CPC configuration. In some embodiments, the 46-1.46-N information included in each of at least one of the 40-1.40-N conditional reconfigurations...40-N is information 46-1.46-N about how, after executing the conditional reconfiguration 40-1.40-N towards the target PSCell candidate cell of the conditional reconfiguration 40-1.40-N, to add a second execution condition to each or more of the other conditional reconfigurations 40-1.40-N to configure the other conditional reconfiguration 40-1.40-N to be reusable as a CPC configuration that relies on the target PSCell candidate cell of the conditional configuration being a server PSCell for UE 12. In some embodiments, for each of the one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the first execution condition 42-1.42-2 needs to be met to trigger the execution of the conditional reconfiguration 40-1.40-N when UE 12 is not configured with any server PSCell configuration. or with no secondary cell cluster, SCG. In some modalities, for each one. Petition 870250081883, dated 11 / 09 / 2025, pp. 128 / 236 117 / 183 of one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the second execution condition 42-1.42-2 needs to be met to trigger the execution of the conditional reconfiguration 40-1.40-N when UE 12 is configured with a server PSCell configuration or with an SCG. In some embodiments, for each of one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the first execution condition 42-1.42-2 is associated with conditional event A4. In some embodiments, for each of one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the second execution condition 42-1.42-2 is associated with conditional event A3 or conditional event A5. In some modes, the information 46-1.. .46-N is included in each of at least one of the conditional reconfigurations 40-1.40-N comprises the second execution condition to be added to each of one or more other 40-1.40-N conditional reconfigurations. In some embodiments, for each of one or more other 40-1.40-N conditional reconfigurations to which a second execution condition is added, the second execution condition is added to a condExecutionCondSCG information element of the 40-1.40-N conditional reconfiguration.

[00429] In some embodiments, for each of the 40-1.40-N conditional reconfigurations, the first execution condition is included in a condExecutionCond information element of the 40-1.40-N conditional reconfiguration.

[00430] In some modes, receiving the 40-1.40-N conditional reconfigurations includes receiving the 40-1.40-N conditional reconfigurations when UE 12 is not configured with any server PSCell configuration or with any SCG. Petition 870250081883, dated 11 / 09 / 2025, pp. 129 / 236 118 / 183

[00431] In some embodiment, the 46-1.46-N information included in each of at least one of the 40-1.40N conditional reconfigurations is 46-1.46-N information about how, after the execution of the 40-1.40-N conditional reconfiguration, to update the first execution condition 42-1.42-2 of each or more of the other 40-1.40-N conditional reconfigurations to change the other 40-1.40-N conditional reconfiguration from a CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration.

[00432] In some embodiments, the 46-1.46-N information included in each of at least one of the 40-1.40-N conditional reconfigurations is included in the 40-1.40-N conditional reconfiguration outside the PSCell 44-1.44-N target candidate configuration of the 40-1.40-N conditional reconfiguration.

[00433] In some embodiments, receiving 40-1.40-N conditional reconfigurations comprises receiving one or more Radio Resource Control Reconfiguration (RRC) messages, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more 40-1.40-N conditional reconfigurations.

[00434] In some embodiments, the method further comprises detecting the fulfillment of the execution condition 421.42-2 included in a first conditional reconfiguration 40-1.40-N between said conditional reconfigurations 40-1.40-N (Block 2010). In some embodiments, the method further comprises executing the first conditional reconfiguration 40-1.40-N based on said detection (Block 2020). In some variety, the method further comprises after executing the first conditional reconfiguration 40-1.40-N, (2030) updating the first execution condition 42-1.42-2 of, or adding a second execution condition to each or more of the others. Petition 870250081883, dated 11 / 09 / 2025, pages 130 / 236 119 / 183 conditional reconfigurations 40-1...40-N according to information 461...46-N included in the first conditional reconfiguration 40-1.40-N on how to execute said update or addition (Block 2030). In some embodiments, said update or addition comprises adding a second execution condition to each or more of the conditional reconfigurations 40-1.40-N according to information 46-1.46-N included in the first conditional reconfiguration 40-1.40-N on how to execute said update or addition. In some embodiments, the method further comprises, after said addition, for each of the one or more other conditional reconfigurations 40-1...40-N to which a second execution condition is added, determining whether the conditional reconfiguration 40-1.40N should be executed by evaluating whether the second execution condition is met.In some embodiments, the method further comprises, after said addition, receiving a message that configures a release of a UE 12 PSCell configuration. In some embodiments, the method further comprises, after said addition, after receiving the message, for each of one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, determining whether to execute the conditional reconfiguration 40-1.40-N by evaluating whether the first execution condition 421.42-2 is met.

[00435] Figure 21 describes a method implemented by a network node 14 in a communication network 10 to allow a user device, UE, 12 to reuse a 40-1.40-N conditional reconfiguration for both the conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and the conditional alteration of a PSCell in multi-connectivity operation. The method includes transmitting 40-1.40-N conditional reconfigurations to UE 12 for the respective target candidate PSCell cells. In Petition 870250081883, dated 11 / 09 / 2025, pages 131 / 236 120 / 183 In some modes, the 40-1...40-N conditional reconfigurations are either PSCell add conditional configurations, CPA, or PSCell change conditional configurations, CPC (Block 2100). In some modes, each of the 40-1.40-N conditional reconfigurations includes a first execution condition 42-1.42-2 that needs to be met to trigger the execution of the 40-1.40-N conditional reconfiguration. In some modes, each of the 40-1.40N conditional reconfigurations includes a PSCell target candidate configuration 44-1.44-N which is a configuration to be applied to the PSCell target candidate cell of the 40-1.40-N conditional reconfiguration when the 40-1.40-N conditional reconfiguration is executed. In some embodiments, each of at least one of the 40-1.40-N conditional reconfigurations also includes 46-1.46-N information on how, after the execution of the 40-1.40-N conditional reconfiguration, to update the first execution condition 421.42-2 of each, or add a second execution condition to one or more of the other 40-1.40-N conditional reconfigurations.

[00436] In some embodiment, the 46-1.46-N information included in each of at least one of the 40-1.40N conditional reconfigurations is 46-1.46-N information about how, after the execution of the 40-1.40-N conditional reconfiguration, to add a second execution condition to each or more other conditional reconfigurations. In some embodiments, the 40-1.40-N conditional reconfigurations are CPA configurations, and the 46-1.46-N information in each of at least one of the 40-1.40-N conditional reconfigurations is 46-1.46-N information about how, after executing the 40-1.40-N conditional reconfiguration, to add a second execution condition to each of one or more of the other 40-1.40-N conditional reconfigurations to configure the other 40-1.40-N conditional reconfiguration to be reusable as a CPC configuration. In some embodiments, the information 46Petition 870250081883, dated 11 / 09 / 2025, page 132 / 236 121 / 183 1.46-N included in each of at least one of the 40-1.40-N conditional reconfigurations is 46-1.46-N information about how, after executing the 40-1.40-N conditional reconfiguration toward the target PSCell candidate cell of the 40-1.40-N conditional reconfiguration, to add a second execution condition to each or more of the other 40-1.40-N conditional reconfigurations to configure the other 40-1.40-N conditional reconfiguration to be reusable as a CPC configuration that is based on the target PSCell candidate cell of the conditional configuration being a server PSCell for the UE. In some embodiments, for each of one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the first execution condition 42-1.42-2 needs to be met to trigger the execution of the conditional reconfiguration 40-1.40-N when UE 12 is not configured with any server PSCell configuration or with any secondary cell group, SCG. In some modes, for each of the one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the second execution condition 42-1.42-2 needs to be met to trigger the execution of the conditional reconfiguration 40-1.40-N when UE 12 is configured with a server PSCell configuration or with an SCG. In some modes, for each of the one or more other conditional reconfigurations 40-1.40-N to which a second execution condition is added, the first execution condition 42-1.42-2 is associated with the conditional event A4. In some modes, for each of the one or more other conditional reconfigurations 40-1.40N to which a second execution condition is added, the second execution condition 42-1.42-2 is associated with conditional event A3 or conditional event A5. In some modes, the information 46-1.46N is included in each of at least one of the reconfigurations. Petition 870250081883, dated 11 / 09 / 2025, pp. 133 / 236 122 / 183 conditional 40-1...40-N configurations comprise the second execution condition to be added to each of one or more other conditional 40-1...40-N configurations. In some embodiments, for each of one or more other conditional 40-1.40-N configurations to which a second execution condition is added, the second execution condition is added to a condExecutionCondSCG information element of the conditional 40-1.40-N configuration.

[00437] In some embodiments, for each of the 40-1.40-N conditional reconfigurations, the first execution condition is included in a condExecutionCond information element of the 40-1.40-N conditional reconfiguration.

[00438] In some modes, the transmission of 40-1.40-N conditional reconfigurations includes the transmission of 40-1.40-N conditional reconfigurations when UE 12 is not configured with any server PSCell configuration or with any SCG.

[00439] In some embodiment, the 46-1.46-N information included in each of at least one of the 40-1.40N conditional reconfigurations is 46-1.46-N information about how, after the execution of the 40-1.40-N conditional reconfiguration, to update the first execution condition 42-1.42-2 of each or more of the other 40-1.40-N conditional reconfigurations to change the other 40-1.40-N conditional reconfiguration from a CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration.

[00440] In some embodiments, the 46-1.46-N information included in each of at least one of the 40-1.40-N conditional reconfigurations is included in the 40-1.40-N conditional reconfiguration outside the PSCell 44-1.44-N target candidate configuration of the 40-1.40-N conditional reconfiguration.

[00441] In some modes, the transmission of reconfigurations Petition 870250081883, dated 11 / 09 / 2025, pp. 134 / 236 123 / 183 conditional 40-1...40-N comprises the transmission of one or more Radio Resource Control Reconfiguration (RRC) messages, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more of the 40-1.40-N conditional reconfigurations.

[00442] The embodiments in this document also include corresponding devices. The embodiments described in this document include, for example, a communication device 12 configured to perform any of the steps of any of the embodiments described above for the communication device 12.

[00443] The embodiments also include a communication device 12 comprising a set of processing circuits and a set of power supply circuits. The set of processing circuits is configured to perform any of the steps of any of the embodiments described above for the communication device 12. The set of power supply circuits is configured to supply power to the communication device 12.

[00444] The embodiments additionally include a communication device 12 comprising a set of processing circuits. The set of processing circuits is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the communication device 12 additionally comprises a set of communication circuits.

[00445] The embodiments additionally include a communication device 12 comprising a set of processing circuits and memory. The memory contains instructions executable by the set of processing circuits by means of which the communication device 12 is configured to perform any of the steps of any of the Petition 870250081883, dated 11 / 09 / 2025, pp. 135 / 236 124 / 183 modes described above for communication device 12.

[00446] In addition, the embodiments include a user equipment (UE). The UE comprises an antenna configured to send and receive wireless signals. The UE also comprises a set of radio front-end circuits connected to the antenna and the processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry. The processing circuitry is configured to perform any of the steps of any of the embodiments described above for the communication device 12. In some embodiments, the UE also comprises an input interface connected to the processing circuitry and configured to allow the input of information into the UE to be processed by the processing circuitry.The UE may comprise an output interface connected to the processing circuitry and configured to output UE information that has been processed by the processing circuitry. The UE may also comprise a battery connected to the processing circuitry and configured to supply power to the UE.

[00447] The modalities in this document also include a network node 14 configured to perform any of the steps of any of the modalities described above for network node 14.

[00448] The embodiments also include a network node 14 comprising a processing circuit set and a power supply circuit set. The processing circuit set is configured to perform any of the steps of any of the embodiments described above for network node 14. The power supply circuit set is configured to provide power to network node 14.

[00449] The modalities also include a network node 14 comprising a set of processing circuits. The set of Petition 870250081883, dated 11 / 09 / 2025, pages 136 / 236 125 / 183 processing circuits are configured to perform any of the steps of any of the modes described above for network node 14. In some modes, network node 14 additionally comprises a set of communication circuits.

[00450] The embodiments additionally include a network node 14 comprising a set of processing circuits and memory. The memory contains instructions executable by the set of processing circuits, by means of which the network node 14 is configured to perform any of the steps of any of the embodiments described above for the network node 14.

[00451] More specifically, the devices described above can perform the methods in this document and any other processing through the implementation of any means, modules, units, or sets of functional circuits. In one embodiment, for example, the devices comprise respective circuits or sets of circuits configured to perform the steps shown in the method figures. The circuits or sets of circuits in this respect may comprise circuits dedicated to performing certain functional processing and / or one or more microprocessors in conjunction with memory. For example, the set of circuits may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.The processing circuitry can be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory may include program instructions to execute one or more telecommunications and / or data communication protocols as well. Petition 870250081883, dated 11 / 09 / 2025, pp. 137 / 236 126 / 183 instructions to execute one or more of the techniques described in this document, in various modes. In modes that employ memory, the memory stores program code that, when executed by one or more processors, performs the techniques described in this document.

[00452] Figure 22, for example, illustrates a communication device 12 as implemented according to one or more embodiments. As shown, the communication device 12 includes the processing circuitry 2210 and the communication circuit 2220. The communication circuitry 2220 (e.g., radio circuitry) is configured to transmit and / or receive information to and / or from one or more other nodes, for example, through any communication technology. Such communication may occur by means of one or more antennas internal or external to the communication device 12. The processing circuitry 2210 is configured to perform the processing described above, for example, in Figures 15, 16, 17 and / or 20, such as by executing instructions stored in memory 2230. The processing circuitry 2210 in this respect may implement certain functional means, units or modules.

[00453] Figure 23 illustrates a network node 14 as implemented according to one or more embodiments. As shown, the network node 14 includes processing circuitry 2310 and communication circuitry 2320. Communication circuitry 2320 is configured to transmit and / or receive information to and / or from one or more other nodes, for example, through any communication technology. Processing circuitry 2310 is configured to perform the processing described above, for example, in Figure 18, Figure 19 and / or Figure 21, such as, for example, executing instructions stored in memory 2330. The processing circuitry Petition 870250081883, dated 11 / 09 / 2025, pages 138 / 236 127 / 183 2310 in this respect may implement certain means, units or functional modules.

[00454] Those skilled in the art will also consider that the embodiments in this document additionally include corresponding computer programs.

[00455] A computer program comprises instructions that, when executed on at least one processor of a device, cause the device to perform any of the respective processing described above. A computer program in this respect may comprise one or more code modules corresponding to the means or units described above.

[00456] The embodiments additionally include a carrier containing such a computer program. This carrier may comprise one of an electronic signal, optical signal, radio signal, or computer-readable storage medium.

[00457] In this respect, the embodiments in this document also include a computer program product stored on a non-transient computer-readable medium (storage or recording) and comprise instructions which, when executed by a device's processor, cause the device to perform as described above.

[00458] The embodiments additionally include a computer program product comprising portions of program code to perform the steps of any of the embodiments in this document, when the computer program product is executed through a computing device. This computer program product may be stored on a computer-readable recording medium.

[00459] Figure 24 shows an example of a 2400 communication system according to some modalities. Petition 870250081883, dated 11 / 09 / 2025, pages 139 / 236 128 / 183

[00460] In the example, the 2400 communication system includes a 2402 telecommunication network which includes an access network 2404, such as a radio access network (RAN), and a 2406 core network, which includes one or more 2408 core network nodes. The 2404 access network includes one or more access network nodes, such as 2410a and 2410b network nodes (one or more of which may be generally referred to as 2410 network nodes) or any other similar 3GPP (3GPP) access nodes or non-3GPP access points. Furthermore, as will be understood by those knowledgeable in the field, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are provided and integrated by a single vendor. Thus, it should be understood that network nodes include disaggregated implementations or parts thereof. For example, in some configurations, the 2402 telecommunications network includes one or more Open-RAN (ORAN) network nodes.An ORAN network node is a node in the 2402 telecommunications network that supports an ORAN specification (for example, a specification published by the ORAN Alliance or any similar organization) and may operate alone or in conjunction with other nodes to implement one or more functionalities of any node in the 2402 telecommunications network, including one or more 2410 network nodes and / or 2408 core network nodes.

[00461] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near real-time or non-real-time) hosting software or software plugins, such as a near real-time control application (e.g., xApp) or a non-real-time control application (e.g., rApp), or any combination thereof (the adjective “open” designates support for an ORAN specification). The network node may support a Petition 870250081883, dated 11 / 09 / 2025, pp. 140 / 236 129 / 183 specification, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Furthermore, an ORAN access node can be a logical node within a physical node. Additionally, an ORAN network node can be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment might include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.The 2410 network nodes facilitate the direct or indirect connection of user equipment (UE), such as by connecting UEs 2412a, 2412b, 2412c, and 2412d (one or more of which may be generally referred to as UEs 2412) to the 2406 core network via one or more wireless connections.

[00462] Exemplary wireless communications via a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Furthermore, in different embodiments, the 2400 communication system may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals via wired or wireless connections. The 2400 communication system may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[00463] UEs 2412 can be any type of a wide variety of communication devices, including wireless devices arranged, configured and / or operational to communicate wirelessly with network nodes. Petition 870250081883, dated 11 / 09 / 2025, pp. 141 / 236 130 / 183 2410 and other communication devices. Similarly, the 2410 network nodes are arranged, capable, configured and / or operable to communicate directly or indirectly with the 2412 UEs and / or with other network nodes or equipment in the 2402 telecommunications network to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the 2402 telecommunications network.

[00464] In the example shown, core network 2406 connects network nodes 2410 to one or more hosts, such as host 2416. These connections can be direct or indirect through one or more intermediate networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 2406 includes one or more core network nodes (e.g., core network node 2408) that are structured with hardware and software components. The characteristics of these components may be substantially similar to those described in relation to UEs, network nodes, and / or hosts, so the descriptions thereof are generally applicable to the corresponding components of core network node 2408.Exemplary core network nodes include functions from one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Service (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Signature Identifier Unveiling Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[00465] Host 2416 may be owned or controlled by a service provider other than an operator or provider of the access network 2404 and / or the telecommunications network 2402 and may be operated by the service provider or on behalf of the service provider. Host 2416 Petition 870250081883, dated 11 / 09 / 2025, pp. 142 / 236 131 / 183 can host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieval and compilation of data under various environmental conditions detected by a plurality of UEs, analytics functionality, social networking, functions to control or otherwise interact with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[00466] As a whole, the 2400 communication system in Figure 24 enables connectivity between UEs, network nodes, and hosts. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other 2G, 3G, 4G, 5G standards or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the 802.11 (WiFi) standards of the Institute of Electrical and Electronics Engineers (IEEE); and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, ZigBee Near Field Communication (NFC), LiFi and / or any low-power wide area network (LPWAN) standard, such as LoRa and Sigfox.

[00467] In some instances, the 2402 telecommunications network is a cellular network that implements standardized 3GPP features. Consequently, the 2402 telecommunications network can support network slicing to provide different logical networks for different devices connected to the 2402 telecommunications network. For example, the 2402 telecommunications network can provide Ultra-Reliable Low Latency Communication (URLLC) services to some UEs, while providing services Petition 870250081883, dated 11 / 09 / 2025, pp. 143 / 236 132 / 183 Enhanced Mobile Wideband (eMBB) to other UEs and / or Massive Machine Type Communication (mMTC) / Massive IoT services to still other UEs.

[00468] In some examples, UEs 2412 are configured to transmit and / or receive information without direct human interaction. For example, a UE may be designed to transmit information to the 2404 access network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the 2404 access network. Additionally, a UE may be configured to operate in single or multiple RAT mode or multiple patterns. For example, a UE may operate with any one or a combination of Wi-Fi, NR (New Radio), and LTE, i.e., it is configured for dual multi-radio connectivity (MR-DC), such as E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[00469] In the example, concentrator 2414 communicates with access network 2404 to facilitate indirect communication between one or more UEs (e.g., UE 2412c and / or 2412d) and network nodes (e.g., network node 2410b). In some examples, concentrator 2414 may be a controller, router, content and analytics source, or any of the other communication devices described in this document in relation to UEs. For example, concentrator 2414 may be a wideband router that allows access to core network 2406 for the UEs. As another example, concentrator 2414 may be a controller that sends commands or instructions to one or more actuators on the UEs. Commands or instructions may be received from UEs, network nodes 2410, or via executable code, script, process, or other instructions on concentrator 2414.As another example, the 2414 concentrator can be a data collector that acts as temporary storage for EU data and, in some configurations, can perform analysis or other processing of the data. For example... Petition 870250081883, dated 11 / 09 / 2025, pp. 144 / 236 133 / 183 In another example, the 2414 concentrator can be a content source. For example, for a UE that is a VR headset, display, speaker, or other media delivery device, the 2414 concentrator can retrieve VR resources, video, audio, or other media or data related to sensory information through a network node, which the 2414 concentrator then provides to the UE directly after performing local processing and / or after adding additional local content. In yet another example, the 2414 concentrator acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low-energy IoT devices.

[00470] The 2414 concentrator can have a constant / persistent or intermittent connection with the 2410b network node. The 2414 concentrator can also allow a different communication scheme and / or schedule between the 2414 concentrator and the UEs (e.g., UE 2412c and / or 2412d) and between the 2414 concentrator and the 2406 core network. In other examples, the 2414 concentrator is connected to the 2406 core network and / or one or more UEs via a wired connection. Additionally, the 2414 concentrator can be configured to connect to an M2M service provider via the 2404 access network and / or to another UE via a direct connection. In some scenarios, the UEs can establish a wireless connection with the 2410 network nodes while still connected through the 2414 concentrator via a wired or wireless connection.In some embodiments, the 2414 concentrator may be a dedicated concentrator—that is, a concentrator whose primary function is to route communications to / from the UEs from / to the 2410b network node. In other embodiments, the 2414 concentrator may be a non-dedicated concentrator—that is, a device that is capable of operating to route communications between the UEs and the 2410b network node, but which is additionally capable of operating as a communication start and / or end point for certain data channels. Petition 870250081883, dated 11 / 09 / 2025, pp. 145 / 236 134 / 183

[00471] Figure 25 shows a UE 2500 according to some embodiments. As used in this document, a UE refers to a device capable, configured, disposed and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, mobile phone, cellular phone, voice over IP (VoIP) phone, wireless local link phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, portable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart device, wireless client premise equipment (CPE), vehicle, vehicle mounted or vehicle embedded / integrated wireless device, etc.Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a Narrowband Internet of Things (NB-IoT) UE, a Machine-Type Communication (MTC) UE, and / or an Enhanced MTC (eMTC) UE.

[00472] A UE can support device-to-device (D2D) communication, for example, through the implementation of a 3GPP standard for side-link communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user, but which cannot or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user, but which can be associated with or operated for the benefit of a user (e.g., Petition 870250081883, dated 11 / 09 / 2025, pp. 146 / 236 135 / 183 a smart energy meter).

[00473] The UE 2500 includes a set of processing circuits 2502 that is operatively coupled via a bus 2504 to an input / output interface 2506, a power supply 2508, a memory 2510, a communication interface 2512 and / or any other component, or any combination thereof. Certain UEs may use all or a subset of the components shown in Figure 25. The level of integration between the components may vary from one UE to another. Additionally, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[00474] The 2502 processing circuitry is configured to process instructions and data and can be configured to implement any operational sequential state machine to execute stored instructions as machine-readable computer programs in memory 2510. The 2502 processing circuitry can be implemented as one or more hardware-implemented state machines (e.g., in distinct logic field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic in conjunction with suitable firmware; one or more stored computer programs, general-purpose processors such as a microprocessor or digital signal processor (DSP), in conjunction with suitable software; or any combination of the foregoing. For example, the 2502 processing circuitry may include multiple central processing units (CPUs).

[00475] In the example, the 2506 input / output interface can be configured to provide an interface to, or interface with, an input device, an output device, or one or more input and / or output devices. Examples of an output device include a high Petition 870250081883, dated 11 / 09 / 2025, pp. 147 / 236 136 / 183 speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. An input device may allow a user to capture information on the UE 2500. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a moving sphere, a directional panel, a touch panel, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to detect user input. A sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.An output device can use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port can be used to provide both an input and an output device.

[00476] In some embodiments, the 2508 power supply is structured as a battery or battery pack. Other types of power supplies, such as an external power supply (e.g., an electricity outlet), photovoltaic device, or energy cell, may be used. The 2508 power supply may additionally include a power circuitry to deliver power from the 2508 power supply itself and / or from an external power supply to various parts of the UE 2500 via the input circuitry or an interface such as a power cable. The power delivery may be, for example, to charge the 2508 power supply. The power circuitry may perform any shaping, conversion, or other modification to the power from the 2508 power supply to make the power suitable. Petition 870250081883, dated 11 / 09 / 2025, pp. 148 / 236 137 / 183 for the respective components of the UE 2500 for which energy is supplied.

[00477] The 2510 memory may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and others. In one example, the 2510 memory includes one or more application programs 2514, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 2516. The 2510 memory may store, for use by the UE 2500, any one of a variety of different operating systems or combinations of operating systems.

[00478] The 2510 memory can be configured to include numerous physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, mini-USB drive, pen drive, key drive, high-density digital versatile disk (HD-DVD), optical disk drive, internal hard disk drive, Blu-ray optical disk drive, holographic digital data storage (HDDS) optical disk drive, external dual mini-DIMM in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory, such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof.The UICC can, for example, be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card". Memory 2510 may allow this. Petition 870250081883, dated 11 / 09 / 2025, pp. 149 / 236 138 / 183 that the UE 2500 access instructions, application programs and the like, stored in transient or non-transient memory media to download data or to load data. A manufacturing article, such as one that utilizes a communication system, may be tangibly incorporated as or in the 2510 memory, which may be or comprise a device-readable storage medium.

[00479] The processing circuitry 2502 can be configured to communicate with an access network or another network using the communication interface 2512. The communication interface 2512 may comprise one or more communication subsystems and may include, or be communicatively coupled to, an antenna 2522. The communication interface 2512 may include one or more transceivers used to communicate, such as through communication with one or more remote transceivers of another wirelessly communicative device (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 2518 and / or a receiver 2520 suitable for providing network communications (e.g., frequency allocations, optical, electrical, and others).Furthermore, the 2518 transmitter and the 2520 receiver can be coupled to one or more antennas (e.g., antenna 2522) and can share circuit components, software, or firmware, or alternatively, be implemented separately.

[00480] In the embodiment illustrated, the communication functions of the 2512 communication interface may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, other similar communication functions, or any combination thereof. The communications may be Petition 870250081883, dated 11 / 09 / 2025, pages 150 / 236 139 / 183 implemented in accordance with one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Network Link (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and others.

[00481] Regardless of the sensor type, a UE can provide an output of data captured by its sensors, through its 2512 communication interface, via a wireless connection to a network node. The data captured by the sensors of a UE can be communicated via a wireless connection to a network node through another UE. The output can be periodic (e.g., once every 15 minutes if it reports the captured temperature), random (e.g., to regulate the reporting load of multiple sensors), in response to a trigger event (e.g., when humidity is detected, an alert is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).

[00482] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the states of the actuator, motor, or switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input, or a robotic arm that performs a medical procedure according to the received input.

[00483] A UE, when in the form of an Internet of Things (IoT) device, may be a device for use in one or more application domains, where those domains comprise, but are not limited to, Petition 870250081883, dated 11 / 09 / 2025, pp. 151 / 236 140 / 183 City wearable technology, extended industrial application and healthcare. Non-limiting examples of such an IoT device are a device that is or is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / humidity sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smartwatch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR),A wearable article for tactile augmentation or sensory enhancement, a water sprinkler, an animal or item tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any type of medical device, such as a heart rate monitor or a remotely controlled surgical robot. A UE in the form of an IoT device comprises a set of circuits and / or software depending on the intended application of the IoT device in addition to other components, as described in relation to the UE 2500 shown in Figure 25.

[00484] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may, in this case, be an M2M device, which may, in a 3GPP context,It can be referred to as an MTC device. As a particular example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent, Petition 870250081883, dated 11 / 09 / 2025, pp. 152 / 236 141 / 183 a vehicle, such as a car, a bus, a truck, a vessel and an aircraft, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[00485] In practice, any number of UEs can be used together in relation to a single use case. For example, a first UE might be integrated into a drone and provide the drone's speed information (obtained via a speed sensor) to a second UE which is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE can adjust the drone's acceleration (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE can also include more than one of the functionalities described above. For example, a UE might understand both the sensor and the actuator and handle data communication for both the speed sensor and the actuators.

[00486] Figure 26 shows a 2600 network node according to some embodiments. As used in this document, a network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, B Nodes, evolved B Nodes (eNBs) and NR B Nodes (gNBs)), ORAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[00487] Base stations can be categorized based on the amount of coverage they provide (or, in other words, their level of transmitted energy) and others, depending on the amount of coverage provided, can be given as femto-base stations, pico-base stations, micro-base stations or macro-base stations. A base station can be Petition 870250081883, dated 11 / 09 / 2025, pp. 153 / 236 142 / 183 a relay node or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an ORAN access node), and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. The parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[00488] Other examples of network nodes include 5G multi-point transmission point (multi-TRP) access nodes, multi-standard radio equipment (MSR) such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multi-cast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Service Mobile Location Centres (E-SMLCs)) and / or Drive Test Minimization (MDTs).

[00489] The network node 2600 includes a set of processing circuits 2602, a memory 2604, a communication interface 2606 and a power supply 2608.The 2600 network node can be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In certain scenarios where the 2600 network node comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may... Petition 870250081883, dated 11 / 09 / 2025, pp. 154 / 236 143 / 183 control multiple NodeBs. In such a scenario, each single NodeB and RNC pair can, in some cases, be considered a single separate network node. In some embodiments, the 2600 network node can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate memory 2604 for different RATs) and some components can be reused (e.g., the same antenna 2610 can be shared by different RATs). The 2600 network node can also include multiple sets of the various components illustrated for different wireless technologies integrated into the 2600 network node, for example, GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or a different chip or set of chips and other components within the 2600 network node.

[00490] The 2602 processing circuitry may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, feature, or combination of operable hardware, software, and / or coded logic to provide, individually or in conjunction with other 2600 network node components, such as 2604 memory, 2600 network node functionality.

[00491] In some embodiments, the processing circuitry 2602 includes a system-on-a-chip (SOC). In some embodiments, the processing circuitry 2602 includes one or more of the radio frequency (RF) transceiver circuitry 2612 and the baseband processing circuitry 2614. In some embodiments, the radio frequency (RF) transceiver circuitry Petition 870250081883, dated 11 / 09 / 2025, pp. 155 / 236 144 / 183 The 2612 and the 2614 baseband processing circuitry may be on separate chips (or chip sets), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the 2612 RF transceiver circuitry and the 2614 baseband processing circuitry may be on the same chip or chip set, board, or unit.

[00492] The 2604 memory may comprise any form of computer-readable volatile or non-volatile memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a flash drive, a Compact Disc (CD) or a Digital Video Disc (DVD)) and / or any other volatile or non-volatile, device-readable, non-transient and / or computer-executable memory device that stores information, data and / or instructions that can be used by the 2602 processing circuitry.Memory 2604 can store any suitable instruction, data, or information that includes a computer program, software, or application containing one or more logic, rules, codes, tables, and / or other instructions capable of being executed by the processing circuitry 2602 and used by the network node 2600. Memory 2604 can be used to store any calculation performed by the processing circuitry 2602 and / or any data received through the communication interface 2606. In some embodiments, the processing circuitry 2602 and memory 2604 are integrated.

[00493] The 2606 communication interface is used in wired or wireless signaling and / or data communication between a network node, network of Petition 870250081883, dated 11 / 09 / 2025, pp. 156 / 236 145 / 183 access and / or EU. As illustrated, the communication interface 2606 comprises port(s) / terminal(s) 2616 for sending and receiving data, for example, to and from a network via a wired connection. The communication interface 2606 also includes a radio front-end circuit assembly 2618 that can be coupled to, or in certain embodiments, a part of, the antenna 2610. The radio front-end circuit assembly 2618 comprises filters 2620 and amplifiers 2622. The radio front-end circuit assembly 2618 can be connected to an antenna 2610 and to the processing circuit assembly 2602. The radio front-end circuit assembly can be configured to condition signals communicated between the antenna 2610 and the processing circuit assembly 2602.The radio front-end circuit assembly 2618 can receive digital data that must be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit assembly 2618 can convert the digital data into a radio signal that has the appropriate channel and bandwidth parameters using a combination of filters 2620 and / or amplifiers 2622. The radio signal can then be transmitted through antenna 2610. Similarly, upon receiving data, antenna 2610 can collect radio signals that are then converted into digital data by the radio front-end circuit assembly 2618. The digital data can be passed to the processing circuit assembly 2602. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[00494] In certain alternative embodiments, the network node 2600 does not include a separate radio front-end circuitry 2618; instead, the processing circuitry 2602 includes a radio front-end circuitry and is connected to the antenna 2610. Similarly, in some embodiments, all or part of the circuitry is included. Petition 870250081883, dated 11 / 09 / 2025, pp. 157 / 236 146 / 183 RF transceiver circuits 2612 are part of communication interface 2606. In still other embodiments, communication interface 2606 includes one or more ports or terminals 2616, the radio front-end circuit assembly 2618 and the RF transceiver circuit assembly 2612, as part of a radio unit (not shown), and communication interface 2606 communicates with baseband processing circuit assembly 2614, which is part of a digital unit (not shown).

[00495] Antenna 2610 may include one or more antennas or antenna arrays, configured to send and / or receive wireless signals. Antenna 2610 may be coupled to the radio front-end circuitry assembly 2618 and may be any type of antenna capable of transmitting and receiving wireless data and / or signals. In certain embodiments, antenna 2610 is separate from network node 2600 and is connectable to network node 2600 via an interface or port.

[00496] Antenna 2610, communication interface 2606 and / or processing circuitry 2602 can be configured to perform any reception operations and / or certain acquisition operations described herein as being performed by the network node. Any information, data and / or signals can be received from a UE, another network node and / or any other network equipment. Similarly, antenna 2610, communication interface 2606 and / or processing circuitry 2602 can be configured to perform any transmission operations described herein as being performed by the network node. Any information, data and / or signals can be transmitted to a UE, another network node and / or any other network equipment.

[00497] The 2608 power supply provides power to the various components of the 2600 network node in a form suitable for the respective components (e.g., at a voltage and current level required for Petition 870250081883, dated 11 / 09 / 2025, pp. 158 / 236 147 / 183 each respective component). The 2608 power supply may additionally comprise, or be coupled to, the power management circuitry to supply the 2600 network node components with power to perform the functionality described herein. For example, the 2600 network node may be connectable to an external power supply (e.g., a power grid, a power outlet) via an input circuitry or interface such as a power cable, wherein the external power supply provides power to the power circuitry of the 2608 power supply. As a further example, the 2608 power supply may comprise a power supply in the form of a battery or battery pack that is connected to, or integrated into, the power circuitry. The battery may provide backup power should the external power supply fail.

[00498] Network node 2600 embodiments may include additional components beyond those shown in Figure 26 to provide certain aspects of network node functionality, including any of the functionalities described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 2600 may include user interface equipment to allow input of information into network node 2600 and to allow output of information from network node 2600. This may allow a user to perform diagnostics, maintenance, repair, and other administrative functions for network node 2600.

[00499] Figure 27 is a block diagram of a 2700 host, which may be an embodiment of the 2416 host of Figure 24, according to various aspects described in this document. As used in this document, the 2700 host may be or comprise various combinations of hardware and / or software, including a single server, a blade server, a cloud-deployed server, a server Petition 870250081883, dated 11 / 09 / 2025, pp. 159 / 236 148 / 183 distributed, a virtual machine, container, or processing resources on a server farm. The 2700 host can provide one or more services to one or more UEs.

[00500] The host 2700 includes a set of processing circuits 2702 that are operatively coupled via a bus 2704 to an input / output interface 2706, a network interface 2708, a power supply 2710, and a memory 2712. Other components may be included in other embodiments. The characteristics of these components may be substantially similar to those described in relation to the devices in the preceding figures, such as Figures 25 and 26, so that the descriptions thereof are generally applicable to the corresponding components of host 2700.

[00501] Memory 2712 may include one or more computer programs which include one or more host application programs 2714 and data 2716, which may include user data, for example, data generated by a UE for host 2700 or data generated by host 2700 for a UE. Host 2700 embodiments may use only a subset or all of the components shown. Host application programs 2714 can be implemented in a container-based architecture and can provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, head-mounted display systems).Host application programs 2714 can also provide for user authentication and license checks and can periodically report on health, routes, and content availability. Petition 870250081883, dated 11 / 09 / 2025, pp. 160 / 236 149 / 183 a central node, such as a device at or on the edge of a core network. Consequently, host 2700 can select and / or specify a different host for over-the-top services for a UE. Host application programs 2714 can support various protocols such as HTTP Live Streaming Protocol (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Broadcast Protocol (RTSP), Dynamic Adaptive Broadcast over HTTP (MPEGDASH), etc.

[00502] Figure 28 is a block diagram illustrating a 2800 virtualization environment in which the functions implemented by some modalities can be virtualized. In the present context, virtualization means creating virtual versions of appliances or devices that may include the virtualization of hardware platforms, storage devices, and network connection resources. As used in this document, virtualization can be applied to any device described herein or components thereof, and refers to an implementation in which at least a portion of the functionality is implemented as one or more virtual components.Some or all of the functions described in this document can be implemented as virtual components running on one or more virtual machines (VMs) deployed in one or more 2800 virtual environments hosted by one or more hardware nodes, such as a hardware computing device operating as a network node, UE, core network node, or host. Additionally, in embodiments where the virtual node does not require radio connectivity (e.g., a core network node or host), then the node can be fully virtualized. In some embodiments, the 2800 virtualization environment includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Orchestration and Management Framework via an O-2 interface. Petition 870250081883, dated 11 / 09 / 2025, pp. 161 / 236 150 / 183

[00503] 2802 applications (which may alternatively be referred to as software cases, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) run in the Q400 virtualization environment to implement some features, functions and / or benefits of some of the modalities described in this document.

[00504] 2804 hardware includes the processing circuitry, memory that stores software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices, as described herein, such as a network interface, input / output interface, and others. The software may be executed by the processing circuitry to instantiate one or more 2806 virtualization layers (also referred to as hypervisors or virtual machine monitors (VMMs)), provide 2808a and 2808b VMs (one or more of which may be generally referred to as 2808 VMs), and / or perform any of the functions, features, and / or benefits described in relation to some embodiments described herein. The 2806 virtualization layer may present a virtual operating platform that appears as network-linking hardware to the 2808 VMs.

[00505] VMs 2808 comprise virtual processing, virtual memory, virtual network link or interface, and virtual storage, and may be executed by a corresponding virtualization layer 2806. Different embodiments of a virtual appliance case 2802 may be implemented in one or more of the VMs 2808, and the implementations may be done in different ways. Hardware virtualization is, in some contexts, referred to as network function virtualization (NFV). NFV can be used to consolidate many types of network equipment into high-volume, industry-standard server hardware, physical switches, and physical storage, which may be located in data centers and customer premises equipment. Petition 870250081883, dated 11 / 09 / 2025, pp. 162 / 236 151 / 183

[00506] In the context of NFV, a 2808 VM can be a software implementation of a physical machine that runs programs as if they were running on a non-virtualized physical machine. Each of the 2808 VMs and the 2804 hardware component that runs that VM, being dedicated by hardware to that VM and / or shared by hardware by that VM with other VMs, form separate virtual network elements. Also in the context of NFV, a virtual network function is responsible for handling specific network functions that are executed by one or more 2808 VMs on top of the 2804 hardware and correspond to the 2802 application.

[00507] 2804 hardware can be implemented in an individual network node with generic or specific components. 2804 hardware can implement some functions through virtualization. Alternatively, 2804 hardware can be part of a larger hardware cluster (e.g., as in a data center or CPE) where many hardware nodes work together and are managed through 2810 management and orchestration, which, among other things, oversees the application lifecycle management 2802. In some embodiments, 2804 hardware is coupled with one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas.Radio units can communicate directly with other hardware nodes through one or more suitable network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling may be provided using a 2812 control system that can alternatively be used for communication between hardware nodes and radio units.

[00508] Figure 29 shows a communication diagram of a Petition 870250081883, dated 11 / 09 / 2025, pages 163 / 236 152 / 183 host 2902 communicating via a network node 2904 with a UE 2906 by a partially wireless connection according to some embodiments. Exemplary implementations, according to various embodiments, of the UE (such as a UE 2412a in Figure 24 and / or UE 2500 in Figure 25), network node (such as network node 2410a in Figure 24 and / or network node 2600 in Figure 26) and host (such as host 2416 in Figure 24 and / or host 2700 in Figure 27) discussed in the preceding paragraphs will be described with reference to Figure 29.

[00509] Like the 2700 host, the 2902 host modalities include hardware, such as a communication interface, processing circuitry, and memory. The 2902 host also includes software, which is stored or accessible by the 2902 host and executable by the processing circuitry. The software includes a host application that can be operational to provide a service to a remote user, such as the UE 2906 connecting via the over-the-top (OTT) 2950 connection that extends between the UE 2906 and the 2902 host. In providing the service to the remote user, a host application can provide user data that is transmitted using the OTT 2950 connection.

[00510] Network node 2904 includes hardware that allows it to communicate with host 2902 and UE 2906. The 2960 connection can be direct or pass through a core network (such as core network 2406 in Figure 24) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a main chain network or the Internet.

[00511] The UE 2906 includes hardware and software, which is stored on or accessible by the UE 2906 and executable through the UE's processing circuitry. The software includes a client application, such as a web browser or operator-specific "app," that can be operated to provide a service to a human or non-human user through the UE. Petition 870250081883, dated 11 / 09 / 2025, pp. 164 / 236 153 / 183 2906 with support from host 2902. On host 2902, a running host application can communicate with a running client application via the OTT 2950 connection that terminates on UE 2906 and host 2902. When providing service to the user, the UE client application can receive request data from the host application and provide user data in response to the request data. The OTT 2950 connection can transfer both request data and user data. The UE client application can interact with the user to generate the user data provided to the host application via the OTT 2950 connection.

[00512] The OTT 2950 connection can be extended via the 2960 connection between host 2902 and network node 2904 and via a wireless 2970 connection between network node 2904 and UE 2906 to provide the connection between host 2902 and UE 2906.Connection 2960 and wireless connection 2970, through which OTT connection 2950 can be provided, were abstractly designed to illustrate communication between host 2902 and UE 2906 via network node 2904, without explicit reference to any intermediate device and the precise routing of messages through those devices.

[00513] As an example of data transmission via the OTT 2950 connection, in step 2908, host 2902 provides user data, which can be accomplished through the execution of a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 2906. In other embodiments, the user data is associated with a UE 2906 that shares data with host 2902 without explicit human interaction. In step 2910, host 2902 initiates a transmission that carries the user data towards UE 2906. Host 2902 can initiate the transmission in response to a request transmitted by UE 2906. The request can be caused by human interaction with UE 2906 or through Petition 870250081883, dated 11 / 09 / 2025, pp. 165 / 236 154 / 183 of the client application operation running on UE 2906. The transmission can pass through network node 2904 according to the teachings of the modalities described throughout this description. Consequently, in step 2912, network node 2904 transmits to UE 2906 the user data that was executed in the transmission that host 2902 initiated, according to the teachings of the modalities described throughout this description. In step 2914, UE 2906 receives the user data transported in the transmission, which can be performed through the client application running on UE 2906 associated with the host application running on host 2902.

[00514] In some instances, UE 2906 runs a client application that provides user data to host 2902. The user data may be provided in reaction to or in response to data received from host 2902. Consequently, in step 2916, UE 2906 may provide user data, which may be accomplished by running the client application. When providing user data, the client application may additionally consider user input received from the user through an input / output interface of the UE 2906. Regardless of the specific way in which the user data was provided, the UE 2906 initiates, in step 2918, the transmission of user data towards host 2902 through network node 2904. In step 2920, according to the teachings of the embodiments described throughout this description, network node 2904 receives user data from the UE 2906 and initiates the transmission of the received user data towards host 2902.In step 2922, host 2902 receives the user data transported in the transmission initiated by UE 2906.

[00515] One or more of the various modalities enhance the performance of OTT services provided to UE 2906 with the use of OTT connection 2950, ​​in which wireless connection 2970 forms the last segment. Petition 870250081883, dated 11 / 09 / 2025, pages 166 / 236 155 / 183

[00516] In an illustrative scenario, factory state information can be collected and analyzed by host 2902. As another example, host 2902 can process audio and video data that can be retrieved from a UE for use in map creation. As another example, host 2902 can collect and analyze real-time data to assist in vehicle congestion control (e.g., traffic light control). As another example, host 2902 can store surveillance video uploaded by a UE. As another example, host 2902 can store or control access to media content such as video, audio, VR, or AR, which can be broadcast, multi-broadcast, or uni-broadcast to UEs.Like other examples, the 2902 host can be used for energy pricing determination, remote control of critical electrical load without time to balance energy generation needs, location services, presentation services (such as compiling diagrams, etc., from data collected from remote devices), or any other data collection, retrieval, storage, analysis, and / or transmission function.

[00517] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors in which one or more modes are enhanced. There may additionally be optional network functionality to reconfigure the OTT 2950 connection between the host 2902 and the UE 2906 in response to variations in measurement results. The measurement procedure and / or the network functionality to reconfigure the OTT connection may be implemented in software and hardware of the host 2902 and / or UE 2906. In some embodiments, sensors (not shown) may be deployed on or in association with other communication devices through which the OTT 2950 connection passes; the sensors may participate in the measurement procedure by providing values ​​of the monitored quantities. Petition 870250081883, dated 11 / 09 / 2025, pp. 167 / 236 156 / 183 exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT 2950 connection may include message format, transmission adjustments, preferred routing, etc.; reconfiguration does not need to directly alter the operation of the network node 2904. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 2902. Measurements may be implemented by the software causing messages to be transmitted, in particular, empty or “artificial” messages, using the OTT 2950 connection while monitoring propagation times, errors, etc.

[00518] Although the computing devices described in this document (e.g., UEs, network nodes, hosts) may include the combination of hardware components illustrated, other embodiments may comprise computing devices with different combinations of components. It should be understood that these computing devices may comprise any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods described in this document.Determination, calculation, acquisition, or similar operations described in this document can be performed through the set of processing circuits, which can process information by, for example, converting the obtained information into other information, comparing the information or converted information with information stored in the network node, and / or performing one or more operations based on the obtained or converted information and, as a result of said processing, making a determination. Furthermore, although the components are graphically represented as boxes... Petition 870250081883, dated 11 / 09 / 2025, pages 168 / 236 157 / 183 unique devices located within a larger box or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that constitute a single illustrated component, and functionality may be divided among separate components. For example, a communication interface may be configured to include any of the components described in this document, and / or the functionality of the components may be divided between the processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[00519] In certain embodiments, some or all of the functionality described herein may be provided by the processing circuitry executing instructions stored in memory, wherein certain embodiments may be a computer program product in the form of a non-transient computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored in a separate or distinct device-readable storage medium, such as in a non-adjustable manner. In either of these particular embodiments, whether executing instructions stored in a non-transient or non-transient computer-readable storage medium, the processing circuitry may be configured to perform the described functionality.The benefits provided by such functionality are not limited to the processing circuitry or other components of the computing device, but are leveraged by the computing device as a whole and / or by end users and a wireless network in general. Petition 870250081883, dated 11 / 09 / 2025, pp. 169 / 236 158 / 183

[00520] Some of the modalities described in this document can be listed as follows: Group A Modalities

[00521] A1. A method implemented by a communication device, the method comprising: To receive, from a network node in a communication network, a conditional reconfiguration that indicates: a configuration of a candidate target cell; There is a first condition that the communication device must evaluate to determine whether to apply the configuration when the communication device is not configured with a Primary and Secondary Cell Group server, SCG, Cell, PSCell; and a second condition that the communication device must evaluate to determine whether to apply the configuration when the communication device is configured with a PSCell server.

[00522] A2. The A1 modality method, wherein the communication device must evaluate the first condition when the communication device is not configured with a server PSCell, to determine whether to apply the configuration to add the candidate target cell as a server PSCell, and wherein the communication device must evaluate the second condition when the communication device is configured with a server PSCell, to determine whether to apply the configuration to change a server PSCell from a source cell to the candidate target cell.

[00523] A3. The method of any of the A1-A2 modalities, in which the conditional reconfiguration includes an execution condition field that indicates the first and second conditions.

[00524] A4. The method of modality A3, in which the execution condition field identifies a measurement configuration, in which the Petition 870250081883, dated 11 / 09 / 2025, pp. 170 / 236 159 / 183 measurement configuration is associated with a reporting configuration, where the reporting configuration indicates the first and second conditions.

[00525] A5. The A4 mode method, in which the reporting configuration indicates an event whose occurrence is to trigger the communication device to apply the configuration, where the event is defined to occur: when the first condition is met while the communication device is not configured with a server PSCell; and when the second condition is met while the communication device is configured with a server PSCell.

[00526] A6. The method of mode A5, wherein: The first condition is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements performed on a server PSCell; and the second condition is a function of both the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00527] A7. The method of any of the modalities A5-A6, in which the event is defined to occur when an input condition is met and an output condition is not met, where: The input condition is defined as satisfied: when a first subcondition is met while the communication device is not configured with a server PSCell; and when both the first subcondition and a second subcondition are met while the communication device is configured with a server PSCell; and the exit condition is set to satisfied: Petition 870250081883, dated 11 / 09 / 2025, pp. 171 / 236 160 / 183 when a third subcondition is met, as long as the communication device is not configured with a PSCell server; and when the third subcondition or a fourth subcondition is met, as long as the communication device is configured with a PSCell server; where the first condition is met when the first subcondition is met and the third subcondition is not met, as long as the communication device is not configured with a PSCell server; where the second condition is met when the first and second subconditions are met, and neither the third nor the fourth subcondition is met, as long as the communication device is configured with a PSCell server.

[00528] A8. The method of any of the A5-A7 modalities, wherein the event is an A5 Event, an A4 Event, an A5-CPAC Event or an A4-CPAC Event.

[00529] A9. The method of any of the A5-A6 modalities, in which the event is defined to occur when an input condition is met and an output condition is not met, where: The input condition is defined as satisfied: when a first subcondition is met, while the communication device is not configured with a PSCell server; and when a second subcondition is met, while the communication device is configured with a PSCell server; and the exit condition is set to satisfied: when a third subcondition is met, while the communication device is not configured with a PSCell Petition 870250081883, dated 11 / 09 / 2025, pp. 172 / 236 161 / 183 server; and when a fourth subcondition is met, while the communication device is configured with a PSCell server; where the first condition is met when the first subcondition is met and the third subcondition is not met, as long as the communication device is not configured with a server PSCell; where the second condition is met when the second subcondition is met and the fourth subcondition is not met, while the communication device is configured with a PSCell server.

[00530] A10. The method of any of the A5-A7 and modalities A9, where the event is an A3 Event or an A3-CPAC Event.

[00531] A11. The A4 modality method, in which the reporting configuration indicates the first and second events whose occurrence is to trigger the communication device to apply the configuration, while the communication device is and is not configured with a PSCell server, respectively, where the first condition is met when the first event occurs and the second condition is met when the second event occurs.

[00532] A12. The method of modality A3, in which the execution condition field identifies a measurement configuration, in which the measurement configuration is associated with the first and second reporting configurations, in which the first reporting configuration indicates the first condition and the second reporting configuration indicates the second condition.

[00533] A13. The A12 modality method, in which the first reporting configuration indicates a first event whose occurrence triggers the communication device to apply the configuration, where the first event is defined to occur when the first condition is met, while the communication device is not configured with a PSCell. Petition 870250081883, dated 11 / 09 / 2025, pp. 173 / 236 162 / 183 server, where the second reporting configuration indicates a second event whose occurrence triggers the communication device to apply the configuration, where the second event is defined to occur when the second condition is met, while the communication device is configured with a PSCell server.

[00534] A14. The A13 modality method, in which the first and second report configurations have the same report configuration identifier.

[00535] A15. The method of modality A3, in which the execution condition field identifies the first and second measurement configurations, in which the first measurement configuration is associated with a first reporting configuration and in which the second measurement configuration is associated with a second reporting configuration, in which the first reporting configuration indicates the first condition and the second reporting configuration indicates the second condition.

[00536] A16. The A15 modality method, wherein the first reporting configuration indicates a first event whose occurrence is to trigger the communication device to apply the configuration, wherein the first event is defined to occur when the first condition is met, while the communication device is not configured with a server PSCell, wherein the second reporting configuration indicates a second event whose occurrence is to trigger the communication device to apply the configuration, wherein the second event is defined to occur when the second condition is met, while the communication device is configured with a server PSCell.

[00537] A17. The method of any of the A15-A16 modes, where the first and second measurement configurations have the same measurement configuration identifier.

[00538] A18. The method of modality A3, in which the field of Petition 870250081883, dated 11 / 09 / 2025, pp. 174 / 236 163 / 183 execution condition identifies the first and second measurement configurations, where the first measurement configuration is associated with a first reporting configuration and the second measurement configuration is associated with a second reporting configuration, where the first reporting configuration indicates the first condition and the second reporting configuration indicates the second condition.

[00539] A19. The method of the A18 modality, in which the first and second measurement configurations have different measurement configuration identifiers.

[00540] A20. The method of modality A3, wherein the execution condition field identifies the first and second sets of measurement configuration, wherein the first set of measurement configuration includes one or more first measurement configurations that are respectively associated with one or more first reporting configurations and wherein the second set of measurement configuration includes one or more second measurement configurations that are respectively associated with one or more second reporting configurations, wherein the one or more first reporting configurations indicate the first condition and the one or more second reporting configurations indicate the second condition.

[00541] A21. The method of any of the A1-A2 modalities, in which the conditional reconfiguration includes first and second execution condition fields that indicate the first and second conditions respectively.

[00542] A22. The method of modality A21, in which the first and second execution condition fields identify the first and second measurement configurations, respectively, in which the first and second measurement configurations are respectively associated with the first and second reporting configurations, in which the first and second Petition 870250081883, dated 11 / 09 / 2025, pp. 175 / 236 164 / 183 report settings indicate, respectively, the first and second conditions.

[00543] A23. The A22 modality method, wherein the first reporting configuration indicates a first event whose occurrence is to trigger the communication device to apply the configuration, wherein the first event is defined to occur when the first condition is met, while the communication device is not configured with a server PSCell, wherein the second reporting configuration indicates a second event whose occurrence is to trigger the communication device to apply the configuration, wherein the second event is defined to occur when the second condition is met, while the communication device is configured with a server PSCell.

[00544] A24. The method of any of the embodiments A1-A23, wherein the first condition is a function of the results of one or more measurements performed on the candidate target cell and is not a function of the results of any measurements performed on a server PSCell, and wherein the second condition is a function of the results of one or more measurements performed on the candidate target cell and the results of one or more measurements performed on a server PSCell.

[00545] A25. The method of any of the A1-A24 modalities, where the conditional reconfiguration corresponds to a conditional PSCell addition configuration when the communication device is not configured with a server PSCell and corresponds to a conditional PSCell change configuration when the communication device is configured with a server PSCell.

[00546] A26. The method of any of the A1-A25 modalities, in which the conditional reconfiguration is reusable for adding or changing PSCell.

[00547] A27. The method of any of the modalities A1-A26, Petition 870250081883, dated 11 / 09 / 2025, pp. 176 / 236 165 / 183 additionally includes: To determine whether or not the communication device is configured with a PSCell server; and based on that determination, to evaluate the first or second condition to determine if the configuration should be applied.

[00548] A28. The method of the A27 modality, which additionally comprises responding to the determination to apply the configuration, applying the configuration

[00549] A29. The A28 modality method, in which the configuration application comprises adding the candidate target cell as a server PSCell or changing a server PSCell from a source cell to the candidate target cell, depending on whether or not the communication device is configured with a server PSCell.

[00550] A30. The method of any of the A1-A29 modalities, additionally comprising, after applying the configuration for adding PSCell, reusing the configuration for changing PSCell.

[00551] A31. The method of any of the A1-A30 modalities additionally comprises: Evaluate the first condition when the communication device is not configured with a server PSCell, to determine whether to apply the configuration to add the candidate target cell as a server PSCell; and / or evaluate the second condition when the communication device is configured with a server PSCell, to determine whether to apply the configuration to change a server PSCell from a source cell to the candidate target cell.

[00552] AA1. A method implemented by a communication device, the method comprising: to receive, from a network node in a communication network, a Petition 870250081883, dated 11 / 09 / 2025, pp. 177 / 236 166 / 183 conditional reconfiguration that indicates a configuration of a candidate target cell and a condition under which the communication device must apply the configuration; and after receiving the conditional reconfiguration, receive, from the network node, signaling that changes the condition under which the communication device must apply the configuration.

[00553] AA2. The method of modality AA1, additionally comprising: Before receiving the signal, detect whether the condition is met and apply the configuration to add the candidate target cell as a server PSCell; where the signaling is received after applying the configuration to add the candidate target cell as a server PSCell, via reception.

[00554] AA3. The AA2 modality method, further comprising, after receiving the signal, detecting the fulfillment of the altered condition and applying the configuration to change a server PSCell from a source cell to the candidate target cell.

[00555] AA4. The method of any of the AA1-AA3 modalities, in which the conditional reconfiguration includes an execution condition field whose value indicates the condition, in which the signaling alters the condition by indicating an altered value for the execution condition field.

[00556] AA5. The method of any of the AA1-AA3 modalities, wherein the conditional reconfiguration includes an execution condition field, wherein the execution condition field identifies a measurement configuration that indicates the condition, wherein the signaling alters the condition indicating a different measurement configuration for the conditional reconfiguration.

[00557] AAA1. A method performed by a device of Petition 870250081883, dated 11 / 09 / 2025, pp. 178 / 236 167 / 183 communication, the method comprising: To receive, from a network node in a communication network, a conditional reconfiguration that includes a configuration of a candidate target cell; To determine whether or not the communication device is configured with a Primary and Secondary Cell Group server, SCG, Cell, PSCell; Based on whether or not the communication device is configured with a server PSCell, apply the configuration to add the candidate target cell as a server PSCell or to change a server PSCell from a source cell to the candidate target cell.

[00558] AAA2. The AAA1 modality method, additionally comprising determining which condition to evaluate in...

Claims

1. Method performed by a user equipment, UE, (12) to reuse a conditional reconfiguration (40) both for the conditional addition of a primary cell of a group of secondary cells, PSCell, in multiconnectivity operation and for the conditional alteration of a PSCell in multiconnectivity operation, characterized in that the method comprises: receiving (2000) conditional reconfigurations (40) for the respective target candidate cells of PSCell, wherein the conditional reconfigurations (40) are conditional configurations of PSCell addition, CPA, or conditional configurations of PSCell alteration, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40);and a PSCell target candidate configuration (44) that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; wherein each of at least one of the conditional reconfigurations (40) also includes information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each or more of the other conditional reconfigurations (40).; 2. Method according to claim 1, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to add a second execution condition to each or more of the other conditional reconfigurations (40). Petition 870250081883, dated 11 / 09 / 2025, pp. 196 / 236 2 / 13 3. Method according to claim 2, characterized in that the conditional reconfigurations (40) are CPA configurations, and in that the information (46) in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to add a second execution condition to each or more other conditional reconfigurations (40) in order to configure the other conditional reconfiguration (40) to be reusable as a CPC configuration.

4. Method according to claim 3, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after executing the conditional reconfiguration (40) towards the candidate target cell of the conditional reconfiguration (40), adding a second execution condition to each or more other conditional reconfigurations (40) to configure the other conditional reconfiguration (40) to be reusable as a CPC configuration that is based on the candidate target cell of the conditional configuration being a server PSCell for the UE (12).

5. Method according to any one of claims 2 to 4, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added: the first execution condition (42) needs to be met to trigger the execution of the conditional reconfiguration (40) when the UE (12) is not configured with any server PSCell configuration or with any secondary cell group, SCG; and the second execution condition (42) needs to be met to trigger the execution of the conditional reconfiguration (40) when the UE (12) is configured with a server PSCell configuration or with an SCG. Petition 870250081883, dated 11 / 09 / 2025, p. 197 / 236 3 / 13 6. Method according to any one of claims 2 to 5, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added: the first execution condition (42) is associated with the conditional event A4; and the second execution condition (42) is associated with the conditional event A3 or the conditional event A5.

7. Method according to any one of claims 2 to 6, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) comprises the second execution condition to be added to each of one or more other conditional reconfigurations (40).

8. Method according to any one of claims 2 to 7, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added, the second execution condition is added in an information element condExecutionCondSCG of the conditional reconfiguration (40).

9. Method according to any one of claims 1 to 8, characterized in that, for each of the conditional reconfigurations (40), the first execution condition is included in a condExecutionCond information element of the conditional reconfiguration (40).

10. Method according to any one of claims 1 to 9, characterized in that receiving the conditional reconfigurations (40) comprises receiving the conditional reconfigurations (40) when the UE (12) is not configured with any PSCell server configuration or with any SCG. Petition 870250081883, dated 11 / 09 / 2025, pp. 198 / 236 4 / 13 11. Method according to claim 1, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of each or more of the other conditional reconfigurations (40) to change the other conditional reconfiguration (40) from a CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration.

12. Method according to any one of claims 1 to 11, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is included in the conditional reconfiguration (40) outside the PSCell target candidate configuration (44) of the conditional reconfiguration (40).

13. Method according to any one of claims 1 to 12, characterized in that receiving the conditional reconfigurations (40) comprises receiving one or more radio resource control reconfiguration messages, RRC, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more of the conditional reconfigurations (40).

14. Method according to any one of claims 1 to 13, characterized in that it further comprises: detecting (2010) the fulfillment of the execution condition (42) included in a first conditional reconfiguration (40) among said conditional reconfigurations (40); executing (2020) the first conditional reconfiguration (40) based on said detection; and when executing the first conditional reconfiguration (40), (2030) updating the first execution condition (42) of, or adding a second execution condition to each or more of the other conditional reconfigurations (40) in accordance with the information (46) included in the first conditional reconfiguration (40) on how to execute said update or addition.

15. Method according to claim 14, characterized in that said update or addition comprises adding a second execution condition to each of the other conditional reconfigurations (40) according to the information (46) included in the first conditional reconfiguration (40) on how to perform said update or addition, and in that the method further comprises, after said addition: for each of the one or more other conditional reconfigurations (40) to which a second execution condition is added, determining whether the conditional reconfiguration (40) should be executed by evaluating whether the second execution condition is met; receiving a message that configures a release of a UE(12) PSCell configuration;and after receiving the message, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added, determine whether to execute the conditional reconfiguration (40) by evaluating whether the first execution condition (42) is met.; 16. Method implemented by a network node (14) in a communication network (10) to allow a user device, UE, (12) to reuse a conditional reconfiguration (40) both for conditional addition of a primary cell of a group of secondary cells, PSCell, in multiconnectivity operation and for conditional alteration of a PSCell in multiconnectivity operation, characterized in that the method comprises: transmitting, to the UE (12), conditional reconfigurations (40) Petition 870250081883, of 11 / 09 / 2025, p.200 / 236 6 / 13 for the respective PSCell target candidate cells, wherein the conditional reconfigurations (40) are PSCell add conditional configurations, CPA, or PSCell change conditional configurations, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40); and a PSCell target candidate configuration (44) that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; wherein each of at least one of the conditional reconfigurations (40) also includes information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each or more other conditional reconfigurations (40).

17. Method according to claim 16, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to add a second execution condition to each or more of the other conditional reconfigurations (40).

18. Method according to claim 17, characterized in that the conditional reconfigurations (40) are CPA configurations, and in that the information (46) in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to add a second execution condition to each or more of the other conditional reconfigurations (40) to configure the other conditional reconfiguration (40) to be reusable as a CPC configuration. Petition 870250081883, dated 11 / 09 / 2025, pp. 201 / 236 7 / 13 19. Method according to claim 18, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after executing the conditional reconfiguration (40) towards the target candidate PSCell cell of the conditional reconfiguration (40), adding a second execution condition to each or more of the other conditional reconfigurations (40) to configure the other conditional reconfiguration (40) to be reusable as a CPC configuration that is based on the target candidate PSCell cell of the conditional configuration being a server PSCell for the UE (12).

20. Method according to any one of claims 17 to 19, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added: the first execution condition (42) needs to be met to trigger the execution of the conditional reconfiguration (40) when the UE (12) is not configured with any server PSCell configuration or with any secondary cell group, SCG; and the second execution condition (42) needs to be met to trigger the execution of the conditional reconfiguration (40) when the UE (12) is configured with a server PSCell configuration or with an SCG.

21. Method according to any one of claims 17 to 20, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added: the first execution condition (42) is associated with conditional event A4; and the second execution condition (42) is associated with conditional event A3 or conditional event A5. Petition 870250081883, dated 11 / 09 / 2025, p. 202 / 236 8 / 13 22. Method according to any one of claims 17 to 21, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) comprises the second execution condition to be added to each of one or more other conditional reconfigurations (40).

23. Method according to any one of claims 17 to 22, characterized in that, for each of one or more other conditional reconfigurations (40) to which a second execution condition is added, the second execution condition is added in a condExecutionCondSCG information element of the conditional reconfiguration (40).

24. Method according to any one of claims 16 to 23, characterized in that, for each of the conditional reconfigurations (40), the first execution condition is included in a condExecutionCond information element of the conditional reconfiguration (40).

25. Method according to any one of claims 16 to 24, characterized in that transmitting the conditional reconfigurations (40) comprises transmitting the conditional reconfigurations (40) when the UE (12) is not configured with any PSCell server configuration or with any SCG.

26. Method according to claim 16, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of each or more of the other conditional reconfigurations (40) to change the other conditional reconfiguration (40) from a CPA configuration to a CPC configuration or from a CPC configuration to a CPA configuration. Petition 870250081883, dated 11 / 09 / 2025, pp. 203 / 236 9 / 13 27. Method according to any one of claims 16 to 26, characterized in that the information (46) included in each of at least one of the conditional reconfigurations (40) is included in the conditional reconfiguration (40) outside the PSCell target candidate configuration (44) of the conditional reconfiguration (40).

28. Method according to any one of claims 16 to 27, characterized in that transmitting the conditional reconfigurations (40) comprises transmitting one or more radio resource control reconfiguration messages, RRC, wherein each RRC reconfiguration message includes a condReconfigToAddModList information element comprising a list of one or more of the conditional reconfigurations (40).

29. User equipment, UE, (12) configured to reuse a conditional reconfiguration (40) both for conditional addition of a primary cell from a group of secondary cells, PSCell, in multi-connectivity operation and for conditional alteration of a PSCell in multi-connectivity operation, characterized in that the UE (12) is configured to: receive conditional reconfigurations (40) for the respective target candidate PSCell cells, wherein the conditional reconfigurations (40) are PSCell addition conditional configurations, CPA, or PSCell alteration conditional configurations, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40);and a PSCell target candidate configuration (44) that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; Petition 870250081883, dated 11 / 09 / 2025, p. 204 / 236 10 / 13 wherein each of at least one of the conditional reconfigurations (40) also includes information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each or more of the other conditional reconfigurations (40).; 30. User equipment (UE) (12) according to claim 29, characterized in that it is configured to perform the method as defined in any one of claims 2 to 15.

31. Network node (14) configured for use in a communication network (10) to allow a user device, UE, (12) to reuse a conditional reconfiguration (40) both for conditional addition of a primary cell of a group of secondary cells, PSCell, in multiconnectivity operation and for conditional alteration of a PSCell in multiconnectivity operation, characterized in that the network node (14) is configured to: transmit, to the UE (12), conditional reconfigurations (40) for the respective target candidate PSCell cells, wherein the conditional reconfigurations (40) are conditional PSCell addition configurations, CPA, or conditional PSCell alteration configurations, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40);and a PSCell target candidate configuration (44) that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; wherein each of at least one of the conditional reconfigurations (40) also includes information (46) on how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each of one or more other conditional reconfigurations (40).; 32. Network node (14) according to claim 31, characterized in that it is configured to perform the method as defined in any one of claims 17 to 28.

33. Computer program, characterized in that it comprises instructions which, when executed by at least one processor of a user device, cause the user device to perform the method as defined in any one of claims 1 to 15.

34. Computer program, characterized in that it comprises instructions which, when executed by at least one processor of a network node (14), cause the network node (14) to perform the method as defined in any one of claims 16 to 28.

35. Carrier containing the computer program as defined in claim 33 or 34, characterized in that the carrier is one of an electronic signal, optical signal, radio signal or computer-readable storage medium.

36. User equipment, UE, (12) configured to reuse a conditional reconfiguration (40) both for conditional addition of a primary cell from a group of secondary cells, PSCell, in multiconnectivity operation and for conditional alteration of a PSCell in multiconnectivity operation, characterized in that the UE (12) comprises: a set of communication circuits; and a set of processing circuits configured to receive conditional reconfigurations (40) for the respective target candidate PSCell cells, wherein the conditional reconfigurations (40) are conditional PSCell addition configurations, CPA, or configurations Petition 870250081883, dated 11 / 09 / 2025, p.206 / 236 12 / 13 conditional changes of PSCell, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40); and a PSCell target candidate configuration (44) that is a configuration to be applied to the PSCell target candidate cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; wherein each of at least one of the conditional reconfigurations (40) also includes information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each or more of the other conditional reconfigurations (40).

37. User equipment, UE, (12) according to claim 36, characterized in that the processing circuitry is configured to perform the method as defined in any one of claims 2 to 15.

38. Network node (14) configured for use in a communication network (10) to allow a user equipment, UE, (12) to reuse a conditional reconfiguration (40) both for conditional addition of a primary cell of a group of secondary cells, PSCell, in multiconnectivity operation and for conditional alteration of a PSCell in multiconnectivity operation, characterized in that the network node (14) comprises: a set of communication circuits; and a set of processing circuits configured to transmit, through the set of communication circuits, to the UE (12), conditional reconfigurations (40) for the respective target candidate cells of PSCell, wherein the conditional reconfigurations (40) are configurations Petition 870250081883, of 11 / 09 / 2025, p.207 / 236 13 / 13 PSCell Addition Conditionals, CPA, or PSCell Change Conditional Settings, CPC; wherein each of the conditional reconfigurations (40) includes: a first execution condition (42) that needs to be met to trigger the execution of the conditional reconfiguration (40); and a PSCell Target Candidate Setting (44) that is a setting to be applied to the PSCell Target Candidate Cell of the conditional reconfiguration (40) when the conditional reconfiguration (40) is executed; wherein each of at least one of the conditional reconfigurations (40) also includes information (46) about how, after the execution of the conditional reconfiguration (40), to update the first execution condition (42) of, or add a second execution condition to each or more other conditional reconfigurations (40).

39. Network node (14) according to claim 38, characterized in that the set of processing circuits is configured to perform the method as defined in any one of claims 17 to 28.

Images