Load balancing method and apparatus, related device and storage medium

Abstract

Provided in the embodiments of the present application are a load balancing method and apparatus, a related device and a storage medium. The method comprises: receiving a registration request message initiated by a first terminal, wherein the registration request message carries a coverage layer identifier of a first coverage layer in which the first terminal camps; on the basis of the number of terminals camping in the first coverage layer, determining for the first terminal a target coverage layer allowable for registration, wherein when the number of terminals camping in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; and when the number of terminals camping in the first coverage layer reaches the load sharing threshold, instructing the first terminal to camp in the target coverage layer different from the first coverage layer, and re-initiating the registration request message; and allowing the first terminal to register in the target coverage layer. Thus, a large number of terminals camping in a certain coverage layer in a concentrated manner is avoided, and load balancing between coverage layers is realized.

Description

Load balancing method, device, related equipment and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on March 21, 2024, with application number 202410330416.3 and application name “Load balancing method, device, related equipment and storage medium”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of satellite communication technology, and in particular to a load balancing method, apparatus, related equipment and storage medium. Background Art

[0003] NTN (Non Terrestrial Network) is a terminal-satellite direct communication technology based on new air interface technology. It can use the 5G NR (New Radio) framework to enable smart terminals to directly connect to satellites. Satellites are used to carry base stations. The base stations in the NTN network are called NTN base stations.

[0004] Traditional low-orbit satellite constellations, such as the Iridium system, primarily utilize single-layer coverage due to their small number of satellites. However, broadband, high-throughput satellite constellations comprised of tens of thousands of satellites inevitably require multiple-layer coverage. Multiple-layer coverage refers to the presence of multiple NTN base stations, all providing network coverage to ground terminals. In these scenarios, uneven service loads can occur.

[0005] Taking multiple coverage at different orbital altitudes as an example, if the constellation at orbital altitude 1 operates at the F1 frequency and the constellation at orbital altitude 2 operates at the F2 frequency, double coverage is formed on the ground. For the same type of terminal, the frequency search order after power-on is the same, for example, consistent with the cell search method in the ground network, which may cause all terminals to first search for the NTN base station at orbital altitude 1 and reside there after power-on. In this case, all terminals will initiate services under the NTN base station at orbital altitude 1, resulting in a high service load on the NTN base station at orbital altitude 1 and no service on the NTN base station at orbital altitude 2, resulting in uneven service coverage between different orbital altitude layers.

[0006] Summary of the Invention

[0007] The purpose of the embodiments of the present invention is to provide a load balancing method, apparatus, related equipment and storage medium to achieve load balancing between overlay layers.

[0008] The specific technical solutions are as follows:

[0009] In a first aspect of the present application, a load balancing method is provided, the method comprising:

[0010] receiving a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides;

[0011] Determining a target coverage layer for the first terminal to be allowed to register based on the number of terminals residing in the first coverage layer; wherein, when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message;

[0012] The first terminal is allowed to register in the target coverage layer.

[0013] Optionally, the coverage layer is divided according to the track height and / or the ascending and descending track status of the NTN base station.

[0014] Optionally, one or more NTN base stations at orbital heights are grouped into the same coverage layer.

[0015] Optionally, NTN base stations at different orbital altitudes are divided into different coverage layers, and orbit-raising NTN base stations and orbit-dropping NTN base stations at the same orbital altitude are divided into different coverage layers.

[0016] Optionally, the load sharing threshold includes a first threshold for the total number of resident terminals and / or a second threshold for the number of resident terminals in a connected state;

[0017] The determining, based on the number of resident terminals in the first coverage layer, a target coverage layer in which registration is allowed for the first terminal includes:

[0018] Determining whether the total number of resident terminals in the first coverage layer reaches the first threshold; and / or determining whether the number of resident terminals in the first coverage layer in a connected state reaches the second threshold;

[0019] If the total number of terminals resident in the first coverage layer does not reach the first threshold, and / or the number of terminals resident in the connected state in the first coverage layer does not reach the second threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0020] Optionally, the load sharing threshold includes a third threshold for the total number of resident terminals in a single coverage area and / or a fourth threshold for the number of resident connected terminals in a single coverage area;

[0021] The determining, based on the number of resident terminals in the first coverage layer, a target coverage layer in which registration is allowed for the first terminal includes:

[0022] Determining a first coverage area where the first terminal is located according to the terminal location information carried in the registration request message;

[0023] Determining whether the total number of terminals in the first coverage area and residing in the first coverage layer reaches the third threshold; and / or determining whether the number of terminals in the first coverage area and residing in the first coverage layer and in a connected state reaches the fourth threshold;

[0024] If the total number of terminals in the first coverage area and residing in the first coverage layer does not reach the third threshold; and / or the number of terminals in the first coverage area and residing in the first coverage layer and in a connected state does not reach the fourth threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0025] Optionally, the step of instructing the first terminal to reside in the target coverage layer and re-initiating a registration request message includes:

[0026] Sending a registration rejection message carrying the identification information of the target coverage layer to the first terminal; the registration rejection message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message carrying the identification information of the target coverage layer;

[0027] or,

[0028] A registration acceptance message carrying the identification information of the target coverage layer is sent to the first terminal; the registration acceptance message is used to inform the first terminal that the initial registration is completed, and to instruct the first terminal to stay in the target coverage layer after entering the idle state, and to re-initiate a registration request message carrying the identification information of the target coverage layer.

[0029] Optionally, the method further includes:

[0030] When the total number of terminals residing in each coverage layer is lower than the first ratio of the resident number threshold of a single coverage layer, a converged coverage layer is determined, and the second terminals residing in each coverage layer are instructed to reside in the converged coverage layer and re-initiate a registration request message.

[0031] Optionally, the step of instructing the second terminal residing in each of the coverage layers to reside in the converged coverage layer and re-initiating a registration request message includes:

[0032] Upon receiving the tracking area update TAU registration request initiated by the second terminal, sending a TAU reject message carrying the identification information of the converged coverage layer to the second terminal; the TAU reject message is used to instruct the second terminal to reside in the converged coverage layer and re-initiate a TAU registration request carrying the identification information of the converged coverage layer;

[0033] or,

[0034] When a TAU request initiated by the second terminal is received, a TAU acceptance message carrying the identification information of the converged coverage layer is sent to the second terminal; the TAU acceptance message is used to inform the second terminal that the TAU registration is completed, and to instruct the second terminal to stay in the converged coverage layer after entering the idle state, and re-initiate a TAU request carrying the identification information of the converged coverage layer.

[0035] Optionally, the method further includes:

[0036] When all the second terminals reside in the converged coverage layer, the NTN base stations in other coverage layers except the converged coverage layer are instructed to enter a dormant state.

[0037] Optionally, the method further includes:

[0038] Determine a candidate NTN base station according to the first position of the terminal to be paged; the candidate NTN base station includes an NTN base station covering the first position and belonging to different coverage layers;

[0039] Determine, according to the coverage layer where the terminal to be paged currently resides, a target NTN base station belonging to the coverage layer from among the candidate NTN base stations;

[0040] A paging indication message for the terminal to be paged is sent to the target NTN base station, so that the target NTN base station initiates paging for the terminal to be paged.

[0041] In a second aspect of the present application, the present application further provides a load balancing method, applied to a first terminal, the method comprising:

[0042] receiving a system broadcast message of an NTN base station, where the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs;

[0043] Applying to reside in the first coverage layer according to the system broadcast message;

[0044] After residing in the first coverage layer, initiating a registration request message to a core network, wherein the registration request message carries a coverage layer identifier of the first coverage layer;

[0045] Receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a target coverage layer different from the first coverage layer, and re-initiate a registration request message.

[0046] A third aspect of the present application provides a load balancing device, comprising:

[0047] A receiving module, configured to receive a registration request message initiated by a first terminal, wherein the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides;

[0048] a determination module, configured to determine a target coverage layer for the first terminal based on the number of resident terminals in the first coverage layer; wherein, when the number of resident terminals in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of resident terminals in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message;

[0049] A registration module is configured to allow the first terminal to register in the target coverage layer.

[0050] A fourth aspect of the present application provides a load balancing device, applied to a first terminal, the device comprising:

[0051] A first receiving module is configured to receive a system broadcast message of an NTN base station, wherein the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs;

[0052] An application module, configured to apply for residing in the first coverage layer according to the system broadcast message;

[0053] a registration module, configured to initiate a registration request message to a core network after residing in the first coverage layer, wherein the registration request message carries a coverage layer identifier of the first coverage layer;

