Electronic device and operating method thereof

Abstract

This operating method of an electronic device may comprise, for migration of a target cell from a first distributed unit (DU) to a second DU, the steps of: controlling a first operation of copying cell configuration information about the target cell of the first DU to the second DU; identifying whether one or more operations for the migration of the target cell from the first DU to the second DU fail; and removing the cell configuration information from the second DU on the basis of a failure of at least one of the one or more operations.

Description

Electronic devices and their operating methods

[0001] The present disclosure relates to a method and an electronic device for migrating a target cell from a source DU (distributed unit) to a target DU.

[0002] In the communications industry, technology for virtualized radio access networks (RANs), or vRANs (virtualized RANs), is rapidly growing. Conventional hardware-based RANs require specific hardware to perform each communication function. Mobile carriers, due to hardware compatibility issues, have had to build RANs using hardware configurations from the same manufacturer. However, vRANs are software-based, not hardware-based. Their communication functions can be performed by software configurations. In other words, vRANs do not require specialized hardware to perform communication functions, and their software configurations can be run on general-purpose server devices to perform communication functions. Consequently, mobile carriers can build vRANs using products from various manufacturers, rather than being tied to a single manufacturer's product.

[0003] The present disclosure can be implemented in various ways, including as a method, system, device, or computer program stored on a computer-readable storage medium.

[0004] In one embodiment of the present disclosure, a method of operating an electronic device may include a step of controlling a first task of replicating cell configuration information for a target cell of a first distributed unit (DU) to a second DU for migration of the target cell from the first DU to the second DU. In one embodiment of the present disclosure, the method of operating an electronic device may include a step of identifying whether one or more tasks for migration of the target cell from the first DU to the second DU have failed. In one embodiment of the present disclosure, the method of operating an electronic device may include a step of removing the cell configuration information from the second DU based on a failure of at least one task among the one or more tasks.

[0005] In one embodiment of the present disclosure, a program for performing an operating method of an electronic device on a computer can be recorded on a computer-readable recording medium.

[0006] In one embodiment of the present disclosure, an electronic device may include a memory that stores one or more instructions and at least one processor that executes the one or more instructions stored in the memory. In one embodiment of the present disclosure, the at least one processor may execute the one or more instructions, thereby controlling a first task of replicating cell configuration information for a target cell of a first distributed unit (DU) to a second DU for migration of the target cell from the first DU to the second DU. In one embodiment of the present disclosure, the at least one processor may execute the one or more instructions, thereby enabling the electronic device to identify whether one or more tasks for migration of the target cell from the first DU to the second DU have failed. In one embodiment of the present disclosure, the at least one processor may execute the one or more instructions, thereby enabling the electronic device to remove the cell configuration information from the second DU based on a failure of at least one of the one or more tasks.

[0007] FIG. 1 is a diagram showing an example of a wireless communication system structure according to one embodiment of the present disclosure.

[0008] FIG. 2 is a flowchart illustrating an example of a cell transfer method from a source DU to a target DU according to one embodiment of the present disclosure.

[0009] FIG. 3 is a diagram illustrating an example of an electronic device controlling a first task according to one embodiment of the present disclosure.

[0010] FIG. 4 is a diagram illustrating an example of removing cell configuration information from a target DU upon failure of a first task in one embodiment of the present disclosure.

[0011] FIG. 5 is a diagram illustrating an example of an electronic device controlling a second task according to one embodiment of the present disclosure.

[0012] FIG. 6 is a diagram illustrating an example of removing MAC context and cell configuration information from a target DU upon failure of a second task in one embodiment of the present disclosure.

[0013] FIG. 7 is a diagram illustrating an example of an electronic device controlling a third task according to one embodiment of the present disclosure.

[0014] FIG. 8A is a diagram illustrating an example of reconfiguring the fronthaul path and the control path and removing MAC context and cell configuration information from the target DU in response to a failure of the third task in one embodiment of the present disclosure.

[0015] FIG. 8b is a diagram illustrating an example of removing MAC context and MAC / PHY cell configuration information from a source DU upon success of a third task in one embodiment of the present disclosure.

[0016] FIG. 9 is a diagram illustrating an example of an electronic device controlling a fourth task according to one embodiment of the present disclosure.

[0017] FIG. 10 is a drawing showing an example of an operating method of an electronic device according to one embodiment of the present disclosure.

[0018] FIG. 11 is a drawing showing an example of an electronic device according to one embodiment of the present disclosure.

[0019] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.

[0020] When describing embodiments, detailed descriptions of related known technologies are omitted if they are deemed to unnecessarily obscure the main point. Furthermore, numbers (e.g., "first," "second," etc.) used in the description of embodiments are merely identifiers used to distinguish one component from another. Furthermore, unless the context clearly indicates otherwise, the singular forms "a," "an," and "the" are understood to include plural references.

[0021] It should also be understood that the blocks and combinations of flowcharts in each flowchart can be executed by one or more computer programs containing computer-executable instructions. The one or more computer programs may be stored entirely in a single memory, or may be stored in separate portions across multiple different memories.

[0022] All functions or operations described in this document may be performed by a single processor or a combination of processors. A single processor or a combination of processors is a circuitry that performs processing, and may include circuitry such as an Application Processor (AP), a Communication Processor (CP), a Graphical Processing Unit (GPU), a Neural Processing Unit (NPU), a Microprocessor Unit (MPU), a System on Chip (SoC), or an Integrated Chip (IC).

[0023] Below, with reference to the attached drawings, embodiments of the present disclosure are described in detail to facilitate implementation by those skilled in the art. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. Before proceeding with a detailed description of the invention, the terms used herein are defined or understood as follows.

[0024] When a component is referred to herein as being "connected" or "connected" to another component, it should be understood that the component may be directly connected to or connected to the other component, but may also be connected or connected via another component in between, unless otherwise specifically stated. Furthermore, "connection" may include a wireless connection or a wired connection.

[0025] In addition, in this specification, components expressed as 'unit', 'module', etc. may be two or more components combined into one component, or one component may be divided into two or more components with more detailed functions. In addition, each component described below may additionally perform some or all of the functions performed by other components in addition to its own main function, and of course, some of the main functions performed by each component may be performed exclusively by other components.

[0026] In this disclosure, the expression "at least one of a, b, or c" can refer to "a", "b", "c", "a and b", "a and c", "b and c", "all of a, b, and c", or variations thereof. In this disclosure, the expression "a or b" can refer to "a", "b", "a and b", or variations thereof. In this disclosure, the expression "a (or, b, c)" or the expression "a, b, or c" can refer to "a", "b", "c", "a and b", "a and c", "b and c", "all of a, b, and c", or variations thereof.

[0027] In one embodiment of the present disclosure, the term "transfer" may include moving, copying, duplicating, or synchronizing previous target information contained in any logical or physical space to any other space. In one embodiment of the present disclosure, the term "transfer" may include causing previous target information (e.g., context information) contained, stored, or set in space A (or device A, module A) to be contained, stored, or set in space B (or device B, module B). In one embodiment of the present disclosure, "transfer" may include causing previous target information contained, stored, or set in space A (or device A, module A) to be contained, stored, or set in space B (device B or module B), and removing, deleting, or releasing the previous target information in space A (device A or module A).

[0028] In one embodiment of the present disclosure, a "cell transfer" may include transferring at least one of information, context, or interface associated with a cell. For example, a "cell transfer" may include transferring cell configuration information. For example, a "cell transfer" may be a cell-by-cell transfer, and may include transferring cell configuration information and a UE context of a UE (user equipment) associated with the cell. For example, a "cell transfer" may be a UE-by-UE transfer, and may include transferring a UE context of a UE (user equipment) associated with the cell. For example, a "cell transfer" may be a UE-by-UE transfer, and may include transferring an interface for user data (e.g., an F1-U interface).

[0029] In one embodiment of the present disclosure, "cell configuration information" may include information about basic settings, operation methods, configurations, or parameters of each cell in a wireless communication system. For example, "cell configuration information" may include information about frequency bands, channel bands, frequency allocation information, transmission output power settings, cell identifiers, settings in time and frequency domains, interference management with other cells and base stations, scheduling information (e.g., DL (downlink) / UL (uplink) Max Resource Block, PDSCH (physical downlink shared channel), PUSCH (physical uplink shared channel), SSB (synchronization signal block), etc.), or timing information (e.g., number of slots per flame, etc.).

[0030] In one embodiment of the present disclosure, a "UE context" may include information for wireless communication of a UE in a wireless communication system. For example, the "UE context" may include location information of a UE, a UE identifier, a status of the UE, service requirements, information on the network and cell currently in use, performance information, function information, security information, or authentication information of the UE. For example, the "UE context" may include a unique number for each situation of UEs connected to a base station (e.g., a radio network temporary identifier (RNTI)), information on DL Data Volume per UE (e.g., a buffer occupancy (BO)), information on UL Data Volume per UE (e.g., a buffer status report (BSR)), a physical downlink control channel (PDCCH) monitoring period for the UE to transmit and receive new DL / UL traffic (e.g., discontinuous reception (DRX)), and retransmission information per UE (e.g., hybrid automatic repeat request (HARQ) information). For example, a "UE context" may include different parameter values ​​or data for each of multiple UEs associated with the same cell. For example, a "UE context" may include common parameter values ​​or data for multiple UEs associated with the same cell.

[0031] In one embodiment of the present disclosure, "connection relationship" may include the meaning of "connection relationship," "inclusion relationship," "attachment relationship," or "matching relationship." For example, "connected" may include the meaning of "connected," "inclusion," "attachment," or "matched." In one embodiment of the present disclosure, "connection" may include the meaning of data communication being possible, either wired or wireless. For example, "A and B are connected" may include the meaning that A and B are capable of data communication, i.e., can transmit and receive data with each other.

[0032] In one embodiment of the present disclosure, “setting” may include “creating,” “activating,” “connecting,” “establishing,” or “initiating.”

[0033] In one embodiment of the present disclosure, “releasing” may include “removing,” “deactivating,” “stopping / suspending,” or “disconnecting.”

[0034] In one embodiment of the present disclosure, “A performing action B” may include “A directly performing action B” or “A controlling C to perform action B.” In one embodiment of the present disclosure, “A controlling action B” may include “A directly performing action B” or “A controlling C to perform action B.”

[0035] In one embodiment of the present disclosure, a “UE associated with a cell” may include a UE associated with a cell, a UE attached to a cell, a UE communicating with an RU including a cell (i.e., transmitting and receiving data), a UE receiving a communication service via a cell, a UE transmitting and receiving data via a cell, a UE accessing a network via a cell, a UE included in a range (e.g., effective range, communication range) of a cell, a UE requesting a radio resource of a cell, or a UE allocated a radio resource of a cell, etc. For example, one or more UEs associated with a target cell may have a connection established and managed based on cell configuration information for the target cell.

[0036] In one embodiment of the present disclosure, "path" or "interface" may include the meaning of a module (e.g., a software module, a hardware module) that enables data transmission and reception. In one embodiment of the present disclosure, "path" or "interface" may include the meaning of a logical or physical connection relationship. In one embodiment of the present disclosure, "path" or "interface" may include the meaning of a data transmission and reception path. In one embodiment of the present disclosure, "establishing an interface between A and B" may include the meaning of establishing a connection so that A and B can transmit and receive data with each other and process the received data.

[0037] In one embodiment of the present disclosure, "scale-out for a DU" and "scaling-out for a DU" may include adding a new DU to a DU pool containing DUs. In one embodiment of the present disclosure, "scale-out for a DU" and "scaling-out for a DU" may include migrating cells contained in a DU to another DU (e.g., a newly added DU).

[0038] In one embodiment of the present disclosure, “scale-in for a DU” and “scaling-in for a DU” may include removing the DU from the DU pool. In one embodiment of the present disclosure, “scale-in for a DU” and “scaling-in for a DU” may include transferring cells included in the DU to another DU (e.g., an existing DU).

[0039] In one embodiment of the present disclosure, the term "task" may be a classification or grouping of operations performed by one or more devices based on any criteria. For example, a "task" may include each step in the process of transferring a cell. For example, a "task" may include a classification or grouping of operations for cell transfer based on a point in time at which failure or success is determined in the process of transferring a cell. In one embodiment of the present disclosure, a "task" may include a group of operations performed by one or more devices for a specific purpose or result. For example, a "task of transferring C from A to B" may include operations to be performed by "A," operations to be performed by "B," and operations to be performed by another device to transfer C from A to B.

[0040] FIG. 1 is a diagram showing an example of a wireless communication system structure according to one embodiment of the present disclosure.

[0041] In one embodiment of the present disclosure, a wireless communication system may include a core network (110) and a radio access network (RAN) (120). The core network (110) may include user authentication information for each telecommunications company, and may be a platform network that is wired and connected to servers and systems of various service providers via optical cables.

