Provision of measurement data for locating an inactive user equipment

By leveraging layer 1 measurements to identify mobility patterns and prioritize cell paging based on signal strength, the system efficiently locates inactive user equipment, addressing the inefficiencies of existing methods and enhancing network performance.

WO2024227592A1PCT designated stage expired Publication Date: 2024-11-07NOKIA TECHNOLOGIES OY
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2024/060258
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-04
Filing Date
2024-04-16
Publication Date
2024-11-07

AI Technical Summary

Technical Problem

Current strategies for locating inactive user equipment in a radio access network either result in significant network overhead or delay, as they either page all cells or rely on frequent updates, which are inefficient and time-consuming.

Method used

Implementing a system where network nodes receive and utilize layer 1 measurements from user equipment to identify mobility patterns and selectively page cells, optimizing the paging process by prioritizing cells with strong signal strengths and recent measurements.

Benefits of technology

This approach allows for faster and more efficient location of inactive user equipment, reducing network overhead and minimizing delays in reconnecting, while maintaining efficient resource management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2024060258_07112024_PF_FP_ABST
    Figure EP2024060258_07112024_PF_FP_ABST
Patent Text Reader

Abstract

According to an aspect, there is provided a solution in which a radio access network operating using layer 1 / layer 2 triggered mobility, LTM, can use the latest L1 measurements of prepared cells received from a particular user equipment, to better identify the latest user equipment location when performing radio access network paging. A first network node that supports at least one of central unit control plane, CU-CP, functionality or a layer 3 protocol of a radio access network may establish a connection towards a user equipment and receive information related to layer 1 measurements performed by the user equipment.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] PROVISION OF MEASUREMENT DATA FOR LOCATING AN INACTIVE USER EQUIPMENT

[0002] TECHNICAL FIELD

[0003] Various example embodiments generally relate to the field of telecommunication systems. In particular, some example embodiments relate to a solution for enabling locating an inactive user equipment in a radio access network .

[0004] BACKGROUND

[0005] A user equipment may have a RRC_INACTIVE (RRC, Radio Resource Control) in a wireless communication network, for example, a 5G network. In the RRC_INACTIVE state, the UE is in a CM-CONNECTED (CM, Connection Management) state and can move within an area, i.e. RAN-based Notification Area (RAN, Radio Access Network) configured by a radio access network RAN) , without notifying the RAN. In the RRC_INACTIVE state, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving Access and Mobility management Function (AMF) and User Plane Function (UPF) .

[0006] If the last serving gNB then receives downlink (DL) data from the UPF or DL UE-associated signalling from the AMF while the UE is in RRC_INACTIVE state, the last serving gNB pages the UE in the cells corresponding to the RAN-based Notification Area (RNA) and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s) . This paging is called RAN paging.

[0007] The RAN may be configured with multiple cells. When the RNA is configured with multiple cells, the UE will not perform many RNA updates (RNAU) and it can be quickly traceable by paging all or almost all cells in case of incoming traffic. On the other hand, if the RNA is a small set of cells , few cells need to be paged to locate the UE . However, the UE need to send an RNAU often, as it will cross the RNA border frequently . Thus , there exist several strategies to locate the UE faster, for example , by defining a small RNA that causes frequent RNAU of the UEs , or defining a large RNA that causes either paging of all cells or causes delay on locating the UE . However, the strategies have either the drawback of generating signi ficant overhead or delaying the paging procedure .

[0008] SUMMARY

[0009] This summary is provided to introduce a selection of concepts in a simpli fied form that are further described below in the detailed description . This summary is not intended to identi fy key features or essential features of the claimed subj ect matter, nor is it intended to be used to limit the scope of the claimed subj ect matter .

[0010] Example embodiments of the present disclosure provides a solution in which more ef ficient paging of a user equipment may be provided . Thi s and other benefits may be achieved by the features of the independent claims . Further example embodiments are provided in the dependent claims , the description, and the drawings .

[0011] According to a first aspect , a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, may comprise at least one processor and at least one memory storing instructions which, when executed by the at least one processor, cause the first network node to at least to perform : establish a connection towards a user equipment ; and receive information related to layer 1 measurements performed by the user equipment .

[0012] In an example embodiment of the first aspect , the information related to the layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .

[0013] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : transmit a message triggering provision of the information related to the layer 1 measurements .

[0014] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : start a validity timer for the layer 1 measurements .

[0015] In an example embodiment of the first aspect , the layer 1 measurements comprises layer 1 measurements received from a source network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network and from a target network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of the radio access network .

[0016] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : receive the layer 1 measurements with a retrieve UE context response message from a source network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of the radio access network .

[0017] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : receive layer 3 measurements associated with the user equipment with a RAN noti fication area update message .

[0018] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : receive incoming traf fic for the user equipment ; and page the user equipment according to a paging scheme associated with the layer 1 measurements .

[0019] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : page the last serving cell of the user equipment and cells indicated in a configurable number of last measurements .

[0020] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : identi fy a mobility pattern of the user equipment ; and page cells associated with the mobility pattern .

[0021] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : page the last serving cel l of the user equipment and a subset of cells indicated in the layer 1 measurements .

[0022] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : select a set of beams for each identi f ied cell based on the layer 1 measurements .

[0023] In an example embodiment of the first aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : transmit the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network .

[0024] According to a second aspect , a second network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of a radio access network, may comprise at least one processor ; and at least one memory storing instructions which, when executed by the at least one proces sor, cause the second network node at least to : establish a connection towards a user equipment ; receive , from a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment ; and transmit , towards the first network node , information related to received layer 1 measurements .

[0025] In an example embodiment of the second aspect , the information related to the received layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .

[0026] In an example embodiment of the second aspect , the instructions , when executed by the at least one processor, cause the second network node to perform : receive a radio resource control , RRC, release message from the first network node to be forwarded to the user equipment to instruct the user equipment to operate in an inactive state , wherein together with the RRC release message a request for providing information related to the layer 1 measurement is received .

[0027] In an example embodiment of the second aspect , the instructions , when executed by the at least one processor, cause the second network node to perform : transmit an LTM cell change trigger message towards the user equipment ; and transmit a message towards the first network node indicating the triggered LTM cell change and including the information related to the layer 1 measurements .

[0028] According to a third aspect , a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, may comprise at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the first network node to at least to : transmit layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM .

[0029] In an example embodiment of the third aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : transmit the layer 1 measurements with a retrieve UE context response message to a target network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of the radio access network .

[0030] In an example embodiment of the third aspect , the instructions , when executed by the at least one processor, cause the first network node to perform : transmit the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network in response to receiving a handover success message .

[0031] According to a fourth aspect , a user equipment for operating in an inactive state , may comprise at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to : establish a connection towards a first network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of a radio access network; receive , from the first network node , a message including an instruction to operate in the inactive state ; and transmit , when operating in the inactive state , a radio resource control , RRC, resume request message including information related to at least one measurement performed by the user equipment .

[0032] In an example embodiment of the fourth aspect , the information is related to layer 1 and / or layer 3 measurements performed by the user equipment .

[0033] According to a fi fth aspect , a method performed by a first network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of a radio access network, comprises establishing a connection towards a user equipment ; and receiving information related to layer 1 measurements performed by the user equipment .

[0034] In an example embodiment of the fi fth aspect , the information related to the layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .

[0035] In an example embodiment of the fi fth aspect , the method further comprises transmitting a message triggering provision of the information related to the layer 1 measurements .

[0036] In an example embodiment of the fi fth aspect , the method further comprises starting a validity timer for the layer 1 measurements . In an example embodiment of the fi fth aspect , the layer 1 measurements comprises layer 1 measurements received from a source network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network and from a target network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of the radio access network .

[0037] In an example embodiment of the fi fth aspect , the method further comprises receiving the layer 1 measurements with a retrieve UE context response message from a source network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of the radio access network .

[0038] In an example embodiment of the fi fth aspect , the method further comprises receiving layer 3 measurements associated with the user equipment with a RAN noti fication area update message .

[0039] In an example embodiment of the fi fth aspect , the method further comprises receiving incoming traf fic for the user equipment ; and paging the user equipment according to a paging scheme associated with the layer 1 measurements .