[0054] The second receiving module is used to receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a target coverage layer different from the first coverage layer and re-initiates a registration request message.

[0055] A fifth aspect of the present application provides a server, comprising a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0056] Memory for storing computer programs;

[0057] The processor is configured to implement any of the above load balancing methods when executing a program stored in the memory.

[0058] In a sixth aspect of the present application, a terminal is provided, comprising a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0059] Memory for storing computer programs;

[0060] The processor is configured to implement any of the above load balancing methods when executing a program stored in the memory.

[0061] In a seventh aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, any of the above-mentioned load balancing methods is implemented.

[0062] In an eighth aspect of the present application, a computer program product comprising instructions is also provided, which, when executed on a computer, enables the computer to execute any of the above-mentioned load balancing methods.

[0063] Beneficial effects of the embodiments of the present application:

[0064] The load balancing method, apparatus, related equipment and storage medium provided by the embodiments of the present application include: receiving a registration request message initiated by a first terminal, the registration request message carrying a coverage layer identifier of a first coverage layer where the first terminal resides; determining a target coverage layer for the first terminal to be allowed to register based on the number of terminals residing in the first coverage layer; wherein, when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, indicating that the first terminal resides in a target coverage layer different from the first coverage layer, and re-initiating a registration request message; and allowing the first terminal to register in the target coverage layer.

[0065] It can be seen that the NTN base stations are divided into different coverage layers, and a single coverage layer includes NTN base stations that implement single-layer network coverage for ground terminals. The registration request message sent by the first terminal to the core network carries the identifier of the first coverage layer where the terminal resides. The core network can count the number of terminals residing in each coverage layer through the registration request message. The core network is also pre-configured with a load sharing threshold. When the number of terminals residing in the first coverage layer reaches the pre-configured load sharing threshold, the first terminal is not allowed to continue to reside in the first coverage layer, and a target coverage layer suitable for the first terminal to reside is determined. This avoids a large number of terminals concentrating on a certain coverage layer and achieves load balancing between coverage layers. It also avoids the service users of a certain coverage layer exceeding the capacity requirements of the coverage layer, resulting in user access failure or reduced data transmission throughput.

[0066] Of course, it is not necessary to achieve all of the advantages described above simultaneously in order to implement any product or method of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0067] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0068] FIG1 is a flow chart of a load balancing method provided in an embodiment of the present application;

[0069] FIG2 is a schematic diagram of multiple coverage of an NTN network provided in an embodiment of the present application;

[0070] FIG3 is another schematic diagram of multiple coverage of an NTN network provided in an embodiment of the present application;

[0071] FIG4 is a schematic diagram of a process for configuring a broadcast coverage layer identifier for an NTN base station according to an embodiment of the present application;

[0072] FIG5 is a signaling interaction diagram of an operation and maintenance platform configuring data to a core network according to an embodiment of the present application;

[0073] FIG6 is another flow chart of a load balancing method according to an embodiment of the present application;

[0074] FIG7 is a signaling interaction diagram of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application;

[0075] FIG8 is a flow chart of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application;

[0076] FIG9 is another signaling interaction diagram of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application;

[0077] FIG10 is a signaling interaction diagram of a load aggregation process provided in an embodiment of the present application;

[0078] FIG11 is a signaling interaction diagram of a load aggregation operation provided in an embodiment of the present application;

[0079] FIG12 is another signaling interaction diagram of a load aggregation operation provided in an embodiment of the present application;

[0080] FIG13 is a flow chart of a paging method for an NTN multiple coverage scenario provided by an embodiment of the present application;

[0081] FIG14 is a flow chart of a load balancing method applied to a terminal according to an embodiment of the present application;

[0082] FIG15 is a schematic structural diagram of a load balancing device applied to a core network according to an embodiment of the present application;

[0083] FIG16 is a schematic structural diagram of a load balancing device applied to a terminal according to an embodiment of the present application;

[0084] FIG17 is a schematic diagram of the structure of a server provided in an embodiment of the present application;

[0085] FIG18 is a schematic structural diagram of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0086] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field based on this application are within the scope of protection of the present invention.

[0087] In order to ensure global coverage of broadband communication networks, as well as coverage reliability and network resilience, broadband communication satellite constellations generally consist of multi-layer hybrid constellations composed of sub-constellations with different orbital altitudes and inclinations, thereby forming multiple coverage on the ground.

[0088] In the multiple coverage scenario of the NTN network, after the terminals are turned on, a large number of terminals may reside in the NTN base stations in the same coverage layer, resulting in an unbalanced service load between different coverage layers.

[0089] Moreover, this problem cannot be solved by configuring the neighbor relationship between different coverage layers.

[0090] Specifically, for terrestrial network deployment, namely TN (Terrestrial Network), overlapping coverage will be performed in some hot spots. In the overlapping coverage area, the base station will evaluate the load of the cell based on the PBR (Physical Resource Block) utilization rate or the number of connected users in the cell, and obtain the load of the overlapping neighboring cells through the Xn interface (i.e., the interface between base stations). The connection state is switched according to the load relationship between the overlapping cells to achieve load balancing.

[0091] However, for the NTN network, satellites at different orbital altitudes have different orbital altitudes and different satellite movement speeds. As a result, there is relative motion between satellites at different orbital altitudes, and their mutual positional relationships are not fixed. For satellites at the same orbital altitude, there is even faster relative motion, and the relative positions change even more rapidly. Therefore, it is difficult to configure Xn interface inter-satellite links and neighboring cell relationships between NTN base stations in different coverage layers.

[0092] It can be seen that due to the relative motion problem between NTN base stations in different coverage layers, it is difficult to configure the Xn interface and neighboring cell relationship. Therefore, the load balancing solution between different coverage layers of ground base stations cannot be used. A new multi-coverage load balancing processing method needs to be proposed.

[0093] The present application provides a load balancing method for multiple coverage of a non-terrestrial network (NTN). The method can be applied to a core network. As shown in FIG1 , the method includes the following steps:

[0094] S101: Receive a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides.

[0095] In an embodiment of the present application, NTN base stations are divided into multiple coverage layers based on specific rules. A single coverage layer includes NTN base stations that implement single network coverage for ground terminals, that is, each coverage layer can implement single network coverage for ground terminals.

[0096] In one embodiment of the present application, the coverage layers are divided according to the track height and / or the elevation / elevation state of the NTN base station.

[0097] When only the track height is considered, NTN base stations at one or more track heights can be classified into the same coverage layer.

[0098] When considering both the orbit height and the orbit ascending and descending status, NTN base stations at different orbit heights can be divided into different coverage layers, and the orbit ascending NTN base stations and orbit descending NTN base stations at the same orbit height are divided into different coverage layers.

[0099] Specifically, as shown in Figure 2, Figure 2 is a schematic diagram of multiple coverage of the NTN network provided by an embodiment of the present application. In Figure 2, NTN base station 201 at a first orbital altitude and NTN base station 202 at a second orbital altitude are both connected to the ground core network 203. These two NTN base stations at different orbital altitudes form multiple coverage of the ground. Figure 2 also shows terminal 204, which is shown in Figure 2 as being under dual coverage of NTN base station 201 and NTN base station 202.

[0100] For sub-constellations at the same orbital altitude, the presence of both ascending and descending satellites will also provide dual coverage of the ground, as shown in Figure 3, which is another schematic diagram of multiple coverage of the NTN network provided by an embodiment of the present application. Figure 3 shows four NTN base stations at the same orbital altitude, including two ascending NTN base stations 301 and two descending NTN base stations 302, all connected to the core network 303. Figure 3 also shows a terminal 304, which is shown in Figure 3 as being under dual coverage of the ascending NTN base station 301 and the descending NTN base station 302.

[0101] As can be seen, the orbit-raising NTN base station 301 at this orbital altitude forms a single coverage layer on the ground, and the orbit-dropping NTN base station 302 at this orbital altitude also forms a single coverage layer on the ground. Therefore, it is necessary to divide the orbit-raising NTN base stations and the orbit-dropping NTN base stations at the same orbital altitude into different coverage layers.

[0102] As an example, the coverage layers of the NTN base stations are identified. For example, the ascending NTN base station at the first orbital height covers the first layer, which is recorded as coverage layer 1; the descending NTN base station at the first orbital height covers the second layer, which is recorded as coverage layer 2; the ascending NTN base station at the second orbital height covers the third layer, which is recorded as coverage layer 3; the descending NTN base station at the second orbital height covers the fourth layer, which is recorded as coverage layer 4, and so on.

