MOBILITY IN WIRELESS COMMUNICATION SYSTEMS

Description

TECHNOLOGICAL FIELD

[0001] Various example embodiments relate to wireless communication systems, and more particularly, to facilitating mobility within such wireless communication systems.BACKGROUND

[0002] 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. Layer 1 or layer 2, sometimes termed lower layer triggered mobility LTM is being increasingly considered to reduce the latency, overhead and interruption time associated with a UE moving between the different cells. Potential problems associated with lower layer triggered mobility is that as the measurements used are lower layer measurements that are not averaged over time a non-ideal cell may be selected.

[0003] 3GPP contribution R2-2209482 Vivo 'Discussion on dynamic switch for L1 L2 mobility' Agenda item 8.4.2.3 Discussion and Decision, 10 - 19 Oct 2022 discusses handover preparations using L1 measurements received from a UE at a gNB-DU. During LTM preparation the network identifies and configures a set of potential neighboring cells that the user equipment (UE) can quickly switch to during a mobility event, based on real-time signal strength measurements reported by the UE through lower layer (L1 / L2) signalling. These are candidate cells for LTM.

[0004] Huawei Hi Silicon 'Solutions to cell switch in LTM' Discussion and Decision 14 - 18 Nov 2022 R2-2211642 3GPP TSG-RAN WG2 Meeting # 120 Agenda item 8.4.3.3 discloses LTM where the network provides LTM candidate cells to the UE, the UE reports L1 measurements, the network triggers a cell switch command and the UE switches.

[0005] Oppo 'Discussion on measurement related issues of L1 / L2 mobility' 3GPP draft; R2-2209626, 3GPP Vol. RAN WG30 Agenda item 8.4.2.4 discusses LTM and recognises a problem that the L1 beam measurement results may be less reliable for a cell switching decision then L3 cell measurements.BRIEF SUMMARY

[0006] The invention is defined by the independent claims. Embodiments are defined by the dependent claims.BRIEF DESCRIPTION

[0007] Some example embodiments will now be described with reference to the accompanying drawings in which: FIG. 1 illustrates a signalling diagram for the LTM procedure for a network using CU-DU split architecture; Fig. 2 illustrates a signalling diagram for the LTM procedure according to an embodiment; Fig. 3 illustrates a signalling diagram for the LTM procedure that reuses existing f1AP messages according to one embodiment; Fig. 4 illustrates a signalling diagram for the LTM procedure that reuses existing f1AP messages according to a further embodiment; Fig. 5 shows table 1 and indicates properties of the L3 handover information message; Fig. 6 shows table 2 and indicates properties of the LTM handover required message; Fig. 7 shows table 3 and indicates properties of the LTM handover refuse message; Fig. 8 shows table 4 and indicates properties of the Cause IE; Fig. 9 shows table 5 and indicates properties of the LTM handover confirm message; Fig. 10 shows table 6 and indicates properties of the LTM handover information message; Fig. 11 shows table 7 and indicates properties of the UE context modification request message; Fig. 12 shows table 8 and indicates properties of the LTM context modification response message; and Fig. 13 schematically shows a communication network according to an embodiment. DETAILED DESCRIPTION

[0008] Before discussing the example embodiments in any more detail, first an overview will be provided.

[0009] An example of a lower layer or L1 / 2 Triggered Mobility procedure is provided in Fig. 1. Herein, the UE is served by a cell under the source DU. The target cell is under the target DU. It is to be noted that the target DU and the source DU can be the same entity (i.e., both serving and target cell can be under the same DU, aka. Intra-DU scenario). However, the intra-DU scenario is not shown in Fig. 1. It is further to be noted that in the example of Fig. 1 the DUs are under the same CU. According to that: Steps 1-3: The UE sends a L3 Measurement Report message to the CU via the Source DU. The CU decides to use LTM and initiates LTM candidate cells preparation. Steps 4-5: The CU sends a UE context setup request to the target DU for the preparation of the target cells Steps 6-7: The CU sends a UE modification setup request to the source DU for the preparation of the target cells in the source DU. Additionally this message may be used for the provision of target cell information in the Source DU. Steps 8-12: The CU prepares the RRC Configuration and provides it to the UE. The UE stores the configuration of LTM candidate target cell(s) and transmits a RRCReconfigurationComplete message to the CU. Steps 13-14: The UE may perform DL synchronization and TA acquisition with candidate target cell(s) before receiving the LTM cell switch command. Step 15: The UE performs L1 measurements on the configured LTM candidate target cell(s), and transmits lower-layer measurement reports to the source DU. Step 16-17: The source DU decides to execute LTM cell switch to a target cell, and transmits a MAC CE triggering LTM cell switch Step 18: The UE switches to the configuration of the LTM candidate target cell and accesses the target cell. If needed (i.e., if Timing Advance is not available / valid) it performs Random Access. Steps 19-20: The UE indicates successful completion of the LTM cell switch towards target cell using an RRC Reconfiguration complete. Steps 21-22: UE context is released if the CU decides accordingly.

