Context release procedures for a user equipment

Abstract

Embodiments of the disclosure describe a method for managing User Equipment (UE) context release procedures. The method includes transmitting, by a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node, a handover request message to initiate a handover event of a User Equipment (UE). The method includes determining, upon successful completion of the handover event, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node. The method includes maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message receives prior to the data collection update message from the target NG-RAN node. The method includes releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

Description

CONTEXT RELEASE PROCEDURES FOR A USER EQUIPMENTCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to India Provisional Application No. 202411086113, filed on November 8, 2024, and India Non-Provisional Application No. 202411086113, filed on April 18, 2025, the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to context release procedures for a User Equipment (UE).BACKGROUND

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

[0004] The field of wireless communications has made significant progress with the introduction of Fifth-Generation (5G) networks, particularly in enhancing network slicing capabilities through Artificial Intelligence (Al) and Machine Learning (ML) technologies. These advancements associated with Al and ML technologies facilitate more efficient resource allocation, improved service differentiation, and optimized network management, which are essential for meeting the diverse requirements of modern applications and services. A fundamental aspect of sustaining optimal network performance lies in the assessment and feedback mechanisms concerning UserEquipment (UE) performance metrics during handover processes between network nodes. This includes transitions between source nodes and target nodes, where maintaining service continuity and minimizing latency are paramount. Effective handover management is crucial as handover management directly impacts user experience and overall network reliability.

[0005] According to the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.743, the optimization of AI / ML-driven network slicing models necessitates a systematic collection of targeted feedback from gNodeBs (gNBs). This feedback is crucial for optimizing network operations and encompasses several key metrics, as detailed hereinafter.

[0006] Firstly, a metric associated with measured radio resource status per slice provides insights into availability and utilization of radio resources allocated to each network slice. Secondly, a measured slice available capacity, which includes understanding the capacity constraints of individual slices is critical for ensuring that Service Level Agreements (SLAs) are met. Lastly, Performance feedback from UEs after handover involves collecting data on their performance during these handover events. This feedback is crucial for validating the AI / ML-based decisions made at the source node . The specification further emphasizes the importance of obtaining more granular UE performance feedback. Such detailed insights are essential for accurately evaluating the performance of UEs associated with specific slices in operation. This level of granularity enables one or more entities involved in network slicing to make informed decisions regarding resource allocation, slice management, and overall network optimization strategies.SUMMARY

[0007] 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 intendedto identify key or essential inventive concepts of the disclosure nor is it intended for determining the scope of the disclosure.

[0008] According to one embodiment of the present disclosure, a method is disclosed. The method includes transmitting, by a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node, a handover request message to initiate a handover event of a User Equipment (UE) from the source NG-RAN node to the target NG-RAN node. The method further includes determining, upon successful completion of the handover event, by the source NG-RAN node, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node. The method further includes maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node. The method further includes releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

[0009] According to one embodiment of the present disclosure, a method is disclosed. The method includes receiving, by a target Next Generation Radio Access Network (NG-RAN) node, a handover request message from a source NG-RAN node for a User Equipment (UE). The method further includes transmitting, by the target NG-RAN node, a handover acknowledgement message to the source NG-RAN node, in response to transmitting the handover request message. The method further includes detecting, after transmitting the handover acknowledgement message, by the target NG-RAN node, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node. The method further includes preparing,by the target NG-RAN node, a data collection update message including the requested data as per a data collection ID Information Element (IE). The method further includes transmitting, by the target NG-RAN node, the data collection update message to the source NG-RAN node. The method further includes transmitting, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

[0010] According to one embodiment of the present disclosure, an apparatus is disclosed. The apparatus is configured to transmit a handover request message to initiate a handover event of a User Equipment (UE) from a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node. The apparatus is further configured to determine, upon successful completion of the handover event, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node. The apparatus is further configured to maintain a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node. The apparatus is further configured to release the UE context at the source NG- RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

[0011] According to one embodiment of the present disclosure, an apparatus is disclosed. The apparatus is configured to receive a handover request message from a source Next Generation Radio Access Network (NG-RAN) node for a User Equipment (UE). The apparatus is further configured to transmit a handover acknowledgement message to the source NG-RAN node, in response to transmitting the handover request message. The apparatus is further configured to detect, after transmitting the handover acknowledgement message, an occurrence of a successfulcompletion of the handover event between the source NG-RAN node and a target NG-RAN node. The apparatus is further configured to prepare a data collection update message including the requested data as per a data collection ID Information Element (IE). The apparatus is further configured to transmit the data collection update message to the source NG-RAN node. The apparatus is further configured to transmit, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

[0012] According to one embodiment of the present disclosure, a non-transitory computer- readable medium storing instructions is disclosed. The one or more instructions are executed by an apparatus which comprises one or more processors. The one or more processors may transmit a handover request message to initiate a handover event of a User Equipment (UE) from a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node. The one or more processors may determine, upon successful completion of the handover event, whether an UE context release message is received prior to a data collection update message from the target NG-RAN node. The one or more processors may maintain a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node. The one or more processors may release the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

[0013] According to one embodiment of the present disclosure, a non-transitory computer- readable medium storing instructions is disclosed. The one or more instructions are executed by an apparatus which comprises one or more processors. The one or more processors may receive a handover request message from a source Next Generation Radio Access Network (NG-RAN) nodefor a User Equipment (UE). The one or more processors may transmit a handover acknowledgement message to the source NG-RAN node, in response to transmitting the handover request message. The one or more processors may detect, after transmitting the handover acknowledgement message, an occurrence of a successful completion of the handover event between the source NG-RAN node and a target NG-RAN node. The one or more processors may prepare a data collection update message including the requested data as per a data collection ID Information Element (IE). The one or more processors may transmit the data collection update message to the source NG-RAN node. The one or more processors may transmit, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