[0103] In the embodiment of the present application, the coverage layer identification can be configured for the NTN base station by the operation and maintenance platform, and the operation and maintenance platform can be understood as a platform for monitoring and managing the operating status of the NTN base station. The operation and maintenance platform is pre-configured with rules for determining the coverage layer to which the NTN base station belongs, such as those mentioned above: the NTN base station at the first orbital altitude is recorded as coverage layer 1; the NTN base station at the first orbital altitude is recorded as coverage layer 2; the NTN base station at the second orbital altitude is recorded as coverage layer 3; the NTN base station at the second orbital altitude is recorded as coverage layer 4, etc. Furthermore, based on the ephemeris information of the NTN base station, it can be determined whether the NTN base station is in the orbit raising state or the orbit lowering state, and combined with the orbital altitude of the NTN base station, the coverage layer to which the NTN base station belongs can be determined.

[0104] After the NTN base station is powered on, the operation and maintenance platform configures the coverage layer identifier of the NTN base station so that the NTN base station can determine its own coverage layer identifier. When the NTN base station flies over the perigee or apogee, due to the change in the status of the NTN base station's ascending and descending orbit, the operation and maintenance platform updates the NTN base station's coverage layer identifier and notifies the NTN base station.

[0105] Accordingly, NTN base stations can carry their own coverage layer identifiers in system broadcast messages, allowing terminals to determine their current coverage layer. As an example, a field is added to the System Information Block 1 (SIB1) of the system broadcast message to broadcast the layer identifier. If the coverage layer identifier changes, the coverage layer identifier in the system broadcast message is modified according to the procedures specified in the 3GPP protocol.

[0106] For ease of understanding, the following description is provided in conjunction with FIG4 , which is a schematic diagram of a flow chart of configuring a broadcast coverage layer identifier for an NTN base station according to an embodiment of the present application, including the following steps:

[0107] S401: The NTN base station is powered on and started.

[0108] S402: The operation and maintenance platform configures a coverage layer identifier for the NTN base station.

[0109] S403: The NTN base station broadcasts the coverage layer identifier.

[0110] As an example, a field is added to SIB1 to carry the overlay layer identifier and broadcast it periodically.

[0111] S404: The NTN base station flies over the perigee or apogee.

[0112] S405: The operation and maintenance platform updates the coverage layer identifier of the NTN base station.

[0113] When the NTN base station flies over the perigee or apogee, due to the change in the state of the NTN base station's lift rail, the operation and maintenance platform updates the coverage layer identification of the NTN base station and informs the NTN base station.

[0114] S406: The NTN base station broadcasts the new coverage layer identifier.

[0115] In addition, in addition to broadcasting the identity of the current coverage layer, the NTN base station can also broadcast information such as the frequency of other coverage layers outside the current coverage layer, which can accelerate the terminal's search for other coverage layers and shorten the time to select a coverage layer.

[0116] The operation and maintenance platform can configure the coverage layer information of the NTN network to the core network, including the base station list information contained in each coverage layer and the ephemeris information of each NTN base station.

[0117] After powering on, a terminal first performs synchronization on a supported frequency band. This synchronization process determines the time slot and synchronization frame, which are then used to access information such as the SIB. After synchronization is complete, the terminal reads the master information block (MIB) and SIB. By examining the information in SIB1, the terminal determines the current coverage layer and whether it can reside in that coverage layer. If the residency conditions are met, the terminal resides in that coverage layer. As is easy to understand, since coverage layers are composed of multiple NTN base stations, the fact that a terminal resides in a particular coverage layer can be understood as the terminal residing in a specific NTN base station within that coverage layer.

[0118] After the terminal resides in a certain coverage layer, it needs to initiate a registration request to the core network. In this embodiment of the present application, the terminal that has resided in a certain coverage layer and needs to further register with the core network is recorded as the first terminal. The first terminal initiates a registration request message to the core network, where the registration request message can be transmitted to the core network through the NTN base station transparent transmission. That is, the NTN base station does not process the registration request message initiated by the terminal and directly forwards it to the core network.

[0119] In the embodiment of the present application, the registration request message carries the coverage layer identifier of the first coverage layer where the first terminal resides, so that the core network can determine the coverage layer where the first terminal that currently initiates the registration request resides.

[0120] S102: Determine a target coverage layer for the first terminal to be allowed to register based on the number of terminals residing in the first coverage layer; when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, instruct the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiate a registration request message.

[0121] S103: Allow the first terminal to register in the target coverage layer.

[0122] In an embodiment of the present application, during the terminal registration process, the core network counts the number of terminals residing in each coverage layer according to the coverage layer identifier reported by the terminal, and decides whether to perform load sharing in combination with a pre-configured load sharing threshold.

[0123] The following first introduces the process of configuring data from the operation and maintenance platform to the core network with reference to Figure 5. As shown in Figure 5, the process includes the following steps:

[0124] S501: The core network system starts.

[0125] S502: The operation and maintenance platform configures the load threshold parameters of the overlay layer to the core network.

[0126] S503: The core network records the load threshold parameter.

[0127] S504: The operation and maintenance platform sends the NTN base station list information of the coverage layer to the core network.

[0128] S505: The core network updates the NTN base station list information of the coverage layer.

[0129] As an example, the operation and maintenance platform can periodically send a list of NTN base stations in the overlay layer. Accordingly, the core network periodically updates the list of NTN base stations in the overlay layer. The period can be pre-set, for example, to a quarter of the orbital period or a half of the orbital period.

[0130] S506: The operation and maintenance platform sends the ephemeris information of the NTN base station to the core network.

[0131] S507: The core network updates the ephemeris information of the NTN base station.

[0132] As an example, the operation and maintenance platform may periodically send the ephemeris information of the NTN base station. Accordingly, the core network periodically updates the ephemeris information of the NTN base station.

[0133] It can be seen that a load threshold parameter is pre-configured on the core network side. This parameter can represent the load sharing threshold of a single coverage layer, for example, the maximum number of terminals allowed to reside in a single coverage layer.

[0134] As mentioned above, the core network counts the number of terminals residing in each coverage layer. If the count value reaches the load sharing threshold, the coverage layer is load shared, that is, the registration request initiated by the terminal residing in the coverage layer is rejected, and the target coverage layer is determined for the terminal, that is, the coverage layer suitable for the terminal to reside, and the terminal is instructed to reside in the target coverage layer, and then the registration request message is re-initiated.

[0135] As an example, if the terminal currently resides in coverage layer a, and the number of terminals residing in coverage layer a currently counted by the core network has reached the load sharing threshold, then the terminal is not allowed to complete registration, and a suitable coverage layer b is determined for the terminal to reside, instructing the terminal to reside in coverage layer b, and then re-initiating the registration request message.

[0136] In the embodiment of the present application, the method for determining the target coverage layer for the terminal is not limited. For example, any coverage layer where the number of resident terminals does not reach the load sharing threshold is used as the target coverage layer; or the coverage layer with the least number of resident terminals is used as the target coverage layer.

[0137] In an embodiment of the present application, after receiving the instruction, the first terminal may search for a system broadcast message broadcast by the target coverage layer according to the frequency corresponding to the target coverage layer, reside in the target coverage layer, and re-initiate a registration request message to the core network. After receiving the registration request message carrying the identifier of the target coverage layer, the core network allows the first terminal to complete registration in the core network because the number of terminals residing in the target coverage layer does not reach the load sharing threshold.

[0138] The allowing the first terminal to register in the target coverage layer specifically refers to executing steps for registering the first terminal in the target coverage layer.

[0139] The load balancing method provided in the embodiment of the present application is applied to receive a registration request message initiated by a first terminal, wherein the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides; a target coverage layer in which registration is allowed is determined for the first terminal based on the number of terminals residing in the first coverage layer; wherein, when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, the first terminal is instructed to reside in a target coverage layer different from the first coverage layer, and the registration request message is re-initiated; the first terminal is allowed to register in the target coverage layer.

[0140] It can be seen that the NTN base stations are divided into different coverage layers, and a single coverage layer includes NTN base stations that implement single-layer network coverage for ground terminals. The registration request message sent by the first terminal to the core network carries the identifier of the first coverage layer where the terminal resides. The core network can count the number of terminals residing in each coverage layer through the registration request message. The core network is also pre-configured with a load sharing threshold. When the number of terminals residing in the first coverage layer reaches the pre-configured load sharing threshold, the first terminal is not allowed to continue to reside in the first coverage layer, and a target coverage layer suitable for the first terminal to reside is determined. This avoids a large number of terminals concentrating on a certain coverage layer and achieves load balancing between coverage layers. It also avoids the service users of a certain coverage layer exceeding the capacity requirements of the coverage layer, resulting in user access failure or reduced data transmission throughput.

