Mobility in wireless communication systems
By determining and indicating candidate primary secondary cells operating on different frequencies, the network node expands the choice of cells during handover, addressing limitations in existing technologies and enhancing user equipment throughput and mobility in wireless communication systems.
Patent Information
- Application Number
- GB2023007112
- Authority / Receiving Office
- GB · GB
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-13
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
TECHNOLOGICAL FIELD Various example embodiments relate to wireless communication systems, and more particularly, to facilitating mobility within such wireless communication systems. BACKGROUND As a user equipment (UE) moves through a wireless communication system, it may move through cells that comprise regions of radio coverage that are supported by one or more network access nodes. Maintaining an ability for a UE to communicate effectively with the wireless communication system as it moves through regions of radio coverage is typically referred to as mobility. Complexity may arise for user equipment that are configured to use carrier aggregation and support dual connectivity such that the user equipment is enabled to connect concurrently to a primary cell and primary secondary cell, the primary secondary cell improving throughput for the user equipment. A handover in the primary cell may affect the configuration of the connection with the primary secondary cell. BRIEF SUMMARY The scope of protection sought for various example embodiments of the invention is set out by the independent claims. The example embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention. According to various, but not necessarily all, example embodiments of the invention there is provided a network node for supporting providing radio coverage to user equipment that are configured to support carrier aggregation and dual connectivity, the carrier aggregation comprising at least a first serving frequency of a serving primary cell and at least one further serving frequency of at least one serving secondary cell, said network node comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network node at least to: determine at least one cell that is a potential candidate cell for addition as a primary secondary cell during handover with secondary cell group of a user equipment from a serving network node to said network node and where said frequency of operation of said at least one cell is different to said serving frequency of the serving primary cell and any serving secondary cells for said user equipment; to generate an indication of said frequency of operation of said at least one potential candidate cell for transmission to said serving network node. When performing a handover with secondary cell group, measurements transmitted by a user equipment are used to select the cells for handover. Conventionally the measurements transmitted in a measurement report by a user equipment that are useful for selecting a preferred primary secondary cell are limited to a best neighbour cell operating at the same frequency as each of the serving secondary cells. This limits the choice of potential primary secondary cells in a handover. It was recognised that a non-serving network node is aware of neighbouring cells that may well be effective primary secondary cells. However, such cells may not operate in one of the serving frequencies of the current secondary cells and as such would be precluded from becoming a primary secondary cell during the handover or cell change as a user equipment would not perform measurements for these cells and thus, this information would not be provided to the serving cell. This is addressed by the network node determining cells as candidate primary secondary cells and when the frequency of operation or radio coverage of such cells is not one of a serving frequency of the serving primary or secondary cell to transmit an indication of this frequency to the serving network node. In this way embodiments seek to increase the choice of primary secondary cells, which cells increase the throughput of the user equipment, by providing an indication of which additional measurements to be made by the user equipment might allow potential candidate primary secondary cells to be considered and perhaps added during any handover. A handover may include a cell change and / or cell switch. Procedures of embodiments support the UE to change / switch from serving cells to neighbouring / candidate / target cells while maintaining the communication via cellular / radio network to a global communication network. In some example embodiments, the measurements made by the user equipment may comprise at least one of the following: layer one signal strength or layer one signal quality measurements. A secondary cell may be one that provides radio coverage within the radio coverage of a corresponding primary cell. A secondary serving cell is one that is under the control 2 of the same network node as the primary serving cell, but which provides radio coverage in a different serving frequency. In some example embodiments, the measurements are for enabling a serving master node of the serving primary cell to initiate a conditional handover with a secondary cell group. In some example embodiments, said network node is caused to determine which of said at least one potential candidate primary secondary cells is a preferred candidate cell and to generate said indication of said frequency only for said preferred candidate primary secondary cells. Where there are many potential candidate primary secondary cells, then it may be advantageous for the network node to select one or a subset that are likely to be preferred during a handover and only indicate the frequencies of these cells. In some example embodiments, said network node is caused to determine which of said at least one potential candidate primary secondary cells are preferred candidate primary secondary cells in response to a message received from at least one of an operations administration and maintenance OAM message, or a message generated by a self-organising network SON module or a machine learning, artificial intelligence AI / ML module associated with the network. In some example embodiments, said message received from said OAM, SON, AI / ML comprises an indication of which said plurality of potential candidate primary secondary cells are likely to provide preferred coverage for said user equipment. In some example embodiments, said indication of preferred candidate primary secondary cell is based on location, mobility and / or configuration. The cell that is likely to be the preferred primary secondary cell will depend on a number of factors including at least one of the following: the cell’s location, the UE’s location, the UE’s mobility and / or the configuration of the UE and / or the cell. In some example embodiments, said network node is further caused to transmit said indication of said frequency to said serving network node as a handover information element. In some example embodiments, said indication of said frequency is sent via an interface between network nodes, such as as part of an Xn setup procedure, or as part of an Xn NG-RAN node configuration update procedure. In some example embodiments, said indication of said frequency is sent in one of the following: an update, update acknowledgment, a request or a response. In some example embodiments, said network node is caused to: determine that said frequency of operation of said at least one cell is different to said serving frequency of said serving primary cell and any serving secondary cells based on receiving a message from said serving network node, said message indicating said frequencies of operation of said serving primary cell and of said any serving secondary cells, and based on determining whether said at least one potential candidate cell for addition as a primary secondary cell during handover with secondary cell group to said network node provides radio coverage using a frequency different to said frequencies of operation of said serving primary cell and serving secondary cells; and based on the determining, generating said indication of said frequency. In some example embodiments, said network node being caused while acting as a serving network node to a user equipment to: respond to receipt from a target network node of an indication of at least one frequency of operation of at least one potential candidate primary secondary cell, said at least one frequency of operation being different to said first and said at least one further serving frequencies, the responding comprising generating an indication for transmission to a user equipment indicating said user equipment should perform measurements including at least one measurement at said at least one frequency of operation of said at least one potential candidate primary secondary cell that is different to said first and said at least one further serving frequencies. In some example embodiments, said network node is caused to: receive a handover request from said serving network node, said handover request comprising a measurement report from a user equipment, said measurement report including at least one measurement at said at least one frequency for said potential candidate primary secondary that is different to said frequencies of operation of said serving primary and secondary cells; and to forward said at least one measurement to a network node supporting providing radio coverage in said potential candidate primary secondary cell. The at least one measurement may be forwarded as part of a secondary node addition request. In some example embodiments, said network node is caused: to receive a measurement report from said user equipment, said measurement report including said at least one measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies, to generate a handover request for transmission to said target network node, said handover request including an indication of results of said user equipment measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies. According to various, but not necessarily all, example embodiments of the invention there is provided according to one aspect, a method performed at a network node for supporting providing radio coverage to user equipment that are configured to support carrier aggregation and dual connectivity, the carrier aggregation comprising at least a first serving frequency of a serving primary cell and at least one further serving frequency of at least one serving secondary cell, said method comprising: determining at least one cell that is a potential candidate cell for addition as a primary secondary cell during a handover with secondary cell group of a user equipment from a serving network node to said network node and when said frequency of operation of said at least one cell is different to said serving frequency of a serving primary cell and any serving secondary cells for said user equipment, generating an indication of said frequency of operation of said at least one potential candidate primary secondary cell for transmission to said serving network node. In some example embodiments, the method comprises determining which of said at least one potential candidate primary secondary cell is a preferred candidate cell and generating said indication of said frequency only for said preferred candidate primary secondary cells. In some example embodiments, the method comprises determining which of said potential candidate primary secondary cells are preferred candidate primary secondary cells in response to a message received from at least one of an operations administration and maintenance OAM message, or a message generated by a selforganising network SON module, or a machine learning, artificial intelligence AI / ML module associated with the network. In some example embodiments, said message received from said OAM, SON, AI / ML comprises an indication of which said plurality of potential candidate secondary cells are likely to provide preferred coverage for said user equipment. In some example embodiments, the method comprises transmitting said indication of said frequency to said serving network node as a handover information element. In some example embodiments, the method comprises: receiving a handover request from said serving network node, said handover request comprising a measurement report from a user equipment, said measurement report including at least one measurement at said at least one frequency for said potential candidate primary secondary that is different to said frequencies of operation of said serving primary and secondary cells; and forwarding said at least one measurement to a network node supporting providing radio coverage in said potential candidate primary secondary cell. In some example embodiments, the method comprises determining that said frequency of operation of said at least one cell is different to said serving frequency of said serving primary cell and any serving secondary cells based on receiving a message from said serving network node, said message indicating said frequencies of operation of said serving primary cell and of said any serving secondary cells, and based on determining whether said at least one potential candidate cell for addition as a primary secondary cell during handover with secondary cell group to said network node provides radio coverage using a frequency different to said frequencies of operation of said serving primary cell and serving secondary cells, and based on the determining generating said indication of said frequency of operation. In some example embodiments, the method comprises while acting as a serving network node to a user equipment: performing the steps of: responding to receipt from a target network node of an indication of at least one frequency of operation of at least one potential candidate primary secondary cell, said at least one frequency of operation being different to said first and said at least one further serving frequencies, the responding comprising generating an indication for transmission to a user equipment indicating said user equipment should perform measurements including at 6 least one measurement at said at least one frequency of operation of said at least one potential candidate primary secondary cell that is different to said first and said at least one further serving frequencies. In some example embodiments, the method comprises receiving a measurement report from said user equipment, said measurement report including said at least one measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies, and in response generating a handover request for transmission to said target network node said handover request including an indication of results of said user equipment measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies. According to various, but not necessarily all, example embodiments of the invention there is provided a computer program comprising computer readable instructions which when executed by a processor on a network node cause said network node to perform a method according to said one aspect or some example embodiments of said one aspect. According to various, but not necessarily all, example embodiments of the invention there is provided a network node for supporting providing radio coverage to user equipment that are configured to support carrier aggregation and dual connectivity, the carrier aggregation comprising at least a first serving frequency of a serving primary cell and at least one further serving frequency of at least one serving secondary cell, said network node comprising: means for determining at least one cell that is a potential candidate cell for addition as a primary secondary cell during handover with secondary cell group of a user equipment from a serving network node to said network node; where said frequency of operation of said at least one cell is different to said serving frequency of the serving primary cell and any serving secondary cells for said user equipment; and means for generating an indication of said frequency of operation of said at least one potential candidate cell for transmission to said serving network node. The means may perform the optional features set out in relation to the apparatus mentioned above. According to various, but not necessarily all, example embodiments of the invention there is provided a non-transitory computer readable medium comprising program instructions stored thereon, which when executed by a processor on a network node cause said network node to: perform at least the following: determine at least one cell that is a potential candidate cell for addition as a primary secondary cell during handover with secondary cell group of a user equipment from a serving network node to said network node; and when said frequency of operation of said at least one cell is different to said serving frequency of the serving primary cell and any serving secondary cells for said user equipment; to generate an indication of said frequency of operation of said at least one potential candidate cell for transmission to said serving network node. The instructions may be for performing the optional features set out in relation to the method mentioned above. Further particular and preferred aspects are set out in the accompanying independent and dependent claims. Features of the dependent claims may be combined with features of the independent claims as appropriate, and in combinations other than those explicitly set out in the claims. Where an apparatus feature is described as being operable to provide a function, it will be appreciated that this includes an apparatus feature which provides that function or which is adapted or configured to provide that function. BRIEF DESCRIPTION Some example embodiments will now be described with reference to the accompanying drawings in which: Fig. 1 schematically illustrates cells for which measurements may be present in the measurement report generated by a user equipment to support condition handover (CHO) with secondary cell group (SCG) according to a first embodiment; Fig. 2 schematically illustrates cells for which measurements may be present in the measurement report generated by a user equipment to support CHO with SCG according to a second embodiment; Fig. 3A schematically shows the mobility of a user equipment supporting carrier aggregation and dual connectivity in relation to primary and secondary cells; Fig.3B schematically shows the user equipment and the network nodes providing the radio coverage cells shown in Fig. 3A; Fig. 4 shows a high-level an exemplary signalling diagram of CHO with 5G secondary cell group; Fig.5 details the Measurement Configuration and Measurement Reporting shown in step 0 of Fig. 4; Fig. 6 shows an extract of a measResultServingMOList; Fig. 7 shows a servingCellMO is a measObjectld that points to a MeasObjectNR whose ssbFrequency is equal to the frequency of a serving cell; Fig. 8 shows Step 0. Measurement Configuration and Reporting with best neighbouring cell reported for each serving cell; Fig. 9 provides an illustration of the change in the MeasConfig to configure the UE to measure and report the best neighbouring cells on candidate (non-serving) carrier frequencies; Fig. 10 provides an illustration of the change in the MeasResults to allow the UE to report measurements on multiple best neighbouring cells on carrier frequencies different from that of the serving cells and an illustration of the scenario where measldl linked to MeasObjectldl triggers a Measurement Report message; Fig. 11 illustrates the scenario where measld2 linked to MeasObjectld2 triggers a Measurement Report message; Fig. 12 shows how the proposal makes it possible to prepare the SN addition for a PSCell on a candidate non-serving frequency F3 and the SN addition for a PSCell on a candidate non-serving frequency F4 upon receipt of a single Measurement Report; Fig. 13 illustrates how to report the measurements for several best neighbouring cells per serving frequency. Fig. 14 shows a Xn Setup procedure; and Fig. 15 shows a NG_RAN node configuration update procedure. DETAILED DESCRIPTION Before discussing the example embodiments in any more detail, first an overview will be provided. When performing a handover with secondary cell group, the measurements conventionally transmitted in an information element by a user equipment for potential candidate primary secondary cells are limited to a best neighbour cell operating at the same frequency as each of the serving secondary cells. This limits the choice of potential primary secondary cell. Embodiments seek to increase the choice of primary secondary cells in a handover by providing additional measurements relating either to multiple candidate primary secondary cells at a serving frequency of the serving 9 secondary cells (used for carrier aggregation) or at a frequency different to the current serving frequencies, that is the serving primary and serving secondary cells. These measurements are sent in a single measurement report, thereby providing the information without increasing latency. Fig. 1 schematically illustrates a plurality of serving cells 10, 12A, 12B comprising a serving primary cell 10 operating at a first serving frequency F1, and two serving secondary cells 12a and 12b operating respectively at frequencies F2 and F5. The radio coverage of these serving secondary cells is at least partially within the radio coverage of the serving primary cell and a user equipment configured for carrier aggregation may be able to transmit / receive data via each of the cells at the respective serving frequencies. Fig.1 also schematically shows cells 20, 22a and 22b that represent candidate primary and secondary cells for a potential handover. The user equipment generates a measurement report for transmission to the network node for use in a handover decision, and the measurement report may include measurements for a number of candidate primary cells 20 each operating at the serving frequency F1 and one best neighbouring cell 22a, 22b for each of the frequencies of the serving secondary cells, that is F2 and F5. These measurements are present in a conventional UE measurement report transmitted to a source node for conditional handover with secondary cell group. This report provides a limited number of secondary cells that can be considered and prepared in a handover situation and embodiments seek to increase the number of potential target primary secondary cells and thereby improve the addition of secondary nodes in the handover. In this example embodiment, measurements for neighbouring cells 22c operating at frequency F3 and the neighbouring cells 22d operating at frequency F4 are transmitted in the same measurement report as the measurements for the potential target cells operating at the serving frequencies. Fig. 2 shows an alternative example embodiment where the measurement report, rather than providing additional cell measurements for cells that operate at non-serving frequencies, additional cells 22c and 22d that operate at the same serving frequency as the serving secondary cells are provided in the measurement report. Thus, in this case as in the earlier example embodiment additional cell measurements relevant for candidate primary secondary cells are transmitted in the user equipment measurement report providing an increase in choice of cells that may be added as primary secondary 10 cells on handover. As these measurements appear in the same single measurement report there is no additional latency and the selected cells can be prepared for addition during the handover procedure. Fig.3A is an example of the configuration of a two-layer radio coverage network. Let the UE be configured with a CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different serving carrier frequencies of the CA configuration. A serving cell refers to the PCell (F1), the first SCell (F2) or the second SCell (F5). Fig. 3A shows the coverage area of a serving primary cell 10 PCell 1 (operating at frequency F1 under network node MN1 (master node 1)) and a target primary cell 20 PCell2 (operating at frequency F1 under network node MN2, (master node 2). The smaller lighter circles show the coverage area of primary secondary PSCells operating at different frequencies. In the PCelU coverage, PSCelU and PSCell2 have coverage areas shown schematically by the circles or bubbles and operate at frequencies of F10 and F20, respectively. Similarly, in the target primary cell PCell2 coverage, the PSCell3 and PSCell4 coverage areas and operate at frequencies of F3 and F4, respectively. The UE mobility direction is shown with an arrow in this example. Fig. 3A also shows show first serving SCell (F2) and second serving SCell (F5) of the CA configuration. Fig. 3A schematically shows a CHO with SCG change. The UE has dual connectivity and is served by cells PCelU (F1) and PSCell2 (F20) and is moving towards target MN2 and will handover to have dual connectivity with cells PCell2 (F2) and PSCell 3 (F3). So in the CHO both the PCell and PSCell change. As is shown in Fig. 3A, the PSCell3 is in the border of PCelU and PCell2. Whenever the UE handovers to PCell2, it can also enter the coverage of the PSCell3. In R17 / R18 CHO with SCG, MN2 may require configuring the UE with an SCG made of PSCell3 if the UE moves from the shown cell border. To determine whether the UE enters the coverage of PSCell3 when it moves towards PCell2, MN1 (controlling PCelU) should configure the UE with PSCell3 frequency (F3) measurements which will be reported to the MN 1 (controlling PCelU) by the UE. Where the MeasurementReport sent from the user equipment includes measurements for target PCell2 on a neighbouring frequency F1 and cells on a serving frequency F1, F2 and F5 and additionally PSCell3 on the 11 non-serving frequency F3. Then the MN1 (controlling PCelU) will forward to the MN2 the PCell2 measurements along with the PSCell3 measurements. The MN2 may reserve resources for PSCell3 directly while reserving resources for PCell2 which avoids the PSCell addition after the PCell handover completion. The target MN2 can determine the PSCells which border the source PCelU and associated frequencies (like F3) for these PSCells as follows. The UE may handover to PCell2 without any PSCell3 connectivity and then the MN2 (controlling PCell2) can setup (shortly after the handover) the dual connectivity (DC) with the strongest PSCell under the PCell2 coverage. The decision by MN2 to setup DC can be based on UE measurements that are reported by the UE to MN2 after the handover. This will clearly indicate to the MN2 (controlling PCell2) that the PSCell3 is close to the border of PCelU. In that way, the MN2 can learn the PSCell frequencies that are relevant in the cell border of MN1, and MN2 can inform MN1 about those relevant frequencies. In this example, the MN2 will inform MN1 (for example via Frequencies for SCG Addition during Handover Information IE the Xn NG-RAN NODE CONFIGURATION UPDATE message) that the cell border between PCelU and PCell2 requires the UEs to be configured with the measurements of frequency F3. Since the frequency F4 is not relevant to the cell border, but only relevant to the coverage area of PCell2, this frequency may not be reported to the MN1 which avoids any unnecessary measurement configuration of F4 when the UE is served by PCelU. Fig.3B schematically shows the configuration of network nodes such as the master nodes MN1 30 and user equipment 50. The network nodes MN2, and the secondary nodes SN1 and SN2 are configured in a similar way to MN1. Network node 30 comprises a memory 34 for storing computer readable instructions, processing circuitry 32 for executing the instructions and transmitting and receiving circuitry 36 for transmitting and receiving messages and data to user equipment and other network nodes. User equipment 50 comprises a memory 54 for storing computer readable instructions, processing circuitry 52 for executing the instructions and transmitting and receiving circuitry 56 for transmitting and receiving messages and data. User equipment also comprises sensing circuitry for performing measurements of signal strength and / or signal quality measurements of reference signals for example broadcast by different network nodes. To put the above in context, conditional handover CHO which in this example is with 5G secondary cell group SCG is considered in the embodiments, and is illustrated in Fig. 4 which provides at a high-level an exemplary signalling diagram of this procedure. In step 0, the source MN master node configures the UE 50 with measurement and reporting configuration, in accordance with TS 38.331 V17.4.0. These reporting configurations are for example of type event-triggered with event A3 (triggered when a neighbour cell becomes better than a special cell SpCell by an offset) or A5 (SpCell becomes worse than threshold 1, while neighbour becomes better than threshold 2). SpCell can be a Primary Cell (spCell of a master cell group) or PSCell (spCell of a secondary cell group). Subsequently, the UE performs the measurements configured by the source MN. When the entering conditions defined for event A3 or A5 are met during a time defined as time to trigger, the UE initiates the procedure of measurement reporting to send measurement results to the source MN. The step 0 is a set of procedures detailed in the following paragraphs and constitutes the core of procedures to which embodiments apply. In this application, step 0 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells (primary cell spCell of a master cell group) for conditional handover. These event-triggered measurement reporting criteria use eventA3 and eventA5. In step 1, the source MN starts the CHO procedure by initiating the Xn (network interface) Handover Preparation procedure including MCG (master cell group_ configuration and, if the UE is configured with an SCG (secondary cell group), SCG configuration. The source MN includes the (source) SN (secondary node) UE XnAP (Xn application protocol) ID, SN ID, the UE context in the (source) SN and the CHO Information Request IE in the Handover Request message. In step 2, if the candidate MN decides to keep the UE context in the SN, the candidate MN sends the SN Addition Request message to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the SN Addition Request message to the candidate SN including the UE 13 context in the source SN that was established by the source MN. Otherwise, the candidate MN may send the SN Addition Request message to the candidate SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. Within the SN Addition Request message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE XnAP ID in the source MN, in order to indicate that the SN Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. In step 3, the (candidate) SN replies with the SN Addition Request Acknowledge message. The (candidate) SN may include the indication of the full or delta RRC configuration. In step 3a, for the SN terminated bearers using MCG resources, the candidate MN provides Xn-U DL TNL (Xn user plane downlink transport network layer) address information in the Xn-U Address Indication message. In step 4, the candidate MN includes within the Handover Request Acknowledge message the MN RRC reconfiguration message to be sent to the UE in order to perform the conditional handover and may also provide forwarding addresses to the source MN. If PDU (protocol data unit) session split is performed in the target side during handover procedure, more than one data forwarding addresses corresponding to each node are included in the Handover Request Acknowledge message. The candidate MN indicates to the source MN that the UE context in the SN is kept if the candidate MN and the SN decided to keep the UE context in the SN in step 2 and step 3. In step 4a, the source MN sends the Xn-U Address Indication message to the (source) SN. This Xn-U Address Indication message notifies conditional handover to the (source) SN, which may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. In step 5, the source MN sends an RRC reconfiguration message to the UE, including the CHO configuration, i.e., a list of RRC reconfiguration* messages and associated execution conditions, in which each RRC reconfiguration* message contains an MCG configuration and possibly an SCG configuration in the RRC reconfiguration** message received from the candidate SN in step 3. In step 6, the UE applies the RRC reconfiguration message received in step 5, stores the CHO configuration, and replies to the MN with an RRC reconfiguration complete message. In step 7 / 8, the UE maintains connection with the source MN and, if the UE is configured with a PSCell, with the source PSCell, after receiving CHO configuration, and starts evaluating the CHO execution condition for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate cell, synchronizes to that candidate cell and completes the RRC handover procedure by sending RRC reconfiguration complete* message to the target MN. If the stored configuration for the selected candidate cell includes an SCG configuration, the UE includes an embedded SN RRCReconfigurationComplete** message for the target SN. The UE releases stored CHO configurations after successful completion of RRC handover procedure. In step 9, if configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. In step 10, if the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via SN Reconfiguration Complete message. In step 11, the target MN sends the Handover Success message to the source MN to inform that the UE has successfully accessed the target cell. In step 12a / b, the source MN sends SN Release Request message to the (source) SN including a Cause indicating MCG mobility. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. The (source) SN acknowledges the release request. In step 12c, the source MN sends XN-U Address Indication message to the (source) SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. In step 12d, the source MN sends the Handover Cancel message toward the other signalling connections or other candidate MNs, if any, to cancel CHO for the UE. In step 12e / f, If the target MN is configured with other candidate PCell(s) associated with other candidate SN(s) than the target SN, the target MN sends the SN Release Request message(s) to the corresponding candidate SN(s). Other candidate MN(s) send(s) the SN Release Request message(s) to other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. In step 13a, the (source) SN sends the Secondary RAT (radio access technology) Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR / E-UTRA radio. In step 13b, the source MN sends the Secondary RAT Data Usage Report message to AMF to provide information on the used NR / E-UTRA resource. In step 14, for bearers using RLC AM, the source MN sends the SN Status Transfer message to the target MN, including, if needed, SN Status received from the source SN. The target MN forwards the SN Status to the target SN, if needed. In step 15, if applicable, data forwarding takes place from the source side (i.e., source MN or source SN). If the SN is kept, data forwarding may be omitted for the SN terminated bearers or QoS flows kept in the SN. In step 16-19, the target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEI Ds (tunnel endpoint identifier) for one PDU session in the Path Switch Request message, multiple UL TEID of the UPF (user plane function) for the PDU session should be included in the Path Switch Ack message in case there is TEID update in UPF. In step 20, the target MN initiates the UE Context Release procedure towards the source MN. In step 21, upon reception of the UE Context Release message from source MN, the (source) SN releases C-Plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE contest kept indication was included in the SN Release Request message in step 12a. Below, we describe below an example scenario where the UE is served by the MN with a procedure other than handover. If the UE has connected to the MN via handover, then the RRC Reconfiguration is given to the UE via initial source MN. Later in the application we describe alternative scenarios where the measurement configuration is provided only via source MN. In embodiments the measurement configuration may be given to the UE in the target cell’s RRC Reconfiguration (either via HO command, or via Conditional Reconfiguration). It should be noted that Step 0 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. Fig. 5 details the Measurement Configuration and Measurement Reporting shown in step 0 of Fig. 4. In step 0, the source MN applies the procedure of Measurement Configuration, and the UE applies the procedure of Measurement Reporting whose purpose is to transfer measurement results from the UE to the source MN. The step 0 is a set of procedures detailed in the section below and constitutes the core procedures to which the application relates. In step 0.1 / 0.2, the source MN sends to the UE a RRCReconfiguration message including intra-frequency measurements configurations, to detect candidate PCells for conditional handover. In accordance with TS 38.331 V17.4.0, a reporting condition is identified with a measurement identifier noted Measld. The measld is linked to a measurement configuration identified with measObjectld and an associated reporting configuration identified with reporting configuration identifier, reportConfigld. The IE MeasObjectld is used to identify a Measurement Object configuration. The IE ReportConfigld is used to identify a Measurement Reporting configuration. Among other parameters defined in TS 38.331 V17.4.0, the Measurement Object defines the frequency of the measurements which is here the frequency of the serving PCell as the conditional handover is intra-frequency. The Reporting Configuration defines the parameters of the eventA3 (or eventA5) to detect candidate PCells) such as offsets, thresholds, or time-to-trigger. The eventA3 (or eventA5) for the UE to detect candidate PCells for the conditional handover are set with a threshold typically, 2-3dB lower than legacy (non-conditional) handover threshold. The above eventA3 (or eventA5) describes the example of a reporting configuration which is used for triggering the reporting of intra-frequency candidate PCell. In the scope of this invention, any event can be configured, i.e., A1 to A6 + X1, X2 and D1 that is to say all events that are EventTriggerConfig. In step 0.3, the UE detects cells, neighbours of the PCell, as PCell candidates for the conditional handoverand denoted here PCelU and PCell2 In step 0.4, the UE sends a Measurement Report message including measurement results associated with each serving cell of the carrier aggregation (CA) configuration: the results on the PCell and multiple best neighbouring cells at the frequency of this PCell, the results on each SCell and the single best neighbouring cell at the frequency of this SCell. Fig. 6 shows an extract of a measResultServingMOList (MCG SCell at F5 not shown) for a CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5). Let the UE be configured with an CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different carrier frequencies of the CA configuration. A serving cell refers to the PCell (F1), the first SCell (F2) or the second SCell (F5). In the context of R17 / R18 conditional handover (CHO) with secondary cell group (SCG) and when the UE sends a MeasurementReport for eventA3 (or eventA5) including intra-frequency (F1) candidate PCells for CHO, the UE can also report a best neighbouring cell (denoted BestNeighCell) for each serving cell. If the PCell is on F1, the measurements on F2 and F5 may require the configuration of measurement gaps. When the entering conditions are met on F1 for eventA3 (or eventA5) during a time to trigger, the UE sends to the source MN a MeasurementReport including the measurement result for the best neighbouring cell (denoted measResultBestNeighCell as per TS 38.331 V17.4.0) for each serving cell. In accordance with TS 38.331 V17.4.0, the measResultServingMOList includes several measResultBestNeighCell. IE measResultServingMOList indicates Measured results of measured cells with reference signals indicated in the serving cell measurement objects including measurement results of SpCell, configured SCell(s) and best neighbouring cell within measured cells with reference signals indicated in on each serving cell measurement object. MeasurementReport including measResultBestNeighCell is reported by the UE to indicate measResultBestNeighCell(FI) for PCell (F1), measResultBestNeighCell(F2) for SCell (F2) and measResultBestNeighCell(F5) for SCell (F5). A measResultBestNeighCell indicates the measurement result for the best neighboring cell of the serving cell identified by servCellld. A measResultBestNeighCell includes the physCellld and the measResult for the best neighboring cell of the serving cell identified by servCellld. Looking now at the measurement configuration in step 0.1 of FIG.8 which describes the measurement configuration and reporting with one best neighboring cell reported for each serving cell: In step 0.1, the source MN can send to the UE a RRCReconfiguration message including a measurement configuration defined to obtain from the UE a MeasurementReport including the best neighboring cell (denoted BestNeighCell) for each serving cell. In accordance with TS 38.331 V17.4.0, the source MN sets the servingCellMO IE so that the UE can report the measResultServingMOList IE. For this purpose, the reportAddNeighMeas is also included in ReportConfigNR for eventA3 (or eventA5) For this purpose, in step 0.1, the source MN shall first include in the measurement configuration the field reportAddNeighMeas in the ReportConfigNR IE for eventA3 (or 19 event A5). Thus, the network tells the UE to include the best neighboring cells per serving frequency in the MeasurementReport for eventA3 (or event A5). Terminology “serving frequency” refers to the frequency of a serving cell in a CA configuration. In accordance with TS 38.331 V17.4.0, the source MN shall send ReportConfigNR -> EventTriggerConfig -> reportAddNeighMeas ENUMERATED {setup} OPTIONAL where the ReportConfigNR for eventA3 (or eventA5) For this purpose, the servingCellMO is also included in the ServingCellConfig of the PCell and each SCell For this purpose, the source MN shall set the servingCellMO for each serving cell. The servingCellMO is the measObjectld of the MeasObjectNR in MeasConfig which is associated to the serving cell. In accordance with TS 38.331 V17.4.0, the field reportAddNeighMeas indicates that the UE shall include the best neighbour cells per serving frequency. The source MN shall set the TS 38331 IE servingCellMO (measObjectld) in ServingCellConfig IE for each serving cell. A serving cell refers to the PCell (F1), the first SCell (F2) or the second SCell (F5). The source MN requires the UE to search for a best neighbouring cell at the same frequency as the serving cell. The servingCellMO (as measObjectld) shall point to a MeasObjectNR whose ssbFrequency (synchronisation signal block frequency shall be equal carrier frequency of the serving cell. Fig. 7 shows a servingCellMO is a measObjectld that points to a MeasObjectNR whose ssbFrequency is equal to the frequency of a serving cell (F5 not shown). In accordance with TS 38.331 V17.4.0, the servingCellMO as measObjectld shall refer to a MeasObjectNR whose ssbFrequency (ARFCN-ValueNR) shall be included in servingCellConfigCommon as absoluteFrequencySSB. The ServingCellConfig IE is used to configure (add or modify) the UE with a serving cell, which may be the PCell or an SCell of an MCG or the PSCell or an SCell of an 20 SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g., in additionally configured bandwidth parts). Source MN shall not configure any ReportConfig associated with a MeasObject pointed by the servingCellMO in ServingCellConfig IE For the UE to report measurements on the frequency F1 of the PCell (F1) (resp. F2 of the SCell (F2) or F5 of the SCell (F5)), the network only needs to configure (at least) one MeasObject whose ssbFrequency is F1 (resp. F2 or F5). Below Measurement Configuration for Measurement Reporting with measResultServingMOList is described. In FIG. 8, Step 0 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. In step 0, if the source MN applies the procedure of Measurement Configuration with reportAddNeighMeas in ReportConfig NR IE and servingCellMO in the ServingCellConfig IE, the UE applies the procedure of Measurement Reporting with measResultServingMOList. The step 0 which constitutes the core of procedures to which the present invention applies can be improved as described in FIG.8. FIG. 8 shows Step 0. Measurement Configuration and Reporting with best neighbouring cell reported for each serving cell. The preparations of single or multiple SN addition(s) for CHO with SCG are described in the next paragraphs. Let the UE be configured with a CA (carrier aggregation) configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different carrier frequencies of the CA configuration. A serving cell refers to the PCell (F1), the first SCell (F2) or the second SCell (F5). Step 0 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. In R17, the target MN that controls a candidate PCell for CHO initiates a single SN addition preparation per candidate PCell that can only be paired with a single candidate PSCell. In R18, the target MN that controls a candidate PSCell for CHO can initiate multiple SN addition preparations per candidate PCell that can be paired with multiple candidate PSCells. In R17 / R18, when the step 0 includes a measurement configuration and reporting with best neighbouring cell reported for each serving cell, the UE sends a Measurement Report to the source MN in the step 0.4 and the source MN can initiate: • multiple preparations of intra-frequency condition handovers with the candidate PCells • at F1 i.e., the neighbouring cells at F1 including the best neighbouring cell reported for PCell (F1) • multiple preparation of inter-frequency SN additions with candidate PSCells • at F2 i.e., SCell (F2) and best neighbouring cell reported for first SCell (F2) • at F5 i.e., SCell (F5) and best neighbouring cell reported for second SCell (F5) One problem (Problem N°1) related to R17 / R18 procedure is related to SN additions with candidate PSCells at frequencies of the serving cells only, as outlined below. Step 0 in FIG. 8 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. In step 0, if the source MN applies the procedure of Measurement Configuration with reportAddNeighMeas in ReportConfig NR IE and servingCellMO in the ServingCellConfig IE, the multiple preparation of SN additions can only be performed with candidate PSCells at frequencies of the serving cells only Let the UE be configured with the PCell (F1), a first SCell (F2) and a second SCell (F5), the UE will only report measurements on these frequencies as such the network can initiate measurement-based preparation of the SN additions for candidate PSCells at F2 and F5. If no neighbouring PSCell detected on these frequencies or if there are PSCells on other frequencies than F2 and F5, the UE will not report them along the serving frequency measurement (Problem N°1). Another problem (Problem N°2) related to R17 / R18 procedure relates to there being only one best neighbouring cell is reported per serving cell, as outlined below. Historically, the network seeks to maintain a CA configuration when handing over the UE from the source MN to the target MN, which is why the network requires the UE to report a single best neighbouring cell per serving cell, PCell and SCell. Step 0 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. In step 0, if the source MN applies the procedure of Measurement Configuration with reportAddNeighMeas in ReportConfig NR IE and servingCellMO in the ServingCellConfig IE, the multiple preparation of SN additions can only rely on one best neighboring cell reported per serving cell. Let the UE be configured with the Pcell (F1), a first SCell (F2) and a second SCell (F5), the preparation of the SN additions can only rely on one best neighbouring cell on F2 and another on F5. If there are multiple cells available at that frequency that can be selected by the network due to e.g., load balancing reasons or other considerations such as the support of network slices - or due to pro-active preparation of multiple candidate cells for conditional handover procedure, UE will not report more than one cell (Problem N°2). In R17 / R18 CHO with SCG, before the source MN starts the conditional handover procedure by initiating the Xn Handover Preparation, the source MN initiates a procedure of Measurement Configuration with a measld linked to a MeasObjectld and a ReportConfigld: • MeasObjectld identifies a MeasObject whose ssbFrequency is the carrier frequency of the PCell (= carrier frequency of the serving cell PCell of the serving MN); • ReportConfigld identifies a ReportConfigNR (for eventA3 or eventA5) including reportAddNeighMeas ServingCellMO is included in ServingCellConfig IE (of PCell and each SCell). As per 3GPP technical specifications, the UE initiates a single procedure of Measurement Reporting whose purpose is to transfer measurement results to the source MN with candidate PSCells at frequencies of the serving cells (i.e., PCell and SCells) only. This functionality leads to a problem, because this single procedure of Measurement Reporting cannot transfer measurement results to the source MN with candidate PSCells at candidate frequencies other than those of the serving cells (Problem N°1). The problem is that the Measurement Report message does not include / provide an IE to report candidate PSCell(s) on a carrier frequency different than a serving frequency. Measurement Report message can report a mix of serving / candidate PCell(s), serving / candidate SCell(s), candidate PSCell(s) on serving frequencies but with no candidate PSCell(s) on a non-serving frequency. This functionality leads to the above problem N°1: with this single measurement report procedure, the UE cannot transfer measurement results to the source MN with candidate PSCells at candidate frequencies other than those of the serving cells. Eventually, the network cannot know whether it should initiate the preparation of the PSCells that are operating at non-serving carrier frequencies. The current 3GPP technical specifications does not allow the Measurement Report message to report the aforementioned mix including candidate PSCell(s) on a nonserving frequency. A further problem arises in R17 / R18 CHO with SCG, before the source MN starts the conditional handover procedure by initiating the Xn Handover Preparation, if the source MN applies the procedure of Measurement Configuration with reportAddNeighMeas in ReportConfigNR IE and servingCellMO in the ServingCellConfig IE, the multiple preparation of SN additions can only rely on one best neighbouring cell reported per serving cell (Problem N°2). That is, Source MN I serving cell PCell asks UE to measure and report additional neighboring cells = PSCells within SCG to the serving cell PCell). A yet further problem (Problem N°3) arises as currently during the Xn setup procedure (via XN SETUP REQUEST or XN SETUP RESPONSE message), target MN shares the frequencies of the cells that it controls (via TS 38.423 V17.4.0 9.2.2.12 Served Cell Information E-UTRA) and the frequencies of its neighbouring cells (via TS 38.423 V17.4.0 9.2.2.13 Neighbour Information NR) which could be candidate PSCells. Currently, the source MN cannot learn which frequencies are of interest to the target MN and having all frequencies configured by the source MN may not be an option as they may be too many. Before the source MN configures the measurements to know the candidate neighbouring PSCells for R17 / R18 CHO with SCG, the source MN cannot know which are the frequencies of interest for CHO with SCG and on which cells controlled by the target MN are deployed. (=source MN does not know on which carrier frequency a target MN operates its own cells). At least to partially tackle the above-mentioned problems, embodiments according to aspect 1 (addressing problem N°2) seek to address this in the CHO with SCG procedure by providing for the UE a possibility to switch from serving cells on a first set of frequencies to target cells operating on a second set of frequencies. The second set includes at least one additional frequency not supported in the first set, wherein the target cells may operate on a serving and / or a non-serving frequency. With a single measurement configuration procedure, the source MN may configure the UE more efficiently to report target cells not only on serving frequencies but also on non-serving frequencies. UE receives measurement configuration from the source MN (in MeasConfig) for serving cells with trigger when to report the measurements to the source MN, those reports (MeasResults) include additionally a new IE to report the measured results of the non-serving frequencies. UE receives measurement configuration from the source MN (in same MeasConfig) for target / candidate cells on non-serving frequencies, which do not include a trigger (i.e., no ReportConfig) when to report the measurement to the source MN. UE performs the measurements and reports a single measurement report indicating the results of the configured measurements. Upon reception of this single measurement report, the source MN may initiate the conditional handover (with SCG) preparation by forwarding to the target MN the UE measurements. Then the target MN may initiate the SN preparation for target PSCells which operate not only on serving frequencies but also on non-serving frequencies. An embodiment according to aspect 1 addresses the above with an improved MeasConfig provided by the source MN (step 0.1 of FIG.8) • When sending a measurement report including the measurement results for serving cell(s) (PCell and SCell if any) frequencies, UE is configured to include the measurement results of target cells on candidate carrier frequencies that are different from those of serving cell frequencies. • an embodiment according to aspect 1 may add candidateFrequencyConf-r18 to configure the UE to measure and report the best neighbouring cells on candidate carrier frequencies • Some embodiments according to aspect 1 seek to improve TS 38.331 V17.4.0 MeasConfig IE by configuring the UE to measure and report the best neighbouring cells on candidate carrier frequency (ies) which is (are) different from that of the serving cell which may be the SpCell or an SCell of an MCG or SCG. • Some embodiments according to aspect 1 provide a new information element candidateFrequencyConf-r18 in TS 38.331 V17.4.0 MeasConfig IE Compared to the prior art, these embodiments with further embodiments (explained below) removes the need of configuring several measurement IDs i.e., at least one measurement ID per candidate frequency, where new frequencies are added, a new measurement object is added, but the existing Measurement IDs are used. For the UE to report measurements on a candidate frequency, the network only needs to configure (at least) one MeasObject whose ssbFrequency is a candidate frequency. The network should neither configure nor bind any ReportConfig to a MeasObject whose ssbFrequency is candidate frequency. Embodiments above according to aspect 1 improve the Measurement Configuration to resolve or at least address R17 / R18 Problem N°1 Yet further embodiments also relating to aspect 1 provide an improved MeasResults by the UE (step 0.4) • When sending a measurement report including the measurement results for serving cell(s) (PCell and Scell if any) frequencies, UE reports the measurement results for best neighboring cells which are operating on different frequencies that those of serving cell (Pcell or SCell). • Embodiments add candidateNeighbourFreqList-r18 to allow UE to report measurements on multiple best neighbouring cells on carrier frequencies different from that of the serving cell which may be the SpCell or an SCell of an MCG orSCG • Embodiments aim to improve TS 38.331 V17.4.0 MeasResults IE to allow the UE to report measurements on the best neighbouring cells on candidate carrier frequency (lEs) which is (are) different from that of the serving cell. • Embodiments adds the new information element candidateNeighbourFreqList-r18 in TS 38.331 V17.4.0 MeasResults IE • Compared to the prior art, embodiments remove the need to configure several measurement IDs, i.e., at least one measurement ID per candidate non-serving frequency. A single measurement report on a serving frequency allows the UE to report measurements on candidate frequencies of also other than a serving frequency( / ies). When the UE sends to the source MN a MeasurementReport (triggered by eventA3 or eventA5) to report measured candidate PCells for an intra-frequency CHO at the PCell serving frequency, the UE additionally includes available measurements on candidate cells on non-serving frequencies. In further embodiments according to aspect 2 addressing problem N°2: • UE may include more than one best neighbouring target cells operating on a serving frequency of SCell; • When sending a measurement report including the measurement results for serving cell(s) (PCell and SCell if any) frequencies, UE reports the measurement results for multiple neighbouring cells which are operating on same frequencies as those of serving cell (SCell). • The further embodiments add measResultBestNeighCellList-r18 to allow the UE to report measurements on several best neighbouring cells on carrier frequency of the serving cell which may be the SpCell or an SCell of an MCG or SCG. Some further embodiments aim to improve TS 38.331 V17.4.0 MeasResultServMO in MeasResults IE to allow the UE to report measurements on several best neighbouring cells on carrier frequency of the serving cell. Some further embodiments add the new information element measResultBestNeighCellList-r18 in TS 38.331 V17.4.0 MeasResultServMO IE in MeasResults IE. Compared to the prior art, the further embodiment removes the limitation of only one best neighbouring cell reported per serving cell The further embodiment according to aspect 2 improves the Measurement Reporting resolving or at least addressing R17 / R18 Problem N°2 The alignment between nodes to configure measurements of multiple candidate cells is discussed below and provides a yet further embodiment according to aspect 3 that aims to address Problem N°3. In one option 1 of aspect 3, the target MN can inform the source MN during the Xn Setup procedure (via XN SETUP REQUEST or XN SETUP RESPONSE message) about frequencies: • that allow target MN to add SCG at these frequencies during handover; • for which source MN configures radio measurements; • for which UE reports radio measurements. In option 1 of aspect 3, the target MN can also inform the source MN during the NG-RAN node Configuration Update procedure (via NG-RAN NODE CONFIGURATION UPDATE or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message) about frequencies: • that allow target MN to add SCG at these frequencies during handover; • for which source MN configures radio measurements; • for which UE reports radio measurements. Currently, in Xn Setup or NG-RAN node Configuration Update procedure, target MN shares the frequencies of the cells that it controls, as well the frequencies of the neighbouring cells that could be actually PSCells. The yet further embodiment according to aspect 3 proposes that target gNB communicates with the source gNB the frequencies of the neighbouring cells that are of interest to be configured for the sake of CHO with SCG or even (baseline) handover of SCG. The yet further embodiment of aspect 3 allows the source MN to select the frequencies of interest for target MN (in prior-art all the frequencies of target PSCells that can be configured by target MN are conveyed during the Xn setup procedure or the NG-RAN node Configuration Update procedure) i.e., configuring all frequencies may not be an option if they are too many 28 (although in reality it may be only couple of frequencies). Indeed, all the frequencies of target PSCells are conveyed during the Xn setup procedure (via XN SETUP REQUEST or XN SETUP RESPONSE in FIG. 14) or during the NG-RAN node Configuration Update procedure (via NG-RAN NODE CONFIGURATION UPDATE or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE in FIG. 15). In this report, the yet further embodiment of aspect 3 is described with procedures from TS 38.423. The yet further embodiment could also be described with the peer procedures in TS 36.423 or any future application protocols between future network controllers. The candidate frequencies to be measured by the UE in step 0 (Fig. 8) must be compliant with the UE capabilities, the target MN interest for PSCell for the sake of CHO with SCG (i.e., as a candidate frequency on which possible candidate PSCell operates) In one embodiment, the target MN is informed about the frequencies that are relevant for SCG addition during the handover via 1) OAM, 2) another SON / AI-ML module or 3) UE measurements that are reported to target MN after performing an inter-MN handover without SCG. In the latter case, if the target MN configures an SCG (on frequency e.g., f3) for the UE shortly after performing a single connectivity handover (HO without target SCG), target MN informs source MN about frequency f3 given that it is relevant for handover with SCG addition. F3 refers to the description given subsequently on the determination by the gNB of the frequencies to set TS 38.423 Frequencies for SCG Addition during Handover Information IE In another option 2 of aspect 3, the source MN is informed about the frequencies that are considered by the target gNBs for SCG addition via 1) OAM or 2) another SON / AI-ML module. Compared to the prior art, the yet further embodiment of aspect 3 allow the source MN to learn the candidate frequencies that are considered by the target MN for SCG addition. Step 0 of FIG.8 refers to the RRC Reconfiguration procedure initiated by the source MN to configure intra-frequency measurements to detect candidate PCells for conditional handover. These event-triggered measurements use eventA3 and eventA5. 29 The yet further embodiment of aspect 3 improves the OAM / SON solution to resolve R17 / R18 Problem N°3 Another embodiment according to aspect 4 involves UE capabilities and addresses problem N°4. The other embodiment of aspect 4 introduces several R17 / R18 UE capability indicators which indicate the support of the proposed embodiments. For example, a UE capability indicator which indicates to the network node / gNB the capability to support the proposed embodiment, "enhanced R17 / R18 target PSCell measurement configuration and reporting on a candidate frequency different from serving PCell / SCell frequency". The capability to support a proposed further embodiment, "enhanced R17 / R18 measurement reporting to include more than one best neighbouring target cells operating on a serving PCell / SCell frequency". Embodiments seek to address the above problems using techniques described in more detail below. The addition of candidateFrequencyConf-r18 to configure the UE to measure and report the best neighbouring cells on candidate carrier frequencies. An embodiment according to aspect 1 aims to improve TS 38.331 V17.4.0 MeasConfig IE to configure the UE to measure and report the best neighbouring cells on candidate carrier frequency (lEs) which is (are) different from that of the serving cell which may be the SpCell or an SCell of an MCG or SCG. Further the new information element candidateFrequencyConf-r18 in TS 38.331 V17.4.0 MeasConfig IE is added. ...............................g The field candidateFrequencyConf indicates a set of candidate frequencies different from the frequency of a serving cell which may be the SpCell or an SCell of an MCG or SCG. The UE must perform and report measurements on the best neighbouring cells on a candidate frequency. The UE must perform these measurements on a candidate frequency while it performs, on a serving cell, a measurement whose configuration is identified by a Measld in the applicableMeasIdList. A candidate frequency is indicated by the ssbFrequency, i.e., the frequency of the SSB, associated to the MeasObjectNR whose configuration is identified by a MeasObjectld in the applicableMeasObjectldList. Fig. 9 schematically shows the candidateFrequencyConf to configure the UE to measure and report on candidate (non-serving) carrier frequencies i.e., F3 or F4 - as per an embodiment. Let the UE be configured with an CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different carrier frequencies of the CA configuration. Fig. 9 provides an illustration of the change in the MeasConfig to configure the UE to measure and report the best neighbouring cells on candidate (non-serving) carrier frequencies i.e., F3 or F4. An embodiment according to aspect 1 thus aims to improve the MeasConfig to configure the UE to measure and report the best neighbouring cells on candidate carrier frequency (F3 and F4) which are different from that of the serving cell which may be the PCell (at F1) or an SCell (at F2). The candidateFrequencyConf field indicates a set of candidate frequencies F3 and F4 different from the frequency F1 (resp. F2) of the serving PCell (resp. the serving SCell). The UE must perform and report measurements on the best neighboring cells on a candidate frequency F3 and F4. The UE may report (e.g. provide measurement results of) one or more cells on frequency F3 and / or one or more cells on frequency F4. The UE performs these measurements on a candidate frequency F3 and F4 and the UE performs measurement whose configuration is identified by Measldl (linked to MeasObjectldl for F1) or Measld2 (linked to MeasObjectld2 for F2) in the applicableMeasIdList. A candidate frequency F3 (resp. F4) is indicated by the ssbFrequency, i.e., the frequency of the SSB, associated to the MeasObjectNR whose configuration is identified by MeasObjectld3 (resp. MeasObjectld4) in the applicableMeasObjectldList. A further embodiment according to aspect 1 adds candidateNeighbourFreqList-r18 to allow UE to report measurements on multiple best neighbouring cells on carrier frequencies different from that of the serving cell which may be the SpCell or an SCell of an MCG or SCG. This proposal aims to improve TS 38.331 V17.4.0 MeasResults IE to allow the UE to report measurements on the best neighbouring cells on candidate carrier frequency (ies) which is (are) different from that of the serving cell. The proposal adds the new information element candidateNeighbourFreqList-r18 in TS 38.331 V17.4.0 MeasResults IE. : : = The field candidateNeighbourFreqList indicates a set of measurement results made on candidate frequencies different from the frequency of a serving cell which may be the SpCell or an SCell of an MCG or SCG. A candidate frequency is indicated by the frequency of the SSB associated to the MeasObjectNR whose configuration is identified by the candidateServingCellMOId. The field measResultBestNeighCellList indicates a set of measurements on the best neighboring cells on the candidate frequency. Let the UE be configured with an CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different carrier frequencies of the CA configuration, i.e. different serving frequencies of the UE. Fig. 10 provides an illustration of the change in the MeasResults to allow the UE to report measurements on multiple best neighboring cells on carrier frequencies different from that of the serving cells. Some embodiments according to aspect 1 thus aim to improve the MeasResults to allow the UE to report measurements on the best neighboring cells on candidate frequency candidate frequencies F3 and F4 which are different from the frequency F1 of the serving PCell (F1). The field candidateNeighbourFreqList indicates a set of measurement results made on candidate frequencies F3 and F4 different frequency F1 (resp. F2) of the serving PCell (resp. the serving SCell). The candidate frequency F3 is indicated by the frequency F3 of the SSB associated to the MeasObjectNR whose configuration is identified by the candidateServingCellMOId (MeasObjectld3). Same logic for F4. The field measResultBestNeighCellList indicates a set of measurements on the best neighbouring cells on the candidate frequency F3. Same logic for F4. Fig. 11 provides an illustration of the change in the MeasResults to allow the UE to report measurements on multiple best neighbouring cells on carrier frequencies different from that of the serving cells. Some embodiments according to aspect 1 thus aim to improve the MeasResults to allow the UE to report measurements on the best neighbouring cells on candidate frequency candidate frequencies F3 and F4 which are different from the frequency F1 of the serving PCell (F1). The differences between Fig.s 10 and 11 are as follows: Fig. 10 illustrates the scenario where measldl linked to MeasObjectldl triggers a Measurement Report message including cell(s) on F1 with reported cells on F3 (physCellld130, physCellld131) and F4 (physCellld140, physCellld141). Fig. 11 illustrates the scenario where measld2 linked to MeasObjectld2 triggers a Measurement Report message including cell(s) on F2 and cells on F3 (physCellld232, physCellld233) and F4 (physCellld242, physCellld243). The field candidateNeighbourFreqList indicates a set of measurement results made on candidate frequencies F3 and F4 different frequency F2 of the serving SCell (F2). The candidate frequency F3 is indicated by the frequency F3 of the SSB associated to the MeasObjectNR whose configuration is identified by the candidateServingCellMOId (MeasObjectld3). Same logic for F4. The field measResultBestNeighCellList indicates a set of measurements on the best neighbouring cells on the candidate frequency F3 and on F4. The acronym BestNeighCell refers to a best neighbouring cell on a serving or candidate frequency. Fig. 10 illustrates how a proposal makes it possible to report the measurements not only to the service frequencies but also to the candidate frequencies. Fig. 11 illustrate how the proposal makes it possible to prepare the SN addition for a PSCell on a candidate frequency F3. Fig. 12 shows how the proposal makes it possible to prepare the SN addition for a PSCell on a candidate frequency F3, this portion described below in italics. In step 1, the source MN starts the CHO procedure by initiating the Xn Handover Preparation procedure including MCG configuration and, if the UE is configured with an SCG, SCG configuration. The source MN includes the (source) SN UE XnAP ID, SN ID, the UE context in the (source) SN and the CHO Information Request IE in the Handover Request message. The source MN includes in the Xn Handover Preparation message the measurement results on non-serving candidate frequencies (F3 or F4) received from the UE in step 0.4. In step 2, if the candidate MN decides to keep the UE context in the SN, the candidate MN sends the SN Addition Request message to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the SN Addition Request message to the candidate SN including the UE context in the source SN that was established by the source MN. Otherwise, the 34 candidate MN may send the SN Addition Request message to the candidate SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. Within the SN Addition Request message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE XnAP ID in the source MN, in order to indicate that the SN Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. The target MN may send SN Addition Request message to the SN by including the candidate PSCell on F3 or F4 as received from the source MN in Xn Handover Request message. An embodiment according to aspect 2 provides a possibility to add measResultBestNeighCellList-r18 to allow the UE to report measurements on several best neighbouring cells on carrier frequency of the serving cell other than the PCell. Thus, this embodiment according to aspect 2 aims to improve TS 38.331 V17.4.0 MeasResultServMO in MeasResults IE to allow the UE to report measurements on several best neighbouring cells on carrier frequency of the serving cell other than the PCell. The further embodiment could also be described with the peer procedures in TS 36.331 or any future application protocols between a future network controller and the user equipment. An embodiment according to aspect 2 adds the new information element measResultBestNeighCellList-r18 in TS 38.331 V17.4.0 MeasResultServMO IE in MeasResults IE The field ‘measResultBestNeighCellList’ indicates a list of measurements on the best neighbouring cells on the frequency of the serving cell which is identified by ServCelllndex. The above shows measResultBestNeighCellList to indicate a list of measurements 35 on the best neighbouring cells of PCell(F1) and SCell(F2) - the last portion, change in ASN.1 from TS 38.331 V17.4.0. Let the UE be configured with an CA configuration consisting of the PCell (F1), a first SCell (F2) and a second SCell (F5) where F1, F2 and F5 denote the different serving carrier frequencies of the CA configuration. An embodiment according to aspect 2 aims to add the measResultBestNeighCellList in MeasResultServMO in MeasResults to allow the UE to report measurements on several best neighbouring cells on carrier frequency F1 of the serving PCell(F1) and on carrier frequency F2 of the serving SCell(F2). The field measResultBestNeighCellList indicates a list of measurements on the best neighbouring cells on the frequency of the serving cell which is identified by ServCelllndex. The acronym BestNeighCell refers to a best neighbouring cell on a serving or candidate frequency. Fig. 13 illustrates how the further embodiment makes it possible for the UE to report the measurements for several best neighbouring cells per serving frequency other than the PCell frequency. Fig. 14 shows an embodiment of a Xn Setup, successful operation, related to option 1 of aspect 3, where the target MN can inform the source MN during the Xn setup procedure (via XN SETUP REQUEST or XN SETUP RESPONSE message) about non-serving frequencies that are considered by the target MN for SCG addition during handover. With option 1 in Fig. 15, the target MN can also inform the source MN during the NG-RAN node Configuration Update procedure (via NG-RAN NODE CONFIGURATION UPDATE or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message) about non-serving frequencies that are considered by the target MN for SCG addition during handover. In an alternative option 2 of the aspect 3, the source gNB receives the preferred frequencies of candidate target MN from OAM or SON / AI-ML module. Details below are provided below on Xn Setup of Fig. 14: these details specify the change proposed in the Xn application protocol (XnAP) i.e., to add Frequencies for SCG Addition during Handover Information IE. 36 An alternative NG-RAN node Configuration Update: specifies the change proposed by option-1 in the Xn application protocol (XnAP) i.e., to add Frequencies for SCG Addition during Handover Information IE. The next paragraphs detail the determination by the gNB of the non-serving frequencies to set TS 38.423 Frequencies for SCG Addition during Handover Information IE In Fig. 14 the NG-RAN nodel initiates the procedure by sending the XN SETUP REQUEST message to the candidate NG-RAN node2. The candidate NG-RAN node2 replies with the XN SETUP RESPONSE message. If frequencies are considered by the NG-RAN nodel for SCG addition during handover, the NG-RAN nodel shall inform the NG-RAN node2 by including in the XN SETUP REQUEST message the Frequencies for SCG Addition during Handover Information IE. If frequencies are considered by the NG-RAN node2 for SCG addition during handover, the NG-RAN node2 shall inform the NG-RAN nodel by including in the XN SETUP RESPONSE message the Frequencies for SCG Addition during Handover Information IE. The embodiment of option 1 of aspect 3 introduces changes (in italics above) in the NG-RAN NODE CONFIGURATION UPDATE and NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE messages to resolve R17 / R18 Problem N°3 Fig. 15 shows NG-RAN node Configuration Update, successful operation. The NG-RAN nodel initiates the procedure by sending the NG-RAN NODE CONFIGURATION UPDATE message to a peer NG-RAN node2. If frequencies are considered by the NG-RAN nodel for SCG addition during handover, the NG-RAN nodel shall inform the NG-RAN node2 by including in the NG-RAN NODE CONFIGURATION UPDATE message the Frequencies for SCG Addition during Handover Information IE. If frequencies are considered by the NG-RAN node2 for SCG addition during handover, the NG-RAN node2 shall inform the NG-RAN nodel by including in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message the Frequencies for SCG Addition during Handover Information IE. This embodiment of option 1 introduces changes (in italics above) in the NG-RAN NODE CONFIGURATION UPDATE and NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE messages to resolve R17 / R18 Problem N°3 Some embodiments are related to 5G New Radio and, in particular, Multi-RAT Mobility (MRM) concept targeted for 3GPP Rel-18 and beyond which enables and improves mobility / cell-changes in RAN where the Central-Unit - Distributed-Unit (CU-DU) structure is deployed, i.e., enabling operations between different DU (inter-DU) of different vendors via CU (involving the Control Plane or / and User Plane aspects of the Central-Unit, CU-CP, CU-UP); Dual connectivity supports CHO with SCG for limited situations and the following problems are considered: • Problem 1: SN additions with candidate PSCells at frequencies of serving cells only; • Problem 2: only one best neighbouring cell is reported per serving cell; • Problem 3: source MN cannot learn which carrier frequencies are interesting for the target MN; Some embodiments address the above problems by one of more of: • when sending a measurement report including the measurement results for serving cell(s) (PCell and SCell if any) frequencies, UE is configured to include the measurement results of target cells on candidate carrier frequencies that are different from those of serving cell frequencies (aspect 1); • When sending a measurement report including the measurement results for serving cell(s) (PCell and SCell if any) frequencies, UE reports the measurement results for best neighbouring cells which are operating on different frequencies that those of serving cell (PCell or SCell) (aspect 1); • UE may include in the measurement report more than one best neighbouring target cells operating on a serving frequency of SCell (aspect 2); • the source MN is informed (via Xn, OAM, SON, AI-ML) about frequencies (1) that allow target MN to add SCG at frequencies during handover (2) for which source MN configures radio measurements (3) for which UE reports radio measurements (aspect 3); • UE provides UE capability indicator to the network node / gNB which enables the network node to operate according to the above with the UE (aspect 4). During dual connectivity operation, a CHO with SCG may occur while moving to the serving cell borders of serving MN and serving SN. Enhancements are proposed to avoid a need for a completely new RRC Reconfiguration after changing into the target cells of target MN and target SN due to the fact that the target MN / SN operates on further frequencies different to those of serving MN / SN. In some embodiments the UE receives a new measurement configuration which may include: • a configuration to measure target cells on frequencies F3, F4 where the frequencies F3, F4 are further frequencies within the target MN2 resp. target cells PSCell3, PSCell4 that the MN1 does not operate on; • a configuration to report more than just one best / strongest target cells on “non-serving” frequencies; • a configuration as to whether and how to report more than just one best / strongest neighbour cells on the same frequency as the currently serving secondary cells; • Serving gNB / MN determines / obtains information about “non-serving frequencies” operated within the coverage of a neighbouring MN; • Serving gNB / MN receives UE capability indicator from UE whether UE supports measurements on “non-serving frequencies”; • Serving gNB / MN requests and configures measurements and measurement reports from the UE on candidate target cells operating on serving frequencies and non-serving frequencies; • Serving gNB / MN: provides information about the frequencies on which the cells operate within the coverage of the serving MN (MCG and SCG cells) and receives a list of frequencies on which the target MN operates in addition to the serving MN. For those additional frequencies, serving MN may request additional measurements and measurement reports from a UE; • Target gNB / MN receives from serving MN a list / set of frequencies on which the serving MN currently operates and compares them to the list / set of frequencies on which the target MN currently operates and the non-matching frequencies are the “non-serving frequencies” of candidate target cells within the target MN coverage. Target MN provides those “non-serving frequencies” to the serving MN for which the serving MN may request the UE to perform new / additional measurements. A person of skill in the art would readily recognize that steps of various abovedescribed methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machineexecutable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods. The tern non-transitory as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g. RAM vs ROM). As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. Although example embodiments of the present invention have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the invention as claimed. Features described in the preceding description may be used in combinations other than the combinations explicitly described. Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not. Although features have been described with reference to certain embodiments, those features may also be present in other embodiments whether described or not. Whilst endeavouring in the foregoing specification to draw attention to those features of the invention believed to be of particular importance it should be understood that the Applicant claims protection in respect of any patentable feature or combination of features hereinbefore referred to and / or shown in the drawings whether or not particular emphasis has been placed thereon.
Claims
1. A network node for supporting providing radio coverage to user equipment thatare configured to support carrier aggregation and dual connectivity, the carrier aggregation comprising at least a first serving frequency of a serving primary cell and at least one further serving frequency of at least one serving secondary cell, said network node comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the network node at least to:determine at least one cell that is a potential candidate cell for addition as a primary secondary cell during handover with secondary cell group of a user equipment from a serving network node to said network node and when said frequency of operation of said at least one cell is different to said serving frequency of the serving primary cell and any serving secondary cells for said user equipment;to generate an indication of said frequency of operation of said at least one potential candidate cell for transmission to said serving network node.
2. The network node according to claim 1, wherein said network node is caused to determine which of said at least one potential candidate primary secondary cells is a preferred candidate cell and to generate said indication of said frequency only for said preferred candidate primary secondary cells.
3. The network node according to claim 2, wherein said network node is caused to determine which of said at least one potential candidate primary secondary cells are preferred candidate primary secondary cells in response to a message received from at least one of an operations administration and maintenance OAM message, or a message generated by a self-organising network SON module or a machine learning, artificial intelligence AI / ML module associated with the network.
4. The network node according to claim 3, wherein said message received from said OAM, SON, AI / ML comprises an indication of which said plurality of potential candidate primary secondary cells are likely to provide preferred coverage for said user equipment.
5. The network node according to any preceding claim, said network node being further caused to transmit said indication of said frequency to said serving network node as a handover information element.
6. The network node according to any preceding claim, said network node being caused to:determine that said frequency of operation of said at least one cell is different to said serving frequency of said serving primary cell and any serving secondary cells based on receiving a message from said serving network node, said message indicating said frequencies of operation of said serving primary cell and of said any serving secondary cells, and based on determining whether said at least one potential candidate cell for addition as a primary secondary cell during handover with secondary cell group to said network node provides radio coverage using a frequency different to said frequencies of operation of said serving primary cell and serving secondary cells; andbased on the determining, generating said indication of said frequency..
7. The network node according to any preceding claim, said network node being caused to:receive a handover request from said serving network node, said handover request comprising a measurement report from a user equipment, said measurement report including at least one measurement at said at least one frequency for said potential candidate primary secondary that is different to said frequencies of operation of said serving primary and secondary cells; andto forward said at least one measurement to a network node supporting providing radio coverage in said potential candidate primary secondary cell.
8. The network node according to any preceding claim,said network node being caused while acting as a serving network node to a user equipment to:respond to receipt from a target network node of an indication of at least one frequency of operation of at least one potential candidate primary secondary cell, said at least one frequency of operation being different to said first and said at least one further serving frequencies, the responding comprising generating an indication for transmission to a user equipment indicating said user equipment should perform measurements including at least one measurement at said at least one frequency of9. The network node according to claim 8, wherein said network node is caused: to receive a measurement report from said user equipment, said measurement report including said at least one measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies,to generate a handover request for transmission to said target network node, said handover request including an indication of results of said user equipment measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies.
10. The method performed at a network node for supporting providing radio coverage to user equipment that are configured to support carrier aggregation and dual connectivity, the carrier aggregation comprising at least a first serving frequency of a serving primary cell and at least one further serving frequency of at least one serving secondary cell, said method comprising:determining at least one cell that is a potential candidate cell for addition as a primary secondary cell during a handover with secondary cell group of a user equipment from a serving network node to said network node and when said frequency of operation of said at least one cell is different to said serving frequency of a serving primary cell and any serving secondary cells for said user equipment;generating an indication of said frequency of operation of said at least one potential candidate primary secondary cell for transmission to said serving network node.
11. The method according to claim 10, comprising determining which of said at least one potential candidate primary secondary cell is a preferred candidate cell and generating said indication of said frequency only for said preferred candidate primary secondary cells.
12. The method according to claim 11, comprising determining which of said potential candidate primary secondary cells are preferred candidate primary secondary cells in response to a message received from at least one of an operations administration and maintenance OAM message, or a message generated by a selforganising network SON module, or a machine learning, artificial intelligence AI / ML module associated with the network.
13. The method according to claim 12, wherein said message received from said OAM, SON, AI / ML comprises an indication of which said plurality of potential candidate secondary cells are likely to provide preferred coverage for said user equipment.
14. The method according to claim 11 or 12, comprising transmitting said indication of said frequency to said serving network node as a handover information element.
15. The method according to any one of claims 10 to 14, comprising:determining that said frequency of operation of said at least one cell is different to said serving frequency of said serving primary cell and any serving secondary cells based on receiving a message from said serving network node, said message indicating said frequencies of operation of said serving primary cell and of said any serving secondary cells, and based on determining whether said at least one potential candidate cell for addition as a primary secondary cell during handover with secondary cell group to said network node provides radio coverage using a frequency different to said frequencies of operation of said serving primary cell and serving secondary cells, and based on the determining generating said indication of said frequency of operation.
16. The method according to any one of claims 10 to 15, said method comprising:receiving a handover request from said serving network node, said handover request comprising a measurement report from a user equipment, said measurement report including at least one measurement at said at least one frequency for said potential candidate primary secondary that is different to said frequencies of operation of said serving primary and secondary cells; andforwarding said at least one measurement to a network node supporting providing radio coverage in said potential candidate primary secondary cell17 The method according to any one of claims 10 to 16, comprising while acting as a serving network node to a user equipment: performing the steps of:responding to receipt from a target network node of an indication of at least one frequency of operation of at least one potential candidate primary secondary cell, said at least one frequency of operation being different to said first and said at least one further serving frequencies, the responding comprising generating an indication for transmission to a user equipment indicating said user equipment should perform measurements including at least one measurement at said at least one frequency of18. The method according to any one of claims 10 to 17, comprising receiving a5 measurement report from said user equipment, said measurement report including said at least one measurement at said at least one frequency of operation that is different to said first and said at least one further serving frequencies, and in response generating a handover request for transmission to said target network node said handover request including an indication of results of said user equipment measurement at said at least10 one frequency of operation that is different to said first and said at least one further serving frequencies.
19. A computer program comprising computer readable instructions which when executed by a processor on a network node cause said network node to perform a15 method according to any one of claims 10 to 18.
Citation Information
Patent Citations
Terminal and handover judgement method
US20160269967A1
Measurement method and apparatus
US20230031500A1