[0014] 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 are illustrated in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the disclosure and are therefore not to be considered limiting of its scope. The disclosure will be described and explained with additional specificity and detail in the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Features, aspects, and advantages of 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 is a diagram of an example of an implementation environment in which systems and / or methods, described herein, may be implemented, according to an embodiment as disclosed herein;FIG. 2 is a sequence flow diagram illustrating a method for managing User Equipment(UE) context release procedure at a source Next Generation Radio Access Network (NG-RAN) node (as option-1), according to an embodiment as disclosed herein;FIG. 3 is a sequence flow diagram illustrating a method for managing the UE context release procedure at a target NG-RAN node (as option-2), according to another embodiment as disclosed herein;FIG. 4 is a flow diagram illustrating a method for managing the UE context release procedure based on a predefined timer at the source NG-RAN node, according to an embodiment as disclosed herein;FIG. 5 is a flow diagram illustrating a method for managing the UE context release procedure for enhancing a reporting procedure associated with a handover, according to an embodiment as disclosed herein; andFIG. 6 illustrates a diagram of example components of an apparatus, according to an embodiment as disclosed herein.DETAILED DESCRIPTION

[0016] 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 anotherembodiment). Additionally, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make other embodiments 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).

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

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

[0019] 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 beopen-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.

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

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

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

[0023] Machine learning includes various types of learning methods such as supervised learning, unsupervised learning, reinforcement learning, semi-supervised learning, self-supervised learning, transudative learning, transfer learning, meta learning, and the like. These types 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.

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

[0025] Throughout this disclosure, the terms “source Next Generation Radio Access Network (NG-RAN) node”, “source gNB” and “NG-RAN1” are used interchangeably and imply a similar meaning. Similarly, the terms “target NG-RAN node”, “target gNB” and “NG-RAN2” are used interchangeably and imply a similar meaning.

[0026] In the context of wireless communications, upon a successful completion of a Handover (HO) from a source gNB to a target gNB, the target gNB transmits User Equipment (UE) performance metrics (data) back to the source gNB, which is applicable only when the source NG- RAN node has included a Data Collection ID IE in the handover request message to the target NG-RAN node This data enables the source gNB to assess the effectiveness of mobility decisions andserves as feedback to validate the precision of AI / ML training algorithms. To facilitate this process, retention at the source NG RAN node of a UE context for a UE transitioned to the target gNB remains essential until the corresponding feedback information is received.

[0027] However, the current UE context release mechanism dictates immediate relinquishment of the UE context upon receiving a UE context release notification from the target gNB, Consequently, this limitation prevents effective evaluation of the merits of mobility decisions or validation of the accuracy of AI / ML training when feedback information from the target gNB needs to be signaled to the source gNB.

[0028] Therefore, it is desired to address the above-mentioned disadvantages or other shortcomings or at least provide a useful alternative for UE context release procedures, as discussed throughout the disclosure (FIGS. 1 to 6).

[0029] To address the above-mentioned disadvantages or challenges, a disclosed method and / or apparatus provides a unique strategy for the UE context release procedures detailed below.

[0030] In the context of a handover process, the UE context release procedure is initiated by the target NG-RAN node to signal the source NG-RAN node that one or more radio and control plane resources associated with a UE context may be released. To facilitate the reporting of the UE performance metrics from the target NG-RAN node to the source NG-RAN node in alignment with Release 18 AI / ML specifications, two options are available regarding the UE context release message transmitted from the target NG-RAN node to the source NG-RAN node upon successful handover completion.

[0031] In one or more embodiments, the first option (option-1) describes that if the source NG- RAN node includes a data collection Identifier (ID) Information Element (IE) in a handoverrequest message, the source NG-RAN node may disregard the UE context release received from the target NG-RAN node until the source NG-RAN node has processed data collection update, as described in conjunction with FIG. 2. Following the completion of a data collection update procedure, the source NG-RAN node may then act upon the previously received UE context release. This approach represents a deviation from the traditional behavior observed in recipient of the UE context release procedure. Employing a legacy mechanism where the target NG-RAN node transmits the UE context release to the source NG-RAN node upon successful handover completion may result in altered behavior at the source NG-RAN node upon receipt of the UE context release from the target NG-RAN node.

[0032] In one or more embodiments, the second option (option-2) describes that upon successful handover completion, the target NG-RAN node withholds the transmission of the UE context release to the source NG-RAN node, deferring this action until after the data collection update message has been sent, as described in conjunction with FIG. 3. In this scenario, the source NG- RAN node’s response to the UE context release remains consistent with a legacy mechanism, while the behavior of the target NG-RAN node diverges from the legacy mechanism. The second option mitigates a risk of the UE context release at the source NG-RAN node prior to receiving a UE performance feedback. The second option stipulates that the target NG-RAN node may transmit the UE context release to the source NG-RAN node subsequent to dispatching the data collection update, specifically in instances where the data collection ID IE is included in a handover request message.

[0033] In one or more embodiments, the disclosed method and / or apparatus offers several advantages. For instance, the disclosed method and / or apparatus ensures that the source NG-RANnode retains the necessary performance feedback before proceeding with the release of resources, thereby ensuring the accuracy of comparison of the performance metrics collected during the handover process. This approach minimizes the risk of premature resource release, which could lead to data loss or degradation in service quality. Additionally, by aligning with Release 18 AI / ML specifications, the disclosed method and / or apparatus fosters improved integration of advanced analytics and machine learning capabilities, ultimately contributing to a more efficient and responsive network environment, which is discussed in conjunction with FIG. 4.

[0034] Referring now to the drawings, and more particularly to FIGS. 1 to 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

