UE Context Processing for Enhanced Baseline Mobility

Abstract

The various examples of embodiments described herein relate to methods, apparatus, and computer programs for UE context processing, and more specifically (but not exclusively) to UE context processing for enhanced (e.g., simplified) baseline mobility. One such example of an embodiment relates to a method comprising: providing an endpoint terminal identifier associated with an endpoint terminal to a network management entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with an access network entity or function on the 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.

Description

Technical Field

[0001] Various examples of embodiments described in this disclosure relate to methods, apparatus, and computer programs for user equipment (UE) context processing, and more specifically (but not exclusively) to UE context processing for enhanced (e.g., simplified) baseline mobility. Background Technology

[0002] Over time, communication networks have expanded continuously around the world. Various organizations, such as the European Telecommunications Standards Institute (ETSI), the 3rd Generation Partnership Project (3GPP), the Telecommunications and Internet Convergence Services and Protocols for Advanced Networks (TISPAN), the International Telecommunication Union (ITU), 3GPP2, the Internet Engineering Task Force (IETF), IEEE (Institute of Electrical and Electronics Engineers), and the WiMAX Forum, are developing standards or specifications for telecommunications networks and access environments.

[0003] As an example, 3GPP defines the interface of the 5G core network NF and the related application programming interface (API) for each network function (NF) to enable communication between the NFs. Summary of the Invention

[0004] The various examples of embodiments described in this disclosure provide certain advantages, such as in the form of one or more improvements, which are expressly described herein or will be apparent to those skilled in the art from this disclosure. Therefore, at least some examples of embodiments of this disclosure are intended to provide (or otherwise contribute to) at least some of the aforementioned advantages and improvements.

[0005] Various aspects of the various examples of embodiments described in this disclosure are set forth in the claims and relate to methods, apparatus, and computer program products in the context of UE context processing for simplifying baseline mobility.

[0006] At least some of the foregoing advantages and improvements can be achieved by the methods, apparatus, and nontransitory storage media specified in the claims. Further advantages and improvements can be achieved by the methods, apparatus, and nontransitory storage media set forth in the corresponding dependent claims.

[0007] In this regard, according to various examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, enable the apparatus to at least: provide an endpoint terminal identifier associated with an endpoint terminal to a network management entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with the apparatus, the apparatus being located on the 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.

[0008] According to various examples of embodiments, the device can also request endpoint-specific information from a network management entity or function by providing an endpoint terminal identifier.

[0009] According to various examples of embodiments, switching can represent a switch from a first network to a second network, wherein the second network is different from the first network; and the device can be associated with the second network.

[0010] According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier that is available at the device or at a second network and network function associated with the device.

[0011] According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity (S-TMSI).

[0012] According to various examples of the embodiments, the first RRC configuration may be a public RRC configuration, which is applicable to radio cells and / or transmit receiving points (TRPs) associated with at least one of the first network and the second network, and / or the public RRC configuration is applicable to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with at least one of the first network and the second network.

[0013] According to various examples of embodiments, endpoint-specific information may include user equipment (UE) radio capability information.

[0014] According to various examples of embodiments, a 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).

[0015] According to at least some examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, enable the apparatus to at least: receive from an access network entity or function an endpoint terminal identifier associated with an endpoint terminal, the endpoint terminal being 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 located on the target side of the handover; determine endpoint terminal-specific information corresponding to the received endpoint terminal identifier using a database; and provide the determined endpoint terminal-specific information to the access network entity or function.

[0016] According to at least some examples of the embodiments, the access network entity or function may be a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

[0017] According to at least some examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, enable the apparatus to at least: receive a message from a first network, the message relating to a handover of the apparatus from the first network to a second network; establish a common RRC configuration if the apparatus is configured with an RRC configuration different from a common radio resource control (RRC) configuration, wherein the common RRC configuration applies to radio cells and / or transmit receive points (TRPs) associated with at least one of the first and second networks, and / or the common RRC configuration applies to radio cells and / or TRPs associated with at least one associated access network element or function of the first and second networks; and perform a handover.

[0018] According to at least some examples of the embodiments, the public RRC configuration may include at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and wherein enabling the device to establish the public RRC configuration may further include enabling the device to release any at least one DRB and PDU session established at the first network that is different from the public RRC configuration.

[0019] According to at least some examples of the embodiments, the apparatus may also map at least one of the Quality of Service (QoS) flows and PDU sessions established at the first network to at least one default DRB and / or at least one default PDU session.

[0020] According to various examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, may cause the apparatus to at least: request, from a network session management entity or function, at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes information about the QoS of the endpoint terminal established at the first network; receive at least one of the requested PDU session information or QoS information; and configure Data Radio Bearer (DRB) reconfiguration for the endpoint terminal based on at least one of the received PDU session information or QoS information.

[0021] According to various examples of the embodiments, the device can also perform requests and / or receive requests via network management entities or functions.

[0022] According to various examples of the 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 device may also execute the request by performing PDU session acquisition via a path change request procedure.

[0023] According to at least some examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive a request provided by an access network entity or function for providing at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the access network entity or function is associated with the second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes information about the QoS of the endpoint terminal established at the first network; and provide at least one of the requested PDU session information or QoS information.

[0024] According to at least some examples of the embodiments, the device may also perform receiving and / or providing via a network management entity or function.

[0025] According to at least some examples of the embodiments, the device may also at least partially implement the functions of the Session Management Function (SMF); the network management entity or function may be the Access and Mobility Management Function (AMF); and the device may also perform provision by performing PDU session acquisition via a path change confirmation process.

[0026] According to various examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: generate a message relating to the completion of a handover of the apparatus from a first network to a second network; provide the message to the second network, and include in the message a Data Radio Bearer (DRB) configuration of the apparatus established at the first network, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about a PDU session of the apparatus established at the first network, and the QoS information including information about the QoS of the apparatus established at the first network; and receive a DRB reconfiguration based on the provided message.

[0027] According to various examples of embodiments, an apparatus may include: at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive a message related to the 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 a Data Radio Bearer (DRB) configuration of the endpoint terminal established at the first network, and wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about a PDU session of the endpoint terminal established at the first network, and the QoS information including information about the QoS of the endpoint terminal established at the first network; determine, based on the received DRB configuration, which PDU session to continue for the endpoint terminal; and provide a DRB reconfiguration based on the determination.

[0028] Furthermore, according to various examples of embodiments, an apparatus may include: components for providing an endpoint terminal identifier associated with an endpoint terminal to a network management entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with the apparatus, the apparatus being located on the target side of the handover; components 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 components for providing the second RRC configuration to the endpoint terminal based on the endpoint terminal-specific information.

[0029] According to various examples of embodiments, the apparatus may also include components for requesting endpoint-specific information from a network management entity or function by providing an endpoint terminal identifier.

[0030] According to various examples of embodiments, switching can represent a switch from a first network to a second network, wherein the second network is different from the first network; and the device can be associated with the second network.

[0031] According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier that is available at the device or at a second network and network function associated with the device.

[0032] According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity (S-TMSI).

[0033] According to various examples of the embodiments, the first RRC configuration may be a public RRC configuration, which is applicable to radio cells and / or transmit receiving points (TRPs) associated with at least one of the first network and the second network, and / or the public RRC configuration is applicable to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with at least one of the first network and the second network.

[0034] According to various examples of embodiments, endpoint-specific information may include user equipment (UE) radio capability information.

[0035] According to various examples of embodiments, a 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).

[0036] According to at least some examples of embodiments, an apparatus may include: components for receiving an endpoint terminal identifier associated with an endpoint terminal from an access network entity or function, the endpoint terminal being 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 located on the target side of the handover; components for determining endpoint terminal-specific information corresponding to the received endpoint terminal identifier using a database; and components for providing the determined endpoint terminal-specific information to the access network entity or function.

[0037] According to at least some examples of the embodiments, the access network entity or function may be a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

[0038] According to at least some examples of embodiments, an apparatus may include: a component for receiving a message from a first network, the message being related to a handover of the apparatus from the first network to a second network; establishing a common RRC configuration if the apparatus is configured with an RRC configuration different from a common radio resource control (RRC) configuration, wherein the common RRC configuration applies to radio cells and / or transmit receive points (TRPs) associated with at least one of the first and second networks, and / or the common RRC configuration applies to radio cells and / or TRPs associated with at least one of the first and second networks' associated access network elements or functions; and performing a handover.

[0039] According to at least some examples of the embodiments, the public RRC configuration may include at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and the means may further include components for releasing any at least one of the DRB and PDU sessions established at a first network that are different from the public RRC configuration.

[0040] According to at least some examples of the embodiments, the apparatus may further include components for mapping at least one of a Quality of Service (QoS) flow and a PDU session established at a first network to at least one default DRB and / or at least one default PDU session.

[0041] According to various examples of embodiments, an apparatus may include: components for requesting, from a network session management entity or function, at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, the apparatus being associated with the second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes information about the QoS of the endpoint terminal established at the first network; components for receiving at least one of the requested PDU session information or QoS information; and components for configuring a Data Radio Bearer (DRB) reconfiguration for the endpoint terminal based on at least one of the received PDU session information or QoS information.

[0042] According to various examples of embodiments, the device may also include components for requesting and / or receiving requests via network management entities or functions.

[0043] 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 also include components for requesting PDU session acquisition by performing a path change request procedure.

