Method and apparatus for optimization of mutual mobility between distributed radio access network nodes

Abstract

The invention relates to data communication. Certain examples provide a user equipment, UE, (110) for accessing a radio access network, RAN, (100) comprising at least: a central node (210), and distributed nodes (220), the central node controlling the distributed nodes, where the UE comprises: at least one processor (12); and at least one memory (13) storing instructions (14) that, when executed by the at least one processor, cause the UE to at least: establish a connection towards a radio access network; receiving (502) a UE context modification request from the central node, the UE context modification request comprising: a request to change at least part of the low-layer configuration, and an identifier related to the request; performing (502) a change in the requested low-layer configuration; sending (504), towards the central node, an acknowledgement that the requested change has been performed; and sending (505) the identifier towards the distributed node.

Description

Technical Field

[0001] Various examples of the present disclosure relate to the field of data communication, and in particular to: user equipment, distributed nodes, central nodes, and systems for data communication. Certain examples, although not affecting the foregoing, relate to: user equipment, distributed nodes, central nodes, and systems for inter-cell mobility based on layer 1 / layer 2 in a radio access network. Background Art

[0002] Traditional in Radio Access Network RAN g During intra-gNB-CU mobility, the user equipment UE moves from one cell of the gNB-CU to another cell of the gNB-CU. g During intra-NB-CU mobility, the number of nodes currently serving the UE g NB-CU g The NB distributed unit DU switches the service of the UE to a new gNB-DU of the gNB-CU which will start serving the UE. The intra-gNB-CU handover HO procedure (also referred to as the inter-gNB-DU HO procedure) is performed to achieve intra-gNB-CU mobility (also referred to as inter-gNB-DU mobility).

[0003] The traditional intra-gNB-CU (inter-gNB-DU) HO process is not always optimal.

[0004] In some cases, it may be desirable to provide improved data communication, especially such as in intra-gNB-CU mobility.

[0005] The listing or discussion of any previously disclosed document or any background in this specification should not be regarded as an admission that the document or background is part of the prior art or is common general knowledge. One or more aspects / examples of the present disclosure may or may not address one or more of the background issues. Summary of the invention

[0006] The scope of protection sought by various embodiments of the present invention is defined by the claims.

[0007] According to various examples of the present disclosure, but not necessarily all examples, examples as claimed in the appended claims are provided.Any examples and features described in this specification that do not belong to the scope of the independent claims should be interpreted as examples that help understand various embodiments of the present invention.

[0008] According to at least some examples of the present disclosure, a user equipment UE for accessing a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and a distributed node, the central node controlling the distributed node, wherein the UE comprises:

[0009] at least one processor; and

[0010] At least one memory stores instructions, which when executed by at least one processor, cause the UE to at least:

[0011] establishing a connection towards a radio access network;

[0012] A UE context modification request is received from a central node, wherein the UE context modification request

[0013] include:

[0014] Requests to change at least part of the low-level configuration, and

[0015] an identifier associated with the request;

[0016] Perform the requested low-level configuration changes;

[0017] sending a confirmation towards the central node that the requested change has been performed; and

[0018] An identifier is sent towards the distributed nodes.

[0019] According to various examples, but not necessarily all examples, of the present disclosure, there is provided a method for a user equipment (UE), the method comprising actions, at least in part, causing:

[0020] Establishing a connection towards a radio access network RAN, wherein the RAN comprises at least: a central node, and distributed nodes, the central node controlling the distributed nodes;

[0021] A UE context modification request is received from a central node, where the UE context modification request includes:

[0022] Requests to change at least part of the low-level configuration, and

[0023] an identifier associated with the request;

[0024] Perform the requested low-level configuration changes;

[0025] sending a confirmation towards the central node that the requested change has been performed; and

[0026] An identifier is sent towards the distributed nodes.

[0027] According to various, but not necessarily all, examples of the present disclosure, a chipset is provided that includes processing circuitry configured to perform the above-described method.

[0028] According to various examples, but not necessarily all examples, of the present disclosure, modules, circuit systems, devices, and / or systems including components for performing the above-described methods are provided.

[0029] According to various examples of the present disclosure, but not necessarily all examples, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the above-described method.

[0030] According to various examples of the present disclosure, but not necessarily all examples, a non-transitory computer-readable medium encoded with instructions is provided, which, when executed by at least one processor, causes the above method to perform at least the following items.

[0031] According to at least some examples of the present disclosure, a user equipment UE for accessing a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and a distributed node, the central node controlling the distributed node, wherein the UE comprises:

[0032] means for establishing a connection towards a radio access network;

[0033] A component for receiving a UE context modification request from a central node, the UE context modification request comprising:

[0034] Requests to change at least part of the low-level configuration, and

[0035] an identifier associated with the request;

[0036] means for performing the requested low-level configuration change;

[0037] means for sending towards the central node a confirmation that the requested change has been performed; and

[0038] Means for sending an identifier towards a distributed node.

[0039] The following part of this Summary section describes various features that may be features of any of the examples described in the preceding part of the Summary section.A description of a function should be considered to also disclose any means suitable for performing that function.

[0040] In some examples, but not necessarily all examples, the UE context modification request is received from the central node in at least one selected from the group consisting of:

[0041] Layer 3 protocol messages;

[0042] Radio Resource Configuration RRC message; and

[0043] RRC reconfiguration message.

[0044] In some examples, but not necessarily all examples, the identifier is sent to the distributed node, at least one selected from the following group:

[0045] via layer 2 signaling;

[0046] in layer 2 protocol messages; and

[0047] In the media access control MAC control element CE.

[0048] In some examples, but not necessarily all examples, the identifier is sent to the distributed node in at least one selected from the group consisting of:

[0049] via layer 1 signaling;

[0050] In uplink control information UCI;

[0051] In a channel state information (CSI) report; and

[0052] In layer 1 measurement reports.

[0053] In some examples, but not necessarily all examples, the UE context modification request includes: an indicator for requesting the UE to confirm to the distributed node that the UE has performed the requested change; and wherein the UE is also configured to: at least in part based on the received indicator, send an identifier toward the distributed node for confirming to the distributed node that the UE has performed the requested change.

[0054] In some examples, but not necessarily all examples, the indicator is: a flag, or an identifier.

[0055] In some examples, but not necessarily all, the identifier is:

[0056] An identifier used to identify the request;

[0057] a multi-bit identifier; or

[0058] Logo.

[0059] In some examples, but not necessarily all examples, the requested change includes: a request for the UE to at least one selected from the following group:

[0060] Reconfigure the UE's low-layer protocols;

[0061] Adjusting layer 1 L1 measurements performed by the UE;

[0062] Reconfigure UE's L1 measurement report;

[0063] measuring one or more beams of a target cell; and

[0064] Report one or more measurements of one or more beams of the target cell.

[0065] According to at least some examples of the present disclosure, a distributed node of a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and a distributed node, the central node controlling the distributed node, wherein the distributed node comprises:

[0066] at least one processor; and

[0067] At least one memory storing instructions that, when executed by at least one processor, cause the distributed node to at least:

[0068] A first user equipment UE context modification request is received, the first user equipment UE

[0069] The context modification request is sent from the central node to the distributed node, and the first UE goes up and down

[0070] A request for modification includes:

[0071] Requests to change at least part of the low-level configuration, and

[0072] an identifier associated with the request;

[0073] Receive a second UE context modification request, the second UE context modification request from

[0074] The central node sends the second UE context modification request to the UE via the distributed node.

[0075] Please include:

[0076] Requests to change at least part of the low-level configuration, and

[0077] Identifier;

[0078] sending a second UE context modification request towards the UE; and

[0079] An identifier is received from a UE.

[0080] According to at least some examples of the present disclosure, there is provided a method for a distributed node of a radio access network RAN, the radio access network RAN ​​comprising at least: a central node, and a distributed node, the central node controlling the distributed node, wherein the method comprises actions at least in part causing:

[0081] A first user equipment UE context modification request is received, the first user equipment UE context modification request is sent from the central node to the distributed node, the first UE context modification request includes:

[0082] Requests to change at least part of the low-level configuration, and

[0083] an identifier associated with the request;

[0084] A second UE context modification request is received, where the second UE context modification request is sent from the central node to the UE via the distributed node, where the second UE context modification request includes:

[0085] Requests to change at least part of the low-level configuration, and

[0086] Identifier;

[0087] sending a second UE context modification request towards the UE; and

[0088] An identifier is received from a UE.

[0089] According to various, but not necessarily all, examples of the present disclosure, a chipset is provided that includes processing circuitry configured to perform the above-described method.

[0090] According to various examples, but not necessarily all examples, of the present disclosure, modules, circuit systems, devices, and / or systems including components for performing the above-described methods are provided.

[0091] According to various examples of the present disclosure, but not necessarily all examples, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the above-described method.

[0092] According to various examples of the present disclosure, but not necessarily all examples, a non-transitory computer-readable medium encoded with instructions is provided, which, when executed by at least one processor, causes the above method to perform at least the following items.

[0093] According to at least some examples of the present disclosure, a distributed node of a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and a distributed node, the central node controlling the distributed node, wherein the distributed node comprises:

[0094] A component for receiving a first user equipment UE context modification request, the first user equipment UE context modification request is sent from the central node to the distributed node, the first UE context modification request includes:

[0095] Requests to change at least part of the low-level configuration, and

[0096] an identifier associated with the request;

[0097] A component for receiving a second UE context modification request, the second UE context modification request is sent from the central node to the UE via the distributed node, the second UE context modification request comprising:

[0098] Requests to change at least part of the low-level configuration, and

[0099] Identifier;

[0100] means for sending a second UE context modification request towards the UE; and

[0101] Means for receiving an identifier from a UE.

[0102] The following part of this Summary section describes various features that may be features of any of the examples described in the preceding part of the Summary section.A description of a function should be considered to also disclose any means suitable for performing that function.

[0103] In some examples, but not necessarily all examples, the distributed node is further configured to determine that the UE has performed the requested change based at least in part on the identifier received from the UE.

[0104] In some examples, but not necessarily all examples, the distributed node is further configured to: send a response to the first UE context modification request towards the central node.

[0105] In some examples, but not necessarily all examples, the response to the first UE context modification request includes: an identifier or a replacement identifier for identifying the request.

[0106] In some examples, but not necessarily all, the distributed nodes are also configured to:

[0107] receiving from the UE a confirmation that the requested change has been performed, for transmission towards the central node; and

[0108] This confirmation is sent towards the central node.

[0109] In some examples, but not necessarily all examples, the first UE context modification request includes a request for at least one or more of the following:

[0110] Reconfigure the UE's low-layer protocols.

[0111] Adjust the interpretation of layer 1 L1 measurement reports received from UE;

[0112] receiving L1 measurements for the target cell from the UE;

[0113] associating one or more measurements with the one or more beams of the target cell, the one or more measurements from a measurement report received from the UE; and

[0114] Handover the UE to at least one item selected from the following group:

[0115] Target cells controlled by distributed nodes;

[0116] a target cell controlled by another distributed node; and

[0117] One or more candidate target cells.

[0118] In some examples, but not necessarily all examples, the first UE context modification request includes: a plurality of requested changes to a lower layer configuration, and wherein:

[0119] The identifier is configured to: identify multiple requested changes, or