[0035] FIG. 1 is a diagram of an example of an implementation environment 100 in which systems and / or methods, described herein, may be implemented, according to an embodiment as disclosed herein. The implementation environment 100 includes a User Equipment (UE) 110, a service environment 120, and a network 130. The service environment 120 may relate to a source Next Generation Radio Access Network (NG-RAN) node (e.g., NG-RAN1) and a target NG-RAN node (e.g., NG-RAN2). The service environment 120 includes one or more sub-environments 121-1 to 121-N (collectively and / or interchangeably referred hereinafter as 121). To illustrate this, FIG. 1 shows, for convenience, examples of a 1st sub-environment 121-1, a 2nd sub-environment 121-2, and an N111sub-environment 121-N (where N is any natural number).

[0036] The UE 110 is connected to the network 130, and the network 130 is connected to the service environment 120. The connections may be wired, wireless, or a combination of both wired and wireless. The UE 110 and the service environment 120 are connected via the network 130.

[0037] The UE 110 is a device that communicates with the service environment 120. The UE 110 receives information from the service environment 120 and / or sends information to the service environment 120. Also, the UE 110 may generate and / or store information to be transmitted, as necessary. Also, the UE 110 may store and / or process information that is received, as necessary.

[0038] The example FIG. 1 refers to the “UE”. However, it should be understood by those skilled in the art that general terms such as “user device”, “terminal”, “terminal device”, “communication device”, and “communication terminal” can be used interchangeably with the term “UE”.

[0039] For example, the UE 110 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e g., a smartphone, a radiotelephone, etc.), a wearable device (e g., a pair of smart glasses or a smart watch), or a similar device.

[0040] The service environment 120 is an environment that communicates with the UE 110 to provide one or more services. The service environment 120 receives information from the UE 110 and / or sends information to the UE 110. Also, the service environment 120 may generate and / or store information to be transmitted, as necessary. Also, the service environment 120 may store and / or process information that is received, as necessary. For example, the service environment 120 may provide computing resources as one of the services. It should be noted that the service is not limited to being provided to the UE 110; it may also be provided to devices other than the UE 110. For example, based on communication from the UE 110, the service may perform processes such as anomaly detection or traffic analysis and notify the results to a predetermined destination.

[0041] The example FIG. 1 refers to the “service environment”. The term “service environment” is used to refer to the broader context within which services operate. For example, cloudenvironments, platforms, computing systems, network systems, and cloud systems generally represent the environments in which services are conducted, and these are included within the“service environment”. However, the “service environment” is not limited to these examples. Additionally, the specific types of environments within the “service environment” are not restricted. For instance, cloud environments and cloud systems can be categorized as private cloud, public cloud, hybrid cloud, or multi-cloud, all of which are included within the “service environment”.

[0042] The one or more services provided by the service environment 120 is not specifically limited and can be adjusted according to the embodiments. For example, the one or more services may include a service that provides information to the UE 110, a service that stores information from the UE 110, or a service that performs processing based on information from the UE 110 and returns the results of the processing.

[0043] In an embodiment, the service environment 120 may also provide computing resources such as the service. The computing resources can be hardware resources and / or software resources. For example, applications, processors, memory, and storage can be included in the provided computing resources. Each computing resource can communicate with other computing resources via wired connections, wireless connections, or a combination of wired and wireless connections.

[0044] The provided computing resources can be actual resources (also referred to as physical resources) and / or virtual resources. Furthermore, means of virtualization for virtual resources can be selected as appropriate. That is, in this disclosure, the use of adjectives such as “virtual” or “virtualized” to describe names does not imply that they are virtualized by a specific means of virtualization. For example, “virtual machine” refers to software that operates like an actualcomputer, realized through means of virtualization, and it is not intended to exclude those realized by specific means of virtualization such as hypervisors or containers. Conversely, when means of virtualization such as hypervisors or containers are mentioned in this disclosure, it is merely cited as a general method of implementation. It should also be interpreted that embodiments implemented with other virtualization means are also disclosed. Also, the services may also be provided using resources virtualized by different means.

[0045] The service environment 120 includes one or more devices, such as servers and network devices, which provide services or perform processes. The placement of these devices within the service environment 120 can be determined as appropriate. Additionally, if the service environment 120 includes one or more sub-environments 121, the placement of devices can be determined based on predetermined policies for each sub-environment 121. For example, devices related to the first service may be placed in the 1st sub-environment 121-1, and devices related to the second service may be placed in the 2nd sub-environment 121-2. In another example, devices expected to have a higher load than a predetermined threshold may be placed in the 1st subenvironment 121-1, while devices expected to have a lower load than the predetermined threshold may be placed in the 2nd sub -environment 121-2. In this way, specific devices can be placed in specific sub-environments 121. Conversely, each sub-environment 121 can be specialized for a particular purpose.

[0046] In an embodiment, all processes executed in a single service may run within a single service environment, or in multiple service environments. Multiple processes executed in a single service could be provided by different service environments.

[0047] The network 130 is a network that exchanges information between the UE 110 and the service environment 120. The network 130 includes one or more wired and / or wireless networks.

[0048] For example, the network 130 may include a cellular network (e.g., a Fifth Generation (5G) network, a Long-Term Evolution (LTE) network, a Third Generation (3G) network, a Code Division Multiple Access (CDMA) network, etc.), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, a NonTerrestrial Network (NTN), and / or a combination of these or other types of networks.

[0049] The network 130 can be a part of a network. For example, in a 5G network that includes a RAN, a transport network, and a core network, the network 130 can be at least one of the RAN, the transport network, or the core network. For example, the service environment 120 could be in the core network, in which case the network 130 could correspond to a network that is a combination of a RAN and a transport network and is part of the 5G network.

[0050] The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. It should be understood that any changes that may be implemented by those skilled in the art, such as the addition or rearrangement of well-known devices or networks at the time of implementation, are included in this disclosure.

[0051] FIG. 2 is a sequence flow diagram illustrating a method 200 for managing the UE context release procedure at the source NG-RAN node 200a (as option-1), according to an embodiment as disclosed herein. The method 200 may execute multiple operations to manage the UE context release procedure, which are given below.

[0052] At operation 201, the method 200 includes transmitting, by the source NG-RAN node 200a, a data collection request message (i.e., data collection request) to the target NG-RAN node 200b to initiate a collection of specific data.