[0010] For L1 / L2-triggered mobility (LTM), the LTM decision is made by the gNB-DU. The LTM decision is based solely on L1 measurements reports and this may lead to the following problems: L1 measurements reports are unfiltered reports such that the channel impairments (fast fading, shadow fading, etc.) which results in the measured L1 RSRP values to be fluctuating significantly. This issue is more pronounced in FR2 (high frequency band) scenarios where the measured signal fluctuates significantly in the higher carrier frequencies. Handover decision based on unstable L1 RSRP measurements may lead to ping-pongs or a handover to a non-preferred cell (i.e. a cell may appear to be a suitable target cell, but only for a short period of time); which eventually leads to unnecessary or wrong handovers. Additionally, in case of misconfigurations, e.g., L1 handover decision may be triggered using different thresholds than L3 events. And the two events (i.e., L1 event and L3 event) may be triggered at the same time.

[0011] In case when both L1 / L2-triggered mobility and L3 based mobility are configured simultaneously, the current specification does not have a procedure to enable efficient coexistence and reliable handover.

[0012] The application proposes that the DU makes the decision based on its own configuration, but while considering additional L3 measurements information. The DU then informs the CU about the HO decision and CU sends F1AP Message, providing the L1 measurements.

[0013] Thus, according to embodiments, the DU makes the decision and proceeds with either L1 or L3 handover, this provides a decreased interruption time, and the paradigm of LTM as agreed in 3GPP and described with respect to Fig. 1 is followed.

[0014] In embodiments use is made of L3 measurements and CU decision in order to assist the LTM decision at the DU side. This has an advantage of increasing the LTM robustness (i.e., avoiding wrong cell selection based on unfiltered L1 measurements)

[0015] According to the invention: When initiating the L3 handover, the gNB-CU sends to the gNB-DU the necessary information before triggering the L3 handover preparation towards the target cell.

[0016] This information, referred to in this invention as L3 HO information, may include at least one or all of the following: ∘ Either the list of candidate target cells for L3 handover (i.e., TS 38.331 IE measResultListNR) received as a part of TS 38.331 IE MeasResults from UE via an RRC container sent from gNB-DU to gNB-CU ∘ A subset from the list of candidate target cells extracted from TS 38.331 IE MeasResults received from UE > For example, the gNB-CU can provide the gNB-DU with information (e.g., NR Cell Identity or physical cell ID) about the L3-based strongest cell or multiple cells sorted by RSRP / RSRQ with the L3-based strongest cell being the first. The gNB-DU decides to trigger LTM based on both L1 measurements received from the UE and the L3 HO information received from the gNB-CU. ∘ The gNB-DU defines a common set of neighbouring cells between L1 measurements and L3 HO information received from the gNB-CU. The common set may consist of a single cell or multiple cells. ∘ The gNB-DU triggers a LTM handover to a cell selected from this common set.

[0017] According to the invention A more robust decision to trigger an LTM handover which is reinforced by L3 measurements is provided.

[0018] The gNB-DU is prevented or at least impeded from choosing a wrong cell for the LTM handover, because the gNB-DU's choice is not solely based on unfiltered L1 measurement reports.

[0019] Embodiments provide three cases that can occur when the gNB-DU compares the L1 measurements with the L3 HO information. Case 1 - A common cell according to L1 measurements and L3 HO information. Case 2 - No common cell according to L1 measurements and L3 HO information. ∘ Case 2a - Unsuccessful DU-initiated LTM handover procedure. ∘ Case 2b - Successful DU-initiated LTM handover procedure. Case 3 - L3 HO information with no L1 measurements.

[0020] The above cases lead to possible impacts on F1AP procedures (signalling between the gNB-CU and the gNB_DU) and new F1AP messages which are described below in three different alternatives: Fig. 2 shows the signalling flow for the first alternative whereby the new signalling required for embodiments is provided on new F1AP messages between the DU and CU.Alternative 1: Call Flow Description

[0021] Four cases can occur when the gNB-DU compares the L1 measurements received from the UE with the L3 HO information received from the gNB-CU.