[0141] In one embodiment of the present application, the load sharing threshold includes a first threshold for the total number of resident terminals and / or a second threshold for the number of resident terminals in a connected state.

[0142] Accordingly, the target coverage layer allowed for registration is determined for the first terminal based on the number of resident terminals in the first coverage layer, specifically:

[0143] Determining whether the total number of resident terminals in the first coverage layer reaches a first threshold; and / or determining whether the number of resident terminals in the first coverage layer in a connected state reaches a second threshold;

[0144] If the total number of terminals resident in the first coverage layer does not reach the first threshold, and / or the number of terminals resident in the connected state in the first coverage layer does not reach the second threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0145] Specifically, the pre-configured load sharing threshold can be of various types, including a first threshold for the total number of resident terminals. That is, when determining whether the number of resident terminals in the first coverage layer has reached the pre-configured load sharing threshold, all states of resident terminals in the first coverage layer are considered, including: connected state, deactivated state, and idle state. Among them, the connected state means that the terminal and the NTN base station, as well as the NTN base station and the core network are connected, and data transmission can be carried out at any time. The deactivated state means that no connection is established between the terminal and the NTN base station, but a connection is established for the terminal between the NTN base station and the core network. Once data needs to be sent to the terminal, the NTN base station can send a paging call, and the terminal can quickly return to the connected state after receiving it. The idle state means that no connection is established between the terminal and the NTN base station, as well as between the NTN base station and the core network.

[0146] Correspondingly, if only the first threshold is considered, the total number of resident terminals in the first coverage layer in the connected state, deactivated state and idle state is counted to determine whether the first threshold is reached. If so, load balancing is performed for the first terminal, that is, the first terminal is instructed to reside in other coverage layers and the registration request message is re-initiated.

[0147] In a possible embodiment, the preconfigured load sharing threshold includes a second threshold for the number of resident terminals in the connected state. That is, considering that terminals in the connected state occupy more system resources, only resident terminals in the connected state are counted during load balancing.

[0148] Correspondingly, if only the second threshold is considered, the number of resident terminals in the connected state in the first coverage layer is counted to determine whether the second threshold is reached. If so, load balancing is performed for the first terminal, that is, the first terminal is instructed to reside in other coverage layers and the registration request message is re-initiated.

[0149] In a possible embodiment, if the first threshold and the second threshold are considered at the same time, if the total number of terminals resident in the first coverage layer does not reach the first threshold, and the number of terminals resident in the connected state in the first coverage layer does not reach the second threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0150] It can be seen that in the embodiment of the present application, multiple types of load sharing thresholds can be pre-configured. When performing load balancing processing, only resident terminals in the connected state or resident terminals in all states are considered, which improves the flexibility of load balancing processing.

[0151] In one embodiment of the present application, the load sharing threshold includes a third threshold for the total number of resident terminals in a single coverage area and / or a fourth threshold for the number of resident terminals in a connected state in a single coverage area. The target coverage layer allowed for registration is determined for the first terminal based on the number of resident terminals in the first coverage layer, specifically:

[0152] Determining a first coverage area where the first terminal is located according to the terminal location information carried in the registration request message;

[0153] Determining whether the total number of terminals in the first coverage area and residing in the first coverage layer reaches a third threshold; and / or determining whether the number of terminals in the first coverage area and residing in the first coverage layer and in a connected state reaches a fourth threshold;

[0154] If the total number of terminals in the first coverage area and residing in the first coverage layer does not reach the third threshold; and / or the number of terminals in the first coverage area and residing in the first coverage layer in a connected state does not reach the fourth threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0155] Specifically, the pre-configured load sharing threshold may further include a threshold for a single coverage area, wherein a single coverage area refers to a ground coverage area. The coverage area may be pre-planned, for example, each cell of an NTN base station may be used as a coverage area.

[0156] Correspondingly, if only the third threshold is considered, the first coverage area where the first terminal is located is determined based on the terminal location information carried in the registration request message. When determining whether to perform load balancing for the first terminal, the total number of terminals in the first coverage area and residing in the first coverage layer is counted, that is, the resident terminals in the connected state, deactivated state and idle state are included. If the third threshold is reached, load balancing is performed for the first terminal, that is, the first terminal is instructed to reside in other coverage layers, and the registration request message is re-initiated.

[0157] In a possible embodiment, considering that terminals in a connected state occupy more system resources, a fourth threshold for the number of terminals in a connected state residing in a single coverage area is preconfigured.

[0158] Correspondingly, if only the fourth threshold is considered, the number of terminals in the first coverage area and in the connected state residing in the first coverage layer is counted. If the fourth threshold is reached, load balancing is performed for the first terminal, that is, the first terminal is instructed to reside in other coverage layers and the registration request message is re-initiated.

[0159] In a possible embodiment, if the third threshold and the fourth threshold are considered at the same time, if the total number of terminals in the first coverage area and residing in the first coverage layer does not reach the third threshold; and the number of terminals in the first coverage area and residing in the first coverage layer in a connected state does not reach the fourth threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0160] It can be seen that in the embodiment of the present application, the load sharing threshold for a single ground coverage area can also be pre-configured. When performing load balancing, in addition to considering the number of terminals residing in the entire coverage layer, the number of terminals residing in a single ground coverage area can also be considered. When the number of terminals residing in a single ground coverage area reaches the corresponding threshold, load balancing is also performed on the first terminal, thereby avoiding the existence of a large number of terminals residing in the same coverage layer in a single ground coverage area, resulting in load imbalance between different coverage layers within the ground coverage area.

[0161] In one embodiment of the present application, in step S102, instructing the first terminal to reside in a target coverage layer different from the first coverage layer and re-initiating a registration request message specifically includes:

[0162] Sending a registration rejection message carrying identification information of the target coverage layer to the first terminal; the registration rejection message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message carrying identification information of the target coverage layer;

[0163] Specifically, referring to FIG6 , which is another flowchart of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application, as shown in FIG6 , includes S601 - S604 .

[0164] S601: Receive a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides.

[0165] Among them, a single coverage layer includes an NTN base station that implements single network coverage for ground terminals.

[0166] S602: Determine whether the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold. If so, execute S603.

[0167] S603: Determine a target coverage layer for the first terminal.

[0168] S604: Send a registration rejection message carrying identification information of the target coverage layer to the first terminal; the registration rejection message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message carrying identification information of the target coverage layer.

[0169] Specifically, if the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, the core network may directly deny the first terminal's registration by sending a registration rejection message to the first terminal, which carries the identification information of the target coverage layer. Upon receiving this message, the first terminal can search for system broadcast messages broadcast by the target coverage layer based on its frequency information and apply to reside in the target coverage layer.

[0170] As mentioned above, in addition to broadcasting the identification of the current coverage layer, the NTN base station can also broadcast information such as the frequency of other coverage layers outside the current coverage layer. Therefore, after receiving the identification of the target coverage layer, the first terminal can search for the frequency corresponding to the target coverage layer and receive the system broadcast message of the target coverage layer at the frequency, which speeds up the first terminal's search for the target coverage layer and shortens the time to select the target coverage layer.

[0171] After executing the specific process, the first terminal successfully resides in the target coverage layer, and then the first terminal re-sends a registration request message carrying the identifier of the target coverage layer to the core network, thereby completing registration in the core network.

[0172] For ease of understanding, further explanation is provided below in conjunction with FIG7 . FIG7 is a signaling interaction diagram of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application. As shown in FIG7 , the method includes the following steps:

[0173] S701: The terminal successfully searches the network and resides in a certain coverage layer.

[0174] S702: The terminal initiates a registration process to the core network, carrying the overlay layer identification information.

[0175] As an example, the register message sent by the terminal, that is, the registration request message specified in the protocol, carries the overlay layer identification information.

[0176] S703: The core network counts the number of users in the coverage layer and compares it with the load threshold to determine whether load sharing is required.

[0177] The number of users in the coverage layer, that is, the number of resident terminals in the coverage layer, if reaches a load threshold, it is determined that load sharing is required.

