UE context handling for enhanced baseline mobility

Abstract

UE context handling for enhanced baseline mobility includes providing S710, to a network management entity or function, e.g. Access and Mobility Management Function (AMF), an endpoint terminal identifier, e.g. shortened temporary mobile subscriber identity (S-TMSI), related to an endpoint terminal configured with a first radio resource control (RRC) configuration, e.g. a common RRC configuration, and having completed a handover associated with an access network entity or function, e.g. gNB, at a target side of the handover. Endpoint terminal specific information corresponding to the provided endpoint terminal identifier is received S720, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration. The second RRC configuration is provided S730 to the endpoint terminal based on the endpoint terminal specific information.

Description

Technical Field Various examples of embodiments described in the subject disclosure relate to a method, apparatus, and computer program for user equipment (UE) context handling, and more specifically (but not exclusively) to UE context handling for enhanced (e.g., simplified) baseline mobility. Background Over time, an increasing extension of communication networks has taken place all over the world. Various organizations, such as the European Telecommunications Standards Institute (ETSI), the 3rd Generation Partnership Project (3GPP), Telecoms &Internet converged Services &Protocols for Advanced Networks (TISPAN), the International Telecommunication Union (ITU), 3rd Generation Partnership Project 2 (3GPP2), Internet Engineering Task Force (IETF), the IEEE (Institute of Electrical and Electronics Engineers), the WiMAX Forum and the like are working on standards or specifications for telecommunication networks and access environments. By way of example, 3GPP defines 5G Core Network Function’s (NF’s) interfaces and relevant Application Programming Interfaces (APIs) for each NF to communicate between NFs. Summary Various examples of embodiments described in the subject disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or otherwise apparent to a person skilled in the relevant art(s) from the subject disclosure. Hence, at least some examples of embodiments of the subject disclosure aim to provide (or otherwise contribute to) at least part of theses aforementioned advantages and improvements. Certain aspects of various examples of embodiments described in the subject disclosure are set forth in the claims and pertain to methods, apparatuses and computer program products in the context of UE context handling for simplified baseline mobility. At least some of aforementioned advantages and improvements may be achieved through the methods, apparatuses and non-transitory storage media as specified in the claims. Further advantages and improvements may be achieved through the methods, apparatuses and non-transitory storage media set forth in respective dependent claims. Insofar, according to various examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: provide, to a network management entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the apparatus, the apparatus being at a target side of the handover; receive endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; and provide the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. According to various examples of embodiments, the apparatus may further be caused to request the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. According to various examples of embodiments, the handover may represent a handover from a first network to a second network, wherein the second network is different from the first network; and the apparatus may be associated with the second network. According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier available at the apparatus or available at the second network and the network function to which the apparatus is associated. According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity, S-TMSI. According to various examples of embodiments, the first RRC configuration may be a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. According to various examples of embodiments, the endpoint terminal specific information may comprise user equipment, UE, radio capability information. According to various examples of embodiments, the network management entity or function may be responsible for managing endpoint terminal access to the network and endpoint terminal mobility, wherein the network management entity or function may be an Access and Mobility Management Function, AMF. According to at least some examples of embodiments, an apparatus may comprise at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: receive, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover; determine, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; and provide the determined endpoint terminal specific information to the access network entity or function. According to at least some examples of embodiments, the access network entity or function may be a gNB, gNB for future radio access technology, or a disaggregated form of gNB. According to at least some examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: receive a message from a first network, the message related to a handover of the apparatus from the first network to a second network; if the apparatus is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establish the common RRC configuration, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; and perform the handover. According to at least some examples of embodiments, the common RRC configuration may comprise at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the apparatus caused to establish the common RRC configuration may further comprise the apparatus being caused to release any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. According to at least some examples of embodiments, the apparatus may further be caused to map at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. According to various examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: request, from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the apparatus being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; receive the requested at least one of PDU session information or QoS information; and configure a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. According to various examples of embodiments, the apparatus may further be caused to perform the requesting and / or the receiving via a network management entity or function. According to various examples of embodiments, the network session management entity or function may be a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the apparatus may further be caused to perform the requesting by performing a PDU session retrieval via path switch request procedure. According to at least some examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: receive a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and provide the requested at least one of PDU session information or QoS information. According to at least some examples of embodiments, the apparatus may further be caused to perform the receiving and / or the providing via a network management entity or function. According to at least some examples of embodiments, the apparatus may be further caused to implement, at least in part, functionality of a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the apparatus may further be caused to perform the providing by performing a PDU session retrieval via path switch acknowledgement procedure. According to various examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: generate a message related to completion of a handover of the apparatus from a first network to a second network; provide the message to the second network and include the apparatus’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the apparatus’s PDU sessions established at the first network, and the QoS information comprises information about the apparatus’s QoSs established at the first network; and receive a DRB reconfiguration based on the provided message. According to various examples of embodiments, an apparatus may comprise: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, may cause the apparatus at least to: receive a message related to completion of a handover of an endpoint terminal from a first network to a second network, wherein the apparatus is associated with the second network, wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; determine which PDU session to continue for the endpoint terminal, based on the received DRB configuration; and provide a DRB reconfiguration based on the determination. Moreover, according to various examples of embodiments, an apparatus may comprise means for providing, to a network management entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the apparatus, the apparatus being at a target side of the handover; means for receiving endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; and means for providing the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. According to various examples of embodiments, the apparatus may further comprise means for requesting the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. According to various examples of embodiments, the handover may represent a handover from a first network to a second network, wherein the second network is different from the first network; and the apparatus may be associated with the second network. According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier available at the apparatus or available at the second network and the network function to which the apparatus is associated. According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity, S-TMSI. According to various examples of embodiments, the first RRC configuration may be a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. According to various examples of embodiments, the endpoint terminal specific information may comprise user equipment, UE, radio capability information. According to various examples of embodiments, the network management entity or function may be responsible for managing endpoint terminal access to the network and endpoint terminal mobility, wherein the network management entity or function may be an Access and Mobility Management Function, AMF. According to at least some examples of embodiments, an apparatus may comprise means for receiving, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover; means for determining, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; and means for providing the determined endpoint terminal specific information to the access network entity or function. According to at least some examples of embodiments, the access network entity or function may be a gNB, gNB for future radio access technology, or a disaggregated form of gNB. According to at least some examples of embodiments, an apparatus may comprise: means for receiving a message from a first network, the message related to a handover of the apparatus from the first network to a second network; if the apparatus is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establish the common RRC configuration, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; and perform the handover. According to at least some examples of embodiments, the common RRC configuration may comprise at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the apparatus may further comprise means for releasing any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. According to at least some examples of embodiments, the apparatus may further comprise means for mapping at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. According to various examples of embodiments, an apparatus may comprise: means for requesting, from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the apparatus being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; means for receiving the requested at least one of PDU session information or QoS information; and means for configuring a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. According to various examples of embodiments, the apparatus may further comprise means for requesting and / or receiving via a network management entity or function. According to various examples of embodiments, the network session management entity or function may be a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the apparatus may further comprise means for requesting by performing a PDU session retrieval via path switch request procedure. According to at least some examples of embodiments, an apparatus may comprise means for receiving a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and means for providing the requested at least one of PDU session information or QoS information. According to at least some examples of embodiments, the apparatus may further comprise means for receiving and / or providing via a network management entity or function. According to at least some examples of embodiments, the apparatus may be further caused to implement, at least in part, functionality of a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the apparatus may further comprise means for performing a PDU session retrieval via path switch acknowledgement procedure. According to various examples of embodiments, an apparatus may comprise:means for generating a message related to completion of a handover of the apparatus from a first network to a second network; means for providing the message to the second network and include the apparatus’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the apparatus’s PDU sessions established at the first network, and the QoS information comprises information about the apparatus’s QoSs established at the first network; and means for receiving a DRB reconfiguration based on the provided message. According to various examples of embodiments, an apparatus may comprise: means for receiving a message related to completion of a handover of an endpoint terminal from a first network to a second network, wherein the apparatus is associated with the second network, wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; means for determining which PDU session to continue for the endpoint terminal, based on the received DRB configuration; and means for providing a DRB reconfiguration based on the determination. Furthermore, according to at least some examples of embodiments, a method may comprise providing, to a network management entity or function an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with an access network entity or function the access network entity or function being at a target side of the handover; receiving endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; and providing the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. According to various examples of embodiments, the method may further comprise requesting the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. According to various examples of embodiments, the handover may represent a handover from a first network to a second network, wherein the second network is different from the first network; and the access network entity or function may be associated with the second network. According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier available at the access network entity or function or available at the second network and the network function to which the access network entity or function is associated. According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity, S-TMSI. According to various examples of embodiments, the first RRC configuration may be a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. According to various examples of embodiments, the endpoint terminal specific information may comprise user equipment, UE, radio capability information. According to various examples of embodiments, the network management entity or function may be responsible for managing endpoint terminal access to the network and endpoint terminal mobility, wherein the network management entity or function may be an Access and Mobility Management Function, AMF. According to at least some examples of embodiments, a method may comprise receiving, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover; determining, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; and providing the determined endpoint terminal specific information to the access network entity or function. According to at least some examples of embodiments, the access network entity or function may be a gNB, gNB for future radio access technology, or a disaggregated form of gNB. According to at least some examples of embodiments, a method may comprise receiving, at an endpoint terminal, a message from a first network, the message related to a handover of the endpoint terminal from the first network to a second network; if the endpoint terminal is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establishing the common RRC configuration, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; and performing the handover. According to at least some examples of embodiments, the common RRC configuration may comprise at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the establishing may further comprise releasing any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. According to at least some examples of embodiments, the method may further comprise mapping at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. According to various examples of embodiments, a method may comprise requesting, an access network entity or function and from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; receiving the requested at least one of PDU session information or QoS information; and configuring a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. According to various examples of embodiments, the method may further comprise performing the requesting and / or the receiving via a network management entity or function. According to various examples of embodiments, the network session management entity or function may be a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the method may further comprise performing the requesting by performing a PDU session retrieval via path switch request procedure. According to various examples of embodiments, a method may comprise receiving a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and providing the requested at least one of PDU session information or QoS information. According to various examples of embodiments, the method may further comprise performing the receiving and / or the providing via a network management entity or function. According to various examples of embodiments, the method may be applicable at a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the method may further comprise performing the providing by performing a PDU session retrieval via path switch acknowledgement procedure. According to at least some examples of embodiments, a method may comprise generating, at an endpoint terminal, a message related to completion of a handover of the endpoint terminal from a first network to a second network; providing the message to the second network and include the endpoint terminal’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and receiving a DRB reconfiguration based on the provided message. According to at least some examples of embodiments, a method may comprise receiving, at an access network entity or function, a message related to completion of a handover of an endpoint terminal from a first network to a second network, wherein the access network entity or function is associated with the second network, wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; determining which PDU session to continue for the endpoint terminal, based on the received DRB configuration; and providing a DRB reconfiguration based on the determination. Furthermore, according to various examples of embodiments, there may be provided a computer program product for a computer, including software code portions for performing the steps of any of the above-outlined methods, when said product is run on the computer. According to at least some examples of embodiments, the computer program product may include a computer-readable medium on which said software code portions are stored, and / or the computer program product may be directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures. Any one of the aspects mentioned according to the claims may facilitate UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility, thereby providing at least part of the aforementioned advantages and improvements. Examples of embodiments described in the subject disclosure may, for instance, e.g., with regard to the UE capability retrieval procedure according to various examples of embodiments of the subject disclosure, realize that it is not required to consume the radio resource to retrieve the UE radio capability. Further, apart from the target scenario described according to various examples of embodiments of the subject disclosure, the radio access network (RAN) can request and retrieve the UE radio capability from core network (CN) anytime RAN requires it, unlike the conventional procedure that the UE radio capability is obtained from CN only in the connection setup. In addition, e.g., with regard to the quality of service (QoS) configuration handling solution during handover according to various examples of embodiments of the subject disclosure, it can be realized to resolve issues in a simple manner, whilst it would require performance compromise to deliver all services into a single protocol data unit (PDU) session and single data radio bearer (DRB). Further, a complementary step may enable to resume the same QoS configuration as in source RAN. Moreover, it can be realized to resolve the issues by retaining the same QoS configuration as in source RAN, whereas UE is required to store the prior DRB configuration and report it to target RAN. Further advantages may become apparent to a person skilled in the art in view of the following. Brief Description of the Drawings Some examples of embodiments of the subject disclosure are described below, by way of illustrative and non-limiting example only, with reference to the accompanying drawings, in which: FIG. 1 (including part 1 of 2 and part 2 of 2) shows an overall procedure of baseline handover w / o network (NW) preparation with Access and Mobility Management Function (AMF) and / or User Plane Function (UPF) relocation; FIG. 2 (including part 1 of 2 and part 2 of 2) shows an additional procedure when the target RAN applies delta configuration; FIG. 3 shows problems on PDU session / QoS flow continuation during handover according to various examples of embodiments of the subject disclosure; FIG. 4 (including part 1 of 2 and part 2 of 2) shows a proposed UE radio capability retrieval procedure initiated by RAN to AMF according to various examples of embodiments of the subject disclosure; FIG. 5 (including part 1 of 2 and part 2 of 2) shows procedures on QoS configuration fallback according to various examples of embodiments of the subject disclosure; FIG. 6 (including part 1 of 2 and part 2 of 2) shows procedures on QoS configuration reporting from UE according to various examples of embodiments of the subject disclosure; FIG. 7 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 8 shows a flowchart illustrating to an example method according to various examples of embodiments of the subject disclosure; FIG. 9 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 10 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 11 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 12 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 13 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure; FIG. 14 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; FIG. 15 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; FIG. 16 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; FIG. 17 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; FIG. 18 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; FIG. 19 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure; and FIG. 20 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Detailed Description In general, two or more end points involved in a communication therebetween may be implemented as a particular type of end point (e.g., a communication station or entity or function, such as a terminal device, user equipment (UE), or other communication network element, a database, a server, host, etc.), or as one or more network elements or functions (e.g., virtualized network functions), such as communication network control elements or functions, for example access network elements like access points (APs), radio base stations (BSs), relay stations, eNBs, gNBs etc., and core network elements or functions, for example control nodes, support nodes, service nodes, gateways, user plane functions, access and mobility functions, etc.. These end points may belong to a single communication network system, different communication network systems, or a combination of at least one same communication network system and at least one different communication network system. In the following, various examples of embodiments will be described using, as an example of a communication network to which examples of embodiments may be applied, a communication network architecture based on 3GPP standards for a communication network, such as a 5G / NR, without restricting the examples of embodiments to such an architecture. It, however, is would be apparent to a person skilled in the art that the examples of embodiments may also be applied to other kinds of communication networks like 4G and / or LTE (and even 6G and higher) where mobile communication principles are integrated, e.g., Wi-Fi, worldwide interoperability for microwave access (WiMAX), Bluetooth®, personal communications services (PCS), ZigBee®, wideband code division multiple access (WCDMA), systems using ultra-wideband (UWB) technology, mobile ad-hoc networks (MANETs), wired access, etc. Furthermore, without loss of generality, the description of some examples of embodiments is related to a mobile communication network, but the subject disclosure can be extended and applied to any other type of communication network, such as a wired communication network or datacenter networking. Any examples of embodiments described in the subject disclosure are to be understood only as non-limiting and illustrative in nature. Although portions of the subject disclosure may refer to the expressions “an”, “one”, or “some” example(s) of embodiment(s) in several specific locations, this does not necessarily mean that each such reference is related to the same example(s) of embodiment(s), or that the described feature only applies to a single example of an embodiment. Individual features from different examples of embodiments may also be combined to provide other examples of embodiments. Furthermore, terms like “comprising” and “including” should be understood as not limiting the described examples of embodiments to consist of only those features that have been mentioned; such examples of embodiments can also contain features, structures, units, modules etc. that have not been specifically mentioned. A simplified system architecture of a (tele)communication network including a mobile communication system, where some examples of embodiments, are applicable may include an architecture of one or more communication networks. The one or more communication networks may include wireless access network subsystem(s) and core network(s). Such an architecture may include one or more communication network control elements or functions, access network elements, radio access network elements, access service network gateways or base transceiver stations, such as a base station (BS), an access point (AP), a NodeB (NB), an eNB, or a gNB, a distributed or a centralized unit (CU), which controls a respective coverage area orcell(s) and with which one or more communication stations such as communication elements or functions, like user devices (e.g., customer devices), mobile devices, or terminal devices, like a UE, or another device having a similar function, such as a modem chipset, a chip, a module etc., which can also be part of a station, an element, a function or an application configured to conduct a communication, such as a UE, an entity or function usable in a machine-to-machine communication architecture, or attached as a separate element to such an element, function or application capable of conducting a communication, or the like, are configured to communicate via one or more channels via one or more communication beams for transmitting several types of data in a plurality of access domains. Furthermore, (core) network elements or network functions ((core) network control elements or network functions, (core) network management elements or network functions), such as gateway network elements / functions, mobility management entities, a mobile switching center, servers, databases and the like may be included. Functions and interconnections of the described elements and functions, which also depend on the actual network type, are apparent to those skilled in the art and may be described in corresponding specifications, so that a description thereof is omitted herein. However, it is to be noted that several additional network elements and signaling links may be employed for a communication to or from an element, function or application, like a communication endpoint, a communication network control element, such as a server, a gateway, a radio network controller, and other elements of the same or other communication networks besides those described in detail herein below. It should be appreciated that according to some examples of embodiments, a so-called “liquid” or flexible network concept may be implemented where the operations and functionalities of a network element, a network function, or of another entity of the network, may be performed in different entities or functions, such as in a node, host or server, in a flexible manner. Thus, a “division of labor” between involved network elements, functions or entities may vary case by case. The subject disclosure, in some examples of embodiments, relates to UE context handling, and more specifically (but not exclusively) to UE context handling for enhanced (e.g., simplified) baseline mobility. In the first release of LTE (Rel-8) and NR (Rel-15), handover procedures were introduced, which is mandatory support for UE and so regarded as the baseline mobility management for UE in the connected mode (RRC_CONNECTED). Figure 9.2.3.2.1-1 in TS 38.300 shows the baseline handover procedures for NR without AMF / UPF relocation, which is the same as for LTE in Rel-8. After the first release of LTE and NR, mobility features were continuously evolved and increased as optional support for UE. For6G, it is likewise expected that the baseline handover mechanism is introduced as mandatory for UE in the first release of specifications. The baseline mobility supported for all 6G capable UE can be further enhanced (e.g., simplified) without the preparation phase and data forwarding, to address wide range mobility requirements for 6G. One of the variants on the baseline mobility may be to perform handover without NW preparation. In this approach, UE 110 may obtain common / dedicated RRC configurations applicable to all cells / TRPs beforehand as illustrated (in Step 0) in FIG. 1 (including parts 1 of 2 and 2 of 2; to be connected at A’ -A” and B’ - B”). Therefore, the Source RAN 120 does not have to forward any UE specific information (e.g., UE radio capability) to the Target RAN 130, unlike the NR baseline handover as in Figure 9.2.3.2.1-1 in TS 38.300. However, even though UE always have the RRC configurations applicable to all cells / TRPs, there would be a scenario that the Target RAN would benefit from applying different configuration than the basic RRC configuration. For instance, 2-layer Multiple Input Multiple Output (MIMO) is enabled (or otherwise facilitated) in the basic RRC configuration, but the Target RAN supports 4-layer MIMO and would benefit from enabling (or otherwise facilitating) 4-layer MIMO to the UE. In this case, the network can perform to reconfigure the RRC configuration for the UE 210 as shown in Steps 20 and 21 illustrated in FIG. 2 (including of parts 1 of 2 and 2 of 2; to be connected at A’ - A” and B’ - B”). Nevertheless, since this handover scheme is designed to avoid UE specific information transfer between RANs as outlined above, the Target RAN 230 does not have UE radio capability for the UE 210. As such, the Target gNB cannot have knowledge whether the different configuration can be applied for the UE 210. For instance, the Target RAN 230 cannot know if the UE 210 supports 4-layer MIMO, even though the Target RAN 230 would benefit from such configuration. Other issues potentially foreseeable in a handover mechanism without NW preparation may be how to continue PDU session(s) and QoS flow(s) upon the handover is performed. The envisaged issue is illustrated in FIG. 3 as outlined below in detail with reference to 1 to 5. 1. UE 310 obtains a baseline RRC configuration applicable to all cells / TRPs, e.g., when UE 310 establishes an RRC connection and transits to the connected mode (RRC / CM CONNECTED). The baseline RRC configuration includes a minimum set of radio bearer configurations and associated PDU session. For instance, minimum set of Signaling Radio Bearers (SRBs) (SRB0, 1 and 2) and one (default) DRB and one (default) PDU session. It may be noted that it is out of scope of the various examples of embodiments of the subject disclosure how UE 310 is provisioned with the baseline RRC configuration. 2. A set of PDU sessions and QoS flows established for UE 310 is provided by Session Management Function (SMF) 350 to RAN 320 via NGAP initial context setup procedure. 3. RAN 320 updates DRB configuration for UE 310 via RRC Reconfiguration, in accordance with the PDU session and QoS flow information provided via NGAP initial context setup procedure. For uplink (UL), QoS flow mapping to DRB is provided for UE 310 as part of SDAP configuration. 4. In addition, while UE 310 is in the connected mode, the PDU session resource may be updated, e.g., setup, modify or release PDU session(s) and QoS flow(s). For instance, an additional service (e.g., IMS voice call) is requested, which require PDU session / QoS flow update. 5. Upon the PDU session / QoS flow update is triggered via NGAP PDU session management procedure, RAN 320 further updates DRB configuration for UE 310 via RRC Reconfiguration. As can be seen in these steps, there is a scenario that QoS related configurations including PDU session, QoS flow and DRB settings are updated and different from the ones in the baseline RRC configuration, which UE 310 is initially provided with. Then, as a handover is performed without NW preparation as illustrated in 6 of FIG. 3, the following problems can be envisaged: Problem 1: How can target RAN obtain PDU session / QoS flow information at source RAN? According to the existing path switch procedure specified in TS 38.413, target RAN has to provide which PDU session can be continued in DL and which PDU session cannot be continued at target RAN. To do this, target RAN needs to know prior PDU session established at source RAN. Problem 2: Can DRB configuration (including PDU session and QoS flow mapping) be maintained at target RAN or not? Owing to the design principle to avoid NW preparation in advance of handover, there is no mechanism for target RAN and UE to synchronize the DRB configuration as source RAN. In NR and LTE, a base station can obtain a UE radio capability from the CN, if it is stored in the CN. The base station can download the UE capability from the CN, only when the UE goes to the connected mode (RRC / CM) and establishes an RRC connection. There are not any other opportunities for the base station to retrieve the UE capability from the CN. Thus, even though the target RAN needs the UE radio capability in illustrated Step 20 as shown in FIG. 2, the target RAN cannot acquire this from CN, according to the current NR and LTE standards. Yet, there is a mechanism that a base station acquires UE radio capability directly from a UE. A UE capability transfer procedure defined in 3GPP TS 38.331 shows a UE receiving a “UECapabilityEnquiry” from NW and providing “UECapabilitylnformation” to the NW. The UE capability transfer procedure can be used for the RAN to receive the UE radio capability, so that the RAN can apply the different RRC configuration on the target cell after handover. On the other hand, Frequent UE capability transfer over the air is not desirable due to the fact that the size of UE radio capabilities is colossal and thousands of octets. UE Radio Capability ID Mapping procedure is defined in 3GPP TS 38.413, where it is shown an NG-RAN node to provide a “UE RADIO CAPABILITY ID MAPPING REQUEST” to an AMF and the receive from the AMF a “UE RADIO CAPABILITY ID MAPPING RESPONSE”. This procedure is used for the NG-RAN node to request from the AMF UE Radio Capability information mapped to the UE Radio Capability ID. The assumption is that an ID is assigned for the UE Radio Capability, which is reported from the UE. This procedure can be used if such an ID mapping is used for the UE radio capability management and the capability ID is obtained from UE. In addition, this procedure also relies on information obtained from UE, which would consume the radio resource. With regards to PDU session / QoS flow continuation issues, the existing XnAP supports the procedure for a new NG-RAN node to retrieve UE context from an old NG-RAN node as illustrated in 3GPP TS 38.423, where there is shown on old NG-RAN node to receive a “RETRIEVE UE CONTEXT REQUEST” from a new NG-RAN node and to provide to the new NG-RAN node a “RETRIEVE UE CONTEXT RESPONSE”. Whilst the Retrieve UE context procedure is defined for RRC connection resume, as procedure wise, it could be used for target RAN to obtain a UE context upon handover. However, with regard to the issues identified and / or potentially foreseeable as outlined above in detail, there is room for improvement. Therefore, various examples of embodiments described in the subject disclosure provide certain advantages, for example in the form of one or more improvements that are either explicitly described herein or those otherwise apparent to a person skilled in the art from the subject disclosure. At least some example embodiments may pertain to UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility as indicated above. To address the problems as outlined above in detail, a procedure is defined herewith over the RAN - CN interface as illustrated in 21 and 22 of FIG. 4 (including parts 1 of 2 and 2 of 2; to be connected at A’ - A” and B’ - B”) according to various examples of embodiments of the subject disclosure, so that the Target RAN 430 can obtain the UE radio capability from the CN upon the target gNB’s decision to apply the target cell specific RRC configuration to UE 410. With regards to the PDU session / QoS flow continuation issue, at least the following solutions can be considered: Solution 1. Upon Handover, UE fallbacks to the baseline RRC configuration. Solution 2. UE reporting on DRB configuration as source RAN. Details are elaborated in the following according to various examples of embodiments of the subject disclosure. With reference to FIG. 4, in 20, upon handover completion, the Target RAN 430 decides to apply a different RRC configuration than the one currently configured for the UE 410. In Step 21, the Target RAN 430 requests AMF 440 to provide the UE radio capability. To do this, the Target RAN 430 provides a UE identifier to AMF 440. The UE identifier can be a temporary ID available at the Target RAN 430, e.g., a S-TMSI or another temporary ID by which AMF 440 can identify UE 410 (e.g., uniquely). In 22, upon request from the Target RAN 430, AMF 440 searches its repository (e.g., a database) for the corresponding UE radio capability linked to the UE identifier provided in 21 and transfers it to the Target RAN 430. In 23, upon retrieving the UE radio capability, the Target RAN 430 checks if the different RRC configuration the Target RAN 430 intends to apply to the UE 410 is compliant with the UE radio capability. If compliant, the different RRC configuration is provided and applied for the UE 410. Some advantages of the proposed UE capability retrieval procedure are as follows: • It does not require consuming the radio resource to retrieve the UE radio capability. • Apart from the target scenario described herein according to various examples of embodiments of the subject disclosure, the RAN can request and retrieve the UE radio capability from CN anytime RAN requires it, unlike the conventional procedure that the UE radio capability is obtained from CN only in the connection setup. With regard to Solution 1 as indicated above for the PDU session / QoS flow continuation issue, a procedure is illustrated in FIG. 5 (including parts 1 of 2 and 2 of 2; to be connected at A’ - A” and B’ - B”) according to various examples of embodiments of the subject disclosure, wherein 9, 13, 14 and 15 are highlighted. In 9, upon receiving the handover (HO) command, the UE 510 fallsback to the DRB configuration including PDU session and QoS flow information as provided in , i.e. the baseline RRC configuration. For instance, it is one (default) DRB and one (default) PDU session. Any other DRBs, PDU sessions and QoS flows established at Source RAN 520 are released. All QoS flows and PDU sessions established at Source RAN 520 are mapped into the default PDU session and default DRB. Optionally, in 13, the Target RAN 530 can request SMF 550 to retrieve PDU session and QoS information from SMF 550, which was established at Source RAN 520. For instance, this can be supported via AMF 540 by enhancing the existing path switch request procedure defined in 3GPP TS 38.413. Optionally, in 14, upon receiving request, SMF 550 can provide PDU session and QoS information to Target RAN 530 via AMF 540. Likewise, this can be supported by enhancing the existing path switch acknowledgement procedure defined in 3GPP TS 38.413. In 15, the Target RAN 530 reconfigures the DRB configuration for UE 510, in accordance with the PDU session and QoS information obtained from SMF 550 in 14. With regards to Solution 2 as indicated above, a procedure is illustrated in FIG. 6 (including parts 1 of 2 and 2 of 2; to be connected at A’ - A” and B’ - B”) according to various examples of embodiments of the subject disclosure, wherein 11 and 12 are highlighted. In 11, when UE 610 sends the HO command to Target RAN 630, UE 610 includes the DRB configuration established at Source RAN 620. It includes PDU session and QoS flow information established at Source RAN 620. In 12, from the DRB configuration provided by UE 610, Target RAN 630 can decide which PDU session is continued or not. Target RAN 630 can include accepted and rejected PDU session information in the path switch request procedure. Some advantages of the proposed QoS configuration handling solution during handover are as follows: • Solution 1 can resolve the identified issue in an enhanced (e.g., simple) manner, whilst it would require performance compromise to deliver all services into a single PDU session and single DRB. A complementary action (13 and 14) enables (or otherwise facilitates) to resume the same QoS configuration as in source RAN. • Solution 2 can resolve the identified issue by retaining the same QoS configuration as in source RAN, whereas UE is to store the prior DRB configuration and report it to target RAN. In the following, further examples of embodiments are described in relation to the aforementioned methods and / or apparatuses. Referring now to FIG. 7, there is shown a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 7, in S710, the method comprises providing, to a network management entity or function (e.g., a target AMF) an endpoint terminal identifier related to an endpoint terminal (e.g., a UE) configured with a first radio resource control, RRC, configuration (e.g., a common RRC configuration) and having completed a handover associated with an access network entity or function (e.g., agNB), the access network entity or function being at a target side of the handover. S710 may represent at least part of 21 as shown in FIG. 4. Further, in S720, the method comprises receiving endpoint terminal specific information (e.g., UE radio capability information) corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration. S720 may represent at least part of 22 as shown in FIG. 4. Additionally, in S730, the method comprises providing the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. S730 may represent at least part of 23 as shown in FIG. 4. Moreover, according to at least some examples of embodiments, the method may further comprise requesting the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. Furthermore, according to various examples of embodiments, the handover may represent a handover from a first network (e.g., a Source RAN) to a second network (e.g., a Target RAN), wherein the second network is different from the first network; and the access network entity or function may be associated with the second network. Moreover, according to at least some examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier available at the access network entity or function or available at the second network and the network function to which the access network entity or function is associated. Furthermore, according to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity, S-TMSI. Moreover, according to at least some examples of embodiments, the first RRC configuration may be a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. Furthermore, according to various examples of embodiments, the endpoint terminal specific information may comprise user equipment, UE, radio capability information. Moreover, according to at least some examples of embodiments, the network management entity or function may be responsible for managing endpoint terminal (e.g., UE) access to the network and endpoint terminal (e.g., UE) mobility, wherein the network management entity or function may be an Access and Mobility Management Function, AMF. Referring now to FIG. 8, FIG. 8 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 8, in S810, the method comprises receiving, from an access network entity or function (e.g., a gNB), an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration (e.g., a common RRC configuration) and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover. S810 may represent at least part of 21 as shown in FIG. 4. Further, in S820, the method comprises determining, by use of a database, endpoint terminal specific information (e.g., UE radio capability information) corresponding to the received endpoint terminal identifier. S820 may represent at least part of 21 as shown in FIG.4. Additionally, in S830, the method comprises providing the determined endpoint terminal specific information to the access network entity or function. S830 may represent at least part of 22 as shown in FIG.4. Moreover, according to at least some examples of embodiments, the access network entity or function may be a gNB, gNB for future radio access technology (e.g., 6G), or a disaggregated form of gNB, such as Central Unit (CU) and / or Distributed Unit (DU) including the ones for future radio access technology. Referring now to FIG. 9, FIG. 9 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 9, in S910, the method comprises receiving, at an endpoint terminal, a message (e.g., handover command) from a first network (e.g., a Source RAN), the message related to a handover of the endpoint terminal from the first network to a second network (e.g., a Target RAN). S910 may represent at least part of 8 as shown in FIG.5. If the endpoint terminal is configured with a radio resource control, RRC, configuration different from a common RRC configuration, as determined in S915 (YES in S915), the common RRC configuration is established in S920, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network S915 and S920 may represent at least part of 9 as shown in FIG.5. Additionally, in S930, the method comprises performing the handover. S930 may represent at least part of 10 as shown in FIG. 5. Furthermore, according to various examples of embodiments, the common RRC configuration may comprise at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the establishing may further comprise releasing any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. Furthermore, according to various examples of embodiments, the method may further comprise mapping at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. Referring now to FIG. 10, FIG. 10 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 10, in S1010, the method comprises requesting, at an access network entity or function (e.g., a gNB) and from a network session management entity or function (e.g., an SMF), at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network. The PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network. S1010 may represent at least part of 13 as shown in FIG. 5. In addition, in S1020, the method comprises receiving the requested at least one of PDU session information or QoS information. S1020 may represent at least part of Step 14 as shown in FIG. 5. Further, in S1030, the method comprises configuring a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. S1030 may represent at least part of Step 15 as shown in FIG. 5. Furthermore, according to various examples of embodiments, the method may further comprise performing the requesting and / or the receiving via a network management entity or function (e.g., an AMF). Further, according to various examples of embodiments, the network session management entity or function may be a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the method may further comprise performing the requesting by performing a PDU session retrieval via path switch request procedure. Referring now to FIG. 11, FIG. 11 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 11, in S1110, the method comprises receiving a request provided by an access network entity or function (e.g., a gNB) to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network. The PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network. S1110 may represent at least part of 13 as shown in FIG. 5. In addition, in Step S1120, the method comprises providing the requested at least one of PDU session information or QoS information. S1120 may represent at least part of 14 as shown in FIG. 5. Furthermore, according to various examples of embodiments, the method may further comprise performing the receiving and / or the providing via a network management entity or function (e.g., an AMF). Further, according to various examples of embodiments, the method may be applicable at a Session Management Function, SMF; the network management entity or function may be an Access and Mobility Management Function, AMF; and the method may further comprise performing the providing by performing a PDU session retrieval via path switch acknowledgement procedure. Referring now to FIG. 12, FIG. 12 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 12, in S1210, the method comprises generating, at an endpoint terminal (e.g., a UE), a message (e.g., handover command) related to completion of a handover of the endpoint terminal from a first network (e.g., Source RAN) to a second network (e.g., Target RAN). S1210 may represent at least part of 11 as shown in FIG. 6. In addition, in S1220, the method comprises providing the message to the second network and include the endpoint terminal’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information. The PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network. S1220 may represent at least part of 11 as shown in FIG. 6. Further, in S1230, the method comprises receiving a DRB reconfiguration based on the provided message. S1230 may represent at least part of 14 as shown in FIG. 6. Referring now to FIG. 13, FIG. 13 shows a flowchart illustrating an example method according to various examples of embodiments of the subject disclosure. In particular, according to FIG. 13, in S1310, the method comprises receiving, at an access network entity or function (e.g., a gNB), a message related to completion of a handover of an endpoint terminal from a first network (e.g., a Source RAN) to a second network (e.g., Target RAN). The access network entity or function is associated with the second network, the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information. The PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network. S1310 may represent at least part of 11 as shown in FIG. 6. In addition, in S1320, the method comprises determining which PDU session to continue for the endpoint terminal, based on the received DRB configuration. S1320 may represent at least part of 12 as shown in FIG. 6. Further, in S1330, the method comprises providing a DRB reconfiguration based on the determination. S1330 may represent at least part of 14 as shown in FIG. 6. Referring now to FIG. 14, FIG. 14 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 14 shows a block diagram illustrating an apparatus 1400, which may represent an access network entity or function (e.g., Target RAN) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to an access network entity or function, the access network entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1400 shown in FIG. 14 may include a processing circuitry, a processing function, a control unit or a processor 1410, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1410 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1431 and 1432 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1410. The I / O units 1431 and 1432 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1420 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1410 and / or as a working storage of the processor or processing function 1410. It is to be noted that the memory 1420 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1410 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1410 includes one or more of the following sub-portions. Sub-portion 1411 is a providing portion, which is usable as a portion for providing an endpoint terminal identifier. The portion 1411 may be configured to perform processing according to S710 of FIG. 7. Further, sub-portion 1412 is a receiving portion, which is usable as a portion for receiving endpoint terminal specific information. The portion 1412 may be configured to perform processing according to S720 of FIG. 7. Moreover, sub-portion 1413 is a providing portion, which is usable as a portion for providing a second RRC configuration. The portion 1413 may be configured to perform processing according to S730 of FIG. 7. Referring now to FIG. 15, FIG. 15 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 15 shows a block diagram illustrating an apparatus 1500, which may represent a network management entity or function (e.g., AMF) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively)UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to a network management entity or function, the network management entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1500 shown in FIG. 15 may include a processing circuitry, a processing function, a control unit or a processor 1510, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1510 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1531 and 1532 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1510. The I / O units 1531 and 1532 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1520 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1510 and / or as a working storage of the processor or processing function 1510. It is to be noted that the memory 1520 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1510 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1510 includes one or more of the following sub-portions. Sub-portion 1511 is a receiving portion, which is usable as a portion for receiving an endpoint terminal identifier. The portion 1511 may be configured to perform processing according to S810 of FIG. 8. Further, sub-portion 1512 is a determining portion, which is usable as a portion for determining endpoint terminal specific information. The portion 1512 may be configured to perform processing according to S820 of FIG. 8. Moreover, sub-portion 1513 is a providing portion, which is usable as a portion for providing determined endpoint terminal specific information. The portion 1513 may be configured to perform processing according to S830 of FIG. 8. Referring now to FIG. 16, FIG. 16 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 16 shows a block diagram illustrating an apparatus 1600, which may represent an endpoint terminal (e.g., UE) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to an endpoint terminal, the endpoint terminal may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1600 shown in FIG. 16 may include a processing circuitry, a processing function, a control unit or a processor 1610, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1610 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1631 and 1632 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1610. The I / O units 1631 and 1632 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1620 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1610 and / or as a working storage of the processor or processing function 1610. It is to be noted that the memory 1620 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1610 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1610 includes one or more of the following sub-portions. Sub-portion 1611 is a receiving portion, which is usable as a portion for receiving a message. The portion 1611 may be configured to perform processing according to S910 of FIG. 9. Further, sub-portion 1612 is an establishing portion, which is usable as a portion for establishing a common RRC configuration. The portion 1612 may be configured to perform processing according to S920 of FIG. 9. Moreover, sub-portion 1613 is a performing portion, which is usable as a portion for performing a handover. The portion 1613 may be configured to perform processing according to S930 of FIG. 9. Referring now to FIG. 17, FIG. 17 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 17 shows a block diagram illustrating an apparatus 1700, which may represent an access network entity or function (e.g., gNB) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to an access network entity or function, the access network entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1700 shown in FIG. 17 may include a processing circuitry, a processing function, a control unit or a processor 1710, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1710 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1731 and 1732 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1710. The I / O units 1731 and 1732 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1720 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1710 and / or as a working storage of the processor or processing function 1710. It is to be noted that the memory 1720 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1710 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1710 includes one or more of the following sub-portions. Sub-portion 1711 is a requesting portion, which is usable as a portion for requesting PDU session information and / or QoS information. The portion 1711 may be configured to perform processing according to S1010 of FIG. 10. Further, sub-portion 1712 is a receiving portion, which is usable as a portion for receiving requested information. The portion 1712 may be configured to perform processing according to S1020 of FIG. 10. Moreover, sub-portion 1713 is a configuring portion, which is usable as a portion for configuring a DRB reconfiguration. The portion 1713 may be configured to perform processing according to S1030 of FIG. 10. Referring now to FIG. 18, FIG. 18 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 18 shows a block diagram illustrating an apparatus 1800, which may represent a network session management entity or function (e.g., SMF) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to a network session management entity or function, the network session management entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1800 shown in FIG. 18 may include a processing circuitry, a processing function, a control unit or a processor 1810, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1810 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1831 and 1832 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1810. The I / O units 1831 and 1832 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1820 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1810 and / or as a working storage of the processor or processing function 1810. It is to be noted that the memory 1820 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1810 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1810 includes one or more of the following sub-portions. Sub-portion 1811 is a receiving portion, which is usable as a portion for receiving a request. The portion 1811 may be configured to perform processing according to S1110 of FIG. 11. Further, sub-portion 1812 is a providing portion, which is usable as a portion for providing requested information. The portion 1812 may be configured to perform processing according toS1120 of FIG. 11. Referring now to FIG. 19, FIG. 19 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 19 shows a block diagram illustrating an apparatus 1900, which may represent an endpoint terminal (e.g., UE) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to an endpoint terminal, the endpoint terminal may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 1900 shown in FIG. 19 may include a processing circuitry, a processing function, a control unit or a processor 1910, such as a CPU or the like, which is suitable to enable (or otherwise facilitate) UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 1910 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 1931 and 1932 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1910. The I / O units 1931 and 1932 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 1920 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 1910 and / or as a working storage of the processor or processing function 1910. It is to be noted that the memory 1920 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 1910 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 1910 includes one or more of the following sub-portions. Sub-portion 1911 is a generating portion, which is usable as a portion for generating a message. The portion 1911 may be configured to perform processing according to S1210 of FIG. 12. Further, sub-portion 1912 is a providing portion, which is usable as a portion for providing a message. The portion 1912 may be configured to perform processing according to S1220 of FIG. 12. Moreover, sub-portion 1913 is a receiving portion, which is usable as a portion for receiving a DRB reconfiguration. The portion 1913 may be configured to perform processing according to S1230 of FIG. 12. Referring now to FIG. 20, FIG. 20 shows a block diagram illustrating an example apparatus according to various examples of embodiments of the subject disclosure. Specifically, FIG. 20 shows a block diagram illustrating an apparatus 2000, which may represent an access network entity or function (e.g., gNB) as outlined above with reference to FIGS. 4 to 6, according to various examples of embodiments, which may participate in UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility. Furthermore, even though reference is made to an access network entity or function, the access network entity or function may be also another device or function having a similar task, such as a chipset, a chip, a module, an application etc., which can also be part of a network element or attached as a separate element to a network element, or the like. It should be understood that each block and any combination thereof may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and / or circuitry. The apparatus 2000 shown in FIG. 20 may include a processing circuitry, a processing function, a control unit or a processor 2010, such as a CPU or the like, which is suitable to enable UE context handling, and more specifically (but not exclusively)UE context handling for enhanced (e.g., simplified) baseline mobility. The processor 2010 may include one or more processing portions or functions dedicated to specific processing as described below, or the processing may be run in a single processor or processing function. Portions for executing such specific processing may be also provided as discrete elements or within one or more further processors, processing functions or processing portions, such as in one physical processor like a CPU or in one or more physical or virtual entities, for example. Reference signs 2031 and 2032 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 2010. The I / O units 2031 and 2032 may be a combined unit including communication equipment towards several entities / elements, or may include a distributed structure with a plurality of different interfaces for different entities / elements. Reference sign 2020 denotes a memory usable, for example, for storing data and programs to be executed by the processor or processing function 2010 and / or as a working storage of the processor or processing function 2010. It is to be noted that the memory 2020 may be implemented by using one or more memory portions of the same or different type of memory, but may also represent an external memory, e.g., an external database provided on a cloud server. The processor or processing function 2010 is configured to execute processing related to the above described processing. In particular, the processor or processing circuitry or function 2010 includes one or more of the following sub-portions. Sub-portion 2011 is a receiving portion, which is usable as a portion for receiving a message. The portion 2011 may be configured to perform processing according to S1310 of FIG. 13. Further, sub-portion 2012 is a determining portion, which is usable as a portion for determining which PDU session to continue. The portion 2012 may be configured to perform processing according to S1320 of FIG. 13. Moreover, sub-portion 2013 is a providing portion, which is usable as a portion for providing a DRB reconfiguration. The portion 2013 may be configured to perform processing according to S1330 of FIG. 13. It shall be noted that the apparatuses 1400, 1500, 1600, 1700, 1800, 1900 and 2000 as outlined above with reference to FIGS. 14 to 20 may comprise further / additional sub-portions, which may allow the apparatuses 1400 to 2000 to perform such methods / method as outlined above with reference to FIGS. 4 to 6. As described herein, the subject disclosure describes UE context handling, and more specifically (but not exclusively) UE context handling for enhanced (e.g., simplified) baseline mobility, which may, according to some examples of embodiments, prove advantageous over a proprietary solution for at least the following reasons. Examples of embodiments described in the subject disclosure may, for instance, e.g., with regard to the UE capability retrieval procedure according to various examples of embodiments of the subject disclosure, realize that it is not required to consume the radio resource to retrieve the UE radio capability. Further, apart from the target scenario described according to various examples of embodiments of the subject disclosure, the radio access network (RAN) can request and retrieve the UE radio capability from core network (CN) anytime RAN requires it, unlike the procedure where the UE radio capability is obtained from CN only in the connection setup. In addition, e.g., with regard to the quality of service (QoS) configuration handling solution during handover according to various examples of embodiments of the subject disclosure, it can be realized to resolve issues in an enhanced (e.g., simple, efficient) manner, whilst it would require performance compromise to deliver all services into a single protocol data unit (PDU) session and single data radio bearer (DRB). Further, a complementary step may enable (or otherwise facilitate) resume the same QoS configuration as in source RAN. Moreover, it can be realized to resolve the issues by retaining the same QoS configuration as in source RAN, whereas UE is required to store the prior DRB configuration and report it to target RAN. It should be appreciated that - an access technology via which traffic is transferred to and from an entity in the communication network may be any suitable present or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Worldwide Interoperability for Microwave Access), LTE, LTE-A, 5G, 6G, Bluetooth, Infrared, and the like may be used; additionally, examples of embodiments may also apply wired technologies, e.g., IP based access technologies like cable networks or fixed lines. - examples of embodiments suitable to be implemented as software code or portions thereof and being run using a processor or processing function are software code independent and can be specified using any known or future developed programming language, such as a high-level programming language, such as objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages etc., or a low-level programming language, such as a machine language, or an assembler. - implementation of examples of embodiments is hardware independent and may be implemented using any known or future developed hardware technology or any hybrids of these, such as a microprocessor or CPU (Central Processing Unit), MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), and / or TTL (Transistor-Transistor Logic). - examples of embodiments may be implemented as individual devices, apparatuses, units, means or functions, or in a distributed fashion, for example, one or more processors or processing functions may be used or shared in the processing, or one or more processing sections or processing portions may be used and shared in the processing, wherein one physical processor or more than one physical processor may be used for implementing one or more processing portions dedicated to specific processing as described, - an apparatus may be implemented by a semiconductor chip, a chipset, or a (hardware) module including such chip or chipset; - examples of embodiments may also be implemented as any combination of hardware and software, such as ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) or CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components. - examples of embodiments may also be implemented as computer program products, including a computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to execute a process as described in embodiments, wherein the computer usable medium may be a non-transitory medium. The term “circuitry” may refer to one or more or all of the following examples of embodiments: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.” This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device. The term “non-transitory,” as used herein, is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM). It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of the various example of embodiments of the subject disclosure. As used herein, “at least one of the following:” and “at least one of” and similar expression, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. As used herein, the expression “and / or” also means any and all combinations of the listed terms, including at least any one of the elements, at least any two or more of the elements, or at least all of the elements. As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included. Analogously, performing a step or functionality “based on A” does not indicate that the step or functionality is performed solely based on “A” as one or more additional conditions may be included. Although the subject disclosure has been described herein before with reference to various examples of embodiments thereof, the subject disclosure is not limited thereto and it will be apparent to a person skilled in the art that various modifications can be made to the subject disclosure. Some of the various examples of embodiments of the subject disclosure are listed below by way of non-limiting and illustrative example. Example Embodiment 1: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: provide, to a network management entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the apparatus, the apparatus being at a target side of the handover; receive endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; and provide the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. Example Embodiment 2: The apparatus according to Example Embodiment 1, wherein the apparatus is further caused to request the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. Example Embodiment 3: The apparatus according to Example Embodiment 1 or 2, wherein the handover represents a handover from a first network to a second network, wherein the second network is different from the first network; and the apparatus is associated with the second network. Example Embodiment 4: The apparatus according to any of Example Embodiments 1 to 3, wherein the endpoint terminal identifier is a temporary endpoint terminal identifier available at the apparatus or available at the second network and the network function to which the apparatus is associated. Example Embodiment 5: The apparatus according to Example Embodiment 4, wherein the endpoint terminal identifier is a shortened temporary mobile subscriber identity, S-TMSI. Example Embodiment 6: The apparatus according to any of Example Embodiments 1 to 5, wherein the first RRC configuration is a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. Example Embodiment 7: The apparatus according to any of Example Embodiments 1 to 6, wherein the endpoint terminal specific information comprises user equipment, UE, radio capability information. Example Embodiment 8: The apparatus according to any of Example Embodiments 1 to 7, wherein the network management entity or function is responsible for managing endpoint terminal access to the network and endpoint terminal mobility, namely, an Access and Mobility Management Function, AMF. Example Embodiment 9: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover; determine, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; and provide the determined endpoint terminal specific information to the access network entity or function. Example Embodiment 10: The apparatus according to Example Embodiment 9, wherein the access network entity or function is a gNB, gNB for future radio access technology, or a disaggregated form of gNB. Example Embodiment 11: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a message from a first network, the handover command related to a handover of the apparatus from the first network to a second network; if the apparatus is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establish the common RRC configuration, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; and perform the handover. Example Embodiment 12: The apparatus according to Example Embodiment 11, wherein the common RRC configuration comprises at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the apparatus caused to establish the common RRC configuration further comprises the apparatus being caused to release any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. Example Embodiment 13: The apparatus according to Example Embodiment 11 or 12, wherein the apparatus is further caused to map at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. Example Embodiment 14: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: request, from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the apparatus being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; receive the requested at least one of PDU session information or QoS information; and configure a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. Example Embodiment 15: The apparatus according to Example Embodiment 14, wherein the apparatus is further caused to perform the requesting and / or the receiving via a network management entity or function. Example Embodiment 16: The apparatus according to Example Embodiment 15, wherein the network session management entity or function is a Session Management Function, SMF; the network management entity or function is an Access and Mobility Management Function, AMF; and the apparatus is further caused to perform the requesting by performing a PDU session retrieval via path switch request procedure. Example Embodiment 17: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and provide the requested at least one of PDU session information or QoS information. Example Embodiment 18: The apparatus according to Example Embodiment 17, wherein the apparatus is further caused to perform the receiving and / or the providing via a network management entity or function. Example Embodiment 19: The apparatus according to Example Embodiment 18, wherein the apparatus is further caused to implement, at least in part, functionality of a Session Management Function, SMF; the network management entity or function is an Access and Mobility Management Function, AMF; and the apparatus is further caused to perform the providing by performing a PDU session retrieval via path switch acknowledgement procedure. Example Embodiment 20: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: generate a message related to completion of a handover of the apparatus from a first network to a second network; provide the message to the second network and include the apparatus’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprisesat least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the apparatus’s PDU sessions established at the first network, and the QoS information comprises information about the apparatus’s QoSs established at the first network; and receive a DRB reconfiguration based on the provided message. Example Embodiment 21: An apparatus, comprising, at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a message related to completion of a handover of an endpoint terminal from a first network to a second network, wherein the apparatus is associated with the second network, wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; determine which PDU session to continue for the endpoint terminal, based on the received DRB configuration; and provide a DRB reconfiguration based on the determination. Example Embodiment 22: A method, comprising providing, to a network management entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with an access network entity or function, the access network entity or function being at a target side of the handover; receiving endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; and providing the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information. Example Embodiment 23: The method according to Example Embodiment 22, further comprising requesting the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier. Example Embodiment 24: The method according to Example Embodiment 22 or 23, wherein the handover represents a handover from a first network to a second network, wherein the second network is different from the first network; and the access network entity or function is associated with the second network. Example Embodiment 25: The method according to any of claims 22 to 24, wherein the endpoint terminal identifier is a temporary endpoint terminal identifier available at the access network entity or function or available at the second network and the network function to which the access network entity or function is associated. Example Embodiment 26: The method according to Example Embodiment 25, wherein the endpoint terminal identifier is a shortened temporary mobile subscriber identity, S-TMSI. Example Embodiment 27: The method according to any of Example Embodiments 22 to 26, wherein the first RRC configuration is a common RRC configuration, the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network. Example Embodiment 28: The method according to any of Example Embodiments 22 to 27, wherein the endpoint terminal specific information comprises user equipment, UE, radio capability information. Example Embodiment 29: The method according to any of claims 22 to 28, wherein the network management entity or function is responsible for managing endpoint terminal access to the network and endpoint terminal mobility, namely, an Access and Mobility Management Function, AMF. Example Embodiment 30: A method, comprising receiving, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover; determining, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; and providing the determined endpoint terminal specific information to the access network entity or function. Example Embodiment 31: The method according to Example Embodiment 30, wherein the access network entity or function is a gNB, gNB for future radio access technology, or a disaggregated form of gNB. Example Embodiment 32: A method, comprising receiving, at an endpoint terminal, a message from a first network, the message related to a handover of the endpoint terminal from the first network to a second network; if the endpoint terminal is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establishing the common RRC configuration, wherein the common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / or the common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; and performing the handover. Example Embodiment 33: The method according to Example Embodiment 32, wherein the common RRC configuration comprises at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; and wherein the establishing further comprises releasing any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration. Example Embodiment 34: The method according to Example Embodiment 32 or 33, wherein the method further comprises mapping at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions. Example Embodiment 35: A method, comprising requesting, at an access network entity or function and from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; receiving the requested at least one of PDU session information or QoS information; and configuring a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information. Example Embodiment 36: The method according to Example Embodiment 35, wherein the method further comprises performing the requesting and / or the receiving via a network management entity or function. Example Embodiment 37: The method according to Example Embodiment 36, wherein the network session management entity or function is a Session Management Function, SMF; the network management entity or function is an Access and Mobility Management Function, AMF; and the method further comprises performing the requesting by performing a PDU session retrieval via path switch request procedure. Example Embodiment 38: A method, comprising receiving a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, wherein the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and providing the requested at least one of PDU session information or QoS information. Example Embodiment 39: The method according to Example Embodiment 38, wherein the method further comprises performing the receiving and / or the providing via a network management entity or function. Example Embodiment 40: The method according to Example Embodiment 39, wherein the method is applicable at a Session Management Function, SMF; the network management entity or function is an Access and Mobility Management Function, AMF; and the method further comprises performing the providing by performing a PDU session retrieval via path switch acknowledgement procedure. Example Embodiment 41: A method, comprising generating, at an endpoint terminal, a message related to completion of a handover of the endpoint terminal from a first network to a second network; providing the message to the second network and include the endpoint terminal’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; and receiving a DRB reconfiguration based on the provided message. Example Embodiment 42: A method, comprising receiving, at an access network entity or function, a message related to completion of a handover of an endpoint terminal from a first network to a second network, wherein the access network entity or function is associated with the second network, wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, and wherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information, the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, and the QoS information comprises information about the endpoint terminal’s QoSs established at the first network; determining which PDU session to continue for the endpoint terminal, based on the received DRB configuration; and providing a DRB reconfiguration based on the determination. Example Embodiment 43: A computer program product for a computer, including software code portions for performing the steps of any of Example Embodiments 22 to 29, 30 to 31, 32 to 34, 35 to 37, 38 to 40, 41, or 42, when said product is run on the computer. Example Embodiment 44: The computer program product according to Example Embodiment 43, wherein the computer program product includes a computer-readable medium on which said software code portions are stored, and / or the computer program product is directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures. The following meanings for the abbreviations used herein apply: 3GPP 3rd Generation Partnership Project 3GGP2 3rd Generation Partnership Project 2 4G Fourth Generation 5G Fifth Generation OuU 5G Core Network 6G Sixth Generation AMF Access and Mobility Management Function AP Access Point API Application Programming Interface BS Base Station CDMA Code Division Multiple Access CN Core Network DRB Data Radio Bearer eNB Evolved Node B EPC Evolved Packet Core ETSI European Telecommunications Standards Institute gNB HO Next Generation Node B Handover IEEE Institute of Electrical and Electronics Engineers ITU International Telecommunication Union L1 / L2 Layer-1 / Layer-2 LTE Long Term Evolution LTE-A Long Term Evolution-Advanced MAC Medium Access Control MANETs Mobile Ad-Hoc Networks MIMO Multiple Input Multiple Output NAS Non-Access Stratum NB Node B NF Network Function NG-RAN NG Radio Access Network NGAP NG Application Protocol NR NR Radio access NW Network PDU Protocol Data Unit PSA PDU Session Anchor RAM Random Access Memory RAN Radio Access Network Rei Release ROM Read Only Memory RRC Radio Resource Control S-TMSI shortened Temporary Mobile Subscriber Identity SDAP Service Data Adaptation Protocol SM Session Management SMF Session Management Function SRB Signaling Radio Bearer TISPAN Telecoms &Internet converged Services &Protocols for Advanced Networks TRP Transmission Reception Point UE User Equipment UL Uplink UPF User Plane Function UWB Ultra-Wideband WCDMA Wideband Code Division Multiple Access WiMAX Worldwide Interoperability for Microwave Access WLAN Wireless Local Area Network

