Method and apparatus for performing handover in non-terrestrial network

Abstract

A method for performing backhaul handover on a satellite backhaul link, according to the present disclosure, may comprise the operations of: acquiring, from at least one of a base station and a fixed wireless access (FWA), orbit information and traffic load information about each of a source satellite and a target satellite; on the basis of the acquired orbit information and the acquired traffic load information, identifying whether a backhaul handover determination condition is satisfied; and upon identifying that the backhaul handover determination condition is satisfied, transmitting a backhaul handover request to at least one of the base station and the FWA.

Description

Method and apparatus for performing handover in a non-terrestrial network

[0001] The present disclosure relates to a method and apparatus for performing a handover in a wireless communication system. More specifically, the present disclosure relates to a method and apparatus for performing a handover between a base station and a backhaul satellite in a non-terrestrial network (NTN).

[0002] Wireless communication networks are generally operated through terrestrial base stations, but there are limitations in establishing stable network connectivity in areas where it is difficult to build base stations due to geographical and environmental constraints. To address this, non-terrestrial network (NTN) technology utilizing satellites, HAPS (High Altitude Platforms), and UAVs (drones) is gaining attention. NTN can provide network services even in environments lacking existing mobile communication infrastructure, such as remote areas, oceans, aviation, space, and disaster zones, and can secure more extensive connectivity by forming a hybrid network linked with terrestrial networks.

[0003] Satellite-based non-terrestrial networks (NTNs) can be implemented in two main ways: either through a method where the satellite is directly connected to a terminal, or through a backhaul method where the satellite is connected to a terrestrial base station. This invention deals with a non-terrestrial network (NTN) method utilizing backhaul satellites, which features a structure where the satellite is connected to a terrestrial mobile communication base station (RAN) to transmit data to the terrestrial network. In backhaul NTNs, since satellites move rapidly, handovers between the satellite and the base station occur frequently, requiring handover technology different from that of conventional terrestrial base stations. Furthermore, because satellite networks have more limited network resources than terrestrial networks, optimal handover and load balancing technologies that consider traffic load are required.

[0004] The information described above may be provided as related art for the purpose of aiding understanding of the present disclosure. No claim or determination is made as to whether any of the foregoing may be applied as prior art in relation to the present disclosure.

[0005] A method for performing a backhaul handover in a satellite backhaul link according to the present disclosure may include: acquiring orbit information and traffic load information for each of a source satellite and a target satellite from at least one of a base station or a fixed wireless access (FWA); identifying whether a backhaul handover determination condition is satisfied based on the acquired orbit information and the acquired traffic load information; and transmitting a backhaul handover request to at least one of the base station or the FWA as it is identified that the backhaul handover determination condition is satisfied.

[0006] An electronic device according to the present disclosure may include a memory for storing instructions and at least one processor. The instructions may be executed individually or collectively by the at least one processor so that the electronic device obtains orbit information and traffic load information for a source satellite and a target satellite, respectively, from at least one of a base station or a fixed wireless access (FWA), identifies whether a backhaul handover determination condition is satisfied based on the obtained orbit information and the obtained traffic load information, and transmits a backhaul handover request to at least one of the base station or the FWA as it is identified that the backhaul handover determination condition is satisfied.

[0007] In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components.

[0008] FIG. 1 illustrates an exemplary wireless network according to the present disclosure.

[0009] FIG. 2 is a diagram illustrating an overview of a method for performing a handover between a base station and a backhaul satellite in a non-terrestrial network according to the present disclosure.

[0010] FIG. 3 is a flowchart illustrating the process of performing a handover between a base station and a backhaul satellite in a non-terrestrial network according to the present disclosure.

[0011] FIG. 4 is a flowchart illustrating the process of establishing a backhaul handover policy in one embodiment.

[0012] FIG. 5 is a flowchart illustrating the process of performing a handover between a base station and a backhaul satellite in one embodiment.

[0013] FIG. 6 is a flowchart illustrating the process of performing a backhaul handover by a first controller that establishes a backhaul handover policy and a second controller that determines whether to perform a backhaul handover in one embodiment.

[0014] FIG. 7 is a block diagram illustrating data transmitted and received between a controller, a base station, and an FWA according to one embodiment.

[0015] FIG. 8 is a block diagram illustrating data transmitted and received between a first controller, a second controller, a base station, and an FWA according to one embodiment.

[0016] FIG. 9 is an example diagram illustrating a method for determining whether to perform a backhaul handover based on RSRP or RSSI in one embodiment.

[0017] FIG. 10 is an example diagram illustrating a method for determining whether to perform a backhaul handover based on RSRP in one embodiment.

[0018] FIG. 11 is a diagram showing an example of selecting a target satellite from among a plurality of candidate target satellites and performing a backhaul handover on the selected target satellite.

[0019] FIG. 12 is a block diagram showing the configuration of a satellite according to various embodiments of the present disclosure.

[0020] FIG. 13 is a block diagram showing the configuration of a base station or FWA according to various embodiments of the present disclosure.

[0021] FIG. 14 is a block diagram showing the configuration of an electronic device according to various embodiments of the present disclosure.

[0022] Embodiments of the present disclosure are described below in detail with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. Furthermore, in order to clearly explain the present disclosure in the drawings, parts unrelated to the explanation have been omitted, and similar parts throughout the specification are denoted by similar reference numerals.

[0023] The terms used in this disclosure are described in their current, general form considering the functions mentioned herein; however, they may refer to various other terms depending on the intent of those skilled in the art, case law, or the emergence of new technologies. Accordingly, the terms used in this disclosure should not be interpreted solely by their names, but should be interpreted based on the meaning of the terms and the overall content of this disclosure.

[0024] Additionally, terms such as the first, second, third, ..., Nth may be used to describe various components, but the components should not be limited by these terms. These terms are used for the purpose of distinguishing one component from another.

[0025] Throughout the specification, when a part is described as being "connected" to another part, this includes not only cases where they are "directly connected," but also cases where they are "electrically connected" with other components interposed between them. Furthermore, when a part is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0026] Phrases such as "in one embodiment" appearing in various places in this disclosure do not necessarily refer to the same embodiment.

[0027] One embodiment of the present disclosure may be represented by functional block configurations and various processing steps. Some or all of these functional blocks may be implemented by various numbers of hardware and / or software configurations that execute specific functions. For example, the functional blocks of the present disclosure may be implemented by one or more microprocessors or by circuit configurations for a specific function. Additionally, for example, the functional blocks of the present disclosure may be implemented in various programming or scripting languages. The functional blocks may be implemented as algorithms executed on one or more processors. Furthermore, the present disclosure may employ prior art for electronic configuration, signal processing, and / or data processing. Terms such as “mechanism,” “element,” “means,” and “configuration” may be used broadly and are not limited to mechanical and physical configurations.

[0028] Furthermore, the connecting lines or connecting members between the components depicted in the drawings are merely illustrative of functional connections and / or physical or circuit connections. In the actual device, connections between components may be represented by various alternative or added functional connections, physical connections, or circuit connections.