[0053] In one embodiment, the data collection request message may include, for example, the data collection ID IE, including parameters that indicate the specific data (e.g., UE performance metrics like throughput, packet loss, packet delay, etc.) to be collected and conditions for collecting the specific data.

[0054] At operation 202, the method 200 includes receiving, by the source NG-RAN node 200a, a data collection response from the target NG-RAN node 200b, in response to transmitting the data collection request message. The data collection response acknowledges the data collection request message and may include relevant information regarding a status of the data collection process.

[0055] At operation 203, the method 200 includes transmitting, by the source NG-RAN node 200a to a target NG-RAN node 200b, a handover request message to initiate a handover event of the UE from the source NG-RAN node 200a to the target NG-RAN node 200b. For instance, the following embodiments are relevant only when the source NG-RAN node 200a has included the data collection ID IE in the handover request message to the target NG-RAN node 200b. In one embodiment, the handover request message comprises the data collection ID IE to ensure that the target NG RAN node 200b performs the requested data collection after a successful handover process, which may relate to the operation 201.

[0056] At operation 204, the method 200 includes receiving, by the source NG-RAN node 200a, a handover acknowledgement message (i.e., handover request acknowledgement) from the targetNG-RAN node 200b, in response to transmitting the handover request message. The handoveracknowledgement message confirms that the target NG-RAN node 200b is prepared to accept the UE, thereby facilitating the transition.

[0057] At operation 205, the method 200 includes detecting, upon receiving the handover acknowledgement message, by the source NG-RAN node 200a, an occurrence of a successful completion of the handover event between the source NG-RAN node 200a and the target NG- RAN node 200b. This detection signifies that the UE has been successfully transferred from the source NG-RAN node 200a to the target NG-RAN node 200b, ensuring continuity of service.

[0058] At operation 206, the method 200 includes receiving, by the source NG-RAN node 200a, a UE context release message (i.e., UE context release) from the target NG-RAN node 200b. In one embodiment, the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG-RAN node.

[0059] At operation 207, the method 200 includes determining, by the source NG-RAN node 200a, whether the UE context release message is received prior to a data collection update message (i.e., data collection update) from the target NG-RAN node 200b. The data collection update message comprises, for example, information sent from the target NG-RAN node 200b to the source NG- RAN node 200a for UE performance metrics like throughput, packet loss, and packet delay. The source NG-RAN node 200a maintains a UE context at the source NG-RAN node 200a, in response to determining that the UE context release message received prior to the data collection update message from the target NG-RAN node 200b.

[0060] In one embodiment, the UE context may include, for example, a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality ofService (QoS) parameters, security context information, location information, and a type of service information.

[0061] At operation 208, the method 200 includes receiving, by the source NG-RAN node 200a, the data collection update message from the target NG-RAN node 200b. At operation 209, the method 200 includes determining, by the source NG-RAN node 200a, whether the UE context release message is received prior to the data collection update message from the target NG-RAN node 200b. The source NG-RAN node 200a releases the UE context at the source NG-RAN node 200a, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node 200b.

[0062] The disclosed method 200 ensures that the source NG-RAN node 200a retains the UE context until the data collection update message is received. The data collection update message relates to the performance feedback and the UE performance metrics. This retention facilitates the source NG-RAN node 200a in assessing the effectiveness of the mobility decisions and provides critical feedback for validating the accuracy of AEML training processes, as one of the advantages of the disclosed method 200.

[0063] FIG. 3 is a sequence flow diagram illustrating a method 300 for managing the UE context release procedure at the target NG-RAN node 200b (as option-2), according to another embodiment as disclosed herein. The method 300 may execute multiple operations to manage the UE context release procedure, which are given below.

[0064] At operation 301, the method 300 includes receiving, by the target NG-RAN node 200b, the data collection request message from the source NG-RAN node 200a to initiate data collection process. At operation 302, the method 300 includes transmitting, by the target NG-RAN node 200b,the data collection response to the source NG-RAN node 200a, in response to receiving the data collection request message.

[0065] At operation 303, the method 300 includes receiving, by the target NG-RAN node 200b, the handover request message from the source NG-RAN node 200a for the UE. In one embodiment, the handover request message comprises the data collection ID IE. At operation 304, the method 300 includes transmitting, by the target NG-RAN node 200b, the handover acknowledgement message to the source NG-RAN node 200a, in response to receiving the handover request message. At operation 305, the method 300 includes detecting, after transmitting the handover acknowledgement message, by the target NG-RAN node 200b, the occurrence of the successful completion of the handover event between the source NG-RAN node 200a and the target NG- RAN node 200b.

[0066] At operation 306, the method 300 includes preparing, by the target NG-RAN node 200b, the data collection update message including the requested data as per the data collection ID IE. In addition, after preparation of the data collection update message, the method 300 includes transmitting, by the target NG-RAN node 200b, the data collection update message to the source NG-RAN node 200a. At operation 307, the method 300 includes transmitting, after transmitting the data collection update message, the UE context release message to the source NG-RAN node 200a.

[0067] In one embodiment, in the disclosed method 300, the source NG-RAN node 200a’ s response to the UE context release follows the traditional method, while the target NG-RAN node 200b’s actions differ from the traditional method. As a result, the disclosed method 300 providesfamiliarity for operators and eases the implementation process, as one of advantages of the disclosed method 300.

[0068] In one embodiment, in the disclosed method 300, the target NG-RAN node 200b holds back the UE context release to the source NG-RAN node 200a until after the target NG-RAN node 200b sends the data collection update message. In other words, the disclosed method 300 reduces the risk of the source NG-RAN node 200a releasing the UE context before receiving the performance feedback / data collection update message, which minimizes the chances of losing the performance feedback that could affect network optimization, as one of the advantages of the disclosed method 300.