[0022] The four cases start when the gNB-DU receives the L3 HANDOVER INFORMATION message from the gNB-CU, step 15. According to the invention, this message includes L3 HO information. The L3 HO information comprises the Candidate Cells For Handover List IE as a list of candidate cells for the handover triggered by the upper layers in the gNB-CU. The L3 HO information may also comprise an RRC Container IE which includes the MeasurementReport reported by the UE (in step 12 of Fig. 3). Subsequently, the procedure for the four identified cases are as follows:Case 1 - A common cell according to L1 measurements and L3 HO information is found, in this case:

[0023] At step 16, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements.

[0024] At step 17, the gNB-DU retrieves one or more cells common to L1 measurements and L3 HO information.

[0025] At step 18, the gNB-DU sends a MAC CE command to the UE triggered to this common cell.

[0026] At step 19, the gNB-DU sends a CELL CHANGE message to the gNB-CU triggered to this common cell.

[0027] At step 20, the L1 Cell Change procedure is initiated.Case 2 - No common cell according to L1 measurements and L3 HO information is found:Case 2a - Unsuccessful DU-initiated LTM handover procedure.

[0028] At step 21, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements. At step 22, the gNB-DU cannot retrieve any cell common to L1 measurements and L3 HO information.

[0029] At step 23, the gNB-DU sends the LTM HANDOVER REQUIRED message to the gNB-CU to transfer information related to the handover triggered by the lower layers in the gNB-DU. This message includes the Candidate Cell for LTM HO ID List IE. The gNB-CU should consider the Candidate Cell For LTM HO ID List IE included in the LTM HANDOVER REQUIRED message as a list of candidate cells for the handover triggered by the lower layers in the gNB-DU. These cells are identified by the included NR CGls (new radio cell global identities). The gNB-DU may send for each candidate cell the Cell Results IE including the L1 measurements relevant to this candidate cell as received from UE.

[0030] At step 24, upon reception of the LTM HANDOVER REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in LTM HANDOVER REQUIRED message. The gNB-CU decides to proceed with the L3 handover instead of the LTM handover and therefore to initiate the L3 handover preparation.

[0031] At step 25, the gNB-CU sends the LTM HANDOVER REFUSE message to the gNB-DU including the Cause IE set to 'upper layer HO preparation'.

[0032] At step 26, the L3 handover procedure initiated during step 24 continues.Case 2b - Successful DU-initiated LTM handover procedure.

[0033] At step 27, the gNB-DU receives the L1 Measurement Report as in step 21.

[0034] At step 28, the gNB-DU cannot retrieve any cell common to L1 measurements and L3 HO information as in step 22.

[0035] At step 29, the gNB-DU sends the LTM HANDOVER REQUIRED message to the gNB-CU as in step 23.

[0036] At step 30, upon reception of the LTM HANDOVER REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in LTM HANDOVER REQUIRED message. The gNB-CU decides to proceed with the LTM handover instead of the L3 handover and therefore to not initiate the L3 handover preparation.

[0037] At step 31, the gNB-CU sends the LTM HANDOVER CONFIRM message to the gNB-DU including the Candidate Cell For LTM HO ID IE set as the NR CGI of the candidate cell selected by the gNB-CU for the handover triggered by the L1 layers in the gNB-DU. The gNB-DU shall consider that the gNB-CU used the L1 information in the LTM HANDOVER REQUIRED message not to initiate the preparation of a L3 handover.

[0038] At step 32, the gNB-DU sends a MAC CE command to the UE triggered to the cell identified by the NR CGI included in the LTM HANDOVER CONFIRM message.

[0039] At step 33, the L1 Cell Change procedure is initiated.Case 3 - L3 HO information with no L1 measurements

[0040] At step 34, the gNB-DU has not received an L1 Measurement Report with L1 measurements from the UE.

[0041] At step 35, the gNB-DU sends the LTM HANDOVER INFORMATION message to the gNB-CU to indicate that the LTM handover has not been initiated. This message includes the LTM HO status IE which is set to 'not initiated'.Alternative 1: Impacts on F1AP signalling

[0042] Below is the list of new F1AP messages in order to enable embodiments.• L3 HANDOVER INFORMATION

[0043] This message is sent by the gNB-CU and is used to transfer information related to the handover triggered by the upper layers in the gNB-CU.

[0044] Direction: gNB-CU to gNB-DU and illustrated in table 1 of Fig. 5.

[0045] The gNB-DU should use the Candidate Cells For Handover List IE included in the L3 HANDOVER INFORMATION message as a list of candidate cells for the handover triggered by the upper layers in the gNB-CU. The gNB-DU should use, if present, the RRC Container IE for the indication of measurement results by the upper layers at the UE. These cells are identified by the included NR CGls. The gNB-DU should compare these cells with other cells reported by the lower layers for the handover triggered by the lower layers in the gNB-DU. The gNB-DU should use the RRC Container IE if present for this comparison.