[0178] S704: The core network sends a registration rejection message to the terminal, carrying identification information of the target coverage layer.

[0179] The target coverage layer is determined by the core network and is a coverage layer suitable for the terminal to reside.

[0180] S705: The terminal searches for a new network and resides there again according to the target coverage layer frequency information in the broadcast message.

[0181] After receiving the registration rejection message, the terminal stops the subsequent registration process and re-searches the network for residence based on the frequency information of the target coverage layer, that is, applies to reside in the target coverage layer.

[0182] S706: The terminal re-initiates a registration process to the core network, carrying the identification information of the target coverage layer.

[0183] After the terminal resides in the target coverage layer, it resends a register message to the core network, carrying the identification information of the target coverage layer.

[0184] S707: The core network sends a registration acceptance message to the terminal, notifying the terminal that the registration is successful.

[0185] S708: The core network records the information of the coverage layer where the terminal is located.

[0186] After successful registration, the core network records the coverage layer where the terminal resides.

[0187] In another embodiment of the present application, in step S102, the step of instructing the first terminal to reside in a target coverage layer different from the first coverage layer and re-initiating a registration request message specifically includes:

[0188] A registration acceptance message carrying identification information of the target coverage layer is sent to the first terminal; the registration acceptance message is used to inform the first terminal that the initial registration is completed, and instruct the first terminal to stay in the target coverage layer after entering the idle state, and re-initiate a registration request message carrying identification information of the target coverage layer.

[0189] Specifically, referring to FIG8 , a flow chart of a load balancing method for multiple coverage of a non-terrestrial network (NTN) provided in an embodiment of the present application is shown, including S801 to S804 . S801 to S802 can refer to S601 to S602 and are not described in detail.

[0190] S803: Determine a target coverage layer for the first terminal.

[0191] S804: Send a registration acceptance message carrying the identification information of the target coverage layer to the first terminal; the registration acceptance message is used to inform the first terminal that the initial registration is completed, and instruct the first terminal to stay in the target coverage layer after entering the idle state, and re-initiate a registration request message carrying the identification information of the target coverage layer.

[0192] Specifically, if the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, in order to avoid the core network rejecting terminal registration, which increases the registration time and causes a decline in user experience, the core network can also complete the registration process according to the normal process and allow the first terminal to complete registration in the core network, that is, send a registration acceptance message to the first terminal, but the message carries the identification information of the target coverage layer. After receiving the message, the first terminal completes the initial registration, but after entering the idle state, it searches for the system broadcast message broadcast by the target coverage layer according to the frequency information of the target coverage layer, applies to reside in the target coverage layer, and re-initiates a registration request message carrying the identification information of the target coverage layer.

[0193] For ease of understanding, further description is given below in conjunction with FIG9 , which is another signaling interaction diagram of a load balancing method for multiple coverage of a non-terrestrial network NTN provided in an embodiment of the present application. As shown in FIG9 , the method includes the following steps:

[0194] S901: The terminal successfully searches the network and resides in a certain coverage layer.

[0195] S902: The terminal initiates a registration process to the core network, carrying the overlay layer identification information.

[0196] S903: The core network counts the number of users in the coverage layer and compares it with the load threshold to determine whether load sharing is required.

[0197] S904: The core network sends a registration acceptance message to the terminal, carrying identification information of the target coverage layer.

[0198] The target coverage layer is determined by the core network and is a coverage layer suitable for the terminal to reside.

[0199] Specifically, the core network and the terminal may pre-agreed that if the registration accept message does not carry any overlay identification information, it indicates that the core network allows the terminal to register and does not require load sharing. In this case, the process ends at S905.

[0200] If the registration acceptance message carries the identification information of the target coverage layer, it indicates that the core network allows the terminal to register, but load burden is required. The terminal needs to apply to reside in the target coverage layer when entering the idle state, and re-initiate a registration request message carrying the identification information of the target coverage layer after residing in the target coverage layer.

[0201] S905: The terminal receives the registration acceptance message and completes the initial registration.

[0202] S906: When the terminal enters the idle state, it searches for a new network and resides in the network according to the target coverage layer frequency information in the broadcast message.

[0203] S907: The terminal re-initiates a registration process to the core network, carrying the identification information of the target coverage layer.

[0204] After the terminal resides in the target coverage layer, it resends a register message to the core network, carrying the identification information of the target coverage layer.

[0205] S908: The core network sends a registration acceptance message to the terminal, notifying the terminal that the registration is successful.

[0206] S909: The core network records the information of the coverage layer where the terminal is located.

[0207] After successful registration, the core network records the coverage layer where the terminal resides.

[0208] It can be seen that in the embodiment of the present application, the core network first allows the terminal to complete registration, and instructs the terminal to apply to reside in the target coverage layer after entering the idle state. This gentle processing method is used to avoid the core network directly rejecting the terminal registration, resulting in an increase in the terminal registration time and a decrease in user experience.

[0209] In one embodiment of the present application, the method further includes: when the sum of the number of terminals residing in each coverage layer is lower than the first proportion of the resident number threshold of a single coverage layer, determining the converged coverage layer, instructing the second terminal residing in each coverage layer to reside in the converged coverage layer, and re-initiating the registration request message.

[0210] In this embodiment of the present application, the core network may also perform real-time statistics on the total number of resident terminals in each coverage layer to determine whether the total number of resident terminals is less than a first ratio of a resident number threshold for a single coverage layer. If so, this indicates that there are relatively few resident terminals in each coverage layer, eliminating the need to occupy NTN base stations in multiple coverage layers. Therefore, load aggregation is performed. The first ratio may be preset, for example, 50%.

[0211] Specifically, a converged coverage layer is determined, for example, any coverage layer is determined as the converged coverage layer, or the coverage layer with the largest number of currently resident terminals is determined as the converged coverage layer. Then, the second terminal resident in each coverage layer is instructed, that is, all terminals are resident in the converged coverage layer, and then a registration request message is re-initiated.

[0212] When the second terminal resides in the convergent coverage layer, the NTN base stations in other coverage layers except the convergent coverage layer are instructed to enter a dormant state.

[0213] In one embodiment of the present application, the core network may also report the total number of resident terminals in each coverage layer to the operation and maintenance platform, and the operation and maintenance platform may determine whether to perform the load aggregation operation. For details, please refer to Figure 10, which is a signaling interaction diagram of the load aggregation process provided in an embodiment of the present application, as shown in Figure 10, including the following steps:

[0214] S1001: The core network reports the collected user data of each coverage layer in the NTN network to the operation and maintenance platform.

[0215] The above user data specifically includes the number of resident terminals in each coverage layer.

[0216] S1002: The operation and maintenance platform determines whether the number of users in all coverage layers is lower than a first proportion of a resident number threshold of a single coverage layer.

[0217] If the judgment result is yes, execute S1003.

[0218] S1003: Instruct the core network to perform load aggregation operations.

[0219] Specifically, a convergence indication message carrying identification information of a convergence coverage layer may be sent to the core network. The convergence coverage layer may be determined by the operation and maintenance platform.

[0220] S1004: The core network performs load aggregation operations.

[0221] S1005: The core network notifies the operation and maintenance platform that the load aggregation operation is completed, and all users access the aggregation coverage layer.

[0222] S1006: The operation and maintenance platform configures NTN base stations in other coverage layers except the converged coverage layer to stop service and enter a low power consumption state.

[0223] As can be seen, statistics are collected for all user traffic in each coverage layer. When the total user traffic falls below a certain percentage of the network coverage layer load threshold, load aggregation is performed to aggregate users into the same coverage layer. Therefore, when the number of users is small, by aggregating users into the same coverage layer, services in other coverage layers can be suspended, reducing satellite payload power consumption.

[0224] In one embodiment of the present application, the step of instructing the second terminal residing in each coverage layer to reside in the converged coverage layer and re-initiating the registration request message may specifically include:

[0225] When a tracking area update TAU registration request initiated by the second terminal is received, a TAU rejection message carrying the identification information of the converged coverage layer is sent to the second terminal; the TAU rejection message is used to instruct the second terminal to reside in the converged coverage layer and re-initiate a TAU registration request carrying the identification information of the converged coverage layer.

[0226] Since the second terminal has completed registration in the core network, a registration rejection message cannot be sent directly to the second terminal. However, the TAU registration mechanism specified in the protocol can be used to guide the second terminal to reside in the converged coverage layer.

