Slice-aware mobility decision based on throughput absorption capacity information

Abstract

Disclosed herein is an apparatus. The apparatus is configured to receive, from at least one of a gNodeB-Distributed Unit (gNB-DU) of a gNB or a gNodeB-Centralized Unit (gNB-CU) of one or more neighbouring gNBs, measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner. The apparatus is configured to receive, from the at least one of the gNB-DU of the gNB or the gNB-CU of the neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner. The apparatus is configured to determine whether to prepare one or more candidate cells for implementing one or more mobility solution mechanisms based on the received measured and predicted throughput absorption capacity information.

Description

SLICE-AWARE MOBILITY DECISION BASED ON THROUGHPUT ABSORPTIONCAPACITY INFORMATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to Indian Provisional Application No. 202411074367. filed on October 1, 2024. and Indian Non-Provisional Application No. 202411074367, filed on March 27, 2025, the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to a slice-aware mobility decision based on throughput absorption capacity infonnation.BACKGROUND

[0003] The information disclosed in this background section is only for an enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgment or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] Mobility or handover ensures seamless connectivity of an ongoing communication session of a User Equipment (UE) by transferring a session from one cell, i.e., a base station or a gNodeB (gNB) to another cell in a connected state while the UE is on the move.

[0005] Layerl / Layer 2 Triggered Mobility (LTM), introduced in Release-18 of Third Generation Partnership Project (3GPP), offers improvements in handover latency and interruption time compared to Layer 3-based mobility solutions. However, the initial implementation of the LTMintroduced in Release 18 has several limitations as compared to Layer 3-based mobility solutions. Currently, the ongoing 3GPP Release- 19 work item (WI) on mobility enhancements aims to remove a number of these limitations.SUMMARY

[0006] This summary is provided to introduce a selection of concepts, in a simplified format, that are further described in the detailed description of the disclosure. This summary is neither intended to identify key or essential inventive concepts of the present disclosure nor is it intended to determine the scope of the disclosure.

[0007] According to one embodiment of the present disclosure, an apparatus is disclosed. The UE is configured to receive measured throughput absorption capacity information corresponding to each of a plurality of slices wi thin each of a plurality of cells of a gNB or one or more neighbouring gNBs, in a periodic manner. The measured throughput absorption capacity information is received from at least one of a gNodeB-Distributed Unit (gNB-DU) of the gNB or a gNodeB -Centralized Unit (gNB-CU) of the one or more neighbouring gNBs. The measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR. The apparatus is also configured to receive predicted throughput absorption capacity information corresponding to each of the plurality7of slices w ithin each of the plurality7of cells in the periodic manner. The predicted throughput absorption capacity information is received from at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs. The predicted throughput absorption capacity information comprises a predicted UL GBR, a predicted UL non-GBR, a predicted DL GBR, and a predictedDL non-GBR for a time duration. Moreover, the apparatus is configured to determine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms. The determination is based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information.

[0008] According to another embodiment of the present disclosure, a method is disclosed. The method includes receiving, by a gNodeB-Centralized Unit (gNB-CU) of a gNB, measured throughput absorption capacity infomiation corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner. The measured throughput absorption capacity information is received from at least one of a gNodeB-Distributed Unit (gNB-DU) of the associated gNB or a gNB-CU of one or more neighbouring gNBs. The measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR. The method also includes receiving, by the gNB-CU of the first gNB, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner. The predicted throughput absorption capacity information is received from the at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs. The predicted throughput absorption capacity information comprises a predicted UL GBR, a predicted UL non-GBR, a predicted DL GBR, and a predicted DL non-GBR for a time duration. Moreover, the method includes determining, by the gNB-CU of the first gNB, whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms. The determination is based on the received measured throughputabsorption capacity information and the received predicted throughput absorption capacity information.

[0009] According to another embodiment of the present disclosure, a non-transitory computer- readable medium is disclosed. The non-transitory computer-readable medium stores instructions. The instructions comprise one or more instructions that are executed by agNodeB- Centralized Unit (gNB-CU) of a first gNB. The gNB-CU comprises one or more processors. The one or more instructions cause the one or more processors to receive measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality of cells of the first gNB or the one or more neighbouring gNBs in a periodic manner. The measured throughput absorption capacity information is received from at least one of a gNodeB-Distributed Unit (gNB-DU) of the gNB or a gNB-CU of the one or more neighbouring gNBs. The measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DU non-GBR. The one or more instructions also cause the one or more processors to receive predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner. The predicted throughput absorption capacity information is received from at least one of the gNB- DU of the gNB or the gNB-CU of the one or more neighbouring gNBs. The predicted throughput absorption capacity' information comprises a predicted UL GBR, a predicted UL non-GBR, a predicted DL GBR, and a predicted DL non-GBR for a time duration. Moreover, the one or more instructions also cause the one or more processors to determine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms. The determination is based on the received measured throughputabsorption capacity information and the received predicted throughput absorption capacity information.

[0010] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will be rendered by reference to specific embodiments thereof, which is illustrated in the appended drawing. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting its scope. The disclosure will be described and explained with additional specificity and detail with the accompanying drawings.BRIEF DESCRIPTION OF DRAWINGS