[0046] Note-1: after the gNB-CU-CP receives the MeasurementReport message from the UE, two signalling formats are possible 1. The gNB-CU-CP sends the MeasurementReport message in an RRC Container IE which is then decoded by the gNB-DU or 2. The gNB-CU-CP decodes the MeasurementReport message and builds a Cell Results IE under the Candidate Cells For Handover List IE as described for the LTM HANDOVER REQUIRED message • LTM HANDOVER REQUIRED

[0047] This message is sent by the gNB-DU and is used to transfer information related to the handover triggered by the lower layers in the gNB-DU.

[0048] Direction: gNB-DU to gNB-CU. The properties of the message are shown in table 2 of Fig. 6

[0049] The gNB-CU should consider the Candidate Cell For LTM HO ID List IE included in the LTM HANDOVER REQUIRED message as a list of candidate cells for the handover triggered by the lower layers in the gNB-DU. These cells are identified by the included NR CGls. The gNB-DU may send for each candidate cell the Cell Results IE including the lower layers measurements relevant to this candidate cell as received from UE so that the gNB-CU can compare these with the upper layers measurements that are received from the UE.• LTM HANDOVER REFUSE

[0050] This message is sent by the gNB-CU to indicate the request for the handover triggered by the lower layers in the gNB-DU was unsuccessful (i.e., not accepted by gNB-CU).

[0051] Direction: gNB-CU to gNB-DU. The properties of the messages are shown in table 3 in Fig. 7.

[0052] If the Cause IE included in the LTM HANDOVER REFUSE message is set to 'upper layer HO preparation', the gNB-DU shall consider the request for the handover triggered by the lower layers in the gNB-DU to be unsuccessful.

[0053] The purpose of the Cause IE is to indicate the reason for a particular event for the F1AP protocol and the properties of this IE are shown in table 4 in Fig. 8.• LTM HANDOVER CONFIRM

[0054] This message is sent by the gNB-CU to indicate the request for the handover triggered by the lower layers in the gNB-DU was successful (i.e., accepted by gNB-CU) and that the gNB-CU used the lower layers information in the LTM HANDOVER REQUIRED message to not initiate the preparation of a handover triggered by the upper layers.

[0055] Direction: gNB-CU to gNB-DU. The properties of this message are shown in table 5 in Fig. 9.

[0056] The gNB-CU shall set the Candidate Cell For LTM HO ID IE included in the LTM HANDOVER CONFIRM message as the NR CGI of the candidate cell selected for the handover triggered by the lower layers in the gNB-DU. The gNB-DU shall consider the gNB-CU used the lower layers information in the LTM HANDOVER REQUIRED message not to initiate the preparation of a handover triggered by the upper layers.• LTM HANDOVER INFORMATION

[0057] This message is sent by the gNB-DU to indicate that the handover request triggered by the lower layers of the gNB-DU has not been initiated.

[0058] Direction: gNB-DU to gNB-CU, the properties of this message are shown in table 6 in Fig. 10.

[0059] The gNB-CU should consider the Candidate Cell For LTM HO ID List IE included in the LTM HANDOVER REQUIRED message as a list of candidate cells for the handover triggered by the lower layers in the gNB-DU. These cells are identified by the included NR CGls. The gNB-DU may send the lower layers measurements relevant to the candidate cells that are received from UE so that the gNB-CU can compare these with the upper layers measurements that are received from the UE.Alternative 2: Reusing existing F1AP messages

[0060] There are two possible ways of reusing existing F1AP messages to implement embodiments. These are described below:Alternative 2a: One way of reusing existing F1AP messages.

[0061] Fig.3 shows the Call Flow or signalling diagram for alternative 2a Four cases can occur when the gNB-DU compares the L1 measurements received from the UE with the L3 HO information received from the gNB-CU.

[0062] The four cases start at step 6 when the gNB-DU receives the UE CONTEXT MODIFICATION REQUEST message from the gNB-CU including the LTM Modification Request IE which includes L3 HO information. The L3 HO information comprises the Candidate Cells For Handover List IE as a list of candidate cells for the handover triggered by the upper layers in the gNB-CU. The L3 HO information may also comprise an RRC Container IE which includes the MeasurementReport reported by the UE (step 12). Subsequently, the procedure for the four identified cases are as follows:Case 1 - A common cell according to L1 measurements and L3 HO information

[0063] At step 7, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements.