[0227] Specifically, the protocol stipulates that TAU ​​registration is triggered when the terminal's location area changes, or TAU registration is triggered periodically. For ease of understanding, the following is a detailed description with reference to FIG11. FIG11 is a signaling interaction diagram of a load aggregation operation provided in an embodiment of the present application, including the following steps:

[0228] S1101: The terminal triggers TAU registration due to a location area change or reaching a trigger period.

[0229] S1102: The terminal initiates a TAU registration request to the core network.

[0230] S1103: The core network determines that it is currently in a state of executing a load aggregation operation.

[0231] S1104: The core network sends a TAU reject message to the terminal.

[0232] The TAU reject message carries identification information of the converged coverage layer.

[0233] S1105: The terminal reselects a network to search for and reside in based on the frequency information of the converged coverage layer.

[0234] After a specific process, the terminal resides in the converged coverage layer.

[0235] S1106: The terminal re-initiates a TAU registration request carrying the identification information of the converged coverage layer.

[0236] As an example, the TAU REQ message carries identification information of the converged coverage layer.

[0237] S1107: The core network sends a TAU acceptance message to the terminal, notifying the terminal that the TAU registration is successful.

[0238] S1108: The core network updates the coverage layer where the terminal is located.

[0239] As can be seen, in one embodiment of the present application, the TAU registration mechanism specified in the protocol can be used to reject the TAU registration after receiving a TAU registration request initiated by the terminal, and feedback is given of a TAU rejection message carrying the identification information of the converged coverage layer, thereby guiding the terminal to reside in the converged coverage layer. After a certain period of time, each terminal completes the coverage layer change through the TAU registration mechanism, and all terminals reside in the converged coverage layer. This can then instruct NTN base stations in other coverage layers to enter sleep mode, reducing satellite payload power consumption.

[0240] In one embodiment of the present application, the step of instructing the second terminal residing in each coverage layer to reside in the converged coverage layer and re-initiating the registration request message may specifically include:

[0241] When a TAU request initiated by the second terminal is received, a TAU acceptance message carrying the identification information of the converged coverage layer is sent to the second terminal; the TAU acceptance message is used to inform the second terminal that the TAU registration is completed, and to instruct the second terminal to stay in the converged coverage layer after entering the idle state, and re-initiate a TAU request carrying the identification information of the converged coverage layer.

[0242] For ease of understanding, the following is a detailed description with reference to FIG12 . FIG12 is another signaling interaction diagram of a load aggregation operation provided in an embodiment of the present application, including the following steps:

[0243] S1201: The terminal triggers TAU registration due to a location area change or reaching a trigger period.

[0244] S1202: The terminal initiates a TAU registration request to the core network.

[0245] S1203: The core network determines that it is currently in a state of executing a load aggregation operation.

[0246] S1204: The core network sends a TAU acceptance message to the terminal.

[0247] The TAU accept message carries identification information of the converged coverage layer. The TAU accept message is used to inform the second terminal that the TAU registration is completed and to instruct the second terminal to reside in the converged coverage layer after entering the idle state.

[0248] S1205: The terminal receives the TAU acceptance message and completes the TAU registration.

[0249] S1206: When the terminal enters the idle state, it searches for a new network and resides there according to the frequency information of the converged coverage layer in the broadcast message.

[0250] S1207: The terminal re-initiates the TAU registration process to the core network, carrying the identification information of the converged coverage layer.

[0251] S1208: The core network sends a TAU acceptance message to the terminal, notifying the terminal that the TAU registration is successful.

[0252] S1209: The core network updates the coverage layer where the terminal is located.

[0253] It can be seen that in one embodiment of the present application, the terminal is guided to reside in the converged coverage layer with the help of the TAU registration mechanism specified in the protocol. In addition, considering that after the terminal receives the TAU rejection message, the terminal in the connected state will release the service, resulting in a decline in user experience, a gentle way is adopted to guide the terminal to reside in the converged coverage layer. That is, the core network completes the TAU registration according to the normal process, that is, sends a TAU acceptance message to the second terminal to inform the second terminal that the TAU registration is completed, but the TAU acceptance message carries the identification information of the converged coverage layer. After receiving the message, the second terminal enters the idle state, searches for the system broadcast message of the converged coverage layer according to the frequency information of the converged coverage layer, applies to reside in the converged coverage layer, and re-initiates the registration request message carrying the identification information of the converged coverage layer. This avoids the decline in user experience due to the release of the service after the terminal receives the TAU rejection message.

[0254] The following introduces the paging process in the non-terrestrial network (NTN) and introduces the technical problems existing in the paging process under multiple coverage.

[0255] Specifically, paging refers to the process of searching for terminal users initiated by the network side. The trigger condition for paging is when the network has signaling or data to be sent to the mobile terminal, but the status of the mobile terminal is not connected. At this time, the network side cannot send data directly to the terminal, and the network side must perform a paging action.

[0256] In related technologies, when the core network performs paging based on the terminal location, since the terminal location is covered by multiple networks, the core network searches for an NTN base station that covers the terminal location. However, due to the multiple coverage of the NTN network, the terminal will find multiple NTN base stations. The core network can only notify each NTN base station to send paging. However, the terminal will only reside under a certain NTN base station. Therefore, the paging of other NTN base stations is invalid, resulting in a waste of the precious air interface resources of the NTN base station, an increase in the power consumption of the NTN base station, and possible interference due to collision of paging opportunities.

[0257] In one embodiment of the present application, as shown in FIG13 , which is a flow chart of a paging method for an NTN multiple coverage scenario provided by an embodiment of the present application, the method further includes the following steps:

[0258] S1301: Determine candidate NTN base stations according to a first location of the terminal to be paged; the candidate NTN base stations include NTN base stations covering the first location and belonging to different coverage layers;

[0259] In this step, due to the multiple coverage characteristics of the NTN network, multiple candidate NTN base stations can be determined based only on the first location of the terminal to be paged. The candidate NTN base stations all cover the first location and belong to different coverage layers.

[0260] S1302: According to the coverage layer where the terminal to be paged currently resides, determine a target NTN base station belonging to the coverage layer from candidate NTN base stations;

[0261] In this embodiment, the core network can determine the coverage layer where the terminal is located, and can filter out the target NTN base station belonging to the coverage layer from the candidate NTN base stations by combining the NTN base station list information of each coverage layer.

[0262] S1303: Send a paging indication message for the terminal to be paged to the target NTN base station, so that the target NTN base station initiates paging for the terminal to be paged.

[0263] There is only one determined target NTN base station, so the core network only needs to send a paging indication message to the target NTN base station.

[0264] It can be seen that since the concept of coverage layer is introduced in the embodiment of the present application, the core network can determine the coverage layer where the terminal is located. Therefore, after determining the candidate NTN base station based on the first position of the terminal to be paged, the target NTN base station can be screened out according to the coverage layer where the terminal is located, that is, the NTN base station belonging to the coverage layer, and then only the target NTN base station is instructed to initiate paging for the terminal to be paged. This can avoid the NTN base station from initiating invalid paging, save the precious air interface resources of the NTN base station, reduce the power consumption of the NTN base station, and avoid interference caused by collision of paging opportunities.

[0265] 14 is a flow chart of a load balancing method applied to a terminal according to an embodiment of the present application, which includes the following steps:

[0266] S1401: Receive a system broadcast message from an NTN base station, where the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs. A single coverage layer includes an NTN base station that implements single network coverage for a ground terminal.

[0267] S1402: Apply to reside in the first overlay layer according to the system broadcast message.

[0268] S1403: After residing in the first overlay layer, a registration request message is sent to the core network. The registration request message carries the overlay layer identifier of the first overlay layer.

[0269] S1404: Receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, where the indication message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message.

[0270] It can be seen that NTN base stations are divided into different coverage layers, and a single coverage layer includes NTN base stations that implement single-layer network coverage for ground terminals. The system broadcast message of the NTN base station carries the identifier of the first coverage layer to which the NTN base station belongs. Therefore, after the first terminal achieves residence based on the system broadcast message, the registration request message sent to the core network also carries the identifier of the first coverage layer where the terminal resides. The core network can count the number of terminals residing in each coverage layer through the registration request message. The core network is also pre-configured with a load sharing threshold. When the number of terminals residing in the first coverage layer reaches the pre-configured load sharing threshold, the first terminal is not allowed to continue to reside in the first coverage layer, and a target coverage layer suitable for the first terminal to reside is determined. This avoids a large number of terminals concentrating on a certain coverage layer and achieves load balancing between coverage layers. It also avoids the service users of a certain coverage layer exceeding the capacity requirements of the coverage layer, resulting in user access failure or reduced data transmission throughput.