[0069] In one embodiment, the disclosed method 300 allows the target NG-RAN node 200b to send the UE context release to the source NG-RAN node 200a after sending the data collection update, especially when the data collection ID IE is included in the handover request message. In other words, the disclosed method 300 supports better resource management by preserving critical context information (UE context) until it is no longer needed.

[0070] In one or more embodiments, the disclosed method may perform a plurality of operations to manage the UE context release procedure via a predefined timer (e.g., a Time for Xn interface (TXn) Relocation Preparation (TXnRELOCprep), a TXn Relocation Overall (TXnRELOCoverall), etc.), which are given below.

[0071] In one embodiment, the source NG-RAN node 200a initiates the handover procedure by transmitting the handover request message to the target NG-RAN node 200b. Upon sending this handover request message, the source NG-RAN node 200a may activate a timer TXnRELOCprep, which is discussed in conjunction with FIG. 4. Upon receipt of the handover requestacknowledgement message, the source NG-RAN node 200a may deactivate the timer TXnRELOCprep and conclude the handover procedure.

[0072] In one embodiment, the handover procedure is designated as immediate, the source NG- RAN node 200a may initiate a timer TXnRELOCoverall. If the UE context release procedure is not initiated towards the source NG-RAN node 200a by any prepared NG-RAN node prior to the expiration of the timer TXnRELOCoverall, the source NG-RAN node 200a may request an Access and Mobility Management Function (AMF) to release the UE context, which is discussed in conjunction with FIG. 4.

[0073] In one embodiment, to facilitate Al / ML feedback requirements, it is imperative that the target NG-RAN node 200b transmits the data collection update to the source NG-RAN node 200a before the expiration of the timer TXnRELOCoverall. The source NG-RAN node 200a may maintain the UE context until either the timer expires or till the source NG-RAN node 200a receives the data collection update from the target NG-RAN node 200b, which is discussed in conjunction with FIG. 4.

[0074] In one embodiment, the timing for the transmission of the data collection update from the target NG-RAN node 200b is contingent upon the value of a collection time duration for the UE performance IE and one or more exit conditions configured by the source NG-RAN node 200a. Therefore, the source NG-RAN node 200a may configure the timer TXnRELOCoverall in consideration of the collection time duration for the UE performance IE and the specified one or more exit conditions. This configuration may ensure the retention of the UE context until the data collection update is received, which is discussed in conjunction with FIG. 4.

[0075] FIG. 4 is a flow diagram illustrating a method 400 for managing the UE context release procedure based on the predefined timer at the source NG-RAN node 200a, according to an embodiment as disclosed herein. The method 400 may execute multiple operations to manage the UE context release procedure, which are given below.

[0076] At operation 401, the method 400 includes initiating, after transmitting the handover request message, by the source NG-RAN node 200a, the predefined timer at the source NG-RAN node 200a. At operation 402, the method 400 includes determining, by the source NG-RAN node 200a, whether the initiated predefined timer is expired or whether the data collection update message is received from the target NG-RAN node 200b.

[0077] At operation 403, the method 400 includes maintaining the UE context at the source NG- RAN node 200a, in response to determining that the initiated predefined timer is not expired and the data collection update message is not received from the target NG-RAN node 200b.

[0078] At operation 404, the method 400 includes releasing the UE context at the source NG-RAN node 200a, in response to determining that the initiated predefined timer is expired and the data collection update message is received from the target NG-RAN node 200b.

[0079] At operation 405, the method 400 includes transmitting a request to the AMF to release the UE context, in response to determining that the initiated predefined timer is expired and the data collection update message is not received from the target NG-RAN node 200b

[0080] FIG. 5 is a flow diagram illustrating a method 500 for managing the UE context release procedure for enhancing a reporting procedure associated with the handover, according to an embodiment as disclosed herein. The method 500 may execute multiple operations to manage theUE context release procedure and relate to further operations associated with FIG. 2 and FIG. 3, which are given below.

[0081] At operation 501, the method 500 includes evaluating, by the target NG-RAN node 200b, one or more UE performance metrics based on the performance data included in the data collection request message. At operation 502, the method 500 includes determining, based on the one or more evaluated UE performance metrics, whether a handover decision process for the UE from the source NG-RAN node 200a to the target NG-RAN node 200b is appropriate. At operation 503, the method 500 includes validating, based on the one or more evaluated UE performance metrics from the target NG-RAN node 200b, an accuracy of at least one Al model utilized for the handover decision process at the source NG-RAN node 200a.

[0082] Consider an example scenario associated with a mobile network, where users (UE) frequently transition between different coverage areas managed by various nodes. To ensure stable connections during these movements, a handover process is employed. Initially, when a user moves from one area to another, their mobile device (UE) transmits performance data such as signal strength, to the source NG-RAN node 200a. This source NG-RAN node 200b evaluates these metrics to assess the user’s current connection quality. Based on the evaluated metrics, such as weak signal strength from the target NG-RAN node 200b, the source NG-RAN node 200a determines whether initiating the handover process is appropriate. If the metrics and Al-based prediction suggest that the user would benefit from a better connection at the target node, the handover is deemed necessary. Following this decision, the target NG-RAN node 200b also validates the accuracy of the Al models used at the source NG-RAN node 200a for making handover decisions. This validation involves comparing the evaluated performance metrics againstthe expected outcomes predicted by the Al models. If discrepancies arise, adjustments may be needed to enhance the Al models for future handover decisions. This process ultimately aims to improve user experience during mobility within the network.

[0083] In one or more embodiments, the disclosed method 500 provides several advantages. For instance, by evaluating the UE performance metrics, the disclosed method 500 can make more informed handover decisions, ensuring smooth and efficient transitions between network nodes (e.g., 200a and 200b). This analysis of performance data enhances overall network performance by optimizing resource allocation and managing traffic effectively. Additionally, real-time validation of Al models against actual UE performance metrics ensures that these Al models remain accurate and effective in guiding handover decisions, thereby minimizing the risk of errors.

