Inter-node signaling for multiple CHO configurations for same primary cell

Abstract

Systems and methods related to signaling for multiple conditional switching (CHO) configurations for the same primary cell (PCell) are disclosed. In one embodiment, a method performed by a candidate target master node (MN) for a user equipment (UE) includes receiving a handover request message for a CHO of the UE to a candidate target PCell from a source MN, transmitting a secondary node addition request message to one or more candidate target secondary nodes (SNs) for one or more primary secondary cell group (SCG) cells (PSCell), and receiving an acknowledgement message. The method further includes generating a CHO configuration for the candidate target SN based on the acknowledgement message, where for the candidate target PCell, the CHO configuration includes a CHO configuration for a candidate target SCG or PSCell for each of the candidate target SN. The method also includes sending a handover request acknowledgement message including the CHO configuration to the source MN.

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 585,077, filed on September 25, 2023, the entire disclosure of which is hereby incorporated by reference. Technical Field

[0003] This disclosure relates to conditional switching in cellular communication systems. Background Technology

[0004] Conditional toggle (CHO)

[0005] In cellular communication systems such as 3GPP 5GS, handover is typically triggered when the User Equipment (UE) is at the cell edge and experiencing poor radio conditions. If the UE rapidly enters poor radio conditions, the conditions may already be so poor that the actual handover process may be difficult to execute. If the uplink (UL) is already poor, this may cause the network to be unable to detect measurement reports sent by the UE, and therefore the network cannot initiate the handover process. Downlink (DL) problems may cause handover commands (i.e., RRCReconfiguration messages with the reconfigurationWithSync field) to fail to reach the UE. Under poor radio conditions, DL messages are fragmented more frequently, which increases the risk of retransmissions and the risk of messages not reaching the UE in a timely manner. Failed transmission of handover commands is a common cause of unsuccessful handovers.

[0006] To improve mobility robustness and address the aforementioned issues, a concept called Conditional Handover (CHO) was introduced in 3GPP Release 16. The core idea of ​​CHO is that the transmission and execution of the handover command are separated. This allows the handover command to be sent to the UE earlier while radio conditions are still favorable, increasing the likelihood of successful message delivery. Based on associated execution conditions, the handover command is executed at a later point in time. Execution conditions typically take the form of thresholds, such as the candidate target cell's signal strength becoming X dB better than the serving cell (the so-called A3 event), or the serving cell's signal strength becoming X dBm worse and the candidate target cell's signal strength becoming Y dBm better (the so-called A5 event).

[0007] In the context of this disclosure, a cell for which a conditional handover (or other conditional mobility procedure) has been configured is referred to as a “candidate target cell” or “potential target cell.” Similarly, a radio network node controlling a candidate / potential target cell is referred to as a “candidate target node” or “potential target node.” In a sense, once the CHO execution conditions for a candidate / potential target cell have been met, and CHO execution toward that candidate / potential target cell has been triggered, the cell is no longer “potential” or “candidate” in the usual sense of the term, because it is no longer uncertain whether a CHO will be executed toward it. Therefore, after the CHO execution conditions have been met / triggered, the relevant candidate / potential target cell is sometimes referred to herein as a “target cell.”

[0008] Figure 1 This shows the signaling flow used for conditional switching in the 3GPP New Radio (NR). Figure 1 The steps of the condition switching process are as follows.

[0009] Steps 101-102. The UE and the source gNodeB (gNB) have an established connection and are exchanging user data. Due to some trigger, such as a measurement report from the UE, the source gNB decides to configure one or more CHO candidate cells. The threshold used for the measurement report should be selected as lower than the threshold in the handover execution conditions. This allows the serving cell to prepare for handover while the radio link to the UE is still stable. The handover execution is completed at a point in time (and at the threshold) after the handover execution is deemed optimal.

[0010] Step 103. The source gNB sends a CHO REQUEST to the target gNB, which contains the information necessary to prepare for conditional handover on the target side. Among other things, this information includes the current source configuration and UE capabilities.

[0011] Step 104. The target gNB prepares for handover and responds to the source gNB with a CHO REQUEST ACKNOWLEDGE, which includes a handover command (RRC reconfiguration message) to be sent to the UE and executed subsequently if / when the execution conditions are met. The handover command includes information required by the UE to access the target cell, such as random access configuration, a new cell radio network temporary identifier (C-RNTI) assigned by the target access node, and security parameters that enable the UE to calculate the target security key, allowing the UE to send a handover completion message (RRCReconfigurationComplete message).

[0012] Steps 105-106. To configure the candidate target cell, the source node sends a CHO configuration (i.e., an RRC reconfiguration message) to the UE, which contains the handover command and associated execution conditions. The handover command (also an RRC reconfiguration message) is the same as the handover command generated by the target node in steps 103-104 during the handover preparation phase, and the execution conditions are generated by the source node.

[0013] Steps 107-108. Afterwards, if the execution conditions are met, the UE performs a handover by performing random access and sending a handover completion message (i.e., an RRC reconfiguration completion message) to the target node.

[0014] Step 109. The target gNB sends a HANDOVER SUCCESS message to the source gNB, indicating that the UE has successfully established a target connection.

[0015] Steps 110-111. Upon receiving the handover success indication, the source gNB ceases scheduling any further DL or UL data to the UE and sends an SN STATUS TRANSFER message to the target gNB, indicating the latest Packet Data Convergence Protocol (PDCP) sequence number (SN) transmitter and receiver status. The source node also begins forwarding user data to the target node.

[0016] Step 112. Upon receiving the handover completion message, the target node can begin exchanging user data with the UE. The target node also requests the Access and Mobility Management Function (AMF) to switch the DL data path from the source node's User Plane Function (UPF) to the target node (not shown). Once the path handover is complete, the target node sends a UE CONTEXTRELEASE message to the source node.

[0017] The concept of conditional handover in 3GPP Rel-16 has been generalized into a common conditional reconfiguration framework, in which the UE can also be pre-configured with other types of reconfiguration, which can be performed via RRC reconfiguration messages (in New Radio (NR)) or RRC connection reconfiguration messages (in Long Term Evolution (LTE)) when a specific associated condition is triggered.

[0018] Conditional Primary / Secondary Cell Group (SCG) Cell Addition (CPA) and Conditional PSCell Change (CPC) are examples of two other types of reconfiguration operating on PSCells in a Multi-Radio Dual-Connectivity (MR-DC) scenario using the conditional reconfiguration framework. In both CPA and CPC, when the execution condition is met, it is not a handover, but rather a PSCell addition (in the case of CPA) or a PSCell change (in the case of CPC) is performed. CPC and CPA were introduced in 3GPP Rel-16 and Rel-17, respectively. Note that, depending on the specific 3GPP specification, a PSCell can be referred to as a primary / secondary cell or a primary SCG cell, and these terms are used interchangeably herein.

[0019] CHOs with target SCG and CHOs with candidate SCGs

[0020] In 3GPP Rel-16, the target configuration of CHO, i.e. the Radio Resource Control (RRC) configuration applied and executed by the UE when the associated execution conditions are met, may include only the primary cell group (MCG) configuration, i.e. no secondary cell group (SCG) / PSCell configuration can be part of the configuration subsequently applied by the UE.

[0021] In 3GPP Rel-17, support for including SCG configuration in CHO target configuration has been added. This means that when the associated execution conditions for CHO are met, the UE can apply both the target MCG configuration and the associated target SCG configuration.

[0022] With the addition in Rel-17, the UE can therefore also be configured with the SCG configuration when performing a CHO. However, the associated execution conditions then only apply to the CHO, i.e., related to the primary cell (PCell). Therefore, there is a risk that the radio conditions for the associated SCG / PSCell may be less favorable when the CHO execution conditions are met and the configuration is executed.