[0040] In an example embodiment of the fi fth aspect , the method further comprises paging the last serving cell of the user equipment and cells indicated in a configurable number of last measurements .

[0041] In an example embodiment of the fi fth aspect , the method further comprises identi fying a mobility pattern of the user equipment ; and paging cells associated with the mobility pattern .

[0042] In an example embodiment of the fi fth aspect , the method further comprises paging the last serving cell of the user equipment and a subset of cells indicated in the layer 1 measurements .

[0043] In an example embodiment of the fi fth aspect , the method further comprises selecting a set of beams for each identi fied cell based on the layer 1 measurements .

[0044] In an example embodiment of the fi fth aspect , the method further comprises transmitting the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network .

[0045] According to a s ixth aspect , a method performed by a second network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of a radio access network, comprises : establishing a connection towards a user equipment ; receiving, from a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment ; and transmitting, towards the first network node , information related to received layer 1 measurements .

[0046] In an example embodiment of the sixth aspect , the information related to the received layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .

[0047] In an example embodiment of the fi fth aspect , the method further comprises receiving a radio resource control , RRC, release message from the first network node to be forwarded to the user equipment to instruct the user equipment to operate in an inactive state , wherein together with the RRC release message a request for providing information related to the layer 1 measurement is received .

[0048] In an example embodiment of the fi fth aspect , the method further comprises transmitting an LTM cell change trigger message towards the user equipment ; and transmitting a message towards the first network node indicating the triggered LTM cell change and including the information related to the layer 1 measurements .

[0049] According to a seventh aspect , a method performed by a first network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of a radio access network, comprises transmitting layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM .

[0050] In an example embodiment of the seventh aspect , the method further comprises transmitting the layer 1 measurements with a retrieve UE context response mes s age to a target network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of the radio acces s network .

[0051] In an example embodiment of the seventh aspect , the method further comprises transmitting the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of the radio acces s network in response to receiving a handover succes s mes s age .

[0052] According to an eight aspect , a method for operating a user equipment operating in an inactive state , comprises establishing a connection towards a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network; receiving, from the first network node , a message including an instruction to operate in the inactive state ; and transmitting, when operating in the inactive state , a radio resource control , RRC, resume request message including information related to at least one measurement performed by the user equipment .

[0053] In an example embodiment of the eighth aspect , the information is related to layer 1 and / or layer 3 measurements performed by the user equipment .

[0054] According to a ninth aspect , a (non-transitory ) computer readable medium is disclosed . The (non- transitory) computer readable medium may comprise program instructions that , when executed by an apparatus , cause the apparatus to perform a method according to the fi fth, sixth, seventh or eighth aspect , or any example embodiment thereof .

[0055] According to a tenth aspect , a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, may comprise means for : establishing a connection towards a user equipment ; and receiving information related to layer 1 measurements performed by the user equipment .

[0056] According to an eleventh aspect , a second network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of a radio access network, may comprise means for : establishing a connection towards a user equipment ; receiving, from a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment ; and transmitting, towards the first network node , information related to received layer 1 measurements .

[0057] According to a twel fth aspect , a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, may comprise means for transmitting layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM .

[0058] According to a thirteenth aspect , a user equipment for operating in an inactive state , may comprise means for : establishing a connection towards a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network; receiving, from the first network node , a message including an instruction to operate in the inactive state ; and transmitting, when operating in the inactive state , a radio resource control , RRC, resume request message including information related to at least one measurement performed by the user equipment .

[0059] Many of the attendant features will be more readily appreciated as they become better understood by reference to the following detailed description considered in connection with the accompanying drawings .

[0060] DESCRIPTION OF THE DRAWINGS

[0061] The accompanying drawings , which are included to provide a further understanding of the example embodiments and constitute a part of this speci fication, illustrate example embodiments and together with the description help to understand the example embodiments. In the drawings :

[0062] FIG. 1 illustrates an example of a split access node architecture .

[0063] FIG. 2A illustrates an example of a RAN-based notification area.

[0064] FIG. 2B illustrates another example of a RAN-based notification area.

[0065] FIG. 3 illustrates an example of an apparatus configured to practice one or more example embodiments.

[0066] FIG. 4 illustrates the concept of layer 1 / layer 2 triggered mobility (LTM) in a radio access network.

[0067] FIG. 5A illustrates a signaling diagram according to an example embodiment.

[0068] FIG. 5B illustrates a signaling diagram according to another example embodiment.

[0069] FIG. 5C illustrates a signaling diagram according to another example embodiment.

[0070] FIG. 5D illustrates a signaling diagram according to another example embodiment.

[0071] FIG. 6 illustrates example of a method according to an example embodiment.

[0072] FIG. 7 illustrates example of a method according to another example embodiment.

[0073] FIG. 8 illustrates example of a method according to another example embodiment.

[0074] FIG. 9 illustrates example of a method according to another example embodiment.

[0075] FIG. 10 illustrates a signaling diagram according to an example embodiment.

[0076] FIG. 11 illustrates a signaling diagram according to another example embodiment.

[0077] FIG. 12 illustrates a signaling diagram according to another example embodiment. FIG. 13 illustrates a signaling diagram according to another example embodiment.

[0078] FIG. 14 illustrates a signaling diagram according to another example embodiment.

[0079] Like references are used to designate like parts in the accompanying drawings .

[0080] DETAILED DESCRIPTION

[0081] Reference will now be made in detail to example embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below in connection with the appended drawings is intended as a description of the present examples and is not intended to represent the only forms, in which the present example may be constructed or utilized. The description sets forth the functions of the example and the sequence of steps for constructing and operating the example. However, the same or equivalent functions and sequences may be accomplished by different examples.

[0082] FIG. 1 illustrates an example of a split access node architecture. An access node, represented by a gNB 100, may be split, functionally and / or physically, to a central unit (CU) 108 and one or more distributed units (DU) 102-1, 102-2, ..., 102-N. The CU 108 may be also referred to as a gNB-CU and the DU(s) be also referred to as gNB-DU(s) . The CU 108 may comprise a control plane (CP) and user plane (UP) entities, represented by a gNB- CU-CP 104 and a gNB-CU-UP 106, respectively. The gNB-CU- CP 104 may be configured to control communication of signaling data that enables transfer of user / application data at the user plane. User plane communications may be provided by one or more gNB-CU-UPs 106 associated with the gNB-CU-CP 104. CU 108 and DU(s) may be configured to provide radio access network (RAN) services to device (s) , represented by user equipment (UE) 110, at one or more cells.

[0083] Control and user plane entities of the CU 108 may communicate via a communication interface, such as for example an El interface. The CU 108 may communicate with a DU 102-n (n = 1...N) over a communication interface, such as for example an Fl interface. The Fl interface may comprise control and user plane interfaces (Fl-C, Fl-U) between the DU 102-n and the control and user plane entities of the CUs 108, respectively. The DU(s) 102-1 to 102-N may be collectively referred to as the DU(s) 102, where N is a positive integer ranging for example from 1 to 100. However, higher values, such as for example up to 236-l, are possible as well.

[0084] The CU / DU-split architecture enables disaggregation of the RAN, thus enabling operators to utilize different vendors for different network nodes, but also to enable network vendors to split their network implementations for scalability purposes. For example, control and user planes may be separated to their own entities, thereby enabling control and user plane functions to be dimensioned separately. The split may be however (almost) invisible to a user equipment (UE) and therefore, at the UE side, the protocol layers may be (mostly) unaware of the split, except for minor parts which the UE may implicitly determine from the associated RRC configuration.

[0085] The following description may provide further details of alternatives, modifications and variances: a gNB comprises e.g., a node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC, e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2 incorporated by reference. The gNB-CU 108 comprises e.g., a logical node hosting e.g., RRC, SDAP and PDCP protocols of the gNB or RRC and PDCP protocols of the en-gNB that controls the operation of one or more gNB-DUs . The gNB-CU 108 terminates the Fl interface connected with the gNB-DU.

[0086] The gNB-DU 102-1, 102-2, 102-N comprises e.g., a logical node hosting e.g., RLC, MAC and PHY layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU.