[0271] The present application also provides a load balancing device for use in a core network. FIG15 is a schematic diagram of a structure of a load balancing device for use in a core network according to an embodiment of the present application. The device includes:

[0272] The receiving module 1501 is configured to receive a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides;

[0273] Determining module 1502, configured to determine a target coverage layer for the first terminal based on the number of resident terminals in the first coverage layer; wherein, when the number of resident terminals in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of resident terminals in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message;

[0274] The registration module 1503 is configured to allow the first terminal to register in the target coverage layer.

[0275] It can be seen that the NTN base stations are divided into different coverage layers, and a single coverage layer includes NTN base stations that implement single-layer network coverage for ground terminals. The registration request message sent by the first terminal to the core network carries the identifier of the first coverage layer where the terminal resides. The core network can count the number of terminals residing in each coverage layer through the registration request message. The core network is also pre-configured with a load sharing threshold. When the number of terminals residing in the first coverage layer reaches the pre-configured load sharing threshold, the first terminal is not allowed to continue to reside in the first coverage layer, and a target coverage layer suitable for the first terminal to reside is determined. This avoids a large number of terminals concentrating on a certain coverage layer and achieves load balancing between coverage layers. It also avoids the service users of a certain coverage layer exceeding the capacity requirements of the coverage layer, resulting in user access failure or reduced data transmission throughput.

[0276] In one embodiment of the present application, the coverage layer is divided according to the track height and / or the elevation track status of the NTN base station.

[0277] In one embodiment of the present application, one or more NTN base stations at orbital heights are divided into the same coverage layer.

[0278] In one embodiment of the present application, NTN base stations at different orbital altitudes are divided into different coverage layers, and ascending NTN base stations and descending NTN base stations at the same orbital altitude are divided into different coverage layers.

[0279] In one embodiment of the present application, the load sharing threshold includes a first threshold for the total number of resident terminals and / or a second threshold for the number of resident terminals in a connected state;

[0280] The determination module 1502 is specifically configured to:

[0281] Determining whether the total number of resident terminals in the first coverage layer reaches the first threshold; and / or determining whether the number of resident terminals in the first coverage layer in a connected state reaches the second threshold;

[0282] If the total number of terminals resident in the first coverage layer does not reach the first threshold, and / or the number of terminals resident in the connected state in the first coverage layer does not reach the second threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0283] In one embodiment of the present application, the load sharing threshold includes a third threshold for the total number of resident terminals in a single coverage area and / or a fourth threshold for the number of resident connected terminals in a single coverage area;

[0284] The determination module 1502 is specifically configured to:

[0285] The determining, based on the number of resident terminals in the first coverage layer, a target coverage layer in which registration is allowed for the first terminal includes:

[0286] Determining a first coverage area where the first terminal is located according to the terminal location information carried in the registration request message;

[0287] Determining whether the total number of terminals in the first coverage area and residing in the first coverage layer reaches the third threshold; and / or determining whether the number of terminals in the first coverage area and residing in the first coverage layer and in a connected state reaches the fourth threshold;

[0288] If the total number of terminals in the first coverage area and residing in the first coverage layer does not reach the third threshold; and / or the number of terminals in the first coverage area and residing in the first coverage layer in a connected state does not reach the fourth threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

[0289] In one embodiment of the present application, the determination module 1502 is specifically configured to:

[0290] Sending a registration rejection message carrying the identification information of the target coverage layer to the first terminal; the registration rejection message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message carrying the identification information of the target coverage layer;

[0291] or,

[0292] Sending a registration acceptance message carrying the identification information of the target coverage layer to the first terminal; the registration acceptance message is used to inform the first terminal that the initial registration is completed, and instruct the first terminal to reside in the target coverage layer after entering the idle state, and re-initiate a registration request message carrying the identification information of the target coverage layer

[0293] In one embodiment of the present application, the device further comprises:

[0294] The aggregation module is used to determine the aggregation coverage layer when the total number of terminals residing in each coverage layer is lower than the first ratio of the resident number threshold of a single coverage layer, and instruct the second terminal residing in each coverage layer to reside in the aggregation coverage layer and re-initiate the registration request message.

[0295] In one embodiment of the present application, the aggregation module is specifically configured to:

[0296] Upon receiving the tracking area update TAU registration request initiated by the second terminal, sending a TAU reject message carrying the identification information of the converged coverage layer to the second terminal; the TAU reject message is used to instruct the second terminal to reside in the converged coverage layer and re-initiate a TAU registration request carrying the identification information of the converged coverage layer;

[0297] or,

[0298] When a TAU request initiated by the second terminal is received, a TAU acceptance message carrying the identification information of the converged coverage layer is sent to the second terminal; the TAU acceptance message is used to inform the second terminal that the TAU registration is completed, and to instruct the second terminal to stay in the converged coverage layer after entering the idle state, and re-initiate a TAU request carrying the identification information of the converged coverage layer.

[0299] In one embodiment of the present application, the apparatus further comprises:

[0300] The instructing module is configured to instruct NTN base stations in other coverage layers except the convergent coverage layer to enter a dormant state when all the second terminals reside in the convergent coverage layer.

[0301] In one embodiment of the present application, the apparatus further includes: a paging module configured to:

[0302] Determine a candidate NTN base station according to the first position of the terminal to be paged; the candidate NTN base station includes an NTN base station covering the first position and belonging to different coverage layers;

[0303] Determine, according to the coverage layer where the terminal to be paged currently resides, a target NTN base station belonging to the coverage layer from among the candidate NTN base stations;

[0304] A paging indication message for the terminal to be paged is sent to the target NTN base station, so that the target NTN base station initiates paging for the terminal to be paged.

[0305] The present application also provides a load balancing device applied to a core network. Referring to FIG16 , FIG16 is a schematic structural diagram of a load balancing device applied to a terminal according to an embodiment of the present application. The device includes:

[0306] The first receiving module 1601 is configured to receive a system broadcast message from an NTN base station, where the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs;

[0307] An application module 1602 is configured to apply for residing in the first coverage layer according to the system broadcast message;

[0308] The registration module 1603 is configured to initiate a registration request message to the core network after residing in the first coverage layer, where the registration request message carries the coverage layer identifier of the first coverage layer;

[0309] The second receiving module 1604 is used to receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a target coverage layer different from the first coverage layer and re-initiates a registration request message.

[0310] It can be seen that NTN base stations are divided into different coverage layers, and a single coverage layer includes NTN base stations that implement single-layer network coverage for ground terminals. The system broadcast message of the NTN base station carries the identifier of the first coverage layer to which the NTN base station belongs. Therefore, after the first terminal achieves residence based on the system broadcast message, the registration request message sent to the core network also carries the identifier of the first coverage layer where the terminal resides. The core network can count the number of terminals residing in each coverage layer through the registration request message. The core network is also pre-configured with a load sharing threshold. When the number of terminals residing in the first coverage layer reaches the pre-configured load sharing threshold, the first terminal is not allowed to continue to reside in the first coverage layer, and a target coverage layer suitable for the first terminal to reside is determined. This avoids a large number of terminals concentrating on a certain coverage layer and achieves load balancing between coverage layers. It also avoids the service users of a certain coverage layer exceeding the capacity requirements of the coverage layer, resulting in user access failure or reduced data transmission throughput.

[0311] The embodiment of the present invention further provides a server, which can be understood as a server that carries a core network, or as a server that carries a specific network element in the core network. As shown in Figure 17, the server includes a processor 1701, a communication interface 1702, a memory 1703, and a communication bus 1704. The processor 1701, the communication interface 1702, and the memory 1703 communicate with each other through the communication bus 1704.

[0312] Memory 1703, used for storing computer programs;

[0313] The processor 1701 is configured to execute the program stored in the memory 1703 by performing the following steps:

[0314] receiving a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides;

[0315] Determining a target coverage layer for the first terminal to be allowed to register based on the number of terminals residing in the first coverage layer; wherein, when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message;

[0316] The first terminal is allowed to register in the target coverage layer.

[0317] The communication bus mentioned in the server above can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0318] The communication interface is used for communication between the above server and other devices.

[0319] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0320] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0321] The embodiment of the present invention further provides a terminal, as shown in FIG18 , including a processor 1801, a communication interface 1802, a memory 1803, and a communication bus 1804, wherein the processor 1801, the communication interface 1802, and the memory 1803 communicate with each other via the communication bus 1804.