Claims

1. A method, comprisingproviding, to a network management entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with an access network entity or function, the access network entity or function being at a target side of the handover;receiving endpoint terminal specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal specific information indicating the endpoint terminal’s capability to be configured with a second RRC configuration different from the first RRC configuration; andproviding the second RRC configuration to the endpoint terminal based on the endpoint terminal specific information.

2. The method according to claim 1, further comprisingrequesting the endpoint terminal specific information from the network management entity or function by the provision of the endpoint terminal identifier.

3. The method according to claim 1 or 2, whereinthe handover represents a handover from a first network to a second network, wherein the second network is different from the first network; andthe access network entity or function is associated with the second network.

4. The method according to any of claims 1 to 3, wherein the endpoint terminal identifier is a temporary endpoint terminal identifier available at the access network entity or function or available at the second network and the network function to which the access network entity or function is associated.

5. The method according to claim 4, wherein the endpoint terminal identifier is a shortened temporary mobile subscriber identity, S-TMSI.

6. The method according to any of claims 1 to 5, wherein the first RRC configuration is a common RRC configuration,the common RRC configuration applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / orthe common RRC configuration applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network.

7. The method according to any of claims 1 to 6, wherein the endpoint terminal specific information comprises user equipment, UE, radio capability information.