[0087] The gNB-CU-CP 104 comprises e.g., a logical node hosting e.g., the RRC and the control plane part of the PDCP protocol of the gNB-CU for an en-gNB or a gNB. The gNB-CU-CP 104 terminates the El interface connected with the gNB-CU-UP 106 and the Fl-C interface connected with the gNB-DU.

[0088] The gNB-CU-UP 106 comprises e.g., a logical node hosting e.g., the user plane part of the PDCP protocol of the gNB-CU for an en-gNB, and the user plane part of the PDCP protocol and the SDAP protocol of the gNB-CU for a gNB. The gNB-CU-UP 106 terminates the El interface connected with the gNB-CU-CP 104 and the Fl-U interface connected with the gNB-DU, e.g., according to 3GPP TS 38.401 V16.6.0 (2021-07) section 3.1 incorporated by reference .

[0089] Different functional splits between the central and distributed unit are possible, e.g., called options:

[0090] Option 1 (lA-like split) : o The function split in this option is similar to the 1A architecture in DC. RRC is in the central unit. PDCP, RLC, MAC, physical layer and RE are in the distributed unit.

[0091] Option 2 (3C-like split) : o The function split in this option is similar to the 3C architecture in DC. RRC and PDCP are in the central unit. RLC, MAC, physical layer and RF are in the distributed unit.

[0092] Option 3 (intra RLC split) : o Low RLC (partial function of RLC) , MAC, physical layer and RF are in the distributed unit. PDCP and high RLC (the other partial function of RLC) are in the central unit.

[0093] Option 4 (RLC-MAC split) : o MAC, physical layer and RF are in the distributed unit. PDCP and RLC are in the central unit.

[0094] Or else, e.g., according to 3GPP TR 38.801 V14.0.0 (2017-03) section 11 incorporated by reference.

[0095] A gNB supports different protocol layers, e.g., Layer 1 (LI) - physical layer.

[0096] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC) , Radio Link Control (RLC) , Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP) , where e.g. : o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC QoS flows; o Comp, refers to header compression and Segm. To segmentation; o Control channels include (BCCH, PCCH) . Layer 3 (L3) includes e.g., Radio Resource Control (RRC) , e.g., according to 3GPP TS 38.300 V16.6.0 (2021- 06) section 6 incorporated by reference.

[0097] A Radio Access Network (RAN) node or network node like e.g. a gNB, base station, gNB CU or gNB DU or parts thereof may be implemented using e.g. an apparatus with at least one processor and / or at least one memory (with computer-readable instructions (computer program) ) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-) layer of a RAN (Radio Access Network) , e.g. layer 2 and / or layer 3.

[0098] The gNB CU and gNB DU parts may e.g., be co-located or physically separated. The gNB CU may include two parts a CU-CP and a CU-UP part. The CU-CP part may even be split, e.g. in a first CP part located at the CU, and a second CP part located at the DU. This first and second CP part may perform different RRC operations and processing, e.g. central and local operations, respectively, or overlapping operations which may need coordination. The gNB DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A Central Unit (CU) may also be called BBU / REC / RCC / C-RAN / V-RAN, O-RAN, or part thereof. A Distributed Unit (DU) may also be called RRH / RRU / RE / RU, or part thereof. Hereinafter, in various example embodiments of the present disclosure, the CU- CP (or more generically, the CU) may also be referred to as a (first) network node that supports at least one of central unit control plane functionality or a layer 3 protocol of a radio access network; and similarly, the DU may be referred to as a (second) network node that supports at least one of distributed unit functionality or the layer 2 protocol of the radio access network. A gNB-DU supports one or multiple cells, and could thus serve as e.g., a serving cell for a user equipment (UE) .

[0099] A user equipment (UE) may include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (Radio Access Network) , a smartphone, an in-vehicle apparatus, an loT device, a M2M device, or else. Such UE or apparatus may comprise: at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, like e.g. RRC connection to the RAN. A UE is e.g., configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell) . A UE may generate and transmit and receive RRC messages containing one or more RRC PDUs (Packet Data Units) .

[0100] 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, incorporated by reference) .

[0101] A UE is e.g., either in RRC_CONNECTED state or in RRC_INACTIVE state when an RRC connection has been established .

[0102] In RRCJCONNECTED state a UE may: o store the AS context; o transfer unicast data to / from the UE; o monitor control channels associated with the shared data channel to determine if data is scheduled for the data channel; o provide channel quality and feedback information; o perform neighboring cell measurements and measurement reporting.

[0103] The RRC protocol includes e.g. the following main functions : o RRC connection control; o measurement configuration and reporting; o establishment / modif ication / release of measurement configuration (e.g. intrafrequency, inter-frequency and inter-RAT measurements) ; o setup and release of measurement gaps; o measurement reporting.

[0104] FIG. 2A illustrates an example of a RAN-based notification area (RNA) 200. A UE in the RRC_INACTIVE state can be configured by the last serving NG-RAN node with the RNA 200. In general, the RAN can cover a single or multiple cells. In the example illustrated in FIG. 2A, the RNA 200 covers a subset of cells 1, cells 2 and cells 3. A RAN-based notification area update (RNAU) is periodically sent by the UE as configured, when the UE it reselects a cell that is not part of configured RNA. The cells 1, cells 2 and cells 3 may be controlled by a network node, i.e. central unit (CU) 202, that supports central unit control plane, CU-CP, functionality of a radio access network. Cells 1 may belong to a first distributed unit, cells 2 may belong to a second distributed unit and cells 3 may belong to a third distributed unit. A User Plane Function (UPF) 204 may be connected to the central unit 112.

[0105] FIG. 2B illustrates another example of an RNA 206. The RNA 206 covers a subset of cells 1, cells 2, cells 3, cells 4 and cells 5. A RAN-based notification area update (RNAU) is periodically sent by the UE as configured, when the UE it reselects a cell that is not part of configured RNA. The cells 1, cells 2 and cells 3 may be controlled by a CU 208 and the cells 4 and cells 5 may be controlled by a CU 210. Cells 1 may belong to a first distributed unit, cells 2 may belong to a second distributed unit, cells 3 may belong to a third distributed unit, cells 4 may belong to a fourth distributed unit and cells 5 may belong to a fifth distributed unit. The CU 208 controls the first, second and third distributed units and the CU 210 controls the fourth and fifth distributed units. A UPF 204 may be connected to the central unit 208 and 210.

[0106] When considering the case that the RNA is set to a relatively large area for reducing the frequent RNAU of the UEs and in order to reduce the paging cost, several paging strategies exist in the order to reduce the paging cost, for example:

[0107] 1) Page the last known cell and hope that the UE is there. It is very likely that the UE has already left the cell. In this case, paging only the last known cell will be in vain as the UE cannot be detected in the first attempt. Then, the network may start paging (sequentially) the potential cells where the UE might be located which increases the paging cost incrementally and increases the delay to connection resume setup.

[0108] 2) Page the last known cell and neighboring cells simultaneously and hope UE is there. Network layout (Error! Reference source not found.) can be quite complex. The UE may be located in a small coverage area of one cell, which is not really in the main coverage area of the cell. If the last known cell has a large set of neighbor cells, it results in exhaustive paging of multiple neighbor cells. Further, if the UE is neither detected in the last known cell nor in the neighbor cells, the network may start paging (sequentially) the potential cells (beyond the last known and neighbor cells) where the UE might be located. This increases the paging cost incrementally and increases the delay in locating the UE .

[0109] 3) Page all cells in RNA simultaneously. It is known that the UE is in one of the cells in the given RNA as the UE performs RNAU when changing the RNA. Eventually, paging all cells in the RNA simultaneously locates the UE immediately but this incurs significant network overhead.

[0110] Thus, there is a need for a solution that would not cause significant network overhead while simultaneous avoiding the delay in locating the UE .