[0044] According to at least some examples of embodiments, an apparatus may include: components for receiving a request provided by an access network entity or function for providing at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes QoS information about the endpoint terminal established at the first network; and components for providing at least one of the requested PDU session information or QoS information.

[0045] According to at least some examples of the embodiments, the device may also include components for receiving and / or providing via a network management entity or function.

[0046] According to at least some examples of the embodiments, the apparatus may also at least partially implement the functions of the Session Management Function (SMF); the network management entity or function may be the Access and Mobility Management Function (AMF); and the apparatus may further include components for performing PDU session acquisition via a path change confirmation process.

[0047] According to various examples of embodiments, an apparatus may include: components for generating a message related to the completion of a handover of the apparatus from a first network to a second network; components for providing a message to the second network and including a Data Radio Bearer (DRB) configuration of the apparatus established at the first network in the message, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about a PDU session of the apparatus established at the first network, and the QoS information including information about the QoS of the apparatus established at the first network; and components for receiving DRB reconfiguration based on the provided message.

[0048] According to various examples of embodiments, an apparatus may include: components for receiving a message related to the 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 a Data Radio Bearer (DRB) configuration of the endpoint terminal established at the first network, and wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about a PDU session of the endpoint terminal established at the first network, and the QoS information including information about the QoS of the endpoint terminal established at the first network; components for determining, based on the received DRB configuration, which PDU session to continue for the endpoint terminal; and components for providing a DRB reconfiguration based on the determination.

[0049] Furthermore, according to at least some examples of the embodiments, a method may include: providing an endpoint terminal identifier associated with an endpoint terminal to a network management entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with an access network entity or function on the 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 ability 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.

[0050] According to various examples of embodiments, the method may also include requesting endpoint-specific information from a network management entity or function by providing an endpoint endpoint identifier.

[0051] According to various examples of embodiments, a handover can represent a switch from a first network to a second network, wherein the second network is different from the first network; and an access network entity or function can be associated with the second network.

[0052] According to various examples of embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier that is available at an access network entity or function or at a second network and network function associated with the access network entity or function.

[0053] According to various examples of embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity (S-TMSI).

[0054] According to various examples of the embodiments, the first RRC configuration may be a public RRC configuration, which is applicable to radio cells and / or transmit receiving points (TRPs) associated with at least one of the first network and the second network, and / or the public RRC configuration is applicable to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with at least one of the first network and the second network.

[0055] According to various examples of embodiments, endpoint-specific information may include user equipment (UE) radio capability information.

[0056] According to various examples of embodiments, a 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).

[0057] According to at least some examples of the embodiments, a method may include: receiving from an access network entity or function an endpoint terminal identifier associated with an endpoint terminal, the endpoint terminal being 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 located on the target side of the handover; determining endpoint terminal-specific information corresponding to the received endpoint terminal identifier using a database; and providing the determined endpoint terminal-specific information to the access network entity or function.

[0058] According to at least some examples of the embodiments, the access network entity or function may be a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

[0059] According to at least some examples of the embodiments, a method may include: receiving a message at an endpoint terminal from a first network, the message relating to a handover of the endpoint terminal from the first network to a second network; establishing a common RRC configuration if the endpoint terminal is configured with an RRC configuration different from a common radio resource control (RRC) configuration, wherein the common RRC configuration applies to radio cells and / or transmit receive points (TRPs) associated with at least one of the first and second networks, and / or the common RRC configuration applies to radio cells and / or TRPs associated with at least one of the first and second networks' associated access network elements or functions; and performing a handover.

[0060] According to at least some examples of the embodiments, the public RRC configuration may include at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and the establishment may also include releasing any at least one DRB and PDU session established at the first network that is different from the public RRC configuration.

[0061] According to at least some examples of the embodiments, the method may further include mapping at least one of the Quality of Service (QoS) flow and PDU session established at the first network to at least one default DRB and / or at least one default PDU session.

[0062] According to various examples of embodiments, a method may include: 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 and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the access network entity or function is associated with the second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes information about the QoS of the endpoint terminal established at the first network; receiving at least one of the requested 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 the PDU session information or QoS information.

[0063] According to various examples of embodiments, the method may also include performing a request and / or receiving via a network management entity or function.

[0064] According to various examples of the 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 include performing a request by executing a PDU session acquisition via a path change request procedure.

[0065] According to various examples of embodiments, a method may include: receiving a request provided by an access network entity or function to provide at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes QoS information about the endpoint terminal established at the first network; and providing at least one of the requested PDU session information or QoS information.

[0066] According to various examples of embodiments, the method may also include receiving and / or providing via a network management entity or function.

[0067] According to various examples of embodiments, the method can be applied to a Session Management Function (SMF); the network management entity or function can be an Access and Mobility Management Function (AMF); and the method can also include providing the service by performing PDU session acquisition via a path transformation confirmation process.

[0068] According to at least some examples of embodiments, a method may include: generating at an endpoint terminal a message related to completing a handover of the endpoint terminal from a first network to a second network; providing the message to the second network, and including in the message a Data Radio Bearer (DRB) configuration of the endpoint terminal established at the first network, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about the PDU session of the endpoint terminal established at the first network, and the QoS information including information about the QoS of the endpoint terminal established at the first network; and receiving DRB reconfiguration based on the provided message.

[0069] According to at least some examples of embodiments, a method may include: receiving at an access network entity or function a message related to completing 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 a Data Radio Bearer (DRB) configuration for the endpoint terminal established at the first network, and wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information, the PDU session information including information about a PDU session established at the first network for the endpoint terminal, and the QoS information including information about the QoS established at the first network for the endpoint terminal; determining, based on the received DRB configuration, which PDU session to continue for the endpoint terminal; and providing a DRB reconfiguration based on the determination.

[0070] Furthermore, according to various examples of the embodiments, a computer program product for a computer can be provided, including software code portions for performing any of the steps of the methods described above when the product is run on a computer.

[0071] According to at least some examples of the embodiments, a computer program product may include a computer-readable medium on which software code portions are stored, and / or the computer program product may be directly loaded into the internal memory of a computer and / or may be transmitted via a network through at least one of the processes of uploading, downloading, and pushing.

[0072] Any aspect of the claims may facilitate UE context processing, and more specifically (but not exclusively) facilitate UE context processing for enhanced (e.g., simplified) baseline mobility, thereby providing at least a portion of the aforementioned advantages and improvements.

[0073] Examples of embodiments described in this disclosure, for example, pertain to the UE capability acquisition process of various examples of embodiments of this disclosure, recognizing that it is not necessary to consume radio resources to acquire UE radio capabilities. Furthermore, beyond the target scenarios described in the various examples of embodiments of this disclosure, unlike the conventional process of acquiring UE radio capabilities from the CN only during connection establishment, the Radio Access Network (RAN) can request and acquire UE radio capabilities from the Core Network (CN) when the RAN needs them. Additionally, for example, regarding the Quality of Service (QoS) configuration processing solutions during handover of various examples of embodiments of this disclosure, a simple approach can be adopted while requiring performance trade-offs to deliver all services to a single Protocol Data Unit (PDU) session and a single Data Radio Bearer (DRB). Furthermore, supplementary steps can enable the restoration of the same QoS configuration as in the source RAN. Moreover, it can be recognized that by resolving the issue by retaining the same QoS configuration as in the source RAN, the UE needs to store the previous DRB configuration and report it to the target RAN.

[0074] Other advantages will become apparent to those skilled in the art in light of the following. Attached Figure Description

[0075] The following description, with reference to the accompanying drawings, illustrates some examples of embodiments of the present disclosure by way of illustrative and non-limiting example only, wherein: Figure 1 (including part 1 of 2 and part 2 of 2) illustrates the overall process of baseline handover without network (NW) preparation in the event of Access and Mobility Management Function (AMF) and / or User Plane Function (UPF) relocation; Figure 2 (including part 1 of 2 and part 2 of 2) illustrates the additional process when incremental configuration is applied to the target RAN; Figure 3 The present invention illustrates the problem of PDU session / QoS flow continuation during handover in various examples of embodiments of the present disclosure; Figure 4 (including parts 1 and 2) illustrates a proposed UE radio capability acquisition process initiated by the RAN to the AMF according to various examples of embodiments of the present disclosure; Figure 5 (including parts 1 and 2) illustrates a process for QoS configuration fallback in various examples of embodiments according to this disclosure; Figure 6 (including parts 1 and 2) illustrates various examples of the process of reporting QoS configuration from a UE according to embodiments of the present disclosure; Figure 7 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 8A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 9 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 10 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 11 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 12 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 13 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown; Figure 14 A block diagram illustrating various examples of embodiments according to the present disclosure is shown; Figure 15 A block diagram illustrating various examples of embodiments according to the present disclosure is shown; Figure 16 A block diagram illustrating various examples of embodiments according to the present disclosure is shown; Figure 17 A block diagram illustrating various examples of embodiments according to the present disclosure is shown; Figure 18 A block diagram illustrating various examples of embodiments according to the present disclosure is shown; Figure 19 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown; and Figure 20 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown. Detailed Implementation