[0120] The identifier includes a plurality of identifiers configured to respectively identify a plurality of requested changes.

[0121] In some examples, but not necessarily all, the distributed nodes are also configured to:

[0122] Based at least in part on the identifier received from the central node, adjusting an interpretation of a layer 1 L1 measurement report received from the UE; and / or

[0123] Based at least in part on the identifier received from the central node, one or more measurements are associated with one or more beams of the target cell, the one or more measurements from the measurement report received from the UE.

[0124] In some examples, but not necessarily all examples, the distributed node is further configured to determine, based at least in part on the identifier received from the UE, whether one or more L1 measurements received from the UE are to be associated with at least one item selected from the following group:

[0125] Target community;

[0126] one or more candidate target cells;

[0127] one or more beams of a target cell; and

[0128] One or more beams of one or more candidate target cells.

[0129] In some examples, but not necessarily all, the distributed nodes are also configured to:

[0130] Determining to trigger the UE to perform a handover of the UE to a target cell is based at least in part on at least one item selected from the group consisting of:

[0131] an identifier received from the UE; and

[0132] After receiving the identifier from the UE, an L1 measurement report is received from the UE.

[0133] In some examples, but not necessarily all examples, the second UE context modification request is received from the central node in at least one selected from the group consisting of:

[0134] Layer 3 protocol messages;

[0135] Radio Resource Configuration RRC message; and

[0136] RRC reconfiguration message.

[0137] In some examples, but not necessarily all examples, the identifier is received from the UE, at least one selected from the following group:

[0138] via layer 2 signaling;

[0139] in layer 2 protocol messages; and

[0140] In the media access control MAC control element CE.

[0141] In some examples, but not necessarily all examples, the identifier is received from the UE, at least one selected from the following group:

[0142] via layer 1 signaling;

[0143] In uplink control information UCI;

[0144] In a channel state information (CSI) report; and

[0145] In layer 1 measurement reports.

[0146] In some examples, but not necessarily all examples, the second UE context modification request includes: an indicator for requesting the UE to confirm to the distributed node that the UE has performed the requested change; and wherein the distributed node is also configured to: receive an identifier from the UE for confirming to the distributed node that the UE has performed the requested change.

[0147] In some examples, but not necessarily all examples, the indicator is: a flag, an identifier.

[0148] In some examples, but not necessarily all, the identifier is:

[0149] An identifier used to identify the request;

[0150] a multi-bit identifier; or

[0151] Logo.

[0152] In some examples, but not necessarily all examples, the requested change of the second UE context modification request includes: a request for the UE, at least one selected from the following group:

[0153] Reconfigure the UE's low-layer protocols;

[0154] Adjusting layer 1 L1 measurements performed by the UE;

[0155] Reconfigure UE's L1 measurement report;

[0156] measuring one or more beams of a target cell; and

[0157] Report one or more measurements of one or more beams of the target cell.

[0158] According to at least some examples of the present disclosure, a central node of a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and distributed nodes, the central node controlling the distributed nodes, wherein the central node comprises:

[0159] at least one processor; and

[0160] At least one memory storing instructions that, when executed by at least one processor, cause the distributed node to at least:

[0161] Generate an identifier associated with a request to change at least part of a low-level configuration

[0162] association;

[0163] Sending a first user equipment UE context modification request towards the distributed node,

[0164] A user equipment UE context modification request includes:

[0165] Change at least some of the low-level requests, and

[0166] Identifiers; and

[0167] Sending a second UE context modification request to the UE, the second UE context modification request

[0168] The request includes:

[0169] Requests to change at least part of the low-level configuration, and

[0170] Identifier.

[0171] According to at least some examples of the present disclosure, a method for a central node of a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and a distributed node, the central node controlling the distributed node, the method comprising:

[0172] generating an identifier associated with a request to change at least a portion of a low-level configuration;

[0173] Sending a first user equipment UE context modification request towards the distributed node, where the first user equipment context modification request includes:

[0174] Change at least some of the low-level requests, and

[0175] Identifiers; and

[0176] Sending a second UE context modification request towards the UE, the second UE context modification request comprising:

[0177] Requests to change at least part of the low-level configuration, and

[0178] Identifier.

[0179] According to various, but not necessarily all, examples of the present disclosure, a chipset is provided that includes processing circuitry configured to perform the above-described method.

[0180] According to various examples, but not necessarily all examples, of the present disclosure, modules, circuit systems, devices, and / or systems including components for performing the above-described methods are provided.

[0181] According to various examples of the present disclosure, but not necessarily all examples, there is provided a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform the above-described method.

[0182] According to various examples of the present disclosure, but not necessarily all examples, a non-transitory computer-readable medium encoded with instructions is provided, which, when executed by at least one processor, causes the above method to perform at least the following items.

[0183] According to at least some examples of the present disclosure, a central node of a radio access network RAN ​​is provided, the radio access network RAN ​​comprising at least: a central node and distributed nodes, the central node controlling the distributed nodes, wherein the central node comprises:

[0184] means for generating an identifier associated with a request to change at least a portion of a low level configuration;

[0185] A component configured to send a first user equipment UE context modification request towards a distributed node, the first user equipment context modification request comprising:

[0186] Change at least some of the low-level requests, and

[0187] Identifiers; and

[0188] A component for sending a second UE context modification request towards the UE, the second UE context modification request comprising:

[0189] Requests to change at least part of the low-level configuration, and

[0190] Identifier.

[0191] The following part of this Summary section describes various features that may be features of any of the examples described in the preceding part of the Summary section.A description of a function should be considered to also disclose any means suitable for performing that function.

[0192] In some examples, but not necessarily all examples, the central node is further configured to receive a response to the first UE context modification request from the distributed node.

[0193] In some examples, but not necessarily all examples, the response to the first UE context modification request includes: an identifier or a replacement identifier for identifying the request.

[0194] In some examples, but not necessarily all examples, the central node is also configured to:

[0195] A confirmation is received from the UE that the requested change has been performed.

[0196] In some examples, but not necessarily all examples, the first UE context modification request includes a request for at least one or more of the following:

[0197] Reconfigure the low-level protocols of distributed nodes.

[0198] Adjust the interpretation of layer 1 L1 measurement reports received from UE;

[0199] receiving L1 measurements for the target cell from the UE;

[0200] associating one or more measurements with the one or more beams of the target cell, the one or more measurements from a measurement report received from the UE; and

[0201] Handing over the UE from the cell of the distributed node to at least one selected from the following group:

[0202] Target cell, and

[0203] One or more candidate target cells.

[0204] In some examples, but not necessarily all examples, the first UE context modification request includes: a plurality of requested changes to a lower layer configuration, and wherein:

[0205] The identifier is configured to: identify multiple requested changes, or

[0206] The identifier includes a plurality of identifiers configured to respectively identify a plurality of requested changes.

[0207] In some examples, but not necessarily all examples, the second UE context modification request is sent to the UE in at least one selected from the following group:

[0208] Layer 3 protocol messages;

[0209] Radio Resource Configuration RRC message; and

[0210] RRC reconfiguration message.

[0211] In some examples, but not necessarily all examples, the second UE context modification request includes an indicator for requesting the UE to confirm to the distributed node that the UE has performed the requested change.

[0212] In some examples, but not necessarily all examples, the indicator is: a flag, or an identifier.

[0213] In some examples, but not necessarily all, where the identifier is:

[0214] An identifier used to identify the request;

[0215] a multi-bit identifier; or

[0216] Logo.

[0217] In some examples, but not necessarily all examples, the requested change of the second UE context modification request includes: requesting the UE to perform at least one item selected from the following group:

[0218] Reconfigure the UE's low-layer protocols;

[0219] Adjusting layer 1 L1 measurements performed by the UE;

[0220] Reconfigure UE's L1 measurement report;

[0221] measuring one or more beams of a target cell; and

[0222] Report one or more measurements of one or more beams of the target cell.

[0223] Although the above examples and optional features of the present disclosure are described separately, it should be understood that their provision in all possible combinations and arrangements is included in the present disclosure. It should be understood that each example of the present disclosure may include any or all features described for other examples of the present disclosure, and vice versa. In addition, it should be understood that any one or more or all features in any combination can be implemented by devices, methods, and / or computer program instructions as needed and appropriate, or be included in devices, methods, and / or computer program instructions, or be executed by devices, methods, and / or computer program instructions. BRIEF DESCRIPTION OF THE DRAWINGS

[0224] Some examples will now be described with reference to the accompanying drawings, in which:

[0225] Figure 1 An example of the subject matter described herein is shown;

[0226] Figure 2 Another example of the subject matter described herein is shown;

[0227] Figure 3 Another example of the subject matter described herein is shown;

[0228] Figure 4 Another example of the subject matter described herein is shown;

[0229] Figure 5 Another example of the subject matter described herein is shown;

[0230] Figure 6 Another example of the subject matter described herein is shown;

[0231] Figure 7 Another example of the subject matter described herein is shown;

[0232] Figure 8 Another example of the subject matter described herein is shown, and

[0233] Fig. 9 Another example of the subject matter described herein is shown.

[0234] The drawings are not necessarily drawn to scale. For clarity and brevity, certain features and views in the drawings may be shown schematically or exaggerated in proportion. For example, the dimensions of some elements in the drawings may be exaggerated relative to other elements to aid in illustration. Similar reference numerals may be used in the drawings to represent similar features. For clarity, all reference numerals may not necessarily be shown in all drawings.

[0235] In the drawings (and description), similar features may be referenced by the same three-digit number. In the drawings (and description), optional subscripts for the three-digit numbers may be used to distinguish different instances of similar features. Thus, three-digit numbers without a subscript may be used as a general reference, while three-digit numbers with a subscript may be used as a specific reference. A subscript may include: a single digit marking different instances. A subscript may include: two digits, the two digits including: a first digit marking a group of instances, and a second digit marking a different instance in the group.

[0236] Abbreviations / Definitions

[0237] 5G Fifth Generation

[0238] CE Control Elements

[0239] CU Central Unit / Central Node

[0240] CSI Channel State Information

[0241] DL Downlink

[0242] DU Distributed Unit / Distributed Node

[0243] gNB gNodeB

[0244] HO Handover

[0245] ID Identifier

[0246] L1 Layer 1

[0247] L2 Layer 2

[0248] L3 Layer 3

[0249] MAC Media Access Control

[0250] NR New Radio

[0251] RAN Radio Access Network

[0252] RRC Radio Resource Configuration

[0253] UCI Uplink Control Information

[0254] UE User Equipment

[0255] UL Uplink DETAILED DESCRIPTION

[0256] Figure 1 An example of a network 100 is schematically shown, the network 100 includes: a plurality of network nodes, the plurality of network nodes including: a terminal node 110 (also referred to as a user equipment UE), an access node 120, and one or more core nodes 130. The terminal node 110 and the access node 120 communicate with each other. The access node 120 communicates with the one or more core nodes 130. The one or more core nodes 130 may communicate with each other in some examples, but not necessarily all examples. The one or more access nodes 120 may communicate with each other in some examples, but not necessarily all examples.

[0257] In this example, the network 100 is a radio telecommunication network, ie a Radio Access Network RAN, in which at least some of the terminal nodes 110 and the access nodes 120 communicate with each other using transmission / reception of radio waves.

