Apparatus, method and computer program

Abstract

Apparatus, methods, and computer programs for handover in a communications network are provided to enable handover of a user equipment from a source network node to a target network node with robust mobility.

Description

Technical Field

[0001] Various example embodiments relate to an apparatus, method, and computer program product, specifically, but not limited to, network devices (network nodes, gNBs) and user equipment (UEs) as part of a communication system for efficient handover in such systems. Background Technology

[0002] A communication system enables communication between two or more entities (such as communication devices, base stations, and / or other nodes) by providing carrier waves between the various entities involved in the communication path.

[0003] A communication system can be a wireless communication system. Examples of wireless communication systems include Public Land Mobile Networks (PLMNs) operating based on radio standards (e.g., radio standards provided by 3GPP), satellite-based communication systems, and various wireless local area networks (e.g., wireless local area networks (WLANs)). Wireless systems can be divided into cells and are often referred to as cellular systems or cellular networks.

[0004] Communication systems and associated equipment typically operate according to a given standard or specification that defines how the various entities associated with the system are permitted to perform, how they are allowed to interact with each other, and how they should be implemented. The communication protocols and / or parameters to be used for connections within the network are also defined by this standard or specification. As mentioned above, examples of some standards include radio standards provided by 3GPP, such as 2G, 3G, 4G, and 5G. The communication system described herein is based on the 5G standard. However, the described embodiments are not limited to operating according to 5G and may also be applicable to future radio standards, such as 6G. Summary of the Invention

[0005] Therefore, a user equipment is provided. The user equipment includes at least one processor and at least one memory, the at least one memory including computer code for one or more programs, the at least one memory and the computer code being configured, using the at least one processor, to enable the user equipment to at least: identify a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment when performing a handover from a source cell to a target cell, and notify the target cell of the mismatch.

[0006] A switchover can be a conditional PCell change or a conditional switchover. When a switchover is a conditional switchover, the switchover configuration is a conditional switchover configuration.

[0007] In a user equipment, identifying a mismatch may include: decoding the handover configuration of the target cell when performing a handover from the source cell to the target cell, and detecting a mismatch between the decoded handover configuration and the configuration of the source cell. This mismatch may be a difference in SDAP configuration, DRB configuration, RLC configuration, or cell group configuration.

[0008] The user equipment can also be configured to receive an updated handover configuration for a target cell based on the current configuration of the source cell. Receiving the updated handover configuration for the target cell may include receiving a reconfiguration from a network node providing access to the target cell.

[0009] In some embodiments, an updated handover configuration is received after a path handover delay.

[0010] The updated handover configuration can be handled by the core network components. Alternatively, as mentioned above, network nodes providing access to the target cell can provide the updated handover configuration.

[0011] At the user equipment (UE), receiving the updated handover configuration of the target cell may include performing an RRC reconfiguration procedure to trigger DRB establishment or release. Alternatively, the UE may perform an RRC reconfiguration procedure to trigger DRB-QoS flow remapping.

[0012] A network node for a network is also provided, configured for handover of a user equipment from a source cell to a target cell. The network node is configured to provide access to the target cell and includes at least one processor and at least one memory, the at least one memory including computer code for one or more programs, the at least one memory and the computer code being configured, using the at least one processor, to cause the network node to at least: receive the current configuration of the source cell, store the configuration of the source cell, determine that there is a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment, and update the handover configuration of the target cell according to the current configuration of the source cell.

[0013] Within a network node, when a new PDU session is established or a PDU session is modified, the current configuration of the source cell can be received. Alternatively, when a QoS flow is established or released, the current configuration of the source cell can be received.

[0014] Network nodes can also be configured to send the updated handover configuration of the target cell to the user equipment each time the current configuration of the source cell is received.

[0015] Sending the updated handover configuration of the target cell to the user equipment may include: retrieving the stored updated handover configuration of the target cell and initiating an RRC reconfiguration procedure to reconfigure the user equipment using the stored updated handover configuration. Alternatively, sending the updated handover configuration of the target cell to the user equipment may include: retrieving the stored updated handover configuration of the target cell and initiating an RRC reconfiguration procedure to trigger DRB establishment or release. In another alternative, sending the updated handover configuration of the target cell may include: retrieving the stored updated handover configuration of the target cell and initiating an RRC reconfiguration procedure to trigger DRB to QoS flow remapping.

[0016] Network nodes can also be configured to send an indication of a mismatch between the source cell's configuration and the handover configuration applied in the target cell to core network components, such as the Access Management Function (AMF). This indication of a mismatch can be executed within the path handover request message. The core network components can then process the mismatch.

[0017] The updated handover configuration applied in the target cell can be triggered by core network components.

[0018] Network nodes can also be configured to receive from the source network node the updated handover configuration applied in the target cell based on the current configuration of the source cell.

[0019] Network nodes can also be configured to update the handover configuration applied in the target cell to synchronize with the current configuration of the source cell.

[0020] Alternatively, network nodes can be configured to perform path handover, which causes a path handover delay before the user equipment receives the updated handover configuration of the target cell. The path handover delay can be the time period between releasing the DRB to the source cell and establishing the DRB to the target cell. Alternatively, the path handover delay can be the time period that triggers the DRB-to-QoS flow remapping. The updated handover configuration can then include new QoS information.

[0021] A user equipment is also provided, comprising: a component for identifying a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment when performing a handover from a source cell to a target cell; and a component for notifying the target cell of the mismatch.

[0022] A network node for a network is also provided, configured for handover of a user equipment from a source cell to a target cell. The network node is configured to provide access to the target cell and includes: components for receiving the current configuration of the source cell; components for storing the configuration of the source cell; components for determining a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; and components for updating the handover configuration of the target cell based on the current configuration of the source cell.

[0023] In one aspect, a method for a user equipment includes: identifying a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment when performing a handover from a source cell to a target cell; and notifying the target cell of the mismatch.

[0024] The above-described method for a user equipment can be executed by a machine-readable, non-transient program storage device that tangibly embodies the instructions of a machine-executable program.

[0025] The above-described method for a user device can also be executed by a computer program product embodied on a computer-readable distribution medium and including program instructions that, when executed by a device, cause the device to perform the above-described method.

[0026] The computer program product may also include program instructions that, when executed by the device, cause the device to perform the methods described above.

[0027] On the other hand, the present invention provides a method for a network node configured for handover of a user equipment from a source cell to a target cell. The network node is configured to provide access to the target cell. The method includes: receiving a current configuration of the source cell; storing the configuration of the source cell; determining a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; and updating the handover configuration of the target cell based on the current configuration of the source cell.

[0028] The updated switching configuration can be an RRC configuration.

[0029] The above-described method for network nodes can be executed by a machine-readable, non-transient program storage device that tangibly embodies machine-executable program instructions.

[0030] The above-described method for a network node can be executed by a computer program product embodied on a computer-readable distribution medium and including program instructions that, when executed by a device, cause the device to perform the above-described method.

[0031] The computer program product may also include program instructions that, when executed by the device, cause the device to perform the methods described above.

[0032] Example embodiments will now be described with reference to the accompanying drawings, in which: Attached Figure Description

[0033] Figure 1 The signaling diagram schematically illustrates a conditional handover.

[0034] Figure 2 The signaling diagram schematically illustrates a conditional handover.

[0035] Figure 3 This is a simplified diagram of a communication network;

[0036] Figure 4 This is a simplified diagram of the user equipment;

[0037] Figure 5 These are simplified diagrams illustrating some examples of memory and storage media;

[0038] Figure 6 This is a simplified diagram of network components;

[0039] Figure 7 The signaling diagram schematically illustrates an embodiment;

[0040] Figure 8 The signaling diagram schematically illustrates an embodiment;

[0041] Figure 9 The signaling diagram schematically illustrates an embodiment;

[0042] Figure 10 This is a flowchart illustrating a method according to an embodiment;

[0043] Figure 11 This is a flowchart illustrating a method according to an embodiment;

[0044] Figure 12 This is a flowchart illustrating a method according to an embodiment;

[0045] Figure 13 This is a flowchart illustrating a method according to an embodiment;

[0046] Figure 14 A flowchart illustrating a method according to an embodiment is provided; and

[0047] Figure 15 This is a flowchart illustrating a method according to an embodiment. Detailed Implementation

[0048] The following embodiments are merely exemplary. Although the specification may refer to "a," "an," or "some" (or more) embodiments in multiple places throughout the text, this does not necessarily mean that each reference refers to the same (or more) embodiments, or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. For the purposes of this disclosure, the phrases "at least one of A or B," "at least one of A and B," and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A or B" and "A and / or B" mean (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0049] 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, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments.

[0050] Conditional Handover (CHO), described in 3GPP Release 16, is a mechanism to improve mobility robustness. CHO was further developed in Release 17 and will continue to evolve in future 3GPP releases. In the case of CHO, the RAN network can prepare multiple target cells, where each conditional handover reconfiguration is associated with CHO execution conditions evaluated by the UE. CHO execution conditions refer to measurement IDs (associating the measurement object with the reporting configuration) and are configured by the source gNB. The reporting configuration defines measurement events (A3 or A5) that trigger CHO execution. Whenever the CHO execution conditions are met, the corresponding target configuration is selected, and a handover is performed toward the selected target cell.