[0084] In one or more embodiments, the disclosed method 500 may adapt dynamically to changing network conditions and user demands further enhancing user experience and maintaining service quality. By determining the appropriateness of handovers in real-time, the disclosed method 500 also reduces latency, improving responsiveness for users. Moreover, collecting and analyzing performance data provides valuable insights into network behavior, which can inform future upgrades and improvements. This disclosed method 500 may increase the reliability of connections by ensuring that handovers are initiated only when necessary, thus reducing, for example, dropped calls or interruptions.

[0085] FIG. 6 illustrates a diagram of example components of an apparatus, according to an embodiment as disclosed herein. As shown in FIG. 6, the apparatus 600 comprises a processor610, a memory 620, a storage component 630, an input component 640, an output component 650,a communication interface 660, and a bus 670. In one embodiment, the apparatus 600 may relate to at least one of the NG-RAN1 200a, the NG-RAN1 200b, or any other network device.

[0086] The processor 610, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 610 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 610 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 type of processing component.

[0087] The memory 620 includes a non-transitory computer readable medium. Memory 620 includes a Random-Access Memory (RAM), a Read Only Memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 610. The memory 620 comprises machine-readable instructions which are executable by the processor 610. These machine-readable instructions when executed by the processor 610 cause the processor 610 to perform one or more method steps of an embodiment described above.

[0088] The storage component 630 stores information and / or software related to the operation and use of the apparatus 600. For example, the storage component 630 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.