[0064] At step 8, the gNB-DU retrieves a cell common to L1 measurements and L3 HO information.

[0065] At step 9, the gNB-DU sends a MAC CE command to the UE triggered to this common cell.

[0066] At step 10, the gNB-DU sends a CELL CHANGE message to the gNB-CU triggered to this common cell.

[0067] At step 11, the L1 Cell Change procedure is initiated.Case 2 - No common cell according to L1 measurements and L3 HO informationCase 2a - Unsuccessful DU-initiated LTM handover procedure.

[0068] At step 12, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements.

[0069] At step 13, the gNB-DU cannot retrieve a cell common to L1 measurements and L3 HO information.

[0070] At step14, the gNB-DU sends the LTM HANDOVER REQUIRED message to the gNB-CU to transfer information related to the handover triggered by the lower layers in the gNB-DU. This message includes the Candidate Cell for LTM HO ID List IE. The gNB-CU should consider the Candidate Cell For LTM HO ID List IE included in the LTM HANDOVER REQUIRED message as a list of candidate cells for the handover triggered by the lower layers in the gNB-DU. These cells are identified by the included NR CGls. The gNB-DU may send for each candidate cell the Cell Results IE including the L1 measurements relevant to this candidate cell as received from UE.

[0071] At step 15, upon reception of the LTM HANDOVER REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in LTM HANDOVER REQUIRED message. The gNB-CU decides to proceed with the L3 handover instead of the LTM handover and therefore to initiate the L3 handover preparation.

[0072] At step 16, the gNB-CU sends the LTM HANDOVER REFUSE message to the gNB-DU including the Cause IE set to 'upper layer HO preparation'.

[0073] At step 17, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU including the LTM Modification Response IE which includes the LTM HO status IE set to 'execution cancel'. The gNB-CU shall consider that the gNB-DU has cancelled the execution of the LTM handover.

[0074] At step 18, the L3 handover procedure initiated during step 15 continuesCase 2b - Successful DU-initiated LTM handover procedure.

[0075] At step 19, the gNB-DU receives the L1 Measurement Report as in step 12.

[0076] At step 20, The gNB-DU cannot retrieve a cell common to L1 measurements and L3 HO information as in step 13.

[0077] At step 21, the gNB-DU sends the LTM HANDOVER REQUIRED message to the gNB-CU as in step 14.

[0078] At step 22, upon reception of the LTM HANDOVER REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in LTM HANDOVER REQUIRED message. The gNB-CU decides to proceed with the LTM handover instead of the L3 handover and therefore to not initiate the L3 handover preparation.

[0079] At step 23, the gNB-CU sends the LTM HANDOVER CONFIRM message to the gNB-DU including the Candidate Cell For LTM HO ID IE set as the NR CGI of the candidate cell selected by the gNB-CU for the handover triggered by the L1 layers in the gNB-DU. The gNB-DU shall consider that the gNB-CU used the L1 information in the LTM HANDOVER REQUIRED message not to initiate the preparation of a L3 handover.

[0080] At step 24, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU including the LTM Modification Response IE which includes the LTM HO status IE set to 'execution resume'. The gNB-CU shall consider that the gNB-DU has resumed the execution of the LTM handover.

[0081] At step 25, the gNB-DU sends a MAC CE command to the UE triggered to the cell identified by the NR CGI included in the LTM HANDOVER CONFIRM message.

[0082] At step 26, the L1 Cell Change procedure is initiated.Case 3 - L3 HO information with no L1 measurements

[0083] At step 27, the gNB-DU has not received an L1 Measurement Report with L1 measurements from the UE.

[0084] At step 28, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU to indicate that the LTM handover has not been initiated. This message includes the LTM Modification Response IE which includes the LTM HO status IE which is set to 'not initiated'.Alternative 2a: impacts on F1AP signalling

[0085] Below are new IEs (in bold) which can be added to the following existing F1AP messages in order to enable embodiments.• UE CONTEXT MODIFICATION REQUEST

[0086] This message includes a new TS 38.473 IE called LTM Modification Request IE. Details of this are provided in table 7 Fig. 11.

[0087] If the LTM Modification Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider this upper layers information for lower layers triggered handover.

[0088] If the Candidate Cells For Handover List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider that the candidate cells for handover should be compared with other cells reported by lower layers for lower layer triggered handover. These cells are identified by the included NR CGls.

[0089] If the RRC Container IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU may use it for the indication of measurement results by the upper layers at the UE. The gNB-DU may use the RRC Container IE if present for the comparison between the cells reported by the UE to the lower layers of the gNB-DU and the cells reported by the UE to the upper layers of the gNB-CU.