[0029] In the present disclosure, backhaul handover refers to an operation between a ground base station and a satellite in which the base station changes the connection from the backhaul satellite currently connected to the base station to another backhaul satellite. The present disclosure may provide a method for performing backhaul handover. In a non-terrestrial network (NTN) environment, a ground base station maintains a backhaul link through a specific satellite, but due to the mobility of the satellite, a backhaul handover to a new satellite may be necessary to ensure a continuous connection.

[0030] In the present disclosure, the controller (200) can manage interoperability with satellites and ground base stations in a non-terrestrial network (NTN) environment and can establish or execute a backhaul handover policy. The controller (200) can determine the optimal backhaul handover timing of the satellite backhaul link by utilizing PLMN information, network slicing information, satellite orbit data (TLE information), etc. Additionally, it can determine whether to perform a backhaul handover by considering traffic load and channel capacity, and can approve or adjust backhaul handover requests by analyzing the network status. For example, the controller (200) may include a Non-RT RIC and a Near-RT RIC. Depending on the system configuration, the controller (200) may be separated into a first controller (201) and a second controller (202), or it may operate as a single unit. The first controller (201) performs the role of establishing a backhaul handover policy for the entire network, and the second controller (202) performs individual backhaul handover decisions and can monitor network traffic in real time. For example, the first controller (201) may be a Non-RT RIC, and the second controller (202) may be a Near-RT RIC.

[0031] In the present disclosure, an electronic device (e.g., electronic device (300)) may refer to a device including a controller (e.g., controller (200), first controller (201), second controller (202)). The electronic device (300) may be a satellite, a ground server, a base station, a gateway, an edge computing node, or a data center, and may include various other devices. The electronic device (300) includes a controller (200) and can control data transmission and reception and backhaul handover operations with the satellite and the ground base station within a non-ground (NTN) network. The electronic device (300) can determine whether to perform a backhaul handover by analyzing signal quality information (RSRP, RSRQ, RSSI), network traffic load information, and GNSS data collected from the satellite and ground network elements. Additionally, it can select a backhaul handover approval and an optimal target satellite to maintain the continuity of the satellite backhaul link when performing a backhaul handover.

[0032] In the present disclosure, an element management system (EMS) is a system for performing efficient operation and management of network resources and may include network slicing and traffic monitoring functions. In a non-terrestrial network (NTN) environment, the EMS may collect network slicing information and provide it to a controller to optimize the interoperability between a satellite network and a terrestrial network. Additionally, it may analyze the network traffic load status to adjust resource allocation for specific services or user groups, thereby supporting the establishment of backhaul handover policies in an NTN environment. The EMS manages public land mobile network (PLMN) information and slicing data according to the network operator's policy and can set the priority of specific network slices based on this. Through this, it can provide more stable network connections for emergency services or services with high Quality of Service (QoS) requirements in an NTN environment, and can adjust backhaul handover execution criteria considering traffic load. Furthermore, the EMS may perform functions such as monitoring network status in real time and automatically setting alternative paths or adjusting backhaul handover policies in the event of a failure.

[0033] The present disclosure will be described in detail below with reference to the attached drawings.

[0034] FIG. 1 illustrates an exemplary wireless network according to an embodiment of the present disclosure.

[0035] The wireless network embodiment shown in FIG. 1 is for illustrative purposes only. Other embodiments of the wireless network (100) may be used without departing from the scope of the present disclosure.

[0036] As illustrated in FIG. 1, the wireless network includes a gNB (101) (e.g., a base station (BS)), a gNB (102), and a gNB (103). The gNB (101) communicates with the gNB (102) and the gNB (103). The gNB (101) also communicates with at least one network (130), such as the Internet, a proprietary Internet Protocol (IP) network, or another data network.

[0037] The gNB (102) provides wireless broadband access to the network (130) to a first plurality of user terminals (UEs) within the coverage area (120) of the gNB (102). The first plurality of UEs includes a UE (111) that may be located in a small business; a UE (112) that may be located in an enterprise (E); a UE (113) that may be located in a WiFi hotspot (HS); a UE (114) that may be located in a first residence (R); a UE (115) that may be located in a second residence (R); and a UE (116) that may be a mobile device (M) such as a cell phone, a wireless laptop, a wireless PDA, etc. The gNB (103) provides wireless broadband access to the network (130) to a second plurality of UEs within the coverage area (125) of the gNB (103). The second plurality of UEs includes a UE (115) and a UE (116). In some embodiments, one or more gNBs (101 to 103) may communicate with each other and with UEs (111 to 116) using 5G / NR, LTE (long term evolution), LTE-A (long term evolution-advanced) (LTE-A), WiMAX, WiFi, or other wireless communication technologies.