[0011] Features, aspects, and advantages of certain exemplary embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:FIG. 1 illustrates a disaggregated Next Generation Node B (gNB) architecture, according to the state of art;FIG. 2 illustrates a sequence flow diagram for a successful operation of a resource status reporting initiation over an Fl interface, in accordance with an embodiment of the present disclosure;FIG. 3 illustrates a sequence flow diagram for a successful operation of a resource status reporting over the Fl interface, in accordance with another embodiment of the present disclosure;FIG. 4 illustrates a sequence flow diagram for the successful operation of the resource status reporting initiation over an Xn interface, in accordance with an embodiment of the present disclosure;FIG. 5 illustrates a sequence flow diagram for the successful operation of the resource status reporting over the Xn interface, in accordance with an embodiment of the present disclosure;FIG. 6 illustrates a flowchart depicting a method for implementing a slice-aware mobility decision based on throughput absorption capacity information, in accordance with an embodiment of the present disclosure;FIG. 7 illustrates a flowchart depicting a method for determining whether to prepare one or more candidate cells for implementing one or more mobility solution mechanisms, in accordance with an embodiment of the present disclosure; andFIG. 8 illustrates an embodiment of an example device, in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0012] The following detailed description of example embodiments refers to the accompanying drawings. The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below7relate to one of the various embodiments. It should be noted that it is possible to make otherembodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0013] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0014] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every' other claim in the claim set.

[0015] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a'’ and "an" are intended to include one or more items, and may be used interchangeably with “one or more.'’ Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of[A] and [B],” “[A] and / or [B],” or£'at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0016] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0017] In the present disclosure, specific tasks may be performed using Artificial Intelligence / Machine Learning (AI / ML) models. An AI / ML model is a model generated using one or more Al technologies, one or more ML algorithms, or both, and generates output data based on input data. This output data is used to perform tasks. Tasks performed using AI / ML models include those generally referred to as intellectual tasks, such as classification, prediction, natural language processing, etc.

[0018] Although Al and ML are explained separately, ML is a technology included in Al. In ML, instead of being explicitly programmed for a specific task, systems can improve their performance over time by identifying patterns and making inferences from training data. Typically, the generation of ML models includes data collection, model training, and model inference. Data collection involves gathering and preprocessing data to be used for training and inference. Model training involves developing and validating models using the collected data. Model inference involves applying the trained models to new data to generate new output data and perform tasks.

[0019] Machine learning includes various types of learning methods such as supervised learning, unsupervised learning, reinforcement learning, semi-supervised learning, selfsupervised learning, transudative learning, transfer learning, meta learning, and the like. Thesetypes of learning methods can be appropriately selected according to the embodiments. Unless otherwise specified, the application of types not mentioned in this description is not precluded. Additionally, the structure of ML models may vary depending on the embodiments and learning methods, and is not limited to the methods disclosed. Furthermore, ML includes deep learning, which uses models that include neural networks. Deep learning models may include, for example, deep neural networks (DNNs). convolutional neural networks (CNNs), etc.

[0020] It should be noted that the AI / ML models presented hereinafter are examples and are not limited to the illustrated AI / ML models. They can be modified or altered by using different Al or ML algorithms. The configuration of the neural network is not limited to the configuration disclosed in the present disclosure and can be modified.

[0021] A Radio Access Network (RAN) is an important component in a telecommunications system and includes multiple network entities or network components that facilitate connections with end-user devices (User Equipment (UE)). In Third Generation Partnership Project (3GPP) Technical Specification Group (TSG) RAN Meeting #105, Release-19 study item in RP-24032, titled ‘‘SID on enhancements for AIML for NG-RAN'’ is converted to a work item RP-242385 with title “Enhancements for Artificial Intelligence (AI)ZMachine Learning (ML) for NG-RAN”. The converted work item aims to specify data collection enhancements and signaling support within existing Next Generation RAN (NG-RAN) interfaces and architecture (including non-split architecture and split architecture) for AI / ML- based Slicing and AI / ML based Coverage and Capacity Optimization (CCO) [RAN3], The work item further aims to incorporate support of leftovers in Rel-18 AI / ML for NG-RAN [RAN3], which includes Mobility7Optimization for New7Radio Dual Connectivity (NR-DC),split architecture support for Release-18 use cases, and continuous Minimizing Drive Test(MDT) collection targeting the same UE across Radio Resource Control (RRC) states.

[0022] Further, a measured / predicted shce-level radio resource status and a measured / predicted slice available capacity may be transferred between NG-RAN nodes to assist an AI / ML network slicing model. The AI / ML assisted network slicing model in an NG-RAN node may generate resource management within Radio Resource Management (RRM) policy (internal output), and slice-aware mobility decisions (internal output) as outputs.

[0023] The feedback collected for the NG-RAN nodes includes legacy UE performance feedback for UEs handed over from a source NG-RAN node.

[0024] Further, several agreements have been made in the RAN3. Particularly, in RAN3#124, in Rel-19, predicted information from a Core Network (CN) to the NG-RAN is not considered. Rel-19 agrees to improve granularity of UE performance feedback for slicing. For Further Study (FFS), Rel-19 discloses whether to include a measured / predicted UE throughput per slice as input from a local node or not. Additionally, FFS, Rel-19 discloses whether to introduce delivery' of a slice level UE throughput prediction / measurement during a handover (HO) procedure or not.

[0025] In RAN3#125, a slice UE performance needs to be introduced, while the granularity to support the slice UE performance may be further checked in the Work Item (WI) phase.

[0026] Further, Layerl / Layer2 (L1 / L2) triggered mobility (LTM) introduced in Rel-18 may offer improvements in handover latency and interruption time compared to Layer 3-based mobility solutions. However, the LTM as introduced in Rel-18 has several limitations as compared to the Layer 3-based mobility solutions.