[0076] Typically, the two or more endpoints communicating between them can be implemented as specific types of endpoints (e.g., communication stations, entities, or functions such as terminal equipment, user equipment (UE), or other communication network elements, databases, servers, hosts, etc.), or as one or more network elements or functions (e.g., virtualized network functions), such as communication network control elements or functions, such as access network elements like access points (APs), radio base stations (BSs), relay stations, eNBs, gNBs, etc., and core network elements or functions, such as control nodes, support nodes, service nodes, gateways, user plane functions, access and mobility functions, etc. These endpoints can belong to a single communication network system, different communication network systems, or a combination of at least one identical communication network system and at least one different communication network system.

[0077] In the following description, various examples of embodiments will be used as examples of communication networks based on 3GPP standards for communication networks (such as 5G / NR) as examples of communication networks to which the embodiments can be applied, without limiting the examples of embodiments to such architectures. However, it will be apparent to those skilled in the art that the examples of embodiments can also be applied to other types of communication networks that integrate mobile communication principles, such as 4G and / or LTE (even 6G and higher), such as Wi-Fi, WiMAX, Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, Mobile Ad Hoc Networks (MANET), wired access, etc. Furthermore, without loss of generality, while the description of some examples of embodiments relates to mobile communication networks, this disclosure can be extended and applied to any other type of communication network, such as wired communication networks or data center networks.

[0078] Any examples of embodiments described in this disclosure are to be understood in a non-limiting and illustrative manner only. While portions of this disclosure may refer to “a,” “an,” or “some” examples of embodiments in several specific places, this does not necessarily mean that each such reference relates to the same example(s) of the embodiments(s), or that the described features apply only to a single example of an embodiment. Various features from different examples of embodiments may also be combined to provide other examples of embodiments. Furthermore, terms such as “comprising” and “including” should be understood not to limit the described examples of embodiments to consisting only of those features already mentioned; such examples of embodiments may also contain features, structures, units, modules, etc., not specifically mentioned.

[0079] A simplified system architecture of a (telecommunications) communication network, including a mobile communication system (some examples of which are applicable), may include the architecture of one or more communication networks. One or more communication networks may include a radio access network subsystem and a core network. 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 transceivers, such as base stations (BS), access points (APs), NodeBs (NBs), eNBs or gNBs, distributed units or centralized units (CUs) that control a corresponding coverage area or cell, and one or more communication stations configured to communicate with them via one or more channels and via one or more communication beams to transmit several types of data in multiple access domains. These one or more communication stations may be communication elements or functions, such as user equipment (e.g., client equipment), mobile devices, or terminal devices, such as UEs, or another device with similar functionality, such as modem chipsets, chips, modules, etc. This other device may also be part of a station, element, function, or application configured to perform 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 communication, or the like. In addition, it may include (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, mobile switching centers, servers, databases and the like.

[0080] The functionality and interconnection of the described elements and functions also depend on the actual network type, which will be obvious to those skilled in the art and can be described in the relevant specifications, and therefore their description is omitted here. However, it should be noted that several additional network elements and signaling links may be used for communication to or from elements, functions, or applications, such as communication endpoints, communication network control elements (such as servers, gateways, radio network controllers), and other elements of the same or other communication networks besides those described in detail below.

[0081] It should be understood that, according to some examples of the embodiments, a so-called "liquid" or flexible network concept can be implemented, in which the operation and function of network elements, network functions, or another entity of the network can be performed in a flexible manner in different entities or functions, such as in nodes, hosts, or servers. Therefore, the "division of labor" between the network elements, functions, or entities involved may vary depending on the circumstances.

[0082] In some examples of embodiments, this disclosure relates to UE context processing, and more specifically (but not exclusively) to UE context processing for enhanced (e.g., simplified) baseline mobility.

[0083] In the first versions of LTE (Rel-8) and NR (Rel-15), a handover procedure was introduced, which the UE must support and is therefore considered the UE's baseline mobility management (RRC_CONNECTED) in connected mode. (TS 38.300) Figure 9 Section 2.3.2.1-1 illustrates the NR baseline handover process without AMF / UPF relocation, which is identical to that of LTE in Rel-8. Following the first releases of LTE and NR, mobility features have continuously evolved and been added as optional support for the UE. Similarly, for 6G, a baseline handover mechanism is expected to be introduced in the first release of the specification as mandatory for the UE.

[0084] The baseline mobility supported by all 6G-capable UEs can be further enhanced (e.g., simplified) without a preparation phase and data forwarding to address the broad mobility requirements of 6G. One variation of baseline mobility could be performing a handover without NW preparation. In this approach, UE 110 can pre-obtain a public / private RRC configuration applicable to all cells / TRPs, as shown in step 0 of Figure 1 (Figure 1 includes parts 1 and 2 of 2; for connection at A'–A'' and B'–B''). Therefore, in TS 38.300... Figure 9 Unlike the NR baseline handover shown in .2.3.2.1-1, the source RAN 120 does not need to forward any UE-specific information (e.g., UE radio capabilities) to the target RAN 130.

[0085] However, even if the UE always has an RRC configuration applicable to all cells / TRPs, there may be scenarios where the target RAN benefits from applying a configuration different from the basic RRC configuration. For example, Layer 2 Multiple-Input Multiple-Output (MIMO) may be enabled (or otherwise facilitated) in the basic RRC configuration, but the target RAN supports Layer 4 MIMO and will benefit from enabling (or otherwise facilitating) Layer 4 MIMO to the UE. In this case, the network can perform a reconfiguration of the RRC configuration of UE 210, as shown in steps 20 and 21 of Figure 2 (Figure 2 includes parts 1 and 2 of 2; for connection at A'–A'' and B'–B''). However, since this handover scheme is designed to avoid UE-specific information transmission between RANs as described above, the target RAN 230 does not have the UE radio capabilities of UE 210. Therefore, the target gNB cannot know whether this different configuration can be applied to UE 210. For example, even if the target RAN 230 would benefit from this configuration, the target RAN 230 cannot know whether UE 210 supports Layer 4 MIMO.

[0086] Other potentially foreseeable problems in a handover mechanism without NW preparation could be how to continue PDU sessions and QoS flows during handover. These envisioned problems include... Figure 3 As shown below, as detailed in references 1 to 5.

[0087] For example, when UE 310 establishes an RRC connection and transitions to connected mode (RRC / CM CONNECTED), UE 310 obtains a baseline RRC configuration applicable to all cells / TRPs. The baseline RRC configuration includes a minimal set of radio bearer configurations and associated PDU sessions. For example, a minimal set of signaling radio bearers (SRBs) (SRB0, 1, and 2) and a (default) DRB and a (default) PDU session. It should be noted that how the baseline RRC configuration is provided to UE 310 is beyond the scope of the various examples of embodiments in this disclosure.

[0088] The Session Management Function (SMF) 350 provides the RAN 320 with a set of PDU sessions and QoS flows established for the UE 310 via the NGAP initial context setup procedure.

[0089] RAN 320 updates the DRB configuration of UE 310 via RRC reconfiguration based on the PDU session and QoS flow information provided via the NGAP initial context setup procedure. For uplink (UL), as part of the SDAP configuration, it provides UE 310 with a mapping of QoS flows to the DRB.

[0090] Furthermore, when the UE 310 is in connected mode, it can update PDU session resources, such as establishing, modifying, or releasing PDU sessions and QoS flows. For example, it can request additional services that require PDU session / QoS flow updates (e.g., IMS voice calls).

[0091] When a PDU session / QoS flow update is triggered via the NGAP PDU session management process, RAN 320 further updates the DRB configuration of UE 310 via RRC reconfiguration.

[0092] These steps reveal a possible scenario where QoS-related configurations, including PDU sessions, QoS flows, and DRB settings, are updated and differ from the baseline RRC configuration initially provided to the UE 310. Subsequently, when... Figure 3 As shown in Figure 6, when performing a switchover without NW preparation, the following problems can be considered: Question 1: How does the target RAN obtain PDU session / QoS flow information from the source RAN? According to the existing path transition procedure specified in TS 38.413, the target RAN must indicate which PDU sessions can continue in the DL and which PDU sessions cannot continue at the target RAN. To do this, the target RAN needs to know the previous PDU sessions established at the source RAN.

[0093] Question 2: Can the DRB configuration (including PDU sessions and QoS flow mapping) be maintained at the target RAN? Because of the design principle of avoiding NW preparation before handover, there is no mechanism to synchronize the DRB configuration of the target RAN and UE with the DRB configuration of the source RAN.

[0094] In NR and LTE, if the UE's radio capabilities are stored in the CN, the base station can obtain the UE's radio capabilities from the CN. The base station can only download UE capabilities from the CN when the UE enters connected mode (RRC / CM) and establishes an RRC connection. The base station has no other opportunity to obtain UE capabilities from the CN. Therefore, even if the target RAN needs the UE's radio capabilities in step 20 as shown in Figure 2, the target RAN cannot obtain these capabilities from the CN according to the current NR and LTE standards. However, there is a mechanism for the base station to obtain UE radio capabilities directly from the UE. The UE capability transmission procedure defined in 3GPP TS 38.331 shows the UE receiving "UECapabilityEnquiry" from the NW and providing "UECapabilityInformation" to the NW.

[0095] The UE capability transmission procedure can be used by the RAN to receive UE radio capabilities, allowing the RAN to apply different RRC configurations on the target cell after handover. On the other hand, due to the large size of UE radio capabilities (thousands of octets), frequent over-the-air UE capability transmissions are undesirable. The UE radio capability ID mapping procedure is defined in 3GPPTS 38.413, which illustrates an NG-RAN node providing a "UE radio capability ID mapping request" to the AMF and receiving a "UE radio capability ID mapping response" from the AMF. This procedure is used to map UE radio capability information from the AMF to UE radio capability IDs requested by the NG-RAN node. The assumption is that IDs are assigned to the UE radio capabilities reported by the UE. This procedure can be used if such ID mapping is used for UE radio capability management and capability IDs are obtained from the UE. Furthermore, this procedure relies on information obtained from the UE, which consumes radio resources.

[0096] Regarding the PDU session / QoS flow continuation issue, XnAP already supports the procedure for a new NG-RAN node to obtain the UE context from an old NG-RAN node, as shown in 3GPP TS 38.423. In this procedure, the old NG-RAN node receives a "Get UE Context Request" from the new NG-RAN node and provides a "Get UE Context Response" to the new NG-RAN node. Although the UE context acquisition procedure is defined for RRC connection recovery, in practice, this procedure can be used to enable the target RAN to obtain the UE context during handover.

[0097] However, there is room for improvement regarding the identified and / or potentially foreseeable problems as detailed above. Therefore, the various examples of embodiments described in this disclosure offer certain advantages, such as in the form of one or more improvements that are explicitly described herein or will be apparent to those skilled in the art from this disclosure.

[0098] At least some example embodiments may involve UE context processing, and more specifically (but not exclusively) UE context processing for enhanced (e.g., simplified) baseline mobility as described above.

[0099] To address the problems detailed above, various examples of embodiments of this disclosure define procedures on the RAN-CN interface shown in Figures 21 and 22 (Figure 4 includes parts 1 and 22 of 2; connected at A'–A'' and B'–B''), such that the target RAN 430 can obtain UE radio capabilities from the CN when the target gNB decides to apply a target cell-specific RRC configuration to the UE 410.

[0100] Regarding the PDU session / QoS flow continuation issue, at least the following solutions can be considered: Solution 1. During handover, the UE falls back to the baseline RRC configuration.

[0101] Solution 2: UE reports DRB configuration at the RAN source.

[0102] The details are described below with reference to various examples of embodiments of the present disclosure.

[0103] Referring to Figure 4, in step 20, upon completion of the handover, the target RAN 430 decides to apply an RRC configuration different from the currently configured RRC configuration for UE 410. In step 21, the target RAN 430 requests the AMF 440 to provide UE radio capabilities. To this end, the target RAN 430 provides the AMF 440 with a UE identifier. The UE identifier can be a temporary ID available at the target RAN 430, such as an S-TMSI or another temporary ID that the AMF 440 can use to uniquely identify UE 410. In step 22, based on the request from the target RAN 430, the AMF 440 searches its repository (e.g., database) for the corresponding UE radio capability linked to the UE identifier provided in step 21 and transmits it to the target RAN 430. In step 23, upon obtaining the UE radio capability, the target RAN 430 checks whether the different RRC configuration that the target RAN 430 intends to apply to UE 410 conforms to the UE radio capability. If the conditions are met, a different RRC configuration is provided and applied to UE 410.

[0104] The proposed UE capability acquisition process has the following advantages: It does not require consuming radio resources to acquire UE radio capabilities.

[0105] In addition to the target scenarios described herein, which are various examples of embodiments of this disclosure, the RAN can request and obtain UE radio capabilities from the CN at any time the RAN needs them, which is different from the conventional process of obtaining UE radio capabilities from the CN only during connection establishment.

[0106] Regarding Solution 1 indicated above for the PDU session / QoS flow continuation problem, various examples of embodiments of this disclosure are shown in Figure 5 (Figure 5 includes portions 1 and 2 of 2; connected at A'–A'' and B'–B''), where 9, 13, 14 and 15 are highlighted.

[0107] In step 9, upon receiving a handover (HO) command, UE 510 falls back to the DRB configuration, which includes PDU session and QoS flow information provided in the baseline RRC configuration. For example, it is a (default) DRB and a (default) PDU session. Any other DRBs, PDU sessions, and QoS flows established at the source RAN 520 are released. All QoS flows and PDU sessions established at the source RAN 520 are mapped to the default PDU session and default DRB.

[0108] Optionally, in step 13, the target RAN 530 may request the SMF 550 to obtain the PDU session and QoS information established at the source RAN 520 from the SMF 550. For example, this can be supported via the AMF 540 by enhancing the existing path change request procedure defined in 3GPP TS 38.413.

[0109] Optionally, in step 14, upon receiving a request, the SMF 550 can provide PDU session and QoS information to the target RAN 530 via the AMF 540. This can also be supported by enhancing the existing path change confirmation process defined in 3GPP TS 38.413.

[0110] In step 15, the target RAN 530 reconfigures the DRB configuration of UE510 based on the PDU session and QoS information obtained from SMF 550 in step 14.

[0111] Regarding solution 2 as described above, various examples of embodiments of this disclosure are shown in FIG6 (FIG6 includes part 1 and part 2 of 2; connected at A'–A'' and B'–B''), where 11 and 12 are highlighted.

[0112] In step 11, when UE 610 sends an HO command to target RAN 630, UE 610 includes the DRB configuration established at source RAN 620. This includes the PDU session and QoS flow information established at source RAN 620.

[0113] In section 12, based on the DRB configuration provided by UE 610, the target RAN 630 can determine which PDU session should continue. The target RAN 630 can include accepted and rejected PDU session information during the path change request process.

[0114] The proposed QoS configuration processing solution during handover has several advantages, as follows: Solution 1 addresses the identified problem in an enhanced (e.g., simpler) manner, while requiring a performance trade-off to deliver all services to a single PDU session and a single DRB. Supplementary actions (13 and 14) enable (or otherwise facilitate) the restoration of the same QoS configuration as in the source RAN.

[0115] Solution 2 can address the identified problem by retaining the same QoS configuration as in the source RAN, while the UE stores the previous DRB configuration and reports it to the target RAN.

[0116] In the following text, further examples of embodiments are described with respect to the foregoing methods and / or apparatus.

[0117] Now for reference Figure 7 The diagram illustrates flowcharts of example methods for various embodiments according to this disclosure.

[0118] Specifically, according to Figure 7 In S710, the method includes providing an endpoint terminal identifier associated with an endpoint terminal (e.g., UE) to a network management entity or function (e.g., a target AMF), the endpoint terminal being 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., a gNB) located on the target side of the handover.