[0042] In one embodiment of the present disclosure, the RAN (120) may include at least one RU (Radio Unit) (128_1, 128_2, 128_3, 128_4, 128_5, 128_6), at least one DU (Distributed Unit) (124_1, 124_2, 124_3, 124_4), and a CU (centralized unit) (122). In one embodiment of the present disclosure, the RAN (120) may include, but is not limited to, a vRAN (virtualized Radio Access Network) system. For example, the RAN (120) may include a 5GS (5G System), 4GS, or other wireless communication system, and may also refer to a wireless communication system to be developed in the future.

[0043] In one embodiment of the present disclosure, the CU (122) may be an entity that performs functions of some layers among the protocol layers of a network. For example, the CU (122) may be an entity that performs network functions of the RRC (Radio Resource Control) layer and the PDCP (Packet Data Convergence Protocol) layer, but the functions that the CU (122) can process are not limited to the functions of the RRC layer and the PDCP layer described above. For example, the CU (122) may perform functions such as QoS (Quality of Service) setting, packet reordering, and security setting and processing. For example, the CU (122) may mean a vCU (virtualized-CU) of a vRAN system, but is not limited thereto.

[0044] One CU (122) can be connected to N DUs, where N can be any integer greater than 1. The CU (122) and the DUs (124_1, 124_2, 124_3, 124_4) can be connected by an interface. For example, the interface between the CU (122) and the DUs (124_1, 124_2, 124_3, 124_4) can be an F1 interface (or a mid-hole interface). For example, the F1 interface can include F1-C, which is an F1 interface of a control plane, and F1-U, which is an F1 interface of a user plane.

[0045] RAN (120) may include DU (124_1), DU (124_2), and DU (124_3). DU (124_1), DU (124_2), and DU (124_3) may perform the same function, but DU (124_3) is described as an example below.

[0046] In one embodiment of the present disclosure, DU (124_3) may be an entity that performs functions of some layers among the protocol layers of the network except for some layers performed by CU (122). For example, DU (124_3) may be an entity that performs network functions (e.g., baseband functions) of RLC (Radio Link Control) layer, MAC (Medium Access Control) layer, and PHY (Physical) layer, but the functions that DU (124_3) can process are not limited to the functions of the RLC layer, MAC layer, and PHY layer described above. For example, DU (124_3) may perform a buffer function, a radio resource scheduling function, a data reprocessing function, etc. For example, DU (124_3) may be a vDU (virtualized-DU) of a vRAN system, but is not limited thereto. For example, DU (124_3) may correspond to a component module, an arbitrary processing operation unit, a distribution unit performing arbitrary processing, software, etc. For example, DU (124_3) may correspond to one server.

[0047] One DU can be connected to N RUs, where N can be any integer greater than 1. Referring to FIG. 1, DU (124_1) can be connected to RU (128_1), ..., and RU (128_2), DU (124_2) can be connected to RU (128_3), ..., and RU (128_4), and DU (124_3) can be connected to RU (128_5), ..., and RU (128_6). In one embodiment of the present disclosure, DU (124_3) and RU (128_5, 128_6) can be connected by an interface. For example, the interface between DU (124_3) and RU (128_5, 128_6) can be a front haul interface.

[0048] RU(128_1), RU(128_2), RU(128_3), RU(128_4), RU(128_5) and RU(128_6) can perform the same function, but RU(128_6) is described as an example below.

[0049] In one embodiment of the present disclosure, RU (128_6) may be an entity that performs some functions of the PHY layer other than those handled by DU (124_3). For example, DU (124_3) may perform the function of the high-PHY layer, and RU (128_6) may perform the function of the low-PHY layer. For example, RU (128_6) may perform a data transmission and reception function via an RF antenna.

[0050] In existing RAN systems, a DU can be connected 1:1 to a cell site containing one or more RUs, and the DU's processing capacity can be determined based on the maximum traffic that can enter the cell site. Based on traffic trends over time, the peak traffic hours are limited (e.g., 5:00 PM to 9:00 PM), and outside of these hours, unused DU resources, i.e., remaining available resources, may exist.

[0051] According to one embodiment of the present disclosure, a vRAN system may employ a virtualized DU (vDU) pooling technology that breaks the 1:1 relationship between existing DUs and cell sites (a collection of RUs) and virtualizes DUs by pooling them. This can reduce the number of servers required to build a RAN system and reduce capital expenditures (CAPEX). Furthermore, compared to existing RAN systems, power consumption can be reduced and operating expenditures (OPEX) can be reduced.

[0052] A vRAN system according to one embodiment of the present disclosure may employ vCU pooling technology, which pools and virtualizes CUs. This can reduce the number of servers required to build a RAN system and reduce capital expenditures (CAPEX). Furthermore, compared to existing RAN systems, power consumption can be reduced and operating expenditures (OPEX) can be reduced.

[0053] In one embodiment of the present disclosure, a vDU scaling method may be used in the RAN (120) to efficiently utilize server resources by dynamically scaling out or scaling in DUs according to current traffic conditions. In the case of scaling out, a DU (124_4) may be newly created in the RAN (120), but is not limited thereto. For example, the DU (124_4) may already exist in the RAN (120). In the case of scaling in, the DU (124_4) may already exist in the RAN (120).

[0054] Hereinafter, DU (124_3) may be denoted as the first DU (124_3), and DU (124_4) may be denoted as the second DU (124_4). In the case of scale-out in FIG. 1, the first DU (124_3) may correspond to the source DU, and the second DU (124_4) may correspond to the target DU. In the case of scale-in in FIG. 1, the first DU (124_3) may correspond to the target DU, and the second DU (124_4) may correspond to the source DU. The first DU (124_3) and the second DU (124_4) may be connected via an inter DU interface (Xd interface) (126).

[0055] In one embodiment of the present disclosure, scale-out may include adding a new DU (e.g., a second DU (124_4)) to the DU pool for the CU (122). For example, when the amount of traffic that a first DU (124_3) included in the DU pool must process increases, a second DU (124_4) may be added to the DU pool. For example, adding the second DU (124_4) to the DU pool may include adding a module corresponding to the second DU (124_4) to the DU pool. For example, adding the second DU (124_4) to the DU pool may include initiating operation of an additional server capable of processing data. When the capacity or performance of processing data of the first DU (124_3) (e.g., an existing server) reaches its limit, a second DU (124_4) (a non-limiting example, a server with similar specifications) can be added to the communication system using scale-out. In this case, the cell whose data is being processed by the first DU (124_3) can be migrated from the first DU (124_3) to the second DU (124_4), so that the cell's data can be processed by the second DU (124_4).

[0056] In an embodiment of the present disclosure, scale-in may include removing a second DU (124_4) included in a DU pool. For example, when the amount of traffic that the DUs included in the DU pool must process decreases, the second DU (124_4) may be removed from the DU pool. For example, removing the second DU (124_4) from the DU pool may include removing a module corresponding to the second DU (124_4). For example, removing the second DU (124_4) from the DU pool may include stopping the operation of a server that was processing data. By using scale-in, the number of servers that are no longer needed to operate can be reduced, and resources can be saved. For scale-in, a cell whose data is processed by the second DU (124_4) may be migrated from the second DU (124_4) to the first DU (124_3), so that the cell's data is processed by the first DU (124_3).

[0057] In one embodiment of the present disclosure, in addition to the case of scaling by adding or removing the second DU (124_4) from the DU pool, a cell whose data is processed by the second DU (124_4) may be migrated from the second DU (124_4) to the first DU (124_3) so that the cell's data is processed by the first DU (124_3), or a cell whose data is processed by the first DU (124_3) may be migrated from the first DU (124_3) to the second DU (124_4) so ​​that the cell's data is processed by the second DU (124_4). For example, a cell may be migrated from the first DU (124_3) with a large traffic volume to the second DU (124_4) with a relatively small traffic volume so that the cell's data is processed by the second DU (124_4).

[0058] If each process that was sequentially performed for the migration of the target cell fails during the process, it may be impossible to proceed to the next process, or multiple UEs associated with the target cell may be disconnected altogether. If a failure occurs during the migration of the target cell but communication is resumed without performing a restoration to the original settings, all UEs may be disconnected. This is because if MAC scheduling is resumed without restoring or detecting an abnormal connection or a disconnection, a normal communication environment cannot be provided to the UE. A radio link failure (RLF) may occur due to the UE disconnection, and since the UEs perform random access (RA), a load may be placed on other DUs, and the service quality of the communication network may be degraded.

[0059] In one embodiment of the present disclosure, a method for determining success or failure at each step during the target cell transfer process may be provided. In one embodiment of the present disclosure, a recovery method and scope may be provided based on failure at each step.

[0060] FIG. 2 is a flowchart illustrating an example of a cell transfer method from a source DU to a target DU according to one embodiment of the present disclosure.

[0061] In explaining Fig. 2, any explanation that overlaps with the explanation given above in Fig. 1 may be omitted.

[0062] FIG. 2 may illustrate an example of a method (200) in which an electronic device transfers a cell from a source DU to a target DU. The electronic device performing the method (200) is an electronic device including a cell transfer module (e.g., a scaling agent module) that manages, controls, or processes cell transfer, and may include a device of the source DU, a device of the target DU, and / or another separate device. For example, the source DU (or the device of the source DU) may include a cell transfer module. For example, the target DU (or the device of the target DU) may include a cell transfer module. For example, another device separate from the source DU and the target DU may include a cell transfer module.

[0063] Referring to FIG. 2, a method (200) according to one embodiment of the present disclosure may include steps 210 to 290. In one embodiment of the present disclosure, steps 210 to 290 of the method (200) may be executed by a cell transfer module included in an electronic device. In one embodiment of the present disclosure, steps 210 to 290 of the method (200) may be executed by at least one processor included in the electronic device. The method (200) is not limited to that illustrated in FIG. 2, and in one or more embodiments, steps not illustrated in FIG. 2 may be further included, or some steps may be omitted.

[0064] In one embodiment of the present disclosure, the electronic device can perform the method (200) upon identifying a DU scaling (e.g., scale-out, scale-in) request (or instruction) of an operations, administration, and maintenance (OAM) module. In one embodiment of the present disclosure, the electronic device can perform the method (200) upon identifying a cell transfer request (or instruction) of the OAM module. For example, the electronic device can identify a cell transfer request (or instruction) from a source DU (e.g., a first DU) to a target DU (e.g., a second DU) from the OAM module. For example, the electronic device can identify a transfer request (or instruction) of a source DU to a target cell from the OAM module.

[0065] In one embodiment of the present disclosure, the electronic device may perform the method (200) upon determining DU scaling. In one embodiment of the present disclosure, the electronic device may perform the method (200) upon determining cell migration. For example, the electronic device may determine cell migration from a source DU to a target DU. For example, the electronic device may determine migration of the source DU to a target cell.

[0066] In step 210, the electronic device may control a first operation of duplicating cell configuration information for a target cell of a source DU to a target DU. In one embodiment of the present disclosure, the electronic device may transfer cell configuration information for a target cell included (or configured) in the source DU to the target DU. The cell configuration information for the target cell may include information about a frequency band of the target cell, a radio resource scheduling method, a common signal transmitted to one or more UEs associated with the target cell, and the like.

[0067] In one embodiment of the present disclosure, the electronic device can transfer cell configuration information for a target cell included in at least one of an RLC layer, a MAC layer, or a PHY layer of a source DU to at least one of the RLC layer, the MAC layer, or the PHY layer of the target DU. For example, the electronic device can transfer cell configuration information included in the RLC layer of the source DU to the RLC layer of the target DU. For example, the electronic device can transfer cell configuration information included in the MAC layer of the source DU to the MAC layer of the target DU. For example, the electronic device can transfer cell configuration information included in the PHY layer of the source DU to the PHY layer of the target DU. In one embodiment of the present disclosure, the cell configuration information included in each of the RLC layer, the MAC layer, and the PHY layer of the source DU may be different from each other, may be partially different, or may be the same from each other.

[0068] In one embodiment of the present disclosure, the electronic device can transfer the target cell by setting the target cell in the target DU using the parameters used to set the target cell in the source DU. For example, the electronic device can create (or set) cell configuration information for the target cell in the target DU using the parameters used to create (or set) cell configuration information for the target cell in the source DU.

[0069] In one embodiment of the present disclosure, the electronic device can copy the cell configuration information for the target cell contained in the source DU to the target DU. For example, the electronic device can control the source DU to copy the cell configuration information for the target cell and provide it to the target DU. For example, the cell configuration information for the target cell can be transferred, copied, or replicated from the source DU to the target DU through an interface between the DUs. For example, the electronic device can obtain the cell configuration information for the target cell from the source DU and provide it to the target DU.

[0070] At step 212, the electronic device can determine whether the first task has failed.

[0071] In step 220, the electronic device may initialize cell configuration information for the target cell of the target DU based on determining that the first task has failed. For example, the electronic device may initialize configuration values ​​for the target cell of the target DU based on the failure of the first task.