[0023] For 3GPP Rel-18, the work item concerning mobility enhancements (see RP-223520, 3GPP Work Item Description: Further NR Mobility Enhancements, MediaTek Inc., Apple Inc., 3GPP TSG RAN Meeting #98-e, eConference, December 12-16, 2022) includes the following objectives to support CHOs with different candidate SCGs:

[0024] 4. Specify the CHO [RAN3, RAN2] for both the target MCG and candidate SCG for the CPC / CPA in NR-DC.

[0025] ○ The CHO values ​​for both the target MCG and the target SCG were used as the baseline.

[0026] Therefore, work is underway in 3GPP to enable the UE to consider the radio conditions of candidate SCG / PSCells when determining what target MCG+SCG configuration to apply and execute. The CHO conditions for candidate PCells are then combined with the CPA / CPC conditions for one or more associated candidate PSCells.

[0027] In RAN2#123, the following agreements were reached regarding the CHOs, including the target MCG and candidate SCGs:

[0028] => When releasing an SCG, the UE does not automatically remove the configuration used for the CHO, which includes the configuration of the target MCG and the candidate SCG.

[0029] =>R2 assumes that the source MN initiates preparation of an R18 CHO with one or more candidate SCGs, for example, the S-MN “tells” the T-MN whether it is allowed to configure one or more candidate SCGs. FFS signaling details.

[0030] => Candidate MN recommends candidate PSCell to candidate SN (for CHOs with CPCs initiated by MN).

[0031] => The CHO recovery details used to handle the added CHO caused by this feature are FFS.

[0032] => For feature R18, R2 assumes that the UE does not need to continue conditional reconfiguration evaluation of CHOs with (one or more) candidate SCGs when initiating the SCG failure information procedure.

[0033] => The recommendation of candidate PSCells can be based on measurement results.

[0034] => For this R18 feature, R2 assumes that once the PSCell change is triggered, the evaluation of the execution conditions for a CHO with one or more candidate SCGs does not need to continue.

[0035] =>maxNrofCondCells = The maximum number of conditional configurations that the UE can store (assumed to be a memory limit), the value of which is FFS.

[0036] =>selectedCondRRCReconfig-r17 is not reused to indicate the selected target SCG to the target MN, that is, the UE indicates the selected PSCell's physCellId and ARFCN-ValueNR to the target MN.

[0037] =>condEventA3 or condEventA5 is not used as an execution condition for candidate PSCells (it can be revisited later if a strong reason can be provided).

[0038] => For CHOs with candidate SCG cases, condEvent A4 is used for the current PSCell (i.e., if it is configured as a candidate PSCell for evaluation).

[0039] At the RAN3#121 meeting, the following agreement was reached regarding CHOs with multiple SCGs.

[0040] For a CHO with multiple SCGs in different T-SNs, the handover request confirmation message includes a list of information for each SCG, such as the PDU session permission result, data forwarding address, and a list of prepared PSCells for each prepared T-SN. This protocol can be revisited after the RAN2 protocol.

[0041] Correspondingly, the list of transparent containers pointing to the target Next Generation Radio Access Network (NG-RAN) node and the source NG-RAN node for the RRC HANDOVERCOMMAND (Switch Command) message has been introduced into the PSCell list for FFS, as shown below.

[0042]

[0043] Summary of the Invention

[0044] Systems and methods related to inter-node signaling for multiple Conditional Handover (CHO) configurations for the same primary cell (PCell) in a wireless network are disclosed. In one embodiment, a method performed by a network node acting as a candidate target primary node (MN) for a user equipment (UE) includes receiving a handover request message from a source MN, the handover request message indicating that the handover request is for a CHO for the UE to a candidate target PCell operated by the candidate target MN. The method further includes sending a secondary node add request message to one or more candidate target secondary nodes (SNs) for one or more primary secondary cell group (SCG) cells (PSCells), and receiving one or more secondary node add request confirmation messages from the one or more candidate target SNs. The method further includes generating a CHO configuration for the one or more candidate target SNs based on the one or more secondary node add request confirmation messages, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The method further includes sending a handover request confirmation message including the CHO configuration to the source MN. In this way, the structure for switching request confirmation can be simplified for CHOs with multiple candidate SCGs.

[0045] In one embodiment, the switch request confirmation message includes a separate switch command message for each CHO configuration in the CHO configuration. In another embodiment, for each separate switch command message, the switch request confirmation message also includes an execution condition associated with the switch command message.

[0046] In one embodiment, the handover request confirmation message includes a single handover command message, which includes the CHO configuration. In another embodiment, the handover request confirmation message further includes execution conditions associated with the handover command message.

[0047] In one embodiment, each of the one or more secondary node add request acknowledgment messages includes one or more Radio Resource Control (RRC) reconfiguration messages, the one or more RRC reconfiguration messages corresponding to one or more candidate target SCG or PSCell configurations for a CHO of a corresponding candidate target SN among the one or more candidate target SNs. In one embodiment, the one or more RRC reconfiguration messages include multiple RRC reconfiguration messages for configurations of multiple candidate SCGs or PSCells from the same candidate target SN. In one embodiment, each RRC reconfiguration message is associated with a specific CHO having a candidate SCG configuration.

[0048] A corresponding embodiment of a network node acting as a candidate target MN for a UE is also disclosed. In one embodiment, a network node acting as a candidate target MN for a UE is adapted to receive a handover request message from a source MN, the handover request message indicating that the handover request is a CHO for the UE to a candidate target PCell operated by the candidate target MN. The network node is also adapted to send a secondary node add request message to one or more candidate target SNs for one or more PSCells, and to receive one or more secondary node add request confirmation messages from the one or more candidate target SNs. The network node is also adapted to generate a CHO configuration for the one or more candidate target SNs based on the one or more secondary node add request confirmation messages, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The network node is also adapted to send a handover request confirmation message including the CHO configuration to the source MN.

[0049] In one embodiment, a network node acting as a candidate target MN for a UE includes processing circuitry configured to receive a handover request message from a source MN, the handover request message indicating that the handover request is a Call of Interest (CHO) for the UE to a candidate target PCell operated by the candidate target MN. The processing circuitry is further configured to send a secondary node add request message to one or more candidate target SNs for one or more PSCells, and receive one or more secondary node add request confirmation messages from the one or more candidate target SNs. The processing circuitry is further configured to generate a CHO configuration for the one or more candidate target SNs based on the one or more secondary node add request confirmation messages, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The processing circuitry is further configured to send a handover request confirmation message including the CHO configuration to the source MN.

[0050] Embodiments of a method performed by a network node acting as a source MN for a UE are also disclosed. In one embodiment, a method performed by a network node acting as a source MN for a UE includes sending a handover request message to a candidate target MN, the handover request message indicating that the handover request is for the UE to a candidate target PCell operated by the candidate target MN. The method further includes receiving from the candidate target MN a handover request confirmation message including a handover request configuration for one or more candidate target SNs, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The method further includes generating and sending an RRC reconfiguration message including the CHO configuration to the UE.

[0051] In one embodiment, the switch request confirmation message includes a separate switch command message for each CHO configuration in the CHO configuration. In another embodiment, for each separate switch command message, the switch request confirmation message also includes an execution condition associated with the switch command message.

[0052] In one embodiment, the handover request confirmation message includes a single handover command message, which includes the CHO configuration. In another embodiment, the handover request confirmation message further includes execution conditions associated with the handover command message.

[0053] A corresponding embodiment for a network node acting as a source MN for a UE is also disclosed. In one embodiment, a network node acting as a source MN for a UE is adapted to send a handover request message to a candidate target MN, the handover request message indicating that the handover request is for the UE to a candidate target PCell operated by the candidate target MN. The network node is also adapted to receive from the candidate target MN a handover request confirmation message including a handover request configuration for one or more candidate target SNs, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The network node is also adapted to generate and send an RRC reconfiguration message including the CHO configuration to the UE.

[0054] In one embodiment, a network node acting as a source MN for a UE includes processing circuitry configured to send a handover request message to a candidate target MN, the handover request message indicating that the handover request is for a Call of Interest (CHO) for the UE to a candidate target PCell operated by the candidate target MN. The processing circuitry is further configured to cause the network node to receive from the candidate target MN a handover request confirmation message including a CHO configuration for one or more candidate target SNs, wherein for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. The processing circuitry is further configured to cause the network node to generate and send an RRC reconfiguration message including the CHO configuration to the UE.

[0055] Embodiments of a method performed by a network node acting as a candidate target MN for a UE are also disclosed. In one embodiment, a method performed by a network node acting as a candidate target MN for a UE includes sending a message to the source MN for the UE requesting the release or modification of a CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least a CHO configuration for the candidate target PCell.

[0056] In one embodiment, the method further includes receiving a request from a candidate target SN to which the candidate target PSCell belongs in the CHO configuration for releasing or modifying the CHO configuration that includes the candidate target PSCell.

[0057] In one embodiment, the method further includes receiving a request from the source MN for a new or updated CHO configuration for the same candidate target PCell. In one embodiment, the method further includes generating the new or modified CHO configuration and sending the new or modified CHO configuration to the source MN. In one embodiment, the method further includes generating a configuration for execution conditions associated with the new or modified CHO configuration, wherein sending the new or modified CHO configuration to the source MN includes sending the new or modified CHO configuration and the configuration for the associated execution conditions to the source MN.

[0058] A corresponding embodiment of a network node for acting as a candidate target MN for a UE is also disclosed. In one embodiment, a network node for acting as a candidate target MN for a UE is adapted to send a message to the source MN for the UE requesting the release or modification of the CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least one CHO configuration for the candidate target PCell.

[0059] In one embodiment, a network node for acting as a candidate target MN for a UE includes processing circuitry configured to send a message to the source MN for the UE requesting the release or modification of a CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least a CHO configuration for the candidate target PCell.

[0060] In one embodiment, a method performed by a network node acting as a source MN for a UE includes receiving from a candidate target MN a message requesting the release or modification of a CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least one CHO configuration for the same PCell. The method further includes sending a request for a new or updated CHO configuration for the candidate target PCell, receiving the new or modified CHO configuration from the candidate target MN, and generating and sending a message including the new or modified CHO configuration to the UE.

[0061] In one embodiment, the method further includes receiving from the candidate target MN a configuration for one or more execution conditions associated with the new or modified CHO configuration. In one embodiment, the message sent to the UE also includes the one or more execution conditions.

[0062] In one embodiment, a network node acting as a source MN for a UE is adapted to receive messages from a candidate target MN requesting the release or modification of a CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least one CHO configuration for the same PCell. The network node is also adapted to send a request for a new or updated CHO configuration for the candidate target PCell, receive the new or modified CHO configuration from the candidate target MN, and generate and send a message including the new or modified CHO configuration to the UE.

[0063] In one embodiment, a network node acting as a source MN for a UE includes processing circuitry configured to receive messages from a candidate target MN requesting the release or modification of a CHO configuration for a candidate target PCell having two or more CHO configurations, and / or requesting the addition of at least one CHO configuration for the same PCell. The processing circuitry is further configured to send a request for a new or updated CHO configuration for the candidate target PCell, receive the new or modified CHO configuration from the candidate target MN, and generate and send a message including the new or modified CHO configuration to the UE. Attached Figure Description

[0064] Several aspects of this disclosure are illustrated in conjunction with the accompanying drawings, which are incorporated in and form a part of this specification, and together with the specification serve to explain the principles of this disclosure.

[0065] Figure 1 This shows the signaling flow used for conditional handover in the 3GPP New Radio (NR);

[0066] Figure 2 This is a flowchart illustrating a method performed by a first network node acting as a candidate target master node (MN) for a user equipment (UE) according to some embodiments of the present disclosure;

[0067] Figure 3 This is a flowchart illustrating a method performed by a network node acting as a source MN for a UE, according to some embodiments of the present disclosure;

[0068] Figure 4 This is a flowchart illustrating a method for acting as a network node of a candidate target MN according to some embodiments of the present disclosure. The UE is configured with multiple CHO configurations for a candidate target primary cell (PCell) belonging to the candidate target MN, including at least one conditional handover (CHO) configuration. The at least one CHO configuration also includes a candidate target primary / secondary cell group (SCG) cell (PSCell) (and associated execution conditions) to enable the release or modification of the CHO configuration.

[0069] Figure 5 This is a flowchart illustrating a method for a network node acting as a UE (source MN) to request the release or modification of a CHO configuration, according to some embodiments of this disclosure.

[0070] Figure 6 Examples of communication systems according to some embodiments are shown;

[0071] Figure 7 A UE is shown according to some embodiments;

[0072] Figure 8 Network nodes are shown according to some embodiments;

[0073] Figure 9 This is a block diagram of a host based on the various aspects described in this document; the host can be... Figure 6 An example of a host computer;

[0074] Figure 10 This is a block diagram illustrating a virtualized environment in which the functionality implemented by some embodiments can be virtualized; and

[0075] Figure 11 This diagram illustrates a communication between a host and a UE via a network node through a partial wireless connection, according to some embodiments. Detailed Implementation

[0076] The embodiments described below represent information enabling those skilled in the art to practice the embodiments and illustrate the best mode for practicing the embodiments. Those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts not specifically mentioned herein after reading the following description in consideration of the accompanying drawings. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0077] There are some challenges. When a target primary node (MN) (e.g., a target radio access network (RAN) node, such as a target gNodeB (gNB)) provides a source MN (e.g., a source RAN node, such as a source gNB) with multiple conditional handover (CHO) configurations for candidate secondary cell groups (SCGs), multiple handover command messages for each candidate primary SCG cell (PSCell) / SCG, with parameters for the associated conditional PSCell Addition (CPA) / conditional PSCell Change (CPC) execution conditions, and only one configuration for the CHO (i.e., without any associated CPA / CPC execution conditions) should be sent within the handover request confirmation message.