[0090] Note-2: after the gNB-CU-CP receives the MeasurementReport message from the UE, two signalling formats are possible : 1. The gNB-CU-CP sends the MeasurementReport message in an RRC Container IE which is then decoded by the gNB-DU or 2. The gNB-CU-CP decodes the MeasurementReport message and build a Cell Results IE under the Candidate Cells For Handover List IE as described for the LTM HANDOVER REQUIRED message • UE CONTEXT MODIFICATION RESPONSE

[0091] This message includes a new TS 38.473 IE called LTM Modification Response IE. Details of this are provided in table 8, Fig. 12.

[0092] If the LTM Modification Response IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall consider the gNB-DU has received the upper layers information for lower layer triggered handover.

[0093] If the LTM HO status IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall consider that the gNB-DU has not initiated the handover triggered by lower layers or has used upper layers information to resume or cancel the execution of the handover triggered by lower layers.

[0094] Below is the list of F1AP messages which are same as Alternative 1. LTM HANDOVER REQUIRED (see Alternative 1) LTM HANDOVER REFUSE (see Alternative 1) LTM HANDOVER CONFIRM (see Alternative 1)

[0095] Alternative 2b: Second way of reusing existing F1AP messages.

[0096] Fig. 4 shows the call Flow or signalling diagram for Alternative 2b.

[0097] Four cases can occur when the gNB-DU compares the L1 measurements received from the UE with the L3 HO information received from the gNB-CU.

[0098] The four cases start at step 6 when the gNB-DU receives the UE CONTEXT MODIFICATION REQUEST message from the gNB-CU including the LTM Modification Request IE which includes L3 HO information. The L3 HO information comprises the Candidate Cells For Handover List IE as a list of candidate cells for the handover triggered by the upper layers in the gNB-CU. The L3 HO information may also comprise an RRC Container IE which includes the MeasurementReport reported by the UE (step 12). Subsequently, the procedure for the four identified cases are as follows:Case 1 - A common cell according to L1 measurements and L3 HO information

[0099] At step 7, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements.

[0100] At step 8, the gNB-DU retrieves a cell common to L1 measurements and L3 HO information.

[0101] At step 9, the gNB-DU sends a UE CONTEXT MODIFICATION RESPONSE message to the CU which includes the LTM Modification Response IE where LTM HO status IE is set to 'execution resume'.

[0102] At step 10, the gNB-DU sends a MAC CE command to the UE triggered to this common cell.

[0103] At step 11, the gNB-DU sends a CELL CHANGE message to the gNB-CU triggered to this common cell.

[0104] At step 12, the L1 Cell Change procedure is initiated.Case 2 - No common cell according to L1 measurements and L3 HO informationCase 2a - Unsuccessful DU-initiated LTM handover procedure.

[0105] At step 13, the gNB-DU receives the L1 Measurement Report from the UE including the L1 measurements. The L1 measurements are reported by the UE for one or more cells. The L1 measurements may comprise RSRP, RSRQ or SINR measurements.

[0106] At step 14, the gNB-DU cannot retrieve a cell common to L1 measurements and L3 HO information.

[0107] At step 15, the gNB-DU sends the UE CONTEXT MODIFICATION REQUIRED message to the gNB-CU to transfer information related to the handover triggered by the lower layers in the gNB-DU. This message includes the LTM Modification Required IE which includes the Candidate Cell for LTM HO ID List IE. The gNB-CU should consider the Candidate Cell For LTM HO ID List IE included in the UE CONTEXT MODIFICATION REQUIRED message as a list of candidate cells for the handover triggered by the lower layers in the gNB-DU. These cells are identified by the included NR CGls. The gNB-DU may send for each candidate cell the Cell Results IE including the L1 measurements relevant to this candidate cell as received from UE.

[0108] At step 16, upon reception of the UE CONTEXT MODIFICATION REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in UE CONTEXT MODIFICATION REQUIRED message. The gNB-CU decides to proceed with the L3 handover instead of the LTM handover and therefore to initiate the L3 handover preparation.

[0109] At step 17, the gNB-CU sends the UE CONTEXT MODIFICATION REFUSE message to the gNB-DU including the Cause IE set to 'upper layer HO preparation'.

[0110] At step 18, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU including the LTM Modification Response IE which includes the LTM HO status IE set to 'execution cancel'. The gNB-CU shall consider that the gNB-DU has cancelled the execution of the LTM handover.

[0111] At step 19, the L3 handover procedure initiated during step 15 continues.Case 2b - Successful DU-initiated LTM handover procedure.

[0112] At step 20, the gNB-DU receives the L1 Measurement Report as in step 13.