[0072] In one embodiment of the present disclosure, the electronic device may release (or remove) cell configuration information for a target cell in a target DU upon failure of a first task. For example, if at least a portion of the cell configuration information for a target cell in a source DU is replicated (or copied, set) to the target DU and the first task fails, the electronic device may remove at least a portion of the replicated cell configuration information from the target DU. For example, if the first task fails, the electronic device may remove information or data generated in the target DU by the task of replicating the cell configuration information for the target cell to the target DU.

[0073] In step 230, the electronic device may control a second task of replicating one or more first UE contexts for the target cell of the source DU to the target DU based on determining the success of the first task. In one embodiment of the present disclosure, the electronic device may transfer one or more first UE contexts for the target cell, included in the MAC layer of the source DU, to the MAC layer of the target DU. For example, the electronic device may transfer (or copy, replicate) one or more first UE contexts for the target cell from the source DU (e.g., the MAC layer of the source DU) to the target DU (e.g., the MAC layer of the target DU).

[0074] The one or more first UE contexts for the target cell may include UE contexts for one or more UEs associated with the target cell, which are included (or configured) in the source DU. For example, the one or more first UE contexts for the target cell may include MAC contexts configured (or configured) in the MAC layer of the DU. For example, the one or more first UE contexts for the target cell may include UE contexts created (or configured) or accumulated in the source DU (e.g., in the MAC layer) until the second task.

[0075] In one embodiment of the present disclosure, the electronic device may use parameters used to create (or set) a first UE context for one or more UEs associated with the target cell in the source DU (e.g., MAC layer) to create (or set) one or more first UE contexts for the target cell in the target DU (e.g., MAC layer).

[0076] In one embodiment of the present disclosure, an electronic device can copy (or replicate) one or more first UE contexts for a target cell, which are included in a source DU (e.g., MAC layer), to a target DU (e.g., MAC layer). For example, the electronic device can control the source DU to copy (or replicate) one or more first UE contexts for a target cell, which are included in the MAC layer, and provide them to the target DU. For example, one or more first UE contexts for a target cell can be transferred, copied, or replicated from the source DU to the target DU through an inter-DU interface. For example, the electronic device can obtain one or more first UE contexts for a target cell from the source DU and provide them to the target DU.

[0077] At step 232, the electronic device can determine whether the second task has failed.

[0078] In step 240, the electronic device may perform cell release processing for the target DU based on determining that the second task has failed. In one embodiment of the present disclosure, the electronic device may control to release the target cell in the target DU based on determining that the second task has failed. In one embodiment of the present disclosure, the electronic device may release (or remove) at least one first UE context for the target cell replicated (or set) in the target DU (e.g., MAC layer) based on the failure of the second task.

[0079] For example, if at least a portion of one or more first UE contexts for a target cell of a source DU are replicated (or copied, set) to the target DU and the second operation fails, the electronic device may remove at least a portion of the one or more first UE contexts replicated from the target DU. For example, if the second operation fails, the electronic device may remove information or data generated in the target DU by the operation of replicating one or more first UE contexts to the target DU.

[0080] In one embodiment of the present disclosure, based on determining the failure of the second task, the electronic device may initialize cell configuration information for the target cell of the target DU in step 220. For example, based on the failure of the second task, the electronic device may perform cell release processing for the target DU in step 240, and then initialize the target DU in step 220.

[0081] In step 250, based on determining the success of the second task, the electronic device may control a third task of switching (or changing) the fronthaul path from the source DU to the target DU, replicating one or more second UE contexts for the target cell of the source DU to the target DU, and switching (or changing) the control path from the source DU to the target DU. In one embodiment of the present disclosure, the electronic device may switch (or change) the fronthaul path, i.e., the RU-PHY interface from 'RU of the target cell' - 'PHY layer of the source DU' to 'RU of the target cell' - 'PHY layer of the target DU'. In one embodiment of the present disclosure, the electronic device may switch (or change) the control path for each layer from the source DU to the target DU. In one embodiment of the present disclosure, the electronic device may transfer one or more second UE contexts for the target cell, which are included (or set) in the source DU, to the target DU.

[0082] The one or more second UE contexts for the target cell may include UE contexts for one or more UEs associated with the target cell that are included (or configured) in the source DU. For example, the one or more second UE contexts for the target cell may include MAC contexts that are configured (or configured) in the MAC layer of the DU. For example, the one or more second UE contexts for the target cell may include UE contexts that are created (or configured) or accumulated in the source DU (e.g., in the MAC layer) after the second operation. For example, the one or more second UE contexts for the target cell may include UE contexts that are created (or configured) or accumulated in the source DU (e.g., in the MAC layer) after duplication (or transfer) of a first UE context for the target cell.

[0083] At step 252, the electronic device can determine whether the third task has failed.

[0084] At step 260, the electronic device may switch (or change) the fronthaul path for the target cell back from the target DU to the source DU, or switch (or change) the control path for the target cell back from the target DU to the source DU, based on determining that the third task has failed. In one embodiment of the present disclosure, if the control path for the target cell is switched from the source DU to the target DU at step 250 and the third task has failed, the electronic device may revert the control path for the target cell from the target DU to the source DU.

[0085] In one embodiment of the present disclosure, if the fronthaul path for the target cell is switched from the source DU to the target DU in step 250 and the third task fails, the electronic device may restore the fronthaul path for the target cell from the target DU to the source DU. For example, if the RU-PHY interface is switched (or changed) from 'RU of the target cell' - 'PHY layer of the source DU' to 'RU of the target cell' - 'PHY layer of the target DU' and the third task fails, the electronic device may switch (or change) the RU-PHY interface from 'RU of the target cell' - 'PHY layer of the target DU' to 'RU of the target cell' - 'PHY layer of the source DU'.

[0086] In one embodiment of the present disclosure, after the electronic device re-switches the fronthaul path and / or the control path to the target cell, the electronic device can resume MAC scheduling of the source DU. In one embodiment of the present disclosure, after the electronic device re-switches the fronthaul path and / or the control path to the target cell, the electronic device can restart the queue of buffered fronthaul messages. For example, the queue of buffered fronthaul messages can be transmitted to the source DU.

[0087] In one embodiment of the present disclosure, the electronic device may perform cell release processing for the target DU at step 240 based on determining that the third task has failed. For example, the electronic device may release (or remove) a MAC context for a target cell replicated (or set) in the target DU based on the failure of the third task. For example, the electronic device may remove at least one first UE context for the target cell replicated (or set) in the target DU (e.g., MAC layer) and / or at least one second UE context for the target cell based on the failure of the third task.

[0088] For example, if at least a portion of one or more second UE contexts for the target cell of the source DU are replicated (or copied, set) to the target DU and the third task fails, the electronic device may remove at least a portion of the one or more second UE contexts replicated from the target DU. For example, if the third task fails, the electronic device may remove information, data generated in the target DU by the task of replicating one or more second UE contexts for the target cell to the target DU.

[0089] In one embodiment of the present disclosure, based on determining that the third task has failed, the electronic device may initialize cell configuration information for the target cell of the target DU at step 220. For example, based on the failure of the third task, the electronic device may switch the fronthaul path and / or the control path from the target DU to the source DU at step 260, perform cell release processing for the target DU at step 240, and then initialize the cell configuration information of the target DU at step 220.

[0090] Based on the failure of the first task, the second task, or the third task, in step 222, the electronic device may determine whether the number of attempts to transfer the target cell from the source DU to the target DU is less than the maximum number of attempts. In one embodiment of the present disclosure, if the first task, the second task, or the third task fails, the electronic device may initialize the target DU for the target cell and determine whether the number of attempts to transfer the cell from the source DU to the target DU is less than the maximum number of attempts to determine whether to retry the transfer of the target cell from the source DU to the target DU. The maximum number of attempts may be a preset (or determined) value.

[0091] In one embodiment of the present disclosure, the electronic device may determine not to retry cell transfer from the source DU to the target DU based on determining that the number of previous attempts is greater than or equal to the maximum number of attempts. For example, if the number of previous attempts is not less than the maximum number of attempts, the electronic device may determine not to retry cell transfer from the source DU to the target DU.

[0092] In one embodiment of the present disclosure, the electronic device may determine to retry the cell transfer from the source DU to the target DU based on determining that the number of previous attempts is less than the maximum number of attempts. For example, if the number of previous attempts is not greater than or equal to the maximum number of attempts, the electronic device may determine to retry the target cell transfer from the source DU to the target DU. Accordingly, the electronic device may re-perform method (200) based on determining that the number of previous attempts is less than the maximum number of attempts.

[0093] In step 270, based on determining the success of the third task, the electronic device may control (or perform) cell release processing for the PHY layer and MAC layer of the source DU. In one embodiment of the present disclosure, the electronic device may release a target cell for the PHY layer and MAC layer of the source DU. For example, the electronic device may remove (or release) cell configuration information for a target cell included (or set) in the PHY layer and MAC layer of the source DU. For example, the electronic device may remove (or release) a UE context (e.g., a MAC context) for a target cell included (or set) in the PHY layer and MAC layer of the source DU.

[0094] In one embodiment of the present disclosure, based on determining the success of the third task, the electronic device may restart the fronthaul message queue that was being buffered. For example, if the third task is successful, the fronthaul message queue that was being buffered may be transmitted to the target DU. In one embodiment of the present disclosure, if the third task is successful, the electronic device may transmit and receive data between the RU and the PHY layer of the target DU. In one embodiment of the present disclosure, if the data of the fronthaul message queue and the RU are smoothly transmitted to the target DU, the electronic device may control (or perform) cell release processing for the PHY layer and the MAC layer of the source DU.

[0095] In step 280, the electronic device may control a fourth operation of duplicating one or more third UE contexts for the target cell of the source DU to the target DU and switching one or more F1 paths for the target cell from the source DU to the target DU. In one embodiment of the present disclosure, the electronic device may transfer the third UE contexts for multiple UEs associated with the target cell from the source DU (e.g., RLC layer) to the target DU (e.g., RLC layer) on a per-UE basis. The one or more third UE contexts for the target cell may include UE contexts (e.g., RLC contexts) for one or more UEs associated with the target cell, which are included (or set) in the RLC layer of the source DU.

[0096] In one embodiment of the present disclosure, an electronic device can switch an F1 path for multiple UEs associated with a target cell from a source DU to a target DU on a per-UE basis. The F1 path can include a path (or interface) between a DU (e.g., an RLC layer of the DU) and a CU. The electronic device can switch an F1 path for multiple UEs associated with the target cell from 'the RLC layer of the source DU' to 'the RLC layer of the target DU' to 'the CU' on a per-UE basis. Multiple F1 paths can be configured for one UE.

[0097] For example, the electronic device can transfer a third UE context of a UE group including at least one of a plurality of UEs associated with the target cell from a source DU to a target DU, and switch an F1 path for the UE group from the source DU to the target DU. For example, the electronic device can sequentially transfer the third UE context and change the F1 path for the plurality of UE groups. Accordingly, the electronic device can transfer the third UE context and switch the F1 path multiple times per UE (i.e., per UE group) rather than transferring the third UE context or switching the F1 path for the plurality of UEs associated with the target cell all at once.

[0098] Even if the fourth task fails for some of the plurality of UEs associated with the target cell, the electronic device may not abort or restore the target cell transfer process. For example, even if the third UE context for some of the plurality of UEs associated with the target cell is not successfully transferred, or the F1 path for some of the UEs is not successfully switched, resulting in disconnection of the communication services of some of the UEs, the electronic device may not abort the target cell transfer. For example, if the communication services of some of the plurality of UEs are disconnected, some of the UEs may attempt to connect to the target cell and / or other cells through random access (RA).

[0099] In step 290, the electronic device can control (or perform) cell release processing for the RLC layer of the source DU. In one embodiment of the present disclosure, the electronic device can release a target cell for the RLC layer of the source DU. For example, the electronic device can remove (or release) cell configuration information for a target cell included (or set) in the RLC layer of the source DU. For example, the electronic device can remove (or release) a UE context (e.g., an RLC context) for a target cell included (or set) in the RLC layer of the source DU.

[0100] FIG. 3 is a diagram illustrating an example of an electronic device controlling a first task according to one embodiment of the present disclosure.

[0101] In explaining Fig. 3, any explanation that overlaps with the explanation given above in Fig. 1 or Fig. 2 may be omitted.

[0102] In one embodiment of the present disclosure, the electronic device includes a cell transfer module (e.g., a scaling agent module) that manages, controls, or processes cell transfer, and may include a device of a source DU (310), a device of a target DU (320), and / or another device. For example, the source DU (310) or the target DU (320) may include a cell transfer module.

[0103] In one embodiment of the present disclosure, the electronic device may control a first task of replicating cell configuration information for a target cell of a source DU (310) to a target DU (320). For example, a cell transfer module of the electronic device may control the source DU (310) and / or the target DU (320) to perform an operation for the first task. For example, the cell transfer module of the electronic device may transmit a request, an instruction, a message, a command, data, and / or information to the source DU (310) and / or the target DU (320) to perform an operation for the first task.