[0078] By including an additional container for the switch command message in the XnAP switch request confirmation message, where the new container is for the candidate PSCell, and the existing container for the switch command message in the same message needs to be included even without a candidate PSCell, it is impossible to provide configuration only for CHO configurations with associated CPA / CPC execution. This prevents the candidate target MN from providing all configurations associated with CPA / CPC conditions, which would be useful in some scenarios (e.g., where the switch (HO) will only be performed with PSCell addition or change).

[0079] It also does not allow the candidate target MN to provide the source MN with an additional or updated CHO target configuration with the candidate SCG (i.e., a CHO with a CPA / CPC configuration) (i.e., an RRC reconfiguration / switch command message).

[0080] Another issue is that if the target MN determines that one of the CHO configurations used for the PCell needs to be changed—for example, from one candidate PSCell to another, or by adding a new CHO configuration and / or releasing one of the CHO configurations—it is impossible for the target MN to indicate this to the source MN. The only available means is to use the XnAP CHO CANCEL message to trigger the release of the CHO configuration used for the PCell. Therefore, it is impossible to release any of multiple CHO configurations (including, for example, a CHO-only configuration for a candidate target PCell) or trigger a modification to any of the CHO configurations or the addition of another CHO configuration for the same PCell.

[0081] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges. Systems and methods are disclosed herein for network nodes to send multiple CHO configurations (i.e., handover command messages and corresponding execution conditions) for the same primary cell (PCell) in the same message from a target MN to a source MN. This includes systems and methods that thus allow some or all handover command (RRC reconfiguration) messages for the same PCell to include execution conditions for candidate PSCells included in or associated with the handover command (RRC reconfiguration) message.

[0082] This document also discloses a system and method for a target MN to trigger a source MN to configure a new CHO configuration for a PCell that already has a CHO configuration, or to send a request to modify the CHO configuration (e.g., to change a candidate PSCell).

[0083] This document discloses a system and method for allowing multiple CHO configurations within a single message (e.g., within a single RRC container) to be transferred from a target MN to a source MN when they exist for a selected PCell.

[0084] Certain embodiments may provide one or more of the following technical advantages. One example advantage is that embodiments of this disclosure can simplify the structure of the RRC transparent container within a switch request confirmation message for a CHO with multiple candidate SCGs.

[0085] The first set of embodiments includes a method for acting as a first network node of a (candidate) target master node (MN) for a user equipment (UE). In this regard, Figure 2This is a flowchart illustrating a method performed by a first network node acting as a candidate target MN for a UE, according to some embodiments of this disclosure. Note that in Figure 2 In the diagram, optional steps are indicated by dashed lines / boxes. Furthermore, although the actions performed by the first network node are... Figure 2 The description refers to it as a "step", and in Figure 2 The steps are shown in a specific order, but they can be performed in any desired order, and some of them can be performed in parallel. Figure 2 The steps of the process performed by the first network node acting as the candidate target MN are as follows:

[0086] - Step 200: The first network node (which acts as the candidate target MN for the UE) receives a handover request message from the source MN, indicating that the request is for conditional handover. In other words, the candidate target MN for the UE receives a handover request message from the source MN to conditionally hand over the UE to the candidate target PCell operated by the candidate target MN.

[0087] In one example, the message includes an indication that the request is for a conditional switch with one or more candidate SCG / PSCells, or that the target MN can provide a conditional switch configuration with one or more candidate SCG / PCells.

[0088] - Step 202: The first network node (which acts as a candidate target MN for the UE) sends an S-NODE ADDITION REQUEST message to one or more candidate target SNs for one or more candidate target PSCells.

[0089] - Step 204: The first network node (which acts as a candidate target MN for the UE) receives an S-NODE ADDITION REQUEST ACKNOWLEDGE message from one or more candidate target SNs, which includes one or more RRC reconfiguration messages.

[0090] One or more RRC reconfiguration messages can correspond to one or more target SCG configurations for a CHO that has one or more candidate SCG configurations. That is, a candidate target SN provides multiple RRC reconfiguration messages to configure multiple candidate SCGs / PSCells from the same candidate target SN. Thus, each RRC reconfiguration message can be associated with a specific CHO that has a candidate SCG configuration.

[0091] - Step 206: The first network node (which acts as a candidate target MN for the UE) determines the generated CHO configuration, i.e., one or more handover command messages, and includes these within a container (e.g., within a single RRC container), and may also include associated CPA / CPC execution conditions. In other words, the candidate target MN for the UE generates a CHO configuration for one or more candidate target SNs based on the received secondary node add request confirmation messages(s)(s), wherein for a candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs.

[0092] In one embodiment, the XnAP handover request confirmation message includes a single RRC container with a single handover command message, which includes multiple CHO configurations.

[0093] In one embodiment, the XnAP handover request confirmation message includes a single RRC container with multiple handover command messages, one handover command message for each CHO configuration.

[0094] In one embodiment, the RRC container includes both (one or more) switching command messages and associated CPA / CPC execution conditions.

[0095] ○ In one embodiment, the RRC container includes only one or more switch command messages.

[0096] - Step 208: The first network node (which acts as a candidate target MN for the UE) sends a handover request confirmation message to the source MN. The handover request confirmation message includes the generated CHO configuration from step 206. In other words, the handover request confirmation message includes the generated RRC message (e.g., a single RRC container that includes one or more handover command messages and may also include associated CPA / CPC execution conditions) in the transparent container information element (IE) from the target NG-RAN node to the source NG-RAN node or in a new IE for the container. As discussed above, for the same candidate target PCell operated by the candidate target MN, the handover request confirmation message includes multiple CHO configurations, wherein for each candidate target SN, these multiple CHO configurations respectively include one or more CHO configurations for one or more SCGs or PSCells operated by the candidate target SN.

[0097] One set of embodiments includes a method for acting as a network node for a UE (User Equipment). In this regard, Figure 3 This is a flowchart illustrating a method performed by a network node acting as a source MN for a UE, according to some embodiments of this disclosure. Note that in Figure 3 In the diagram, optional steps are indicated by dashed lines / boxes. Furthermore, although actions performed by network nodes are... Figure 3 The term "step" is used in the description and Figure 3 The steps are shown in a specific order, but they can be performed in any desired order, and some of them can be performed in parallel. Figure 2 The steps of the process performed by the network node acting as the source MN are as follows:

[0098] - Step 300: The network node (which acts as the source MN for the UE) sends a handover request message to the candidate target MN, indicating that the request is for conditional handover. In other words, the source MN for the UE sends a handover request message to the candidate target MN to conditionally hand over the UE to the candidate target PCell operated by the candidate target MN.

[0099] In one example, the message includes an indication that the request is for a conditional switch with one or more candidate SCG / PSCells, or that the target MN can provide a conditional switch configuration with one or more candidate SCG / PSCells.

[0100] - Step 302: The network node (which acts as the source MN for the UE) receives a handover request confirmation message from the candidate target MN, which contains, for example, multiple CHO configurations and associated CPA / CPC execution conditions within a transparent container IE from the target NG-RAN node to the source NG-RAN node or a new IE for the container. In other words, for the same candidate target PCell operated by the candidate target MN, the handover request confirmation message includes multiple CHO configurations, where these multiple CHO configurations correspond to the corresponding CHO configurations for an SCG or PSCell operated by one or more candidate target SNs; that is, there is one CHO configuration for each SCG or PSCell for each candidate target SN.

[0101] In one embodiment, the handover request confirmation message includes a single RRC container with a single handover command message that includes multiple CHO configurations.

[0102] In one embodiment, the XnAP handover request confirmation message includes a single RRC container with multiple handover command messages, one handover command message for each CHO configuration.

[0103] In one embodiment, the RRC container includes both (one or more) switching command messages and associated CPA / CPC execution conditions.

[0104] ○ In one embodiment, the RRC container includes only one or more switch command messages.

[0105] - Step 304: The network node (which acts as the source MN for the UE) generates and sends an RRC reconfiguration message to the UE, which includes one or more CHO configurations received from the candidate target MN for the same PCell.

[0106] In one embodiment, the source MN generates execution conditions for the candidate target PCell (i.e., for the CHO) and the associated candidate target PSCell (i.e., for the CPA / CPC) (if any), and includes these in the RRC reconfiguration message sent to the UE. The execution conditions for the CPA / CPC can be based on the corresponding execution condition information it receives from the candidate target MN (for the CHO with candidate SCG / PSCell configuration).

[0107] When a UE is already configured with multiple CHO configurations for the same candidate target PCell (e.g., one or more CHO configurations with different associated candidate PSCell(s), and therefore with associated CPA / CPC execution conditions) and may be configured with a CHO configuration that does not have any associated candidate PSCell (which may or may not have an SCG configuration), the network may need to update the CHO configuration for the candidate target PCell. For example, a candidate target MN (which processes the candidate target PCell) may need to change the candidate PSCell used for its CHO configuration, such as replacing the CHO configuration that includes candidate target PSCell A with a CHO configuration that includes another candidate target PSCell B. This can be triggered, for example, by an indication from the candidate target SN processing PSCell A that it is no longer a suitable candidate PSCell. The candidate target MN can then decide to configure another candidate target PSCell B with the CHO configuration of the candidate target PCell. This can be triggered by the candidate target MN itself, or it can be based on an indication from the candidate target SN.