[0258] The RAN 100 may be a cellular network comprising: a plurality of cells 122, each cell 122 being served by an access node 120. The access node 120 comprises: a cellular radio transceiver. The terminal node 110 comprises: a cellular radio transceiver.

[0259] In the particular example shown, network 100 is a Next Generation (NG), or New Radio (NR) network. NR is the name given by the Third Generation Partnership Project (3GPP) for fifth generation (5G) technology.

[0260] The interface between the terminal node 110 and the access node 120 is a radio interface 124 (eg, a Uu interface). The interface between the access node 120 and one or more core nodes 130 is a backhaul interface 128 (eg, an S1 and / or NG interface).

[0261] Depending on the exact deployment scenario, the access node 120 may be a RAN node, such as a NG-RAN node. The NG-RAN node may be a gNodeB (gNB), which provides NR user plane and control plane protocol terminals towards the UE. The NG-RAN node may be a new generation evolved universal terrestrial radio access network (E-UTRAN) NodeB (ng-eNB), which provides E-UTRA user plane and control plane protocol terminals towards the UE. The gNB and ng-eNB may be connected to each other via an Xn interface. The gNB and ng-eNB are also connected to the 5G core (5GC) via an NG interface, more specifically, to the AMF (access and mobility management function) via an NG-C interface, and to the UPF (user plane function) via an NG-U interface. The access nodes 120 may be connected to each other via an Xn interface 126. The cellular network 100 may be configured to operate in a licensed or unlicensed band, particularly an unlicensed band such as 60 GHz, where beamforming is necessary to achieve the desired coverage.

[0262] The access node 120 may be deployed in NR standalone operation / scenario. The access node 120 may be deployed in NR non-standalone operation / scenario. The access node may be deployed in carrier aggregation (CA) operation / scenario. The access node 120 may be deployed in dual connectivity operation / scenario (i.e., multi-radio access technology-dual connectivity (MR-DC)), such as but not limited to the following:

[0263] Evolved Universal Terrestrial Radio Access - New Radio Dual Connectivity (EUTRA-NR-DC, also known as EN-DC),

[0264] New Radio - Evolved Universal Terrestrial Radio Access Dual Connectivity (NR-EUTRA-DC, also known as NE-DC),

[0265] Next Generation Radio Access Network Evolved Universal Terrestrial Radio Access - New Radio Dual Connectivity (NG-RAN E-UTRA-NR Dual Connectivity, also known as NGEN-DC), or

[0266] New Radio Dual Connectivity (also known as NR-DC).

[0267] In this non-standalone / dual connectivity deployment, the access nodes 120 may be connected to each other via an X2 or Xn interface, and to an evolved packet core (EPC) via an S1 interface, or to a 5GC via an NG interface.

[0268] Terminal nodes 110 are network elements in a network that terminate at the user side of a wireless link. They are devices that allow access to network services. Terminal nodes 110 may be referred to as user equipment (UE), mobile terminals, or mobile stations. The term "user equipment" may be used to specify a mobile device that includes a smart card for authentication / encryption, such as a user identity module (SIM). In other examples, the term "user equipment" is used to specify a mobile device that includes a circuit system for authentication / encryption embedded as part of the user equipment, such as a software SIM.

[0269] The access node 120 is a network element in the network that is responsible for radio transmission and reception to and from the terminal node 110 in one or more cells 122. Such an access node may also be referred to as a transmission reception point (TRP) or a base station. The access node 120 is a network terminal of a radio link. The access node 120 may be implemented as a single network device, or decomposed / distributed across two or more RAN nodes (such as a central unit (CU), a distributed unit (DU), a remote radio head (RRH)), using different functional division architectures and different interfaces.

[0270] In the following description, the access node will be referred to as gNB 120, and the terminal node 110 will be referred to as UE 110.

[0271] Figure 2 An example of an access node 120 (e.g., a gNB) is illustrated. In this example, the access node has a decomposed (divided) architecture. The gNB 120 includes: one or more distributed units / distributed nodes (gNB-DU) 220, and a central unit / central node (gNB-CU) 210.

[0272] The gNB-CU 210 is a logical node, referred to as a central node, configured to host the radio resource connection (RRC) layer and other layers of the gNB 120. The gNB-CU 210 controls the operation of one or more gNB-DUs 220. The gNB-DU 220 is a logical node, referred to as a distributed node, configured to host the radio link control (RLC) protocol layer, the media access control (MAC) layer, and the physical (PHY) layer of the access node (gNB) 120. The gNB-DU 220 communicates to the RRC layer hosted by the gNB-CU via a dedicated interface 250 (F1).

[0273] one g The NB-DU 220 may support one or more cells 122 (not shown in the figure). One cell is supported by only one gNB-DU 220.

[0274] The gNB-CU 210 and the gNB-DU 220 communicate via a dedicated interface 250 (F1 interface). The F1 interface 250 connects the radio resource connection (RRC) layer hosted by the gNB-CU 210 to different lower layers (e.g., Layer 1 and Layer 2) hosted by the gNB-DU 220. The F1 interface functions are divided into: F1-control plane functions (F1-C) 2501, and F1-user plane functions (F1-U) 2502.

[0275] In the following description: the central unit of the gNB (i.e., gNB-CU) will be referred to as CU 210, the distributed unit of the gNB (i.e., gNB-DU) will be referred to as DU 220, and the terminal node 110 will be referred to as UE 110.

[0276] As described above, the gNB includes: a node that provides NR user plane and control plane protocol terminals towards the UE. The gNB is connected to the 5GC via the NG interface, for example according to Section 3.2 of 3GPP TS38.300V16.6.0 (2021-06).

[0277] The CU includes: a logical node that, for example, hosts the RRC, SDAP, and PDCP protocols of a gNB, or hosts the RRC and PDCP protocols of an en-gNB, which controls the operation of one or more DUs. The CU terminates at the F1 interface connected to the DU.

[0278] The DU includes logical nodes such as the RLC, MAC, and PHY layers that host the gNB or en-gNB, and its operation is partially controlled by the CU. One DU supports one or more cells. One cell is supported by only one DU. The DU terminates at the F1 interface connected to the CU.

[0279] The CU control plane (i.e., CU-CP) includes logical nodes such as hosting RRC and the control plane part of the PDCP protocol for the CU of an en-gNB or gNB. The CU-CP terminates at the E1 interface connected to the CU-UP and the F1-C interface connected to the DU.

[0280] The CU-user plane (i.e., CU-UP) includes, for example, a logical node hosting the user plane portion of the PDCP protocol for the gNB-CU of the en-gNB, and the user plane portion of the PDCP protocol and the SDAP protocol for the gNB-CU of the gNB. The gNB-CU-UP terminates at the E1 interface connected to the gNB-CU-CP and the F1-U interface connected to the gNB-DU, for example according to 3GPP TS 38.401 V16.6.0 (2021-07) Section 3.1.

[0281] There can be different functional divisions between CU and DU (called options, for example):

[0282] Option 1 (1A-similar partition): The functional partition in this option is similar to the 1A architecture in DC. RRC is in CU. PDCP, RLC, MAC, physical layer, and RF are in DU.

[0283] Option 2 (3C-like partition): The functional partition in this option is similar to the 3C architecture in DC. RRC and PDCP are in CU. RLC, MAC, physical layer, and RF are in DU.

[0284] Option 3 (Partitioning within RLC): Low RLC (partial functions of RLC), MAC, physical layer, and RF are in DU. PDCP and High RLC (other partial functions of RLC) are in CU.

[0285] Option 4 (RLC-MAC partition): MAC, physical layer, and RF are in DU, PDCP and RLC are in CU.

[0286] Otherwise, for example according to 3GPP TR 38.801 V14.0.0 (2017-03) section 11.

[0287] gNB supports different protocol layers, such as Layer 1 (L1) - physical layer.

[0288] Layer 2 (L2) of NR is divided into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where for example:

[0289] The physical layer provides a transport channel for the MAC sublayer;

[0290] The MAC sublayer provides logical channels for the RLC sublayer;

[0291] The RLC sublayer provides RLC channels for the PDCP sublayer;

[0292] The PDCP sublayer provides radio bearer for the SDAP sublayer;

[0293] The SDAP sublayer provides QoS flows for 5GC;

[0294] Comp. refers to header compression, and Segm. refers to segmentation;

[0295] Control channels include (BCCH, PCCH).

[0296] Layer 3 (L3) includes: for example, Radio Resource Control (RRC), for example according to Section 6 of 3GPP TS 38.300 V16.6.0 (2021-06).

[0297] RAN (Radio Access Network) nodes, or network nodes, or central nodes, or distributed nodes (e.g., gNB, base station, CU, or DU or parts thereof) may be implemented using, for example, a device having at least one processor and / or at least one memory (having computer-readable instructions (computer programs)), which is configured to support, and / or provide, and / or process: CU, and / or DU related functions, and / or features, and / or at least one protocol (sub) layer of RAN (Radio Access Network), such as layer 2 and / or layer 3. They may also be implemented using specific components configured to perform corresponding specific tasks, such as a layer 3 component performing a layer 3 operation, a layer 2 component performing a layer 2 operation, etc.

[0298] The CU and DU parts may be, for example, co-located or physically separated. The gNB DU may be even further divided, for example into two parts, for example: one part includes processing equipment and the other part includes antennas. The CU may also be referred to as BBU / REC / RCC / C-RAN / V-RAN, O-RAN, or parts thereof. The DU may also be referred to as RRH / RRU / RE / RU, or parts thereof.

[0299] A DU supports one or more cells, and thus one or more cells can serve as, for example, a serving cell for a user equipment (UE).

[0300] User equipment (UE) may include: a wireless or mobile device, a device with a radio interface to interact with a RAN (Radio Access Network), a smartphone, a vehicle-mounted device, an IoT device, an M2M device, etc. Such a UE or device may include: at least one processor; and at least one memory including computer program code; wherein at least one memory and computer program code are configured to, together with at least one processor, enable the device to perform at least certain operations, such as an RRC connection with the RAN. The UE is configured to, for example, generate a message (e.g., including a cell ID) that will be sent to the RAN via radio (e.g., to reach a serving cell and communicate with the serving cell). The UE can generate, send and receive RRC messages containing one or more RRC PDUs (packet data units).

[0301] The UE may have different states (e.g. according to 3GPP TS 38.331 V16.5.0 (2021-06) sections 42.1 and 4.4).

[0302] For example, when the RRC connection has been established, the UE is in the RRC_CONNECTED state, or the RRC_INACTIVE state.

[0303] In the RRC_CONNECTED state, the UE can:

[0304] Store AS context;

[0305] Transmit unicast data to / from UE;

[0306] monitoring a control channel associated with a shared data channel to determine whether data is scheduled for the data channel;

[0307] Providing channel quality and feedback information; and / or

[0308] Perform neighbor cell measurements and measurement reporting.

[0309] The RRC protocol includes the following main functions:

[0310] RRC connection control;

[0311] Measurement configuration and reporting;

[0312] Establishment / modification / release of measurement configurations (e.g. intra-frequency, inter-frequency, and inter-RAT measurements);

[0313] Measuring the establishment and release of the gap; and / or

[0314] Measurement report.