[0027] A disaggregated architecture is defined in the 3GPP decomposing a Next GenerationNode B (gNB) into multiple logical entities. FIG. 1 illustrates the disaggregated architecture of a gNB 100. according to the state of the art. The multiple logical entities may include one or more first units 102 may be represented by at least one distributed unit (referred to as gNB-DU) and one or more second units 104 may be represented by a centralized unit (referred to as gNB- CU). The gNB-CU may be further split into a CU Control Plane (CP) part, also referred to as a gNB-CU-CP. and a CU User Plane (UP) part, also referred to as a gNB-CU-UP. Such a split enables the implementation of the CU-CP and CU-UP parts in different locations. For example, such a split of the gNB 100 into the plurality of logical entities enables flexibility, scalability, and efficiency in the deployment and operation of 5G networks. The disaggregated architecture of the gNB 100 may also include a Radio Unit (gNB-RU), not shown in FIG. 1.

[0028] The gNB-RU may be responsible for the radio transmission and reception of signals. The gNB-RU may include physical Radio Frequency (RF) components such as antennas, power amplifiers, and analog-to-digital converters. The gNB-RU may be located at a cell site or a radio tower, close to the antennas. Further, the gNB-DU may perform baseband processing functions such as physical layer processing, channel coding, and modulation / demodulation. For example, the gNB-DU may host a Radio Link Control (RLC), a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The gNB-DU may also perform scheduling operations. Multiple gNB-RUs may be connected to a single gNB-DU, allowing for centralized processing of multiple radio units. Multiple gNB-DUs may be connected to a single gNB-CU. The gNB-CU may be responsible for higher-layer processing functions such as radio resource management, mobility7management, and connection management. The gNB-CU may provide a centralized control point for multiple gNB-DUs, enabling network-wide coordination and optimization.

[0029] According to one configuration, the gNB-DU may host multiple cells (for example, a max of 512 as per cunent specifications). The gNB-CU-CP may host one or more gNB-DUs and one or more gNB-CU-UPs. Also, the gNB-CU-UP may host the Packet Data Convergence Protocol-User Plane part (PDCP-U) and Service Data Adaptation Protocols (SDAP). More specifically, 3GPP RAN3 cardinality for the 5G gNB defines that the gNB 100 may only include one gNB-CU-CP. There may be an "n” number of gNB-DUs controlled by a gNB-CU- CP. Further, there may be ‘m” number of gNB-CU-UP controlled by the gNB-CU-CP in the gNB 100. Also, one gNB-DU may be served by multiple gNB-CU-UP. The various entities and / or network functions within the gNB 100 may communicate via one or more interfaces including an Fl-C interface, an Fl-U interface, and an El interface. The Fl-C interface is a control plane interface between the gNB-CU and the gNB-DU within the gNB 100. The Fl-C interface is used for signaling and control messages related to radio resource management, mobility management, and configuration management. The Fl-C interface facilitates coordination between the gNB-CU and the gNB-DU for efficient network operation and service delivery'. The Fl-U interface is a user plane interface between the gNB-CU and the gNB-DU in the gNB 100 architecture. The Fl-U interface is responsible for transporting user data packets between the gNB-CU and the gNB-DU. The Fl-U interface handles user plane data processing, including packet forw arding, Quality of Service (QoS) management, and encryption / decryption functions. The El interface in the gNB 100 connects the gNB-CU-CP entity w ith the gNB-CU- UP.

[0030] In Rel-18, the LTM is limited to intra-CU mobility. The data scheduling operations generally take place at the gNB-DU. However, in order to support L1 / L2 centric inter-cell change (i.e. change of serving cell) in the disaggregated architecture of the gNB 100, the HOpreparation phase i.e., providing the candidate / target cell configuration to the UE is performed by the gNB-CU-CP. that is autonomously executed by the gNB-DU without requiring further interaction with the upper layers in the gNB-CU-CP.

[0031] However, there is a need for Handover (HO) preparation that takes place at the gNB- CU-CP, but is executed autonomously by the gNB-DU, without further interaction with the upper layers.

[0032] The LTM is a procedure in which a gNB receives LI measurement report(s) from a UE. and on the basis of the received LI measurement report(s), the gNB may change a UE serving cell by a cell switch command signalled via a Medium Access Control (MAC) Control Element (CE). The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through RRC signalling. Then, the UE switches to a target configuration according to the cell switch command. The LTM procedure can be used to reduce mobility latency.

[0033] Further, the LTM supports both an intra-gNB-DU and an inter-gNB-DU mobility' within the same gNB-CU. The LTM also supports both intra-frequency and inter-frequency mobility, including mobility to an inter-frequency cell that is not a current serving cell. The LTM is supported only for licensed spectrum. Particularly, the LTM supports a Primary' Cell (PCell) change in a non-Carrier Aggregation (non-CA) scenario and a non-Dual Connectivity (nonDC) scenario. The LTM also supports PCell and Secondary' Cells (SCell(s)) change in a Carrier Aggregation (CA) scenario. Additionally, the LTM supports a dual connectivity' scenario, including the PCell and Master Cell Group (MCG) SCell(s) change, and intra-Subscription Network (intra-SN) Primary Serving Cell (PSCell) and Secondary' Cell Group (SCG) SCell(s)change without a Mobility Network (MN) involvement. However, the LTM for simultaneousPCell and PSCell change is not supported.

[0034] While the UE has stored all configured LTM candidate configurations, the UE may also execute any L3 handover except for Dual Active Protocol Stack (DAPS) handover (HO). In the Radio Resource Control (RRC) message which the UE applies for any L3 handover (except the DAPS HO), the LTM candidate configurations may be added / modified / released by a target cell.

[0035] Further, as defined in Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.300, a Conditional Handover (CHO) is a handover that is executed by the UE when one or more handover execution conditions are met. The UE is configured with one or more CHO candidate cells and starts evaluating the execution condition(s) upon receiving a CHO configuration. The UE stops evaluating the execution condition(s) once a handover is executed.