8. The method according to any of claims 1 to 7, wherein the network management entity or function is responsible for managing endpoint terminal access to the network and endpoint terminal mobility, namely, an Access and Mobility Management Function, AMF.

9. A method, comprisingreceiving, from an access network entity or function, an endpoint terminal identifier related to an endpoint terminal configured with a first radio resource control, RRC, configuration and having completed a handover associated with the access network entity or function, the access network entity or function being at a target side of the handover;determining, by use of a database, endpoint terminal specific information corresponding to the received endpoint terminal identifier; andproviding the determined endpoint terminal specific information to the access network entity or function.

10. The method according to claim 9, wherein the access network entity or function is a gNB, gNB for future radio access technology, or a disaggregated form of gNB.

11. A method, comprisingreceiving, at an endpoint terminal, a message from a first network, the message related to a handover of the endpoint terminal from the first network to a second network;if the endpoint terminal is configured with a radio resource control, RRC, configuration different from a common RRC configuration, establishing the common RRC configuration, whereinthe common RRC configuration is applicable to radio cells and / or transmission reception points, TRPs, associated with at least one of the first network or the second network, and / orthe common RRC configuration is applicable to radio cells and / or TRPs associated with access network elements or functions associated with at least one of the first network or the second network; andperforming the handover.

12. The method according to claim 11, whereinthe common RRC configuration comprises at least one default data radio bearers, DRBs, and / or at least one default protocol data unit, PDU, sessions; andwherein the establishing further comprises releasing any at least one of DRBs or PDU sessions established at the first network and different from the common RRC configuration.