[0119] S710 can represent at least a portion of 21 as shown in Figure 4.

[0120] Furthermore, in S720, the method includes receiving endpoint terminal-specific information (e.g., UE radio capability information) corresponding to the provided endpoint terminal identifier, which indicates that the endpoint terminal is capable of being configured with a second RRC configuration different from the first RRC configuration.

[0121] S720 can represent at least a portion of 22 as shown in Figure 4.

[0122] Additionally, in S730, the method includes providing a second RRC configuration to the endpoint terminal based on endpoint terminal-specific information.

[0123] S730 can represent at least a portion of 23 as shown in Figure 4.

[0124] Furthermore, according to at least some examples of the embodiments, the method may also include requesting endpoint-specific information from a network management entity or function by providing an endpoint endpoint identifier.

[0125] Furthermore, according to various examples of the embodiments, a handover can 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 an access network entity or function can be associated with the second network.

[0126] Furthermore, according to at least some examples of the embodiments, the endpoint terminal identifier may be a temporary endpoint terminal identifier that is available at an access network entity or function or at a second network and network function associated with the access network entity or function.

[0127] Furthermore, according to various examples of the embodiments, the endpoint terminal identifier may be a shortened temporary mobile subscriber identity (S-TMSI).

[0128] Furthermore, according to at least some examples of the embodiments, the first RRC configuration may be a public RRC configuration, which is applicable to radio cells and / or transmit receiving points (TRPs) associated with at least one of the first network and the second network, and / or the public 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 and the second network.

[0129] Furthermore, according to various examples of embodiments, endpoint terminal-specific information may include user equipment (UE) radio capability information.

[0130] Furthermore, according to at least some examples of the embodiments, a network management entity or function may be responsible for managing the access of an endpoint terminal (e.g., a UE) to the network and the mobility of the endpoint terminal (e.g., a UE), wherein the network management entity or function may be an Access and Mobility Management Function (AMF).

[0131] Now for reference Figure 8 , Figure 8 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0132] Specifically, according to Figure 8 In S810, the method includes receiving an endpoint terminal identifier associated with an endpoint terminal from an access network entity or function (e.g., gNB), the endpoint terminal being 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 located on the target side of the handover.

[0133] S810 can represent at least a portion of 21 as shown in Figure 4.

[0134] Furthermore, in S820, the method includes using a database to determine endpoint terminal-specific information (e.g., UE radio capability information) corresponding to the received endpoint terminal identifier.

[0135] S820 can represent at least a portion of 21 as shown in Figure 4.

[0136] Additionally, in S830, the method includes providing the determined endpoint terminal-specific information to the access network entity or function.

[0137] S830 can represent at least a portion of 22 as shown in Figure 4.

[0138] Furthermore, according to at least some examples of the embodiments, the access network entity or function may be a gNB, a gNB for future radio access technologies (e.g., 6G), or a de-aggregated form of a gNB, such as a central unit (CU) and / or a distributed unit (DU), including a CU and / or a DU for future radio access technologies.

[0139] Now for reference Figure 9 , Figure 9 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0140] Specifically, according to Figure 9 In S910, the method includes receiving a message (e.g., a handover command) at an endpoint terminal from a first network (e.g., a source RAN), the message being related to a handover of the endpoint terminal from the first network to a second network (e.g., a target RAN).