[0104] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can replicate cell configuration information for a target cell included (or set) in an RLC layer of a source DU (310) to an RLC layer of a target DU (320). For example, the electronic device can transfer cell configuration information for a target cell in an RLC layer of the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can replicate cell configuration information for a target cell included (or set) in an RLC layer of the source DU (310) to an RLC layer of the target DU (320) by controlling the source DU (310) and / or the target DU (320).

[0105] Referring to FIG. 3, the source DU (310) can identify (or acquire) (330) cell configuration information (i.e., RLC cell configuration information) for a target cell of the RLC layer. The source DU (310) can set (or duplicate) (332) the RLC cell configuration information set in the source DU (310) to the target DU (320). For example, the source DU (310) can provide information, parameters, or data for setting (or duplicating, transferring) the RLC cell configuration information to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) the setting of the RLC cell configuration information to the target DU (320). The target DU (320) can provide a response (334) to the source DU (310) regarding the completion (or success) of the setup (or replication, transfer) of RLC cell setup information.

[0106] For example, if RLC cell configuration information is successfully set in the target DU (320), the target DU (320) can provide a response indicating completion (or success) of the setting (or replication, transfer) of the RLC cell configuration information to the source DU (310). For example, if RLC cell configuration information is not successfully set in the target DU (320), the target DU (320) can provide a response indicating incompletion (or failure) of the setting (or replication, transfer) of the RLC cell configuration information to the source DU (310).

[0107] In one embodiment of the present disclosure, the electronic device can identify a response indicating completion (or success) of setting up RLC cell configuration information for the target DU (320) or a response indicating incompletion (or failure) of setting up. For example, the electronic device can identify a response indicating completion (or success) of copying (or setting up, transfer) RLC cell configuration information to the target DU (320) or a response indicating incompletion (or failure) of copying (or setting up, transfer) RLC cell configuration information to the target DU (320). For example, the electronic device can receive a response indicating completion (or success) of setting up RLC cell configuration information or incompletion (or failure) of setting up RLC cell configuration information from the source DU (310) or the target DU (320).

[0108] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can replicate cell configuration information for a target cell included (or set) in a MAC layer of a source DU (310) to a MAC layer of a target DU (320). For example, the electronic device can transfer cell configuration information for a target cell in the MAC layer of the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can replicate cell configuration information for a target cell included (or set) in the MAC layer of the source DU (310) to the MAC layer of the target DU (320) by controlling the source DU (310) and / or the target DU (320).

[0109] Referring to FIG. 3, the source DU (310) can identify (or acquire) (340) cell configuration information (i.e., MAC cell configuration information) for a target cell of the MAC layer. The source DU (310) can set (or replicate) (342) the MAC cell configuration information set in the source DU (310) to the target DU (320). For example, the source DU (310) can provide information, parameters, or data for setting (or replicating, transferring) the MAC cell configuration information to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) the setting of the MAC cell configuration information to the target DU (320). The target DU (320) can provide a response (344) to the source DU (310) regarding the completion (or success) of the setting (or replicating, transferring) of the MAC cell configuration information.

[0110] For example, if MAC cell configuration information is successfully set in the target DU (320), the target DU (320) can provide a response indicating completion (or success) of setting (or replication, transfer) of the MAC cell configuration information to the source DU (310). For example, if MAC cell configuration information is not successfully set in the target DU (320), the target DU (320) can provide a response indicating incompletion (or failure) of setting (or replication, transfer) of the MAC cell configuration information to the source DU (310).

[0111] In one embodiment of the present disclosure, the electronic device can identify a response indicating completion (or success) of setting MAC cell configuration information for the target DU (320) or a response indicating incompletion (or failure) of setting. For example, the electronic device can identify a response indicating completion (or success) or incompletion (or failure) of duplication (or setting, transfer) of MAC cell configuration information to the target DU (320). For example, the electronic device can receive a response indicating completion (or success) or incompletion (or failure) of setting MAC cell configuration information from the source DU (310) or the target DU (320).

[0112] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can replicate cell configuration information for a target cell included (or set) in a PHY layer of a source DU (310) to a PHY layer of a target DU (320). For example, the electronic device can transfer cell configuration information for a target cell in a PHY layer of the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can replicate cell configuration information for a target cell included (or set) in a PHY layer of the source DU (310) to a PHY layer of the target DU (320) by controlling the source DU (310) and / or the target DU (320).

[0113] Referring to FIG. 3, the source DU (310) can identify (or acquire) (350) cell configuration information (i.e., PHY cell configuration information) for a target cell of a PHY layer. The source DU (310) can set (or copy) (352) the PHY cell configuration information set in the source DU (310) to the target DU (320). For example, the source DU (310) can provide information, parameters, or data for setting (or copying, transferring) the PHY cell configuration information to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) setting of the PHY cell configuration information to the target DU (320). The target DU (320) can provide a response (354) to the source DU (310) regarding the completion (or success) of the setting (or duplication, transfer) of the PHY cell setting information.

[0114] For example, if PHY cell configuration information is successfully set in the target DU (320), the target DU (320) can provide a response indicating completion (or success) of setting (or duplication, transfer) of the PHY cell configuration information to the source DU (310). For example, if PHY cell configuration information is not successfully set in the target DU (320), the target DU (320) can provide a response indicating incompletion (or failure) of setting (or duplication, transfer) of the PHY cell configuration information to the source DU (310).

[0115] In one embodiment of the present disclosure, the electronic device can identify a response indicating completion (or success) of setting up PHY cell configuration information for the target DU (320) or a response indicating incompletion (or failure) of setting up. For example, the electronic device can identify a response indicating completion (or success) of copying (or setting, transfer) PHY cell configuration information to the target DU (320) or a response indicating incompletion (or failure) of copying (or setting, transfer) PHY cell configuration information to the target DU (320). For example, the electronic device can receive a response indicating completion (or success) of setting up PHY cell configuration information or incompletion (or failure) of setting up PHY cell configuration information from the source DU (310) or the target DU (320).

[0116] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) may identify (or determine) whether a first task has failed (i.e., succeeded). For example, the electronic device may identify (or determine) whether the first task has failed based on a response indicating whether the setup for each of the identified (or received) RLC layer, MAC layer, and PHY layer has been completed (or succeeded).

[0117] For example, if a setup completion (or success) response for at least one of the RLC layer, the MAC layer, or the PHY layer is not identified (or received), the electronic device may determine that the first task has failed. For example, if a setup incomplete response for at least one of the RLC layer, the MAC layer, or the PHY layer is identified (or received), the electronic device may determine that the first task has failed. For example, if the number of setup completion responses identified (or received) is less than a predetermined reference number (e.g., 3), the electronic device may determine that the first task has failed.

[0118] Although FIG. 3 illustrates an example in which cell configuration information for a target cell is transferred in the order of the RLC layer, MAC layer, and PHY layer, the present invention is not limited thereto. For example, the electronic device may transfer cell configuration information for the target cell in a different order. For example, the electronic device may arbitrarily transfer cell configuration information for the target cell. For example, the electronic device may transfer cell configuration information for the target cell simultaneously, independently, or in parallel for each of the RLC layer, MAC layer, and PHY layer.

[0119] FIG. 4 is a diagram illustrating an example of removing cell configuration information from a target DU upon failure of a first task in one embodiment of the present disclosure.

[0120] In explaining Fig. 4, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 3 may be omitted.

[0121] An electronic device (e.g., a cell transfer module) may initialize the target DU (320) for the target cell based on the failure of the first task. In one embodiment of the present disclosure, upon identifying (or determining) the failure of the first task, the electronic device may initialize (or remove, release) cell configuration information for the target cell in the target DU (320). For example, the electronic device may remove cell configuration information for the target cell from at least one of the RLC layer, the MAC layer, or the PHY layer of the target DU (320).

[0122] In one embodiment of the present disclosure, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to remove cell configuration information for a target cell from the target DU (320). For example, the electronic device can transmit a request, an instruction, a message, a command, data and / or information to the source DU (310) and / or the target DU (320) to perform an operation for releasing cell configuration information for a target cell of the target DU (320). For example, the electronic device can transmit a message, a command, data and / or information requesting (or instructing, commanding) release of cell configuration information for the target cell to the target DU (320), thereby causing the target DU (320) to remove (or delete) cell configuration information for the target cell. For example, the electronic device may cause the source DU (310) to transmit a message, command, data and / or information requesting (or instructing, commanding) the release of cell configuration information for the target cell to the target DU (320).

[0123] Referring to FIG. 4, the source DU (310) can remove (410) cell configuration information for a target cell from the target DU (320). For example, the source DU (310) can provide a message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell of the target DU (320). The target DU (320) can delete the cell configuration information for the target cell according to the message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell from the source DU (310) (or electronic device). Since there is no separate path change or scheduling interruption, the target DU can be initialized by releasing the RLC cell configuration information, MAC cell configuration information and / or PHY cell configuration information set in the target DU (320).

[0124] According to one embodiment of the present disclosure, operations following failure of the first task are not limited to those illustrated in FIG. 4. For example, operations not illustrated in FIG. 4 may be further performed following failure of the first task.

[0125] FIG. 5 is a diagram illustrating an example of an electronic device controlling a second task according to one embodiment of the present disclosure.

[0126] In explaining Fig. 5, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 4 may be omitted.

[0127] In one embodiment of the present disclosure, if the first task is successful, the electronic device can control a second task of replicating one or more first UE contexts for a target cell of the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to perform the operation for the second task. For example, the cell transfer module of the electronic device can transmit a request, an instruction, a message, a command, data, and / or information to the source DU (310) and / or the target DU (320) to perform the operation for the first task.

[0128] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can replicate one or more first UE contexts (e.g., MAC contexts) for a target cell included (or set) in a MAC layer of a source DU (310) to a MAC layer of a target DU (320). For example, the electronic device can migrate one or more first UE contexts for a target cell from a MAC layer of the source DU (310) to a MAC layer of the target DU (320). For example, the cell transfer module of the electronic device can replicate one or more first UE contexts for a target cell included (or set) in a MAC layer of the source DU (310) to a MAC layer of the target DU (320) by controlling the source DU (310) and / or the target DU (320).

[0129] In one embodiment of the present disclosure, the electronic device can identify a response indicating completion (or success) of setup of one or more first UE contexts for the target DU (320) or a response indicating incompletion (or failure) of setup. For example, the electronic device can identify a response indicating completion (or success) of duplication (or transfer) of one or more first UE contexts to the target DU (320) or a response indicating incompletion (or failure) of setup. For example, the electronic device can receive a response indicating completion (or success) or incompletion (or failure) of setup of one or more first UE contexts for the target DU (320) from the source DU (310) or the target DU (320).

[0130] Referring to FIG. 5, the source DU (310) can identify (or obtain) (510) a list of UEs associated with a target cell. For example, the source DU (310) can identify a plurality of UEs associated with the target cell. The source DU (310) can identify (or obtain) (520) a first UE context for each of the plurality of UEs and set (530) the first UE context in the target DU (320). The target DU (320) can provide a response (e.g., return) (540) to the source DU (310) regarding whether the setting (or duplication, transfer) of the first UE context has been completed (or succeeded) for each of the plurality of UEs.

[0131] For example, if the first UE context is successfully established in the target DU (320), the target DU (320) may provide a response indicating completion (or success) of the establishment (or duplication, transfer) of the first UE context for the target DU (320) to the source DU (310). For example, if the first UE context is not successfully established in the target DU (320), the target DU (320) may provide a response indicating incompletion (or failure) of the establishment (or duplication, transfer) of the first UE context for the target DU (320) to the source DU (310).

[0132] As illustrated, the identification (520), setting (530), and response (540) of the first UE context may be performed in a repeating loop for each of the plurality of UEs. For example, the identification (520) of the first UE context, the setting (530) of the first UE context, and the response (540) may be performed sequentially for each of the plurality of UEs, but is not limited thereto. For example, the identification (520), setting (530), and response (540) of the first UE context may be performed simultaneously, independently, or in parallel for each of the plurality of UEs.

[0133] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) may identify (or determine) whether a second task has failed (i.e., succeeded). For example, the electronic device may identify (or determine) whether the second task has failed based on a response (540) regarding whether the setup (or replication, or transfer) of the identified (or received) first UE context has been completed (or succeeded).

[0134] In one embodiment of the present disclosure, the electronic device may identify (or determine) the failure of the second task based on whether the number of replication completion responses of one or more first UE contexts for the target cell is less than (or equal to) a reference number of responses. For example, the electronic device may determine that the second task has failed if the number of replication completion responses of the first UE contexts for each UE is less than (or equal to) a reference number of responses.

[0135] In one embodiment of the present disclosure, the electronic device can identify the failure of the second task based on whether the ratio of the number of replication completion responses of the first UE context to the number of a plurality of UEs (e.g., UEs included in the UE list) associated with the target cell is less than (or below) a reference ratio. For example, the electronic device can determine that the second task has failed if the ratio of the number of replication completion responses of the first UE context for each UE to the number of a plurality of UEs is less than (or below) a reference ratio (e.g., 0.5%).