13. The method according to claim 11 or 12, wherein the method further comprises mapping at least one of quality of service, QoS, flows or PDU sessions established at the first network into the at least one default DRBs and / or the at least one default PDU sessions.

14. A method, comprisingrequesting, at an access network entity or function and from a network session management entity or function, at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, whereinthe PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, andthe QoS information comprises information about the endpoint terminal’s QoSs established at the first network;receiving the requested at least one of PDU session information or QoS information; andconfiguring a data radio bearer, DRB, reconfiguration for the endpoint terminal based on the received at least one of PDU session information or QoS information.

15. The method according to claim 14, wherein the method further comprises performing the requesting and / or the receiving via a network management entity or function.

16. The method according to claim 15, whereinthe network session management entity or function is a Session Management Function, SMF;the network management entity or function is an Access and Mobility Management Function, AMF; andthe method further comprises performing the requesting by performing a PDU session retrieval via path switch request procedure.

17. A method, comprisingreceiving a request provided by an access network entity or function to provide at least one of protocol data unit, PDU, session information or quality of service, QoS, information related to an endpoint terminal having completed a handover from a first network to a second network, the access network entity or function being associated with the second network, whereinthe PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, andthe QoS information comprises information about the endpoint terminal’s QoSs established at the first network; andproviding the requested at least one of PDU session information or QoS information.