[0036] The CHO configuration contains the configuration of CHO candidate cell(s) generated by candidate gNB(s) and the execution condition(s) generated by a source gNB. An execution condition may include one or two trigger condition(s) (CHO events A3 / A5). Further, only a single Reference Signal (RS) type is supported and at most two different trigger quantities (e.g., Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ), RSRP and Signal-to-Interference-plus-Noise Ratio (SINR), etc.) can be configured simultaneously for an evaluation of the CHO execution condition of a single candidate cell. Furthermore, before any CHO execution condition is satisfied, upon reception of a Handover (HO) command (without the CHO configuration) or an LTM cell switch command MAC CE, the UE executes the HO procedure as described in clause 9.2.3.2 of the TS or an LTM cell switch procedure as described in clause 9.2.3.5 of the TS, regardless of any previously receivedCHO configuration. Moreover, while executing the CHO, i.e. from the time when the UE starts synchronization with the target cell, the UE does not monitor the source cell.

[0037] TS 38.473 and TS 38.423 (specifications related to Fl and Xn) define ‘‘RESOURCE STATUS UPDATE’7procedure which can be configured for periodic information reporting either between CU-DU over the Fl interface or any two neighbouring NG-RAN nodes over an Xn interface, respectively. This information may be used by consumer nodes in their Radio Resource Management (RRM) algorithms.

[0038] Information Elements (IES) associated with a “RESOURCE STATUS UPDATE” message sent from the gNB-DU to the gNB-CU over the Fl interface, as defined in TS 38.473. are provided in Table (1) below.Table 1

[0039] Similarly, IES associated with the “RESOURCE STATUS UPDATE” message sent from one NG-RAN node (NG-RAN node2) to another NG-RAN node (NG-RAN nodei) over the Xn interface to report results of requested measurements, as defined in TS 38.423, are provided in Table (2) below.Table 2

[0040] The basic principles associated with mobility solutions such as the CHO and the LTM include the following:One or more candidate cells are prepared in advance and the candidate cell configuration is sent to the UE;• The HO is executed based on an UE-based approach (execution criteria like in the CHO and Conditional-LTM (C-LTM)) or network based approach (the LTM cell switch command sent by the gNB-DU to the UE); and• There could be an unpredictable "‘lead time” i.e., a time duration between the candidate cell preparation and the HO execution.

[0041] Based on the RAN3 agreements in the AI / ML based network slicing, there are some FFS regarding the UE throughput to enable ‘'Slice-aware mobility decisions”. The FFS may be whether to include the measured / predicted UE throughput per slice as input from the local node or not, and whether to introduce delivery of the slice level UE throughput prediction / measurement during the handover procedure.

[0042] In view of the above, it is observed that the current available periodic information reporting over the Fl / Xn interface includes only relative information about resources and no absolute values. Hence, the objective of the AI / ML based network slicing (i.e., slice-aware mobility decisions) cannot be met using the relative information. Therefore, RAN3 is considered per UE traffic information and / or per UE throughput information (measured / predicted) to be exchanged over the Fl / Xn interface.

[0043] Further, the measured / predicted UE traffic / throughput per slice is considered as a potential input for making the slice-aware mobility decisions. However, there is no consensus to exchange the measured or predicted UE traffic / throughput between neighbouring gNBs, as it may not be feasible to predict the UE traffic / throughput in a serving gNB.

[0044] In addition, even if the measured UE traffic / throughput is exchanged over the Xn / Fl interfaces, the measured UR traffic / throughput may not remain valid in case of the CHO, the LTM, or the C-LTM as the lead time between the candidate cell preparation and the HO execution may be large and unpredictable.

[0045] Lastly, including the measured / predicted UE traffic / throughput per slice in the HO request may be useful, however, such inclusion is reactive in nature (i.e., it is not preventive in nature).

[0046] Thus, a proactive mechanism is required for advanced mobility solutions like the LTM and the CHO, to prevent a source gNB from sending the HO requests to gNBs / gNB-DUs. Particularly, to prevent the Ho requests to gNB / gNB-DUs which are not able to admit the UE and all of its Protocol Data Unit (PDU) sessions and Data Radio Bearers (DRBs). For example, the measured / predicted UE throughput per slice infonnation may only be used to reject a request from a target node after the HO request is sent. However, the measured / predicted UE throughput per slice information may not be used to prevent the HO request from being sent to the target node.

[0047] Therefore, it is desired to provide a proactive solution to prevent unnecessary' HO requests and implement efficient preparation of candidate cells for the CHO, the LTM, and the C-LTM.

[0048] The present disclosure provides a solution to the above-mentioned problem(s). Particularly, the present disclosure provides a technique for implementing a slice-aware mobility decision based on throughput absorption capacity information. For this, the present disclosure proposes to periodically exchange an absolute measure of resource availability between any two NG-RAN nodes directly connected by the Xn interface or between a gNB-CU of any NG-RAN node (i.e., gNB) and an associated gNB-DU connected to the gNB-CU over the Fl interface. The periodic exchange of the absolute measure of resource availability may be at a slice and a cell level instead of per-UE level.

[0049] Particularly, the present disclosure proposes to include the following information in the IES exchanged over the Fl interface for Intra-gNB CHO, the LTM, and the C-LTM, as well as over the Xn interface for Inter-gNB CHO. the LTM, and the C-LTM:• a measured throughput absorption capacity information per slice per cell; and• a predicted throughput absorption capacity information per slice per cell.