[0315] Figure 3An example of message exchange for L1 / L2 based on inter-cell mobility (also referred to as: L1 / L2 center mobility, L1 / L2 inter-cell mobility, and low layer mobility LLM) is illustrated.

[0316] In L1 / L2-based inter-cell mobility, a handover decision (e.g., regarding a cell change, such as changing UE 110 from a serving cell served by a serving DU "source DU" 2201 to a target cell) is made by a source DU based on L1 measurements (e.g., received from the UE), and a command to perform the handover is performed by L2 signaling (e.g., a MAC CE triggering the handover) from the source DU to the UE (where the UE has been pre-configured to handover to the target cell, but is configured to wait for a command / trigger from the source DU to complete the handover). In this regard, the inter-cell mobility is based on L1 measurements and triggered by L2 signaling (hence such mobility is referred to as "L1 / L2"-based inter-cell mobility).

[0317] exist Figure 3 In the handover scenario shown in the message exchange of , the handover is to the target cell of the target DU 2202. However, it should be appreciated that in other scenarios, the target cell may be the cell of the source DU itself 2201 (so that, in fact, the target DU is the source DU).

[0318] In this scenario, UE 110 has established a connection with the RAN and is initially served by source DU2201.

[0319] In box 1, UE 110 provides L3 measurements of the target DU for source DU 2201, such as measurements of one or more beams of one or more target cells of the target DU.

[0320] In block 2, the L3 measurements are forwarded to the CU-CP 230 by the target DU via uplink UL, RRC messaging.

[0321] In box 3, the CU-CP performs a handover HO decision based on L3 measurements and makes a decision on cell preparation.

[0322] In block 4, the CU-CP proceeds to establish a context in the target DU via a UE CONTEXT SETUP REQUEST message.

[0323] In block 5, the target DU responds by sending a UE context setup response message to the CU-CP.

[0324] As part of preparation for the handover, the source DU may be configured to: receive L1 measurements of a newly prepared target cell of the target DU by the UE. In this aspect, the source DU may receive a UE context modification request from the CU, wherein the UE context modification request includes: configuration information for requesting / enabling the source DU to change at least part of the low-layer configuration of the source DU, such as its layer 1 and / or layer 2 configuration / configuration of (multiple) protocols. The UE context modification request may be used to encapsulate an RRC message, which the source DU subsequently sends to the UE (the source DU may send the message toward the UE after receiving the RRC reconfiguration in the UE context modification request from the CU). The sending of the UE context modification request from the CU to the source DU, and the response of the source DU to the CU are described in detail in detail. Figure 3 Not shown (but will be discussed below) Figure 4 Boxes 5 and 6 are shown and discussed)

[0325] In block 6, the CU-CP communicates with the CU-UP 240 to perform a bearer context establishment by sending a bearer context establishment request message.

[0326] In block 7, the CU-UP replies with a Bearer Context Setup Response message.

[0327] In block 8, the CU-CP sends an RRC reconfiguration message to the source DU using downlink DL, RRC messaging.

[0328] In some examples of L1 / L2 based inter-cell mobility, the RRC reconfiguration message may actually include: two UE configuration components, a first configuration component and a second configuration component.

[0329] The first configuration component of the RRC reconfiguration message may include configuration information for enabling the UE to reconfigure its low layer configuration, such as reconfiguring its L1 configuration (such as changing the configuration of the UE's L1 measurement report). For example, the UE may be configured to change its L1 measurement report from reporting measurements of the beams of the current serving cell to reporting measurements of some beams of the current serving cell, and some beams of the target cell (therefore, this measurement of the beams of the target cell in the L1 measurement report will be used by the source DU to decide whether / when to trigger the UE to change the cell to the target cell). In L1 / L2-based inter-cell mobility, the first configuration component is applied immediately by the UE, i.e., immediately after reception of the RRC reconfiguration message.

[0330] As an example, the low layer configuration may be a reconfiguration of the UE's L1 measurements and L1 beam reporting, e.g., so that instead of associating SSB indices 0 to L-1 (where L=number of beams of a cell, e.g. 6) with beam measurements for beams 1 to L of a serving cell:

[0331] SSB indices 0 to X-1 may be associated with the X beams of the serving cell, and

[0332] SSB indices 0 to X to L-1 may be associated with Y beams of the target cell.

[0333] In some examples, there may be two or more target cells (and / or two or more target DUs for the same target cell, respectively). As an example, L1 reconfiguration may be associated with an SSB index:

[0334] a) 0 to 1, beam measurement using 2 beams for the serving cell

[0335] b) 2 to 3, beam measurement using 2 beams of the first target cell for the first target DU

[0336] c) 4 to 5, beam measurement using 2 beams of the second target cell for the second target DU.

[0337] The second configuration component of the RRC reconfiguration message may include configuration information, the application of which will be delayed until triggered by the command of the DU, for the UE to switch from the current serving source cell to the target cell. In L1 / L2-based inter-cell mobility, after reception of the RRC reconfiguration message, the second configuration component will not be applied by the UE immediately, but only when subsequently triggered by the source DU (i.e., by L2 signaling / MAC CE in box 13). When properly triggered, the UE applies the second configuration component and continues to perform the random access procedure (in boxes 15 to 17) to the target cell.

[0338] In block 9, the source DU forwards the RRC reconfiguration message to the UE.

[0339] In block 10 , the UE, having applied the first configuration component and appropriately changed its lower layer configuration, responds to the RRC reconfiguration message with an RRC reconfiguration complete message, which is forwarded to the CU-CP in block 11 .

[0340] In box 12, the UE sends a periodic L1 report to the source DU based on the configuration provided in box 9 (ie, the low-layer configuration change), for example, so that the UE's L1 beam measurement report includes: measurement of one or more beams of the target cell of the target DU.

[0341] In block 13, after the source DU decides that the UE should be handed over to another cell (i.e., the target cell of the target DU) based on the received L1 measurement report (i.e., L1 signaling), the source DU triggers L1 / L2-based inter-cell mobility by sending a MAC CE (i.e., L2 signaling) to the UE. At this point, as shown in block 14, the UE receives data from the serving DU.

[0342] In response to the MAC CE, the UE applies the RRC configuration for the target cell (ie, target DU) indicated by the MAC CE, and performs a random access RA procedure on the target DU as shown in blocks 15 and 16 .

[0343] In block 17 , after the RA procedure, the UE sends an RRC reconfiguration complete message to the target DU, and the RRC reconfiguration complete message is forwarded to the CU-CP via UL RRC messaging in block 18 .

[0344] In blocks 19 and 20, the CU-CP performs a bearer modification with the CU-UP to update the bearer setup and cause the CU-UP to start forwarding data to the target DU (and stop forwarding data to the source DU). This is accomplished by a bearer context modification request message from the CU-CP to the CU-UP in block 19, and a bearer context modification response message from the CU-UP to the CU-CP in block 20. Upon completion, the UE begins receiving data from the target DU as shown in block 21.

[0345] In block 22, the CU-CP releases the UE context from the source DU using a UE CONTEXT RELEASE REQUEST message, to which the source DU replies with a UE CONTEXT RELEASE COMPLETE message.

[0346] In some examples, L1 / L2 based inter-cell mobility (ie, its mechanisms and procedures) may provide methods to reduce: latency, overhead, and (service) interruption time in inter-cell mobility.

[0347] In some examples, L1 / 2 based inter-cell mobility may provide:

[0348] Configuration and maintenance for multiple candidate target cells to allow rapid application of configuration for the candidate target cells;

[0349] Dynamic switching mechanism between candidate serving cells (including special cells SpCell and secondary cells SCell) for potential applicable scenarios based on L1 / L2 signaling;

[0350] L1 enhancements for inter-cell beam management, including: L1 measurement and reporting, and beam indication;

[0351] Timed advance management; and

[0352] CU-DU interface signaling to support L1 / L2-based inter-cell mobility.

[0353] The L1 / L2-based inter-cell mobility process may be applicable to the following scenarios:

[0354] Standalone, CA, and NR-DC cases with serving cell change within one carrier group CG

[0355] Intra-DU situation, intra-CU situation, and inter-DU situation (applicable to both standalone and CA situations)

[0356] Both intra-frequency and inter-frequency

[0357] Both FR1 and FR2

[0358] The source cell and the target cell can be synchronized or not

[0359] Figure 4 FIG. 1 illustrates another example of message exchange for L1 / L2 based inter-cell mobility (with Figure 3 Roughly similar), where the serving / source DU makes handover decisions regarding cell change based on L1 signaling (i.e., L1 measurement reports), and the source DU triggers the cell change through L2 signaling (i.e., MAC CE).

[0360] In blocks 1 to 4, CU 210 decides the preparation of the target cell controlled by target DU 2202 for low layer mobility based on the measurement report from the UE (forwarded to the CU by source DU 2201). Blocks 1, 2, 3, and 4 generally correspond to Figure 3 In: box 1, box 2, box 4, and box 5.