[0141] As shown in Figure 5, S910 can represent at least a part of 8.

[0142] If, as determined in S915, the endpoint terminal is configured with an RRC configuration different from the public radio resource control (RRC) configuration ("Yes" in S915), then a public RRC configuration is established in S920, wherein the public RRC configuration applies to radio cells and / or transmit receiving points (TRPs) associated with at least one of the first and second networks, and / or the public RRC configuration applies to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with at least one of the first and second networks.

[0143] S915 and S920 can represent at least a portion of 9 as shown in Figure 5.

[0144] Additionally, in S930, the method includes performing a switch.

[0145] S930 can represent at least a portion of 10 as shown in Figure 5.

[0146] Furthermore, according to various examples of embodiments, the public RRC configuration may include at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and the establishment may also include releasing any at least one DRB and PDU session established at the first network that is different from the public RRC configuration.

[0147] Furthermore, according to various examples of the embodiments, the method may also include mapping at least one of the Quality of Service (QoS) flow and PDU session established at the first network to at least one default DRB and / or at least one default PDU session.

[0148] Now for reference Figure 10 , Figure 10 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0149] Specifically, according to Figure 10 In S1010, the method includes requesting at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, both at an access network entity or function (e.g., gNB) and from a network session management entity or function (e.g., SMF), where the access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and the QoS information includes QoS information about the endpoint terminal established at the first network.

[0150] S1010 can represent at least a portion of 13 as shown in Figure 5.

[0151] Furthermore, in S1020, the method includes receiving at least one of the requested PDU session information or QoS information.

[0152] S1020 can represent at least a portion of step 14 as shown in Figure 5.

[0153] Furthermore, in S1030, the method includes configuring data radio bearer DRB reconfiguration for the endpoint terminal based on at least one received PDU session information or QoS information.

[0154] S1030 can represent at least a portion of step 15 as shown in Figure 5.

[0155] Furthermore, according to various examples of embodiments, the method may also include performing requests and / or receiving via a network management entity or function (e.g., AMF).

[0156] Furthermore, according to various examples of the 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 also include performing a request by performing a PDU session acquisition via a path change request procedure.

[0157] Now for reference Figure 11 , Figure 11 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0158] Specifically, according to Figure 11In S1110, the method includes 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 and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network. The access network entity or function is associated with the second network. The PDU session information includes information about a PDU session of the endpoint terminal established at the first network, and the QoS information includes QoS information about the endpoint terminal established at the first network.

[0159] S1110 can represent at least a portion of 13 as shown in Figure 5.

[0160] Furthermore, in step S1120, the method includes providing at least one of the requested PDU session information or QoS information.

[0161] S1120 can represent at least a portion of 14 as shown in Figure 5.

[0162] Furthermore, according to various examples of embodiments, the method may also include receiving and / or providing via a network management entity or function (e.g., AMF).

[0163] Furthermore, according to various examples of the embodiments, the method can be applied to a Session Management Function (SMF); the network management entity or function can be an Access and Mobility Management Function (AMF); and the method can also include providing the service by performing PDU session acquisition via a path transformation confirmation process.

[0164] Now for reference Figure 12 , Figure 12 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0165] Specifically, according to Figure 12 In S1210, the method includes generating a message (e.g., a handover command) at the endpoint terminal (e.g., UE) related to the completion of the handover of the endpoint terminal from a first network (e.g., source RAN) to a second network (e.g., target RAN).

[0166] S1210 can represent at least a portion of 11 as shown in Figure 6.

[0167] Furthermore, in S1220, the method includes providing a message to the second network and including the data radio bearer (DRB) configuration of the endpoint terminal established at the first network in the message, wherein the DRB configuration includes at least one of protocol data unit (PDU) session information or quality of service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and the QoS information includes QoS information about the endpoint terminal established at the first network.

[0168] S1220 can represent at least a portion of 11 as shown in Figure 6.

[0169] Furthermore, in S1230, the method includes receiving DRB reconfiguration based on the provided message.

[0170] S1230 can represent at least a portion of 14 as shown in Figure 6.

[0171] Now for reference Figure 13 , Figure 13 A flowchart illustrating various examples of methods according to embodiments of the present disclosure is shown.

[0172] Specifically, according to Figure 13 In S1310, the method includes receiving, at an access network entity or function (e.g., gNB), a message related to the completion of a handover of an endpoint terminal from a first network (e.g., a source RAN) to a second network (e.g., a target RAN). The access network entity or function is associated with the second network, and the message includes a Data Radio Bearer (DRB) configuration for the endpoint terminal established at the first network. The DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and the QoS information includes information about the QoS of the endpoint terminal established at the first network.

[0173] S1310 can represent at least a portion of 11 as shown in Figure 6.

[0174] Furthermore, in S1320, the method includes determining which PDU session to continue for the endpoint terminal based on the received DRB configuration.

[0175] S1320 can represent at least a portion of 12 as shown in Figure 6.

[0176] Furthermore, in S1330, the method includes providing DRB reconfiguration based on this determination.

[0177] S1330 can represent at least a portion of 14 as shown in Figure 6.

[0178] Now for reference Figure 14 , Figure 14 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0179] Specifically, Figure 14 Block diagrams illustrating various examples of apparatus 1400 according to embodiments are shown. This apparatus may represent an access network entity or function (e.g., a target RAN) as outlined above with reference to Figures 4 to 6. This apparatus may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even when referring to an access network entity or function, the access network entity or function may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., which may also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0180] Figure 14 The illustrated apparatus 1400 may include processing circuitry, processing functions, control units, or a processor 1410, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1410 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1431 and 1432 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1410. I / O units 1431 and 1432 may be combined units including communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1420 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1410 and / or as working storage for the processor or processing function 1410. It should be noted that memory 1420 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0181] The processor or processing function 1410 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1410 includes one or more of the following sub-parts. Sub-part 1411 is a providing part that can be used to provide an endpoint terminal identifier. Part 1411 can be configured to... Figure 7 The S710 performs the processing. Furthermore, sub-section 1412 is a receiving section, which can be used to receive terminal-specific information. Section 1412 can be configured according to... Figure 7 The S720 performs the processing. Furthermore, sub-section 1413 is a providing section, which can be used as a section for providing a second RRC configuration. Section 1413 can be configured to... Figure 7 The S730 performs the processing.

[0182] Now for reference Figure 15 , Figure 15 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0183] Specifically, Figure 15 Block diagrams illustrating various examples of apparatus 1500 according to embodiments are shown. This apparatus may represent a network management entity or function (e.g., AMF) as outlined above with reference to Figures 4-6. This apparatus may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even when referring to a network management entity or function, the network management entity or function may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., which may also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0184] Figure 15The illustrated apparatus 1500 may include processing circuitry, processing functions, control units, or a processor 1510, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1510 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1531 and 1532 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1510. I / O units 1531 and 1532 may be combined units including communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1520 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1510 and / or as working storage for the processor or processing function 1510. It should be noted that memory 1520 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0185] The processor or processing function 1510 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1510 includes one or more of the following sub-parts. Sub-part 1511 is a receiving part, which can be used as a part for receiving an endpoint terminal identifier. Part 1511 can be configured to... Figure 8 The S810 performs the processing. Furthermore, sub-part 1512 is a determination part, which can be used to determine endpoint terminal-specific information. Part 1512 can be configured to... Figure 8 The S820 performs the processing. Furthermore, sub-section 1513 is a providing section, which can be used to provide specific endpoint terminal-specific information. Section 1513 can be configured to... Figure 8 The S830 performs the processing.

[0186] Now for reference Figure 16 , Figure 16 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0187] Specifically, Figure 16Block diagrams illustrating various examples of embodiments of an apparatus 1600 that can represent an endpoint terminal (e.g., a UE) as outlined above with reference to Figures 4 to 6, which can participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even with reference to an endpoint terminal, the endpoint terminal can be another device or function with similar tasks, such as a chipset, chip, module, application, etc., and can also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof can be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0188] Figure 16 The illustrated apparatus 1600 may include processing circuitry, processing functions, control units, or a processor 1610, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1610 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1631 and 1632 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1610. I / O units 1631 and 1632 may be combined units comprising communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1620 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1610 and / or as working storage for the processor or processing function 1610. It should be noted that memory 1620 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0189] The processor or processing function 1610 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1610 includes one or more of the following sub-parts. Sub-part 1611 is a receiving part, which can be used as a part for receiving messages. Part 1611 can be configured to... Figure 9The S910 performs the processing. Furthermore, sub-section 1612 is a setup section, which can be used to establish a common RRC configuration. Section 1612 can be configured to... Figure 9 The S920 performs the processing. Furthermore, sub-section 1613 is an execution section, which can be used as a section for execution switching. Section 1613 can be configured to... Figure 9 The S930 performs the processing.