[0136] Referring to FIG. 5, the source DU (310) can identify (550) the number of returns indicating the completion (or success) of the establishment (or replication, transfer) of the first UE context for the target cell. If the number of identified returns is less than (or below) a reference number of responses, the source DU (310) (or electronic device) can determine that the second task has failed. If the number of identified returns is equal to or greater than (or exceeds) the reference number of responses, the source DU (310) (or electronic device) can determine that the second task has succeeded.

[0137] FIG. 6 is a diagram illustrating an example of removing MAC context and cell configuration information from a target DU upon failure of a second task in one embodiment of the present disclosure.

[0138] In describing FIG. 6, any description that overlaps with the description described above in any one of FIGS. 1 to 5 may be omitted. FIG. 6 may illustrate an example in which an electronic device (e.g., a cell transfer module) initializes a target DU (320) for a target cell based on a failure of a second task.

[0139] In one embodiment of the present disclosure, upon identifying (or determining) a failure of the second task, the electronic device may remove (or release) at least one first UE context for the target cell in the target DU (320). For example, the electronic device may remove (or release) at least one first UE context (e.g., MAC context) for the target cell in the MAC layer of the target DU (320).

[0140] In one embodiment of the present disclosure, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to remove at least one first UE context for a target cell from the target DU (320). For example, the electronic device can transmit a request, an instruction, a message, a command, data and / or information to the source DU (310) and / or the target DU (320) to perform an operation for releasing the at least one first UE context. For example, the electronic device can transmit a message, a command, data and / or information requesting (or instructing, commanding) the release of at least one first UE context for the target cell to the target DU (320), thereby causing the target DU (320) to remove (or delete) the at least one first UE context. For example, the electronic device may cause the source DU (310) to transmit a message, command, data and / or information requesting (or instructing, commanding) the release of at least one first UE context to the target DU (320).

[0141] In one embodiment of the present disclosure, upon identifying (or determining) the failure of the second task, the electronic device may remove (or release) the cell configuration information for the target cell from the target DU (320). For example, if the second task fails, the electronic device may remove the MAC context for the target cell from the target DU (320) and remove (or release) the cell configuration information for the target cell.

[0142] Referring to FIG. 6, the source DU (310) can remove (610) a MAC context (e.g., at least one first UE context) for a target cell from the target DU (320). For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the removal of at least one first UE context for the target cell. The target DU (320) can delete the MAC context for the target cell according to the message, command, data and / or information requesting (or instructing, commanding) the removal of the MAC context for the target cell from the source DU (310) (or electronic device).

[0143] Referring to FIG. 6, the source DU (310) can remove (620) cell configuration information for the target cell from the target DU (320) after removing the MAC context (610). For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell. The target DU (320) can delete the cell configuration information for the target cell according to the message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell from the source DU (310) (or electronic device).

[0144] Although FIG. 6 illustrates an example of removing cell configuration information (620) after removing a MAC context (610), the present invention is not limited thereto. For example, the electronic device may perform the removal of the MAC context and the removal of the cell configuration information simultaneously, independently, or in parallel. For example, the electronic device may remove the MAC context after removing the cell configuration information for the target cell.

[0145] According to one embodiment of the present disclosure, operations following failure of the second task are not limited to those illustrated in FIG. 6. For example, following failure of the second task, operations not illustrated in FIG. 6 may be performed additionally, or some operations illustrated in FIG. 6 may be omitted.

[0146] FIG. 7 is a diagram illustrating an example of an electronic device controlling a third task according to one embodiment of the present disclosure.

[0147] In explaining Fig. 7, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 6 may be omitted.

[0148] In one embodiment of the present disclosure, if the second task is successful, the electronic device can control a third task of switching (or changing) a fronthaul path from the source DU (310) to the target DU (320), replicating (or setting) one or more second UE contexts for a target cell of the source DU (310) to the target DU (320), and changing a control path (e.g., a control path of a PHY layer and / or a MAC layer) from the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to perform the operations for the third task. For example, the cell transfer module of the electronic device can transmit a request, an instruction, a message, a command, data, and / or information to the source DU (310) and / or the target DU (320) to perform the operations for the third task.

[0149] In one embodiment of the present disclosure, the electronic device may buffer a fronthaul message for the source DU (310). For example, the electronic device may buffer a fronthaul message for a target cell of the source DU (310). For example, the electronic device may pause the transmission of a fronthaul message queue for the target cell of the source DU (310).

[0150] In one embodiment of the present disclosure, the electronic device can switch the fronthaul path from the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to change the fronthaul path from the source DU (310) to the target DU (320). In one embodiment of the present disclosure, the electronic device can replicate one or more second UE contexts (e.g., MAC contexts) for the target cell of the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to set (or transfer, replicate) one or more second UE contexts for the target cell of the source DU (310) to the target DU (320). In one embodiment of the present disclosure, the electronic device can change the control path from the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to change the control path from the source DU (310) to the target DU (320).

[0151] Referring to FIG. 7, the source DU (310) can buffer (710) a fronthaul message for the source DU (310). For example, the source DU (310) can request buffering processing of the fronthaul message to a module that manages the fronthaul message (e.g., a fronthaul message handler module, a fronthaul splitter module).

[0152] Referring to FIG. 7, the source DU (310) can identify (720) a fronthaul path for a target cell and change (722) the fronthaul path for the target cell to the target DU (320). For example, the source DU (310) can provide data, parameters, or information for setting up a fronthaul path for the target cell to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) setting up a fronthaul path for the target cell.

[0153] The target DU (320) can perform an operation to establish a fronthaul path for the target cell. The source DU (310) can release (724) the fronthaul connection for the target cell. For example, while the target DU (320) is establishing a fronthaul path for the target cell, the source DU (310) can release the fronthaul connection for the target cell. The target DU (320) can provide a response (e.g., return) (726) to the source DU (310) indicating completion (or success) of establishing the fronthaul path for the target cell.

[0154] Referring to FIG. 7, the source DU (310) can change (730) the control path for the target cell to the target DU (320). For example, the source DU (310) can provide data, parameters, or information for setting up a control path for the target cell to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) setting up a control path for the target cell.

[0155] The target DU (320) can perform an operation to establish a control path for the target cell. The source DU (310) can release (732) the control path connection for the target cell. For example, while the target DU (320) is establishing a control path for the target cell, the source DU (310) can release the control path connection for the target cell. The target DU (320) can provide a response (e.g., return) (734) to the source DU (310) indicating completion (or success) of establishing a control path for the target cell.

[0156] Referring to FIG. 7, before duplicating (or transferring) one or more second UE contexts (e.g., MAC contexts) for a target cell, the source DU (310) may suspend (740) MAC scheduling for the target cell. The source DU (310) may duplicate (or transfer, establish) (742) one or more second UE contexts for the target cell to the target DU (320). The one or more second UE contexts for the target cell may include UE contexts generated or accumulated in the MAC layer of the source DU (310) after duplicating (or transferring) the first UE contexts and before suspending MAC scheduling.

[0157] For example, the source DU (310) may provide the target DU (320) with data, parameters, or information for setting up one or more second UE contexts for the target cell. For example, the source DU (310) may transmit a message, command, data, and / or information requesting (or instructing, commanding) setting up one or more second UE contexts for the target cell.

[0158] The target DU (320) may perform an operation to establish one or more second UE contexts for the target cell in the target DU (320). As one or more second UE contexts for the target cell are established (or replicated), the target DU (320) may initiate (or initiate) (744) MAC scheduling for the target cell. The target DU (320) may provide a response (e.g., return) (746) to the source DU (310) indicating completion (or success) of establishing one or more second UE contexts for the target cell.

[0159] In one embodiment of the present disclosure, the electronic device can identify the number of completed responses for the third task. For example, the electronic device can identify the number of completed responses for the third task within a predetermined period of time (e.g., a set period of time). For example, the electronic device can start a timer for a predetermined period of time when the third task starts, and identify the number of completed responses for the third task when the timer expires. In one embodiment of the present disclosure, the electronic device can identify the number of completed responses for the third task received from the target DU (320).

[0160] For example, the predetermined time for the third task may be a short period of time during which the UE user cannot perceive a disconnection from the communication system. For example, the predetermined time may be a short period of time during which the UE's connection with the target cell is not lost. For example, the predetermined time may be a time period set by the mobile operator (e.g., 5 ms).

[0161] In one embodiment of the present disclosure, the electronic device may identify (or determine) the failure of the third task based on the number of completed responses identified within a predetermined time period being less than (or equal to) a predetermined number. For example, the predetermined number may be predetermined based on the number of sub-tasks included in the third task. For example, the predetermined number may be determined based on the number of sub-tasks that change or replicate from a source DU to a target DU.

[0162] For example, the third task may include a first sub-task that switches (or changes) the fronthaul path from the source DU (310) to the target DU (320), a second sub-task that changes the control path from the source DU (310) to the target DU (320), and a third sub-task that replicates (or sets up) one or more second UE contexts for the target cell of the source DU (310) to the target DU (320). In this case, the predetermined number may be 3.

[0163] Referring to FIG. 7, the source DU (310) can identify (750) the number of completion responses (e.g., returns) within a set time. For example, the source DU (310) can determine that the third task has failed if the number of completion responses from the target DU (320) is less than 3. For example, the source DU (310) can determine that the third task has succeeded if the number of completion responses from the target DU (320) is 3.

[0164] Figure 7 illustrates an example in which the first sub-task, the second sub-task, and the third sub-task are performed in parallel, but is not limited thereto. For example, the first sub-task, the second sub-task, and / or the third sub-task may be performed in a predetermined order.

[0165] FIG. 8A is a diagram illustrating an example of reconfiguring the fronthaul path and the control path and removing MAC context and cell configuration information from the target DU in response to a failure of the third task in one embodiment of the present disclosure.

[0166] In describing Fig. 8a, any description that overlaps with the description described above in any one of Figs. 1 to 7 may be omitted. Fig. 8a may illustrate an example in which an electronic device (e.g., a cell transfer module) initializes a target DU (320) for a target cell based on a failure of a third task.

[0167] In one embodiment of the present disclosure, upon identifying (or determining) a failure of the third task, the electronic device may re-switch the fronthaul path for the target cell from the target DU (320) to the source DU (310). For example, the electronic device may change from the RU-target DU (320) back to the RU-source DU (310). For example, the electronic device may release the fronthaul path for the target cell between the PHY layer of the target DU (320) and the RU, and establish a fronthaul path for the target cell between the PHY layer of the source DU (310) and the RU.

[0168] In one embodiment of the present disclosure, a cell transfer module of an electronic device may control the source DU (310) and / or the target DU (320) to change the fronthaul path for a target cell from the target DU (320) to the source DU (310). For example, the electronic device may transmit a request, an instruction, a message, a command, data, and / or information to the source DU (310) and / or the target DU (320) to perform an operation for changing the fronthaul path for the target cell.

[0169] For example, the electronic device can control the target DU (320) to release the fronthaul path for the target cell by transmitting a message, command, data or information requesting (or instructing, commanding) the release of the fronthaul path for the target cell to the target DU (320). For example, the electronic device can control the source DU (310) to establish (or create) the fronthaul path for the target cell by transmitting a message, command, data or information requesting (or instructing, commanding) the establishment of the fronthaul path for the target cell to the source DU (310). Accordingly, the fronthaul path (or interface) between the PHY layer of the target DU (320) and the RU for the target cell can be released, and the fronthaul path (or interface) between the PHY layer of the source DU (310) and the RU for the target cell can be reset.

[0170] In one embodiment of the present disclosure, upon identifying (or determining) a failure of the third task, the electronic device may re-switch the control path for the target cell from the target DU (320) to the source DU (310). For example, the electronic device may change the control path from the RU-target DU (320) back to the RU-source DU (310). For example, the electronic device may release the fronthaul path for the target cell between the PHY layer of the target DU (320) and the RU, and establish the fronthaul path for the target cell between the PHY layer of the source DU (310) and the RU.

[0171] In one embodiment of the present disclosure, a cell transfer module of an electronic device may control the source DU (310) and / or the target DU (320) to change the fronthaul path for a target cell from the target DU (320) to the source DU (310). For example, the electronic device may transmit a request, an instruction, a message, a command, data, and / or information to the source DU (310) and / or the target DU (320) to perform an operation for changing the control path for the target cell.

[0172] For example, the electronic device can control the target DU (320) to release the control path for the target cell by transmitting a message, command, data or information requesting (or instructing, commanding) the release of the control path for the target cell to the target DU (320). For example, the electronic device can control the source DU (310) to establish (or create) the control path for the target cell by transmitting a message, command, data or information requesting (or instructing, commanding) the establishment of the control path for the target cell to the source DU (310). Accordingly, the control path (or interface) between the PHY layer of the target DU (320) and the RU for the target cell can be released, and the control path (or interface) between the PHY layer of the source DU (310) and the RU for the target cell can be reset.

[0173] In one embodiment of the present disclosure, as the fronthaul and control path are changed (or set) to the source DU (310), the electronic device can restart MAC scheduling for the target cell of the source DU (310). For example, the electronic device can cause the source DU (310) to start MAC scheduling for the target cell by transmitting a message, command, data, or information requesting (or instructing, commanding) the source DU (310) to start MAC scheduling for the target cell.