[0108] One set of embodiments includes a method for acting as a network node for a candidate target MN for a UE, the UE being configured with multiple CHO configurations for candidate target PCells belonging to the candidate target MN, including at least one CHO configuration that further includes a candidate target PSCell (and associated CPA / CPC execution conditions). In this regard, Figure 4 This is a flowchart illustrating a method for acting as a network node for a candidate target MN for a UE according to some embodiments of the present disclosure. The UE is configured with multiple CHO configurations for candidate target PCells belonging to the candidate target MN, including at least one CHO configuration that further includes a candidate target PSCell (and associated CPA / CPC execution conditions). Note that in Figure 4 In the diagram, optional steps are indicated by dashed lines / boxes. Furthermore, although actions performed by network nodes are... Figure 4 The term "step" is used in the description and Figure 4 The steps are shown in a specific order, but they can be performed in any desired order, and some of them can be performed in parallel. Figure 4 The steps of the process performed by the network node acting as the candidate target MN are as follows:

[0109] - Step 400 (optional): The network node (which acts as the candidate target MN) receives an instruction from the candidate target SN to which the candidate target PSCell in the CHO configuration belongs, to release or modify the CHO configuration that includes the candidate target PSCell.

[0110] - Step 402: The network node (which acts as the candidate target MN) sends a message to the source MN (i.e. the current serving MN) for the UE to request the release or modification of the CHO configuration for a candidate target PCell with multiple CHO configurations (e.g., one or more CHO configurations in the CHO configurations include one or more candidate SCG / PSCells), i.e., a subset of the CHO configurations for the same candidate target PCell, and / or to request the addition of at least one CHO configuration for the same PCell.

[0111] ○ In one option, the message includes information about CHO configurations to be released, modified, and / or added.

[0112] ■ In one example, the message includes an RRC reconfiguration (switch command) message and / or a configuration for the execution conditions of the CHO configuration to be added or modified.

[0113] ■ In one example, the message includes an indication of which existing CHO configurations to be released or modified. This indication may consist of the identifiers of the candidate target PCell and the candidate target PSCell (in cases where the CHO configuration to be released or modified includes both), or it may include another identifier for the CHO configuration, where each CHO configuration (for the UE) from the same candidate target MN can be assigned a unique identifier, or where each CHO configuration (for the UE) for the same candidate target PCell is assigned a unique identifier. In an alternative, where the indication consists of the identifiers of the candidate target cells (PCell and PSCell) used for the CHO configuration, and the request to release or modify involves a CHO configuration for a PCell that does not include any candidate PSCells (i.e., a "CHO-only" configuration), the indication consists of a setting or value corresponding to "No candidate SCG / PSCell" (i.e., it is a "CHO-only" configuration).

[0114] ○ In one example, a message with a request to modify, release, or add one or more CHO configurations is a new XnAP message from the candidate target MN to the source MN, such as a CONDITIONAL HANDOVER MODIFICATION REQUIRED message or a CONDITIONAL HANDOVER MODIFICATION REQUEST message.

[0115] - Step 404 (Optional): The network node (which acts as the candidate target MN) then receives a request from the source MN for a new or updated CHO configuration for the same candidate target PCell. In one example, this request is received in a new XnAP message sent from the source MN to the candidate target MN, such as a conditional switch modification request message. In another example, the request is received in an XnAP switch request message.

[0116] In some options, if the new or (to be) modified CHO configuration should include the SCG configuration or candidate SCG / PSCell, then the candidate target MN then sends a request for the corresponding new or modified SCG configuration from the corresponding candidate target SN (e.g., an S-node modification request).

[0117] - Step 406 (optional): The network node (which acts as the candidate target MN) then generates a new or modified CHO configuration, and optionally includes configurations for the associated CPA / CPC conditions, if it includes the candidate target SCG / PSCell, and sends these to the source MN. In one example, the new or modified CHO configuration is sent in a new XnAP message, such as a CONDITIONAL HANDOVER MODIFICATION REQUEST ACKNOWLEDGE message. In another example, it is sent in an XnAP HANDOVER REQUEST ACKNOWLEDGE message.

[0118] One set of embodiments includes a method for acting as a network node for a UE (User Equipment). In this regard, Figure 5 This is a flowchart illustrating a method for acting as a network node for a source MN for a UE, according to some embodiments of this disclosure. Note that in Figure 5 In the diagram, optional steps are indicated by dashed lines / boxes. Furthermore, although actions performed by network nodes are... Figure 5 The term "step" is used in the description and Figure 5The steps are shown in a specific order, but they can be performed in any desired order, and some of them can be performed in parallel. Figure 5 The steps of the process performed by the network node acting as the source MN are as follows:

[0119] - Step 500: The network node (which acts as the source MN) receives a message from the candidate target MN to request the release or modification of the CHO configuration for a candidate target PCell with multiple CHO configurations (e.g., one or more CHO configurations in the CHO configurations include one or more candidate SCG / PSCells), i.e., a subset of the CHO configurations for the same candidate target PCell, and / or to request the addition of at least one CHO configuration for the same PCell.

[0120] ○ In one option, the message includes information about CHO configurations to be released, modified, and / or added.

[0121] ■ In one example, the message includes an RRC reconfiguration (switch command) message and / or a configuration for the execution conditions of the CHO configuration to be added or modified.

[0122] ■ In one example, the message includes an indication of which existing CHO configurations are to be released or modified. This indication may consist of the identifier of the candidate target PCell and the identifier of the candidate target PSCell (in the case that the CHO configurations to be released or modified include both), or it may include another identifier of the CHO configurations, where each CHO configuration (for the UE) from the same candidate target MN can be assigned a unique identifier, or where each CHO configuration (for the UE) for the same candidate target PCell is assigned a unique identifier.

[0123] ○ In one example, a message with a request to modify, release, or add one or more CHO configurations is a new XnAP message from the candidate target MN to the source MN, such as a CONDITIONAL HANDOVER MODIFICATION REQUIRED message.

[0124] Step 502: The network node (which acts as the source MN) sends a request for a new or updated CHO configuration for the same candidate target PCell. In one example, the request is sent in a new XnAP message (such as a conditional switch modification request message). In another example, the request is sent in an XnAP switch request message.

[0125] Step 504: The network node (which acts as the source MN) receives the new or modified CHO configuration from the candidate target MN, and optionally also receives the configuration for the associated CPA / CPC conditions if it includes the candidate target SCG / PSCell. In one example, the new or modified CHO configuration is received in a new XnAP message (e.g., a condition switching modification request confirmation message). In another example, it is received in an XnAP switching request confirmation message.

[0126] Step 506: The network node (which acts as the source MN) generates and sends a message to the UE, such as an RRC reconfiguration message, which includes the new or modified CHO configuration and, if it includes candidate target SCG / PSCell, optionally also includes configuration for the associated CPA / CPC conditions. The message may also include an explicit indication of the CHO configuration to be released.

[0127] In an alternative, the source MN receives a message from the candidate target MN containing a request to release or modify the CHO configuration for a candidate target PCell with multiple CHO configurations (e.g., one or more CHO configurations in the CHO configurations include candidate SCG / PSCell(s)), i.e., a request for a subset of CHO configurations for the same candidate target PCell, and / or a request to add CHO configurations for the same PCell. The message also includes target configurations and / or execution conditional configurations for any new (added) and / or modified CHO configurations. In one example, this message is a new XnAP message, such as a conditional handover modification request message sent from the candidate target MN to the source (serving) MN. After receiving the conditional handover modification request message, the source MN then generates and sends a message to the UE, such as an RRC reconfiguration message, which includes the new or modified CHO configuration, and optionally, if it includes candidate target SCG / PSCell(s), configurations for the associated CPA / CPC conditions. If the request includes an indication of the CHO configuration to be released, the source MN may also include the indication of the CHO configuration to be released in the message sent to the UE. Alternatively, the source MN sends a message back to the candidate target MN to confirm the modification of the CHO configuration, such as a new conditional switching modification request confirmation message sent from the source MN to the candidate target MN.

[0128] In an alternative, the candidate target MN indicates to the source MN via an XnAP conditional switch cancellation message that it requests modification of one or more CHO configurations for the candidate target PCell and / or that it wants to add one or more new CHO configurations for the candidate target PCell. This can be combined with a conditional switch cancellation message requesting the release of one or more CHO configurations for the candidate target PCell.

[0129] In one example, a cause value (e.g., a new cause value) is included in the condition switch cancellation message to indicate that the candidate target MN requests modification and / or addition of one or more CHO configurations for one or more candidate target PCells.

[0130] The source MN can then send a message to the candidate target MN, for example, via the transmission of an XnAP handover request message, to request a new (or updated) CHO configuration for one or more candidate target PCells. The candidate target MN then responds to the source MN, for example, via the transmission of an XnAP handover request confirmation message, with a message including the new (or updated) CHO configuration for one or more candidate target PCells. The source MN then generates and sends a message to the UE, such as an RRC reconfiguration message, which includes the new or modified CHO configuration and, optionally, the configuration for the associated CPA / CPC conditions if it includes a candidate target SCG / PSCell. This message may also include an explicit indication of the CHO configuration to be released for that candidate target PCell.

[0131] In one option, the conditional switching cancellation message sent from the candidate target MN to the source MN also includes an indication of any CHO configurations to be modified and / or added. In one example, for any new (added) and / or modified CHO configurations for one or more candidate target PCells, it then also includes the corresponding target configuration and / or execution conditional configuration. In this case, the source MN can generate a message and send it to the UE that includes (one or more) new and / or modified CHO configurations and an indication of any CHO configurations to be released, without first requesting the added / modified CHO configurations from the candidate target MN.