[0051] CHO can also occur in a dual connectivity manner to further improve mobility robustness and enable smooth handover. In this regard, primary and secondary cells (PSCell), primary cell (PCell), and secondary cell (SCell) are mentioned. The terminology used here will be used to outline the characteristics of PSCell in relation to 5G NR. However, it is to be understood that the principles described herein are not limited to these terms and can be applied to other systems with similar architectures. For example, in Multi-Radio Dual Connectivity (MR-DC), the primary cell (PCell) can be a Long Term Evolution (LTE) cell (e.g., Evolved Universal Terrestrial Radio Access-New Radio-Dual Connectivity (EN-DC)).

[0052] PSCell is a type of cell currently defined in 5G New Radio, along with primary cells (PCell), secondary cells (SCell), and special cells (SpCell). A PCell can be used as part of the initial access between the UE and the access network and is considered a primary cell within a primary cell group (MCG). A PSCell can be included as part of a secondary cell group (SCG). SpCells and SCells can reside in at least one of an MCG or an SCG.

[0053] Cells can be controlled by network nodes. There are two different types of network nodes in 5G new radios: primary nodes (which provide a control plane connection to the core network) and secondary nodes (which do not have a control plane connection to the core network). Both primary and secondary nodes can provide a user plane (e.g., data) connection to the core network. Primary nodes can control PCcells. In addition to PCcells, primary nodes can also control at least one PSCell, but not always. Secondary nodes can control at least one PSCell.

[0054] Depending on the dual connectivity option, interfaces may also exist between different nodes. The X2 interface is the interface between eNBs in LTE, which can be reused between Radio Access Network (RAN) nodes in non-standalone operation (e.g., between an eNB and an en-gNB). The Xn interface is the interface between RAN nodes in standalone operation (e.g., between an ng-eNB and an ng-eNB / gNB, and between a gNB / ng-eNB and a gNB).

[0055] The example embodiments in this document relate to subsequent enhancements to Conditional Handover (CHO), which is one of the objectives in 3GPP Release 18WID. Objective 2 in Mobility Enhancement Work Item (RP-221799) is described below: The mechanism and process of NR-DC are specified via L3 enhancement, and cell groups (at least for SCG) are selectively activated: Allows subsequent cell group changes after a CG change without CPC / CPA reconfiguration and re-initiation [RAN2, RAN3, RAN4] Note 4: A unified RRC modeling approach for objectives 1 and 2 can be considered to minimize the workload in RAN2.

[0056] The selective activation of the primary cell group (MCG) is expected to be part of the mobility enhancement WI range in version 19 NR. This selective activation is intended to allow conditional PCell changes by the UE without reconfiguring the UE after each PCell change, since subsequent PSCell changes were prioritized and studied in version 18.

[0057] refer to Figure 3 The network shown schematically illustrates the signaling process for CHO in... Figure 1 It is displayed in the middle.

[0058] UE 140-1 is served by Cell-1, with network node gNB-1 providing access to Cell-1. In step 1, UE 140-1 sends a measurement report to the serving network node gNB-1 to initiate CHO preparation for the target cell Cell-2, served by network node gNB-2. In step 2, the source network node gNB-1 sends a CHO request to the target network node gNB-2. In step 3, the target network node gNB-2 sends a CHO confirmation message to network node gNB-1 to confirm the CHO request from the source Cell-1 to the target Cell-2. In step 4, Cell-1 prepares the target Cell-2 and sends the CHO configuration along with the CHO execution conditions and RRC reconfiguration message to UE 140-1.

[0059] In step 5, when the CHO execution conditions for the target cell Cell-2 are met, the UE disconnects from the source network node gNB-1, that is, it stops transmitting / receiving to / from the source cell Cell-1.

[0060] In step 6, UE 140-1 initiates a random access procedure toward target cell Cell-2 by sending a PRACH preamble message to access node gNB-2 serving target cell Cell-2. In step 7, network node gNB-2 responds by sending a RACH response message back to network node gNB-1 serving source cell Cell-1. In step 8, the UE sends an RRC reconfiguration complete message to network node gNB-2 in target cell Cell-2. Upon successful completion of the random access procedure, target cell Cell-2, in step 9, notifies source cell Cell-1 that the handover process has been successfully completed by sending a handover success message from source network node gNB-1 to target network node gNB-2.

[0061] In step 10, upon receiving a handover success indication from the target network node gNB-2, the source network node gNB-1 initiates data forwarding to the target network node gNB-2 serving the target cell Cell-2. Once the data forwarding process is complete, UE140-1 will continue its data transmission / reception with the network.

[0062] Continuous Callable Headings (CHOs) are designed to enable fast cell handover (FCS) for UEs between ready cells. CHOs aim to improve mobility robustness, and their advantage lies in avoiding handover triggered by measurement report transmission failures, and / or avoiding failures in receiving HO commands. This is because the network will provide the UE 140-1 with a CHO command (CHO preparation) in advance before radio quality deteriorates. However, with high-frequency HOs, due to the shorter dwell time in a serving cell, there is a risk that the target cell may not receive the measurement report triggering handover preparation, or may not provide the CHO to the UE in a timely manner, leading to radio link failures (RLFs).

[0063] For FR2 continuous handover (HO) scenarios, if a CHO command can be used for more than one handover, it can reduce the probability of RLF / HOF. Furthermore, it can reduce signaling overhead. For example... Figure 2 As shown, by utilizing continuous CHO enhancements, UE 140-1 can continuously perform CHOs in Cell-2 and Cell-3, and therefore does not need to wait for CHO configuration from the network after each handover. In this paper, CHOs are prepared to be carried using neighboring cells for fast CHO execution, where UE 140-1 evaluates the corresponding (subset) of CHO execution conditions after each cell handover.