[0050] In an embodiment, the measured throughput absorption capacity information may refer to a measure of a bitrate capacity that the NG-RAN node is able to admit and serve at a given time instance. The measured throughput absorption capacity information may include a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR. The GBR may refer to a specific minimum data rate guaranteed to be delivered by a network for a particular service or user. The measured UL GBR may refer to an actual uplink traffic being transmitted at the NG-RAN node at the given time instance for services with an allocated GBR. The measured UL non-GBR may refer to an actual uplink traffic being transmitted at the NG-RAN node at the given time instance for services that do not have the GBR. The measured DL GBR may refer to an actual downlink traffic being transmitted at the NG-RAN node at the given time instance for services with an allocated GBR. The measured DL non-GBR may refer to an actual downlink traffic being transmitted at the NG-RAN node at the given time instance for services that do not have theGBR.

[0051] In an embodiment, the predicted throughput absorption capacity information may refer to a measure of the bitrate capacity that the NG-RAN node may be able to admit and serve in a given future time instance or over a given future time interval. The predicted throughput absorption capacity information may include a predicted UL GBR. a predicted UL non-GBR. a predicted DL GBR. and a predicted DL non-GBR for a time duration. The predicted UL GBR may refer to an estimated uplink traffic rate that a service with the allocated GBR is expected to use in the given future time instance or over the given future time interval. The predicted UL non-GBR may refer to an estimated uplink traffic rate for services without the allocated GBR that is expected to occur in the given future time instance or over the given future time interval. The predicted DL GBR may refer to an estimated downlink traffic rate that a service with the allocated GBR is expected to use in the given future time instance or over the given future time interval. The predicted DL non-GBR may refer to an estimated downlink traffic rate for services without the allocated GBR that is expected to occur in the given future time instance or over the given future time interval.

[0052] In an embodiment, one or more predefined Al -ML models may be configured to predict the throughput absorption capacity information in a particular prediction window (i.e., time interval). The one or more predefined AI-ML models may also be configured to fine-tune the predicted throughput absorption capacity infonnation based on the measured throughput absorption capacity information during the prediction window.

[0053] In an embodiment, each of the NG-RAN nodes may be configured to determine whether to prepare the one or more candidate cells for implementing the one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity’ information. The one or more mobility'solution mechanisms may include the CHO, the LTM, the C-LTM, a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO). Additionally, each of the NG-RAN nodes may be configured to determine whether an admission of each of a plurality of Packet Data Unit (PDU) sessions and each of a plurality of Data Radio Bearers (DRBs) corresponding to each of a plurality of slices associated with the UE in the one or more candidate cells is possible.

[0054] In an embodiment, each of the NG-RAN nodes may also be configured to indicate the time interval for which the predicted throughput absorption capacity information is valid.

[0055] FIG. 2 illustrates a sequence flow diagram 200 for a successful operation of a resource status reporting initiation over the Fl interface, in accordance with an embodiment of the present disclosure. The sequence flow diagram 200 may illustrate a sequence of operations between a gNB-CU 202 of any NG-RAN node and an associated gNB-DU 204 over the Fl interface.

[0056] At step 206, the gNB-CU 202 may transmit a resource status request message to the associated gNB-DU 204 over the Fl interface. The resource status request message may be transmitted by the gNB-CU 202 to request information about the status of available network resources at the corresponding NG-RAN node.

[0057] At step 208, the gNB-DU 204 may transmit a resource status response message to the gNB-CU 202 over the Fl interface. The resource status response message may include request information about the status of the available network resources at the corresponding NG-RAN node.

[0058] FIG. 3 illustrates a sequence flow diagram 300 for a successful operation of a resource status reporting over the Fl interface, in accordance with an embodiment of the presentdisclosure. The sequence flow diagram 300 may illustrate a sequence of operations between the gNB-CU 202 and the gNB-DU 204 over the Fl interface.

[0059] At step 302, the gNB-DU 204 may transmit a resource status update message to the gNB-CU 202 over the Fl interface. The resource status update message may include the measured absorption throughput capacity information and the predicted absorption throughput capacity information.

[0060] FIG. 4 illustrates a sequence flow diagram 400 for the successful operation of the resource status reporting initiation over the Xn interface, in accordance with an embodiment of the present disclosure. The sequence flow diagram 400 may illustrate a sequence of operations between a first NG-RAN node (NG-RAN1) 402-1 and a second NG-RAN node (NG-RAN2) 402-2 over the Xn interface.

[0061] In an embodiment, the gNB-CU 202 and the gNB-DU 204 may be associated with the NG-RAN1 402-1. Additionally, the NG-RAN2 402-2 may also include a corresponding gNB- CU 404 and an associated gNB-DU 406.

[0062] At step 408, the NG-RAN1 402-1 (particularly, the gNB-CU 202) may transmit the resource status request message to the NG-RAN2 402-2 over the Xn interface. The resource status request message may be transmitted by the NG-RAN 1 402- 1 to request information about the status of available network resources at the NG-RAN2 402-2.

[0063] At step 410, the NG-RAN2 402-2 (particularly, the gNB-CU 404) may transmit the resource status response message to the NG-RAN1 402-1 over the Xn interface. The resource status response message may include request information about the status of the available network resources at the NG-RAN2 402-2.

[0064] FIG. 5 illustrates a sequence flow diagram 500 for a successful operation of the resource status reporting over the Xn interface, in accordance with an embodiment of the present disclosure. The sequence flow diagram 500 may illustrate a sequence of operations between the NG-RAN1 402-1 and the NG-RAN2 402-2 over the Xn interface.

[0065] At step 502, the NG-RAN2 402-2 (particularly, the gNB-CU 404) may transmit the resource status update message to the NG-RAN1 402-1 over the Xn interface. The resource status update message may include the measured absorption throughput capacity information and the predicted absorption throughput capacity information.

[0066] In an embodiment, the NG-RAN1 402-1 may be a serving gNB. therefore, may be referred to as gNB 402-1. Further, the NG-RAN2 402-2 may be a neighbouring gNB with respect to the NG-RAN1 402-1, therefore, may be referred to as neighbouring gNB 402-2. It should be noted that any number of neighbouring gNBs is possible.