[0038] Depending on the network type, the terms "base station" or "BS" may refer to any component (or set of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macrocell, a femtocell, a WiFi access point (AP), or other wirelessly enabled device. A base station may provide wireless access according to one or more wireless communication protocols, such as 5G / NR 3GPP NR, LTE (long term evolution), LTE-A (LTE advanced), HSPA (high speed packet access), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to a remote terminal. Additionally, depending on the network type, the terms "user terminal" or "UE" may refer to any component such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms "user terminal" and "UE" are used in this patent document to refer to a remote wireless terminal wirelessly accessing a BS, whether the UE is considered a mobile device (e.g., a mobile phone or a smartphone) or a fixed device (e.g., a desktop computer or a keyboard).

[0039] The dotted lines indicate the approximate range of the coverage areas (120 and 125), and these areas are depicted as roughly circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas (120 and 125), may have different shapes, including irregular shapes, depending on the configuration of the gNB and changes in the wireless environment associated with natural and artificial obstacles.

[0040] As discussed in more detail below, the wireless network (100) may communicate via one or more communication satellite(s) (104) that may be in orbit above the Earth. The communication satellite(s) (104) may provide network access by communicating directly with the BS (102 and 103), for example, in situations where the BS (102 and 103) are located remotely, or otherwise beyond existing fronthaul and / or backhaul connections, or in situations where facilitation for network access connections is required in addition to these connections. Various UEs (e.g., illustrated by UE (116)) may enable at least some degree of direct communication and / or localization with the communication satellite(s) (104) to receive, for example, location information or coordinates.

[0041] A non-terrestrial network (NTN) refers to a network or network segment that uses RF resources mounted on a communication satellite (or unmanned aerial vehicle system platform) (e.g., communication satellite(s) (104)). Considering the ability to provide extensive coverage and stable service, the NTN is designed to ensure service availability and continuity everywhere. For example, the NTN can support communication services in service-unavailable areas that cannot be covered by existing terrestrial networks, communication services in service-deprived areas experiencing limited communication services, communication services for devices and passengers on mobile platforms, and communication services for future railway / maritime / air communication, etc.

[0042] As described in more detail below, one or more UEs (111 to 116) include circuitry, programming, or a combination thereof for area management in the NTN. In certain embodiments, one or more gNBs (101 to 103) include circuitry, programming, or a combination thereof for area management in the NTN.

[0043] FIG. 1 illustrates an example of a wireless network, but various modifications to FIG. 1 may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. Additionally, the gNB (101) may communicate directly with any number of UEs and provide such UEs with wireless broadband access to the network (130). Similarly, each gNB (102 to 103) may communicate directly with the network (130) and provide UEs with direct wireless broadband access to the network (130). Additionally, the gNBs (101, 102 and / or 103) may provide access to other or additional external networks, for example, an external telephone network or other types of data networks.

[0044] FIG. 2 is a diagram illustrating an overview of a method for performing a backhaul handover between a base station (210) and a backhaul satellite (241, 242) in a non-ground network according to the present disclosure.

[0045] As illustrated in FIG. 2, the present disclosure describes a backhaul handover management method in a non-terrestrial network (NTN) environment using a satellite (240). In the present system, a plurality of satellites (241, 242) are connected to a base station or FWA (210) to provide a backhaul link, and the backhaul link can perform the role of extending the coverage of a mobile communication system or replacing a terrestrial network base station. In one embodiment, each satellite (241, 242) can communicate with other satellites through a gateway (220).

[0046] According to one embodiment, the electronic device (300) can establish a backhaul handover policy and determine whether to perform a backhaul handover based on the established backhaul handover policy. The electronic device (300) may include a controller (200) capable of establishing a backhaul handover policy or determining whether to perform a backhaul handover based on the established backhaul handover policy. In one embodiment, the controller (200) may include a first controller (201) that manages the backhaul handover policy and a second controller (202) that performs real-time backhaul handover decisions. The first controller (201) may establish a backhaul handover policy based on at least one of satellite orbit information, ground network traffic status, or backhaul link status. For example, the first controller (201) may comprehensively analyze the satellite orbit information, ground network traffic status, and backhaul link status, and may establish a backhaul handover policy based on the analysis results. The established backhaul handover policy may be provided to the second controller (202). The second controller (202) can check the communication status with at least one of the satellite (241, 242) and the base station or FWA (210) in real time. The second controller (202) can perform a backhaul handover decision based on a backhaul handover policy provided by the first controller (201). For example, the second controller (202) can perform a backhaul handover decision in real time based on a backhaul handover policy provided by the first controller (201). For example, the second controller (202) can determine whether to perform a backhaul handover at predetermined intervals. For example, the second controller (202) can determine whether to perform a backhaul handover as a predetermined period has elapsed since the most recent backhaul handover decision was made.

[0047] In one embodiment, while the link between the satellite (240) and the base station (210) is maintained, when the base station (210) reaches the backhaul handover time interval, the second controller (202) can determine the need for a backhaul handover and transmit a backhaul handover command to the target satellite (242). For example, the backhaul handover can be performed by selecting the target satellite (242) with a relatively low traffic load by comprehensively considering RSRP, RSSI, and RSRQ. Through this, the concentration of load on the overloaded satellite can be prevented, and the stability and quality of the non-ground network can be improved.

[0048] According to the method of the present disclosure, whether to perform a backhaul handover can be determined based on traffic load and signal quality. In addition, the method of the present disclosure enables efficient backhaul handover management in a satellite-based backhaul network by a first controller (201) and a second controller (202), thereby enabling traffic load distribution and the maintenance of optimal network quality. Through this, network stability can be increased and unnecessary backhaul handovers minimized, thereby improving the quality of service in a non-terrestrial network (NTN) environment.

[0049] FIG. 3 is a flowchart illustrating the process of performing a backhaul handover between a base station and a backhaul satellite in a non-terrestrial network according to the present disclosure.

[0050] According to one embodiment, the controller (200) may be included in the electronic device (300). For example, the electronic device (300) may be at least one of a base station or FWA (210), a satellite (240), or a server. For example, the electronic device (300) may include a carrier's server.

[0051] Referring to identification number 310, the electronic device (300) can obtain data related to the signal strength of the source satellite (241) and the target satellite (242) from at least one of the base station or FWA (210). For example, the signal strength information may include measurements related to the reference signal received power (RSRP) and the received signal strength indicator (RSSI). Through this, the relative signal strength of the source satellite (241) and the target satellite (242) can be compared at the base station or FWA (210).

[0052] Referring to identification number 320, the electronic device (300) may receive signal quality information and traffic load information measured at the base station or FWA (210) from at least one of the base station or FWA (210). For example, the signal quality information may include values ​​related to the reference signal received quality (RSRQ). The traffic load information may include data related to traffic usage, data transmission rate, or whether there is an overload condition within the backhaul link managed by the base station or FWA (210). The base station or FWA (210) may measure the status of the backhaul link in service in real time and, if the need for a backhaul handover increases, transmit data to the controller (200) indicating that the need for a backhaul handover has increased. The base station or FWA (210) may transmit satellite link measurement reports to the controller (200) at predetermined intervals and may transmit additional reports to the controller (200) depending on the network status. For example, if the channel capacity of a backhaul link in service reaches a threshold, a report regarding the condition may be transmitted to the controller (200) to prevent an overload condition. Additionally, the base station or FWA (210) may transmit a satellite link measurement report to the controller (200) to evaluate the need for a backhaul handover if the remaining link time of the backhaul link in service decreases below a threshold. Through this, the electronic device (300) can determine whether to perform a backhaul handover appropriately for the specific situation by considering not only the simple signal strength but also the network load.

[0053] Referring to identification number 330, the electronic device (300) can identify whether the backhaul handover determination condition is satisfied. For example, the electronic device (300) can identify that the backhaul handover determination condition is satisfied when RSRP falls below a certain threshold, when RSRQ decreases below a threshold and communication quality deteriorates, or when the traffic load of the currently connected satellite is excessive and backhaul handover is required. Additionally, for example, the electronic device (300) can identify that the backhaul handover determination condition is satisfied when a signal strength above a certain threshold is identified for the target satellite (242), and the target satellite (242) is identified as maintaining a traffic load state below a certain threshold.

[0054] Referring to identification number 340, the electronic device (300) can transmit a backhaul handover request to a base station or FWA (210) as the backhaul handover determination condition is satisfied. The backhaul handover request can be performed by reflecting a policy that takes into account the network state, thereby preventing unnecessary backhaul handovers and optimizing network resources.

[0055] FIG. 4 is a flowchart illustrating the process of establishing a backhaul handover policy in one embodiment.

[0056] In one embodiment, the first controller (201) can establish a backhaul handover policy based on data related to the orbit information, traffic load information, and signal strength of the source satellite (241) and the target satellite (242). The first controller (201) can establish an optimal backhaul handover policy by analyzing various information to perform efficient backhaul handover in a satellite-based backhaul network.

[0057] Referring to FIG. 4, the first controller (201) can receive data related to the orbit information, traffic load information, or signal strength of the source satellite and the target satellite. The orbit information of the source satellite and the target satellite can be used to predict backhaul handover timing based on the position and direction of movement of the satellites, and the first controller (201) can determine the backhaul handover target satellite based on the current load status of the satellite and the base station. The data related to signal strength may include one of the data related to signal measurement RSRP (reference signal received power), RSRQ (reference signal received quality), or RSSI (received signal strength indicator). The first controller (201) can evaluate the necessity of a backhaul handover through this.

[0058] According to one embodiment, the controller (200) can establish a backhaul handover policy based on PLMN information, base station frequency band (BAND), or network slicing information. Additionally, the controller (200) can predict the time that a base station can maintain a link with each satellite based on two-line element set (TLE) data including the location of the base station and satellite orbit information. Through this, the controller (200) can optimize the backhaul handover policy to evenly distribute the network load and independently manage the traffic capacity between the base station and the satellite.

[0059] In one embodiment, the first controller (201) may establish a backhaul handover policy based on received data. The first controller (201) may comprehensively analyze the received data and establish a backhaul handover policy based on the analysis results. The established backhaul handover policy may include a policy related to at least one of the following: the timing of when backhaul handover between satellites occurs, backhaul handover priority, or a backhaul handover distribution strategy considering traffic load. For example, the backhaul handover policy may be established based on policies for each carrier.

[0060] According to one embodiment, a backhaul handover policy established by a controller (200) or a first controller (201) may be stored in an electronic device (300). In this case, the controller (200) or the second controller (202) may determine whether to perform a backhaul handover based on the backhaul handover policy already stored in the electronic device (300).

[0061] FIG. 5 is a flowchart illustrating the process of performing a backhaul handover between a base station and a backhaul satellite in one embodiment.

[0062] In FIG. 5, the controller (200) may include a first controller (201) and a second controller (202). Alternatively, the controller (200) may perform both the backhaul handover policy establishment and the backhaul handover decision as a whole. The case where the first controller (201) and the second controller (202) each perform the function of establishing a backhaul handover policy and the function of determining whether to perform a backhaul handover separately will be explained in detail in FIG. 6 and will be omitted here.

[0063] Referring to identification number 501, the base station or FWA (210) may measure the current satellite link status for the source satellite (241) and then transmit a satellite link measurement report. The report may include values ​​related to RSRP, RSRQ, RSSI and data related to network load status, which can be used as basic data to determine the need for a backhaul handover.

[0064] Referring to identification number 502, the source satellite (241) can additionally obtain link measurement data for the target satellite (242). In one embodiment, the source satellite (241) can transmit and receive data to and from the target satellite (242) through a gateway (220). The source satellite (241) can transmit the satellite link measurement report received from the base station or FWA (210) and the obtained link measurement data to the controller (200).

[0065] Referring to identification number 503, the controller (200) can determine whether to perform a backhaul handover by analyzing collected satellite link measurement reports. In one embodiment, the controller (200) can determine whether to perform a backhaul handover based on at least one of data related to signal strength (e.g., RSRP, RSRQ, RSSI), traffic load occurring in an NTN environment, network slicing (PLMN, Slice ID), or satellite orbit. For example, the controller (200) can comprehensively analyze data related to signal strength (e.g., RSRP, RSRQ, RSSI), traffic load occurring in an NTN environment, network slicing (PLMN, Slice ID), or satellite orbit, and determine whether to perform a backhaul handover based on the analysis results. For example, the controller (200) can determine whether to perform a backhaul handover based on the traffic conditions of the target satellite (242). For example, if it is identified that the channel capacity of a backhaul satellite in service has reached a threshold, the controller (200) can analyze the report and determine whether to perform a backhaul handover. Additionally, if the remaining connection time of the backhaul satellite in service is below the threshold, it is highly likely that maintaining a continuous connection will be difficult, so the controller (200) can perform a backhaul handover to ensure connection stability. If the signal quality of the backhaul satellite link in service is lower compared to the link signal quality of other satellites, the controller (200) can determine whether to perform a backhaul handover based on a backhaul handover policy, taking into account signal quality and satellite connectivity.

[0066] Referring to identification number 504, if the controller (200) decides to perform a backhaul handover, it may transmit a backhaul handover request to the source satellite (241). The backhaul handover request may include information for establishing a connection with the selected target satellite (242).

[0067] Referring to identification number 505, the source satellite (241) verifies the backhaul handover request and then sends a backhaul handover request confirmation message back to the controller (200). In this process, the controller (200) can verify whether the target satellite (242) is acceptable and whether the backhaul handover conditions are met.

[0068] Referring to identification number 506, the controller (200) transmits a backhaul handover command to the source satellite (241).

[0069] Referring to identification number 507, the source satellite (241) can transmit the backhaul handover command to the base station or FWA (210) after receiving it.

[0070] Referring to identification number 508, the base station or FWA (210) can send a backhaul handover confirmation message to the target satellite (242) after confirming the received backhaul handover command.

[0071] Referring to identification number 509, the target satellite (242) can send a backhaul handover confirmation message to the controller (200) after confirming that the connection with the base station or FWA (210) has been successfully established.

[0072] Referring to identification number 510, the target satellite (242) can transmit a backhaul handover completion message to the source satellite (241), base station, and FWA (210) indicating that the backhaul handover process has been successfully completed. In one embodiment, the target satellite (242) can transmit and receive data through the source satellite (241) and the gateway (220).

[0073] Referring to identification number 511, the source satellite (241) can send a backhaul handover completion confirmation message to the controller (200). Upon receiving the backhaul handover completion confirmation message, the controller (200) can verify whether the backhaul handover was successfully completed. Upon confirming that the backhaul handover procedure was successfully completed, the controller (200) can finalize the backhaul handover procedure.

[0074] FIG. 6 is a flowchart illustrating the process of performing a backhaul handover by a first controller that establishes a backhaul handover policy and a second controller that determines whether to perform a backhaul handover in one embodiment.

[0075] Referring to FIG. 6, the controller (200) may include a first controller (201) and a second controller (202). In one embodiment, the controller (200) may operate in a hierarchical manner, separated into a first controller (201) and a second controller (202). The first controller (201) and the second controller (202) may each perform the functions of establishing a backhaul handover policy and determining whether to perform a backhaul handover. For example, the first controller (201) may be a Non-RT RIC, and the second controller (202) may be a Near-RT RIC.

[0076] In Fig. 6, parts that overlap with the explanation in Fig. 5 will be explained briefly.

[0077] Referring to identification number 601, the base station or FWA (210) can transmit a satellite link measurement report based on the connection status with the source satellite (241).

[0078] Referring to identification number 602, the source satellite (241) can transmit a satellite link measurement report to the second controller (202) that evaluates the possibility of a backhaul handover based on data collected from the base station or FWA (210). Since the description of this process corresponds to the description of identification number 502 in FIG. 5, it will be omitted here.

[0079] Referring to identification number 603, the second controller (202) can transmit satellite link measurement data to the first controller (201). For example, the second controller (202) can acquire satellite link measurement data at predetermined intervals and transmit the acquired satellite link measurement data to the first controller (201).

[0080] Referring to identification number 604, the first controller (201) can establish a backhaul handover policy by analyzing collected data. The first controller (201) can establish a backhaul handover policy by comprehensively considering satellite orbit information, network traffic load status, and signal quality. Since the description regarding the method of the first controller (201) establishing the backhaul handover policy corresponds to the description regarding the method of the controller (200) establishing the backhaul handover policy in FIGS. 3 and 4, it will be omitted here.

[0081] Referring to identification number 605, the first controller (201) can transmit an established backhaul handover policy to the second controller (202). For example, a backhaul handover policy may be established in advance by the first controller (201) and stored in the electronic device (300). In this case, the first controller (201) can transmit the previously stored backhaul handover policy to the second controller (202).

[0082] Referring to identification number 606, the second controller (202) can perform a backhaul handover decision based on collected satellite link measurement reports and a backhaul handover policy received from the first controller (201). For example, the second controller (202) can identify criteria for determining whether to perform a backhaul handover based on the backhaul handover policy received from the first controller (201). Accordingly, the second controller (202) can determine whether to perform a backhaul handover based on the identified criteria and the collected satellite link measurement reports. For example, the second controller (202) can compare the identified criteria with the collected satellite link measurement reports and, based on the comparison result, determine whether to perform a backhaul handover.

[0083] Referring to identification number 607, the second controller (202) may transmit a backhaul handover request to the source satellite (241). For example, the second controller (202) may transmit a backhaul handover request to the source satellite (241) when it decides to perform a backhaul handover. For example, the second controller (202) may not transmit a backhaul handover request to the source satellite (241) when it decides not to perform a backhaul handover. Alternatively, the second controller (202) may transmit information to the source satellite (241) that it has decided not to perform a backhaul handover when it decides not to perform a backhaul handover. Another description of the process may correspond to the description of identification number 504 in FIG. 5.

[0084] Referring to identification number 608, the source satellite (241) can review the backhaul handover request and then send a backhaul handover request confirmation message to the second controller (202). Since the description of this process corresponds to the description of identification number 505 in FIG. 5, it will be omitted here for convenience.

[0085] Referring to identification number 609, the second controller (202) can transmit a backhaul handover command to the source satellite (241). Since the description of this process corresponds to the description of identification number 506 in FIG. 5, it will be omitted here for convenience.

[0086] Referring to identification number 610, the source satellite (241) can transmit the backhaul handover command to the base station or FWA (210) after receiving it. Since the description of this process corresponds to the description of identification number 507 in FIG. 5, it will be omitted here for convenience.

[0087] Referring to identification number 611, the base station or FWA (210) can send a backhaul handover confirmation message to the source satellite (241) after confirming the backhaul handover command. Since the description of this process corresponds to the description of identification number 508 in FIG. 5, it will be omitted here for convenience.

[0088] Referring to identification number 612, the target satellite (242) can send a handover confirmation message to the second controller (202) after confirming that a connection with the base station or FWA (210) has been successfully established. Since the description of this process corresponds to the description of identification number 509 in FIG. 5, it will be omitted here for convenience.

[0089] Referring to identification number 613, the target satellite (242) can transmit a handover completion message to the source satellite (241), the base station, and the FWA (210) indicating that the handover process has been successfully completed. Since the description of this process corresponds to the description of identification number 510 in FIG. 5, it will be omitted here for convenience.

[0090] Referring to identification number 614, the source satellite (241) can send a backhaul handover completion confirmation message to the second controller (202). Upon receiving the backhaul handover completion confirmation message, the second controller (202) can verify whether the backhaul handover has been successfully completed. Upon confirming that the backhaul handover procedure has been successfully completed, the second controller (202) can finalize the backhaul handover procedure.

[0091] FIG. 7 is a block diagram illustrating data transmitted and received between a controller, a base station, an FWA, and an EMS according to one embodiment, and FIG. 8 is a block diagram illustrating data transmitted and received between a first controller, a second controller, a base station, and an FWA according to one embodiment.

[0092] FIGS. 7 and 8 are conceptual diagrams illustrating data flow in which a controller (200) transmits and receives data with a base station, FWA (210), or EMS (710) in a non-terrestrial network (NTN) environment according to the present disclosure. FIG. 7 illustrates a case where the controller (200) operates in a single layer structure, and FIG. 8 illustrates a case where the controller (200) operates in a layered manner, separated into a first controller (201) and a second controller (202).

[0093] Referring to FIG. 7, the controller (200) may be connected to a plurality of base stations (210) and FWAs (210). The controller (200) may receive a satellite link report from a base station or an FWA (210). At least one of the base station (210) or the FWA (210) may collect data related to the signal strength (RSRP), signal quality (RSRQ), or traffic load (RSSI) of the currently connected satellite and the target satellite and transmit it to the controller (200). Based on the received data, the controller (200) may determine a backhaul handover policy appropriate for the network conditions in a non-terrestrial network (NTN).

[0094] Additionally, the controller (200) may receive a slicing report from the EMS (710). The EMS (710) includes network slicing information and provides the controller (200) with the status of network resource allocation for a specific PLMN (public land mobile network) or a specific user group. Based on this information, the controller (200) can make more sophisticated backhaul handover decisions by considering the network slicing policy when performing backhaul handover in a non-terrestrial network (NTN) environment.

[0095] The controller (200) optimizes traffic within the NTN based on collected information and can transmit it to the base station (210) and FWA (210) if backhaul handover is required. This prevents overload in the non-terrestrial network (NTN) environment and maintains optimal network quality.

[0096] Referring to FIG. 8, the controller (200) may be separated into a first controller (201) and a second controller (202) and operate. In one embodiment, the first controller (201) may manage a long-term backhaul handover policy, and the second controller (202) may be responsible for performing near-real-time backhaul handover decisions.

[0097] For example, whether the controller (200) operates as a single layer structure as shown in FIG. 7 or is separated into a first controller (201) and a second controller (202) as shown in FIG. 8 can be determined according to the carrier's policy. For example, the first controller (201) can establish a backhaul handover policy and manage the backhaul handover policy for long-term network optimization. In this case, since the first controller (201) has a low need to identify and respond to network conditions in real time, it can be operated by being installed on a cloud server or a terrestrial server. However, for example, the second controller (202) can identify network conditions in real time and, accordingly, decide in real time whether to perform a backhaul handover. To do this, the second controller (202) must be able to respond to real-time traffic changes, so it can be operated on a satellite or MEC (multi-access edge computing) to minimize latency. That is, for example, the first controller (201) and the second controller (202) may be included in different electronic devices (300).

[0098] The second controller (202) can receive satellite link reports from multiple base stations (210) and multiple FWAs (210). Based on the received reports, the second controller (202) analyzes the possibility of backhaul handover in real time within the non-terrestrial network (NTN) and can perform backhaul handover based on data related to signal strength (RSRP), signal quality (RSRQ), and traffic load (RSSI).

[0099] Meanwhile, the first controller (201) can generate a long-term backhaul handover policy by analyzing the satellite link report received from the second controller (202). The first controller (201) can establish an optimal backhaul handover strategy in a non-ground network (NTN) environment by analyzing satellite orbit information, network traffic flow, and slicing data. The established backhaul handover policy can be transmitted to the second controller (202). Upon receiving the backhaul handover policy, the second controller (202) can make an optimal backhaul handover decision based on the received backhaul handover policy when performing a real-time backhaul handover.

[0100] In addition, as in FIG. 7, the second controller (202) can receive a slicing report from the EMS (710) and, based on this, can perform a backhaul handover considering network slicing in an NTN environment.

[0101] FIG. 9 is an example diagram illustrating a method for determining whether to perform a backhaul handover based on RSRP or RSSI in one embodiment.

[0102] Identification number 910 and identification number 920 are diagrams showing examples in which the amount of signal received within a specified frequency band is different from each other.

[0103] The electronic device (300) can determine the network load status more precisely by analyzing the relationship between wireless resource usage and RSSI. RSSI represents the sum of all signals received in a specific frequency band, and the RSSI value can increase as more wireless resources are used. Therefore, it can be determined that the network traffic load is greater the higher the RSSI value, and based on this, whether to perform a backhaul handover and the timing of the backhaul handover can be determined.

[0104] The example of identification number 910 has a relatively lower density of wireless resources used compared to the example of identification number 920. That is, when the load of the wireless resources is low, as in identification number 910, the electronic device (300) can determine that the RSSI value is maintained at a relatively low level and that the traffic load is low. Therefore, in an environment where the load of wireless resources is low, as in identification number 910, there is less need to perform backhaul handover, and it may be more efficient to maintain the existing backhaul link. Accordingly, the electronic device (300) may decide not to perform backhaul handover.

[0105] On the other hand, in identification number 920, the density of wireless resources used is relatively higher compared to the example of identification number 910. In this case, the electronic device (300) can determine that multiple base stations or terminals share the same frequency resources, and as a result, the RSSI value increases, resulting in a high network load. That is, as in the example of identification number 920, when the traffic throughput of the currently connected source satellite (241) increases and the resource occupancy is high, the electronic device (300) can decide to perform a backhaul handover to prevent network overload and efficiently distribute the backhaul link.

[0106] According to the backhaul handover method of the present disclosure, network load can be determined by utilizing RSSI as well as signal strength (RSRP), and a backhaul handover policy can be optimized based on this. For example, if the RSSI value of a specific backhaul link increases above a certain threshold, it can be determined that the backhaul link is in an overloaded state and a backhaul handover can be performed. In addition, if the RSSI rises above a certain level, the RSRQ value can be additionally considered to evaluate whether the signal quality is deteriorating, and if the RSRQ value drops below a certain level, a backhaul handover can be performed.

[0107] FIG. 10 is an example diagram illustrating a method for determining whether to perform a backhaul handover based on RSRP in one embodiment, and FIG. 11 is a diagram showing an example of selecting a target satellite among a plurality of candidate target satellites and performing a backhaul handover for the selected target satellite.

[0108] Referring to FIG. 10, when the signal strength (RSRP) between the base station (210) and the satellite (240) drops below a predetermined signal strength (RSRP) threshold, a backhaul handover can be performed.

[0109] Referring to FIG. 11, an example is shown in which a target satellite (242) is selected from among a plurality of candidate target satellites (242, 243, 244), and a backhaul handover is performed for the selected target satellite (242). In one embodiment, the electronic device (300) may establish a backhaul handover policy to distribute the traffic load for each satellite based on data related to RSRQ and RSSI along with the RSRP value when performing a backhaul handover. In this case, the backhaul handover may be dynamically adjusted according to the load status of the candidate target satellites (242, 243, 244).

[0110] Referring to FIG. 11, for example, the electronic device (300) can select a target satellite (242) from among a plurality of candidate target satellites (242, 243, 244). The electronic device (300) can select the first candidate target satellite (242) as the target satellite (242) when the load of the first candidate target satellite (242) is the lowest among the plurality of candidate target satellites (242, 243, 244) (e.g., Load = 30%). Accordingly, the electronic device (300) can perform a backhaul handover from the source satellite (241) to the target satellite (242). Accordingly, the load can be distributed. For example, the electronic device (300) may decide not to perform a backhaul handover for the third candidate target satellite (244) when the load of the third candidate target satellite (244) is the highest among the multiple candidate target satellites (242, 243, 244) (e.g., Load = 60%), and may select one of the other candidate target satellites (242, 243) with a relatively low load as the target satellite (242). By doing so, the electronic device (300) can prevent overloading of a specific satellite.

[0111] Through this, the present disclosure allows for the establishment of a more optimized backhaul handover policy by considering signal strength (RSRP), network traffic load (RSSI), and signal quality (RSRQ) together when performing backhaul handover in a non-terrestrial network (NTN) environment. Since the rapid mobility and extensive coverage characteristics of satellites must be considered in a non-terrestrial network (NTN) environment, it may be more effective to establish a backhaul handover policy by considering RSRQ along with RSRP and to determine whether to perform backhaul handover.

[0112] FIG. 12 is a block diagram showing the configuration of a satellite according to various embodiments of the present disclosure.

[0113] FIG. 12 illustrates the configuration of a satellite (240) according to various embodiments of the present disclosure. The configuration exemplified in FIG. 12 can be understood as the configuration of a satellite (240). Terms such as '...part', '...unit', etc. used below refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or a combination of hardware and software.

[0114] Referring to FIG. 12, the satellite (240) may include a communication unit (1210), a memory (1220), and a control unit (1230).

[0115] The communication unit (1210) performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit (1210) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (1210) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the communication unit (1210) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the communication unit (1210) upconverts the baseband signal into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the communication unit (1210) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0116] Additionally, the communication unit (1210) may include a plurality of transmission and reception paths. Furthermore, the communication unit (1210) may include an antenna unit. The communication unit (1210) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (1210) may be composed of a digital circuit and an analog circuit (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuit and the analog circuit may be implemented as a single package. Additionally, the communication unit (1201) may include a plurality of RF chains. The communication unit (1210) may perform beamforming. The communication unit (1210) may apply beamforming weights to a signal to impart directionality according to the settings of the control unit (1230) to the signal to be transmitted or received. According to one embodiment, the communication unit (1210) may include a radio frequency (RF) block (or RF unit). The RF block may include a first RF circuitry associated with the antenna and a second RF circuitry associated with baseband processing. The first RF circuitry may be referred to as RF-A (antenna). The second RF circuitry may be referred to as RF-B (baseband).

[0117] The communication unit (1210) transmits and receives signals as described above. Accordingly, all or part of the communication unit (1210) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the communication unit (1210).

[0118] The communication unit (1210) can convert a bit sequence transmitted from the base station (210) to another node, for example, another connection node, another base station, an upper node, a core network, etc., into a physical signal, and can convert a physical signal received from another node into a bit sequence.

[0119] The memory (1220) stores data such as basic programs, applications, and configuration information for the operation of the satellite (240). The memory (1220) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. Additionally, the memory (1220) provides the stored data upon the request of the control unit (1230).

[0120] The control unit (1230) controls the overall operations of the satellite (240). For example, the control unit (1230) transmits and receives signals through the communication unit (1210). Additionally, the control unit (1230) writes and reads data in the memory (1220). Furthermore, the control unit (1205) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (1230) may include at least one processor. The control unit (1230) may include at least one processor or microprocessor, or may be part of a processor. Additionally, part of the communication unit (1210) and the control unit (1230) may be referred to as CP. The control unit (1230) may include various modules for performing communication. According to various embodiments, the control unit (1230) may control the terminal to perform operations according to various embodiments.

[0121] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present invention and to aid in understanding the invention, and are not intended to limit the scope of the present invention.

[0122] FIG. 13 is a block diagram showing the configuration of a base station or FWA according to various embodiments of the present disclosure.

[0123] FIG. 13 illustrates the configuration of a base station (210) according to various embodiments of the present disclosure. The configuration exemplified in FIG. 13 can be understood as the configuration of a base station (210) as well as an FWA. Terms such as '... unit', '... unit' used below refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or a combination of hardware and software.

[0124] Referring to FIG. 13, the base station (210) may include a communication unit (1310), a backhaul communication unit (1320), a memory (1330), and a control unit (1340).

[0125] The communication unit (1310) performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit (1310) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (1310) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the communication unit (1310) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the communication unit (1310) upconverts the baseband signal into an RF (radio frequency) band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal.

[0126] To this end, the communication unit (1310) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Additionally, the communication unit (1310) may include a plurality of transmission and reception paths. Furthermore, the communication unit (1310) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (1310) may be composed of a digital unit and an analog unit, and the analog unit may be composed of a plurality of sub-units depending on operating power, operating frequency, etc.

[0127] The communication unit (1310) can transmit and receive signals. To this end, the communication unit (1310) may include at least one transceiver. For example, the communication unit (1310) can transmit a synchronization signal, a reference signal, system information, a message, control information, or data. Additionally, the communication unit (1310) can perform beamforming.

[0128] The communication unit (1310) transmits and receives signals as described above. Accordingly, all or part of the communication unit (1310) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the communication unit (1310).

[0129] The backhaul communication unit (1320) provides a wired / wireless interface for communicating with other nodes within the network. That is, the backhaul communication unit (1320) can convert a bit sequence transmitted from the base station (210) to another node, e.g., another connection node, another base station, an upper node, a core network, etc., into a physical signal, and can convert a physical signal received from another node into a bit sequence.

[0130] The memory (1330) stores data such as basic programs, application programs, and configuration information for the operation of the base station (210). The memory (1330) may include memory. The memory (1330) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. The memory (1330) provides stored data upon request from the control unit (1340). According to one embodiment, the memory (1305) may store training data for backhaul handover.

[0131] The control unit (1340) controls the overall operations of the base station (210). For example, the control unit (1340) transmits and receives signals through the communication unit (1310) or through the backhaul communication unit (1320). Additionally, the control unit (1340) writes and reads data to and from the memory (1330). Furthermore, the control unit (1340) can perform the functions of a protocol stack required by the communication standard. To this end, the control unit (1340) may include at least one processor.

[0132] The configuration of the base station (210) shown in FIG. 13 is merely one example of a base station, and the examples of base stations for performing various embodiments of the present disclosure are not limited to the configuration shown in FIG. 13. That is, depending on various embodiments, some configurations may be added, deleted, or changed.

[0133] Although the base station in FIG. 13 is described as a single entity, the present disclosure is not limited thereto. A base station according to various embodiments of the present disclosure may be implemented to form an access network having a distributed deployment as well as an integrated deployment. According to one embodiment, the base station may be distinguished into a central unit (CU) and a digital unit (DU), wherein the CU is implemented to perform upper layer functions (e.g., packet data convergence protocol, RRC) and the DU is implemented to perform lower layer functions (e.g., medium access control (MAC), physical (PHY)). The DU of the base station may form beam coverage on a wireless channel.

[0134] FIG. 14 is a block diagram showing the configuration of an electronic device (300) according to various embodiments of the present disclosure.

[0135] FIG. 14 illustrates the configuration of an electronic device (300) according to various embodiments of the present disclosure. Terms such as '...part', '...unit', etc. used below refer to a unit that processes at least one function or operation, and this may be implemented as hardware or software, or a combination of hardware and software.

[0136] Referring to FIG. 14, the electronic device (300) may include a communication unit (1410), a memory (1420), and a control unit (1430).

[0137] The communication unit (1410) performs functions for transmitting and receiving signals through wired or wireless channels. To this end, the communication unit (1410) may include at least one transceiver. For example, the communication unit (1410) may transmit messages, control information, or data.

[0138] The communication unit (1410) transmits and receives signals as described above. Accordingly, all or part of the communication unit (1410) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the communication unit (1410).

[0139] The memory (1420) stores data such as basic programs, application programs, and configuration information for the operation of the base station (210). The memory (1420) may include memory. The memory (1420) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. The memory (1420) provides stored data upon request from the control unit (1430). According to one embodiment, the memory (1305) may store training data for backhaul handover.

[0140] The control unit (1430) controls the overall operations of the base station (210). For example, the control unit (1430) transmits and receives signals through the communication unit (1310). In addition, the control unit (1430) writes and reads data to and from the memory (1420). Furthermore, the control unit (1430) can perform the functions of a protocol stack required by the communication standard. To this end, the control unit (1430) may include at least one processor.

[0141] According to one embodiment, the control unit (1430) may correspond to one of the controller (200), the first controller (201), or the second controller (202) of the present disclosure. According to one embodiment, the control unit (1430) may perform a judgment operation related to a backhaul handover procedure.

[0142] A method for performing a backhaul handover in a satellite backhaul link according to the present disclosure may include: acquiring orbit information and traffic load information for each of a source satellite and a target satellite from at least one of a base station or a fixed wireless access (FWA); identifying whether a backhaul handover determination condition is satisfied based on the acquired orbit information and the acquired traffic load information; and transmitting a backhaul handover request to at least one of the base station or the FWA as it is identified that the backhaul handover determination condition is satisfied.

[0143] A method for performing a backhaul handover in a satellite backhaul link may further include receiving data related to signal quality for each of the source satellite and the target satellite from at least one of the base station or the FWA.

[0144] The operation of identifying whether the above backhaul handover determination condition is satisfied may include the operation of identifying whether the above backhaul handover determination condition is satisfied based on data related to the received signal quality.

[0145] The data related to the signal quality may include data related to at least one of RSRP, RSRQ, or RSSI for each of the source satellite and the target satellite.

[0146] A method for performing a backhaul handover in a satellite backhaul link may further include an operation of establishing a backhaul handover policy to identify whether the backhaul handover determination condition is satisfied based on the acquired orbit information and the traffic load information.

[0147] The operation of establishing the backhaul handover policy may include the operation of establishing the backhaul handover policy by considering PLMN information and network slicing information.

[0148] The operation of establishing the backhaul handover policy may include establishing the backhaul handover policy based on the channel capacity of each of the source satellite and the target satellite.

[0149] The operation of establishing the above backhaul handover policy may include the operation of establishing a backhaul handover policy based on inter-country boundaries and PLMN information.

[0150] The operation of establishing the backhaul handover policy may include establishing the backhaul handover policy based on the GNSS data of the source satellite and the GNSS data of the target satellite.

[0151] The operation of establishing the above backhaul handover policy may include an operation of optimizing the backhaul handover occurrence cycle to minimize the backhaul handover frequency between the source satellite and the target satellite.

[0152] The operation of establishing the handover policy may include: an operation of predicting a backhaul handover time based on the orbit information of the source satellite and the orbit information of the target satellite; and an operation of establishing the backhaul handover policy based on the prediction result.

[0153] The operation of identifying whether the above backhaul handover determination condition is satisfied may include the operation of determining the necessity of a backhaul handover by dynamically adjusting the weights of the RSRP and RSRQ provided by the source satellite and the target satellite.

[0154] For each of the source satellite and the target satellite, the operation of acquiring orbit information and traffic load information may include the operation of acquiring orbit information and traffic load information for each of the plurality of candidate target satellites.

[0155] The operation of identifying whether the backhaul handover determination condition is satisfied may include the operation of identifying the target satellite among the plurality of candidate target satellites that satisfies the backhaul handover determination condition, based on the orbit information and the traffic load information obtained for each of the plurality of candidate target satellites.

[0156] An electronic device according to the present disclosure may include a memory for storing instructions and at least one processor. The instructions may be executed individually or collectively by the at least one processor so that the electronic device obtains orbit information and traffic load information for a source satellite and a target satellite, respectively, from at least one of a base station or a fixed wireless access (FWA), identifies whether a backhaul handover determination condition is satisfied based on the obtained orbit information and the obtained traffic load information, and transmits a backhaul handover request to at least one of the base station or the FWA as it is identified that the backhaul handover determination condition is satisfied.

[0157] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to receive data related to signal quality for each of the source satellite and the target satellite from at least one of the base station or the FWA, and to identify whether the backhaul handover decision condition is satisfied based on the received data related to signal quality.

[0158] The data related to the signal quality may include data related to at least one of RSRP, RSRQ, or RSSI for each of the source satellite and the target satellite.

[0159] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to establish a backhaul handover policy so as to identify whether the backhaul handover determination condition is satisfied based on the acquired orbit information and the traffic load information.

[0160] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to establish a backhaul handover policy based on the channel capacity of each of the source satellite and the target satellite.

[0161] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to establish a backhaul handover policy based on cross-country boundaries and PLMN information.

[0162] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to optimize the backhaul handover occurrence cycle so as to minimize the backhaul handover frequency between the source satellite and the target satellite.

[0163] The above instructions may be executed individually or collectively by the at least one processor to enable the electronic device to acquire orbit information and traffic load information for each of the plurality of candidate target satellites, and to identify the target satellite among the plurality of candidate target satellites for which a backhaul handover determination condition is satisfied based on the orbit information and traffic load information acquired for each of the plurality of candidate target satellites.

Claims

1. A method for performing a backhaul handover in a satellite backhaul link, An operation of acquiring orbit information and traffic load information for each of a source satellite and a target satellite from at least one of a base station or a fixed wireless access (FWA); An operation to identify whether backhaul handover determination conditions are satisfied based on the above-mentioned acquired orbit information and the above-mentioned acquired traffic load information; and A method comprising the operation of transmitting a backhaul handover request to at least one of the base station or the FWA as it is identified that the above backhaul handover determination condition is satisfied.

2. In Claim 1, The operation further includes receiving data related to signal quality for each of the source satellite and the target satellite from at least one of the base station or the FWA. The operation of identifying whether the above backhaul handover determination condition is satisfied is, A method comprising an operation to identify whether the backhaul handover determination condition is satisfied based on data related to the received signal quality.

3. In Claim 2, A method wherein the data related to the signal quality includes data related to at least one of RSRP, RSRQ, or RSSI for each of the source satellite and the target satellite.

4. In Claim 1, A method further comprising the operation of establishing a backhaul handover policy to identify whether the backhaul handover determination condition is satisfied based on the above-mentioned track information and the above-mentioned traffic load information.

5. In Claim 4, The operation of establishing the above backhaul handover policy is, A method of establishing the above backhaul handover policy by considering PLMN information and network slicing information.

6. In Claim 4, The operation of establishing the above backhaul handover policy is, A method of establishing a backhaul handover policy by considering the channel capacity of each of the source satellite and the target satellite.

7. In Claim 4, The operation of establishing the above backhaul handover policy is, A method, which is an action of establishing a backhaul handover policy by considering inter-country boundaries and PLMN information.

8. In Claim 4, The operation of establishing the above backhaul handover policy is, A method of establishing a backhaul handover policy based on GNSS data of the source satellite and GNSS data of the target satellite.

9. In Claim 4, The operation of establishing the above backhaul handover policy is, A method comprising the operation of establishing a backhaul handover policy to minimize the frequency of backhaul handover between the source satellite and the target satellite.

10. In Claim 4, The operation of establishing the above handover policy is, An operation to predict the time of backhaul handover based on the orbit information of the source satellite and the orbit information of the target satellite; and A method comprising the operation of establishing the backhaul handover policy based on the above prediction result.

11. In Claim 1, The operation of identifying whether the above backhaul handover determination condition is satisfied is, A method comprising the operation of identifying the need for a backhaul handover by dynamically adjusting the weights of RSRP and RSRQ provided by the source satellite and the target satellite.

12. In Claim 1, For each of the source satellite and the target satellite, the operation of acquiring orbit information and traffic load information includes the operation of acquiring orbit information and traffic load information for each of the plurality of candidate target satellites. A method for identifying whether the backhaul handover determination condition is satisfied, comprising identifying the target satellite among the plurality of candidate target satellites that satisfies the backhaul handover determination condition based on the orbit information and the traffic load information obtained for each of the plurality of candidate target satellites.

13. In electronic devices, Memory for storing instructions; and It includes at least one processor, The above instructions are executed individually or collectively by the at least one processor, and the electronic device: Orbit information and traffic load information are obtained for each of the source satellite and target satellite from at least one of a base station or a fixed wireless access (FWA), and Based on the above-mentioned acquired orbit information and the above-mentioned acquired traffic load information, identify whether the backhaul handover determination conditions are satisfied, and An electronic device that transmits a backhaul handover request to at least one of the base station or the FWA as it is identified that the above backhaul handover determination condition is satisfied.

14. In Claim 13, The above instructions are executed individually or collectively by the at least one processor, and the electronic device: Receiving data related to signal quality for each of the source satellite and the target satellite from at least one of the base station or the FWA, and An electronic device that identifies whether the backhaul handover determination condition is satisfied based on data related to the received signal quality.

15. In Claim 14, An electronic device wherein the data related to the signal quality includes data related to at least one of RSRP, RSRQ, or RSSI for each of the source satellite and the target satellite.

Images