[0132] Below is an example implementation from 3GPP TS 38.331 v 17.5.0 (where additions are enclosed in underlined text). In this example, the inter-node handover command message is updated to include an optional configuration of the execution conditions (for the associated CPA / CPC conditions) for the first handover command message (i.e., the handover command message that already exists in the message), and an optional list of additional handover command messages, each with an optional configuration of the execution conditions (for the associated CPA / CPC conditions).

[0133] - Switch command

[0134] This message is used to transmit the switching command generated by the target gNB.

[0135] Direction: From target gNB to source gNB / source RAN.

[0136]

[0137]

[0138] Below are some example implementations from 3GPP TS 38.423 v 17.5.0:

[0139] Switch request confirmation

[0140] This message is sent by the target NG-RAN node to notify the source NG-RAN node of the resources prepared at the target.

[0141] Direction: Target NG-RAN node → Source NG-RAN node.

[0142]

[0143]

[0144]

[0145]

[0146] Figure 6 An example of a communication system 600 according to some embodiments is shown.

[0147] In this example, communication system 600 includes a telecommunications network 602 and a core network 606. Telecommunications network 602 includes an access network 604, such as a radio access network (RAN), and core network 606 includes one or more core network nodes 608. Access network 604 includes one or more access network nodes, such as network nodes 610A and 610B (one or more of which may generally be referred to as network node 610), or any other similar 3GPP access node or non-3GPP access point (AP). Furthermore, as those skilled in the art will understand, network nodes are not necessarily limited to implementations in which the radio and baseband portions are supplied and integrated by a single vendor. Therefore, it will be understood that network nodes include decomposed implementations or portions thereof. For example, in some embodiments, telecommunications network 602 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunications network 602 that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate alone or together with other nodes to perform one or more functions of any node in the telecommunications network 602 (including one or more network nodes 610 and / or core network node 608).

[0148] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), RAN Intelligent Controllers (near real-time or non-real-time) hosting software or software plug-ins (such as near real-time control applications (e.g., xApp) or non-real-time control applications (e.g., rApp)), or any combination thereof (the adjective "open" indicates support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification (such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Fronthaul User Plane Interface, or Open Fronthaul Management Plane Interface). Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in a virtualized environment (described further below), in which one or more network functions are virtualized. For example, the virtualized environment may include an O-Cloud computing platform orchestrated by a service management and orchestration framework via an O-2 interface defined by the O-RAN Consortium or similar technologies. Network node 610 facilitates direct or indirect connections of user equipment (UE), such as connecting UE 612A, 612B, 612C and 612D (one or more of which may generally be referred to as UE 612) to core network 606 via one or more wireless connections.

[0149] Examples of wireless communication via wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various embodiments, communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. Communication system 600 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0150] UE 612 can be any of a variety of communication devices, including wireless devices that are arranged, configured, and / or operable to communicate wirelessly with network node 610 and other communication devices. Similarly, network node 610 is arranged, capable, configured, and / or operable to communicate directly or indirectly with UE 612 and / or with other network nodes or devices in telecommunication network 602 to achieve and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network 602).

[0151] In the depicted example, core network 606 connects network node 610 to one or more hosts, such as host 616. These connections can be direct or indirect connections via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network 606 includes one or more core network nodes (e.g., core network node 608) constructed with hardware and software components. The characteristics of these components can be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node 608. Example core network nodes include functions of one or more of the following: Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Dehiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0152] Host 616 may be under the ownership or control of a service provider other than the operator or provider of access network 604 and / or telecommunications network 602, and may be operated by or on behalf of the service provider. Host 616 may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as retrieving and editing data on various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0153] As a whole, Figure 6 The communication system 600 enables connectivity between the UE, network nodes, and hosts. In this sense, the communication system 600 can be configured to operate according to predefined rules or procedures such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable second-generation, third-generation, fourth-generation, or fifth-generation (2G, 3G, 4G, or 5G) standards, or any applicable future-generation standard (e.g., sixth-generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Microwave Access Global Interoperability (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0154] In some examples, telecommunications network 602 is a cellular network implementing 3GPP standardized features. Therefore, telecommunications network 602 can support network slicing to provide different logical networks to different devices connected to it. For example, telecommunications network 602 can provide ultra-reliable low-latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive Internet of Things (IoT) services to yet another UE.

[0155] In some examples, UE 612 is configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from access network 604, the UE can be designed to send information to access network 604 according to a predetermined schedule. Additionally, the UE can be configured to operate in a single radio access technology (RAT) or multiple RAT or multiple standards mode. For example, the UE can operate using any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., configured for multiple radio dual connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR-Dual Connectivity (EN-DC).

[0156] In this example, hub 614 communicates with access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612C and / or 612D) and network nodes (e.g., network node 610B). In some examples, hub 614 may be a controller, router, content source, and analytics, or any of the other communication devices described herein with respect to the UE. For example, hub 614 may be a broadband router that enables the UE to access core network 606. As another example, hub 614 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node 610, or via executable code, scripts, procedures, or other instructions in hub 614. As another example, hub 614 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, may perform data analytics or other processing. As another example, hub 614 may be a content source. For example, for a UE acting as a virtual reality (VR) headset, display, speaker, or other media delivery device, hub 614 can retrieve VR assets, video, audio, or other media or data related to sensory information via network nodes, and then hub 614 provides them to the UE directly, after performing local processing, and / or after adding additional local content. In yet another example, hub 614 acts as a proxy server or coordinator for the UE, particularly when one or more devices in the UE are low-power IoT devices.

[0157] Hub 614 may have a constant / persistent or intermittent connection to network node 610B. Hub 614 may also allow different communication schemes and / or scheduling between hub 614 and UE (e.g., UE 612C and / or 612D) and between hub 614 and core network 606. In other examples, hub 614 is connected to core network 606 and / or one or more UEs via a wired connection. Furthermore, hub 614 may be configured to connect to a machine-to-machine (M2M) service provider via access network 604 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 610 while still being connected via hub 614 via a wired or wireless connection. In some embodiments, hub 614 may be a dedicated hub, meaning its primary function is to route communication from network node 610b to UE / from UE to network node 610B. In other embodiments, the hub 614 may be a non-dedicated hub, that is, a device capable of operating to route communication between the UE and the network node 610B, but also capable of operating as a communication start and / or end point for certain data channels.

[0158] Figure 7A UE 700 is illustrated according to some embodiments. As used herein, a UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicles, in-vehicle or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including Narrowband Internet of Things (NB-IoT) UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0159] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated equipment. Instead, the UE may represent equipment intended to be sold to or operated by a human user, but the equipment may not be associated with a particular human user, or may not have initially been associated with that particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent equipment not intended to be sold to or operated by an end user, but the equipment may be associated with a user or operated for the user's benefit (e.g., a smart meter).

[0160] UE 700 includes processing circuitry 702, operably coupled via bus 704 to input / output interface 706, power supply 708, memory 710, communication interface 712, and / or any other components, or any combination thereof. Some UEs may utilize... Figure 7 The components shown may be all or a subset of the components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0161] Processing circuitry 702 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored in memory 710 as a machine-readable computer program. Processing circuitry 702 can be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, general-purpose processors such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination thereof. For example, processing circuitry 702 may include multiple central processing units (CPUs).

[0162] In this example, the input / output interface 706 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into the UE 700. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, steering wheels, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0163] In some embodiments, power supply 708 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., electrical outlets), photovoltaic devices, or power batteries. Power supply 708 may also include power circuitry for delivering power from power supply 708 itself and / or external power sources to various parts of UE 700 via input circuitry or an interface such as a power cable. The delivered power may be used, for example, to charge power supply 708. The power circuitry may perform any formatting, conversion, or other modifications on the power from power supply 708 to suit the power supply for the various components of UE 700 to which power is supplied.

[0164] Memory 710 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrical EPROM (EEPROM), disk, optical disk, hard disk, removable tape cartridge, flash drive, etc. In one example, memory 710 includes one or more application programs 714, such as an operating system, web browser application, widget, utility engine, or other application, and corresponding data 716. Memory 710 can store any operating system or combination of operating systems from various operating systems for use by UE 700.

[0165] The memory 710 can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital multifunction disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray disc drive, holographic digital data storage (HDDS) optical disc drive, external mini dual in-line memory module (DIMM), synchronous dynamic RAM (SDRAM), and external micro DIMM. SDRAM, smart card memory (such as a tamper-proof module in the form of a Universal Integrated Circuit Card (UICC), including one or more User Identity Modules (SIMs), such as a Universal SIM (USIM) and / or an Internet Protocol Multimedia Service Identity Module (ISIM), other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." Memory 710 may allow the UE 700 to access instructions, applications, etc., stored on a temporary or non-temporary storage medium to offload or upload data. Articles of manufacture such as those utilizing a communication system may be tangibly embodied in or contained within memory 710, which may be or include a device-readable storage medium.

[0166] Processing circuitry 702 can be configured to communicate with an access network or other networks using communication interface 712. Communication interface 712 may include one or more communication subsystems and may include or be communicatively coupled to antenna 722. Communication interface 712 may include one or more transceivers for communication, such as through one or more remote transceivers capable of wireless communication with another device (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 718 and / or a receiver 720 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., antenna 722) and may share circuitry, software, or firmware, or alternatively, may be implemented separately.

[0167] In the illustrated embodiment, the communication functions of the communication interface 712 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth and NFC, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Fast User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so on.

[0168] Regardless of the type of sensor, the UE can provide the output of data captured by its sensors via its communication interface 712, through a wireless connection to the network node. Data captured by the UE's sensors can be transmitted wirelessly to the network node via another UE. The output can be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to load balance reports from multiple sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0169] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0170] When taking the form of an IoT device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting fixtures, electricity meters, robotic vacuum cleaners, voice-activated smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, power door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring equipment, vehicle parking monitoring equipment, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device (such as heart rate monitors or remotely controlled surgical robots). (Except for...) Figure 7 In addition to the other components described in UE 700 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

[0171] As another concrete example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, the UE can represent a vehicle, such as a car, bus, truck, ship, or aircraft, or other device capable of monitoring and / or reporting its operational status or performing other functions associated with its operation.

[0172] In practice, for a single use case, any number of UEs can be used together. For example, the first UE might be or integrated into the drone and provide the drone's speed information (obtained via a speed sensor) to a second UE acting as a remote controller. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling actuators) to increase or decrease the drone's speed. The first and / or second UEs may also include more than one of the functions described above. For example, the UE might include sensors and actuators and handle communication for data from the speed sensors and actuators.

[0173] Figure 8 A network node 800 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and O-RAN nodes or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0174] Base stations can be classified based on the coverage they provide (or, in other words, based on their transmit power levels); therefore, depending on the coverage provided, a base station can be called a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units, distributed units (e.g., in O-RAN access nodes), and / or remote radio units (RRUs), sometimes referred to as remote radio heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna-integrated radio. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0175] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or BS controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved servicing mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0176] Network node 800 includes processing circuitry 802, memory 804, communication interface 806, and power supply 808. Network node 800 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each component may have its own corresponding components. In some scenarios where network node 800 includes 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 can control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single separate network node in some cases. In some embodiments, network node 800 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 804 for different RATs), and some components may be reused (e.g., the same antenna 810 may be shared by different RATs). Network node 800 may also include multiple sets of various illustrated components for integration into network node 800 using different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 800.