[0174] In one embodiment of the present disclosure, when the fronthaul and control paths are changed (or set) to the source DU (310), the electronic device can stop buffering the fronthaul message for the target cell of the source DU (310). For example, the electronic device can stop buffering the fronthaul message for the target cell of the source DU (310) by transmitting a message, command, data, or information requesting (or instructing, commanding) the stop buffering of the fronthaul message for the target cell of the source DU (310) to the source DU (310) or a fronthaul message management module (e.g., a fronthaul message handler, a fronthaul splitter).

[0175] In one embodiment of the present disclosure, upon identifying (or determining) a failure of the third task, the electronic device may remove (or release) at least one first UE context for the target cell and / or at least one second UE context for the target cell in the target DU (320). For example, the electronic device may remove a UE context (e.g., a MAC context) set (or included) for the target cell in the MAC layer of the target DU (320).

[0176] In one embodiment of the present disclosure, the electronic device may control the source DU (310) and / or the target DU (320) to remove a MAC context (e.g., at least one first UE context and / or at least one second UE context) for a target cell in the target DU (320). For example, the electronic device may transmit a message, a command, data and / or information requesting (or instructing, commanding) the release of the MAC context for the target cell to the target DU (320), thereby causing the target DU (320) to remove (or delete) the MAC context for the target cell. For example, the electronic device may cause the source DU (310) to transmit a message, a command, data and / or information requesting (or instructing, commanding) the release of the MAC context for the target cell to the target DU (320).

[0177] In one embodiment of the present disclosure, upon identifying (or determining) a failure of the third task, the electronic device may remove (or cancel) cell configuration information for the target cell from the target DU (320). For example, the electronic device may remove cell configuration information for the target cell from each of the RLC layer, MAC layer, and PHY layer of the target DU (320).

[0178] Referring to FIG. 8A, the source DU (310) can release (810) the fronthaul path connection of the target DU (320) to the target cell. For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the release of the fronthaul path connection to the target cell, and the target DU (320) can release the fronthaul path connection to the target cell. The source DU (310) can perform an operation to reconnect (or reset) (812) the fronthaul path to the target cell. For example, while the target DU (320) releases the fronthaul path connection to the target cell, the source DU (310) can reconnect the fronthaul path to the target cell. The target DU (320) can provide a response (814) to the source DU (310) indicating the completion (or success) of the release of the fronthaul path to the target cell.

[0179] Referring to FIG. 8A, the source DU (310) can release (820) the control path connection of the target DU (320) to the target cell. For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the release of the control path connection to the target cell, and the target DU (320) can release the control path connection to the target cell. The source DU (310) can perform an operation to reconnect (or reset) (822) the control path to the target cell. For example, while the target DU (320) releases the control path connection to the target cell, the source DU (310) can reconnect the control path to the target cell. The target DU (320) can provide a response (824) indicating the completion (or success) of the release of the control path to the target cell to the source DU (310).

[0180] Although Figure 8a illustrates that the fronthaul path reconfiguration and control path reconfiguration for the target cell are performed in parallel, this is not limited to this. For example, the fronthaul path reconfiguration and control path reconfiguration for the target cell may be performed in a predetermined order or in an arbitrary order.

[0181] Referring to FIG. 8A, the source DU (310) may restart MAC scheduling for the target cell (830) and stop buffering fronthaul messages for the target cell (840). The source DU (310) may remove (850) a MAC context (e.g., at least one first UE context and / or at least one second UE context) for the target cell from the target DU (320). For example, the source DU (310) may provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the removal of the MAC context for the target cell of the target DU (320). The target DU (320) may delete the MAC context for the target cell according to the message, command, data and / or information requesting (or instructing, commanding) the removal of the MAC context for the target cell from the source DU (310).

[0182] Referring to FIG. 8A, the source DU (310) can remove (860) cell configuration information for a target cell from the target DU (320). For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell. The target DU (320) can delete (e.g., initialize) cell configuration information for the target cell set in the target DU (320) according to the message, command, data and / or information requesting (or instructing, commanding) the removal of cell configuration information for the target cell from the source DU (310).

[0183] According to one embodiment of the present disclosure, the operations following the failure of the third task are not limited to those illustrated in FIG. 8A. For example, following the failure of the third task, operations not illustrated in FIG. 8A may be performed additionally, or some operations illustrated in FIG. 8A may be omitted. According to one embodiment of the present disclosure, the order of operations following the failure of the third task is not limited to that illustrated in FIG. 8A. For example, the operations following the failure of the third task may be performed in a different order, simultaneously, independently, and / or in parallel.

[0184] FIG. 8b is a diagram illustrating an example of removing MAC context and MAC / PHY cell configuration information from a source DU upon success of a third task in one embodiment of the present disclosure.

[0185] In explaining Fig. 8b, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 8a may be omitted.

[0186] In one embodiment of the present disclosure, upon identifying (or determining) the success of the third task, the electronic device may stop buffering the fronthaul message for the target cell of the target DU (320). For example, the electronic device may stop buffering the fronthaul message so that the target DU (320) can receive or transmit the fronthaul message for the target cell. The electronic device may control the source DU (310), the target DU (320), or a module managing the fronthaul message (e.g., a fronthaul message handler, a fronthaul splitter) to stop buffering the fronthaul message for the target cell of the target DU (320). For example, the electronic device may cause the target DU (320) to stop buffering the fronthaul message for the target cell by transmitting a message, command, data, or information requesting (or instructing, commanding) the target DU (320) or the fronthaul message management module.

[0187] In one embodiment of the present disclosure, upon identifying (or determining) the success of the third task, the electronic device may initiate MAC scheduling for the target cell of the target DU (320). The electronic device may control the source DU (310) and / or the target DU (320) to initiate MAC scheduling for the target cell of the target DU (320). For example, the electronic device may transmit a message, command, data, or information requesting (or instructing, commanding) the start of MAC scheduling for the target cell to the target DU (320), thereby causing the target DU (320) to initiate MAC scheduling for the target cell.

[0188] In one embodiment of the present disclosure, upon identifying (or determining) the success of the third task, the electronic device may initialize the MAC layer and the PHY layer of the source DU (310) for the target cell. For example, the electronic device may release (or remove) the MAC context, MAC cell configuration information, and PHY cell configuration information for the target cell from the source DU (310). In one embodiment of the present disclosure, the electronic device may control the source DU (310) and / or the target DU (320) to release (or remove) the MAC context, MAC cell configuration information, and PHY cell configuration information for the target cell from the source DU (310).

[0189] Referring to FIG. 8b, the source DU (310) can stop (870) the buffering of the fronthaul message for the target cell of the target DU (320). For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the stop buffering of the fronthaul message for the target cell, and the target DU (320) can stop the buffering of the fronthaul message for the target cell. Referring to FIG. 8b, the source DU (310) can start (880) the MAC scheduling for the target cell of the target DU (320). For example, the source DU (310) can provide the target DU (320) with a message, command, data and / or information requesting (or instructing, commanding) the start of the MAC scheduling for the target cell, and the target DU (320) can start the MAC scheduling for the target cell.

[0190] Referring to FIG. 8b, the source DU (310) can release (or control) (860) the MAC context, MAC cell configuration information, and PHY cell configuration information for the target cell.

[0191] According to one embodiment of the present disclosure, the operations upon the success of the third task are not limited to those illustrated in FIG. 8B. For example, upon the failure of the third task, operations not illustrated in FIG. 8B may be additionally performed, or some operations illustrated in FIG. 8B may be omitted. According to one embodiment of the present disclosure, the order of operations upon the success of the third task is not limited to that illustrated in FIG. 8B. For example, the operations upon the success of the third task may be performed in a different order, simultaneously, independently, and / or in parallel.

[0192] FIG. 9 is a diagram illustrating an example of an electronic device controlling a fourth task according to one embodiment of the present disclosure.

[0193] In explaining Fig. 9, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 8b may be omitted.

[0194] In one embodiment of the present disclosure, if the third task is successful, the electronic device can control a fourth task of replicating third UE contexts (e.g., RLC contexts) of multiple UEs associated with the target cell of the source DU (310) to the target DU (320) and switching the F1 paths of the multiple UEs from the source DU (310) to the target DU (320). For example, the cell transfer module of the electronic device can control the source DU (310) and / or the target DU (320) to perform the operations for the fourth task.

[0195] In one embodiment of the present disclosure, the electronic device can control the fourth task on a per-UE basis. For example, the electronic device can repeatedly perform replication of the third UE context and switching of the F1 path on a per-UE basis for multiple UEs associated with the target cell. The electronic device can attempt replication of the third UE context and switching of the F1 path on a per-UE basis for all UEs associated with the target cell.

[0196] For example, the electronic device may replicate third UE contexts of some UEs among a plurality of UEs associated with the target cell to the target DU (320), switch F1 paths of some UEs from the source DU (310) to the target DU (320), and then replicate third UE contexts of some other UEs among a plurality of UEs associated with the target cell to the target DU (320), and switch F1 paths of some other UEs from the source DU (310) to the target DU (320).

[0197] For example, the electronic device may replicate a third UE context for a first UE group including some UEs among a plurality of UEs associated with the target cell to the target DU (320), switch the F1 path of the first UE group from the source DU (310) to the target DU (320), and in a next loop replicate a third UE context for a second UE group including some other UEs among a plurality of UEs associated with the target cell to the target DU (320), and switch the F1 path of the second UE group from the source DU (310) to the target DU (320).

[0198] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can identify (or obtain) third UE contexts for n (1≤n≤number of UEs ('# of UEs')) UEs among a plurality of UEs associated with a target cell. The third UE contexts can include UE contexts (e.g., RLC contexts) set in (or included in) an RLC layer of the source DU (310). For example, the electronic device can control the source DU (310) to identify (or obtain) third UE contexts for n UEs associated with the target cell of the source DU (310).

[0199] In one embodiment of the present disclosure, the electronic device can replicate (or set, transfer) third UE contexts for n UEs associated with a target cell of a source DU (310) to a target DU (320). For example, the electronic device can replicate third UE contexts (e.g., RLC contexts) for n UEs associated with a target cell of an RLC layer of the source DU (310) to an RLC layer of the target DU (320). For example, the electronic device can control the source DU (310) and / or the target DU (320) to replicate third UE contexts for n UEs associated with a target cell of the source DU (310) to the target DU (320).