[0089] The input component 640 is configured to receive information, such as user input. For example, the input component 640 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 640 may include a sensor for sensing information (e.g., a Global Positioning System (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0090] The output component 650 is configured to provide output information from the apparatus 600. For example, the output component 650 may be, but is not limited to, a display, a speaker, instructions to an external device, and / or one or more Light-Emitting Diodes (LEDs).

[0091] The communication interface 660 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 660 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 apparatus 600 and other devices. In other words, the standard of the communication interface 660 is not limited.

[0092] The bus 670 acts as an interconnect between the processor 610, the memory 620, the storage component 630, the input component 640, the output component 650, and the communication interface 660 of the apparatus 600. The bus 670 may include a wired interconnection or a wireless interconnection.

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

[0094] Examples of the techniques and apparatus described herein include, but are not limited to, the following enumerated embodiments:[1] A method comprising: transmitting, by a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node, a handover request message to initiate a handover event of a User Equipment (UE) from the source NG-RAN node to the target NG-RAN node; determining, upon successful completion of the handover event, by the source NG- RAN node, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node; and performing, by the source NG-RAN node, one of: maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node; or releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.[2] The method as described in [1], wherein at least one of the UE context release message and the data collection update message includes performance data associated with the UE, and wherein the method further comprises: prior to performing at least one, wherein one or more UE performance metrics are evaluated by the target NG-RAN node, based on the performance data included in the data collection update message; performing, by the source NG-RAN node, the at least one: determining, based on the one or more evaluated UE performance metrics, whether a handover decision process for the UE from the source NG-RAN node to a target NG-RAN node is appropriate; or validating, based on the one or more evaluated UE performance metrics from the target NG RAN node, an accuracy of at least one Artificial Intelligence (Al) model utilized for the handover decision process at the source NG RAN node.[3] The method as described in any of [l]-[2], wherein prior to transmitting the handover request message, the method comprises: transmitting, by the source NG-RAN node, a data collection request message to the target NG-RAN node to initiate a collection of specific data, wherein the data collection request message comprises a data collection ID, including parameters that indicate the specific data to collect and conditions for collecting the specific data; andreceiving, by the source NG-RAN node, a data collection response from the targetNG-RAN node, in response to transmitting the data collection request message.[4] The method as described in any of [l]-[3], wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; wherein the UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.[5] The method as described in any of [l]-[4], comprising: receiving, by the source NG-RAN node, a handover acknowledgement message from the target NG-RAN node, in response to transmitting the handover request message; and detecting, upon receiving the handover acknowledgement message, by the source NG-RAN node, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node.[6] The method as described in any of [l]-[5], further comprising:initiating, after transmitting the handover request message, by the source NG-RAN node, a predefined timer at the source NG-RAN node; determining, by the source NG-RAN node, whether the initiated predefined timer is expired or a data collection update message is received from the target NG-RAN node; and performing, by the source NG-RAN node, one of: maintaining a UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is not expired and the data collection update message is not received from the target NG-RAN node; releasing the UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is expired and the data collection update message is received from the target NG-RAN node; or transmitting a request to an Access and Mobility Management Function (AMF) to release the UE context, in response to determining that the initiated predefined-timer is expired and the data collection update message is not received from the target NG-RAN node.[7] The method as described in any of [l]-[6], further comprising: configuring, by the source NG-RAN node, a value of predefined-timer based on a value of collection time duration for UE performance IE and one or more predefined exit conditions,wherein the predefined timer comprises one of a TXn RelocationPreparation (TXnRELOCprep) and a TXn Relocation Overall (TXnRELOCoverall).[8] A method comprising: receiving, by a target Next Generation Radio Access Network (NG-RAN) node, a handover request message from a source NG-RAN node for a User Equipment (UE); transmitting, by the target NG-RAN node, a handover acknowledgement message to the source NG-RAN node, in response to receiving the handover request message; detecting, after transmitting the handover acknowledgement message, by the target NG-RAN node, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node; preparing, by the target NG-RAN node, a data collection update message including the requested data as per a data collection ID Information Element (IE); transmitting, by the target NG-RAN node, the data collection update message to the source NG-RAN node; and transmitting, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.[9] The method as described in [8], wherein prior to receiving the handover request message, the method comprises:receiving, by the target NG-RAN node, a data collection request message from the source NG-RAN node to initiate data collection process, wherein the data collection request message comprises the data collectionID IE, including parameters that indicate specific data to collect and conditions for gathering; and transmitting, by the target NG-RAN node, a data collection response to the source NG-RAN node, in response to receiving the data collection request message.

[0010] The method as described in any of [8]-[9], wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

[0011] An apparatus configured to: transmit a handover request message to initiate a handover of a User Equipment (UE) from a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node;determining, upon successful completion of the handover event, by the source NG-RAN node, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node; and perform one of: maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node; or releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

[0012] The apparatus as described in

[0011] , wherein at least one oftheUE context release message and the data collection update message includes performance data associated with the UE, and the apparatus is further configured to: prior to perform at least one, wherein one or more UE performance metrics are evaluated by the target NG-RAN node, based on the performance data included in the data collection update message; perform the at least one: determine, based on the one or more evaluated UE performance metrics, whether a handover decision process for the UE from the source NG-RAN node to a target NG-RAN node is appropriate; orvalidate, based on the one or more evaluated UE performance metrics from the target NG RAN node, an accuracy of at least one Artificial Intelligence (Al) model utilized for the handover decision process at the source NG RAN node.

[0013] The apparatus as described in any of

[0011] -

[0012] , wherein prior to transmitting the handover request message, the apparatus is configured to: transmit a data collection request message to the target NG-RAN node to initiate a collection of specific data, wherein the data collection request message comprises a data collection ID, including parameters that indicate the specific data to collect and conditions for collecting the specific data; and receive a data collection response from the target NG-RAN node, in response to transmitting the data collection request message.

[0014] The apparatus as described in any of

[0011] -

[0013] , wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein the UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

[0015] The apparatus as described in any of

[0011] -

[0014] , the apparatus is configured to: receive a handover acknowledgement message from the target NG-RAN node, in response to transmitting the handover request message; and detect, upon receiving the handover acknowledgement message, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node.

[0016] The apparatus as described in any of

[0011] -

[0015] , the apparatus is further configured to: initiate, after transmitting handover request message, a predefined timer at the source NG-RAN node; determine whether the initiated predefined timer is expired or a data collection update message is received from the target NG-RAN node; and perform one of: maintaining a UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is not expired and the data collection update message is not received from the target NG-RAN node; releasing the UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is expired and the data collection update message is received from the target NG-RAN node; or transmitting a request to an Access and Mobility Management Function(AMF) to release the UE context, in response to determining that the initiatedpredefined-timer is expired and the data collection update message is not received from the target NG-RAN node.

[0017] The apparatus as described in any of

[0011] -

[0016] , : configure a value of predefined-timer based on a value of collection time duration for UE performance IE and one or more predefined exit conditions, wherein the predefined timer comprises one of a TXn Relocation Preparation (TXnRELOCprep) and a TXn Relocation Overall (TXnRELOCoverall).

[0018] An apparatus configured to: receive a handover request message from a source Next Generation Radio Access Network (NG-RAN) node for a User Equipment (UE); transmit a handover acknowledgement message to the source NG-RAN node, in response to receiving the handover request message; detect, after transmitting the handover acknowledgement message, an occurrence of a successful completion of the handover event between the source NG-RAN node and a target NG-RAN node; prepare a data collection update message including the requested data as per a data collection ID Information Element (IE); transmit the data collection update message to the source NG-RAN node; andtransmit, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

[0019] The apparatus as described in

[0018] , wherein prior to receive the handover request message, the apparatus is configured to: receive a data collection request message from the source NG-RAN node to initiate data collection process, wherein the data collection request message comprises the data collectionID IE, including parameters that indicate specific data to collect and conditions for gathering; and transmit a data collection response to the source NG-RAN node, in response to receiving the data collection request message.

[0020] The apparatus as described in any of

[0018] -

[0019] , wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

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

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

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

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

[0099] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and anycomponent(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.

[0100] 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

CLAIMSWe claim:

1. A method comprising: transmitting, by a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node, a handover request message to initiate a handover event of a User Equipment (UE) from the source NG-RAN node to the target NG-RAN node; determining, upon successful completion of the handover event, by the source NG- RAN node, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node; and performing, by the source NG-RAN node, one of: maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node; or releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

2. The method as claimed in claim 1, wherein at least one of the UE context release message and the data collection update message includes performance data associated with the UE, and wherein the method further comprises:prior to performing at least one, wherein one or more UE performance metrics are evaluated by the target NG-RAN node, based on the performance data included in the data collection update message; performing, by the source NG-RAN node, the at least one: determining, based on the one or more evaluated UE performance metrics, whether a handover decision process for the UE from the source NG-RAN node to a target NG-RAN node is appropriate; or validating, based on the one or more evaluated UE performance metrics from the target NG RAN node, an accuracy of at least one Artificial Intelligence (Al) model utilized for the handover decision process at the source NG RAN node.

3. The method as claimed in claim 1, wherein prior to transmitting the handover request message, the method comprises: transmitting, by the source NG-RAN node, a data collection request message to the target NG-RAN node to initiate a collection of specific data, wherein the data collection request message comprises a data collection ID, including parameters that indicate the specific data to collect and conditions for collecting the specific data; and receiving, by the source NG-RAN node, a data collection response from the target NG-RAN node, in response to transmitting the data collection request message.

4. The method as claimed in claim 1,wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; wherein the UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

5. The method as claimed in claim 1, comprising: receiving, by the source NG-RAN node, a handover acknowledgement message from the target NG-RAN node, in response to transmitting the handover request message; and detecting, upon receiving the handover acknowledgement message, by the source NG-RAN node, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node.

6. The method as claimed in claim 1, further comprising: initiating, after transmitting the handover request message, by the source NG-RAN node, a predefined timer at the source NG-RAN node; determining, by the source NG-RAN node, whether the initiated predefined timer is expired or a data collection update message is received from the target NG-RAN node; andperforming, by the source NG-RAN node, one of: maintaining a UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is not expired and the data collection update message is not received from the target NG-RAN node; releasing the UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is expired and the data collection update message is received from the target NG-RAN node; or transmitting a request to an Access and Mobility Management Function (AMF) to release the UE context, in response to determining that the initiated predefined-timer is expired and the data collection update message is not received from the target NG-RAN node.

7. The method as claimed in claim 6, further comprising: configuring, by the source NG-RAN node, a value of predefined-timer based on a value of collection time duration for UE performance IE and one or more predefined exit conditions, wherein the predefined timer comprises one of a TXn Relocation Preparation (TXnRELOCprep) and a TXn Relocation Overall (TXnRELOCoverall).

8. A method comprising:receiving, by a target Next Generation Radio Access Network (NG-RAN) node, a handover request message from a source NG-RAN node for a User Equipment (UE); transmitting, by the target NG-RAN node, a handover acknowledgement message to the source NG-RAN node, in response to receiving the handover request message; detecting, after transmitting the handover acknowledgement message, by the target NG-RAN node, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node; preparing, by the target NG-RAN node, a data collection update message including the requested data as per a data collection ID Information Element (IE); transmitting, by the target NG-RAN node, the data collection update message to the source NG-RAN node; and transmitting, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

9. The method as claimed in claim 8, wherein prior to receiving the handover request message, the method comprises: receiving, by the target NG-RAN node, a data collection request message from the source NG-RAN node to initiate data collection process, wherein the data collection request message comprises the data collectionID IE, including parameters that indicate specific data to collect and conditions for gathering; andtransmitting, by the target NG-RAN node, a data collection response to the source NG-RAN node, in response to receiving the data collection request message.

10. The method as claimed in claim 8, wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

11. An apparatus configured to: transmit a handover request message to initiate a handover of a User Equipment (UE) from a source Next Generation Radio Access Network (NG-RAN) node to a target NG-RAN node; determining, upon successful completion of the handover event, by the source NG- RAN node, whether a UE context release message is received prior to a data collection update message from the target NG-RAN node; and perform one of:maintaining a UE context at the source NG-RAN node, in response to determining that the UE context release message is received prior to the data collection update message from the target NG-RAN node; or releasing the UE context at the source NG-RAN node, in response to determining that the UE context release message receives subsequent to the data collection update message from the target NG-RAN node.

12. The apparatus as claimed in claim 11, wherein at least one of the UE context release message and the data collection update message includes performance data associated with the UE, and the apparatus further configured to: prior to perform at least one, wherein one or more UE performance metrics are evaluated by the target NG-RAN node, based on the performance data included in the data collection update message; perform the at least one: determine, based on the one or more evaluated UE performance metrics, whether a handover decision process for the UE from the source NG-RAN node to a target NG-RAN node is appropriate; or validate, based on the one or more evaluated UE performance metrics from the target NG RAN node, an accuracy of at least one Artificial Intelligence (Al) model utilized for the handover decision process at the source NG RAN node.

13. The apparatus as claimed in claim 11, wherein prior to transmitting the handover request message, the apparatus is configured to: transmit a data collection request message to the target NG-RAN node to initiate a collection of specific data, wherein the data collection request message comprises a data collection ID, including parameters that indicate the specific data to collect and conditions for collecting the specific data; and receive a data collection response from the target NG-RAN node, in response to transmitting the data collection request message.

14. The apparatus as claimed in claim 11, wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein the UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

15. The apparatus as claimed in claim 11, the apparatus is configured to: receive a handover acknowledgement message from the target NG-RAN node, in response to transmitting the handover request message; anddetect, upon receiving the handover acknowledgement message, an occurrence of a successful completion of the handover event between the source NG-RAN node and the target NG-RAN node.

16. The apparatus as claimed in claim 11, the apparatus is further configured to: initiate, after transmitting the handover request message, a predefined timer at the source NG-RAN node; determine whether the initiated predefined timer is expired or a data collection update message is received from the target NG-RAN node; and perform one of maintaining a UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is not expired and the data collection update message is not received from the target NG-RAN node; releasing the UE context at the source NG-RAN node, in response to determining that the initiated predefined timer is expired and the data collection update message is received from the target NG-RAN node; or transmitting a request to an Access and Mobility Management Function (AMF) to release the UE context, in response to determining that the initiated predefined-timer is expired and the data collection update message is not received from the target NG-RAN node.

17. The apparatus as claimed in claim 16, comprising:configure a value of predefined-timer based on a value of collection time duration for UE performance IE and one or more predefined exit conditions, wherein the predefined timer comprises one of a TXn Relocation Preparation (TXnRELOCprep) and a TXn Relocation Overall (TXnRELOCoverall).

18. An apparatus configured to: receive a handover request message from a source Next Generation Radio Access Network (NG-RAN) node for a User Equipment (UE); transmit a handover acknowledgement message to the source NG-RAN node, in response to receiving the handover request message; detect, after transmitting the handover acknowledgement message, an occurrence of a successful completion of the handover event between the source NG-RAN node and a target NG-RAN node; prepare a data collection update message including the requested data as per a data collection ID Information Element (IE); transmit the data collection update message to the source NG-RAN node; and transmit, after transmitting the data collection update message, the UE context release message to the source NG-RAN node.

19. The apparatus as claimed in claim 18, wherein prior to receive the handover request message, the apparatus is configured to:receive a data collection request message from the source NG-RAN node to initiate data collection process, wherein the data collection request message comprises the data collection ID IE, including parameters that indicate specific data to collect and conditions for gathering; and transmit a data collection response to the source NG-RAN node, in response to receiving the data collection request message.

20. The apparatus as claimed in claim 18, wherein the UE context release message indicates that one or more radio and control plane resources associated with the UE context are allowed to be released at the source NG RAN node; and wherein UE context comprises at least one of a unique identifier, session management information, Radio Resource Control (RRC) information, one or more Quality of Service (QoS) parameters, security context information, location information, and a type of service information.

Images