[0361] As part of the preparation work, the source DU is configured in blocks 5 to 6 to: receive the L1 measurement of the newly prepared target cell of the UE for the target DU (equivalent blocks in Figure 3 In this aspect, the source DU receives a UE context modification request from the CU, wherein the UE context modification request includes: configuration information for requesting / enabling the source DU to change at least part of the low-level configuration of the source DU.

[0362] Box 7 corresponds roughly to Figure 3 Box 8 in.

[0363] In block 8, the UE sends an L1 measurement report, wherein the configuration of the L1 measurement report is according to the low layer configuration previously received by the UE in the last RRC reconfiguration that it has received from the network / CU (ie before the reception of the new RRC reconfiguration in block 9).

[0364] In block 9, the UE receives a new RRC reconfiguration from the network / CU, the new RRC reconfiguration indicating the preparation of a new target cell for the target DU for L1 / L2 based inter-cell mobility. The RRC reconfiguration also requests the UE to change at least part of the UE's low-layer configuration, such as configuring the UE to report at least some L1 measurements for the newly configured target cell.

[0365] In block 10 , the UE sends an RRC reconfiguration complete message to the DU, and the DU forwards the RRC reconfiguration complete message to the CU in block 11 .

[0366] In block 12, the CU sends an RRC reconfiguration complete indication to the DU.

[0367] At the same time, in block 13 , the UE starts sending L1 measurement reports using the new RRC reconfiguration received from the network / CU in block 9 .

[0368] The problem with conventional L1 / L2-based inter-cell mobility is that the source DU cannot clearly know when the UE applies the new RRC reconfiguration of block 9, i.e., the source DU does not know when the UE changes its low-layer configuration according to the RRC reconfiguration message of block 9 (it should be noted that RRC message delivery is actually "transparent" to the source DU, i.e., the source DU does not know the content of the RRC message, so the source DU does not know that the UE has applied the reconfiguration via the UE's RRC reconfiguration completion message of block 10). Therefore, the source DU cannot determine whether the L1 measurement report received in block 13 follows the new RRC reconfiguration of block 9 or the previous RRC reconfiguration. Therefore, the source DU may misunderstand Figure 4 The L1 measurement report of the UE of block 13 of the present invention may misunderstand the radio measurements and the SSB resource indicator included in the L1 measurement report of block 13. Since the source DU makes a handover decision based on the L1 measurement report, any misunderstanding of the L1 measurement report may cause the source DU to make an erroneous or suboptimal handover decision.

[0369] Although a "synchronous" reconfiguration can be performed in blocks 9 to 10, this requires the use of random access toward the serving DU and resetting the PCDP layer and the RLC layer. Performing random access and resetting the protocol layers after each RRC reconfiguration may result in delays and interruption times, thereby defeating the goal of L1 / L2-based inter-cell mobility.

[0370] Various examples of the present disclosure attempt to address such issues in L1 / L2 based inter-cell mobility.

[0371] Certain examples of the present disclosure provide methods for ensuring that the L1 / L2 configuration applied in a UE (e.g., Figure 49), and the L1 / L2 configuration in the DU (e.g. Figure 4 Synchronization of the UE context modification request message in box 5).

[0372] In various examples of the present disclosure, when a CU requests a modification of a UE context involving a change in a low-level configuration, in this regard, the UE context modification request sent by the CU is identified by an identifier ID, and the ID is included in the UE context modification request. In this regard, the CU generates an ID identifying the request and transmits the ID to the source DU and the UE.

[0373] The DU may send a UE Context Modification Response including the ID to the CU. The CU may send an RRC Reconfiguration message to the UE (via the DU). The RRC Reconfiguration includes: an ID generated by the CU (and the ID is also transmitted to the source DU).

[0374] The RRC reconfiguration may also include an indicator requesting the UE to confirm to the DU that the UE has performed the requested low layer configuration change. In this regard, such an indicator may be a flag indicating "L1-sync required" and the ID to be sent by the UE (e.g., via L1 signaling). The ID included in the RRC reconfiguration may be implicitly considered as a trigger for L1-s y In other words, the presence of the ID itself in the RRC reconfiguration can serve as an indicator.

[0375] In an example of the present disclosure, in response to the UE applying a new RRC reconfiguration and completing the reconfiguration of its lower layer protocols, the UE sends L2 or L1 signaling (e.g., MAC CE or L1 signal, such as L1 measurement report) including the received ID to notify the DU: the UE has applied the new lower layer configuration.

[0376] In some examples, the ID may be a flag or a single-bit identifier signaled through an existing L1 uplink control channel indication (i.e., the ID is not a multi-bit / long identifier). This method may be used if the CU only operates for L1 / L2-based inter-cell mobility, prepares a single target DU configuration, and ensures that no other reconfiguration is applied after the L1 / L2-based inter-cell mobility configuration.

[0377] In some examples, after applying the new RRC reconfiguration, the ID may be included by the UE in an L1 measurement report (e.g., a channel state information CSI report). The L1 indication may be always included (e.g., in each L1 measurement report), or only included once, after the UE has applied the new RRC reconfiguration.

[0378] Compared with baseline / traditional L1 / L2 based inter-cell mobility operations (in Figure 3 ), after successfully applying the low-layer configuration using the new RRC configuration, in the example of the present disclosure, the UE may also send an RRC reconfiguration completion message to the source DU, and the source DU forwards the RRC reconfiguration completion message to the CU.

[0379] Figure 5 A signaling diagram is illustrated showing the exchange of signals / messages for L1 / L2 based inter-cell mobility (between: UE 110, source gNB-DU “DU” 220, and gNB-CU “CU” 210) according to an example of the present disclosure.

[0380] and Figure 5 One or more features discussed in relation may be found in one or more of the other figures. Figure 5 During the discussion of the present invention, reference will be made to other figures for the purpose of explanation.

[0381] exist Figure 5 In the example, the UE is configured to: access the RAN, where the RAN includes at least: a CU (which may also be referred to as a "central node" in this article), and a DU serving the UE (which may also be referred to as a "distributed node" in this article), where the central node controls the distributed nodes.

[0382] The UE includes: a component configured to (eg, at least one processor; and at least one memory storing instructions, which when executed by the at least one processor, causes the UE to at least perform the following items:) establish a connection toward a radio access network, as shown in block 501.

[0383] The UE is further configured to: receive a UE context modification request from the central node, as shown in block 502. The UE context modification request includes:

[0384] Requests to change at least part of the low-level configuration, and

[0385] An identifier related to the request (eg, an identifier identifying the request, where the identifier may be generated by the CU and previously assigned / associated with the request).

[0386] Frame 502 and Figure 3 Frames 8 and 9, and Figure 4 Blocks 7 and 10 are somewhat similar, although the UE context modification request of block 502 also includes: an identifier.

[0387] The UE is also configured to perform the requested low-layer configuration change, as shown in block 503 .

[0388] Based at least in part on the execution of the requested low layer configuration change (e.g., in response to applying / completing the requested low layer configuration change), the UE is configured to:

[0389] Sending confirmation that the requested changes have been performed towards the central node, as shown in block 504 (thereby notifying the CU that the requested low-level configuration has been performed / completed - block 504 and Figure 3 Frames 10 and 11 of Figure 4 10 and 11 are somewhat similar); and

[0390] Sending an identifier toward a distributed node, as shown in block 505 (e.g., Figure 6 As discussed, the DU can use this to determine that the requested low-level configuration has been executed / completed).

[0391] In some examples, the UE context modification request is received from the central node in at least one selected from the group consisting of:

[0392] Layer 3 protocol messages;

[0393] Radio Resource Configuration RRC message; and

[0394] RRC reconfiguration message.

[0395] In some examples, the identifier is sent to the distributed node, at least one selected from the following group:

[0396] via layer 2 signaling;

[0397] in layer 2 protocol messages; and

[0398] In the media access control MAC control element CE.

[0399] In some examples, the identifier is sent to the distributed node, at least one selected from the following group:

[0400] via layer 1 signaling;

[0401] In uplink control information UCI;

[0402] In a channel state information (CSI) report; and

[0403] In layer 1 measurement reports.

[0404] In some examples, the identifier is sent to the distributed nodes in the following manner:

[0405] One or more layer 1 measurement reports at least one selected from the following group:

[0406] via layer 1 signaling;

[0407] In uplink control information UCI (e.g. via uplink control channel

[0408] (such as physical uplink control channel PUCCH) transmission);

[0409] In a channel state information (CSI) report; and

[0410] In a layer 1 measurement report (such as a layer 1 beam measurement report).

[0411] In some examples, the UE context modification request includes: an indicator for requesting the UE to confirm to the distributed node that the UE has performed the requested change; and the UE is also configured to: send an identifier toward the distributed node based at least in part on the received indicator, for confirming to the distributed node that the UE has performed the requested change.

[0412] In some examples, the indicator is: a flag, or an identifier (ie, the identifier itself serves as an indicator).

[0413] In some examples, the identifier is:

[0414] An identifier for identifying the request (e.g., an identifier generated by the CU and associated with / assigned to the request);

[0415] a multi-bit identifier; or

[0416] Logo.

[0417] In some examples, the UE context modification request is a request for a handover procedure to switch the UE from the current serving cell to another cell (controlled by the DU or not controlled by the DU). In some examples, the UE context modification request is a request for switching the UE between cells in an L1 / L2 based inter-cell mobility procedure.

[0418] In some examples, the requested change in the low layer configuration includes: a request for the UE, at least one selected from the following group:

[0419] Reconfigure the UE's low-layer protocols;

[0420] Adjusting layer 1 L1 measurements performed by the UE;

[0421] Reconfigure UE's L1 measurement report;

[0422] measuring one or more beams of a target cell; and

[0423] Report one or more measurements of one or more beams of the target cell.

[0424] Figure 6A signaling diagram illustrating the exchange of signals / messages for L1 / L2 based inter-cell mobility (between: UE 110, source gNB-DU “DU” 220, and gNB-CU “CU” 210) is illustrated according to another example of the present disclosure.

[0425] and Figure 6 One or more features discussed in relation may be found in one or more of the other figures. Figure 6 During the discussion of the present invention, reference will be made to other figures for the purpose of explanation.

[0426] In block 601, the CU generates an identifier ID, which is associated with a request to change at least part of a low-level configuration. For example, the ID is configured to: identify the request, and the CU assigns / associates the ID to the request.

[0427] In block 602, the CU sends a first UE context modification request toward a distributed node. The first UE context modification request includes:

[0428] a request to change at least part of the lower layers (i.e. to change the lower layer configuration of the DU), and

[0429] Identifier.

[0430] Box 602 is somewhat similar to Figure 4 In response to receiving the UE context modification, the DU may send a response to the CU (similar to Figure 4 6 of the present invention, although the response may also include: an identifier [i.e., Figure 7 2]), and the DU may apply the requested changes to its lower layer configuration.

[0431] In some examples, the first UE context modification request includes a request for at least one or more of the following:

[0432] Reconfigure the UE's low-layer protocols.

[0433] Adjust the interpretation of layer 1 L1 measurement reports received from UE;

[0434] receiving L1 measurements for the target cell from the UE;

[0435] associating one or more measurements with one or more beams of the target cell, the one or more measurements being from a measurement report received from the UE; and

[0436] Handover the UE to at least one item selected from the following group:

[0437] The target cell controlled by the DU;

[0438] a target cell controlled by another DU; and

[0439] One or more candidate target cells (one or more candidate target cells may be

[0440] can be controlled by DU).

[0441] In some examples, the first UE context modification request includes: a plurality of requested changes to one or more lower layer configurations, and

[0442] The identifier is configured to: identify multiple requested changes, or

[0443] The identifier includes a plurality of identifiers configured to respectively identify a plurality of requested changes.

[0444] In some examples, the distributed nodes are configured to:

[0445] Based at least in part on the identifier received from the central node, adjusting an interpretation of a layer 1 L1 measurement report received from the UE; and / or

[0446] One or more measurements are associated with one or more beams of the target cell based at least in part on the identifier received from the central node, the one or more measurements being from a measurement report received from the UE.

[0447] In response to completion of the requested low-layer configuration change, the DU may send a confirmation toward the CU that the requested change has been performed (not shown). The response to the first UE context modification request may include: an identifier for identifying the request or a replacement identifier (e.g., if the DU has used an identifier generated by the CU and received from the CU that was originally proposed. Such a replacement identifier may be used in place of the identifier generated by the CU in subsequent boxes).

[0448] In block 502, the CU sends a second UE context modification request toward the UE, the request including:

[0449] a request to change at least part of the low-layer configuration (i.e. to change the low-layer configuration of the UE), and

[0450] Identifier.

[0451] Frames 503 to 505 and Figure 4 Frames 503 to 505 are the same.

[0452] In block 603, the DU determines whether the UE has performed the requested change based at least in part on the identifier received from the UE in block 505. In this regard, since the UE sends the identifier only in response to completing the requested change, the DU can determine that the requested low layer configuration has been completed based on matching the identifier received from the UE in block 505 with the identifier received from the CU in block 602.

[0453] In block 604 , the UE sends an L1 measurement report according to the lower layer reconfiguration received in block 502 .

[0454] After the determination of block 605, the DU can determine that the L1 measurement report is consistent with the low layer reconfiguration received in block 502. In this regard, the low layer reconfiguration received in block 502 may be a request for the UE to: one or more of:

[0455] Adjusting layer 1 L1 measurements performed by the UE;

[0456] Reconfigure UE's L1 measurement report;

[0457] measuring one or more beams of a target cell (or one or more candidate target cells); and

[0458] Report one or more measurements of one or more beams of a target cell (or one or more candidate target cells).

[0459] Accordingly, the DU is able to determine whether the L1 measurement received from the UE is associated with at least one item selected from the following group:

[0460] Target community;

[0461] one or more candidate target cells;

[0462] one or more beams of a target cell; and

[0463] One or more beams of one or more candidate target cells.

[0464] The DU may be configured to determine to trigger the UE to perform a handover of the UE to a target cell based at least in part on at least one item selected from the following group:

[0465] an identifier received from the UE; and

[0466] After receiving the identifier from the UE, an L1 measurement report is received from the UE.

[0467] In block 605 , the DU determines whether to change / handover the UE's serving cell to a target cell. The determination is based at least in part on the identifier received in block 505 and the subsequently received L1 measurement report of block 604 .

[0468] Since the DU is able to determine that the UE has performed the requested change based at least in part on the identifier received from the UE in block 505, the DU can determine that the L1 measurement report received in block 604 is consistent with the lower layer reconfiguration of the most recent UE context modification request (i.e., compared to the L1 measurement report consistent with the earlier / previous lower layer configuration received prior to the UE context modification request in block 502). Advantageously, the DU thereby knows that both itself (after block 602) and the UE (after block 502) have applied the corresponding lower layer reconfiguration, and thus the DU's lower layer reconfiguration is "synchronized" with the UE's lower layer reconfiguration. Advantageously, this can avoid / reduce the risk of the DU misinterpreting the L1 measurement report of block 604. In addition, since the DU makes a handover decision to determine a cell change / handover based on the L1 measurement report, this can avoid / reduce the DU making an erroneous or suboptimal handover decision.

[0469] In block 606 , after the determination of block 605 that the DU changes the serving cell of the UE to the target cell, the DU triggers the UE to perform a handover of the UE to the target cell.

[0470] Figure 7 The message flow for L1 / L2-based inter-cell mobility according to an example of the present disclosure (in: UE110, source g NB-DU "DU" 220, and g between NB-CU “CU” 210).

[0471] In block 1, the CU requests modification of the UE context involving lower layers (e.g., a layer 1 reconfiguration request) by sending a UE context modification request to the DU. The request is identified by an ID. The DU stores the previous layer 1 configuration of the UE until the UE indicates that it has switched to a new L1 configuration (i.e., in block 5 as discussed below).

[0472] In block 2, in response to receiving a UE context modification request from the CU, the DU sends a UE context modification response to the CU. The ID may be included in the message. In addition, if the DU determines that the ID received from the CU has been used by the DU, the DU may generate its own replacement ID for identifying the request and send the replacement ID to the CU, for example, in the UE context modification response of block 2.

[0473] In block 3, the CU generates an RRC reconfiguration message including the ID and sends the RRC reconfiguration message to the UE via the DU via DL RRC messaging.

[0474] In block 4, the RRC reconfiguration message is forwarded by the DU to the UE.

[0475] In block 5, after the UE has applied the requested reconfiguration, the UE sends a MAC CE indication to indicate that it has applied the changes requested in the message of block 4. The ID is included in the MAC CE.

[0476] Using the ID reported by the UE in block 5, the DU matches the ID with the ID received by the DU from the CU in the context modification request in block 1, thereby determining that the UE has applied the requested lower layer reconfiguration and has switched its L1 configuration.

[0477] As an alternative to sending the ID via layer 2 signaling (such as MAC CE) in box 5, in other examples, the ID may be sent by the UE in uplink control information UCI containing a channel state information CSI report (e.g., the ID may be included in the L1 beam measurement report - not shown), thereby saving resources by reducing / saving MAC CE signaling.

[0478] In block 6, the RRC reconfiguration has been applied and the UE replies to the CU by sending an RRC Reconfiguration Complete message to the CU via the DU.

[0479] In block 7, the DU forwards the RRC Reconfiguration Complete message to the CU via UL RRC messaging.

[0480] In some examples, the ID / L1 indication may be signaled as a single bit over an existing L1 uplink control channel (rather than the ID / L1 indication being a multi-bit / long identifier). This may be done if the CU prepares only a single target configuration for L1 / L2 based inter-cell mobility operations, and it ensures / requires that no other reconfiguration is applied after the configuration for L1 / L2 based inter-cell mobility operations.

[0481] If the UE is not requested to send L2 or L2 indication (i.e., not requested to send via the messages in boxes 3 and 4: L2 / MAC CE indication in box 5, or L1 indication), the ID can be omitted in the RRC reconfiguration message in boxes 3 and 4, so in box 5, the L2 or L1 indication will not be sent.

[0482] Advantageously, Figure 7 The process can avoid / reduce the DU from misinterpreting the L1 measurement report subsequently received from the UE. Accordingly, the DU can correctly decide the correct / optimal low-layer mobility decision to trigger the UE to switch cells (such as Figure 6 604 to 606). Figure 7 The process can ensure that the UE and DU remain synchronized regarding the new lower layer reconfiguration (ie, the reconfiguration for L1 / L2-based inter-cell mobility).

[0483] Figures 3 to 7 The signal diagrams of can be viewed as illustrating multiple methods, that is, they can be viewed as illustrating one or more actions performed by multiple participants / at multiple entities (e.g., UE 110, DU 220, and CU 210). Therefore, these diagrams can be viewed as illustrating multiple separate methods performed by each corresponding separate participant / entity. These diagrams can also be viewed as illustrating the transmission / communication / transmission / reception (direct or indirect) of various signals / messages / information between participants / entities. In addition, for any (multiple) features / (multiple) actions of sending / causing transmission shown in these diagrams, they can also be viewed as illustrating the corresponding (multiple) features / (multiple) actions of receiving / causing reception.

[0484] The various component blocks shown in the figure may be functional, and the functions described in each block may be performed by a single physical entity (such as: UE, DU, and CU, and reference Figure 8 The functions described may also be implemented by a computer program (e.g., see Fig. 9 Accordingly, in Figures 3 to 7 The blocks shown in the signal diagrams may represent actions in a method, functions performed by an apparatus, and / or instruction / code portions in a computer program.

[0485] Figures 3 to 7 The signal diagrams each represent a possible scenario. The order of the blocks shown is not absolutely necessary, so in principle some blocks can be executed out of order (e.g. especially Figure 5 and Figure 6 504 and 505 in the example).

[0486] It should be understood that Figures 3 to 7 Each box and combination of boxes shown in, and the above-mentioned additional functions can be implemented by various components, such as hardware, firmware, and / or software including one or more computer program instructions. For example, the above-mentioned one or more functions can be performed by a suitably configured device (such as: a UE, DU, or CU including components for performing the above-mentioned functions). The above-mentioned one or more functions can be embodied by a suitably configured computer program (such as a computer program including computer program instructions, which, when executed by the device, causes the device to perform the above-mentioned functions). The computer program instructions can be stored in a memory storage device and executed by a processor.

[0487] It is understood that any such computer program instructions may be loaded onto a computer or other programmable device (i.e., hardware) to cause the machine (when the instructions are executed on the programmable device) to create components for implementing the functions specified in the box. These computer program instructions may also be stored in a computer-readable medium, and the computer program instructions may instruct the programmable device to operate in a particular manner so that the instructions stored in the computer-readable memory produce an article of manufacture including instruction components that implement the functions specified in the box. The computer program instructions may also be loaded onto a programmable device so that a series of operations are performed on the programmable device to produce a computer-implemented process so that the instructions executed on the programmable device provide actions for implementing the functions specified in the box.

[0488] Various examples of the present disclosure, but not necessarily all examples, may be in the form of methods, devices, or computer programs. Accordingly, various examples, but not necessarily all examples, may be implemented in hardware, software, or a combination of hardware and software.

[0489] Various examples of the present disclosure, but not necessarily all examples are described using flow charts and schematic block diagrams.It should be understood that each frame (flow chart and block diagram), and the combination of frames can be realized by the computer program instructions of a computer program.These program instructions can be provided to one or more (multiple) processors, processing circuit systems, or (multiple) controllers, so that the instructions executed thereon create the parts for realizing the function specified in the frame, that is, so that the method can be computer-implemented.Computer program instructions can be performed by (multiple) processors, so that the frame / step / action of a series of operations will be performed by (multiple) processors, to produce a computer-implemented process, so that the instructions executed on (multiple) processors provide the steps for realizing the function specified in the frame.

[0490] Accordingly, the box supports: a combination of components for performing specified functions; a combination of actions for performing specified functions; and a computer program instruction / algorithm for performing specified functions. It should also be understood that each box and combination of boxes can be implemented by a dedicated hardware system that performs the specified function or action, or a combination of dedicated hardware and computer program instructions.

[0491] Various examples, but not necessarily all examples, of the present disclosure provide both a method and a corresponding apparatus, the apparatus comprising: various modules, components, or circuit systems that provide functionality for performing / applying the actions of the method. The modules, components, or circuit systems may be implemented as hardware, or may be implemented as software or firmware executed by a computer processor. In the case of firmware or software, the examples of the present disclosure may be provided as a computer program product, the computer program product comprising: a computer-readable storage structure on which computer program instructions (i.e., software or firmware) are embodied, the computer program instructions being for execution by a computer processor.

[0492] Figure 8 Schematically illustrates a method for carrying out the process described in the present disclosure, and particularly Figures 5 to 7 1 is a block diagram of an apparatus 10 that illustrates the methods, processes, procedures, and signaling shown in FIG. In this regard, the apparatus may perform the roles of: UE 110, DU 220, or CU 210 in the methods shown and described above. Figure 2 The component blocks are functional and the described functions can be performed by a single physical entity.

[0493] The apparatus includes: a controller 11 , which may be provided in a device such as UE 110 , DU 220 , or CU 210 .

[0494] The controller 11 may be embodied by a computing device, in particular such as the above-described devices. In some examples, but not necessarily all, the device may be embodied as a chip, a chip set, a circuit system, or a module, i.e., for any of the above-described uses. As used herein, a "module" refers to a unit or device that does not include certain parts / components added by the final manufacturer or user.

[0495] The controller 11 may be implemented as controller circuitry. The controller 11 may be implemented solely in hardware, with certain aspects in software (including firmware), or may be a combination of hardware and software (including firmware).

[0496] The controller 11 can be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 14 in a general-purpose or special-purpose processor 12, which can be stored on a computer-readable storage medium 13 (such as a memory, or a disk, etc.) and executed by such a processor 12.

[0497] The processor 12 is configured to read from and write to the memory 13. The processor 12 may also include an output interface via which data and / or commands are output by the processor 12, and an input interface via which data and / or commands are input to the processor 12. The apparatus may be coupled to or include one or more other components 15 (e.g., in particular a radio transceiver, a sensor, an input / output user interface element, and / or other modules / devices / components for inputting and outputting data / commands).

[0498] The memory 13 stores a computer program 14, which includes computer program instructions (computer program code) that control the operation of the device 10 when loaded into the processor 12. The computer program instructions of the computer program 14 provide logic and routines that enable the device to perform the operations described in this disclosure and in the Figures 5 to 7 By reading the memory 13 , the processor 12 can load and execute the computer program 14 .

[0499] The computer program instructions may be included in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some examples, but not necessarily all examples, the computer program instructions may be distributed over more than one computer program.

[0500] Although memory 13 is shown as a single component / circuitry, it may be implemented as one or more separate components / circuitry, some or all of which may be integrated / removable, and / or may provide permanent / semi-permanent / dynamic / cache storage.

[0501] Although processor 12 is shown as a single component / circuitry, it may be implemented as one or more separate components / circuitry, some or all of which may be integrated / removable.Processor 12 may be a single-core or multi-core processor.

[0502] The apparatus may include: one or more components for implementing the methods, processes, and programs described in the present disclosure and shown in the figures. It is conceivable that the functions of these components may be combined in one or more components, or performed by other components of equivalent functionality. The description of a function should be additionally regarded as: any component suitable for performing the function is also disclosed. If a structural feature has been described (whether the function or functions are explicitly or implicitly described), it may be replaced by a component for performing one or more of the functions of the structural feature.

[0503] Although examples of devices have been described above in terms of including various components, it should be understood that the components may be embodied as, or controlled by, corresponding controllers or circuit systems (such as one or more processing elements or processors of the device). In this regard, each of the components described above may be one or more of any device, component, or circuit system embodied as hardware, software, or a combination of hardware and software that is configured to perform the corresponding functions of the corresponding components as described above.

[0504] For example, the apparatus may be: UE 110, DU 220, or CU 210. In some examples, the apparatus may be embodied as a chip, a chip set, a circuit system, or a module, ie, for any of the uses described above.

[0505] In one example, the apparatus is a UE and may be embodied on a handheld portable electronic device, such as a mobile phone, a mobile communication device, a wearable computing device, or a personal digital assistant, which may additionally provide one or more audio / text / video communication functions (e.g., telecommunication, video communication, and / or text transmission (Short Message Service (SMS) / Multimedia Message Service (MMS) / email) functions), interactive / non-interactive viewing functions (e.g., web browsing, navigation, TV / program viewing functions), music recording / playback functions (e.g., Moving Picture Experts Group-1 Audio Layer 3 (MP3), or other formats and / or (frequency modulation / amplitude modulation) radio broadcast recording / playback), data downloading / sending functions, image capture functions (e.g., using a (e.g., built-in) digital camera), and gaming functions, or any combination thereof.

[0506] UE can be provided in an electronic device, for example, a mobile terminal. However, it should be understood that the mobile terminal is only an example of an electronic device that will benefit from the implementation examples of the present disclosure, and therefore should not be considered to limit the scope of the present disclosure to this. Although in some implementation examples, the device can be provided in a mobile terminal, other types of electronic devices can easily adopt the examples of the present disclosure. In addition, whether the device is intended to provide mobility, the device can easily adopt the examples of the present disclosure.

[0507] In an example of an apparatus provided within UE 110, the apparatus includes:

[0508] at least one processor 12; and

[0509] At least one memory 13, comprising computer program code.

[0510] At least one memory 13 stores instructions, which when executed by at least one processor 12, cause the apparatus to at least:

[0511] establishing a connection towards a radio access network;

[0512] A UE context modification request is received from a central node, where the UE context modification request includes:

[0514] Requests to change at least part of the low-level configuration, and

[0515] an identifier associated with the request;

[0516] Perform the requested low-level configuration changes;

[0517] sending a confirmation towards the central node that the requested change has been performed; and

[0518] An identifier is sent towards the distributed nodes.

[0519] In an example of a device provided within the distributed node 220, the device includes:

[0520] at least one processor 12; and

[0521] At least one memory 13, comprising computer program code.

[0522] At least one memory 13 stores instructions, which when executed by at least one processor 12, cause the apparatus to at least:

[0523] A first user equipment UE context modification request is received, the first user equipment UE context modification request is sent from the central node to the distributed node, the first UE context modification request includes:

[0526] Requests to change at least part of the low-level configuration, and

[0527] an identifier associated with the request;

[0528] A second UE context modification request is received, where the second UE context modification request is sent from the central node to the UE via the distributed node, where the second UE context modification request includes:

[0531] Requests to change at least part of the low-level configuration, and

[0532] Identifier;

[0533] sending a second UE context modification request towards the UE; and

[0534] An identifier is received from a UE.

[0535] In an example of the means provided within the central node 220, the means include:

[0536] at least one processor 12; and

[0537] At least one memory 13, comprising computer program code.

[0538] At least one memory 13 stores instructions, which when executed by at least one processor 12, cause the apparatus to at least:

[0539] generating an identifier associated with a request to change at least a portion of a low-level configuration;

[0541] Sending a first user equipment UE context modification request towards the distributed node, where the first user equipment UE context modification request includes:

[0543] Change at least some of the low-level requests, and

[0544] Identifiers; and

[0545] Sending a second UE context modification request towards the UE, the second UE context modification request comprising:

[0547] Requests to change at least part of the low-level configuration, and

[0548] Identifier.

[0549] According to some examples of the present disclosure, a system including at least one UE 110, at least one DU 220, and / or at least one CU 210 is provided.

[0550] The examples described above can be used as enabling components of the following items: telecommunication systems; tracking systems; automotive systems; electronic systems, including consumer electronics; distributed computing systems; media systems for generating or presenting media content, including: audio, visual and audio-visual content and their hybrid, middleware, virtual and / or augmented reality; personal systems, including personal health systems or personal fitness systems; navigation systems; user interfaces, also known as human-machine interfaces; networks, including cellular, non-cellular, and fiber optic networks; ad hoc networks; the Internet; the Internet of Things (IOT); Vehicle-to-Everything (V2X); virtualized networks; and related software and services.

[0551] Fig. 9 The computer program 14 is illustrated as being transferable via a transfer mechanism 20. The transfer mechanism 20 may be any suitable transfer mechanism, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a solid-state memory, a recording medium such as a compact disk read-only memory (CD-ROM) or a digital versatile disk (DVD), or an article of manufacture including or tangibly embodying the computer program 14. The transfer mechanism may be a signal configured to reliably transfer the computer program. An apparatus may receive, propagate, or send a computer program as a computer data signal.

[0552] In some examples of the present disclosure, a computer program including instructions is provided, which, when executed by an apparatus (such as UE 110), causes the apparatus to perform at least the following items, or is used to cause at least the following items to be performed:

[0553] establishing a connection towards a radio access network;

[0554] A UE context modification request is received from a central node, where the UE context modification request includes:

[0555] Requests to change at least part of the low-level configuration, and

[0556] an identifier associated with the request;

[0557] Perform the requested low-level configuration changes;

[0558] sending a confirmation towards the central node that the requested change has been performed; and

[0559] An identifier is sent towards the distributed nodes.

[0560] In some examples of the present disclosure, a computer program is provided that includes instructions that, when executed by a device (such as DU 220), cause the device to perform at least the following items, or are used to cause at least the following items to be performed:

[0561] A first user equipment UE context modification request is received, the first user equipment UE context modification request is sent from the central node to the distributed node, the first UE context modification request includes:

[0562] Requests to change at least part of the low-level configuration, and

[0563] an identifier associated with the request;

[0564] A second UE context modification request is received, where the second UE context modification request is sent from the central node to the UE via the distributed node, where the second UE context modification request includes:

[0565] Requests to change at least part of the low-level configuration, and

[0566] Identifier;

[0567] sending a second UE context modification request towards the UE; and

[0568] An identifier is received from a UE.

[0569] In some examples of the present disclosure, a computer program is provided that includes instructions that, when executed by a device (such as CU 210), cause the device to perform at least the following items, or are used to cause at least the following items to be performed:

[0570] generating an identifier associated with a request to change at least a portion of a low-level configuration;

[0571] Sending a first user equipment UE context modification request towards the distributed node, where the first user equipment UE context modification request includes:

[0572] Change at least some of the low-level requests, and

[0573] Identifiers; and

[0574] Sending a second UE context modification request towards the UE, the second UE context modification request comprising:

[0575] Requests to change at least part of the low-level configuration, and

[0576] Identifier.

[0577] References to "computer program", "computer-readable storage medium", "computer program product", "tangibly embodied computer program", etc., or "controller", "computer", "processor", etc. should be understood to include not only computers with different architectures (such as single / multi-processor architectures, and sequential (von Neumann) / parallel architectures), but also special-purpose circuits (such as field programmable gate arrays (FPGAs), application-specific circuits (ASICs)), signal processing devices, and other devices. References to computer programs, instructions, codes, etc. should be understood to include software for programmable processors, or firmware (e.g., the programmable content of a hardware device, whether instructions for a processor, or configurations set for a fixed-function device, gate array, or programmable logic device, etc.).

[0578] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0579] (a) a hardware circuitry-only implementation (such as an implementation using only analog and / or digital circuitry), and

[0580] (b) a combination of hardware circuitry and software such as (where applicable):

[0581] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0582] (ii) any portion of a hardware processor(s) with software (including digital signal processor(s), software, and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions), and

[0583] (c) Hardware circuits and / or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but in which the software may not be present when not required for operation.

[0584] This definition of circuitry applies to all uses of the 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 a hardware-only circuit or processor and its accompanying software and / or firmware. For example, if applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0585] Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0586] Features described in the preceding description may be used in combinations other than the combinations explicitly described.