[0190] Now for reference Figure 17 , Figure 17 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0191] Specifically, Figure 17 Block diagrams illustrating various examples of apparatus 1700 according to embodiments are shown. This apparatus may represent an access network entity or function (e.g., a gNB) as outlined above with reference to Figures 4 to 6. This apparatus may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even when referring to an access network entity or function, the access network entity or function may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., which may also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0192] Figure 17The illustrated apparatus 1700 may include processing circuitry, processing functions, control units, or a processor 1710, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1710 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1731 and 1732 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1710. I / O units 1731 and 1732 may be combined units including communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1720 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1710 and / or as working storage for the processor or processing function 1710. It should be noted that memory 1720 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0193] The processor or processing function 1710 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1710 includes one or more of the following sub-parts. Sub-part 1711 is a request part, which can be used to request PDU session information and / or QoS information. Part 1711 can be configured to... Figure 10 S1010 performs the processing. Furthermore, sub-section 1712 is a receiving section, which can be used as a section for receiving requested information. Section 1712 can be configured to... Figure 10 S1020 performs the processing. Furthermore, subsection 1713 is a configuration section, which can be used to configure DRB reconfiguration. Section 1713 can be configured to... Figure 10 The S1030 process is executed.

[0194] Now for reference Figure 18 , Figure 18 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0195] Specifically, Figure 18Block diagrams illustrating various examples of apparatus 1800 according to embodiments are shown. This apparatus may represent a network session management entity or function (e.g., SMF) as outlined above with reference to Figures 4-6. This apparatus may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even when referring to a network session management entity or function, the network session management entity or function may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., which may also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0196] Figure 18 The illustrated apparatus 1800 may include processing circuitry, processing functions, control units, or a processor 1810, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1810 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1831 and 1832 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1810. I / O units 1831 and 1832 may be combined units comprising communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1820 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1810 and / or as working storage for the processor or processing function 1810. It should be noted that memory 1820 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0197] The processor or processing function 1810 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1810 includes one or more of the following sub-parts. Sub-part 1811 is a receiving part, which can be used as a part for receiving requests. Part 1811 can be configured to... Figure 11S1110 performs the processing. Furthermore, sub-part 1812 is a providing part, which can be used to provide the requested information. Part 1812 can be configured to... Figure 11 The S1120 process is executed.

[0198] Now for reference Figure 19 , Figure 19 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0199] Specifically, Figure 19 Block diagrams illustrating various examples of embodiments of an apparatus 1900 that may represent an endpoint terminal (e.g., a UE) as outlined above with reference to Figures 4 to 6, which may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even with reference to an endpoint terminal, the endpoint terminal may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., and may be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0200] Figure 19The illustrated apparatus 1900 may include processing circuitry, processing functions, control units, or a processor 1910, such as a CPU, adapted to enable (or otherwise facilitate) UE context processing, and more specifically (but not exclusively) for enhanced (e.g., simplified) baseline mobility UE context processing. The processor 1910 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 1931 and 1932 denote input / output (I / O) units or functions (interfaces) connected to the processor or processing function 1910. I / O units 1931 and 1932 may be combined units comprising communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 1920 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 1910 and / or as working storage for the processor or processing function 1910. It should be noted that memory 1920 can be implemented using one or more memory portions of the same or different types of memory, but it can also refer to external memory, such as an external database provided on a cloud server.

[0201] The processor or processing function 1910 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 1910 includes one or more of the following sub-parts. Sub-part 1911 is a generation part, which can be used as a part for generating messages. Part 1911 can be configured to... Figure 12 S1210 performs the processing. Furthermore, sub-part 1912 is a providing part, which can be used as a part for providing messages. Part 1912 can be configured to... Figure 12 S1220 performs the processing. Furthermore, sub-section 1913 is a receiving section, which can be used as a section for receiving DRB reconfiguration. Section 1913 can be configured according to... Figure 12 The S1230 process is executed.

[0202] Now for reference Figure 20 , Figure 20 Block diagrams illustrating various examples of devices according to embodiments of the present disclosure are shown.

[0203] Specifically, Figure 20Block diagrams illustrating various examples of an apparatus 2000 according to embodiments are shown. This apparatus may represent an access network entity or function (e.g., a gNB) as outlined above with reference to Figures 4 to 6. This apparatus may participate in UE context processing and, more specifically (but not exclusively), in UE context processing for enhanced (e.g., simplified) baseline mobility. Furthermore, even when referring to an access network entity or function, the access network entity or function may be another device or function with similar tasks, such as a chipset, chip, module, application, etc., which may also be part of a network element or attached to a network element as a separate element. It should be understood that each block and any combination thereof may be implemented by various means or combinations thereof, such as hardware, software, firmware, one or more processors and / or circuitry.

[0204] Figure 20 The apparatus 2000 shown may include processing circuitry, processing functions, control units, or processor 2010, such as a CPU, adapted to implement UE context processing, and more specifically (but not exclusively) to implement UE context processing for enhanced (e.g., simplified) baseline mobility. Processor 2010 may include one or more processing portions or functions dedicated to a particular processing as described below, or the processing may run in a single processor or processing function. For example, the portion for performing such particular processing may also be provided as a discrete element, or within one or more other processors, processing functions, or processing portions, such as in a physical processor (e.g., a CPU) or in one or more physical or virtual entities. Reference numerals 2031 and 2032 denote input / output (I / O) units or functions (interfaces) connected to processor or processing function 2010. I / O units 2031 and 2032 may be combined units including communication devices for several entities / elements, or may include a distributed structure having multiple different interfaces for different entities / elements. Reference numeral 2020 indicates memory that can be used, for example, to store data and programs to be executed by the processor or processing function 2010 and / or as working storage for the processor or processing function 2010. It should be noted that memory 2020 can be implemented using one or more memory portions of the same or different types of memory, but can also refer to external memory, such as an external database provided on a cloud server.

[0205] The processor or processing function 2010 is configured to perform processing related to the aforementioned processing. Specifically, the processor or processing circuitry or function 2010 includes one or more of the following sub-parts. Sub-part 2011 is a receiving part, which can be used as a part for receiving messages. Part 2011 can be configured to... Figure 13S1310 performs the processing. Furthermore, sub-section 2012 is a determination section, which can be used to determine which PDU session to continue. Section 2012 can be configured to... Figure 13 S1320 performs the processing. Furthermore, sub-part 2013 is a providing part, which can be used as a part to provide DRB reconfiguration. Part 2013 can be configured to... Figure 13 The S1330 process is executed.

[0206] It should be noted that, as referenced above... Figures 14 to 20 The devices 1400, 1500, 1600, 1700, 1800, 1900 and 2000 described herein may include other / additional sub-parts that enable the devices 1400 to 2000 to perform the methods / these methods as described above with reference to Figures 4 to 6.

[0207] As described herein, this disclosure describes UE context processing, and more specifically (but not exclusively) describes UE context processing for enhanced (e.g., simplified) baseline mobility, which, according to some examples of embodiments, can prove superior to proprietary solutions for at least the following reasons.

[0208] Examples of embodiments described in this disclosure can be used, for example, to illustrate the UE capability acquisition process of various examples of embodiments of this disclosure, recognizing that it is not necessary to consume radio resources to acquire UE radio capabilities. Furthermore, in addition to the target scenarios described in the various examples of embodiments of this disclosure, unlike the process of acquiring UE radio capabilities from the CN only during connection establishment, the Radio Access Network (RAN) can request and acquire UE radio capabilities from the Core Network (CN) when the RAN needs them. Furthermore, for example, regarding the Quality of Service (QoS) configuration processing solutions during handover of various examples of embodiments of this disclosure, the problem can be addressed in an enhanced (e.g., simple, efficient) manner, while requiring performance trade-offs to deliver all services to a single Protocol Data Unit (PDU) session and a single Data Radio Bearer (DRB). Furthermore, supplementary steps can enable (or otherwise facilitate) the restoration of the same QoS configuration as in the source RAN. Moreover, it can be recognized that by resolving the problem by retaining the same QoS configuration as in the source RAN, the UE needs to store the previous DRB configuration and report it to the target RAN.

[0209] It should be understood that The access technology that transmits services to and from entities in the communication network can be any suitable current or future technology, such as WLAN (Wireless Local Access Network), WiMAX (Global Microwave Access Interoperability), LTE, LTE-A, 5G, 6G, Bluetooth, infrared, etc.; in addition, examples of embodiments may also apply wired technologies, such as IP-based access technologies, such as cable networks or fixed lines.

[0210] Examples of embodiments suitable for implementation as software code or a portion thereof and for operation using a processor or processing capabilities are independent of software code and can be specified using any known or future-developed programming language, such as high-level programming languages ​​like Objective-C, C, C++, C#, Java, Python, Javascript, other scripting languages, etc., or low-level programming languages ​​such as machine language or assemblers.

[0211] The implementation of the examples is hardware-independent and can be implemented using any known or future-developed hardware technology or any combination thereof, such as microprocessors or CPUs (central processing units), MOS (metal-oxide-semiconductor), CMOS (complementary MOS), BiMOS (bipolar MOS), BiCMOS (bipolar CMOS), ECL (emitter-coupled logic), and / or TTL (transistor-transistor logic).

[0212] Examples of the embodiments can be implemented as individual devices, apparatuses, units, components, or functions, or in a distributed manner. For example, one or more processors or processing functions may be used or shared in a process, or one or more processing segments or processing portions may be used and shared in a process, wherein one or more physical processors may be used to implement one or more processing portions dedicated to the particular processing described.

[0213] The device can be implemented by a semiconductor chip, a chipset, or a (hardware) module that includes such a chip or chipset; Examples of the embodiments can also be implemented as any combination of hardware and software, such as ASIC (application-specific IC (integrated circuit)) components, FPGA (field-programmable gate array) or CPLD (complex programmable logic device) components or DSP (digital signal processor) components.