[0177] Processing circuitry 802 may include one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software and / or coding logic, operable to provide the functionality of network node 800 alone or together with other network node 800 components (such as memory 804).

[0178] In some embodiments, the processing circuitry 802 includes a system-on-a-chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of a radio frequency (RF) transceiver circuitry 812 and a baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on the same chip or chipset, board, or unit.

[0179] Memory 804 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disks), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 802. Memory 804 may store any suitable instructions, data, or information, including computer programs, software, and applications, including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by processing circuitry 802 and utilized by network node 800. Memory 804 may be used to store any calculations performed by processing circuitry 802 and / or any data received via communication interface 806. In some embodiments, processing circuitry 802 and memory 804 are integrated.

[0180] Communication interface 806 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface 806 includes one or more ports / terminals 816 for transmitting and receiving data to and from the network, for example, via a wired connection. Communication interface 806 also includes radio front-end circuitry 818, which may be coupled to antenna 810, or in some embodiments, is part of antenna 810. Radio front-end circuitry 818 includes filter 820 and amplifier 822. Radio front-end circuitry 818 may be connected to antenna 810 and processing circuitry 802. Radio front-end circuitry 818 may be configured to modulate the signal transmitted between antenna 810 and processing circuitry 802. Radio front-end circuitry 818 may receive digital data to be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry 818 may use a combination of filter 820 and / or amplifier 822 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals may then be transmitted via antenna 810. Similarly, when receiving data, antenna 810 can collect radio signals, which are then converted into digital data by radio front-end circuitry 818. The digital data can then be passed to processing circuitry 802. In other embodiments, communication interface 806 may include different components and / or different combinations of components.

[0181] In some alternative embodiments, network node 800 does not include a separate radio front-end circuitry 818; instead, processing circuitry 802 includes the radio front-end circuitry and is connected to antenna 810. Similarly, in some embodiments, all or part of RF transceiver circuitry 812 is part of communication interface 806. In other embodiments, communication interface 806 includes one or more ports or terminals 816, radio front-end circuitry 818, and RF transceiver circuitry 812 as part of a radio unit (not shown), and communication interface 806 communicates with baseband processing circuitry 814 as part of a digital unit (not shown).

[0182] Antenna 810 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 810 may be coupled to radio front-end circuitry 818 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 810 is decoupled from network node 800 and may be connected to network node 800 via an interface or port.

[0183] Antenna 810, communication interface 806, and / or processing circuitry 802 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by network node 800. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna 810, communication interface 806, and / or processing circuitry 802 can be configured to perform any transmit operation described herein as being performed by network node 800. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0184] Power supply 808 provides power to the various components of network node 800 in a form suitable to each component (e.g., at the voltage and current levels required by each respective component). Power supply 808 may further include or be coupled to power management circuitry to supply power to the components of network node 800 for performing the functions described herein. For example, network node 800 may be connected to an external power source (e.g., the mains or electrical outlet) via input circuitry or an interface such as a cable, whereby the external power source supplies power to the power circuitry of power supply 808. As another example, power supply 808 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0185] Embodiments of network node 800 may include Figure 8Additional components beyond those shown are used to provide certain aspects of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node 800 may include a user interface device to allow information to be input into and output from network node 800. This allows users to perform diagnostic, maintenance, repair, and other management functions of network node 800.

[0186] Figure 9 Based on the block diagram of Host 900 described in this article, Host 900 can be... Figure 6 An embodiment of host 616. As used herein, host 900 can be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in server farms. Host 900 can provide one or more services to one or more UEs.

[0187] Host 900 includes processing circuitry 902 operably coupled via bus 904 to input / output interface 906, network interface 908, power supply 910, and memory 912. Other components may be included in other embodiments. These components may be characterized substantially similarly to those shown in the preceding figures (such as...). Figure 7 and Figure 8 The characteristics described for the device make its description generally applicable to the corresponding components of the host 900.

[0188] Memory 912 may include one or more computer programs, including one or more host applications 914 and data 916, which may include user data (e.g., data generated by the UE for the host 900 or data generated by the host 900 for the UE). Embodiments of the host 900 may utilize only a subset or all of the illustrated components. Host application 914 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Universal Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), Moving Picture Experts Group (MPEG), VP9) and audio codecs (e.g., Lossless Audio Codec (FLAC), Advanced Audio Coding (AAC), MPEG, G.711), including code conversion for multiple different categories, types, or implementations for UEs (e.g., mobile phones, desktop computers, wearable display systems, head-up display systems). Host application 914 may also provide user authentication and authorization checks and may periodically report health status, routing, and content availability to a central node (such as a device in the core network or at the edge). Therefore, host 900 can select and / or indicate different hosts for the UE to use for Over-The-Top (OTT) services. Host application 914 can support various protocols, such as HTTP Real-Time Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), HTTP-based Dynamic Adaptive Streaming (DASH or MPEG-DASH), etc.

[0189] Figure 10 This is a block diagram illustrating a virtualization environment 1000 in which some embodiments of functionality can be virtualized. In this context, virtualization means creating virtual versions of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments 1000 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where the virtual node does not require radio connectivity (e.g., a core network node or host), the node can be fully virtualized. In some embodiments, the virtualization environment 1000 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated via an O-2 interface by a service management and orchestration framework.

[0190] Application 1002 (which may alternatively be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in virtualization environment 1000 to implement some of the features, functions, and / or benefits of some embodiments disclosed herein.

[0191] Hardware 1004 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. The software can be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or VM monitors (VMMs)), provide VMs 1008A and 1008B (one or more of which may generally be referred to as VM 1008), and / or perform any functionality, features, and / or benefits described in conjunction with some embodiments described herein. Virtualization layer 1006 can present a virtual operating platform to VM 1008 that appears to be network hardware.

[0192] VM 1008 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 1006. Different embodiments of instances of virtual device 1002 can be implemented on one or more of VM 1008, and can be implemented in different ways. Hardware virtualization is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage, which can reside in data centers and customer premises.

[0193] In the context of NFV, VM 1008 can be a software implementation of a physical machine, whose running programs are executed as if they were running on a physical, non-virtualized machine. Each of VM 1008, and the portion of hardware 1004 that executes that VM—whether dedicated hardware for that VM or hardware shared by that VM and other VMs within VM 1008—forms a separate virtual network element. Still within the NFV context, the virtual network function is responsible for handling specific network functions running on one or more VMs 1008 above hardware 1004 and corresponds to application 1002.

[0194] Hardware 1004 can be implemented in a standalone network node with general or specific components. Hardware 1004 may implement some functions via virtualization. Alternatively, hardware 1004 may be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via management and coordination 1010, which in particular oversees the lifecycle management of application 1002. In some embodiments, hardware 1004 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more suitable network interfaces and may be used in combination with virtual components to provide radio capabilities to virtual nodes such as RANs or base stations. In some embodiments, a control system 1012 may be used to provide some signaling, which may alternatively be used for communication between hardware nodes and radio units.