[0064] Figure 2 (refer to Figure 3 The network (showing the signaling diagram) displays a fast CHO for UE 140-1, which first switches from cell-1 to cell-2, and then from cell-2 to cell-3 served by access node gNB-3. The signaling diagram is interpreted as follows:

[0065] In step 1, UE 140-1 sends a measurement report to its serving cell Cell-1 via network node gNB-1.

[0066] In step 2, the serving cell Cell-1 initiates continuous CHO (fast CHO) preparation as follows: a. A preparation from Cell-1 to Cell-2 b. Another preparation from Cell-3 to Cell-2, which is a temporary CHO preparation. This means that if the UE switches to Cell-3, it can perform a subsequent handover from Cell-3 to Cell-2.

[0067] In step 3, similar to step 2, cell-1 initiates CHO preparation for handover from cell-1 to cell-3 and from cell-2 to cell-3, the latter being a temporary preparation.

[0068] In step 4, Cell-2 confirms the CHO preparation requested by Cell-1. It also provides CHO conditions for temporary CHO preparation from Cell-2 to Cell-1 and from Cell-2 to Cell-3 (if UE140-1 switches to Cell-2, the process is monitored by UE140-1).

[0069] Similar to step 4, in step 5, cell-3 confirms the preparation of the CHO requested by cell-1, as well as the CHO conditions prepared for the temporary CHO from cell-3 to cell-1 and from cell-3 to cell-2.

[0070] In step 6, Cell-1 sends an RRC reconfiguration message to the UE, which includes the CHO preparation and CHO conditions obtained from steps 2 to 5.

[0071] In step 7, when UE 140-1 receives the RRC reconfiguration message, it will monitor the CHO execution conditions: Cell-1 to Cell-2 and Cell-1 to Cell-3, because the current serving cell is Cell-1, while Cell-2 and Cell-3 are the target cells. The remaining conditions and configurations will be suspended until the UE switches to another cell.

[0072] In step 8, the CHO execution conditions from cell-1 to cell-2 are met, and UE 140-1 initiates a CHO toward the target cell-2.

[0073] In step 9, UE 140-1 uses the configuration provided in step 6 to perform a handover to the target cell Cell-2 and completes the handover process. Note that UE 140-1 only decodes the candidate configuration and knows its contents when the CHO is executed.

[0074] In step 10, UE 140-1 begins monitoring CHO execution conditions: Cell-2 to Cell-1 and Cell-2 to Cell-3. This is because Cell-2 is the new serving cell, while Cell-1 and Cell-3 are the target cells (since UE 140-1 has already obtained all the necessary CHO configuration in step 6, no further RRC reconfiguration from the network is required).

[0075] In steps 11 and 12, similar to steps 8 and 9, the CHO execution conditions toward the target cell Cell-3 are met, and UE 140-1 uses the RRC reconfiguration provided in step 6 to switch from Cell-2 to Cell-3.

[0076] In step 13, upon completion of the CHO towards target cell Cell-3, the UE begins monitoring CHO execution conditions from Cell-3 to Cell-1 and from Cell-3 to Cell-2. During conditional PCell preparation or CHO preparation, after the preparation of the conditional configuration at the target cell, the configuration of the source cell is expected to change. This is because, after target cell preparation and before the execution of the conditional PCell or PSCell change or CHO, new PDU sessions and / or new QoS flows may be established at the source cell; or existing PDU sessions or existing QoS flows may be released at the source cell, which could lead to a configuration mismatch between the source and target cells during HO execution.

[0077] Each time there is a change in the configuration of the source cell, the target cell can be prepared again, which requires reconfiguring the UE each time the target cell is prepared again.

[0078] If we consider CHO, it is likely that the HO to the target cell will be performed before the UE is reconfigured using the newly prepared target cell CHO configuration. Furthermore, if there is selective activation of PCell or PSCell, or conditional PCell change, UE 140-1 is not expected to be reconfigured by the network after each PCell or PSCell change.

[0079] In any of the above scenarios, the problem is that a HO to the target cell can be performed using a configuration that is inconsistent with the source cell configuration at the time of the HO.

[0080] The example implementation provides a method to ensure that the configurations for the source cell and the target cell are consistent during handover.

[0081] Figure 3 A system 100 in which operations may be performed according to exemplary aspects and embodiments described herein is schematically shown. System 100 is part of a mobile communication network and includes a mobile device 140-1, which may be a terminal device, a user equipment (UE), or an Internet of Things (IoT) device.

[0082] The term "terminal device" or "UE" refers to any terminal device that may be capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to: mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless terminals, mobile stations, laptop embedded devices (LEE), laptop installed devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, and so on. In the following description, the terms “terminal equipment”, “communication equipment”, “terminal”, “user equipment” and “UE” are used interchangeably.

[0083] For the purposes of this discussion, by system 100 in Figure 3 The portion of the network depicted will be referred to as the 3GPP 5G network. However, this network can be any type of communication network (e.g., 3G or 4G), or it could be 6G or other future networks. Furthermore, the portion of the 5G network shown by System 100 can interact with other networks of different generations, such as 4G or LTE networks, or 6G or other future networks.

[0084] System 100 also includes network nodes gNB-1, gNB-2, and gNB-3, which provide access to the corresponding cells Cell-1, Cell-2, and Cell-3. Network nodes gNB-1, gNB-2, and gNB-3 are part of a mobile communication network, which may include other network nodes serving the corresponding cells.

[0085] The embodiments described herein can be implemented in any mobile communication network or radio system, such as a network or system including at least one of the following Radio Access Technologies (RATs): WiMAX, GSM (2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunications System based on Basic Wideband Code Division Multiple Access (W-CDMA) (UMTS, 3G), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, and Enhanced LTE (eLTE). The term “eLTE” here refers to LTE evolution connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN). The term “resource” can refer to radio resources such as Physical Resource Blocks (PRBs), radio frames, subframes, time slots, subbands, frequency bands, subcarriers, beams, etc. The terms “transmit” and / or “receive” can refer to wireless transmission and / or reception over radio resources via a radio propagation channel.

[0086] However, the embodiments are not limited to the system / RAT given as an example, but those skilled in the art can apply this solution to other communication systems / networks provided with the necessary attributes. Some suitable examples of communication networks include 5G and / or 6G networks. The 3GPP solution for 5G is called New Radio (NR). 6G is considered a further development of 5G. NR has been envisioned to use multiple-input multiple-output (MIMO) multi-antenna transmission technology, more base stations or nodes than current LTE networks (i.e., the so-called small cell concept), including macro base stations cooperating with small LAN access nodes, and may also employ various radio technologies to achieve better coverage and enhanced data rates. 5G will likely include more than one radio access technology / radio access network (RAT / RAN), each optimized for specific use cases and / or spectrum. 5G mobile communications can have a wider range of use cases and related applications, including video streaming, augmented reality, various data sharing methods, and applications for various types of machines, including vehicle safety, various sensors, and real-time control. 5G is expected to have multiple radio interfaces, including sub-6 GHz, centimeter wave and millimeter wave, and will be able to integrate with existing legacy wireless access technologies such as LTE.

[0087] The current architecture in LTE networks is distributed across radios and centralized in the core network. Low-latency applications and services in 5G may require bringing content closer to the radios, leading to local offloading and multi-access edge computing (MEC). 5G enables analytics and knowledge generation at the data source. This approach requires leveraging resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content closer to cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile profiling, collaborative distributed peer-to-peer self-organizing networking and processing, and can also be categorized as local cloud / fog computing and grid / mesh computing, dew point computing, mobile edge computing, cloud point, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented reality and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications). By leveraging Network Functions Virtualization (NVF) and Software-Defined Networking (SDN), edge cloud can be brought into the RAN. Using edge cloud can mean that access node operations are performed, at least partially, in servers, hosts, or nodes operationally coupled to remote radio heads or base stations, including radio components. Network slicing allows the creation of multiple virtual networks over a shared physical infrastructure. These virtual networks are then customized to meet the specific needs of applications, services, devices, customers, or operators.

[0088] The signals of network nodes gNB-1, gNB-2, and gNB-3 are observable by the mobile device or user equipment (UE). UE140-1 is served by network node gNB-1 within cell Cell-1. For the purposes of this discussion, cell Cell-1 is the serving cell (also referred to as the source cell) of UE140-1. UE140-1 is capable of performing conditional handovers from serving cell Cell-1 to target cells Cell-2 or Cell-3, which have corresponding network nodes gNB-2 and gNB-3. However, all three cells—Cell-1, Cell-2, and Cell-3—can act as either serving or target cells for UE140-1. Figure 3 The network shown may also serve other UEs, which could be UE / IoT devices such as mobile phones or autonomous vehicles.

[0089] Network nodes gNB-1, gNB-2, and gNB-3 are interconnected via the Xn interface and each is connected to the core network (5GC) 150 via the NG interface. However, they can also be part of a service-based architecture, and the connection can be non-physical or wireless.

[0090] Network nodes gNB-1, gNB-2, and gNB-3 can act as source network nodes or target network nodes, where a switch from the source network node to the target network node occurs.

[0091] In Cell-1, Cell-2, and Cell-3, network nodes can provide a variety of different broadcast and / or multicast services (MBS) through the Multicast Service Channel (MTCH), which is the data channel that provides multicast / broadcast services.

[0092] Network nodes gNB-1, gNB-2, and gNB-3 can be used to provide information about the Multicast Traffic Channel (MTCH).

[0093] UE 140-1 can be in the RRC_IDLE (RRC idle), RRC_INACTIVE (RRC inactive), or RRC_CONNECTED (RRC connected) state.

[0094] Now refer to Figure 4 A more detailed example of UE 140-1 is provided, which can be any wireless communication device. Figure 4 A schematic partial cross-sectional view of communication device 140-1 is shown. Suitable UE or mobile communication equipment can be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples include mobile stations (MS) or mobile devices (such as mobile phones or so-called "smartphones"), computers provided with wireless interface cards or other wireless interface devices (e.g., USB dongles), personal data assistants (PDAs) or tablet computers provided with wireless communication capabilities, or any combination thereof, etc. For example, a mobile communication device can provide data transmission for carrying communications such as voice, email, text messages, multimedia, etc. Therefore, users can be supplied or provided with a variety of services via their communication devices. Non-limiting examples of these services include two-way or multi-way calling, data communication or multimedia services, or simply access to a data communication network system (such as the Internet). Users can also be provided with broadcast or multicast data. Non-limiting examples of content include downloadable content, television and radio programs, videos, advertisements, various alarms, and other information.

[0095] UE 140-1 can be, for example, a mobile device (i.e., a device not fixed to a specific location), or it can be a fixed device. This wireless device may or may not require human interaction for communication. As described herein, the term UE or “user” is used to refer to any type of wireless communication device.

[0096] UE 140-1 can receive signals via air or radio interface 201 through a suitable receiving device, and transmit signals via a suitable radio signal transmission device. Figure 4 In this diagram, the transceiver device is schematically indicated by block 202. The transceiver device 202 may be provided, for example, by means of a radio section and an associated antenna arrangement. The antenna arrangement may be arranged inside or outside the wireless device.

[0097] UE 140-1 is typically provided with at least one data processing entity or processor 203, at least one memory 204, and other possible components 205 for software and hardware-assisted performance of tasks it is designed to perform, including controlling access to and communication with access systems and other communication devices. Data processing, storage, and other related control means may be provided on a suitable circuit board and / or in a chipset. This feature is indicated by reference numeral 206. Users can control the operation of the wireless device through a suitable user interface (such as a keyboard 207, voice commands, a touchscreen or touchpad, or combinations thereof). A display screen 208, a speaker, and a microphone may also be provided. Furthermore, the wireless communication device may include suitable connectors (wired or wireless) for connecting to other devices and / or for connecting external accessories (e.g., hands-free devices).

[0098] Figure 4 The components of UE 140-1 and / or their associated circuitry shown may also be referred to as “components for receiving…”, “components for transmitting…”, “components for determining…”, etc.

[0099] Figure 5 A schematic representation of non-volatile memory media 300a (e.g., computer optical disc (CD) or digital versatile optical disc (DVD)) and 300b (e.g., Universal Serial Bus (USB) memory stick) is shown, which, when executed by a processor, allows the processor to perform one or more steps of the methods described herein and shown in the accompanying drawings.