[0214] Examples of the embodiments can also be implemented as computer program products, including a computer-usable medium embodying computer-readable program code adapted to perform the processes described in the embodiments, wherein the computer-usable medium may be a non-transitory medium.

[0215] The term "circuit" may refer to one or more of the following examples from the embodiments: Hardware circuit implementation only (such as implementation with purely analog and / or digital circuits) and A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device such as a mobile phone or server to perform various functions); and (Multiple) hardware circuits and / or (multiple) processors (such as (multiple) microprocessors or a portion thereof) that require software (e.g., firmware) to operate, but which may be absent when no software is required to operate.

[0216] This definition of "circuit" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit" also covers only hardware circuitry or processors (or processors), a portion of hardware circuitry or processors, and their accompanying software and / or firmware implementations. For example, where applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0217] As used herein, the term “non-transient” refers to a limitation on the medium itself (e.g., tangible rather than signaling), rather than a limitation on the persistence of data storage (e.g., RAM vs. ROM).

[0218] It should be understood that although the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of various examples of embodiments of this disclosure, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0219] As used herein, “at least one of the following” and “at least one of” and similar expressions (where a list of two or more elements is connected 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 of the elements. As used herein, the expression “and / or” also means any and all combinations of the listed terms, including at least any one element, at least any two or more elements, or at least all of the elements.

[0220] As used herein, unless explicitly stated otherwise, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps. Similarly, performing a step or function “based on A” does not indicate that the step or function is performed solely based on “A”, as it may include one or more additional conditions.

[0221] Although this disclosure has been described herein with reference to various examples of its embodiments, this disclosure is not limited thereto, and it will be apparent to those skilled in the art that various modifications can be made to this disclosure.

[0222] Some examples of embodiments of this disclosure are shown below by way of non-limiting and illustrative examples.

[0223] Example 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 device to at least: Provide network management entities or functions with an endpoint terminal identifier associated with the endpoint terminal, which is configured with a first Radio Resource Control (RRC) configuration and has completed a handover associated with the device, which is on the 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 The second RRC configuration is provided to the endpoint terminal based on the endpoint terminal's specific information.

[0224] Example 2: The apparatus according to Example 1, wherein the apparatus is further configured to: By providing the endpoint terminal identifier, you can request specific information about the endpoint terminal from the network management entity or function.

[0225] Example 3: The apparatus according to Example 1 or 2, wherein This switch represents a switch from a first network to a second network, wherein the second network is different from the first network; and The device is associated with the second network.

[0226] Example 4: An apparatus according to any one of Example 1 to 3, wherein the endpoint terminal identifier is a temporary endpoint terminal identifier that is available at the apparatus or at a second network and network function associated with the apparatus.

[0227] Example 5: The apparatus according to Example 4, wherein the endpoint terminal identifier is a shortened temporary mobile subscriber identity (S-TMSI).

[0228] Example 6: An apparatus according to any one of Example 1 to 5, wherein the first RRC configuration is a common RRC configuration. This public RRC configuration applies to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first and second networks, and / or The public RRC configuration applies to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with the first network and the second network.

[0229] Example 7: An apparatus according to any one of Example 1 to 6, wherein the endpoint terminal-specific information includes user equipment (UE) radio capability information.

[0230] Example 8: An apparatus according to any one of Example 1 to 7, wherein the network management entity or function, namely the access and mobility management function (AMF), is responsible for managing the access of endpoint terminals to the network and the mobility of endpoint terminals.

[0231] Example 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 device to at least: Receive an endpoint terminal identifier associated with an endpoint terminal from an access network entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with the access network entity or function on the target side of the handover. By using a database, endpoint-specific information corresponding to the received endpoint terminal identifier is determined; and Provide the determined endpoint terminal-specific information to the access network entity or function.

[0232] Example 10: The apparatus according to Example 9, wherein the access network entity or function is a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

[0233] Example 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 device to at least: The message received from the first network is a handover command related to the device's handover from the first network to the second network; If the device is configured with an RRC configuration different from the Public Radio Resource Control (RRC) configuration, then the public RRC configuration is established, wherein... This public RRC configuration applies to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first and second networks, and / or The public RRC configuration applies to radio cells and / or TRPs associated with at least one access network element or function in the first network and the second network; and Perform the switch.

[0234] Example 12: The apparatus according to Example 11, wherein The public RRC configuration includes at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and The process of enabling the device to establish the public RRC configuration also includes enabling the device to release any at least one of the DRB and PDU sessions established at the first network that are different from the public RRC configuration.

[0235] Example 13: An apparatus according to Example 11 or 12, wherein the apparatus is further configured to map at least one of a Quality of Service (QoS) flow and a PDU session established at a first network to at least one default DRB and / or at least one default PDU session.

[0236] Example 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 device to at least: The device is associated with the second network by requesting at least one of the following: Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from the first network to the second network, from a network session management entity or function request. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Receive at least one of the requested PDU session information or QoS information; and Based on at least one of the received PDU session information or QoS information, configure the data radio bearer DRB reconfiguration for the endpoint terminal.

[0237] Example 15: The apparatus according to Example 14, wherein the apparatus is further configured to perform requests and / or receptions via a network management entity or function.

[0238] Example 16: The apparatus according to Example 15, wherein The network session management entity or function is the Session Management Function (SMF); The network management entity or function is the Access and Mobility Management Function (AMF); and It also enables the device to execute the request by performing a PDU session acquisition via a path transformation request process.

[0239] Example 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 device to at least: The system receives a request from an access network entity or function to provide at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network. The access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; and Provide at least one of the requested PDU session information or QoS information.

[0240] Example 18: The apparatus according to Example 17, wherein the apparatus is further configured to perform receiving and / or providing via a network management entity or function.

[0241] Example 19: The apparatus according to Example 18, wherein This also enables the device to at least partially implement the Session Management Function (SMF) functionality; The network management entity or function is the Access and Mobility Management Function (AMF); and It also enables the device to perform the provision by executing a PDU session acquisition via a path transformation confirmation process.

[0242] Example 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 device to at least: Generate a message related to the completion of the device's switch from the first network to the second network; The message is provided to the second network, and the data radio bearer (DRB) configuration of the device established at the first network is included in the message, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the device established at the first network, and The QoS information includes information about the QoS of the device established at the first network; and Receive DRB reconfiguration based on the provided messages.

[0243] Example 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 device to at least: Receive messages related to the completion of the handover from the first network to the second network by the endpoint terminal. The device is associated with the second network. The message includes the data radio bearer (DRB) configuration for the endpoint terminal established at the first network, and The DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Based on the received DRB configuration, determine which PDU session to continue for this endpoint terminal; and Based on this determination, DRB reconfiguration can be provided.

[0244] Example 22: A method comprising: Provide a network management entity or function with an endpoint terminal identifier associated with the endpoint terminal, which is configured with a first Radio Resource Control (RRC) configuration and has completed a handover associated with an access network entity or function on the 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 The second RRC configuration is provided to the endpoint terminal based on the endpoint terminal's specific information.

[0245] Example 23: The method according to Example 22 further includes: By providing the endpoint terminal identifier, you can request specific information about the endpoint terminal from the network management entity or function.

[0246] Example 24: The method according to Example 22 or 23, wherein This switch represents a switch 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.

[0247] Example 25: The method according to any one of claims 22 to 24, wherein the endpoint terminal identifier is a temporary endpoint terminal identifier that is available at the access network entity or function or at the second network and the network function associated with the access network entity or function.

[0248] Example 26: The method according to Example 25, wherein the endpoint terminal identifier is a shortened temporary mobile subscriber identity (S-TMSI).

[0249] Example 27: The method according to any one of Example Examples 22 to 26, wherein the first RRC configuration is a common RRC configuration. This public RRC configuration applies to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first and second networks, and / or The public RRC configuration applies to radio cells and / or TRPs associated with at least one of the access network elements or functions associated with the first network and the second network.

[0250] Example 28: The method according to any one of Example 22 to 27, wherein the endpoint terminal-specific information includes user equipment (UE) radio capability information.

[0251] Example 29: The method according to any one of claims 22 to 28, wherein the network management entity or function, namely the access and mobility management function (AMF), is responsible for managing the endpoint terminal's access to the network and the endpoint terminal's mobility.

[0252] Example 30: A method comprising: Receive an endpoint terminal identifier associated with an endpoint terminal from an access network entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with the access network entity or function on the target side of the handover. By using a database, endpoint-specific information corresponding to the received endpoint terminal identifier is determined; and Provide the determined endpoint terminal-specific information to the access network entity or function.

[0253] Example 31: The method according to Example 30, wherein the access network entity or function is a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

[0254] Example 32: A method comprising: At the endpoint terminal, a message is received from the first network, which is related to the endpoint terminal's handover from the first network to the second network; If the endpoint terminal is configured with an RRC configuration different from the Public Radio Resource Control (RRC) configuration, then the public RRC configuration is established, wherein... This public RRC configuration applies to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first and second networks, and / or The public RRC configuration applies to radio cells and / or TRPs associated with at least one access network element or function in the first network and the second network; and Perform the switch.

[0255] Example 33: According to the method of Example 32, wherein The public RRC configuration includes at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and The establishment also includes releasing any at least one of the DRB and PDU sessions established at the first network that are different from the public RRC configuration.

[0256] Example 34: The method according to Example 32 or 33, wherein the method further includes mapping at least one of the Quality of Service (QoS) flow and PDU session established at the first network to at least one default DRB and / or at least one default PDU session.

[0257] Example 35: A method comprising: At an access network entity or function, and from a network session management entity or function, at least one of the following is requested: Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from the first network to the second network. This access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Receive at least one of the requested PDU session information or QoS information; and Based on at least one of the received PDU session information or QoS information, configure the data radio bearer DRB reconfiguration for the endpoint terminal.

[0258] Example 36: The method according to Example 35, wherein the method further includes performing a request and / or receiving via a network management entity or function.

[0259] Example 37: According to the method of Example 36, wherein The network session management entity or function is the Session Management Function (SMF); The network management entity or function is the Access and Mobility Management Function (AMF); and The method also includes performing the request by executing a PDU session acquisition via a path transformation request procedure.

[0260] Example 38: A method comprising: The system receives a request from an access network entity or function to provide at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network. The access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; and Provide at least one of the requested PDU session information or QoS information.

[0261] Example 39: The method according to Example 38, wherein the method further includes receiving and / or providing via a network management entity or function.

[0262] Example 40: The method according to Example 39, wherein This method is applicable to the Session Management Function (SMF). The network management entity or function is the Access and Mobility Management Function (AMF); and The method also includes performing the provision by executing a PDU session acquisition via a path transformation confirmation process.

[0263] Example 41: A method comprising: Generate a message at the endpoint terminal related to the completion of the handover from the first network to the second network; The message is provided to the second network, and the data radio bearer (DRB) configuration of the endpoint terminal established at the first network is included in the message, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; and Receive DRB reconfiguration based on the provided messages.

[0264] Example 42: A method comprising: Receive messages related to the completion of the handover from the first network to the second network at the access network entity or function. The access network entity or function is associated with the second network. The message includes the data radio bearer (DRB) configuration for the endpoint terminal established at the first network, and The DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Based on the received DRB configuration, determine which PDU session to continue for this endpoint terminal; and Based on this determination, DRB reconfiguration can be provided.

[0265] Example 43: A computer program product for a computer, including a software code portion that, when the product is run on a computer, performs the steps of any one of Example 22 to 29, 30 to 31, 32 to 34, 35 to 37, 38 to 40, 41 or 42.

[0266] Example 44: A computer program product according to Example 43, wherein The computer program product includes a computer-readable medium on which the software code portion is stored, and / or The computer program product can be directly loaded into the computer's internal memory and / or can be transmitted over a network by means of at least one of the processes of uploading, downloading, and pushing.

[0267] The following meanings apply to the abbreviations used in this article: 3GPP Third Generation Partnership Project 3GGP2 Third Generation Partnership Program 2 4G fourth generation 5G (Fifth Generation) 5GC 5G Core Network 6G sixth generation AMF Access and Mobility Management Functions AP access point API (Application Programming Interface) BS base station CDMA Code Division Multiple Access CN Core Network DRB Data Radio Bearer eNB Evolution Node B EPC Evolution Group Core ETSI (European Telecommunications Standards Institute) gNB Next Generation Node B HO switch IEEE Institute of Electrical and Electronics Engineers ITU (International Telecommunication Union) L1 / L2 Layer 1 / Layer 2 LTE Long Term Evolution LTE-A Advanced Long Term Evolution MAC Media Access Control MANETs (Mobile Ad Hoc Networks) MIMO (Multiple Input Multiple Output) NAS Non-Access Layer NB Node B NF Network Functions NG-RAN (NG Radio Access Network) NGAP (NG Application Protocol) NR Radio Access NW Network PDU Protocol Data Unit PSA PDU Session Anchor RAM (Random Access Memory) RAN (Radio Access Network) Rel version 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: Telecommunications and Internet Convergence Services and Protocols for Advanced Networks TRP Transmitter / Receiver Point UE User Equipment UL uplink UPF User Plane Functions UWB (Ultra-Wideband) WCDMA Wideband Code Division Multiple Access WiMAX Global Microwave Access Interoperability WLAN (Wireless Local Area Network)

Claims

1. A method comprising: Provide an endpoint terminal identifier associated with an endpoint terminal to a network management entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with an access network entity or function on the target side of the handover; Receive endpoint terminal-specific information corresponding to the provided endpoint terminal identifier, the endpoint terminal-specific information indicating that the endpoint terminal is capable of being configured with a second RRC configuration different from the first RRC configuration; as well as The second RRC configuration is provided to the endpoint terminal based on the endpoint terminal-specific information.

2. The method according to claim 1, further comprising: The endpoint terminal identifier is provided to request endpoint terminal-specific information from the network management entity or function.

3. The method according to claim 1 or 2, wherein The switching refers to a switch 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.

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

5. The method of claim 4, wherein, The endpoint terminal identifier is a shortened temporary mobile subscriber identity (S-TMSI).

6. The method of any one of claims 1 to 5, wherein, The first RRC configuration is a common RRC configuration. The public RRC configuration is applicable to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first network and the second network, and / or The public RRC configuration is applicable to radio cells and / or TRPs associated with at least one access network element or function in the first network and the second network.

7. The method of any one of claims 1 to 6, wherein, The endpoint-specific information includes user equipment (UE) radio capability information.

8. The method according to any one of claims 1 to 7, wherein the network management entity or function, namely the access and mobility management function (AMF), is responsible for managing the endpoint terminal's access to the network and the endpoint terminal's mobility.

9. A method comprising: Receive an endpoint terminal identifier associated with an endpoint terminal from an access network entity or function, the endpoint terminal being configured with a first Radio Resource Control (RRC) configuration and having completed a handover associated with the access network entity or function on the target side of the handover. The endpoint terminal-specific information corresponding to the received endpoint terminal identifier is determined by using a database; as well as The determined endpoint terminal-specific information is provided to the access network entity or function.

10. The method of claim 9, wherein the access network entity or function is a gNB, a gNB for future radio access technologies, or a de-aggregated form of a gNB.

11. A method comprising: At the endpoint terminal, a message is received from a first network, the message being related to the endpoint terminal switching from the first network to a second network; If the endpoint terminal is configured with an RRC configuration different from the Public Radio Resource Control (RRC) configuration, then the public RRC configuration is established, wherein... The public RRC configuration is applicable to radio cells and / or transmit / receive points (TRPs) associated with at least one of the first network and the second network, and / or The public RRC configuration is applicable to radio cells and / or TRPs associated with at least one access network element or function in the first network and the second network; and Perform the switch.

12. The method of claim 11, wherein The public RRC configuration includes at least one default data radio bearer (DRB) and / or at least one default protocol data unit (PDU) session; and wherein, The establishment also includes releasing any at least one of the DRB and PDU sessions established at the first network that are different from the public RRC configuration.

13. The method according to claim 11 or 12, wherein, The method further includes mapping at least one of the Quality of Service (QoS) flows and PDU sessions established at the first network to the at least one default DRB and / or the at least one default PDU session.

14. A method comprising: At an access network entity or function, and from a network session management entity or function, at least one of the following is requested: Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network. The access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Receive at least one of the requested PDU session information or QoS information; as well as Based on the received PDU session information or QoS information, at least one is used to configure the data radio bearer (DRB) reconfiguration for the endpoint terminal.

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

16. The method of claim 15, wherein The network session management entity or function is the Session Management Function (SMF); The network management entity or function is the Access and Mobility Management Function (AMF); and The method also includes executing the request by performing a PDU session acquisition via a path transformation request procedure.

17. A method comprising: Receive a request from an access network entity or function to provide at least one of Protocol Data Unit (PDU) session information and Quality of Service (QoS) information associated with an endpoint terminal that has completed a handover from a first network to a second network, wherein the access network entity or function is associated with the second network. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; as well as Provide at least one of the requested PDU session information or QoS information.

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

19. The method of claim 18, wherein The method is applicable to the Session Management Function (SMF). The network management entity or function is the Access and Mobility Management Function (AMF); and The method further includes performing the provision by executing a PDU session acquisition via a path transformation confirmation process.

20. A method comprising: Generate a message at the endpoint terminal related to the completion of the handover from the first network to the second network; The message is provided to the second network, and the data radio bearer (DRB) configuration of the endpoint terminal established at the first network is included in the message, wherein the DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; as well as Receive DRB reconfiguration based on the provided message.

21. A method comprising: Receive messages related to the completion of the handover from the first network to the second network at the access network entity or function. The access network entity or function mentioned therein is associated with the second network. The message includes the data radio bearer (DRB) configuration of the endpoint terminal established at the first network, and The DRB configuration includes at least one of Protocol Data Unit (PDU) session information or Quality of Service (QoS) information. The PDU session information includes information about the PDU session of the endpoint terminal established at the first network, and The QoS information includes information about the QoS of the endpoint terminal established at the first network; Based on the received DRB configuration, determine which PDU session to continue for the endpoint terminal; as well as DRB reconfiguration is provided based on the determination.

22. A computer program product for a computer, comprising a software code portion that, when the product is run on the computer, is configured to perform the steps of any one of claims 1 to 8, 9 to 10, 11 to 13, 14 to 16, 17 to 19, 20 or 21.

23. The computer program product according to claim 22, wherein... The computer program product includes a computer-readable medium on which the software code portion is stored, and / or The computer program product can be directly loaded into the computer's internal memory and / or can be transmitted via a network by means of at least one of the upload, download, and push processes.

Images