[0113] At step 21, the gNB-DU cannot retrieve a cell common to L1 measurements and L3 HO information as in step 14.

[0114] At step 22, the gNB-DU sends the UE CONTEXT MODIFICATION REQUIRED message to the gNB-CU as in step 15.

[0115] At step 23, upon reception of the UE CONTEXT MODIFICATION REQUIRED message and if the L1 measurements are present, the gNB-CU may compare these with the L3 measurements included in the RRC MeasurementReport message that is received from the UE (step 1). The gNB-CU also uses the Candidate Cell for LTM HO ID List IE included in UE CONTEXT MODIFICATION REQUIRED message. The gNB-CU decides to proceed with the LTM handover instead of the L3 handover and therefore to not initiate the L3 handover preparation.

[0116] At step 24, the gNB-CU sends the UE CONTEXT MODIFICATION CONFIRM message to the gNB-DU including the LTM Modification Confirm IE which includes the Candidate Cell For LTM HO ID IE set as the NR CGI of the candidate cell selected by the gNB-CU for the handover triggered by the L1 layers in the gNB-DU. The gNB-DU shall consider that the gNB-CU used the L1 information in the UE CONTEXT MODIFICATION REQUIRED message not to initiate the preparation of a L3 handover.

[0117] At step 25, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU including the LTM Modification Response IE which includes the LTM HO status IE set to 'execution resume'. The gNB-CU shall consider that the gNB-DU has resumed the execution of the LTM handover.

[0118] At step 26, the gNB-DU sends a MAC CE command to the UE triggered to the cell identified by the NR CGI included in the LTM HANDOVER CONFIRM message.

[0119] At step 27, the L1 Cell Change procedure is initiated.Case 3 - L3 HO information with no L1 measurements

[0120] At step 28 the gNB-DU has not received an L1 Measurement Report with L1 measurements from the UE.

[0121] At step 29, the gNB-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU to indicate that the LTM handover has not been initiated. This message includes the LTM Modification Response IE which includes the LTM HO status IE which is set to 'not initiated'.

[0122] At step 30 the CU makes a decision to initiate the L4 handover preparation.

[0123] At step 31 L3 cell change occurs.

[0124] Fig. 13 schematically shows a wireless communications network according to an embodiment where a UE 10 is moving through the cells of this wireless network. Currently it is in cell 30a which is provided by distributed unit DU 20a and it is in the vicinity of cell 32a provided by distributed unit 20a and cell 30b and 32b provided by distributed unit 20b. Distributed units 20a and 20b are supported by central unit CU 40.

[0125] Lower layer triggered mobility preparation and early synchronisation is performed and the user equipment 10 transmits a L1 measurement report to distributed unit 20a. Transmitting and receiving circuitry 22 at DU 20a receives the report forwards the report to CU 40 where it is received by transmitting and receiving circuitry 42. CU 40 will communicate using transmitting and receiving circuitry 42 with other distributed units including distributed unit 20b and receives configuration information for the cells 30b and 32b supported by DU 20b. CU 40 forwards this information to the UE as an RRC reconfiguration message.

[0126] LTM may then proceed and user equipment 10 will transmit an L1 measurement report to DU 20a. An L3 mobility event may be detected at the UE 10 and may indicate that the UE 10 should target cell 32b and UE 10 will then send a layer 3 RRC measurement report for cell 32b to the distributing unit DU20a which will forward this to the central unit CU 40. Determining circuitry 48 at CU 40 may then determine a potential trigger for a handover to a cell supported by DU 20b and message generating circuitry 46 may generate a handover information message. The DU 20a may then receiving L3 handover information from the CU 40 which will include candidate cells for a handover and in some cases an RRC measurement report. Mobility control circuitry 24 within DU 20a will then consider both the L3 measurements and the L1 measurements and where there is a common cell will select this common cell for a handover. Message generating circuitry 26 will then generate a MAC CE command to trigger the cell change to the selected target cell at the UE 10 and message generating circuitry 26 will also generate a cell change message which will be transmitted by transmitting and receiving circuitry 22 to CU 40.

[0127] Where there is not a common cell mobility control circuitry 24 within DU20a will make a lower layer handover decision based on the candidate cells in the L1 measurements and will generate a message at message generating circuitry 26 for transmission to CU 40 indicating that a LTM handover is required. It will include candidate cells for that handover and L1 measurements.

[0128] Determining circuitry 48 within CU 40 will then determine whether or not the LTM should proceed. If it determines from the measurements that it should proceed message generating circuitry 46 will generate either an LTM handover confirm indicating the LTM is to proceed or it will generate a LTM handover refuse not and mobility control circuitry 44 will then manage a layer 3 handover .