[0111] FIG. 3 illustrates an example of an apparatus 300 configured to practice one or more example embodiments. The apparatus 300 may comprise a user node, a user equipment, an access node, an access point, base station, a radio network node, or a split portion thereof, or in general a device configured to implement functionality described herein. The apparatus 300 may comprise at least one processor 302. The at least one processor 302 may comprise, for example, one or more of various processing devices, such as for example a co-processor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like. The apparatus 300 may further comprise at least one memory 304. The memory 304 may be configured to store, for example, computer program code or the like, for example operating system software and application software. The memory 304 may comprise one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination thereof. For example, the memory may be embodied as magnetic storage devices (such as hard disk drives, magnetic tapes, etc.) , optical magnetic storage devices, or semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , etc.) . The memory 304 is provided as an example of a (non-transitory ) computer readable medium. The term "non-transitory, " as used herein, is a limitation of the medium itself (i.e., tangible, not a signal ) as opposed to a limitation on data storage persistency (e.g., RAM vs . ROM) .

[0112] The apparatus 300 may further comprise a communication interface 308 configured to enable the apparatus 300 to transmit and / or receive information. The communication interface 308 may comprise an internal or external communication interface, such as for example an El, Fl, Fl-C, and / or F2-C interface. The apparatus 300 may further comprise other components and / or functions such as for example a user interface (not shown) comprising at least one input device and / or at least one output device. The input device may take various forms such a keyboard, a touch screen, or one or more embedded control buttons. The output device may for example comprise a display, a speaker, or the like.

[0113] When the apparatus 300 is configured to implement some functionality, some component and / or components of the apparatus 300, such as for example the at least one processor 302 and / or the at least one memory 304, may be configured to implement this functionality. Furthermore, when the at least one processor 302 is configured to implement some functionality, this functionality may be implemented using program code 306 comprised, for example, in the at least one memory 304.

[0114] The functionality described herein may be performed, at least in part, by one or more computer program product components such as software components. According to an example embodiment, the apparatus 300 comprises a processor or processor circuitry, such as for example a microcontroller, configured by the program code 306, when executed, to execute the embodiments of the operations and functionality described herein. Program code 306 is provided as an example of instructions which, when executed by the at least one processor 302, cause performance of the apparatus 300.

[0115] Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include field-programmable gate arrays (FPGAs) , application-specific integrated circuits (ASICs) , application-specific standard products (ASSPs) , system-on-a-chip systems (SOCs) , complex programmable logic devices (CPLDs) , graphics processing units (GPUs) , or the like.

[0116] The apparatus 300 may be configured to perform method (s) described herein or comprise means for performing method (s) described herein. In one example, the means comprises the at least one processor 302, the at least one memory 304 including program code 306 configured to, when executed by the at least one processor 302, cause the apparatus 300 to perform the method ( s ) .

[0117] The apparatus 300 may comprise, for example, a user node, a user equipment or a network device, for example, an access node, an access point, a base station, or a central / distributed unit thereof. Although the apparatus 300 is illustrated as a single device, it is appreciated that, wherever applicable, functions of the apparatus 300 may be distributed to a plurality of devices.

[0118] FIG. 4 illustrates the concept of layer 1 / layer 2 triggered mobility (LTM) in a radio access network. In general, the LTM is a procedure in which a gNB receives measurement reports from UEs, and on their basis the gNB changes UEs' serving cell (s) through MAC CE . The example illustrated in FIG. 4 assumes a disaggregated architecture comprising a UE 400, a source DU 402, target DU 404 and a CU 406.

[0119] Steps 408-412: The UE sends a L3 Measurement Report message to the CU 406 via the source DU 402. The CU 406 decides to use LTM and initiates LTM candidate cells preparation .

[0120] Steps 414-416: The CU 406 sends a UE context setup request to the target DU 404 for the preparation of the target cells.

[0121] Steps 418-420: The CU 406 sends a UE context modification request to the source DU 402 for the preparation of the target cells in the source DU 402. Additionally this message may be used for the provision of target cell information in the source DU 402.

[0122] Steps 422-430: The CU 406 prepares the RRC Configuration and provides it to the UE 400. The UE 400 stores the configuration of LTM candidate target cell (s) and transmits a RRCReconf igurationComplete message to the CU 402. Steps 432-434: The UE 400 may perform DL synchronization and TA acquisition with candidate target cell (s) before receiving the LTM cell switch command.

[0123] Steps 436-440: The UE 400 performs layer 1 (LI) measurements on the configured LTM candidate target cell (s) , and transmits lower-layer measurement reports to the source DU 402.

[0124] Steps 442-444: The source DU 402 decides to execute LTM cell switch to a target cell, and transmits a MAC CE triggering LTM the cell switch.

[0125] Step 446: The UE switches to the configuration of the LTM candidate target cell and accesses the target cell. If needed (if Timing Advance is not available) it performs the random access process.

[0126] Steps 448-450: The UE 400 indicates a successful completion of the LTM cell switch towards the target cell using an RRC Reconfiguration complete message.

[0127] Steps 452-454: UE context is released if the CU 406 decides accordingly.

[0128] FIG. 5A illustrates a signaling diagram according to an example embodiment. The example involves the following elements: a UE 500, a distributed unit DU1 502 of a source gNB 508, a distributed unit DU2 504 of the source gNB 508, a central unit CUI 506 of the source gNB 508, a distributed unit DUS 510 of a target gNB 516, a distributed unit DU4 512 of the target gNB 516, a central unit CU2 514 of the target gNB 516.

[0129] At 518, the UE 500 is configured and operates in the Layer 1 / Layer Triggered Mobility (LTM) . Target cells from the target DUs, i.e., from the DU2 504 and the DUS 510, are prepared during the preparation phase of LTM.

[0130] At 520, 522 and 524, the UE 500 sends layer 1 (LI) measurement reports to the DU1 502. The measurements include the measurements of the prepared cells that belong to the DU1 502, the DU2 504, and the DU3 510.

[0131] At 526, based on the UE requirement / transmission status (for example, there is no DL / UL transmissions) the CUI 506 may decide to send an RRC Release message (to trigger the suspension using the suspendConfig IE) to trigger the UE 500 to switch to RRC Inactive state (in FIG. 5A the message is marked as RRC Suspend for clarity) . The message is sent using a DL RRC Message Transfer to the DU1 502. In this message, the CUI 506 may also indicate to the DU1 502 that it needs the latest LI measurement reports (for specific set of cells) . The CUI may also indicate that the LI measurement reports are needed for a specific time window.

[0132] In an example embodiment, the CUI 506 may request the LI measurements after deciding to page the UE accordingly (i.e., at 538) . In this case, based on the UE inactivity time the CUI 506 may decide whether to request or not for LI measurement (i.e., determine the paging cell based on LI measurement) , and also determine the request configuration (for example, the time window, the number of requested cells and the threshold) .

[0133] In another example embodiment, the CUI 506 may request for cells' ID / TCI-states (or measurement value) that has been measured above a certain threshold within the last x sec, or N number of measurement instances.

[0134] At 528, the DU1 502 sends the RRC Suspend message to the UE 500.

[0135] AT 530, the DU1 502 provides the LI measurements of the UE 500 to the CUI 506. The LI measurements relate to the specific time window. The measurements may also indicate the physical cell IDs (PCIs) of the reported LI measurements. The DU1 502 may be configured to store the LI measurements received from the UE 500. In an example embodiment, the LI measurements may be stored for a specific time or for a configurable time.

[0136] At 532, the CUI 506 may start a validity timer for the LI measurements. In an example embodiment, the validity timer may be in coordination with the DU1 502. The validity timer ensures the validity of the measurement. If the timer expires, the LI measurements may be considered obsolete and discarded in one example embodiment. In another example embodiment, some of all of the LI measurement may still be used even if the validity timer has expired.

[0137] At 534 and 536, the UE 500 turns to RRC Inactive and remains in RRC Inactive.

[0138] At or before 538, incoming traffic comes to the last serving CU, i.e., the CUI 506. Based, for example, on the traffic type requirement (for example, if there is no low-latency requirement) the CUI 506 may decide the paging strategy considering the latest LI measurements obtained at 530.

[0139] In an example embodiment, the CUI 506 may decide to page the last serving cell and the ones indicated in a configurable number of last measurements (as the LI measurements are provided along with the PCIs) .

[0140] In another example embodiment, the CUI 506 may identify a mobility pattern of the UE 500 and page the respective cells. If a mobility pattern is identified, this information may be made user of in deciding the cell paging scheme.