18. The method according to claim 17, wherein the method further comprises performing the receiving and / or the providing via a network management entity or function.

19. The method according to claim 18, whereinthe method is applicable at a Session Management Function, SMF;the network management entity or function is an Access and Mobility Management Function, AMF; andthe method further comprises performing the providing by performing a PDU session retrieval via path switch acknowledgement procedure.

20. A method, comprisinggenerating, at an endpoint terminal, a message related to completion of a handover of the endpoint terminal from a first network to a second network;providing the message to the second network and include the endpoint terminal’s data radio bearer, DRB, configuration established at the first network into the message, wherein the DRB configuration comprises at least one of protocol data unit, PDll, session information or quality of service, QoS, information,the PDll session information comprises information about the endpoint terminal’s PDU sessions established at the first network, andthe QoS information comprises information about the endpoint terminal’s QoSs established at the first network; andreceiving a DRB reconfiguration based on the provided message.

21. A method, comprisingreceiving, at an access network entity or function, a message related to completion of a handover of an endpoint terminal from a first network to a second network,wherein the access network entity or function is associated with the second network,wherein the message includes the endpoint terminal’s data radio bearer, DRB, configuration established at the first network, andwherein the DRB configuration comprises at least one of protocol data unit, PDU, session information or quality of service, QoS, information,the PDU session information comprises information about the endpoint terminal’s PDU sessions established at the first network, andthe QoS information comprises information about the endpoint terminal’s QoSs established at the first network;determining which PDU session to continue for the endpoint terminal, based on the received DRB configuration; andproviding a DRB reconfiguration based on the determination.

22. A computer program product for a computer, including software code portions for performing the steps of any of claims 1 to 8, 9 to 10, 11 to 13, 14 to 16, 17 to 19, 20, or 21, when said product is run on the computer.

23. The computer program product according to claim 22, whereinthe computer program product includes a computer-readable medium on which said software code portions are stored, and / or5 the computer program product is directly loadable into the internal memory of thecomputer and / or transmittable via a network by means of at least one of upload, download and push procedures.

Images