[0067] FIG. 6 illustrates a flowchart depicting a method 600 for implementing the slice-aware mobility decision based on throughput absorption capacity information, in accordance with an embodiment of the present disclosure. The method 600 may be performed by the gNB-CU 202 of the NG-RAN1 402-1.

[0068] At step 602, the gNB-CU 202 of the gNB 402-1 may receive the measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality of cells of the gNB 402-1 or the one or more neighbouring gNBs 402-2 in a periodic manner. The measured throughput absorption capacity information may be received from at least one of the gNB-DU 204 of the associated gNB 402-1 or the gNB-CU 404 of one or more neighbouring gNBs 402-2. The measured throughput absorption capacity information mayinclude the measured UL GBR, the measured UL non-GBR, the measured DL GBR, and the measured DL non-GBR.

[0069] At step 604, the gNB-CU 202 of the gNB 402-1 may receive the predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner. The predicted throughput absorption capacity information may be received from the at least one of the gNB-DU 204 of the associated gNB 402-1 or the gNB-CU 404 of the one or more neighbouring gNBs 402-2. The predicted throughput absorption capacity’ information may include the predicted UL GBR, the predicted UL non-GBR, the predicted DL GBR, and the predicted DL non-GBR for a time duration.

[0070] At step 606, the gNB-CU 202 of the gNB 402-1 may determine whether to prepare one or more candidate cells among the plurality’ of cells for implementing one or more mobility solution mechanisms. The determination may be based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information. Thus, the present disclosure enables the implementation of proactive slice-aware mobility decisions.

[0071] In an embodiment, for determining whether to prepare the one or more candidate cells, the gNB-CU 202 of the gNB 402-1 may determine whether an admission of each of a plurality of Packet Data Unit (PDU) sessions in the one or more candidate cells is possible. The gNB- CU 202 may also determine whether an admission of each of a plurality of Data Radio Bearers (DRBs) in the one or more candidate cells is possible. The PDU sessions and the DRBs may correspond to each of the plurality’ of slices associated with a User Equipment (UE). Thus, the present disclosure helps in avoiding sub-optimal cells during the CHO or the LTM. Additionally, the present disclosure allows for latency and signaling savings.

[0072] In an embodiment, the gNB-CU 202 of the gNB 402-1 may receive an indication associated with the time duration for which the predicted throughput absorption capacity information is valid. Thereafter, the gNB-CU 202 of the gNB 402-1 may determine whether to prepare the one or more candidate cells among the plurality of cells for implementing the one or more mobility solution mechanisms. The determination may be based on the received measured throughput absorption capacity information, the received predicted throughput absorption capacity information, and the received time duration.

[0073] In an embodiment, the one or more mobility solution mechanisms may include one or more of the CHO, the LTM, the C-LTM, a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO).

[0074] In an embodiment, the measured throughput absorption capacity infonnation and the predicted throughput absorption capacity information may be received from the gNB-DU 204 of the associated gNB 402-1 via the Fl interface.

[0075] In an embodiment, the measured throughput absorption capacity and the predicted throughput absorption capacity' may be received from the gNB-CU 404 of the one or more neighbouring gNBs 402-2 via the Xn interface.

[0076] FIG. 7 illustrates a flowchart depicting a method 700 for determining whether to prepare the one or more candidate cells for implementing the one or more mobility solution mechanisms, in accordance with an embodiment of the present disclosure. The method 700 maybe performed by the gNB-CU 202 of the NG-RAN1 402-1.

[0077] At step 702, the gNB-CU 202 of the gNB 402-1 may receive the indication associated with the time duration for which the predicted throughput absorption capacity information is valid.

[0078] At step 704, the gNB-CU 202 of the gNB-402-1 may determine whether to prepare the one or more candidate cells among the plurality of cells for implementing the one or more mobility solution mechanisms. The determination may be based on the received measured throughput absorption capacity information, the received predicted throughput absorption capacity information, and the received time duration.

[0079] FIG. 8 illustrates an embodiment of a device / apparatus 800. As shown in FIG. 8. the device 800 includes a processor 810, a memory 820, a storage component 830. an input component 840, an output component 850, a communication interface 860, and a bus 870. The device 800 may be associated with the gNB-CU 202, the gNB-DU 204, the gNB-CU 404, and the gNB-DU 406. In one embodiment, the device 800 may correspond to the NG-RAN1 402-1 and the NG-RAN2 402-2. The one or more components of the device 800 may be configured to implement one or more operations / functionalities of the present disclosure as discussed above.

[0080] The processor 810, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 810 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 810 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another ty pe of processing component.

[0081] The memory7820 includes a non-transitory computer readable medium. The memory' 820 includes a random-access memory' (RAM), a read only memory' (ROM), and / or another ty pe of dynamic or static storage device (e.g., a flash memory', a magnetic memory', and / or anoptical memory) that stores information and / or instructions for use by the processor 810. The memory 820 comprises machine-readable instructions which are executable by the processor 810. These machine-readable instructions when executed by the processor 810 cause the processor 810 to perform one or more method steps of an embodiment described above.

[0082] The storage component 830 stores information and / or software related to the operation and use of the device 800. For example, the storage component 830 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0083] The input component 840 is configured to receive information, such as user input. For example, the input component 840 may include, but not be limited to. a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 840 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0084] The output component 850 is configured to provide output infomiation from the device 800. For example, the output component 850 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0085] The communication interface 860 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 860 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 800 and other devices. In other words, the standard of the communication interface 860 is not limited.