[0141] In another example embodiment, the CUI 506 may page the last serving cell and a subset of the cells indicated in the measurements in the specific time window.

[0142] In addition to the any of the paging scheme examples above, for each identified cell, a set of beams (for example, in FR2 ) may be derived / selected based on the LI measurements to repeat a paging message.

[0143] At 540-542, the CUI 506 sends the paging message to the UE 500 in accordance with the paging scheme using the indicated cells and the beams (via the respective DUs, i.e., DU1 502 and DU3 510) . In an example embodiment the operation of the paging scheme may be supervised by a timer.

[0144] FIG. 5B illustrates a signaling diagram according to another example embodiment. It is possible that the UE 500 switches to a new cell belonging to a different CU (for example, the CU2 514) and upon the cell switch, the target CU, i.e., the CU2 514, may decide that the UE 500 should change to RRC Inactive state. In this case, in order to enable the CU2 504 to perform an efficient paging, the source CU (i.e., CUI 506) should provide the LI measurements to the target CU (i.e., the CU2 514) .

[0145] At 518, the UE 500 is configured and operates in the LTM, and the serving DU is the DU1 502.

[0146] At 546, the UE 500 sends LI measurement reports to the DU1 502. The measurements include cells that belong to DU1 502, DU2 504 and DU3 510.

[0147] At 548, the UE 500 is handed over using the LTM to the DU3 510.

[0148] At 550, the DU1 502 sends to the CUI 506 the latest LI measurement reports with the cell change triggered command. In an example embodiment, the measurement may relate to a specific time window. The DU1 502 may be configured to store the LI measurements received from the UE 500. In an example embodiment, the LI measurements may be stored for a specific time or for a configurable time .

[0149] At 552, the CU2 514 informs the CUI 506 that the

[0150] LTM handover is successful. At 554, the CUI 506 provides the CU2 514 with the latest LI measurement reports that may relate to the specific time window. In another example embodiment, the CU2 514 may ask for the LI measurements once it decides that it needs these measurements at the transmission of the RRC Release message (to trigger the suspension using the suspendConfig IE) .

[0151] At 556, the UE 500 accesses the network using a cell in the DU3 510, having the LTM configured.

[0152] The remaining steps 558-574 are identical to the steps 528-542.

[0153] FIG. 5C illustrates a signaling diagram according to another example embodiment. In example illustrated in FIG. 5C, the UE 500 is already in the RRC Inactive state and "wakes up" to inform the network about an update in the RNA.

[0154] The steps 518 and 577-584 correspond with the steps 518-534 discussed earlier relating to FIG. 5A.

[0155] At 585, the RNA Update timer (T380) expires or the UE 500 moves outside the configured RNA.

[0156] In response to the triggers obtained at 585, at 586 the UE 500 performs an RNA update to the new CU (i.e. to the CU2 514 via the DU3 510) and provides with the RNA update the latest L3 measurements to the CU2 514.

[0157] At 587 and 588, the CU2 514 retrieves the UE Context from the previous serving CU (i.e., the CUI 506) . The CUI 506 provides in a Retrieve UE Context Response also the latest LI measurements to be used in case the CU2 516 needs to page the UE 500. The CUI 506 may also provide the time of the LI measurements that are measured by the UE 500 for indicating how much outdated the reported LI measurements are. At 589, the CU2 514 decides to send the UE 500 to the RRC Inactive state again and resets the validity timer relating to the LI measurements.

[0158] At 590-591, the CU2 514 transmits an RRC Suspend message to the UE 500 via the DUS 510.

[0159] At 592, the CU2 514 performs a path switch and informs the AMF about the anchor cell change.

[0160] FIG. 5D illustrates a signaling diagram according to another example embodiment. In example illustrated in FIG. 5D, the UE 500 is already in the RRC Inactive state and wakes up to inform the network about an update in the RNA.

[0161] At 585, the RNA Update timer (T380) expires or the UE 500 moves outside the configured RNA.

[0162] In response to the triggers obtained at 585, at 586 the UE 500 performs an RNA update to the new CU (i.e. to the CU2 514 via the DUS 510) and provides with the RNA update the latest L3 measurements to the CU2 514.

[0163] At 593 and 594, the UE 500 sends LI measurement reports to the DUS 510. The measurements include cells that belong to DU2 504 and DUS 510.

[0164] At 595 and 596, the CU2 514 retrieves the UE Context from the previous serving CU (i.e., the CUI 506) . The CUI 506 provides in a Retrieve UE Context Response also the latest LI measurements to be used in case the CU2 516 needs to page the UE 500. The CUI 506 may also provide the time of the LI measurements that are measured by the UE 500 for indicating how much outdated the reported LI measurements are.

[0165] At 597, the CU2 514 decides to send the UE 500 to the RRC Inactive state again and resets the validity timer relating to the LI measurements.

[0166] Steps 598-600 are identical to the steps 526-530 discussed relating to FIG. 5A. At 601 , the CU2 514 performs a path switch and informs the AMF about the anchor cell change .

[0167] FIG . 6 illustrates an example of a method for providing layer 1 measurements when a user equipment is being suspended at a network node that supports at least one o f central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network .

[0168] At 602 , the method may comprise establishing, by the network node , a connection towards a user equipment .

[0169] At 604 , the method may comprise receiving information related to layer 1 measurements performed by the user equipment .

[0170] FIG . 7 illustrates an example of a method for providing layer 1 measurements when a user equipment is being suspended at a network node that supports at least one of distributed unit , DU, functionality or a layer 2 protocol of a radio access network .

[0171] At 700 , the method may comprise establishing a connection towards a user equipment .

[0172] At 702 , the method may comprise receiving, from a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment .

[0173] At 704 , the method may comprise transmitting, towards the first network node , information related to received layer 1 measurements .

[0174] FIG . 8 illustrates an example of a method for providing layer 1 measurements when a user equipment is being suspended at a network node that supports at least one of central unit control plane, CU-CP, functionality or a layer 3 protocol of a radio access network.

[0175] At 800, the method may comprise transmitting, by the network node, layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM.

[0176] FIG. 9 illustrates an example of a method for a user equipment for operating in an inactive state.

[0177] At 900, the method may comprise establishing a connection towards a first network node that supports at least one of central unit control plane, CU-CP, functionality or a layer 3 protocol of a radio access network .

[0178] At 902, the method may comprise receiving, from the first network node, a message including an instruction to operate in the inactive state.

[0179] At 904, the method may comprise transmitting, when operating in the inactive state, a radio resource control, RRC, resume request message including information related to at least one measurement performed by the user equipment.

[0180] In the following further embodiments will be described. Part of the features of the embodiments might be used in other embodiments as well and / or independent from other features of the respective embodiment.

[0181] Starting from 3GPP TS38.300 V17.3.0 (2022-12) an RRC inactive state is described in

[0182] 7.2 Protocol States

[0183] RRC supports the following states which can be characterised as follows:

[0184] RRC INACTIVE:

[0185] PLMN selection;

[0186] Broadcast of system information;

[0187] Cell re-selection mobility; Paging is initiated by NG-RAN (RAN paging) ; RAN-based notification area (RNA) is managed by NG- RAN;

[0188] DRX for RAN paging configured by NG-RAN;

[0189] 5GC - NG-RAN connection (both C / U-planes) is established for UE;

[0190] The UE Inactive AS context is stored in NG- RAN and the UE;

[0191] NG-RAN knows the RNA which the UE belongs to ;

[0192] Transfer of MBS broadcast data to the UE over MRB ( s ) ;

[0193] Transfer of unicast data and / or signalling to / from the UE over radio bearers configured for SDT.

[0194] Further measurements are performed also in inactive state :

[0195] 7.3 System Information Handling

[0196] 7.3.1 Overview

[0197] System Information (SI) consists of a MIB and a number of STBs, which are divided into Minimum SI and Other SI:

[0198] Other SI encompasses all STBs not broadcast in the Minimum SI. Those STBs can either be periodically broadcast on DL-SCH, broadcast on-demand on DL-SCH (i.e. upon request from UEs in RRC_IDLE, RRC_INACTIVE, or RRCJSONNECTED) . Other SI consists of:

[0199] SIB4 contains information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection (including cell reselection parameters common for a frequency as well as cell specific re-selection parameters) , which can also be used for NR idle / inactive measurements; SIB11 contains information related to idle / inactive measurements.

[0200] 8.1 UE Identities

[0201] In this clause, the identities used by NR connected to 5GC are listed.

[0202] For NR connected to 5GC, the following UE identity is used at NG-RAN level:

[0203] I-RNTI: used to identify the UE context in

[0204] RRC INACTIVE.

[0205] 9.2.2 Mobility in RRC_INACTIVE

[0206] 9.2.2.1 Overview

[0207] RRC_INACTIVE is a state where a UE remains in CM- CONNECTED and can move within an area configured by NG- RAN (the RNA) without notifying NG-RAN. In RRC_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving AMF and UPF.

[0208] If the last serving gNB receives DL data from the UPF or DL UE-associated signalling from the AMF (except the UE Context Release Command message) while the UE is in RRC_INACTIVE, it pages in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s) .

[0209] A UE in the RRC_INACTIVE state is required to initiate RNA update procedure when it moves out of the configured RNA. When receiving RNA update request from the UE, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may decide to send the UE back to RRC_INACTIVE state, move the UE into RRCjCONNECTED state, or send the UE to RRC_IDLE. In case of periodic RNA update, if the last serving gNB decides not to relocate the UE context, it fails the Retrieve UE Context procedure and sends the UE back to RRC_INACTIVE, or to RRC_IDLE directly by an encapsulated RRCRelease message.

[0210] 9.2.2.3 RAN-Based Notification Area

[0211] A UE in the RRC_INACTIVE state can be configured by the last serving NG-RAN node with an RNA, where: the RNA can cover a single or multiple cells, and shall be contained within the CN registration area; in this release Xn connectivity should be available within the RNA; a RAN-based notification area update (RNAU) is periodically sent by the UE and is also sent when the cell reselection procedure of the UE selects a cell that does not belong to the configured RNA.

[0212] There are several different alternatives on how the RNA can be configured:

[0213] List of cells:

[0214] A UE is provided an explicit list of cells (one or more) that constitute the RNA.

[0215] List of RAN areas:

[0216] A UE is provided (at least one) RAN area ID, where a RAN area is a subset of a CN Tracking Area or equal to a CN Tracking Area. A RAN area is specified by one RAN area ID, which consists of a TAG and optionally a RAN area Code;

[0217] A cell broadcasts one or, in case of network sharing with multiple cell ID broadcast, more RAN area IDs in the system information.

[0218] NG-RAN may provide different RNA definitions to different UEs but not mix different definitions to the same UE at the same time. UE shall support all RNA configuration options listed above. 9.2.2.4 State Transitions

[0219] 9.2.2.4.2 Network triggered transition from RRC_ INACTIVE to RRC_CONNECTED

[0220] Figure 10 (network triggered transition from RRC_INACTIVE to RRC_CONNECTED) describes the network triggered transition from RRC_INACTIVE to RRC_CONNECTED :

[0221] 1. A RAN paging trigger event occurs (incoming DL user plane, DL signalling from 5GC, etc.) .

[0222] 2. RAN paging is triggered; either only in the cells controlled by the last serving gNB or also by means of Xn RAN Paging in cells controlled by other gNBs, configured to the UE in the RAN-based Notification Area (RNA) .

[0223] 3. The UE is paged with the I-RNTI.

[0224] 4. If the UE has been successfully reached, it attempts to resume from RRC_INACTIVE, as described in clause 9.2.2.4.1.

[0225] A UE is thus paged first by the last serving gNB. If the UE is no longer accessible via the last serving gNB, e.g. due to movement, different options for further paging might be possible, e.g. page all cells of the RNA in parallel to reach the UE fast, page the UE with a cell of the RNA and if not successful try next cell of RNA. It may take some time till the UE is reached, and may be reached only via a cell which has certain access conditions, e.g. low signal strength, which may require a quick subsequent handover to a better suited cell, which required additional signaling, delay, etc. An improvement is looked for to access the UE faster and better. In case the last serving cell stores the latest measurements, e.g. L3 measurements and / or LI measurements, e.g. provided by a distributed unit, e.g. when configured with LTM, then these measurements may also indicate identified measured cells and their signal strengths. This way a priority for selecting cells for sending the paging signals could be defined, e.g. the last serving cell first, and then the cell with the highest signal strength, and then the cell with the second highest signal strength, and so on. This way, the probability to find and access the UE fast is increased. E.g. due to the movement of the UE, the UE may no longer be reachable via the last serving cell, but is still in the neighborhood, and thus is reachable with a high probability via one of the cells identified in the latest measurements. Not only a fast access is more probable, but also an access with good connection conditions. This reduces the risk for a fast subsequent handover requirement. The latest UE measurements may be provided to the last serving cell or another cell together with RNA update. Alternatively, or in addition, the latest UE measurements may be provided to the last serving cell or another cell together with a general resume request and / or with an SDT request, e.g. : The UE in RRC Inactive sends RRCResumeRequest message together with UL SDT data and / or UL SDT signalling and / or latest / available / actual measurement information. The measurement information may include: LI measurement info including e.g. cell IDs and related signal-to-strength measurements values, or e.g. PCIs (or other cell IDs) of the prepared cells instead of the LI measurements.

[0226] The UE is e.g. configured and operates in LTM. The CU decides to switch UE to Inactive state and provides an RRC Suspend message to the respective DU, and informs the DU about the content of the message and requests the LI measurements, e.g. for a specific amount of time. DU provides the message RRC suspend to the UE, and provides respective LI measurements to the CU, e.g. for the requested amount of time, or just once, e.g. the latest LI measurements received from the UE . The DU then releases the UE context and the LTM configuration. The CU stores the received LI measurements. Or at least the cell IDs or PCIs.

[0227] When DL data come to the (anchor) CU the latter identifies the proper cells to be paged (e.g., last cells available in the LI measurement report) . The identified cells could be pages all together at once, thus increasing the chances to find and connect the UE . Or a priority can be configured, e.g. according to the last signal strengths. E.g. the CU stores the cells according to their strengths and thus reduces the amount of storage and configures the order of access.

[0228] The measurement information may alternatively or in addition include: L3 measurement info including e.g. cell IDs and related signal-to-strength measurements values, or e.g. PCIs (or other cell IDs) of the measured cells instead of the complete L3 measurement infos. The CU may store measurement info (e.g. prepared cell IDs in case of configuring LTM based on L3 measurements and / or LI measurement info received from a DU or another CU) and use this info for paging in case of UE in inactive state .

[0229] The CU may also use measurement info to create an RNA. An RNA may be created using the cell ID of the (last) serving cell and its surrounding cells, e.g. known based on topology, or else. These cells however may not necessarily include the measured cells. If the measured cells are added to the RNA, this would ease the selection of cells for paging and the order of selection, thus enabling faster and better access to the UE .

[0230] 9.2.2.5 RNA update Figure 11 (RNA update procedure with UE context relocation) describes the UE triggered RNA update procedure involving context retrieval over Xn. The procedure may be triggered when the UE moves out of the configured RNA, or periodically.

[0231] 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update, and optionally with the latest measurement information, e.g. LI measurements and / or cell IDs, and / or PCI. This enables the gNB, e.g. CU or CU-CP., to use this information to better page the UE in case it remains in inactive mode, and e.g. later on DL data is coming in for the UE .

[0232] 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1.

[0233] 3. The last serving gNB may provide the UE context and optionally stored measurement info of the UE (as assumed in the following) . Alternatively, the last serving gNB may decide to move the UE to RRC_IDLE (and the procedure follows steps 3 and later of figure 9.2.2.5-3) or, if the UE is still within the previously configured RNA, to keep the UE context in the last serving gNB and to keep the UE in RRC_INACTIVE (and the procedure follows steps 3 and later of figure 9.2.2.5- 2) . This enables the gNB, e.g. CU or CU-CP., to use this information to better page the UE in case it remains in inactive mode, and e.g. later on DL data is coming in for the UE .