[0587] Although functions have been described with reference to certain features, those functions may be performable by other features whether described or not.

[0588] Although features have been described with reference to certain examples, these features may also be present in other examples, whether or not described. Accordingly, features related to one example / aspect of the disclosure may include: any or all features related to another example / aspect of the disclosure, and vice versa, as long as they are not contradictory.

[0589] Although various examples of the present disclosure have been described in the preceding paragraphs, it should be understood that modifications may be made to the examples given without departing from the scope of the present invention as described in the claims. For example, although the examples of the present disclosure have been discussed with respect to UE handover / cell handover (i.e., such as L1 / L2-based inter-cell mobility), it should be understood that the examples of the present disclosure are not limited to such applications / processes, and L1 / L2-based inter-cell mobility, but may be applied to other applications / processes involving low-layer reconfiguration (such as layer 1 or layer 2 configuration changes).

[0590] The term "comprising" is used herein in an inclusive, rather than exclusive, sense. That is, any reference to X including Y means that X: may include only one Y, or may include more than one Y. If "comprising" is intended to be used in an exclusive sense, it will be made clear in the context by referring to "including only one" or by using "consisting of".

[0591] In this specification, the terms "connected", "coupled", and "in communication", and their derivatives refer to being operationally connected / coupled / in communication. It should be understood that any number or combination of intermediate components (including no intermediate components) may be present, i.e., to provide direct or indirect connection / coupling / in communication. Any such intermediate components may include hardware and / or software components.