[0086] The bus 870 acts as an interconnect between the processor 810, the memory 820, the storage component 830, the input component 840, the output component 850, and the communication interface 860 of the device 800. The bus 870 may include a wired interconnection or a wireless interconnection.

[0087] The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, device 800 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 8. Additionally, or alternatively, a set of components (e.g., one or more components) of the device 800 may perform one or more functions described as being performed by another set of components of the device 800. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 800 in communication with one another.

[0088] Examples of the techniques and apparatus described herein include, but are not limited to, the following enumerated embodiments:[1] An apparatus configured to: receive, from at least one of a gNodeB-Distributed Unit (gNB-DU) of a gNB or a gNodeB-Centralized Unit (gNB-CU) of one or more neighbouring gNBs, measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality' of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity' infonnation comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL)GBR, and a measured DL non-GBR;receive, from the at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner, wherein the predicted throughput absorption capacity information comprises a predicted UL GBR. a predicted UL non-GBR, a predicted DL GBR. and a predicted DL non-GBR for a time duration; and determine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information.[2] The apparatus as described in [1]. wherein to determine whether to prepare one or more candidate cells, the apparatus is configured to: determine whether an admission of each of a plurality of Packet Data Unit (PDU) sessions and each of a plurality of Data Radio Bearers (DRBs) corresponding to each of the plurality of slices associated with a User Equipment (UE) in the one or more candidate cells is possible.[3] The apparatus as described in any one of [1] to [2], further configured to: receive an indication associated with a time duration for which the predicted throughput absorption capacity information is valid; and determine whether to prepare the one or more candidate cells among the plurality' of cells for implementing the one or more mobility' solution mechanisms based on the received measured throughput absorption capacity' information, the received predicted throughput absorption capacity' information, and the received time duration.[4] The apparatus as described in any of [l]-[3], wherein the measured throughput absorption capacity information and the predicted throughput absorption capacity information are received from the gNB-DU of the associated gNB via an Fl interface.[5] The apparatus as described in any one of [1] to [4], wherein the measured throughput absorption capacity information and the predicted throughput absorption capacity information are received from the gNB-CU of the one or more neighbouring gNBs via an Xn interface.[6] The apparatus as described in any one of [1] to [5], wherein the one or more mobility solution mechanisms include one or more of a conditional handover (CHO), a Layer 1 / Layer 2 Triggered Mobility (LTM), a conditional LTM (C-LTM). a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO).[7] The apparatus as described in any one of [1] to [6], wherein the apparatus corresponds to a gNB-CU of the Next Generation-RAN node.[8] A method comprising: receiving, by a gNodeB-Centralized Unit (gNB-CU) of a gNB from at least one of a gNodeB-Distributed Unit (gNB-DU) of the associated gNB or a gNB-CU of one or more neighbouring gNBs, measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR; receiving, by the gNB-CU of the gNB from the at least one of the gNB-DU of the associated gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each ofthe plurality of cells in the periodic manner, wherein the predicted throughput absorption capacity information compnses a predicted UL GBR, a predicted UL non-GBR, a predicted DL GBR. and a predicted DL non-GBR for a time duration; and determining, by the gNB-CU of the gNB, whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity’ information.[9] The method as described in [8], wherein determining whether to prepare one or more candidate cells comprises: determining, by the gNB-CU of the gNB, whether an admission of each of a plurality of Packet Data Unit (PDU) sessions and each of a plurality of Data Radio Bearers (DRBs) corresponding to each of the plurality of slices associated with a User Equipment (UE) in the one or more candidate cells is possible.

[0010] The method as described in any one of [8] to [9], further comprising: receiving, by the gNB-CU of the gNB, an indication associated with a time duration for which the predicted throughput absorption capacity information is valid; and determining whether to prepare the one or more candidate cells among the plurality' of cells for implementing the one or more mobility solution mechanisms based on the received measured throughput absorption capacity7information, the received predicted throughput absorption capacity information, and the received time duration.

[0011] The method as described in any one of [8] to

[0010] , wherein the measured throughput absorption capacity information and the predicted throughput absorption capacity7information are received from the gNB-DU of the associated gNB via an Fl interface.

[0012] The method as described in any one of [8] to

[0011] , wherein the measured throughput absorption capacity and the predicted throughput absorption capacity are received from the gNB-CU of the one or more neighbouring gNBs via an Xn interface.

[0013] The method as described in any one of [8] to

[0012] , wherein the one or more mobility solution mechanisms include one or more of a conditional handover (CHO), a Layer 1 / Layer 2 Triggered Mobility (LTM), a conditional LTM (C-LTM). a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO).

[0014] A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by agNodeB-Centralized Unit (gNB- CU) of a gNB comprising one or more processors, cause the one or more processors to: receive, from at least one of a gNodeB-Distributed Unit (gNB-DU) of the gNB or the gNB-CU of one or more neighbouring gNBs, measured throughput absorption capacity information corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR; receive, from the at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner, wherein the predicted throughput absorption capacity information comprises a predicted UL GBR, a predicted UL non-GBR, a predicted DL GBR, and a predicted DL non-GBR for a time duration; anddetermine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information.

[0089] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements can be at least one of a hardware device or a combination of hardware devices and software modules. The gNB-CU, the gNB-DU and the NG-RAN nodes may include respective processors, communication units, and storage units (e.g., memory ). The communication units may perform functions for transmitting and receiving signals. The storage units may include executable instructions that, when executed by the corresponding processors, cause the corresponding gNB-CU, the gNB-DU and the NG-RAN nodes to perform the functions as described above with reference to FIGS. 2-7.

[0090] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

[0091] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein.