[0100] As provided herein, various aspects are described in the detailed description of the examples and in the claims. Generally, some examples may be implemented in hardware or special-purpose circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the examples are not limited thereto. Although various examples may be shown or described as block diagrams, flowcharts, or using some other graphical representation, it is to be fully understood that, by way of non-limiting example, the blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, special-purpose circuitry or logic, general-purpose hardware or controllers or other computing devices, or any combination thereof.

[0101] Examples can be implemented by computer software stored in memory and executed by at least one data processor of the entity involved, or by hardware or a combination of hardware and software. Furthermore, in this respect, it should be noted that any process (e.g., as schematically shown in the accompanying drawings and / or previously otherwise described) can represent program steps, or interconnected logic circuits, blocks, and functions, or combinations of program steps with logic circuits, blocks, and functions. Software can be stored on physical media, such as memory chips or memory blocks implemented within a processor, magnetic media (e.g., hard disks or floppy disks), and optical media (e.g., DVDs and their data versions, CDs, etc.).

[0102] The memory can be of any type suitable for the local technological environment and can be implemented using any suitable data storage technology, such as semiconductor memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor can be of any type suitable for the local technological environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), gate-level circuits, and processors based on multi-core processor architectures.

[0103] Additionally or alternatively, some examples may also be implemented using circuitry. This circuitry may be configured to perform one or more of the functions and / or method steps previously described. This circuitry may be provided in base stations and / or communication equipment and / or core network entities.

[0104] As used in this application, the term "circuit device" may refer to one or more or all of the following: (a) Pure hardware circuit implementation (such as implementation in a purely analog and / or digital circuit device); (b) A combination of hardware circuits and software, such as: (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any portion of (multiple) hardware processors and software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable an apparatus (such as a communication device or base station) to perform the various functions previously described; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or portions of (multiple) microprocessors, which require software (e.g., firmware) for operation, but may not exist when it is not required to operate.

[0105] This definition of "circuit device" applies to all uses of the term in this application, including all uses in any claim. As a further example, as used in this application, the term "circuit device" also covers implementations that consist only of hardware circuitry or a processor (or processors) or portions thereof and their accompanying software and / or firmware. The term "circuit device" also covers, for example, integrated circuits.

[0106] In this paper, radio access architectures based on Long Term Evolution Advanced (LTE-A) or New Radio (NR, 5G) are used as examples of access architectures to which the described technologies can be applied to describe different examples; however, the examples are not limited to these architectures. By appropriately adjusting parameters and procedures, the examples can also be applied to other types of communication networks with suitable components. Some examples of other suitable system options are: Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or WiFi), Microwave Access Global System (WiMAX), Bluetooth®, Personal Communication Services (PCS), ZigBee®, Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANET), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0107] Figure 6 The example of a simplified system architecture is shown, which only shows some elements and functional entities, all of which are logical units, and their implementation may differ from those shown. Figure 6 The connections shown are logical connections; the actual physical connections may differ. It will be apparent to those skilled in the art that the system typically also includes… Figure 6 Other functions and structures besides those shown in the document.

[0108] However, these examples are not limited to the systems given as examples, but those skilled in the art can apply the solution to other communication systems provided with the necessary properties.

[0109] Figure 6 The example shows a portion of an exemplary radio access network. For instance, the radio access network may also support services other than those not shown. For simplicity, only network node gNB-1 is shown, which provides UE 140-1 with access to the serving cell Cell-1 before UE 140-1 performs a handover operation. However, Figure 6 The structure and connections shown can also be applied to network nodes gNB-2 and gNB-3, which provide access to cells Cell-2 and Cell-3, respectively.

[0110] Figure 6 UE 140-1 is shown. UE 140-1 is configured to have a radio connection with network node gNB-1 on one or more communication channels. Network node gNB-1 is also connected to core network (5GC) 150. For the purposes of this discussion, network node gNB-1 is the gNB serving UE 140-1 in source cell Cell-1. However, network node gNB-1 could also be an LTEeNB, or even a non-3GPP access node. The physical link from the UE to the gNB is referred to as the uplink or reverse link, and the physical link from the gNB to the UE is referred to as the downlink or forward link. It should be understood that a gNB, or its functionality, can be implemented using any entity suitable for this purpose, such as a node, host, server, or access point.

[0111] Figure 6 The gNB-1 network node structure and functions shown can also be applied to Figure 3 The network nodes gNB-2 and gNB-3 are shown schematically, but for simplicity, only gNB-1 is shown here.

[0112] like Figure 3As shown, the communication system 100 typically includes more than one network node gNB-1, gNB-2, and gNB-3. In this case, the network nodes can also be configured to communicate with each other via wired or wireless links (e.g., Xn interfaces) designed for this purpose. These links can be used for signaling transmission purposes. Alternatively, network nodes gNB-1, gNB-2, and gNB-3 can be part of a network utilizing a service-based architecture. Network node gNB-1 is a computing device configured to control the radio resources of the communication system coupled to it. Network node gNB-1 can also be referred to as a base station, access point, or any other type of interface device, including a relay station capable of operating in a wireless environment. Network node gNB-1 includes a transceiver or is coupled to a transceiver. The transceiver from the gNB provides a connection to an antenna element that establishes a bidirectional wireless link with the device. The antenna element may include multiple antennas or antenna elements. Network node gNB-1 is also connected to the 5G core network 150 (CN or Next Generation Core NGC). Depending on the technology deployed, the network node gNB-1 connects to the Serving and Packet Data Network Gateway (S-GW+P-GW) or User Plane Function (UPF) for routing and forwarding user data packets and provides connectivity to one or more external packet data networks to the device; it also provides connectivity to the Mobility Management Entity (MME) or Access Mobility Management Function (AMF) for controlling the access and mobility of the device (UE).

[0113] Examples of UE devices 140-1 include user units, user equipment, user equipment (UE), terminal equipment, mobile station, mobile device, etc.

[0114] UE device 140-1 generally refers to mobile or fixed devices (e.g., portable or non-portable computing devices), including wireless mobile communication devices that operate with or without a Universal Subscriber Identity Module (USIM), including but not limited to: mobile phones, smartphones, personal digital assistants (PDAs), handheld devices, devices using wireless modems (such as alarm or measuring devices), laptops and / or touchscreen computers, tablets, game consoles, notebook computers, and multimedia devices. It should be understood that the device can also be one used almost exclusively for uplink purposes, an example being a camera or camcorder that uploads images or video clips to a network. The device can also be capable of operating in an Internet of Things (IoT) network, a scenario where objects are provided with the ability to transmit data over the network without human-to-human or human-to-computer interaction, such as in smart grids and connected vehicles. The device can also leverage the cloud. In some applications, the device may include a user-portable device with radio components (such as a watch, headset, or glasses), while computation is performed in the cloud.

[0115] UE 140-1 illustrates a type of apparatus to which resources on the air interface are allocated and assigned, and therefore, any features described herein using the apparatus can be implemented using a corresponding apparatus (such as a relay node). An example of such a relay node is a Layer 3 relay (self-backhaul relay) toward a base station. The apparatus (or, in some examples, a Layer 3 relay node) is configured to perform one or more of the user equipment functionalities.

[0116] The various techniques described in this paper can also be applied to cyber-physical systems (CPS) (a system in which physical entities are controlled by collaborative computing elements). CPS enables the implementation and utilization of a large number of interconnected information and communication technology (ICT) devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems are a subcategory of cyber-physical systems in which the physical systems involved have inherent mobility. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0117] Furthermore, although the device has been described as a single entity, different units, processors, and / or memory units can be implemented. Figure 6 (Not all of them are shown in the image).

[0118] 5G implementations utilize multiple-input multiple-output (MIMO) antennas, far exceeding the base stations or nodes of LTE (the so-called "small cell" concept), including macro sites cooperating with small cells, and employing a variety of radio technologies depending on service requirements, usage scenarios, and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, various data sharing methods, and various forms of machine-type applications (such as massive machine-type communications (mMTC), including vehicle safety, various sensors, and real-time control). It is expected that 5G will have multiple radio interfaces, such as sub-6 GHz or above 24 GHz, centimeter waves, and millimeter waves, and will also integrate with existing legacy radio access technologies (such as LTE). Integration with LTE can be implemented as a system, at least in the early stages, where LTE provides macro coverage, and 5G radio interface access is achieved through aggregation to LTE from small cell access. In other words, 5G is planned to support inter-RAT interoperability (such as LTE-5G) and inter-RI interoperability (inter-radio interface interoperability, such as sub-6 GHz to centimeter wave, 6 GHz and above 24 GHz to centimeter wave and millimeter wave). One concept considered for use in 5G networks is network slicing, where multiple independent and dedicated virtual sub-networks (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput and mobility.

[0119] The LTE network architecture is entirely distributed across the radio, while remaining entirely centralized in the core network. Low-latency applications and services in 5G require bringing content closer to the radio, leading to local offloading and multi-access edge computing (MEC). 5G supports analytics and knowledge generation at the data source. This approach leverages resources that may not have continuous network connectivity, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content closer to cellular subscribers for faster response times. Edge computing encompasses a wide range of technologies, such as wireless sensor networks, mobile data acquisition, mobile profiling, collaborative distributed peer-to-peer self-organizing networks, and processing, which can also be categorized as local cloud / fog computing and grid / mesh computing, dew point computing, mobile edge computing, cloud point computing, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented reality and virtual reality, data caching, the Internet of Things (IoT) (massive connectivity and / or latency critical), and critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications).