[0195] Figure 11 A communication diagram is shown illustrating communication between host 1102 and UE 1106 via network node 1104 over a partial wireless connection, according to some embodiments. Reference will now be made to... Figure 11 Describe the UEs discussed in the previous paragraphs (such as...) Figure 6 UE 612A and / or Figure 7 UE 700), network nodes (such as Figure 6 Network node 610A and / or Figure 8 Network node 800) and host (such as Figure 6 Host 616 and / or Figure 9 Example implementations of the host 900 according to various embodiments.

[0196] Similar to host 900, embodiments of host 1102 include hardware such as a communication interface, processing circuitry, and memory. Host 1102 also includes software stored in or accessible by host 1102 and executable by the processing circuitry. This software includes a host application operable to provide services to remote users, such as UE 1106 connected via an OTT connection 1150 extending between UE 1106 and host 1102. In providing services to remote users, the host application can provide user data transmitted using the OTT connection 1150.

[0197] Network node 1104 includes hardware that enables it to communicate with host 1102 and UE 1106. Connection 1160 can be direct or via a core network (such as...). Figure 6The core network (606) 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 backbone network or the Internet.

[0198] UE 1106 includes hardware and software, the software being stored in or accessible by UE 1106 and executable by the UE's processing circuitry. This software includes client applications, such as web browsers or carrier-specific "applications," operable to provide services to human or non-human users via UE 1106 with the support of host 1102. In host 1102, the executing host application can communicate with the executing client application via OTT connection 1150, which terminates between UE 1106 and host 1102. In providing services to users, the UE's client application can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1150 can transmit request data and user data. The UE's client application can interact with users to generate user data that it provides to the host application via OTT connection 1150.

[0199] OTT connection 1150 can be extended via connection 1160 between host 1102 and network node 1104 and via wireless connection 1170 between network node 1104 and UE 1106 to provide connectivity between host 1102 and UE 1106. Connection 1160 and wireless connection 1170, on which OTT connection 1150 can be provided, are drawn abstractly to illustrate communication between host 1102 and UE 1106 via network node 1104, without explicitly referencing any intermediate devices and the precise routing of messages via those devices.

[0200] As an example of sending data via OTT connection 1150, in step 1108, host 1102 provides user data, which can be done by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE 1106. In other embodiments, the user data is associated with UE 1106, which shares data with host 1102 without explicit human interaction. In step 1110, host 1102 initiates a transmission carrying user data to UE 1106. Host 1102 may initiate the transmission in response to a request sent by UE 1106. This request may be caused by human interaction with UE 1106 or by the operation of a client application executed on UE 1106. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via network node 1104. Therefore, according to the teachings of the embodiments described throughout this disclosure, in step 1112, network node 1104 sends the user data carried in the transmission initiated by host 1102 to UE 1106. In step 1114, UE1106 receives user data carried in the transmission, which can be performed by a client application running on UE1106, which is associated with a host application running on host1102.

[0201] In some examples, UE 1106 executes a client application that provides user data to host 1102. The user data can be provided in response to or in reaction to data received from host 1102. Therefore, in step 1116, UE 1106 can provide user data, which can be done by executing a client application. During the provision of user data, the client application can further consider user input received from a user via the input / output interface of UE 1106. Regardless of the specific manner in which user data is provided, in step 1118, UE 1106 initiates the transmission of user data to host 1102 via network node 1104. In step 1120, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1104 receives user data from UE 1106 and initiates the transmission of the received user data to host 1102. In step 1122, host 1102 receives the user data carried in the transmission initiated by UE 1106.

[0202] One or more of the various embodiments improve the performance of the OTT service provided to the UE 1106 using the OTT connection 1150 formed by the wireless connection 1170 as the final segment.

[0203] In the example scenario, host 1102 can collect and analyze plant status information. As another example, host 1102 can process audio and video data that may have been retrieved from the UE for use in map creation. As another example, host 1102 can collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, host 1102 can store surveillance video uploaded by the UE. As another example, host 1102 can store media content (such as video, audio, VR, or AR) that it can broadcast, multicast, or unicast to the UE, or control access to that media content. As other examples, host 1102 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (such as compiling charts based on data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing, and / or transmitting data.

[0204] In some examples, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 1150 between host 1102 and UE 1106 in response to changes in measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 1150 may be implemented in the software and hardware of host 1102 and / or UE 1106. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1150 passes; the sensors may participate in the measurement process by supplying values ​​of the monitored quantities illustrated above or by supplying values ​​of other physical quantities that the software can calculate or estimate based on. Reconfiguration of the OTT connection 1150 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node 1104. Such processes and functions may be known and practiced in the art. In some embodiments, the measurement may involve dedicated UE signaling, which facilitates host 1102's measurement of throughput, propagation time, latency, etc. Measurements can be achieved by having the software enable the 1150 to send messages using an OTT connection, particularly empty or “fake” messages, while simultaneously monitoring propagation time, errors, etc.

[0205] While the computing devices described herein (e.g., UE, network node, host) may include the illustrated combinations of hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, computing devices may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0206] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of these particular embodiments, the processing circuitry may be configured to perform the described functions, whether or not instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuitry itself or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0207] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

[0208] Some examples of implementations of this disclosure are as follows:

[0209] Example 1: A method performed by a network node acting as a candidate target primary node MN for a user equipment (UE), the method comprising any one or more of the following: receiving (200) a handover request message from a source MN, the handover request message indicating that the handover request is for a conditional handover (CHO); sending (202) a secondary node add request message to one or more candidate target secondary nodes SNs for one or more primary cells (PCells); receiving (204) a secondary node add request confirmation message from the one or more candidate target SNs; generating (206) a CHO configuration for the one or more candidate target SNs; and sending (208) a handover request confirmation message to the source MN, which includes the CHO configuration in a single container (e.g., a single RRC container).

[0210] Example 2: The method described in Example 1, wherein the auxiliary node add request confirmation message includes one or more Radio Resource Control (RRC) reconfiguration messages.

[0211] Example 3: As described in Example 2, wherein the one or more RRC reconfiguration messages correspond to one or more target secondary cell group SCG configurations for a CHO having one or more candidate SCG configurations, i.e., the candidate target SN provides multiple RRC reconfiguration messages for configuring multiple candidate SCGs / PSCells from the same candidate target SN.

[0212] Example 4: The method as described in Example 3, wherein each RRC reconfiguration message is associated with a specific CHO having a candidate SCG configuration.

[0213] Example 5: The method as described in any of Examples 1 to 4, wherein the CHO configuration for the one or more candidate target SNs includes a switching command message, and the switching command message is included in a single container.

[0214] Example 6: The method as described in Example 5, wherein the single container further includes CPA and / or CPC execution conditions associated with the switching command message.

[0215] Example 7: The method as described in any of Examples 1 to 6, wherein the switching request confirmation message includes a single container having a single switching command message, the single switching command message including a CHO configuration.

[0216] Example 8: The method as described in any of Examples 1 to 6, wherein the switching request confirmation message includes a single container with multiple switching command messages, and one switching command message is configured for each CHO.

[0217] Example 9: The method as described in any of Examples 1 to 6, wherein the switching request confirmation message comprises a single container, and the single container comprises both a switching command message and an associated CPA / CPC execution condition.

[0218] Example 10: The method described in any of Examples 1 to 6, wherein the switching request confirmation message includes a single container that includes only the switching command message.

[0219] Example 11: A method performed by a network node acting as a source master node MN for a user equipment UE, the method comprising how to: send (300) a handover request message to a candidate target MN, the handover request message indicating that the handover request is for a conditional handover CHO; receive (302) a handover request confirmation message from the candidate target MN, the handover request confirmation message including two or more CHO configurations (e.g., for the same PCell) in a single container (e.g., a single RRC container); generate and send (304) an RRC reconfiguration message including two or more CHO configurations to the UE.

[0220] Example 12: The method as described in Example 11, wherein the CHO configuration includes a switching command message, and the switching command message is included in a single container.

[0221] Example 13: The method as described in Example 12, wherein the single container further includes CPA and / or CPC execution conditions associated with the switching command message.

[0222] Example 14: The method as described in Example 11, wherein the switching request confirmation message includes a single container with a single switching command message, the single switching command message including a CHO configuration.

[0223] Example 15: The method as described in Example 11, wherein the switching request confirmation message includes a single container with multiple switching command messages, and one switching command message is configured for each CHO.

[0224] Example 16: The method as described in Example 11, wherein the switching request confirmation message comprises a single container, and the single container comprises both a switching command message and associated CPA / CPC execution conditions.

[0225] Example 17: The method described in any of Examples 1 to 6, wherein the switching request confirmation message includes a single container, and the single container includes only the switching command message.

[0226] Example 18: A method performed by a network node acting as a candidate target primary node MN for a user equipment (UE), the method comprising sending (402) a message to the source MN for the UE requesting the release or modification of the CHO configuration for a candidate target primary cell PCell having two or more condition handover CHO configurations, and / or requesting the addition of at least one CHO configuration for the candidate target PCell.

[0227] Example 19: The method as described in Example 18 further includes: receiving (400) from the candidate target auxiliary node SN to which the candidate target PSCell in the CHO configuration belongs, in order to release or modify the CHO configuration including the candidate target PSCell.

[0228] Example 20: The method as described in Example 18 or 19 further includes: receiving (404) a request from the source MN for a new or updated CHO configuration for the same candidate target PCell.

[0229] Example 21: The method described in Example 20 further includes: generating (406) a new or modified CHO configuration and sending (406) the new or modified CHO configuration to the source MN.

[0230] Example 22: The method as described in Example 21 further includes: generating (406) a configuration for CPA / CPC conditions associated with the new or modified CHO configuration, wherein sending (406) the new or modified CHO configuration to the source MN includes sending (406) the new or modified CHO configuration and the configuration for the associated CPA / CPC conditions to the source MN.

[0231] Example 23: A method performed by a network node acting as a source master node MN for a user equipment UE, the method comprising any one or more of the following: receiving (500) a message from a candidate target MN requesting the release or modification of a CHO configuration for a candidate target PCell having two or more condition switching CHO configurations, and / or requesting the addition of at least a CHO configuration for the same PCell; sending (502) a request for a new or updated CHO configuration for a candidate target PCell; receiving (504) a new or modified CHO configuration from the candidate target MN; generating and sending (506) a message including the new or modified CHO configuration to the UE.

[0232] Example 24: The method as described in Example 23 further includes: receiving (504) configurations from the candidate target MN for one or more CPA / CPC conditions associated with the new or modified CHO configuration.

[0233] Example 25: The method described in Example 24, wherein the message sent to the UE further includes one or more CPA / CPC conditions.

[0234] Example 26: The method described in any of the foregoing examples further includes: obtaining user data; and forwarding the user data to a host or user device.

[0235] Example 27: A network node comprising: processing circuitry configured to perform any step as described in any of Examples 1 to 26; and a power supply circuitry configured to supply power to the processing circuitry.

[0236] Example 28: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate the transmission of user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any of Examples 1 to 26 to transmit user data from the host to the UE.

[0237] Example 29: A host as described in the preceding examples, wherein: the host's processing circuitry is configured to execute a host application that provides user data; and the UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0238] Example 30: A method implemented in a host configured to operate in a communication system, the communication system further comprising a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any of the operations described in any of Examples 1 to 26 to transmit the user data from the host to the UE.

[0239] Example 31: The method described in the foregoing embodiments further includes: at a network node, sending user data provided by the host to the UE.

[0240] Example 32: The method described in either of the two preceding examples, wherein user data is provided at the host by executing a host application that interacts with a client application executed on the UE, and the client application is associated with the host application.

[0241] Example 33: A communication system configured to provide over-the-top (OTT) service, the communication system including a host, the host including: processing circuitry configured to provide user data to a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any of Examples 1 to 26 to transmit the user data from the host to the UE.

[0242] Example 34: The communication system as described in the foregoing examples further includes: a network node; and / or a UE.

[0243] Example 35: A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising: processing circuitry configured to initiate the reception of user data; and a network interface configured to receive user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node being configured to perform any of the operations described in any of Examples 1 to 26 to receive user data for the host from a user equipment (UE).

[0244] Example 36: The host as described in the two examples above, wherein: the host's processing circuitry is configured to execute a host application that receives user data; and the host application is configured to interact with a client application executed on the UE, the client application being associated with the host application.