[0322] Memory 1803, used for storing computer programs;

[0323] The processor 1801 is configured to execute the program stored in the memory 1803 to implement the following steps:

[0324] receiving a system broadcast message of an NTN base station, where the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs;

[0325] Applying to reside in the first coverage layer according to the system broadcast message;

[0326] After residing in the first coverage layer, initiating a registration request message to a core network, wherein the registration request message carries a coverage layer identifier of the first coverage layer;

[0327] Receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a target coverage layer different from the first coverage layer, and re-initiate a registration request message.

[0328] The communication bus mentioned in the terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. This communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is used in the figure, but this does not mean that there is only one bus or only one type of bus.

[0329] The communication interface is used for communication between the above terminal and other devices.

[0330] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage. Alternatively, the memory may be at least one storage device located away from the processor.

[0331] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.

[0332] In another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned load balancing methods are implemented.

[0333] In another embodiment of the present invention, a computer program product including instructions is provided. When the computer program product is run on a computer, the computer is enabled to execute any load balancing method in the above embodiments.

[0334] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0335] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0336] Each embodiment in this specification is described in a related manner. Similar portions between the various embodiments can be referenced to each other. Each embodiment focuses on the differences between the other embodiments. In particular, the device, server, terminal, computer storage medium, and computer program product embodiments are generally similar to the method embodiments, so their descriptions are relatively simplified. For related portions, reference can be made to the descriptions of the method embodiments.

[0337] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention are included in the scope of protection of the present invention.

Claims

1. A load balancing method, characterized in that: The method comprises: receiving a registration request message initiated by a first terminal, where the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides; Determining a target coverage layer for the first terminal to be allowed to register based on the number of terminals residing in the first coverage layer; wherein, when the number of terminals residing in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of terminals residing in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message; The first terminal is allowed to register in the target coverage layer.

2. The method according to claim 1, characterized in that The coverage layers are divided according to the track height and / or elevation status of the NTN base station.

3. The method according to claim 2, characterized in that NTN base stations at one or more orbital heights are grouped in the same coverage layer.

4. The method according to claim 2, characterized in that NTN base stations at different orbital altitudes are divided into different coverage layers, and ascending NTN base stations and descending NTN base stations at the same orbital altitude are divided into different coverage layers.

5. The method according to claim 1, wherein The load sharing threshold includes a first threshold for the total number of resident terminals and / or a second threshold for the number of resident terminals in a connected state; The determining, based on the number of resident terminals in the first coverage layer, a target coverage layer in which registration is allowed for the first terminal includes: Determining whether the total number of resident terminals in the first coverage layer reaches the first threshold; and / or determining whether the number of resident terminals in the first coverage layer in a connected state reaches the second threshold; If the total number of terminals resident in the first coverage layer does not reach the first threshold, and / or the number of terminals resident in the connected state in the first coverage layer does not reach the second threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

6. The method according to claim 1, characterized in that The load sharing threshold includes a third threshold for the total number of resident terminals in a single coverage area and / or a fourth threshold for the number of resident connected terminals in a single coverage area; The determining, based on the number of resident terminals in the first coverage layer, a target coverage layer in which registration is allowed for the first terminal includes: Determining a first coverage area where the first terminal is located according to the terminal location information carried in the registration request message; Determine whether the total number of terminals in the first coverage area and residing in the first coverage layer reaches the third and / or, determining whether the number of terminals in the first coverage area and residing in the first coverage layer and in a connected state reaches the fourth threshold; If the total number of terminals in the first coverage area and residing in the first coverage layer does not reach the third threshold; and / or the number of terminals in the first coverage area and residing in the first coverage layer in a connected state does not reach the fourth threshold, the target coverage layer is determined to be the first coverage layer; otherwise, a target coverage layer different from the first coverage layer is determined for the first terminal.

7. The method according to claim 1, characterized in that The step of instructing the first terminal to reside in a target coverage layer different from the first coverage layer and re-initiating a registration request message includes: Sending a registration rejection message carrying the identification information of the target coverage layer to the first terminal; the registration rejection message is used to instruct the first terminal to reside in the target coverage layer and re-initiate a registration request message carrying the identification information of the target coverage layer; or, A registration acceptance message carrying the identification information of the target coverage layer is sent to the first terminal; the registration acceptance message is used to inform the first terminal that the initial registration is completed, and to instruct the first terminal to stay in the target coverage layer after entering the idle state, and to re-initiate a registration request message carrying the identification information of the target coverage layer.

8. The method according to claim 1, characterized in that The method further comprises: When the sum of the number of terminals residing in each coverage layer is lower than the first ratio of the resident number threshold of a single coverage layer, a converged coverage layer is determined, and the second terminals residing in each coverage layer are instructed to reside in the converged coverage layer and re-initiate a registration request message.

9. The method according to claim 8, characterized in that The step of instructing the second terminal residing in each of the coverage layers to reside in the converged coverage layer and re-initiating a registration request message includes: Upon receiving the tracking area update TAU registration request initiated by the second terminal, sending a TAU reject message carrying the identification information of the converged coverage layer to the second terminal; the TAU reject message is used to instruct the second terminal to reside in the converged coverage layer and re-initiate a TAU registration request carrying the identification information of the converged coverage layer; or, When a TAU request initiated by the second terminal is received, a TAU acceptance message carrying the identification information of the converged coverage layer is sent to the second terminal; the TAU acceptance message is used to inform the second terminal that the TAU registration is completed, and to instruct the second terminal to stay in the converged coverage layer after entering the idle state, and re-initiate a TAU request carrying the identification information of the converged coverage layer.

10. The method according to claim 9, characterized in that The method further comprises: When all the second terminals reside in the converged coverage layer, the NTN base stations in other coverage layers except the converged coverage layer are instructed to enter a dormant state.

11. The method according to claim 1, wherein The method further comprises: Determine a candidate NTN base station according to the first position of the terminal to be paged; the candidate NTN base station includes an NTN base station covering the first position and belonging to different coverage layers; Determine, according to the coverage layer where the terminal to be paged currently resides, a target NTN base station belonging to the coverage layer from among the candidate NTN base stations; A paging indication message for the terminal to be paged is sent to the target NTN base station, so that the target NTN base station initiates paging for the terminal to be paged.

12. A load balancing method, characterized in that: Applied to a first terminal, the method includes: receiving a system broadcast message of an NTN base station, where the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs; Applying to reside in the first coverage layer according to the system broadcast message; After residing in the first coverage layer, initiating a registration request message to a core network, wherein the registration request message carries a coverage layer identifier of the first coverage layer; Receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a target coverage layer different from the first coverage layer, and re-initiate a registration request message.

13. A load balancing device, characterized in that: The device comprises: A receiving module, configured to receive a registration request message initiated by a first terminal, wherein the registration request message carries a coverage layer identifier of a first coverage layer where the first terminal resides; a determination module, configured to determine a target coverage layer for the first terminal based on the number of resident terminals in the first coverage layer; wherein, when the number of resident terminals in the first coverage layer does not reach a pre-configured load sharing threshold, the target coverage layer is the first coverage layer; when the number of resident terminals in the first coverage layer reaches the load sharing threshold, instructing the first terminal to reside in a target coverage layer different from the first coverage layer, and re-initiating a registration request message; A registration module is configured to allow the first terminal to register in the target coverage layer.

14. A load balancing device, characterized in that: Applied to a first terminal, the apparatus includes: A first receiving module is configured to receive a system broadcast message of an NTN base station, wherein the system broadcast message carries a coverage layer identifier of a first coverage layer to which the NTN base station belongs; An application module, configured to apply for residing in the first coverage layer according to the system broadcast message; a registration module, configured to initiate a registration request message to a core network after residing in the first coverage layer, wherein the registration request message carries a coverage layer identifier of the first coverage layer; The second receiving module is configured to receive an indication message sent by the core network after determining that the number of terminals residing in the first coverage layer reaches a pre-configured load sharing threshold, wherein the indication message is used to indicate that the first terminal resides in a different coverage layer from the first coverage layer. The target coverage layer of the first coverage layer is selected and the registration request message is re-initiated.

15. A server, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; A processor, configured to implement the method steps described in any one of claims 1 to 11 when executing a program stored in a memory.

16. A terminal, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus; Memory for storing computer programs; The processor is configured to implement the method steps described in claim 12 when executing the program stored in the memory.

17. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method steps of any one of claims 1 to 11 or 12 are implemented.

Images