[0129] In a further embodiment where there is no LTM determined within DU 20a , there are perhaps no L1 measurements, then the message generating circuitry 26 will generate a message indicating that LTM handover status is set to not initiate and mobility control circuitry 44 will then manage a layer 3 handover .

[0130] A person of skill in the art would readily recognize that steps of various above-described 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 machine-executable 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).

[0131] 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.

[0132] 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.

Claims

1. A distributed unit (20a) of an access network node, said distributed unit (20a) being for supporting radio coverage via a cell(30a) and for providing access to said cell to a user equipment (10), said distributed unit comprising: mobility control circuitry (24) configured: in response to receipt of layer 3 handover information for a user equipment (10), from a central unit (40) of said access network, said layer 3 handover information comprising a plurality of identifiers identifying candidate cells for layer 3 handover and where said mobility control circuitry (24) has access to layer 1 measurements for said user equipment, to select a cell for a handover in dependence upon said layer 3 handover information and said layer 1 measurements.

2. The distributed unit according to claim 1, wherein said layer 3 handover information further comprises measurement information for said candidate cells.

3. The distributed unit according to any preceding claim, wherein said mobility control circuitry (24) is configured to determine whether there is at least one common cell that is indicated as a candidate cell from said layer 3 handover information and as a candidate cell from said layer 1 measurements and where so, to select one of said at least one common cells as said cell for said handover.

4. The distributed unit according to claim 3, wherein said mobility control circuitry is configured in response to determining no common candidate cells from said layer 1 measurements and said layer 3 information, to select as a potential target cell one of said candidate cells from said layer 1 measurements; said distributed unit further comprising message generating circuitry (26), said message generating circuitry being configured in response to said mobility control circuitry selecting said potential target cell, to generate a message for transmission to said central unit, said message indicating that a lower layer handover to said potential target cell is requested.

5. The distributed unit according to claim 4, said mobility control circuitry being configured, in response to receipt of a message indicating handover has been accepted from said central unit, to select said potential target cell as said cell for said handover.

6. The distributed unit according to claim 3 or 5, further comprising message generating circuitry (26), said message generating circuitry being configured in response to said mobility control circuitry selecting a cell for said handover, to generate a control command to trigger handover to said selected cell for transmission to said user equipment.

7. The distributed unit according to any preceding claim, said mobility control circuitry (24) being configured where said mobility control circuitry does not have access to layer 1 measurements for said user equipment, to control message generating circuitry to generate a message indicating lower layer triggered mobility is not initiated for said user equipment.

8. A central unit (40) for controlling a plurality of distributed units (20a, 20b) comprising: determining circuitry (48) configured to determine from layer 3 user equipment measurement information, candidate cells for a cell handover for said user equipment; message generating circuitry (46) configured to generate a message for transmission to a distributed unit (20a) supporting a cell (30a) providing radio coverage to said user equipment (10) , said message comprising layer 3 handover information relating to said cell handover, said layer 3 handover information comprises a plurality of identifiers identifying candidate cells for a layer 3 handover; and transmitting circuitry (42) configured to transmit said message to said distributed unit.

9. The central unit according to claim 8, wherein said layer 3 handover information further comprises measurement information for said candidate cells.

10. The central unit according to any one of claims 8 to 9, wherein said message generating circuitry (46) is configured to generate said message in response to at least one of the following: said determining circuitry (48) at said central unit detecting a condition for triggering a layer 3 handover; a predetermined time having elapsed; and said central unit detecting an internal trigger for said message generation during preparation steps performed for preparing lower layer triggered mobility for said user equipment.

11. The central unit according to any one of claims 8 to 10, wherein said determining circuitry is responsive to receipt of a lower layer triggered mobility required message received from said distributed unit, to determine whether to allow a lower layer triggered handover or whether to refuse a lower layer handover; and said message generating circuitry is configured to generate a respective one of a lower layer triggered handover refused or a lower layer handover confirmed message.

12. The central unit according to claim 11, wherein said central unit further comprising mobility control circuitry (44), said mobility control circuitry being responsive to said determining circuitry determining to refuse said lower layer triggered handover to initiate layer 3 handover preparations.

13. The central unit (40) according to any one of claims 8 to 12, wherein said lower layer mobility required request comprises at least one identifier for at least one candidate cell for said lower layer triggered mobility and a respective at least one layer 1 measurement report for said at least one cell, said determining circuitry being configured to determine in dependence upon said layer 1 measurement reports and layer 3 measurement reports a target cell for said handover.