[0592] As used herein, the term "determine / decide" (and its grammatical variations) may include, among others: computing, calculating, processing, deriving, measuring, investigating, identifying, looking up (e.g., looking up in a table, a database, or another data structure), determining, etc. Furthermore, "determining" may include: receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), obtaining, etc. Furthermore, "determining / deciding" may include: resolving, selecting, choosing, establishing, etc.

[0593] In this specification, various examples have been cited. The description of features or functions related to an example indicates that these features or functions are present in the example. The terms "example" or "for example", "may" or "might" as used herein mean that: whether explicitly stated or not, these features or functions are present in at least the example, whether described as an example or not, and they may but not necessarily be present in some or all other examples. Therefore, "example", "for example", "may", or "might" refers to a specific instance in an example class. The attributes of an instance may be attributes of only the instance, or attributes of the class, or attributes of a subclass of the class, which subclass includes some instances in the class, but not all instances.

[0594] In this specification, unless otherwise expressly stated, references to "a / an / the" [feature, element, component, part, etc.] have an inclusive rather than exclusive meaning and should be interpreted as: "at least one" [feature, element, component, part, etc.]. That is, any reference to X that includes one / the Y indicates that X may include only one Y, or may include more than one Y, unless the context clearly indicates otherwise. If "a" or "the" is intended to be used with an exclusive meaning, it will be clearly stated in the context. In some cases, "at least one" or "one or more" may be used to emphasize the inclusive meaning, but the absence of these terms should not be regarded as inferring any exclusive meaning.