[0120] like Figure 6As shown, the communication system 100, via network nodes gNB-1, gNB-2, and gNB-3, can also communicate with other networks 160, such as the public switched telephone network, VoIP network, the Internet, or private networks, or utilize services provided by them. The communication network may also be able to support the use of cloud services; for example, at least a portion of core network operations can be performed as cloud services. When these operations are performed outside the core network, this can also be referred to as edge computing. The communication system may also include a central control entity, etc., to provide facilities for collaboration, such as spectrum sharing, across different operators' networks.

[0121] Edge computing technologies can be incorporated into Radio Access Networks (RANs) by leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN). Using edge cloud technology may mean that access node operations are performed, at least partially, in servers, hosts, or nodes operatively coupled to remote radio heads or base stations, including radio components. Node operations can also be distributed across multiple servers, nodes, or hosts. The cloud RAN architecture enables real-time RAN functions to be performed at or near remote antenna sites (in the distributed unit DU 121 of network node gNB-1), while centralized functions (including those involving the core network 150) are performed centrally (in the centralized unit CU 122 of network node gNB-1). DU 121 and CU are connected via an F1 interface. CU 122 is connected to the 5G core network (5GC) 150 via an NG interface. CU 122 can be split into a user plane CU-UP and a control plane CU-CP. However, in some cases, this division is not performed in CU 122. The centralized unit control plane CU CP 123 of CU 122 provides control data for broadcast services. CU CP 123 is connected to 5GC 150 via an NG-C interface. It should also be understood that the division of labor between core network operations and base station operations in the future may differ from, or even completely disappear from, the division of labor in the 5G standard. Some other technological advancements that may be used include big data and all-IP, which can change the way networks are built and managed. 5G (or New Radio (NR)) networks are designed to support multi-tiered architectures, where edge computing servers can be placed between the core and base stations or NodeBs (gNBs). An example of edge computing is MEC, defined by the European Telecommunications Standards Institute (ETS). It should be understood that MEC (and other edge computing protocols) can also be applied to 4G networks.

[0122] 5G can also leverage satellite communications to enhance or supplement the coverage of 5G services, such as providing backhaul. Possible use cases include providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices, vehicular passengers, mobile broadband (MBB), or ensuring the availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems, particularly mega-constellations (systems deploying hundreds of (nano) satellites). Each satellite in a mega-constellation can cover multiple satellite network entities creating ground cells. These ground cells can be formed through ground relay nodes or by gNBs located on the ground or in satellites.

[0123] Figure 6 The system shown is only an example of a portion of a radio access system. In practice, the system may include multiple network nodes, and UE 140-1 may have access to multiple radio cells. The system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the network nodes may be a home (e / g) nodeB. Furthermore, various types of radio cells and multiple radio cells may be provided within the geographical area of ​​the radio communication system. Radio cells may be macrocells (or umbrella cells), which are large cells typically tens of kilometers in diameter, or they may be small cells (such as microcells, femtocells, or picocells). Figure 6 The network node gNB-1 in the system can provide any type of these cells. Cellular radio systems can be implemented as multi-layered networks comprising several types of cells.

[0124] In the context of this discussion, referring to the Conditional Handover (CHO) procedure described above, Cell-1, Cell-2, and Cell-3 can act as either the primary cell (PCell) or the primary / secondary cell (PSCell). The handover from the source cell to the target cell (from the source network node to the target network node) can be a conditional PSCell change or a conditional handover. The network can be configured to handle conditional PSCell changes or CHOs, respectively, with either a conditional PSCell change configuration or a CHO configuration.

[0125] and Figure 4 Similar to the UE 140-1 shown schematically, network nodes gNB-1, gNB-2, and gNB-3 are also typically provided with at least one processor, at least one memory, and other possible components for software and hardware-assisted execution of the tasks they are designed to perform, including controlling access to and communication with access systems and other communication devices.

[0126] Figure 6 The components and / or associated circuitry of network node gNB-1 (and network nodes gNB-2 and gNB-3) shown in the diagram may also be referred to as “components for transmitting…”, “components for receiving…”, “components for determining…”, “components for providing…”, etc.

[0127] refer to Figure 3 The example embodiment is described using system 100, which shows an exemplary RAN network.

[0128] Depend on Figure 7 The signaling diagram in the image illustrates an example embodiment. Figure 1 and Figure 2 When a conditional PSCell change or CHO is executed from source cell Cell-1 (served by network node gNB-1) to target cell Cell-2 (served by network node gNB-2), as described in the description, UE 140-1 in source cell Cell-1 identifies a mismatch between the configuration of source cell Cell-1 and the CHO configuration applied in target cell Cell-2, and indicates the configuration mismatch to the network when UE 140-1 connects to target cell Cell-2 via network node gNB-2. The target network node gNB-2 then processes the mismatch without affecting the NGAP procedure.

[0129] After a conditional PSCell change or CHO preparation from source cell Cell-1 to target cell Cell-2, UE 140-1 is reconfigured using the conditional PSCell / CHO configuration. When a new PDU session or QoS flow is triggered to establish or release, source network node gNB-1 initiates a re-preparation of target network node gNB-2 using the latest (current) updated configuration of source cell Cell-1.

[0130] The target network node gNB-2 stores the updated conditional PSCell change or CHO configuration after each re-preparation. Assuming that the conditional PSCell change or CHO execution occurs before UE 140-1 is reconfigured using the updated configuration, UE 140-1 decodes the conditional PSCell or CHO configuration during CHO execution and should detect a mismatch between the decoded configuration and the source cell configuration.

[0131] When UE 140-1 connects to target cell Cell-2, RRCReconfigurationComplete The message included " ConfigMismatchIndication ".

[0132] “ ConfigMismatchIndication "It can be a binary flag, or it can have more details, such as a bitmask."

[0133] The target network node gNB-2 should delay the path switching process so that it can handle the configuration mismatch without involving AMF (or without affecting the NGAP process).

[0134] The target network node gNB-2 can handle configuration mismatches via one of the following options: In the first option, the target network node gNB-2 retrieves the stored conditional PSCell or CHO configuration and initiates an RRC reconfiguration procedure to reconfigure UE 140-1 using the stored configuration; that is, network node gNB-2 reconfigures UE 140-1 using the full configuration. In the second option, the target network node gNB-2 retrieves the stored conditional PSCell or CHO configuration and initiates an RRC reconfiguration process to trigger incremental configuration changes by triggering DRB establishment or release or DRB-to-QoS flow remapping.

[0135] exist Figure 7 In the message flow diagram, steps 1 to 15 are Figure 1 and Figure 2 The existing CHO process is shown in the signaling diagram.

[0136] Figure 7 Step 16 and subsequent steps describe the example embodiment described above in more detail. In steps 16 and 17, the source network node gNB-1 receives a PDU session resource establishment / modification request from the AMF in the core network (5GC) 150.

[0137] Figure 7 Step 18 successfully confirms the request from step 16, which includes the updated user plane between core network 150 and source network node gNB-1 (not shown). QoS flows from core network 150 are mapped to DRBs on the radio, causing corresponding source cell configurations and target cell configurations for source cell Cell-1 and target cell Cell-2, respectively.

[0138] exist Figure 7 In steps 19 and 20, the source node gNB-1 initiates a handover request (HO request) to (multiple) target nodes gNB-2 and gNB-3 to update the ready configuration of the target cells Cell-2 and Cell-3.

[0139] exist Figure 7 In steps 24 to 26, target nodes gNB-2 and gNB-3 store the updated configurations of target cells Cell-2 and Cell-3.

[0140] exist Figure 7At step 29, before reconfiguring UE 140-1 using the updated configuration of the target cell (e.g., Cell-2) in step 31, the CHO (or conditional PSCell change) execution condition is met.

[0141] exist Figure 7 At step 29, UE 140-1 detects a configuration mismatch between the source cell configuration and the decoded CHO or conditional PSCell configuration.

[0142] exist Figure 7 At step 33, UE 140-1 includes "ConfigurationMismatchIndication" in the RRCReconfigurationComplete message.

[0143] exist Figure 7 In step 35, the target network node gNB-2 has been enabled in step 33 to delay the initiation of the path handover request process in order to handle the configuration mismatch between the source cell Cell-1 and the target cell Cell-2.

[0144] exist Figure 7 At step 36, the target network node gNB-2 retrieves the stored CHO or conditional PSCell configuration and can trigger step 37 (establish QoS flow to DRB remapping) or step 38 (update CHO configuration during RRC reconfiguration).

[0145] exist Figure 7 In step 31, an RRC reconfiguration with an updated CHO configuration for target cell Cell-2 is intentionally not sent to UE 140-1 in the selective activation MCG because the selective activation / conditional PSCell change behavior in version 19 does not allow any reconfiguration of UE 140-1 (RAN requirement). In this case, a problem occurs when the CHO condition is applied and UE 140-1 applies the target cell configuration for target cell Cell-2 that has not yet been transmitted to UE 140-1. This problem also occurs if step 29 occurs before step 21.