[0234] 4. The gNB may move the UE to RRC_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1 ) , or send the UE back to RRC IDLE (in which case an RRCRelease message is sent by the gNB) , or send the UE back to RRC_INACTIVE as assumed in the following.

[0235] 5. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses.

[0236] 6. / 7. The gNB performs path switch.

[0237] 8. The gNB keeps the UE in RRC_INACTIVE state by sending RRCRelease with suspend indication.

[0238] 9. The gNB triggers the release of the UE resources at the last serving gNB.

[0239] Figure 12 (periodic RNA update procedure without UE context relocation) describes the RNA update procedure for the case when the UE is still within the configured RNA and the last serving gNB decides not to relocate the UE context and to keep the UE in RRC_INACTIVE :

[0240] 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB and appropriate cause value, e.g., RAN notification area update, and optionally with the latest measurement information, e.g. LI measurements and / or cell IDs, and / or PCI. This enables the gNB, e.g. CU or CU-CP., to use this information to better page the UE in case it remains in inactive mode, and e.g. later on DL data is coming in for the UE .

[0241] 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context, providing the cause value received in step 1.

[0242] 3. The last serving gNB stores received information to be used in the next resume attempt (e.g. C-RNTI and PCI related to the resumption cell) , and responds to the gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The RRCRelease message includes Suspend Indication.

[0243] 4. The gNB forwards the RRCRelease message to the UE.

[0244] 9.2.4 Measurements

[0245] In RRC_CONNECTED, the UE measures multiple beams (at least one) of a cell and the measurements results (power values) are averaged to derive the cell quality. In doing so, the UE is configured to consider a subset of the detected beams. Filtering takes place at two different levels: at the physical layer to derive beam quality and then at RRC level to derive cell quality from multiple beams. Cell quality from beam measurements is derived in the same way for the serving cell (s) and for the non-serving cell (s) . Measurement reports may contain the measurement results of the X best beams if the UE is configured to do so by the gNB .

[0246] Network may request the UE to measure NR and / or E- UTRA carriers in RRC_IDLE or RRC_INACTIVE via system information or via dedicated measurement configuration in RRCRelease . If the UE was configured to perform measurements of NR and / or E-UTRA carriers while in RRC_IDLE or in RRC_INACTIVE, it may provide an indication of the availability of corresponding measurement results to the gNB in the RRCSetupComplete message. The network may request the UE to report those measurements after security activation. The request for the measurements can be sent by the network immediately after transmitting the Security Mode Command (i.e. before the reception of the Security Mode Complete from the UE) .

[0247] If the UE was configured to perform measurements of NR and / or E-UTRA carriers while in RRC_INACTIVE, the gNB can request the UE to provide corresponding measurement results in the RRCResume message and then the UE can include the available measurement results in the RRCResume Compl ete message . Alternatively, the UE may provide an indication of the availability of the measurement results to the gNB in the RRCResume Compl ete message and the gNB can then request the UE to provide these measurement results .

[0248] The UE may be pre-configured, or configured by the network, to stored available LI and / or L3 measurements in case of reception of an RRC suspend message to change state of UE to inactive . And to include information related to the stored LI and / or L3 measurements in an RRC resume request message when providing RNA update to the network, and / or when sending UL SDT data and / or UL SDT signalling . The UE may be pre-configured, or configured by the network, to perform LI and / or L3 measurements when in inactive state . The LI measurements might be configured and / or applied when UE is configured with LTM, and then changes its state to inactive . And to include information related to the performed LI and / or L3 measurements in an RRC resume request message when providing RNA update to the network, and / or when sending UL SDT data and / or UL SDT signalling .

[0249] The following shows a 3GPP TS38 . 300 V17 . 3 . 0 ( 2022— 12 ) sections with amendments :

[0250] 8 . 18 Overall procedure for Small Data Transmission during RRC Inactive

[0251] 8 . 18 . 1 RACH based SDT

[0252] The procedure for RACH based small data transmission in RRC Inactive is shown in Figure 13 (RACH based Small Data Transmission in RRC Inactive state ) . 1. The UE in RRC Inactive sends RRCResume Re quest message together with UL SDT data and / or UL SDT signalling, and / or optionally with the latest measurement information, e.g. LI measurements and / or cell IDs, and / or PCI. This enables the gNB, e.g. CU or CU-CP., to use this information to better page the UE in case it remains in inactive mode, and e.g. later on DL data is coming in for the UE .

[0253] 2. The gNB-DU buffers the UL SDT data and / or UL SDT signalling, and / or optionally at least part of the received measurement information.

[0254] 3. The step 3 is as defined in step 4 in clause 8.6.2, with including an indication of SDT access. The gNB-DU may also provide SDT assistance information and / or optionally at least part of the received measurement information.

[0255] 4-5. The steps 4-5 are as defined in steps 6-7 in clause 8.9.6.2. The UL SDT data, if any, is forwarded to the gNB-CU-UP, and the UL signalling, if any, is forwarded to the gNB-CU-CP via the UL RRC MESSAGE TRANSFER message, in which any UL NAS PDU is delivered to AMF.

[0256] 8.6 RRC state transition

[0257] 8.6.1 RRC connected to RRC inactive

[0258] This section gives the RRC connected to RRC inactive state transition given that gNB consists of gNB-CU and gNB-DU (s) , as shown in Figure 14 (RRC connected to RRC inactive state transition procedure) .

[0259] 0. At first, the gNB-CU determines the UE to enter into RRC inactive mode from connected mode.

[0260] 1. The gNB-CU generates RRCRelease message which includes suspend configuration towards UE . The RRC message is encapsulated in UE CONTEXT RELEASE COMMAND message to the gNB-DU. The UE CONTEXT RELEASE COMMAND further optionally includes a request to the gNB-DU to provide latest LI measurements received from the UE or related info, e.g. in case DU has previously been configured with LTM. The UE CONTEXT RELEASE COMMAND may further include information to enable the DU to wait for or request the next LI measurements from the UE before forwarding the RRCRelease to the UE and to enable sending actual / the very latest measurements to the CU. The UE CONTEXT RELEASE COMMAND may further include information to enable the DU not to forward the RRCRelease to the UE in case a LI trigger cell change is expected. The cell change and the inactive state are concurrent procedures. The inactive state is e.g. used in case of no data incoming and thus enabling UE e.g. to save power, but it might be better for the UE to keep a good connection. Thus, if cell change is planed / expected / due, then cell change might get higher priority and be performed. In this case DU will inform CU that cell change has been performed, and not change ot inactive state. DU may e.g. provides to CU in addition the latest measurements to be forwarded to the new CU the UE has connected to. The new CU may then perform change to inactive state. When new CU informs CU about handover success, CU may also inform new CU about condition fulfilled for change to inactive state .

[0261] 2. The gNB-DU forwards RRCRelease message to UE .

[0262] 3. The gNB-DU responds with UE CONTEXT RELEASE COMPLETE message. The UE CONTEXT RELEASE COMPLETE message may include the requested LI measurement info.

[0263] The following shows a 3GPP TS38.331 V17.3.0 (2022—

[0264] 12) sections with amendments: 4.2.1UE states and state transitions including inter RAT

[0265] A UE is either in RRC_CONNECTED state or in RRC_INACTIVE state when an RRC connection has been established .

[0266] RRC_INACTIVE :

[0267] A UE specific DRX may be configured by upper layers or by RRC layer;

[0268] At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast;

[0269] UE controlled mobility based on network configuration;

[0270] The UE stores the UE Inactive AS context;

[0271] A RAN-based notification area is configured by RRC layer;

[0272] Transfer of unicast data and / or signalling to / from UE over radio bearers configured for SDT and optionally transmits available measurement info therewith, e.g. based on (pre-) configuration . The UE:

[0273] Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5) ;

[0274] During SDT procedure, monitors control channels associated with the shared data channel to determine if data is scheduled for it;

[0275] While SDT procedure is not ongoing, monitors a Paging channel for CN paging using 5G- S-TMSI and RAN paging using fullI-RNTI, except if the UE is acting as a L2 U2N Remote UE;

[0276] If configured by upper layers for MBS multicast reception, while SDT procedure is not ongoing, monitors a Paging channel for paging using TMGI; Performs neighbouring cell measurements and cell ( re- ) selection;