[0595] In the claims, the presence of a feature (or a combination of features) refers to: the feature (or combination of features) itself, and features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way. Equivalent features include, for example, features that perform substantially the same function in substantially the same way to achieve substantially the same result.

[0596] In this specification, reference has been made to various examples where adjectives or adjective phrases are used to describe example features. Such description of features in relation to examples indicates that the feature is exactly the same as described in some examples and substantially the same as described in other examples.

[0597] In the above description, the device may alternatively or additionally include: in some other examples, the device includes a distributed device system (e.g., a client / server device system). In the example where the device is provided to form (or the method is implemented as) a distributed system, each device forming a system component and / or part provides (or implements) one or more features, and the one or more features together implement the examples of the present disclosure. In some examples, the device is reconfigured by an entity other than its original manufacturer to implement the examples of the present disclosure by being provided with additional software (e.g., such software is downloaded by a user), which, when executed, causes the device to implement the examples of the present disclosure (such implementation is implemented entirely by the device, or as part of a system of devices as described above).

[0598] The above description describes some examples of the present disclosure, however, those of ordinary skill in the art will be aware of possible alternative structures and method features, which provide equivalent functions to the specific examples of structures and features described above in this article, and have been omitted from the above description for the sake of brevity and clarity. Nevertheless, the above description should be understood to implicitly include: references to such alternative structures and method features that provide equivalent functions, unless such alternative structures or method features are explicitly excluded in the above description of examples of the present disclosure.

[0599] While efforts have been made in the foregoing description to call attention to those features of the examples of the present disclosure which are regarded as particularly important, it should be understood that the applicants claim protection for any patentable feature or combination of features previously mentioned herein and / or shown in the accompanying drawings, whether or not specifically emphasized.

[0600] The examples of the present disclosure and the accompanying claims may be combined appropriately in any manner apparent to those skilled in the art. Individual references to "examples," "in some examples," etc. in this specification do not necessarily refer to the same example, and are not mutually exclusive, unless so stated and / or readily apparent to those skilled in the art from this specification. For example, a feature, structure, process, block, step, action, etc. described in one example may also be included in other examples, but not necessarily.

[0601] Each claim is incorporated into this specification as further disclosure, and the claims are (multiple) embodiments of the present disclosure. In addition, although the claims herein are provided as including specific dependencies, it is contemplated that any claim may be dependent on any other claim, and as long as any alternative embodiments can be generated from combining, integrating, and / or omitting features of individual claims, and / or changing the dependencies of the claims, any such alternative embodiments and their equivalents are also within the scope of the present disclosure.

Claims

1. A user equipment UE for accessing a radio access network RAN, the radio access network RAN ​​comprising at least: A central node, and distributed nodes, wherein the central node controls the distributed nodes, wherein the UE comprises: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the UE to at least: establishing a connection towards the radio access network; A UE context modification request is received from the central node, where the UE context modification request includes: Requests to change at least part of the low-level configuration, and an identifier associated with the request; performing the requested change of the low-level configuration; sending towards the central node a confirmation that the requested change has been performed; and The identifier is sent towards the distributed node.

2. The UE according to claim 1, wherein the UE context modification request is received from the central node in at least one selected from the following group: Layer 3 protocol messages; Radio Resource Configuration RRC message; and RRC reconfiguration message.

3. The UE according to any of the preceding claims, wherein the identifier is sent to the distributed node in at least one selected from the following group: via layer 2 signaling; in layer 2 protocol messages; and In the media access control MAC control element CE.

4. The UE according to any of the preceding claims, wherein the identifier is sent to the distributed node in at least one selected from the following group: via layer 1 signaling; In uplink control information UCI; In a channel state information (CSI) report; and In layer 1 measurement reports.

5. A UE according to any one of the preceding claims, wherein the UE context modification request comprises: an indicator, the indicator being used to request the UE to confirm to the distributed node that the UE has performed the requested change; as well as The UE is further configured to: based at least in part on the received indicator, send the identifier towards the distributed node to confirm to the distributed node that the UE has performed the requested change.

6. The UE according to any of the preceding claims, wherein the indicator is: a flag, or the identifier.

7. A UE according to any one of the preceding claims, wherein the identifier is: an identifier for identifying the request; a multi-bit identifier; or Logo.

8. The UE according to any one of the preceding claims, wherein the requested change comprises: A request for the UE, at least one selected from the following group: reconfiguring a low-layer protocol of the UE; adjusting layer 1 L1 measurements performed by the UE; reconfiguring L1 measurement reporting of the UE; measuring one or more beams of a target cell; as well as Report one or more measurements of one or more beams of the target cell.

9. A method for a user equipment UE, the method comprising: causing, at least in part, actions that result in: Establishing a connection towards a radio access network RAN, wherein the RAN comprises at least: a central node, and distributed nodes, the central node controlling the distributed nodes; A UE context modification request is received from the central node, where the UE context modification request includes: Requests to change at least part of the low-level configuration, and an identifier associated with the request; performing the requested change of the low-level configuration; sending towards the central node a confirmation that the requested change has been performed; and The identifier is sent towards the distributed node.

10. A computer program comprising: Instructions, when executed by a device, cause the device to perform the method according to claim 9.

11. A distributed node of a radio access network RAN, the radio access network RAN ​​comprising at least: A central node and distributed nodes, wherein the central node controls the distributed nodes, wherein the distributed nodes include: at least one processor; and At least one memory storing instructions, which, when executed by the at least one processor, cause the distributed node to at least: A first user equipment UE context modification request is received, where the first user equipment UE context modification request is sent from the central node toward the distributed node, where the first UE context modification request includes: Requests to change at least part of the low-level configuration, and an identifier associated with the request; receiving a second UE context modification request, the second UE context modification request being sent from the central node to the UE via the distributed node, the second UE context modification request comprising: Requests to change at least part of the low-level configuration, and the identifier; sending the second UE context modification request towards the UE; and The identifier is received from the UE.

12. The distributed node of claim 11, wherein the distributed node is further configured to determine that the UE has performed the requested change based at least in part on the identifier received from the UE.

13. The distributed node according to any one of claims 11 to 12, wherein the distributed node is further configured to: send a response to the first UE context modification request towards the central node.

14. The distributed node of claim 13, wherein the response to the first UE context modification request comprises: The identifier or an alternative identifier used to identify the request.

15. The distributed node according to any one of claims 11 to 14, wherein the distributed node is further configured to: receiving from the UE a confirmation that the requested change has been performed, for transmission towards the central node; and The acknowledgement is sent towards the central node.

16. The distributed node according to any one of claims 11 to 15, wherein the first UE context modification request comprises: A request for at least one or more of the following: reconfiguring a low-layer protocol of the UE; adjusting an interpretation of a layer 1 L1 measurement report received from the UE; receiving, from the UE, L1 measurements for a target cell; associating one or more measurements with one or more beams of a target cell, the one or more measurements from a measurement report received from the UE; as well as Handing over the UE to at least one item selected from the following group: a target cell controlled by the distributed node; a target cell controlled by another distributed node; and One or more candidate target cells.

17. The distributed node according to any one of claims 11 to 16, wherein the first UE context modification request comprises: a plurality of requested changes to the low-level configuration, and wherein: The identifier is configured to: identify the plurality of requested changes, or The identifier includes a plurality of identifiers configured to respectively identify the plurality of requested changes.

18. The distributed node according to any one of claims 11 to 17, wherein the distributed node is further configured to: adjusting an interpretation of a layer 1 L1 measurement report received from the UE based at least in part on the identifier received from the central node; and / or Based at least in part on the identifier received from the central node, one or more measurements are associated with one or more beams of a target cell, the one or more measurements being from a measurement report received from the UE.

19. The distributed node according to any one of claims 11 to 18, wherein the distributed node is further configured to determine, based at least in part on the identifier received from the UE, whether one or more L1 measurements received from the UE are to be associated with at least one item selected from the following group: Target community; one or more candidate target cells; one or more beams of the target cell; as well as One or more beams of one or more candidate target cells.

20. The distributed node according to any one of claims 11 to 19, wherein the distributed node is further configured to: Determining to trigger the UE to perform a handover of the UE to a target cell is based at least in part on at least one item selected from the following group: the identifier received from the UE; and An L1 measurement report is received from the UE after receiving the identifier from the UE.

21. A method for a distributed node of a radio access network RAN, the radio access network RAN ​​comprising at least: A central node, and distributed nodes, the central node controlling the distributed nodes, the method comprising: causing, at least in part, actions resulting in: A first user equipment UE context modification request is received, where the first user equipment UE context modification request is sent from the central node toward the distributed node, where the first UE context modification request includes: Requests to change at least part of the low-level configuration, and an identifier associated with the request; receiving a second UE context modification request, the second UE context modification request being sent from the central node to the UE via the distributed node, the second UE context modification request comprising: Requests to change at least part of the low-level configuration, and the identifier; sending the second UE context modification request towards the UE; and The identifier is received from the UE.

22. A computer program comprising: Instructions, which, when executed by a device, cause the device to perform the method according to claim 21.

23. A central node of a radio access network RAN, the radio access network RAN ​​comprising at least: A central node and distributed nodes, wherein the central node controls the distributed nodes, wherein the central node comprises: at least one processor; and At least one memory storing instructions, which, when executed by the at least one processor, cause the distributed node to at least: generating an identifier associated with a request to change at least a portion of a low-level configuration; Sending a first user equipment UE context modification request towards the distributed node, where the first user equipment UE context modification request includes: changing at least part of the underlying request, and the identifier; and Sending a second UE context modification request towards the UE, the second UE context modification request comprising: Requests to change at least part of the low-level configuration, and The identifier.

24. The central node according to claim 23, wherein the central node is further configured to: A confirmation is received from the UE that the requested change has been performed.

25. A method for a central node of a radio access network RAN, the radio access network RAN ​​comprising at least: A central node, and distributed nodes, the central node controlling the distributed nodes, the method comprising: causing, at least in part, actions resulting in: generating an identifier associated with a request to change at least a portion of a low-level configuration; Sending a first user equipment UE context modification request towards the distributed node, where the first user equipment UE context modification request includes: changing at least part of the underlying request, and the identifier; and Sending a second UE context modification request towards the UE, the second UE context modification request comprising: Requests to change at least part of the low-level configuration, and The identifier.

26. A computer program comprising: Instructions, which, when executed by a device, cause the device to perform the method according to claim 25.

27. A system comprising: A UE according to any one of claims 1 to 8, and a distributed node according to any one of claims 11 to 20.

28. The system of claim 27, further comprising: A central node according to any one of claims 23 to 24.

Images