[0146] Figure 7 Step 33 adds a mismatch indication to the RRCReconfigComplete message, thereby notifying the network node gNB-2 in the target cell Cell-2 of the mismatch. The mismatch is detected because the configurations of the source cell Cell-1 and the target cell Cell-2 do not correspond to each other (because they should be mapped to the same QoS flow from core network 150, and in this case they are not).

[0147] exist Figure 7 In steps 33 to 39, the target node gNB-2 providing access to Cell-2 receives a configuration mismatch indication from UE 140-1 at network node gNB-2. Instead of immediately performing a path handover procedure (changing the user plane path from core network 150 to target cell-2 instead of the previous source cell-1), it analyzes or evaluates the configuration mismatch based on the received indication, its own UE context, and information about the established service / user plane. The target node gNB-2 generates a configuration consistent with the source cell-1 (e.g., based on the acknowledged QoS flow from step 18). Then, the target node gNB-2 shares the configuration of target cell-2 with UE 140-1 by sending an RRCReconfiguration message, which is consistent with the configuration of source cell-1 and corresponds to the previous configuration of source cell-1. Finally, a path handover procedure to core network 150 is performed at the target network node gNB-2. The path handover process can be based on the configuration of the source cell Cell-1 previously confirmed in step 18. Alternatively, if this is not possible, the path handover process can conform to the configuration of the target cell Cell-2. The path handover process is delayed until the configuration of the target cell Cell-2 is repaired and / or shared with UE 140-1. This restores user plane operation between UE 140-1 and core network 150 using agreed QoS flows.

[0148] In the Figure 8 In another example embodiment shown in the message flow diagram, when a conditional PSCell change or CHO is executed, UE 140-1 identifies a mismatch between the configuration of the source cell Cell-1 and the applied CHO configuration, and when UE 140-1 connects to the target cell Cell-2, it indicates the configuration mismatch to the network. The network node gNB-2 includes the mismatch indication in the path handover request message to the AMF in the core network 150, thereby allowing the AMF to handle the mismatch.

[0149] In this scenario, two possibilities exist. In the first example, after a conditional PSCell change preparation or CHO preparation and UE 140-1 is reconfigured, when a new PDU session or QoS flow is established or released, the source network node gNB-1 should initiate a re-preparation for the target network node gNB-2 using the latest updated configuration of the source cell cell-1. The target network node gNB-2 stores the updated conditional PSCell change or CHO configuration after each re-preparation using the latest or currently used configuration of the source cell cell-1.

[0150] Alternatively, in the second example, after a conditional PSCell change or CHO preparation and UE 140-1 is reconfigured, the establishment or release of a new PDU session or QoS flow triggers a re-preparation without initiating the target.

[0151] If the conditional PSCell change or CHO execution from source cell Cell-1 to target cell Cell-2 occurs before UE 140-1 is reconfigured using the updated configuration, then when the CHO is executed, UE 140-1 decodes the conditional PSCell or CHO configuration and should detect a configuration mismatch between the decoded configuration and the configuration of source cell Cell-1.

[0152] Then, when UE 140-1 connects to the target cell Cell-2, it includes "" in the RRCReconfigurationComplete message. ConfigMismatchIndication ".

[0153] The network node gNB-2 in the target cell Cell-2 should include "" in the path handover request message. ConfigMismatchIndication This allows the AMF in core network 150 to handle configuration mismatches between source cell Cell-1 and target cell Cell-2.

[0154] “ ConfigMismatchIndication "It can be a binary flag, or it can have more detailed information, such as a bitmask, where each bit can be mapped to a specific DRB configuration, QoS flow configuration, or PDU session."

[0155] exist Figure 8 In the second embodiment shown, the AMF in the core network 150 can handle the configuration mismatch between the source cell Cell-1 and the target cell Cell-2 as follows: Assuming the second example outlined above, the AMF can obtain the "path handover request" from the UE context compared with the AMF at the core network 150. PDUSessionResourceToBeSwitchedDLList "and / or " QosFlowAcceptedList "and / or " PDUSessionResourceFailedToSetupListPSReq The system detected a configuration mismatch between the source cell Cell-1 and the target cell Cell-2.

[0156] AMF can handle detected configuration mismatches, for example, by including indications in the path handover request confirmation, to establish a new QoS flow or PDU session at the target network node gNB-2, or to release an existing QoS flow or PDU session. By triggering E1 bearer context modification and F1 UE context modification to handle the added or released QoS flow, network node gNB-2 can accordingly process the new indications in the path handover request confirmation. This may result in establishing a new DRB or updating an existing DRB to perform DRB-to-QoS flow remapping via one of the following options: Option 1: The target network node gNB-2 retrieves the stored conditional PSCell or CHO configuration and initiates an RRC reconfiguration procedure to reconfigure UE 140-1 using the stored configuration (i.e., reconfigure UE 140-1 using the full configuration). Option 2: The target network node gNB-2 retrieves the stored conditional PSCell or CHO configuration and initiates an RRC reconfiguration process to trigger incremental configuration changes, such as by triggering DRB establishment or release, or DRB to QoS flow remapping.

[0157] Now refer to Figure 8 The above example embodiment is described using a signal flow diagram.

[0158] exist Figure 8 The steps not described below are existing CHO processes, for example, in Figure 1 and Figure 2 As shown in the signaling diagram.

[0159] exist Figure 8 In step 16, the source network node gNB-1 receives a PDU session resource establishment / modification request from the AMF in the core network 150.

[0160] exist Figure 8 At step 21, before reconfiguring UE 140-1 using the updated configuration of target cell Cell-2 (in step 23), the CHO (or conditional PSCell change) execution condition (for handover from source cell Cell-1 to target cell Cell-2) is met.

[0161] At step 21, UE 140-1 detects a mismatch between the source cell Cell-1 configuration and the decoded CHO or conditional PSCell configuration.

[0162] exist Figure 8 In step 25, UE 140-1 includes "" in the RRCReconfigurationComplete message ConfigurationMismatchIndication ".

[0163] exist Figure 8 In step 27, step 25 enables the target node to include "" during the path switching request process. ConfigurationMismatchIndication This allows the AMF to handle configuration mismatches between source cell Cell-1 and target cell Cell-2.

[0164] exist Figure 8 At step 28, step 27 enables the AMF to identify mismatches in the path switching requests “PDUSessionResourceToBeSwitchedDLList” and / or “QosFlowAcceptedList” and / or “PDUSessionResourceFailedToSetupListPSReq” compared with the UE context at the AMF.

[0165] exist Figure 8 At step 29, step 28 enables the AMF to handle configuration mismatches by including an indication in the path exchange request acknowledgment to establish a new QoS flow or PDU session at the target network node gNB-2, or to release an existing QoS flow or PDU session.

[0166] exist Figure 8 In step 30, step 29 enables the target network node gNB-2 to initiate E1 bearer context modification and F1 UE context modification to handle newly added or released QoS flows. This may result in the establishment of a new DRB at the target cell Cell-2, modification of an existing DRB to perform DRB-to-QoS flow remapping, or release of an existing DRB.

[0167] exist Figure 8 In steps 31 and 32, as a result of step 30, the target network node gNB-2 can trigger the remapping of QoS flows to DRB or update the CHO configuration during the RRC reconfiguration process.

[0168] In the Figure 9 In another example embodiment shown in the message flow diagram, after UE 140-1 successfully switches from source cell Cell-1 to target cell Cell-2, when target network node gNB-2 receives the configuration information of source cell Cell-1 from source network node gNB-1 via XnAP message, it detects a mismatch between the source cell configuration and the target cell configuration, and handles the mismatch by updating the CHO configuration of target cell Cell-2 to synchronize with the configuration of source cell Cell-1.

[0169] After UE 140-1 connects to target cell Cell-2 and source network node gNB-1 receives the "HO successful" message from target network node gNB-2, source network node gNB-1 forwards the configuration information of source cell Cell-1 used by UE 140-1 to target network node gNB-2 via UE XnAP connection.

[0170] The target network node gNB-2 delays the path handover process in order to read the configuration of the received source cell Cell-1 and identify whether there is any mismatch between its configuration and that of the target cell Cell-2.

[0171] Upon detecting a configuration mismatch, network node gNB-2 updates the conditional PSCell or CHO configuration to synchronize with the configuration of the received source cell Cell-1. Network node gNB-2 can then perform E1 bearer context modification and F1 UE context modification to handle newly added or released QoS flows. This may result in the establishment of a new DRB at the target cell Cell-2, modification of an existing DRB to perform DRB-to-QoS flow remapping, or release of an existing DRB. The path handover process should be triggered after the aforementioned handling of the configuration mismatch.

[0172] Now refer to Figure 9 The signaling diagram is used to describe this embodiment. Figure 9 Steps not described below are existing CHO processes, for example, in Figure 1 and Figure 2 As shown in the signaling diagram.

[0173] exist Figure 9 In step 16, network node gNB-1 in source cell Cell-1 receives a PDU session resource establishment / modification request from AMF.

[0174] exist Figure 9 In step 21, before reconfiguring UE 140-1 using the updated target configuration (e.g.) Figure 9 As shown in step 23), the CHO (or conditional PSCell change) execution conditions are met.