[0277] Performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area and optionally transmits available measurement info therewith, e.g. based on (pre- ) conf iguration;

[0278] Acquires system information, while SDT procedure is not ongoing, and can send SI request (if configured) ;

[0279] While SDT procedure is not ongoing, performs logging of available measurements together with location and time for logged measurement configured UEs;

[0280] While SDT procedure is not ongoing, performs idle / inactive measurements for idle / inactive measurement configured UEs;

[0281] If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data;

[0282] Transmits SRS for Positioning.

[0283] Further features of the methods directly result from the functionality of DU(s) , CU(s) , or UE, as described throughout the description, claims, and drawings, and are therefore not repeated here. An apparatus may be configured to perform or cause performance of any aspect of the method (s) described herein. Further, a computer program or a computer program product may comprise instructions for causing, when executed by an apparatus, the apparatus to perform any aspect of the method (s) described herein. Further, an apparatus may comprise means for performing any aspect of the method ( s ) described herein . According to an example embodiment , the means comprises at least one processor ; and at least one memory storing instructions that , when executed by the at least one processor, cause the apparatus at least to perform any aspect of the method ( s ) .

[0284] One or more of the examples and embodiments discussed above may enable a solution in which more ef ficient paging may be provided . This may be achieved, for example , due to the fact that there is no need to page the whole RNA in order to identity the UE . Further, one or more of the examples and embodiments discussed above may enable a solution in which most likely location of the UE can be paged .

[0285] Any range or device value given herein may be extended or altered without losing the ef fect sought . Also , any embodiment may be combined with another embodiment unless explicitly disallowed .

[0286] Although the subj ect matter has been described in language speci fic to structural features and / or acts , it is to be understood that the subj ect matter defined in the appended claims is not necessarily limited to the speci fic features or acts described above . Rather, the speci fic features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims .

[0287] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments . The embodiments are not limited to those that solve any or all of the stated problems or those that have any or al l of the stated benefits and advantages . It will further be understood that reference to 'an' item may refer to one or more of those items.

[0288] The steps or operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the example embodiments described above may be combined with aspects of any of the other example embodiments described to form further example embodiments without losing the effect sought.

[0289] The term 'comprising' is used herein to mean including the method, blocks, or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

[0290] As used herein, "at least one of the following: " and "at least one of " and similar wording, where the list of two or more elements are joined by "and" or "or", mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements .

[0291] Although subjects may be referred to as 'first' or 'second' subjects, this does not necessarily indicate any order or importance of the subjects. Instead, such attributes may be used solely for the purpose of making a difference between subjects.

[0292] As used in this application, the term 'circuitry' may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable) : (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and (ii) any portions of hardware processor (s) with software (including digital signal processor ( s ) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) hardware circuit (s) and or processor ( s ) , such as a microprocessor ( s ) or a portion of a microprocessor ( s ) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims.

[0293] As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0294] It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from scope of this speci fication .

Claims

CLAIMS1 . A first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, comprising : at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the first network node to at least to : establish a connection towards a user equipment ; and receive information related to layer 1 measurements performed by the user equipment .2 . The first network node according to claim 1 , wherein the information related to the layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .3 . The first network node according to claim 1 or 2 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : transmit a message triggering provision of the information related to the layer 1 measurements .4 . The first network node according to any of claims 1 - 3 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : start a validity timer for the layer 1 measurements .5 . The first network node according to any of claims 1 - 4 , wherein the layer 1 measurements comprises layer 1 measurements received from a source network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of the radio access network and from a target network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of the radio access network .6 . The first network node according to claim 1 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : receive the layer 1 measurements with a retrieve UE context response message from a source network node that supports at least one of central unit control plane , UUCP, functionality or a layer 3 protocol of the radio access network .7 . The first network node according to claim 6 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : receive layer 3 measurements associated with the user equipment with a RAN noti fication area update message .8 . The first network node according to any one of claims 1 - 7 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : receive incoming traf fic for the user equipment ; and page the user equipment according to a paging scheme associated with the layer 1 measurements .9 . The first network node according to claim 8 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : page the last serving cell of the user equipment and cells indicated in a configurable number of last measurements .10 . The first network node according to claim 8 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : identi fy a mobility pattern of the user equipment ; and page cells associated with the mobility pattern .11 . The first network node according to claim 8 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : page the last serving cell of the user equipment and a subset of cells indicated in the layer 1 measurements .12 . The first network node according to any one of claims 9 - 11 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : select a set of beams for each identi fied cell based on the layer 1 measurements .13 . The first network node according to claim 1 or 2 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform :transmit the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network .14 . A second network node that supports at least one of distributed unit , DU, functionality or a layer 2 protocol of a radio access network, comprising : at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the second network node at least to : establish a connection towards a user equipment ; receive , from a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment ; and transmit , towards the first network node , information related to received layer 1 measurements .15 . The second network node according to claim 14 , wherein the information related to the received layer 1 measurements includes an associated time window indicating validity of provided measurement results , and / or a related validity timer, and / or related timing information .16 . The second network node according to claim 14 or 15 , wherein the instructions , when executed by the atleast one processor, cause the second network node to perform : receive a radio resource control , RRC, release message from the first network node to be forwarded to the user equipment to instruct the user equipment to operate in an inactive state , wherein together with the RRC release message a request for providing information related to the layer 1 measurement is received .17 . The second network node according to claim 14 or 15 , wherein the instructions , when executed by the at least one processor, cause the second network node to perform : transmit an LTM cell change trigger message towards the user equipment ; and transmit a message towards the first network node indicating the triggered LTM cell change and including the information related to the layer 1 measurements .18 . A first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network, comprising : at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the first network node to at least to : transmit layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM .19 . The first network node according to claim 18 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform :transmit the layer 1 measurements with a retrieve UE context response message to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network .20 . The first network node according to claim 18 , wherein the instructions , when executed by the at least one processor, cause the first network node to perform : transmit the layer 1 measurements to a target network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of the radio access network in response to receiving a handover success message .21 . A user equipment for operating in an inactive state , the user equipment comprising : at least one processor ; and at least one memory storing instructions which, when executed by the at least one processor, cause the user equipment at least to : establish a connection towards a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network; receive , from the first network node , a message including an instruction to operate in the inactive state ; and transmit , when operating in the inactive state , a radio resource control , RRC, resume request message including information related to at least one measurement performed by the user equipment .22 . The user equipment of claim 21 , wherein the information is related to layer 1 and / or layer 3 measurements performed by the user equipment .23 . A method performed by a first network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of a radio access network, the method comprising : establishing a connection towards a user equipment ; and receiving information related to layer 1 measurements performed by the user equipment .24 . A method performed by a second network node that supports at least one of the distributed unit , DU, functionality or a layer 2 protocol of a radio access network, the method comprising : establishing a connection towards a user equipment ; receiving, from a first network node that supports at least one of central unit control plane , CU-CP , functionality or a layer 3 protocol of a radio access network, a layer 1 / layer 2 triggered mobility, LTM, configuration message instructing the second network node to operate in LTM and to monitor layer 1 measurements performed by and received from the user equipment ; and transmitting, towards the first network node , information related to received layer 1 measurements .25 . A method performed by a first network node that supports at least one of central unit control plane , CU- CP, functionality or a layer 3 protocol of a radio access network, the method comprising :transmitting layer 1 measurements associated with a user equipment operating in layer 1 / layer 2 triggered mobility, LTM .26 . A method for operating a user equipment operating in an inactive state , the method comprising : establishing a connection towards a first network node that supports at least one of central unit control plane , CU-CP, functionality or a layer 3 protocol of a radio access network; receiving, from the first network node , a message including an instruction to operate in the inactive state ; and transmitting, when operating in the inactive state , a radio resource control , RRC, resume request message including information related to at least one measurement performed by the user equipment .27 . A computer program compri sing instructions for causing an apparatus to carry out the method of any of claims 23 - 26 .

Citation Information

Patent Citations

  • Uplink data fast transmission in CU-du split

    WO2020171369A1

  • Systems and methods for determining the validity of idle mode measurements

    WO2020176025A1