[0200] In one embodiment of the present disclosure, an electronic device (e.g., a cell transfer module) can identify F1 paths for n (1≤n≤the number of UEs (# of UEs)) UEs among a plurality of UEs associated with a target cell. The F1 paths can include paths (or interfaces) between a DU (e.g., an RLC layer of the DU) and a CU. For one UE, multiple F1 paths can be established. For example, the electronic device can control a source DU (310) to identify (or acquire) F1 paths for n UEs associated with the target cell.

[0201] In one embodiment of the present disclosure, the electronic device can change (or switch) the F1 path for n UEs associated with the target cell of the source DU (310) from the source DU (310) to the target DU (320). For example, the electronic device can control the source DU (310) and / or the target DU (320) to change the F1 path for n UEs associated with the target cell of the source DU (310) from the source DU (310) to the target DU (320). For example, the electronic device can release the F1 path between the source DU (310) and the CU, and establish (or create) the F1 path between the target DU (320) and the CU, for the n UEs.

[0202] In one embodiment of the present disclosure, among n UEs associated with a target cell, a UE whose communication with the core network via the target cell is cut off may perform random access (RA). For example, a UE whose communication with the core network via the target cell is cut off while the fourth task is being performed may perform random access (RA). For example, during the process of duplicating a third UE context for n UEs associated with the target cell and changing the F1 path, a UE for which the third UE context duplication or the change of the F1 path fails may have its communication with the core network via the target cell cut off.

[0203] Referring to FIG. 9, a source DU (310) can identify (910) RLC contexts for n UEs associated with a target cell. The source DU (310) can set (or duplicate, transfer) (912) the RLC contexts for the n UEs associated with the target cell to a target DU (320). For example, the source DU (310) can provide data, parameters, or information for setting up RLC contexts for the n UEs associated with the target cell to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) the setting up (or duplication) of one or more second UE contexts for the target cell. The target DU (320) can perform an operation for setting up RLC contexts for the n UEs associated with the target cell to the target DU (320). The target DU (320) may provide a response (914) to the source DU (310) indicating completion (or success) of the setup of RLC contexts for n UEs associated with the target cell.

[0204] Referring to FIG. 9, the source DU (310) can identify (920) an F1 path for n UEs associated with a target cell. The source DU (310) can change (or switch) (922) the F1 path for n UEs associated with the target cell from the source DU (310) to the target DU (320). For example, the source DU (310) can provide data, parameters, or information for changing the F1 path for n UEs associated with the target cell to the target DU (320). For example, the source DU (310) can transmit a message, command, data, and / or information requesting (or instructing, commanding) the establishment (or creation) of an F1 path for n UEs associated with the target cell to the target DU (320). The target DU (320) may perform an operation to establish an F1 path for n UEs associated with the target cell between the target DU (320) (e.g., RLC layer) and the CU. The source DU (310) may perform an operation to release an F1 path for n UEs associated with the target cell between the source DU (310) (e.g., RLC layer) and the CU. The target DU (320) may provide a response (924) to the source DU (310) indicating completion (or success) of establishing an F1 path for n UEs associated with the target cell.

[0205] In one embodiment of the present disclosure, among n UEs associated with a target cell, a UE whose communication with the core network via the target cell is cut off can perform RA. Since restoring the configuration and path of the already changed MAC layer and PHY layer is more expensive, UEs whose transfer to the RLC layer has failed can individually perform RA.

[0206] The iterative loop illustrated in Figure 9 may be repeated until replication of the third UE context and switching of the F1 path are attempted for all UEs associated with the target cell.

[0207] Although FIG. 9 illustrates that the F1 path change (922) is performed after the RLC context is established (912), this is not a limitation. For example, the F1 path change (922) may be performed before the RLC context is established (912). For example, the RLC context establishment (912) and the F1 path change (922) may be performed simultaneously, independently, or in parallel.

[0208] FIG. 10 is a drawing showing an example of an operating method of an electronic device according to one embodiment of the present disclosure.

[0209] In explaining Fig. 10, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 9 may be omitted.

[0210] FIG. 10 may illustrate an example of an operating method (1000) of an electronic device. An electronic device performing the method (1000) may include a cell transfer module (e.g., a scaling agent module) that manages, controls, or processes cell transfer, and may include a device of a source DU, a device of a target DU, and / or other devices. For example, a device of a source DU may include a cell transfer module. For example, a device of a target DU may include a cell transfer module. For example, a device other than the source DU and the target DU may include a cell transfer module.

[0211] Referring to FIG. 10 , a method (1000) according to one embodiment of the present disclosure may include steps 1010 to 1030. In one embodiment of the present disclosure, steps 1010 to 1030 of the method (1000) may be executed by at least one processor included in an electronic device. The method (1000) is not limited to that illustrated in FIG. 10 , and in one or more embodiments, steps not illustrated in FIG. 10 may be further included, or some steps may be omitted.

[0212] In step 1010, the electronic device may control a first operation of replicating cell configuration information for a target cell of the first DU to the second DU, for migration of the target cell from the first DU to the second DU.

[0213] In step 1020, the electronic device may identify whether one or more tasks for transferring the target cell from the first DU to the second DU have failed. In one embodiment of the present disclosure, the electronic device may identify the failure of the first task. For example, the electronic device may determine the failure of the first task if a response indicating completion (or success) of replication of cell configuration information for at least one layer of the second DU is not identified.

[0214] In one embodiment of the present disclosure, the electronic device can identify the success of the first task. If the first task is successful, the electronic device can control a second task of replicating one or more first UE contexts for the target cell of the first DU to the second DU. In one embodiment of the present disclosure, the electronic device can identify the failure of the second task based on the number of replication completion responses of one or more first UE contexts being less than a reference number of responses.

[0215] In one embodiment of the present disclosure, the electronic device can identify the success of the first task and the success of the second task. If the first and second tasks are successful, the electronic device can control a third task of switching the fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing the control path from the first DU to the second DU. In one embodiment of the present disclosure, the electronic device can identify the failure of the third task based on a number of completion responses identified within a predetermined time period being less than a predetermined number.

[0216] In step 1030, the electronic device may remove cell configuration information from the second DU based on a failure of at least one of the one or more tasks. In one embodiment of the present disclosure, the electronic device may remove cell configuration information from the second DU based on a failure of the first task. In one embodiment of the present disclosure, if the second task fails, the electronic device may remove at least one first UE context for the target cell from the second DU and remove cell configuration information from the second DU.

[0217] In one embodiment of the present disclosure, if the third task fails, the electronic device can re-switch the fronthaul path from the second DU to the first DU, remove at least one first UE context for the target cell from the second DU, and remove cell configuration information from the second DU. In one embodiment of the present disclosure, if the third task fails, the electronic device can re-switch the control path from the second DU to the first DU, remove at least one first UE context for the target cell from the second DU, and remove cell configuration information from the second DU. In one embodiment of the present disclosure, based on the failure of the third task, the electronic device can remove at least one first UE context for the target cell and at least one second UE context for the target cell from the second DU, and remove cell configuration information from the second DU.

[0218] In one embodiment of the present disclosure, the electronic device can control a fourth task of replicating third UE contexts of a plurality of UEs associated with a target cell of a first DU to a second DU based on the success of the first task, the second task, and the third task, and switching the F1 path of the plurality of UEs from the first DU to the second DU. At least one UE among the plurality of UEs whose communication with the core network via the target cell is disconnected can perform RA.

[0219] FIG. 11 is a drawing showing an example of an electronic device according to one embodiment of the present disclosure.

[0220] In explaining Fig. 11, any explanation that overlaps with the explanation given above in any one of Figs. 1 to 10 may be omitted.

[0221] The electronic device (1100) illustrated in FIG. 11 is an electronic device that performs cell transfer operations for a DU, and may be a server device. For example, the electronic device (1100) may be a communication device that constitutes a RAN, such as a server device that performs an RU function, a server device that performs a DU function, a server device that performs a CU function, a server device that performs an OAM function, or a server device that constitutes an existing RAN, or may be a separate server device that controls cell transfer (e.g., a scaling agent device, etc.).

[0222] In one embodiment of the present disclosure, the electronic device (1100) may include, but is not limited to, at least one processor (1110) and memory (1120).

[0223] The processor (1110) is electrically connected to components included in the electronic device (1100) and can execute operations or data processing related to control and / or communication of the components included in the electronic device (1100). In one embodiment of the present disclosure, the processor (1110) can load and process requests, commands, or data received from at least one of the other components into a memory and store the processing result data in the memory. The processor (1110) is a component that controls a series of processes so that the electronic device (1100) operates according to the above-described embodiments, and may be configured with one or more processors.

[0224] One or more processors included in the processor (1110) may be circuitry such as a System on Chip (SoC), an Integrated Circuit (IC), etc. One or more processors included in the processor (1110) may include at least one of a general-purpose processor such as a central processing unit (CPU), a Micro Processor Unit (MPU), an application processor (AP), a Digital Signal Processor (DSP), a graphics-only processor such as a GPU (graphic processing unit) or a VPU (vision processing unit), an artificial intelligence-only processor such as an NPU (neural processing unit), or a communication-only processor such as a CP (communication processor). When one or more processors included in the processor (1110) are artificial intelligence-only processors, the artificial intelligence-only processor may be designed with a hardware structure specialized for processing a specific artificial intelligence model.

[0225] The processor (1110) may include various processing circuits and / or multiple processors. For example, the term "processor" as used in this disclosure, including the claims, may include various processing circuits including at least one processor. One or more of the at least one processor may be configured to perform one or more functions of the present disclosure, individually and / or collectively in a distributed manner. In this disclosure, when "processor," "at least one processor," or "one or more processors" is described as being configured to perform multiple functions, this may include situations where one processor performs some of the functions and other processor(s) perform other parts of the functions, and situations where a single processor performs all of the functions. Furthermore, the at least one processor may include a combination of processors that perform various functions in a distributed manner. The at least one processor may execute program instructions to achieve or perform various functions.

[0226] The processor (1110) can write data to the memory (1120) or read data stored in the memory (1120), and in particular, process data according to predefined operation rules or artificial intelligence models by executing a program or at least one instruction stored in the memory (1120). The processor (1110) can be controlled to process input data according to predefined operation rules, algorithms, methods, or models stored in the memory (1120). The processor (1110) can be controlled to process input data based on data stored in the memory (1120). The processor (1110) can perform operations of predefined operation rules, algorithms, methods, or models stored in the memory (1120) using the input data.

[0227] The memory (1120) is electrically connected to the processor (1110) and may store one or more modules, algorithms, operating rules, models, programs, commands, or data related to the operation of components included in the electronic device (1100). For example, the memory (1120) may store one or more modules, algorithms, operating rules, models, programs, commands, or data for processing and controlling the processor (1110). The memory (1120) may be configured as a storage medium or a combination of storage media such as a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory, etc.), a RAM (Random Access Memory), a SRAM (Static Random Access Memory), a ROM (Read-Only Memory), an EEPROM (Electrically Erasable Programmable Read-Only Memory), a PROM (Programmable Read-Only Memory), a magnetic memory, a magnetic disk, an optical disk, etc., but is not limited thereto. The memory (1120) may not exist separately and may be configured to be included in the processor (1110). The memory (1120) may be configured as a volatile memory, a nonvolatile memory, or a combination of a volatile memory and a nonvolatile memory. A program or at least one instruction for performing operations according to the above-described embodiments may be stored in the memory (1120). The memory (1120) may also provide stored data to the processor (1110) at the request of the processor (1110).

[0228] In one embodiment of the present disclosure, the memory (1120) may store data or information identified, acquired, generated, or determined by the electronic device (1100). The memory (1120) may store data or information identified, acquired, generated, or determined by the electronic device (1100) in a compressed form.

[0229] Some modules (e.g., cell transfer modules) that perform at least one operation of the electronic device (1100) may be implemented as hardware modules, software modules, and / or a combination thereof. The memory (1120) may include software modules that perform at least some of the operations of the electronic device (1100) described above. In one embodiment of the present disclosure, the modules included in the memory (1120) may perform operations by being executed by the processor (1110). For example, the modules (i.e., software modules) included in the memory (1120) may include programs, models, or algorithms that are executed according to the control or command of the processor (1110) and are configured to perform operations that derive output data for input data. Some modules that perform at least one operation of the electronic device (1100) may be configured as a plurality of sub-modules or may constitute a single module.

[0230] The electronic device (1100) may include more components than those illustrated in FIG. 11. In one embodiment of the present disclosure, the electronic device (1100) may further include a communication interface (or communication module) for communicating with an external device. In one embodiment of the present disclosure, the electronic device (1100) may further include an input / output device and / or an input / output interface.

[0231] In one embodiment of the present disclosure, the electronic device (1100) may include a communication module for communicating with an external device. For example, the communication module of the electronic device (1100) may support establishing a wired or wireless communication channel with another external device or server and performing communication through the established communication channel. For example, the electronic device (1100) may communicate with a server device that constitutes an existing RAN, such as a server device that performs an RU function, a server device that performs a DU function, a server device that performs a CU function, a server device that performs an OAM function, or a separate server device that controls cell transfer (e.g., a scaling agent device, etc.) through the communication module.