[0175] exist Figure 9 In step 24, UE 140-1 connects to the target cell Cell-2.

[0176] exist Figure 9 In step 26, gNB-2 in target cell Cell-2 sends a HO success message to notify network node gNB-1 that UE 140-1 has successfully connected to target cell Cell-2.

[0177] exist Figure 9 In step 27, network node gNB-1 forwards the configuration of the source cell Cell-1 currently used by UE140-1 (e.g., in a transparent container) via the signaling connection associated with the XnAP UE.

[0178] exist Figure 9 In step 28, the network node gNB-2 in the target cell Cell-2 delays the path handover process to detect whether there is a configuration mismatch between the configuration of the source cell Cell-1 and the stored CHO or conditional PSCell configuration.

[0179] exist Figure 9 In step 29, if a mismatch is detected, network node gNB-1 will update the CHO or conditional PSCell configuration to synchronize with the source cell configuration received in step 27.

[0180] exist Figure 9 In step 30, the network node gNB-2 in the target cell Cell-2 can trigger E1 bearer context modification and F1 UE context modification to handle configuration mismatch.

[0181] exist Figure 9 In steps 31 / 32, after step 30, the target network node gNB-2 can trigger the establishment of QoS flow to DRB remapping or update CHO configuration during the RRC reconfiguration process.

[0182] exist" RRCReconfigurationComplete "Binary data exists in the message" ConfigurationMismatchIndication In the alternative embodiments of the above example embodiments marked with the symbol "", UE 140-1 can be in the " RRCReconfigurationComplete The message includes more detailed information about the configuration mismatch between the source cell Cell-1 and the target cell Cell-2, not just the binary information. ConfigurationMismatchIndication "logo".

[0183] Figure 10 and Figure 11 These are flowcharts showing an overall overview of the methods performed by UE 140-1 and network node gNB-2.

[0184] exist Figure 10 In step 10-1, when UE 140-1 performs a handover from source cell Cell-1 to target cell Cell-2, it identifies a mismatch between the configuration of source cell Cell-1 and the handover configuration of target cell Cell-2 applied in the target UE 140-1. In step 10-2, UE 140-1 notifies network node gNB-2 of the mismatch. Network node gNB-2 provides access to target cell Cell-2.

[0185] The handover from Cell-1 to Cell-2 is either a conditional PSCell change or a conditional handover. Then, the handover configuration for the target Cell-2 applied in UE 140-1 is either a conditional handover configuration or a conditional PSCell configuration.

[0186] When UE 140-1 performs a handover from source cell Cell-1 to target cell Cell-2, it identifies mismatches by decoding the handover configuration of target cell Cell-2. Then, UE 140-1 checks for any mismatches between the decoded handover configuration and the source cell's configuration. These mismatches can be differences in SDAP, DRB, or RLC configurations.

[0187] UE 140-1 can also receive an updated handover configuration for target cell Cell-2 based on the current configuration in source cell Cell-1, for example, by receiving a reconfiguration from network node gNB-2 providing access to target cell Cell-2. This updated handover configuration can be received after a path handover delay. Alternatively, the updated handover configuration can be provided by core network components (such as Access Management Functions (AMF)) in 5G core 150.

[0188] UE 140-1 can also receive the updated handover configuration of target cell Cell-2 by performing an RRC reconfiguration procedure to trigger DRB establishment or release. Alternatively, UE 140-1 can also receive the updated handover configuration of target cell Cell-2 by performing an RRC reconfiguration procedure to trigger DRB-QoS flow remapping.

[0189] Figure 11 The flowchart in the diagram schematically illustrates the method performed by the network node gNB-2 that provides access to the target cell Cell-2 when UE 140-1 performs a handover from source cell Cell-1 to target cell Cell-2.

[0190] In step 11-1, network node gNB-2 receives the current configuration of source cell Cell-1; and in step 11-2, it stores the configuration of source cell Cell-1. When a new PDU session is triggered, or when a QoS flow is established or released, the current configuration of the source cell is received at network node gNB-2.

[0191] In step 11-3, network node gNB-2 detects a mismatch between the configuration of source cell Cell-1 and the handover configuration of target cell Cell-2 used by user equipment UE 140-1. When UE 140-1 connects to network node gNB-2, by receiving a mismatch indication from UE 140-1, network node gNB-2 can determine that there is a mismatch between the configuration of source cell Cell-1 and the handover configuration of target cell Cell-2. Alternatively, gNB-2 can detect the mismatch between the source cell configuration and the target cell configuration at the network node itself.

[0192] Then, network node gNB-2 updates the handover configuration of target cell Cell-2 based on the current configuration of source cell Cell-1 in steps 11-4. For example, the updated handover configuration may include new QoS information.

[0193] Network node gNB-2 can also be configured to send the updated handover configuration of target cell Cell-2 each time it receives the current configuration of source cell Cell-1. Network node gNB-2 can achieve this by retrieving the stored updated handover configuration of target cell Cell-2 and initiating an RRC reconfiguration procedure to reconfigure user equipment 140-1 using the stored updated handover configuration. Alternatively, network node gNB-2 can send the updated handover configuration of target cell Cell-2 to user equipment 140-1 by retrieving the stored updated handover configuration of target cell Cell-2 and initiating an RRC reconfiguration procedure to trigger DRB establishment or release. In another alternative, network node gNB-2 can send the updated handover configuration of target cell Cell-2 to user equipment 140-1 by retrieving the stored updated handover configuration of target cell Cell-2 and initiating an RRC reconfiguration procedure to trigger DRB to QoS flow remapping.

[0194] Network node gNB-2 can also send an indication of a mismatch between the configuration of the source cell Cell-1 and the handover configuration applied in the target cell Cell-2 to components in core network 150. This can be performed in the path handover request message. The core network components in core network 150 (e.g., Access Management Function (AMF)) can then handle this mismatch. Figure 8 The details are shown in more detail.

[0195] Alternatively, network node gNB-2 can be configured to receive from source network node gNB-1 the updated handover configuration applied in target cell Cell-2 based on the current configuration of source cell Cell-1.

[0196] In another alternative, network node gNB-2 can update the handover configuration applied in target cell Cell-2 to synchronize with the current configuration of source cell Cell-1. In this case, after UE 140-1 successfully hands over to target cell Cell-2, network node gNB-2 receives the configuration of source cell Cell-1 from source network node gNB-1. Then, target network node gNB-2 detects a mismatch between the configuration of source cell Cell-1 and the configuration of target cell Cell-2, and updates the configuration of target cell Cell-2 to match the configuration of source cell Cell-1. This... Figure 9 The details are shown in more detail.

[0197] Before User Equipment 140-1 receives the updated handover configuration for Target Cell-2, Network Node gNB-2 can perform a path handover. This path handover causes a path handover delay before User Equipment 140-1 receives the updated handover configuration for Target Cell-2. The path handover delay is the time interval between releasing the DRB to the source cell Cell-1 and establishing the DRB to the target cell Cell-2, or the time interval during which the DRB-to-QoS flow remapping is triggered.

[0198] Figure 12 It is schematically displayed from the perspective of user equipment 140-1 at a higher level. Figure 7 A flowchart of an embodiment.

[0199] In step 12-1, when user equipment 140-1 performs a CHO or conditional PSCell change from source cell Cell-1 to target cell Cell-2, it decodes the handover configuration of target cell Cell-2 (this configuration is applied to user equipment UE140-1).

[0200] In step 12-2, when connecting to the network node gNB-2 that provides access to the target cell Cell-2, UE140-1 identifies a mismatch between the configuration of the source cell Cell-1 and the handover configuration of the target cell Cell-2. This occurs if a mismatch is detected between the decoded handover configuration of the target cell Cell-2 and the configuration of the source cell Cell-1.

[0201] In step 12-3, UE 140-1 notifies the target cell Cell-2 of a mismatch, and in step 12-4, after the path handover delay, UE 140-1 receives a reconfiguration from the network node gNB-2 that provides access to the target cell Cell-2. This reconfiguration is an updated handover configuration for the target cell Cell-2 based on the current configuration applied in the source cell Cell-1.

[0202] Figure 13 The reference is schematically shown from the perspective of the target network node gNB-2 that provides access to the target cell Cell-2. Figure 7 A flowchart of the described embodiments.

[0203] In step 13-1, network node gNB-2 receives the current configuration of source cell Cell-1, and in step 13-2 it stores the configuration of source cell Cell-1.

[0204] In step 13-3, the target network node gNB-2 stores the updated handover configuration of the target cell Cell-2 each time it receives the current configuration of the source cell Cell-1.

[0205] In steps 13-4, UE 140-1 performs a handover from source cell Cell-1 to target cell Cell-2. When UE 140-1 connects to network node gNB-2 during the handover, network node gNB-2 receives from UE 140-1 an indication of a mismatch between the configuration of source cell Cell-1 and the handover configuration applied in target cell Cell-2.

[0206] In steps 13-5, the target network node gNB-2 sends the updated handover configuration of target cell Cell-2 to user equipment 140-1. The updated handover configuration of target cell Cell-2 corresponds to the current configuration of source cell Cell-1. The target network node gNB-2 retrieves the stored updated handover configuration of target cell Cell-2 and initiates a reconfiguration process to reconfigure user equipment 140-1 using the stored updated handover configuration.