[0245] Example 37: The host as described in any of the two examples above, wherein initiating the reception of user data includes requesting user data.

[0246] Example 38: A method implemented by a host configured to operate in a communication system including a network node and a user equipment (UE), the method comprising: at the host, initiating the reception of user data from the UE, the user data originating from a transmission already received from the UE by the network node, wherein the network node performs any of the steps described in any of Examples 1 to 26 to receive user data from the UE for the host.

[0247] Example 39: The method described in the foregoing examples further includes: sending the received user data to the host at the network node.

[0248] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a network node acting as a candidate target master node MN for a user equipment (UE), the method comprising: Receive a (200) handover request message from the source MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to a candidate target primary cell PCell operated by the candidate target MN; Send a (202) secondary node add request message to one or more candidate target secondary nodes SN for one or more primary and secondary cell groups SCG cell PSCell; Receive one or more auxiliary node add request confirmation messages from the one or more candidate target SNs; Based on the one or more auxiliary nodes, a request confirmation message is added to generate (206) a CHO configuration for the one or more candidate target SNs, wherein, for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. as well as Send a (208) switch request confirmation message including the CHO configuration to the source MN.

2. The method as described in claim 1, wherein, The switch request confirmation message includes a separate switch command message for each CHO configuration in the CHO configuration.

3. The method as described in claim 2, wherein, For each individual handover command message, the handover request confirmation message also includes execution conditions associated with the handover command message.

4. The method of claim 1, wherein, The handover request confirmation message includes a single handover command message, which includes the CHO configuration.

5. The method of claim 4, wherein, The handover request confirmation message also includes execution conditions associated with the handover command message.

6. The method according to any one of claims 1 to 5, wherein, Each of the one or more auxiliary node add request confirmation messages includes one or more radio resource control (RRC) reconfiguration messages, the one or more RRC reconfiguration messages corresponding to one or more candidate target SCG or PSCell configurations for the CHO of the corresponding candidate target SN in the one or more candidate target SNs.

7. The method of claim 6, wherein, The one or more RRC reconfiguration messages include multiple RRC reconfiguration messages for the configuration of multiple candidate SCGs or PSCells from the same candidate target SN.

8. The method of claim 7, wherein, Each RRC reconfiguration message is associated with a specific CHO that has a candidate SCG configuration.

9. A network node for acting as a candidate target master node MN for a user equipment (UE), said network node being adapted to: Receive a (200) handover request message from the source MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to a candidate target primary cell PCell operated by the candidate target MN; Send a (202) secondary node add request message to one or more candidate target secondary nodes SN for one or more primary and secondary cell groups SCG cell PSCell; Receive one or more auxiliary node add request confirmation messages from the one or more candidate target SNs; Based on the one or more auxiliary nodes, a request confirmation message is added to generate (206) a CHO configuration for the one or more candidate target SNs, wherein, for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. as well as Send a (208) switch request confirmation message including the CHO configuration to the source MN.

10. The network node of claim 9 is also suitable for performing the method of any one of claims 2 to 8.

11. A network node for acting as a candidate target primary node MN for a user equipment (UE), the network node including processing circuitry configured to cause the network node to: Receive a (200) handover request message from the source MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to a candidate target primary cell PCell operated by the candidate target MN; Send a (202) secondary node add request message to one or more candidate target secondary nodes SN for one or more primary and secondary cell groups SCG cell PSCell; Receive one or more auxiliary node add request confirmation messages from the one or more candidate target SNs; Based on the one or more auxiliary nodes, a request confirmation message is added to generate (206) a CHO configuration for the one or more candidate target SNs, wherein, for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target SCGs or PSCells for each of the one or more candidate target SNs. as well as Send a (208) switch request confirmation message including the CHO configuration to the source MN.

12. The network node as described in claim 11, wherein, The processing circuitry is further configured to cause the network node to perform the method as described in any one of claims 2 to 8.

13. A method performed by a network node acting as a source master node MN for a user equipment (UE), the method comprising: Send a (300) handover request message to the candidate target MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to the candidate target primary cell PCell operated by the candidate target MN; Receive (302) a handover request confirmation message from the candidate target MN, including CHO configuration for one or more candidate target secondary node SNs, wherein, for the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target secondary cell group SCG or primary SCG cell PSCell for each of the one or more candidate target SNs. Generate and send (304) a Radio Resource Control (RRC) reconfiguration message including the CHO configuration to the UE.

14. The method of claim 13, wherein, The switch request confirmation message includes a separate switch command message for each CHO configuration in the CHO configuration.

15. The method of claim 14, wherein, For each individual handover command message, the handover request confirmation message also includes execution conditions associated with the handover command message.

16. The method of claim 13, wherein, The handover request confirmation message includes a single handover command message, which includes the CHO configuration.

17. The method of claim 16, wherein, The handover request confirmation message also includes execution conditions associated with the handover command message.

18. A network node for acting as a source master node MN for a user equipment (UE), said network node being adapted to: Send a (300) handover request message to the candidate target MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to the candidate target primary cell PCell operated by the candidate target MN; Receive (302) a handover request confirmation message from the candidate target MN, including CHO configurations for one or more candidate target secondary nodes SN, wherein, For the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target secondary cell groups (SCGs) or primary SCG cell PSCells for each of the one or more candidate target SNs. Generate and send (304) a Radio Resource Control (RRC) reconfiguration message including the CHO configuration to the UE.

19. The network node of claim 18 is also adapted to perform the method of any one of claims 14 to 17.

20. A network node for acting as a source master node MN for a user equipment (UE), the network node including processing circuitry configured to cause the network node to: Send a (300) handover request message to the candidate target MN, the handover request message indicating that the handover request is a conditional handover CHO for the UE to the candidate target primary cell PCell operated by the candidate target MN; Receive (302) a handover request confirmation message from the candidate target MN, including CHO configurations for one or more candidate target secondary nodes SN, wherein, For the candidate target PCell, the CHO configuration includes one or more CHO configurations for one or more candidate target secondary cell groups (SCGs) or primary SCG cell PSCells for each of the one or more candidate target SNs. Generate and send (304) a Radio Resource Control (RRC) reconfiguration message including the CHO configuration to the UE.

21. The network node as described in claim 20, wherein, The processing circuitry is also configured to cause the network node to perform the method as described in any one of claims 14 to 17.

22. A method performed by a network node acting as a candidate target master node MN for a user equipment (UE), the method comprising: Send (402) a message to the source MN for the UE to request the release or modification of the CHO configuration for a candidate target primary cell PCell with two or more condition handover CHO configurations, and / or request the addition of at least one CHO configuration for the candidate target PCell.

23. The method of claim 22, further comprising: Receive (400) a request from the candidate target auxiliary node SN to which the candidate target PSCell belongs in the CHO configuration to release or modify the CHO configuration that includes the candidate target PSCell.

24. The method of claim 22 or 23, further comprising: Receive (404) a request from the source MN for a new or updated CHO configuration for the same candidate target PCell.

25. The method of claim 24, further comprising: Generate (406) the new or modified CHO configuration and send (406) the new or modified CHO configuration to the source MN.

26. The method of claim 25, further comprising: Generating (406) a configuration for the execution conditions associated with the new or modified CHO configuration, wherein sending (406) the new or modified CHO configuration to the source MN includes sending (406) the new or modified CHO configuration and the configuration for the associated execution conditions to the source MN.

27. A network node for acting as a candidate target primary node MN for a user equipment (UE), said network node being adapted to: Send (402) a message to the source MN for the UE to request the release or modification of the CHO configuration for a candidate target primary cell PCell with two or more condition handover CHO configurations, and / or request the addition of at least one CHO configuration for the candidate target PCell.

28. The network node of claim 27 is also adapted to perform the method of any one of claims 23 to 26.

29. A network node for acting as a candidate target primary node MN for a user equipment (UE), the network node including processing circuitry configured to cause the network node to: Send (402) a message to the source MN for the UE to request the release or modification of the CHO configuration for a candidate target primary cell PCell with two or more condition handover CHO configurations, and / or request the addition of at least one CHO configuration for the candidate target PCell.

30. The network node as described in claim 29, wherein, The processing circuitry is also configured to cause the network node to perform the method as described in any one of claims 23 to 26.

31. A method performed by a network node acting as a source master node MN for a user equipment (UE), the method comprising: Receive (500) messages from the candidate target MN to request the release or modification of the CHO configuration for the candidate target primary cell PCell with two or more condition switching CHO configurations, and / or to request the addition of at least one CHO configuration for the same PCell. Send (502) a request for a new or updated CHO configuration for the candidate target PCell; Receive the new or modified CHO configuration from the candidate target MN (504); Generate and send (506) a message including the new or modified CHO configuration to the UE.

32. The method of claim 31, further comprising: Receive (504) configuration from the candidate target MN for one or more execution conditions associated with the new or modified CHO configuration.

33. The method of claim 32, wherein, The message sent to the UE also includes one or more execution conditions.

34. A network node for acting as a source master node MN for a user equipment (UE), said network node being adapted to: Receive (500) messages from the candidate target MN to request the release or modification of the CHO configuration for the candidate target primary cell PCell with two or more condition switching CHO configurations, and / or to request the addition of at least one CHO configuration for the same PCell. Send (502) a request for a new or updated CHO configuration for the candidate target PCell; Receive the new or modified CHO configuration from the candidate target MN (504); Generate and send (506) a message including the new or modified CHO configuration to the UE.

35. The network node of claim 34 is also suitable for performing the method of any one of claims 32 to 33.

36. A network node for acting as a source master node MN for a user equipment (UE), the network node including processing circuitry configured to cause the network node to: Receive (500) messages from the candidate target MN to request the release or modification of the CHO configuration for the candidate target primary cell PCell with two or more condition switching CHO configurations, and / or to request the addition of at least one CHO configuration for the same PCell. Send (502) a request for a new or updated CHO configuration for the candidate target PCell; Receive the new or modified CHO configuration from the candidate target MN (504); Generate and send (506) a message including the new or modified CHO configuration to the UE.

37. The network node as described in claim 36, wherein, The processing circuitry is further configured to cause the network node to perform the method as described in any one of claims 32 to 33.

Images