[0232] In one embodiment of the present disclosure, the communication module may receive signals, information, requests, and / or data from another external electronic device or server via wired communication or wireless communication, or transmit signals, information, requests, and / or data to another external electronic device or server. According to one embodiment of the present disclosure, the communication module may include a wireless communication module (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (e.g., a local area network (LAN) communication module, or a power line communication module), and may communicate with the external electronic device or server via at least one network, for example, a short-range communication network (e.g., Bluetooth, WiFi direct, or IrDA (infrared data association)) or a long-range communication network (e.g., a cellular network, the Internet, or a computer network (e.g., a LAN or a WAN)) using any one of the communication modules.

[0233] In one embodiment of the present disclosure, the electronic device (1100) can exchange signals, data, requests, and / or information with an external device via a network and communication module. For example, the electronic device (1100) and the external device can directly exchange signals, data, requests, and / or information, but this is not limited to the above. For example, the electronic device (1100) and the external device can also indirectly exchange signals, data, requests, and / or information via another device.

[0234] In any of FIGS. 1 to 11, the operations described as being performed by the electronic device may be performed by a cell transfer module of the electronic device. For example, the operations described as being performed by the electronic device may be performed by at least one processor of the electronic device.

[0235] In any one of FIGS. 1 to 11, the operations described as being performed by the source DU (310) may be performed by an electronic device in which the source DU (310) is included (or set up). For example, the operations described as being performed by the source DU (310) may be performed by at least one processor of the electronic device in which the source DU (310) is included (or set up).

[0236] In any one of FIGS. 1 to 11, the operation described as being performed by the target DU (320) may be performed by an electronic device in which the target DU (320) is included (or set up). For example, the operation described as being performed by the target DU (320) may be performed by at least one processor of the electronic device in which the target DU (320) is included (or set up).

[0237] In one embodiment of the present disclosure, a method of operating an electronic device may include a step of controlling a first task of replicating cell configuration information for a target cell of a first distributed unit (DU) to a second DU for migration of the target cell from the first DU to the second DU. In one embodiment of the present disclosure, the method of operating an electronic device may include a step of identifying whether one or more tasks for migration of the target cell from the first DU to the second DU have failed. In one embodiment of the present disclosure, the method of operating an electronic device may include a step of removing the cell configuration information from the second DU based on a failure of at least one task among the one or more tasks.

[0238] According to one embodiment of the present disclosure, determining whether a cell has failed at each step before the cell and recovering from the failure may be more advantageous in terms of time and resources than determining whether a cell has failed after the entire process is completed.

[0239] In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include the step of identifying a failure of the first task.

[0240] In one embodiment of the present disclosure, the step of removing the cell configuration information from the second DU based on a failure of the at least one task may include the step of removing the cell configuration information from the second DU based on a failure of the first task.

[0241] In one embodiment of the present disclosure, the step of identifying a failure of the first task may include a step of determining a failure of the first task based on a failure to identify a replication completion response of the cell configuration information for at least one layer of the second DU.

[0242] In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include the step of identifying success of the first task. In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include the step of controlling a second task for replicating one or more first user equipment (UE) contexts for the target cell of the first DU to the second DU based on the success of the first task. In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include the step of identifying failure of the second task based on a number of replication completion responses of the one or more first UE contexts being less than a reference number of responses.

[0243] In one embodiment of the present disclosure, the step of removing the cell configuration information from the second DU based on a failure of the at least one task may include the step of removing, based on a failure of the second task, at least one first UE context for the target cell from the second DU and removing the cell configuration information from the second DU.

[0244] In one embodiment of the present disclosure, the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed may include the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed may include the step of identifying whether the first operation has succeeded. In one embodiment of the present disclosure, the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU may include the step of identifying whether a second operation for replicating one or more first UE contexts for the target cell of the first DU to the second DU has succeeded. In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include controlling a third task of switching a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU. In one embodiment of the present disclosure, the step of identifying whether one or more tasks for transferring the target cell from the first DU to the second DU has failed may include identifying a failure of the third task based on a number of completion responses identified within a predetermined time period being less than a predetermined number.

[0245] In one embodiment of the present disclosure, the step of removing the cell configuration information from the second DU based on a failure of the at least one task may include the steps of: re-switching the fronthaul path from the second DU to the first DU, removing at least one first UE context for the target cell from the second DU, and removing the cell configuration information from the second DU based on a failure of the third task.

[0246] In one embodiment of the present disclosure, the step of removing the cell configuration information from the second DU based on a failure of the at least one task may include the step of rerouting the control path from the second DU to the first DU based on a failure of the third task, removing at least one first UE context for the target cell from the second DU, and removing the cell configuration information from the second DU.

[0247] In one embodiment of the present disclosure, the step of removing the cell configuration information from the second DU based on a failure of the at least one task may include the step of removing, based on a failure of the third task, at least one first UE context for the target cell and at least one second UE context for the target cell from the second DU, and removing the cell configuration information from the second DU.

[0248] In one embodiment of the present disclosure, the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU has failed may include the step of identifying whether the first operation has succeeded. In one embodiment of the present disclosure, the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU has failed may include the step of identifying whether a second operation for replicating one or more first UE contexts for the target cell of the first DU to the second DU has succeeded. In one embodiment of the present disclosure, the step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU has succeeded may include the step of identifying whether a third operation for switching a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU has succeeded.

[0249] In one embodiment of the present disclosure, the method may include, based on the success of the third task, controlling a fourth task of replicating third UE contexts of a plurality of UEs associated with the target cell of the first DU to the second DU and switching the F1 path of the plurality of UEs from the first DU to the second DU.

[0250] In one embodiment of the present disclosure, at least one UE among the plurality of UEs whose communication with the core network via the target cell is cut off can perform random access (RA).

[0251] In one embodiment of the present disclosure, the method may include a step of determining, based on the at least one failure, whether the number of transfer attempts of the target cell from the first DU to the second DU is less than a maximum number of attempts. In one embodiment of the present disclosure, the method may include a step of reattempting the transfer of the target cell from the first DU to the second DU based on determining that the number of transfer attempts is less than the maximum number of attempts.

[0252] In one embodiment of the present disclosure, a program for performing an operating method of an electronic device on a computer can be recorded on a computer-readable recording medium.

[0253] In one embodiment of the present disclosure, an electronic device may include a memory storing one or more instructions and at least one processor executing the one or more instructions stored in the memory. In one embodiment of the present disclosure, by the at least one processor executing the one or more instructions, the electronic device may control a first task of replicating cell configuration information for a target cell of a first distributed unit (DU) to a second DU for migration of the target cell from the first DU to the second DU. In one embodiment of the present disclosure, by the at least one processor executing the one or more instructions, the electronic device may identify whether one or more tasks for migration of the target cell from the first DU to the second DU have failed. In one embodiment of the present disclosure, by the at least one processor executing the one or more instructions, the electronic device may remove the cell configuration information from the second DU based on a failure of at least one of the one or more tasks.

[0254] In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can determine the failure of the first task based on the fact that a replication completion response of the cell configuration information for at least one layer of the second DU is not identified. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can remove the cell configuration information from the second DU based on the failure of the first task.

[0255] In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify the success of the first task. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can control a second task of replicating one or more first UE (user equipment) contexts for the target cell of the first DU to the second DU based on the success of the first task. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify the failure of the second task based on the number of replication completion responses of the one or more first UE contexts being less than a reference number of responses.

[0256] In one embodiment of the present disclosure, the electronic device can remove at least one first UE context for the target cell from the second DU and remove the cell configuration information from the second DU, based on a failure of the second task, by the at least one processor executing the one or more instructions.

[0257] In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify the success of the first task. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify the success of a second task of replicating one or more first UE contexts for the target cell of the first DU to the second DU. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can control a third task of switching a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU. In one embodiment of the present disclosure, the electronic device can identify a failure of the third task based on the number of completed responses identified within a predetermined time being less than a predetermined number by the at least one processor executing the one or more instructions.

[0258] In one embodiment of the present disclosure, the electronic device can cause the at least one processor to execute the one or more instructions, so that, based on the failure of the third task, the electronic device can re-switch the fronthaul path from the second DU to the first DU, remove at least one first UE context for the target cell from the second DU, and remove the cell configuration information from the second DU.

[0259] In one embodiment of the present disclosure, the electronic device can, by the at least one processor executing the one or more instructions, reroute the control path from the second DU to the first DU based on the failure of the third task, remove at least one first UE context for the target cell from the second DU, and remove the cell configuration information from the second DU.

[0260] In one embodiment of the present disclosure, the electronic device can remove at least one first UE context for the target cell and at least one second UE context for the target cell from the second DU, and remove the cell configuration information from the second DU, by the at least one processor executing the one or more instructions, based on the failure of the third task.

[0261] In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify success of the first task. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify success of a second task of replicating one or more first UE contexts for the target cell of the first DU to the second DU. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can identify success of a third task of switching a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU. In one embodiment of the present disclosure, by the at least one processor executing the one or more commands, the electronic device can control a fourth task of replicating third UE contexts of a plurality of UEs associated with the target cell of the first DU to the second DU, and switching the F1 path of the plurality of UEs from the first DU to the second DU, based on the success of the third task. In one embodiment of the present disclosure, at least one UE among the plurality of UEs whose communication with the core network via the target cell is disconnected can perform random access (RA).

[0262] In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can determine, based on the at least one failure, whether the number of transfer attempts of the target cell from the first DU to the second DU is less than a maximum number of attempts. In one embodiment of the present disclosure, when the at least one processor executes the one or more commands, the electronic device can reattempt transfer of the target cell from the first DU to the second DU based on determining that the number of transfer attempts is less than the maximum number of attempts.

[0263] A device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory storage medium" simply means a tangible device that does not contain signals (e.g., electromagnetic waves). This term does not distinguish between cases where data is permanently stored in the storage medium and cases where data is temporarily stored. For example, a "non-transitory storage medium" may include a buffer in which data is temporarily stored.

[0264] According to one embodiment, the method according to various embodiments disclosed in the present document may be provided as included in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., compact disc read-only memory (CD-ROM)), or may be distributed online (e.g., downloaded or uploaded) through an application store or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product (e.g., a downloadable app) may be temporarily stored or temporarily generated in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

Claims

1. In the operating method of an electronic device (1100), A step of controlling a first task of replicating cell setting information for the target cell of the first DU (310) to the second DU (320) for migration of the target cell from the first DU (distributed unit) (310); A step of identifying whether one or more tasks for transferring the target cell from the first DU (310) to the second DU (320) have failed; and A method comprising the step of removing the cell setup information from the second DU (320) based on a failure of at least one task among the one or more tasks.

2. In paragraph 1, The step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed is: Comprising a step of identifying a failure of the first task, Based on the failure of at least one of the above tasks, the step of removing the cell setup information from the second DU is: A method comprising the step of removing the cell setup information from the second DU based on the failure of the first task.

3. In paragraph 2, The step of identifying the failure of the above first task is: A method comprising the step of determining failure of the first task based on the fact that a replication completion response of the cell configuration information for at least one layer of the second DU is not identified.

4. In any one of paragraphs 1 to 3, The step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed is: A step of identifying the success of the first task; A step of controlling a second task for replicating one or more first UE (user equipment) contexts for the target cell of the first DU to the second DU based on the success of the first task; and A method comprising: identifying a failure of the second task based on a number of replication completion responses of the one or more first UE contexts being less than a reference number of responses.

5. In any one of paragraphs 1 to 4, Based on the failure of at least one of the above tasks, the step of removing the cell setup information from the second DU is: A method comprising the step of removing at least one first UE context for the target cell from the second DU based on a failure of the second task, and removing the cell configuration information from the second DU.

6. In any one of paragraphs 1 to 5, The step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed is: A step of identifying the success of the first task; A step of identifying success of a second operation of replicating one or more first UE contexts for the target cell of the first DU to the second DU; A third step of controlling a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU; and A method comprising the step of identifying a failure of the third task based on a number of completed responses identified within a predetermined time period being less than a predetermined number.

7. In paragraph 6, Based on the failure of at least one of the above tasks, the step of removing the cell setup information from the second DU is: A method comprising: based on a failure of the third task, re-switching the fronthaul path from the second DU to the first DU, removing at least one first UE context for the target cell in the second DU, and removing the cell configuration information in the second DU.

8. In paragraph 6 or 7, Based on the failure of at least one of the above tasks, the step of removing the cell setup information from the second DU is: A method comprising: based on a failure of the third task, rerouting the control path from the second DU to the first DU, removing at least one first UE context for the target cell from the second DU, and removing the cell configuration information from the second DU.

9. In any one of paragraphs 6 to 8, Based on the failure of at least one of the above tasks, the step of removing the cell setup information from the second DU is: A method comprising: removing at least one first UE context for the target cell and at least one second UE context for the target cell from the second DU based on a failure of the third task, and removing the cell configuration information from the second DU.

10. In any one of paragraphs 1 to 9, The step of identifying whether one or more operations for transferring the target cell from the first DU to the second DU have failed is: A step of identifying the success of the first task; a step of identifying success of a second operation of replicating one or more first UE contexts for the target cell of the first DU to the second DU; and A step of identifying success of a third operation of switching a fronthaul path from the first DU to the second DU, replicating one or more second UE contexts for the target cell of the first DU to the second DU, and changing a control path from the first DU to the second DU; The above method, Based on the success of the third task, a step of controlling a fourth task of duplicating third UE contexts of a plurality of UEs associated with the target cell of the first DU to the second DU and switching the F1 path of the plurality of UEs from the first DU to the second DU, A method in which at least one UE among the plurality of UEs, whose communication with the core network through the target cell is cut off, performs RA (random access).

11. In any one of paragraphs 1 to 10, A step of determining whether the number of previous attempts of the target cell from the first DU to the second DU is less than the maximum number of attempts based on at least one of the failures; and A method comprising the step of reattempting transfer of the target cell from the first DU to the second DU based on determining that the number of previous attempts is less than the maximum number of attempts.

12. A computer-readable recording medium having recorded thereon a program for performing the method of any one of claims 1 to 11 on a computer.

13. In an electronic device (1100), A memory (1120) storing one or more instructions; and At least one processor (1110) for executing one or more instructions stored in the memory (1120), The electronic device, by causing at least one processor (1110) to execute the one or more instructions, In order to migrate a target cell from a first DU (distributed unit) to a second DU, a first task is controlled to replicate cell setting information for the target cell of the first DU to the second DU, Identify whether one or more operations for transferring the target cell from the first DU to the second DU have failed, An electronic device that removes the cell configuration information from the second DU based on a failure of at least one of the above one or more tasks.

14. In paragraph 13, The electronic device, by causing at least one processor (1110) to execute the one or more instructions, Determining the failure of the first task based on the fact that a replication completion response of the cell setup information for at least one layer of the second DU is not identified, An electronic device that removes the cell setup information from the second DU based on the failure of the first task.

15. In paragraph 13 or 14, The electronic device, by causing at least one processor (1110) to execute the one or more instructions, Identify the success of the above first task, Based on the success of the first task, controlling a second task of replicating one or more first UE (user equipment) contexts for the target cell of the first DU to the second DU; An electronic device that identifies a failure of the second task based on a number of replication completion responses of the one or more first UE contexts being less than a reference number of responses.

Images