[0207] In steps 13-6, there is a path handover delay until user equipment 140-1 receives the updated handover configuration of target cell Cell-2 from network node gNB-2.

[0208] Figure 14 It is displayed from the perspective of user equipment 140-1, at a higher level. Figure 8 The flowchart of the embodiments described herein.

[0209] In step 14-1, UE 140-1 performs a handover from source cell Cell-1 to target cell Cell-2, such as CHO or conditional PSCell change.

[0210] In step 14-2, when connecting to the target cell Cell-2, if UE 140-1 identifies a mismatch between the configuration of the source cell Cell-1 and the handover configuration of the target cell Cell-2 applied in UE 140-1, UE 140-1 notifies the target cell Cell-2 of the mismatch via the network node gNB-2 that provides access to the target cell Cell-2.

[0211] In step 14-3, UE 140-1 receives an updated handover configuration for target cell Cell-2 initiated by a component of core network 150 (e.g., AMF). When a component of core network 150 handles a mismatch between the configuration of source cell Cell-1 and the handover configuration of target cell Cell-2 applied in UE 140-1, it provides the updated handover configuration for target cell Cell-2. The AMF provides an indication to target cell Cell-2 to trigger a reconfiguration process, as referenced. Figure 8 As described in more detail, the updated handover configuration of the target cell Cell-2 corresponds to the current configuration in the source cell Cell-1.

[0212] Figure 15 From the perspective of the target network node gNB-2 providing access to the target cell Cell-2, this schematically illustrates the reference when the UE performs a CHO or conditional PCell change from Cell-1 to Cell-2. Figure 9 A flowchart of the described embodiments.

[0213] In step 15-1, network node gNB-2 receives the current configuration of source cell Cell-1.

[0214] In step 15-2, network node gNB-2 delays the path handover process. This is to detect whether there is a configuration mismatch between the current configuration of the received source cell Cell-1 and the stored handover configuration. If such a configuration mismatch is detected, in step 15-3, network node gNB-2 updates the handover configuration to synchronize with the received current configuration of the source cell Cell-1.

[0215] In this way, configuration mismatches between the source and target cells (including conditional PCell changes and conditional PSCell changes) are effectively handled during CHO execution, while the QoS flow mapping principle from the source cell to the DRB is fully applied at the target cell after the HO. This provides a universal solution for various mobility scenarios, including CHO NR-DC and MCG selective activation.

[0216] Various example implementations also provide implementations with or without UE impact and with or without NGAP signaling impact, thereby simplifying the implementation.

[0217] Although the foregoing has been described with reference to specific exemplary embodiments, it is not limited to these embodiments, and those skilled in the art will undoubtedly conceive of many more embodiments falling within the scope of the claims.

[0218] Furthermore, each of the embodiments can be implemented in combination with any other embodiment.

[0219] List of abbreviations AMF – Access and Mobility Management Function CHO – Conditional Switching DRB—Data Radio Bearer HO - Switch MCG – Main Cell Group NGAP – Next Generation Applications NGRAN – Next Generation Radio Access Network PDU – Packet Data Unit QoS – Quality of Service RACH – Random Access Channel UE - User Equipment

Claims

1. A user equipment comprising at least one processor and at least one memory, the at least one memory including computer code for one or more programs, the at least one memory and the computer code being configured to, using the at least one processor, cause the user equipment to at least: When performing a handover from a source cell to a target cell, a mismatch is identified between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; and The mismatch notification is provided to the network node accessing the target cell.

2. The user equipment according to claim 1, wherein the switching is a conditional PSCell change.

3. The user equipment according to claim 1, wherein the handover is a conditional handover.

4. The user equipment according to claim 3, wherein the handover configuration is a conditional handover configuration.

5. The user equipment according to any of the preceding claims, wherein identifying a mismatch comprises: When performing the handover from the source cell to the target cell, the handover configuration of the target cell is decoded, and a mismatch between the decoded handover configuration and the configuration of the source cell is detected.

6. The user equipment of claim 5, wherein the mismatch includes differences in SDAP configuration, DRB configuration, or RLC configuration.

7. The user equipment according to any of the preceding claims, the user equipment is further configured to receive an updated handover configuration of the target cell based on the current configuration of the source cell.

8. The user equipment according to claim 7, wherein receiving the updated handover configuration of the target cell includes: Receive reconfiguration from the network node that provides access to the target cell.

9. The user equipment of claim 8, wherein the updated handover configuration is received after a path handover delay.

10. The user equipment of claim 7, wherein the mismatch is handled by a core network component.

11. The user equipment according to any one of claims 7 to 10, wherein receiving the updated handover configuration of the target cell includes performing an RRC reconfiguration process to trigger DRB establishment or release.

12. The user equipment according to any one of claims 7 to 10, wherein receiving the updated handover configuration of the target cell includes performing an RRC reconfiguration process to trigger DRB to QoS flow remapping.

13. A network node for a network, the network node being configured for handover of a user equipment from a source cell to a target cell, the network node being configured to provide access to the target cell, and comprising at least one processor and at least one memory, the at least one memory including computer code for one or more programs, the at least one memory and the computer code being configured to, using the at least one processor, cause the network node to at least: Receive the current configuration of the source cell; Store the configuration of the source cell; It is determined that there is a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; as well as Update the handover configuration of the target cell based on the current configuration of the source cell.

14. The network node of claim 13, wherein determining the existence of a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment includes: When the UE connects to the network node, it receives a mismatch indication from the UE.

15. The network node of claim 13, wherein determining the existence of a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment includes: The mismatch between the source cell configuration and the target cell configuration is detected at the network node.

16. The network node of claim 13, wherein the current configuration of the source cell is received when a new PDU session is triggered.

17. The network node of claim 13, wherein the current configuration of the source cell is received when the QoS flow establishment or release is triggered.

18. The network node according to any one of claims 13 to 17, wherein the network node is further configured to send the updated handover configuration of the target cell to the user equipment each time the current configuration of the source cell is received.

19. The network node of claim 18, wherein sending the updated handover configuration of the target cell to the user equipment comprises: Retrieve the updated handover configuration of the target cell from the storage, and initiate an RRC reconfiguration procedure to reconfigure the user equipment using the updated handover configuration from the storage.

20. The network node of claim 18, wherein sending the updated handover configuration of the target cell to the user equipment comprises: Retrieve the updated handover configuration of the target cell from the storage and initiate an RRC reconfiguration process to trigger DRB establishment or release.

21. The network node of claim 18, wherein sending the updated handover configuration of the target cell includes: Retrieve the updated handover configuration of the target cell from the storage and initiate an RRC reconfiguration process to trigger DRB to QoS flow remapping.

22. The network node according to any one of claims 13 to 17, the network node being further configured to send an indication to the core network component of a mismatch between the configuration of the source cell and the handover configuration applied in the target cell.

23. The network node of claim 22, wherein the indication of the mismatch between the configuration of the source cell and the handover configuration applied in the target cell is executed in the path handover request message.

24. The network node of claim 22 or 23, wherein the updated handover configuration applied in the target cell is triggered by the core network component.

25. The network node according to any one of claims 22 to 24, wherein the core network component is an access management function.

26. The network node according to any one of claims 13 to 17, wherein the network node is further configured to receive from the source network node the updated handover configuration applied in the target cell according to the current configuration of the source cell.

27. The network node according to any one of claims 13 to 17, wherein the network node is further configured to update the handover configuration applied in the target cell to synchronize with the current configuration of the source cell.

28. The network node of claim 13, further configured to perform path handover, the path handover causing a path handover delay before the user equipment has received the updated handover configuration of the target cell.

29. The network node of claim 28, wherein the updated handover configuration includes new QoS information.

30. The network node according to claim 28 or 29, wherein the path handover delay is the time period between releasing the DRB to the source cell and establishing the DRB to the target cell.

31. The network node according to claim 28 or 29, wherein the path switching delay is a time period used to trigger DRB to QoS flow remapping.

32. A user equipment, comprising: A component used to identify mismatches between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment when performing a handover from the source cell to the target cell; as well as A component used to notify the target cell of the mismatch.

33. A network node for a network, the network node being configured for handover of a user equipment from a source cell to a target cell, the network node being configured to provide access to the target cell, and comprising: Components for receiving the current configuration of the source cell; Components used to store the configuration of the source cell; A component for determining a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; as well as A component for updating the handover configuration of the target cell based on the current configuration of the source cell.

34. A method for a user equipment, comprising: When performing a handover from a source cell to a target cell, a mismatch is identified between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment. as well as The mismatch will be communicated to the target cell.

35. A method for a network node, the network node being configured for handover of a user equipment from a source cell to a target cell, the network node being configured to provide access to the target cell, the method comprising: Receive the current configuration of the source cell; Store the configuration of the source cell; It is determined that there is a mismatch between the configuration of the source cell and the handover configuration of the target cell applied in the user equipment; as well as Update the handover configuration of the target cell based on the current configuration of the source cell.

36. A non-transient program storage device capable of being read by a machine, the non-transient program storage device tangibly embodying a program of machine-executable instructions for performing the method according to claim 32 or 33.

Images