[0092] Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts necessarily need to be performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples. Numerous variations, whether explicitly given in the specification or not, such as differences in structure, dimension, and use of material, are possible. The scope of embodiments is at least as broad as given by the following claims.

[0093] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any component(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as a critical, required, or essential feature or component of any or all the claims.

[0094] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of at least one embodiment, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims

We claim:

1. An apparatus configured to: receive, from at least one of a gNodeB-Distributed Unit (gNB-DU) of a gNB or a gNodeB-Centralized Unit (gNB-CU) of one or more neighbouring gNBs, measured throughput absorption capacity- information corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR. and a measured DL non-GBR; receive, from the at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner, wherein the predicted throughput absorption capacity- information comprises a predicted UL GBR. a predicted UL non-GBR, a predicted DL GBR. and a predicted DL non-GBR for a time duration; and determine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity- information and the received predicted throughput absorption capacity- information.

2. The apparatus as claimed in claim 1, wherein to determine whether to prepare one or more candidate cells, the apparatus is configured to:determine whether an admission of each of a plurality of Packet Data Unit (PDU) sessions and each of a plurality of Data Radio Bearers (DRBs) corresponding to each of the plurality of slices associated with a User Equipment (UE) in the one or more candidate cells is possible.

3. The apparatus as claimed in claim 1. further configured to: receive an indication associated with a time duration for which the predicted throughput absorption capacity information is valid; and determine whether to prepare the one or more candidate cells among the plurality of cells for implementing the one or more mobility solution mechanisms based on the received measured throughput absorption capacity information, the received predicted throughput absorption capacity infonnation, and the received time duration.

4. The apparatus as claimed in claim 1, wherein the measured throughput absorption capacity infonnation and the predicted throughput absorption capacity information are received from the gNB-DU of the associated gNB via an Fl interface.

5. The apparatus as claimed in claim 1, wherein the measured throughput absorption capacity' information and the predicted throughput absorption capacity information are received from the gNB-CU of the one or more neighbouring gNBs via an Xn interface.

6. The apparatus as claimed in claim 1, wherein the one or more mobility solution mechanisms include one or more of a conditional handover (CHO), a Layer 1 / Layer 2 Triggered Mobility (LTM), a conditional LTM (C-LTM), a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO).

7. The apparatus as claimed in claim 1, wherein the apparatus corresponds to a gNB-CU of the Next Generation-RAN node.

8. A method comprising: receiving, by a gNodeB-Centralized Unit (gNB-CU) of a gNB from at least one of a gNodeB-Distributed Unit (gNB-DU) of the associated gNB or a gNB-CU of one or more neighbouring gNBs, measured throughput absorption capacity infonnation corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR; receiving, by the gNB-CU of the gNB from the at least one of the gNB-DU of the associated gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality7of slices within each of the plurality7of cells in the periodic manner, wherein the predicted throughput absorption capacity7information comprises a predicted UL GBR, a predicted UL non-GBR, a predicted DLGBR, and a predicted DL non-GBR for a time duration; anddetermining, by the gNB-CU of the gNB, whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information.

9. The method as claimed in claim 8, wherein determining whether to prepare one or more candidate cells comprises: determining, by the gNB-CU of the gNB, whether an admission of each of a plurality of Packet Data Unit (PDU) sessions and each of a plurality of Data Radio Bearers (DRBs) corresponding to each of the plurality of slices associated with a User Equipment (UE) in the one or more candidate cells is possible.

10. The method as claimed in claim 8, further comprising: receiving, by the gNB-CU of the gNB, an indication associated with a time duration for which the predicted throughput absorption capacity information is valid; and determining whether to prepare the one or more candidate cells among the plurality of cells for implementing the one or more mobility solution mechanisms based on the received measured throughput absorption capacity7information, the received predicted throughput absorption capacity information, and the received time duration.

11. The method as claimed in claim 8, wherein the measured throughput absorption capacity information and the predicted throughput absorption capacity information are received from the gNB-DU of the associated gNB via an Fl interface.

12. The method as claimed in claim 8, wherein the measured throughput absorption capacity and the predicted throughput absorption capacity are received from the gNB-CU of the one or more neighbouring gNBs via an Xn interface.

13. The method as claimed in claim 8. wherein the one or more mobility solution mechanisms include one or more of a conditional handover (CHO), a Layer 1 / Layer 2 Triggered Mobility (LTM), a conditional LTM (C-LTM), a Layer 3 Handover (L3 HO), and a Dual Active Protocol Stack (DAPS) Handover (DAPS HO).

14. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by a gNodeB-Centralized Unit (gNB- CU) of a gNB comprising one or more processors, cause the one or more processors to: receive, from at least one of a gNodeB-Distributed Unit (gNB-DU) of the gNB or the gNB-CU of one or more neighbouring gNBs, measured throughput absorption capacity infonnation corresponding to each of a plurality of slices within each of a plurality of cells of the gNB or the one or more neighbouring gNBs in a periodic manner, wherein the measured throughput absorption capacity' information comprises a measured Uplink (UL) Guaranteed BitRate (GBR), a measured UL non-GBR, a measured Downlink (DL) GBR, and a measured DL non-GBR; receive, from the at least one of the gNB-DU of the gNB or the gNB-CU of the one or more neighbouring gNBs, predicted throughput absorption capacity information corresponding to each of the plurality of slices within each of the plurality of cells in the periodic manner,wherein the predicted throughput absorption capacity information comprises a predicted UL GBR. a predicted UL non-GBR. a predicted DL GBR. and a predicted DL non-GBR for a time duration; and determine whether to prepare one or more candidate cells among the plurality of cells for implementing one or more mobility solution mechanisms based on the received measured throughput absorption capacity information and the received predicted throughput absorption capacity information.

Images