Communication method, communication apparatus and storage medium

Abstract

The present application relates to the field of communications, and provides a communication method, a communication apparatus and a storage medium, capable of effectively controlling the load balancing between NTN cells. The method comprises: acquiring configuration parameters, and sending first information, wherein the configuration parameters comprise at least one of a time parameter, a position parameter and ephemeris information, and the first information is used for indicating that load balancing is executed on the basis of the configuration parameters.

Description

Communication method, communication device and storage medium

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 29, 2023, with application number 202311865411.2 and application name “Communication Method, Communication Device 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 communications, and in particular to a communication method, a communication device, and a storage medium. Background Art

[0003] In a terrestrial network (TN), since there is a large difference between the reference signal received power (RSRP) of terminals located in the cell center area and the RSRP of terminals located in the cell edge area, RSRP can be used to effectively screen out terminals located in the cell center area and terminals in the cell edge area. By setting a switching threshold, terminals in the cell edge area are allowed to switch from the current resident cell to other cells with more idle resources, which can effectively control the load balancing between the cells.

[0004] However, the above solution is only applicable to TN scenarios. In non-terrestrial network (NTN) scenarios, the RSRP of terminals located in different areas of the cell is relatively small, making it difficult to distinguish terminals located at the cell edge by RSRP, and thus unable to effectively control load balancing between cells.

[0005] Summary of the Invention

[0006] In order to solve the above technical problems, the embodiments of the present application provide a communication method, a communication device, and a storage medium, which can more effectively control the load balancing between various NTN cells.

[0007] In a first aspect, a communication method is provided. The method can be performed by a first network device, or by a component of the first network device, such as a processor, chip, or chip system of the first network device, or by a logic module or software that implements all or part of the first network device. The following description uses the method performed by the first network device as an example. The communication method includes obtaining at least one of a time parameter, a location parameter, and ephemeris information, and sending first information indicating load balancing based on configuration parameters.

[0008] It is understandable that the load balancing described in this application may refer to balancing the load or number of terminals among various cells of the NTN by instructing terminal handover.

[0009] In the embodiments of the present application, load balancing can be achieved using at least one of a time parameter, a location parameter, and ephemeris information. Because at least one of the time parameter, the location parameter, or the ephemeris information can better control the number of terminals performing handovers than the signal strength parameter, it can better adapt to NTN scenarios and effectively control load balancing between various NTN cells.

[0010] In conjunction with the first aspect above, in one possible implementation, the time parameter is used to indicate the time when load balancing is performed, such as a time period / time range, or the start time and duration of load balancing, or the start time and end time of load balancing. The location parameter is used to indicate the area where load balancing is performed, such as a regular area / irregular area, or the longitude and latitude information and a preset distance of at least one reference point for load balancing, or the longitude and latitude information of multiple reference points for load balancing. This clarifies the time parameter and the location parameter, so that the first network device can more clearly determine the first information.

[0011] In combination with the above-mentioned first aspect, in a possible implementation method, obtaining configuration parameters includes: receiving configuration parameters from a third network device, that is, the configuration parameters can be obtained from other network devices (i.e., the third network device) other than the first network device, thereby reducing the complexity of obtaining configuration parameters and simplifying system design.

[0012] In combination with the above-mentioned first aspect, in a possible implementation method, the method provided in an embodiment of the present application also includes: sending second information to a third network device and receiving third information from the third network device, wherein the second information is used to indicate the configuration parameters obtained by the first network device to request verification of the configuration parameters; and the third information is used to indicate the feasibility of the configuration parameters.

[0013] That is to say, the first network device can work with the third network device to verify the configuration parameters indicated by the second information to determine the feasibility of the configuration parameters indicated by the second information. In this way, the first network device can subsequently control whether to perform load balancing based on the configuration parameters based on the feasibility of the configuration parameters indicated by the second information to ensure that load balancing can be performed normally based on successful verification.

[0014] In combination with the above-mentioned first aspect, in a possible implementation method, sending the first information includes: when the feasibility of the configuration parameters indicated by the second information meets the preset requirements, sending the first information to the second network device, so as to ensure that load balancing can be executed normally as much as possible.

[0015] In combination with the above-mentioned first aspect, in a possible implementation method, when the configuration parameters include time parameters and / or location parameters, obtaining the configuration parameters includes: receiving ephemeris information, and determining the configuration parameters based on the ephemeris information, so that the first network device can determine the configuration parameters by itself, so that the first network device can subsequently generate first information based on the configuration parameters.

[0016] In combination with the first aspect above, in a possible implementation method, the configuration parameters also include a signal strength parameter, which is used to indicate the signal strength range for performing load balancing. In this way, the first network device can combine at least one of the time parameter, location parameter, and ephemeris information with the channel strength parameter to generate the first information, thereby expanding the diversity of parameters required to perform load balancing, so as to better improve the load balancing effect.

[0017] In combination with the first aspect above, in a possible implementation method, the first information is also used to indicate load balancing based on target parameters, wherein the target parameters are determined from the configuration parameters based on the network type, so that the first network device can provide targeted instructions for load balancing of different types of networks to better improve the load balancing effect.

[0018] In combination with the above-mentioned first aspect, in one possible implementation method, the network type includes TN type and NTN type, so that the communication method described in this application can be applied to TN scenarios and / or NTN scenarios, enriching the application scenarios of the solution provided in this application.

[0019] In a second aspect, a communication method is provided. The method can be executed by a second network device, or by a component of the second network device, such as a processor, chip, or chip system of the second network device. The method can also be implemented by a logic module or software that implements all or part of the second network device. The following description uses the method executed by the second network device as an example. The communication method includes receiving first information, wherein the first information is used to instruct load balancing based on configuration parameters, and the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information.

[0020] In combination with the above second aspect, in a possible implementation, the time parameter is used to indicate the time when load balancing is performed, and the location parameter is used to indicate the area where load balancing is performed.

[0021] In combination with the above second aspect, in a possible implementation, the configuration parameters further include a signal strength parameter, and the signal strength parameter is used to indicate a signal strength range for performing load balancing.

[0022] In combination with the above second aspect, in a possible implementation manner, the first information is further used to instruct to perform load balancing based on a target parameter, wherein the target parameter is determined from a configuration parameter based on a network type.

[0023] In combination with the above second aspect, in a possible implementation, the network type includes TN type and NTN type

[0024] Among them, the technical effects brought about by the second aspect or any implementation method of the second aspect can refer to the technical effects brought about by the corresponding implementation method of the first aspect, and will not be repeated here.

[0025] In a third aspect, a communication device is provided for implementing the various methods described above. The communication device may be the first network device described in the first aspect, or any implementation of the first aspect, or a device including the first network device, or a device included in the first network device, such as a chip; or the communication device may be the second network device described in the second aspect, or any implementation of the second aspect, or a device including the second network device, or a device included in the second network device, such as a chip. The communication device includes modules, units, or means corresponding to the implementation of the above methods, which may be implemented by hardware, software, or by executing corresponding software implementations in hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0026] In some possible designs, the communication device may include a processing module and a transceiver module. The transceiver module, also referred to as a transceiver unit, is configured to implement the transmitting and / or receiving functions described in any of the above aspects and any possible implementations thereof. The transceiver module may be comprised of a transceiver circuit, a transceiver, a transceiver, or a communication interface. The processing module may be configured to implement the processing functions described in any of the above aspects and any possible implementations thereof.

[0027] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in any of the above aspects and any possible implementation methods.

[0028] In a fourth aspect, a communication device is provided, comprising: a processor and a memory; the memory is configured to store computer instructions, and when the processor executes the instructions, the communication device performs the method of any of the aforementioned aspects. The communication device may be the first network device described in the first aspect, or any implementation of the first aspect, or a device including the first network device, or a device included in the first network device, such as a chip; or the communication device may be the second network device described in the second aspect, or any implementation of the second aspect, or a device including the second network device, or a device included in the second network device, such as a chip.

[0029] In a fifth aspect, a communication device is provided, comprising: a processor and a communication interface; the communication interface is configured to communicate with a module external to the communication device; and the processor is configured to execute a computer program or instruction to cause the communication device to perform the method of any of the above aspects. The communication device may be the first network device described in the first aspect, or any implementation of the first aspect, or a device including the first network device, or a device included in the first network device, such as a chip; or the communication device may be the second network device described in the second aspect, or any implementation of the second aspect, or a device including the second network device, or a device included in the second network device, such as a chip.

[0030] In a sixth aspect, a communication device is provided, comprising: at least one processor; the processor is configured to execute a computer program or instruction stored in a memory, so that the communication device performs the method of any of the above aspects. The memory may be coupled to the processor, or may be independent of the processor. The communication device may be the first network device described in the first aspect, or any implementation of the first aspect, or a device including the first network device, or a device included in the first network device, such as a chip; or the communication device may be the second network device described in the second aspect, or any implementation of the second aspect, or a device including the second network device, or a device included in the second network device, such as a chip.

[0031] In the seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is run on a communication device, the communication device can execute any of the above aspects or any of its implementation methods.

[0032] In an eighth aspect, a computer program product comprising instructions is provided, which, when executed on a communication device, enables the communication device to execute the method of any of the above aspects or any of its implementations.

[0033] In a ninth aspect, a communication device is provided (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the functions involved in any of the above aspects or any of its implementation methods.

[0034] In some possible designs, the communication device includes a memory for storing necessary program instructions and data.

[0035] In some possible designs, when the device is a chip system, it can be composed of a chip or include a chip and other discrete devices.

[0036] It can be understood that when the communication device provided in any one of the third to sixth aspects is a chip, the above-mentioned sending action / function can be understood as output, and the above-mentioned receiving action / function can be understood as input.

[0037] In a tenth aspect, a communication method is provided, which includes the method of the above-mentioned first aspect or any implementation thereof, and the method of the above-mentioned second aspect or any implementation thereof.

[0038] In an eleventh aspect, a communication system is provided, which includes the first network device of the above aspect and the second network device of the above aspect.

[0039] Among them, the technical effects brought about by any implementation method in the third aspect to the eleventh aspect can refer to the technical effects brought about by the corresponding implementation method in the first aspect, and will not be repeated here.

[0040] It should be noted that various possible implementations of any of the above aspects can be combined under the premise that the solutions are not contradictory. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] FIG1 is a schematic diagram of a load balancing process provided by an embodiment of the present application;

[0042] FIG2 is a schematic diagram of a TN scenario provided in an embodiment of the present application;

[0043] FIG3 is a schematic diagram of an NTN scenario provided in an embodiment of the present application;

[0044] FIG4 is a schematic diagram of a switching in a load balancing scenario provided by an embodiment of the present application;

[0045] FIG5 is a schematic diagram of switching in another load balancing scenario provided by an embodiment of the present application;

[0046] FIG6 is a schematic structural diagram of a communication system provided in an embodiment of the present application;

[0047] FIG7 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0048] FIG8 is a flow chart of a communication method provided in an embodiment of the present application;

[0049] FIG9 is a schematic diagram of three time period representations provided in an embodiment of the present application;

[0050] FIG10 is a schematic diagram of two regions provided in an embodiment of the present application;

[0051] FIG11 is a schematic diagram of satellite coverage time and area provided in an embodiment of the present application;

[0052] FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

[0053] FIG13 is a flow chart of another communication method provided in an embodiment of the present application;

[0054] FIG14 is a flow chart of another communication method provided in an embodiment of the present application;

[0055] FIG15 is a flow chart of another communication method provided in an embodiment of the present application;

[0056] FIG16 is a schematic structural diagram of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] To facilitate understanding of the technical solutions provided by the embodiments of this application, a brief introduction to the relevant technologies of this application is first given. The brief introduction is as follows:

[0058] 1. Mobility Load Balancing

[0059] Mobility load balancing, also referred to as load balancing, refers to balancing terminals in multiple cells and / or balancing the traffic of terminals in multiple cells so that the load between cells or the number of terminals in each cell is relatively small.

[0060] The randomness of terminal locations and the diversity of service demands can easily lead to significant variations in cell loads. This can cause some cells to experience high loads, leading to network congestion, while others experience low loads, resulting in wasted resources. Load balancing technology can effectively balance coverage across multiple cells, preventing congestion or wasted resources in some cells.

[0061] For example, if there are access network devices 1 and access network device 2, and the load of access network device 1 is higher than the load of access network device 2, then access network device 1 and access network device 2 can exchange resource usage, and access network device 1 can modify the terminal switching threshold, etc., to enable some terminals in the cell covered by access network device 1 to switch out of the current service cell and switch to the cell covered by access network device 2, thereby achieving the purpose of balancing the load between access network device 1 and access network device 2.

[0062] It should be noted that the current load balancing process requires interaction between multiple communication devices, as shown in Figure 1. The load balancing process is described below:

[0063] S101. A network management system (NMS) sends a first modify MOI attributes message to an element management system (EMS). Correspondingly, the EMS receives the first modify MOI attributes message from the NMS.

[0064] The first modified MOI attribute message is used to indicate initial load balancing configuration parameters. The load balancing configuration parameters may include RSRP parameters. The RSRP parameters may be used to indicate the RSRP range for performing load balancing. Of course, the above is merely an exemplary description of the load balancing configuration parameters. The load balancing configuration parameters may also include other information, and the embodiments of the present application do not impose any limitations on this.

[0065] S102 : The EMS sends initial load balancing configuration parameters to the source access network device. Correspondingly, the source access network device receives the initial load balancing configuration parameters from the EMS.

[0066] The source access network device may be an access network device whose load is greater than or equal to a load threshold.

[0067] Optionally, the EMS may set a load threshold according to actual network conditions or experience. For example, the EMS sets the load threshold to 95 bytes per second (bps). This embodiment of the present application does not impose any limitation on this.

[0068] S103: The NMS sends a second message for modifying MOI attributes to the EMS. Correspondingly, the EMS receives the second message for modifying MOI attributes from the NMS.

[0069] The second modified MOI attribute message is used to instruct to perform load balancing.

[0070] S104 . The EMS sends a load balancing indication message to the source access network device. Correspondingly, the source access network device receives the load balancing indication message from the EMS.

[0071] The load balancing indication message is used to instruct the execution of load balancing.

[0072] S105: The source access network device sends a resource status request message to the target access network device. Correspondingly, the target access network device receives the resource status request message from the source access network device.

[0073] The resource status request message is used to instruct the target access network device to measure the target resource.

[0074] Optionally, after S105 , the resource status request message may also be used to instruct the target access network device to measure resources other than the target resource, or the resource status request message may also be used to instruct the target access network device to stop measuring the target resource.

[0075] S106: The target access network device sends a resource status response message to the source access network device. Correspondingly, the source access network device receives the resource status response message from the target access network device.

[0076] The resource status response message is used to indicate that the target access network device has started measuring the target resource.

[0077] S107: The target access network device sends a resource status update message to the source access network device. Correspondingly, the source access network device receives the resource status update message from the target access network device.

[0078] The resource status update message is used to indicate a measurement report, and the measurement report includes resource usage of the target resource. Of course, the above is only an exemplary description of the measurement report, and the measurement report may also include other information, and the embodiment of the present application does not impose any limitation on this.

[0079] Optionally, the target access network device may periodically send resource status update messages to the source access network device according to a configured measurement report reporting period. Correspondingly, the source access network device periodically receives resource status update messages from the target access network device.

[0080] S108. When the usage of the target resource meets the preset conditions, the source access network device sends a switching indication message to the terminal whose RSRP is within the above RSRP range. Correspondingly, the terminal receives the switching indication message from the source access network device.

[0081] The switching indication information is used to instruct the terminal to switch to the target access network device.

[0082] In one possible implementation, since the initial load balancing configuration parameters are set by the NMS, they are generally applicable to a wide range of users, but may be less practical for individual access network devices. Therefore, the source access network device and the target access network device can negotiate to modify the load balancing configuration parameters to better perform load balancing. The following describes the implementation process of negotiating and modifying the load balancing configuration parameters between the source access network device and the target access network device:

[0083] S109: The source access network device sends a mobility change request message to the target access network device. Correspondingly, the target access network device receives the mobility change request message from the source access network device.

[0084] The mobility change request is used to instruct the target access network device to adjust the load balancing configuration parameters, and the mobility change request can carry the modified load balancing configuration parameters. For example, if the resource utilization rate of the target access network device is low, the source access network device can increase the RSRP range indicated by the load balancing configuration parameters.

[0085] S1010: The target access network device sends a mobility change acknowledgement message to the source access network device. Correspondingly, the source access network device receives the mobility change acknowledgement message from the target access network device.

[0086] Wherein, in the case where the target access network device recognizes the modified load balancing configuration parameters carried in the mobility change request, the mobility change response message may be a mobility change success (mobility change acknowledge) message, wherein the mobility change success message is used to indicate that the target access network device has modified the load balancing configuration parameters. In the case where the target access network device does not recognize the modified load balancing configuration parameters carried in the mobility change request, the mobility change response message is used to indicate that the target access network device has not modified the load balancing configuration parameters, and the mobility change response request may carry the modified load balancing configuration parameters recognized by the target access network device.

[0087] As can be seen from the process in Figure 1, the existing load balancing process is performed based on the RSRP range, and this process can be applied to load balancing in TN networks. As shown in Figure 2, in TN, the access network equipment is located on the ground, so that the distance between the terminal under the coverage of the access network equipment and the access network equipment will not exceed a certain threshold. As shown in the relationship curve between the distance between the terminal and the access network equipment and the RSRP of the terminal in Figure 2, there is a clear negative correlation between the distance between the terminal and the access network equipment and the RSRP of the terminal. That is, the RSRP of the terminal that is closer to the access network equipment is higher, while the RSRP of the terminal that is farther away from the ground access network equipment is lower. As shown in Figure 2, since the distance between terminal 1 and the ground access network equipment is closer than that between terminal 2, the RSRP of terminal 1 is higher than that of terminal 2. At this time, load balancing can be performed based on the process shown in Figure 1.

[0088] However, in an NTN, as shown in Figure 3, the access network equipment is located in the air and is generally far away from the terminals. This means that the distance between a terminal covered by the access network equipment and the access network equipment is likely to exceed a certain threshold. As shown in Figure 3, which shows the relationship between the distance between the terminal and the access network equipment and the terminal's RSRP, there is no clear negative correlation between the distance between the terminal and the access network equipment and the terminal's RSRP. This results in no significant difference in the RSRP between terminals within the access network equipment's coverage area. As shown in Figure 3, although the distance between terminal 3 and the access network equipment is closer than that between terminal 4, the difference between the RSRP of terminal 3 and terminal 4 is small.

[0089] In the load balancing scenario, as shown in FIG4 , since there is a large difference between the RSRP of the terminal located in the center area of ​​the TN cell and the RSRP of the terminal located in the edge area of ​​the TN cell, the terminals located in the center area of ​​the TN cell (for example, terminal a in FIG4 ) and the terminals in the edge area of ​​the TN cell (for example, terminal b in FIG4 ) can be effectively screened out through RSRP. By setting the switching threshold, the terminal b in FIG4 is switched from the current resident TN cell to other TN cells with more idle resources, which can effectively control the load balancing between the various TN cells.

[0090] However, the above solution is only applicable to TN scenarios. In NTN scenarios, the RSRP of terminals located in different areas of the NTN cell is relatively small, making it difficult to distinguish terminals located at the edge of the NTN cell by RSRP. This can easily lead to a situation where the handover threshold is too low, resulting in too few terminals handing over to neighboring cells, and the high load of the serving cell remains unrelieved. Alternatively, as shown in Figure 5, it can easily lead to a situation where the handover threshold is too high, resulting in too many terminals handing over to neighboring cells, and the serving cell load is too low, while the load of the neighboring cells is too high, and load balancing is still not achieved.

[0091] Based on this, the present application provides a communication method, in which a first network device can obtain configuration parameters and send first information to instruct load balancing based on the configuration parameters. Since the configuration parameters described in the present application can include at least one of a time parameter, a location parameter, or ephemeris information, and at least one of the time parameter, location parameter, or ephemeris information can better control the number of terminals performing handovers than a signal strength parameter, the method can better adapt to NTN scenarios and more effectively control load balancing between various NTN cells.

[0092] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0093] In order to facilitate understanding of the embodiments of the present application, the following explanations are made before introducing the embodiments of the present application.

[0094] 1. In the embodiments of the present application, for ease of description, when numbering, the numbers may be consecutively numbered starting from 1, starting from 0, or starting from any parameter. It should be understood that the above are all settings made to facilitate the description of the technical solutions provided in the embodiments of the present application, and are not intended to limit the scope of the embodiments of the present application.

[0095] 2. In the embodiment of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information (such as the first indication information below) is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein the other information and the information to be indicated have an association relationship. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can be achieved by means of the arrangement order of each piece of information agreed in advance (for example, stipulated by the protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common parts of each piece of information can also be identified and indicated uniformly to reduce the indication overhead caused by indicating the same information separately.

[0096] In addition, the specific indication method can also be various existing indication methods, such as but not limited to the above-mentioned indication methods and various combinations thereof. The specific details of the various indication methods can be referred to the prior art and will not be repeated herein. As can be seen from the above, for example, when it is necessary to indicate multiple information of the same type, there may be a situation where the indication methods for different information are different. In the specific implementation process, the required indication method can be selected according to specific needs. The embodiment of the present application does not limit the selected indication method. In this way, the indication method involved in the embodiment of the present application should be understood to cover various methods that can enable the party to be indicated to obtain the information to be indicated.

[0097] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The specific sending method is not limited in the embodiments of this application. The sending period and / or sending time of these sub-information can be predefined, for example, predefined according to a protocol, or can be configured by the transmitting device by sending configuration information to the receiving device.

[0098] 3. “Pre-definition” or “pre-configuration” can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a first network device and / or a second network device). The embodiments of the present application do not limit the specific implementation method. Among them, “saving” can mean saving in one or more memories. One or more memories can be set separately or integrated in an encoder or decoder, a processor, or a communication device. One or more memories can also be partially set separately and partially integrated in a decoder, a processor, or a communication device. The type of memory can be any form of storage medium, which is not limited by the embodiments of the present application.

[0099] 4. The “protocol” involved in the embodiments of the present application may refer to a standard protocol in the field of communications, for example, it may include a long term evolution (LTE) protocol, a new radio (NR) protocol, and related protocols used in future communication systems. The embodiments of the present application are not limited to this.

[0100] 5. In the embodiments of the present application, descriptions such as "when...", "in the case of...", "if" and "if" all mean that under certain objective circumstances, the device (for example, the first network device and / or the second network device) will perform corresponding processing. It does not limit the time, nor does it require the device (for example, the first network device and / or the second network device) to perform a judgment action during implementation, nor does it mean that there are other limitations.

[0101] 6. In the description of this application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of this application, in the embodiments of this application, words such as "first" and "second" are used to distinguish between identical or similar items with basically the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0102] In addition, the communication architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of the communication architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0103] FIG6 is a schematic diagram of the structure of a communication system according to an embodiment of the present application. The communication system 600 includes a first network device 601 and a second network device 602. The first network device 601 and the second network device 602 can be connected wirelessly. It should be understood that the number of first network devices 601 and second network devices 602 shown in FIG6 is for example only, and may be greater or less.

[0104] In one possible implementation, first network device 601 obtains configuration parameters and sends first information, where the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information. The first information is used to instruct load balancing to be performed based on the configuration parameters. The specific implementation and related technical effects of this solution can be found in the subsequent method embodiments and are not further described here.

[0105] In one possible implementation, second network device 602 receives first information. The first information indicates that load balancing should be performed based on configuration parameters, where the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information. The specific implementation and related technical effects of this solution can be found in the subsequent method embodiments and are not further described here.

[0106] In some possible implementations, the first network device 601 may be an NMS or an EMS. If the first network device is an NMS, the second network device 601 may be an EMS. If the first network device is an EMS, the second network device 601 may be an access network device. Optionally, the access network device may be an access network device in an NTN.

[0107] In one possible implementation, the NMS in the embodiment of the present application can monitor the status of the network, or further generate or modify network configuration commands, for example, monitor the load status of network devices, or generate configuration parameters or commands related to load balancing.

[0108] In one possible implementation, the EMS in the embodiment of the present application can also monitor the status of the network, or generate or modify network configuration commands. In addition, the EMS can also build a digital twin entity.

[0109] In one possible implementation, the access network device in the embodiment of the present application may include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or an enhanced LTE (LTE-advanced, LTE-A) system, such as a traditional macro base station eNB and a micro base station eNB in ​​a heterogeneous network scenario. Alternatively, it may include a next generation node B (gNB) in a new radio (NR) system. Alternatively, it may include a transmission reception point (TRP), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), a base band pool (BBU pool), or a wireless fidelity (WiFi) access point (AP), etc. Alternatively, it may include a base station in a non-terrestrial network (NTN), that is, it may be deployed on an aircraft or satellite. In the NTN, the network device or access device may serve as a layer 1 (L1) relay, or as a base station, or as an integrated access and backhaul (IAB) node. Alternatively, the first network device may be a device that implements base station functions in the IoT, such as a device that implements base station functions in drone communications, V2X, D2D, or machine-to-machine (M2M) communications.

[0110] Optionally, the communication system 600 may further include a terminal 603 .

[0111] In one possible implementation, the terminal device in the embodiment of the present application may be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal. The terminal may be a user equipment (UE), an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent, or a terminal device in a 5G network or a future evolved public land mobile network (PLMN). The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device or a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. In one possible implementation, the terminal device may be mobile or fixed.

[0112] In a possible implementation, the first network device and the second network device in the embodiment of the present application may also be referred to as a communication device, which may be a general device or a dedicated device, and the embodiment of the present application does not specifically limit this.

[0113] In one possible implementation, the relevant functions of the first network device or the second network device in the embodiment of the present application can be implemented by a single device, or can be implemented by multiple devices together, or can be implemented by one or more functional modules within a single device, and the embodiment of the present application does not specifically limit this. It is understood that the above functions can be network elements in a hardware device, or software functions running on dedicated hardware, or a combination of hardware and software, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0114] For example, the relevant functions of the first network device or the second network device in the embodiment of the present application can be implemented by the communication device 700 in Figure 7. Figure 7 shows a schematic diagram of the structure of the communication device 700 provided in the embodiment of the present application. The communication device 700 includes one or more processors 701, a communication line 702, and at least one communication interface (Figure 7 is only exemplary and is described by taking the communication interface 704 and one processor 701 as an example), and may also include a memory 703.

[0115] The processor 701 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0116] The communication line 702 may include a path for connecting different components.

[0117] Communication interface 704 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, or wireless local area networks (WLAN). For example, the transceiver module may be a device such as a transceiver or a transceiver. In one possible implementation, communication interface 704 may also be a transceiver circuit located within processor 701, used to implement signal input and output to the processor.

[0118] The memory 703 may be a device having a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 702. The memory may also be integrated with the processor.

[0119] The memory 703 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 701. The processor 701 is used to execute the computer-executable instructions stored in the memory 703, thereby implementing the communication method provided in the embodiment of the present application.

[0120] Alternatively, in an embodiment of the present application, the processor 701 may also perform functions related to the processing of the communication method provided in the following embodiments of the present application, and the communication interface 704 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.

[0121] In a possible implementation, the memory 703 in the embodiment of the present application may also be used to store information or parameters described in the following embodiments, such as first indication information.

[0122] The computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

[0123] In a specific implementation, as an embodiment, the processor 701 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 7 .

[0124] In a specific implementation, as an embodiment, the communication device 700 may include multiple processors, such as the processor 701 and the processor 707 in FIG7 . Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0125] In a specific implementation, as an embodiment, the communication apparatus 700 may further include an output device 705 and an input device 706. The output device 705 communicates with the processor 701 and may display information in a variety of ways.

[0126] The communication device 700 can be a general-purpose device or a dedicated device. For example, the communication device 700 can be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, or a device having a similar structure to that shown in FIG7 . The embodiments of the present application do not limit the type of the communication device 700.

[0127] The communication method provided in the embodiment of the present application will be described in detail below with reference to FIG8 .

[0128] It should be noted that in the following embodiments of the present application, the message names, the names of the parameters, or the names of the information between the network elements are only examples. In other embodiments, they may also be other names. The method provided in the embodiments of the present application does not make specific limitations on this.

[0129] It is understood that in the embodiments of the present application, each network element may perform some or all of the steps in the embodiments of the present application. These steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of various operations. In addition, the steps may be performed in a different order than those presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0130] Figure 8 is an example of a communication method provided in an embodiment of the present application. The method is described using the interaction between a first network device and a second network device as an example. Of course, the subject that executes the action of the first network device in the method can also be a device / module in the first network device, such as a chip, processor, processing unit, etc. in the first network device, and the subject that executes the action of the second network device in the method can also be a device / module in the second network device, such as a chip, processor, processing unit, etc. in the second network device. This embodiment of the present application does not specifically limit this.

[0131] Exemplarily, as shown in FIG8 , the communication method includes the following steps:

[0132] S801. A first network device obtains configuration parameters.

[0133] The configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information.

[0134] The time parameter is used to indicate the time when load balancing is performed. That is, the time parameter can indicate both the time point when load balancing is performed and the time period during which load balancing is performed.

[0135] If the time parameter indicates a time point for performing load balancing, the time point may be a start time point or an end time point. Thus, the first network device may determine a time period for performing load balancing based on the time point and a preconfigured time period. The start time point indicates the time point for starting load balancing, and the end time point indicates the time point for stopping load balancing.

[0136] If the time parameter indicates the time period for performing load balancing, the above-mentioned time period may be represented in the following three ways: in one possible implementation, as shown in (a) of Figure 9, the time parameter includes a start time point (start time) and a duration (duration); in another possible implementation, as shown in (c) of Figure 9, the time parameter may include a start time point (start time) and an end time point (end time); in another possible implementation, as shown in (b) of Figure 9, the time parameter includes an end time point (end time) and a duration (duration). Of course, the above is only an exemplary description of the representation of the time period, and the time period can also be represented in other ways, and the embodiments of the present application do not impose any restrictions on this.

[0137] In addition, optionally, the time point or time period involved above may be an absolute time point or absolute time period, or a relative time point or relative time period, and the embodiments of the present application do not impose any restrictions on this.

[0138] The location parameter is used to indicate the area where load balancing is performed. The above-mentioned area can be represented in the following two ways: In one possible implementation, the location parameter may include the latitude and longitude information and a preset distance of at least one reference point, and this implementation is generally applicable to regular areas. For example, as shown in (a) in Figure 10, the area indicated by the above-mentioned location parameter is a circular area (i.e., a regular area). In this way, the area where load balancing is performed indicated by the location parameter can be determined by taking the reference point in the location parameter as the origin and the preset distance in the location parameter as half a point.

[0139] In another possible implementation, the location parameter may include the latitude and longitude information of multiple reference points, and this implementation is generally applicable to irregular areas. For example, as shown in FIG10(b), the area indicated by the location parameter is an irregular area, and multiple reference points are connected to determine the area indicated by the location parameter for load balancing.

[0140] Ephemeris information may include satellite trajectory, coverage inclination, or coverage time. The satellite trajectory may be represented by a satellite orbit and a travel radius, or may be represented by position information at each of multiple moments. Of course, the above is merely an example of ephemeris information; ephemeris information may also include other information, and the present application does not impose any limitations thereto.

[0141] Optionally, the configuration parameters may also include a signal strength parameter, where the signal strength parameter is used to indicate the signal strength range for performing load balancing. In this way, the first network device may combine at least one of the time parameter, location parameter, and ephemeris information with the channel strength parameter to generate the first information, thereby expanding the diversity of parameters required for performing load balancing and thereby better improving the load balancing effect. Exemplarily, the above-mentioned signal strength may be RSRP. The above is only an exemplary description of signal strength. Signal strength may also be other network indicators, and the embodiments of the present application do not impose any restrictions on this.

[0142] Of course, the above is only an exemplary description of the configuration parameters. The configuration parameters may also include other parameters, and the embodiments of the present application do not impose any limitations on this.

[0143] In some embodiments, the first network device can obtain configuration parameters in the following two ways: Method 1 is that the first network device obtains configuration parameters from the third network device. Method 2 is that the first network device determines the configuration parameters on its own. Methods 1 and 2 are described in detail below:

[0144] Method 1 is that the first network device obtains configuration parameters from the third network device. In method 1, the third network device can send configuration parameters to the first network device, and the first network device receives the configuration parameters from the third network device accordingly, reducing the complexity of obtaining configuration parameters and simplifying system design.

[0145] In one example, the third network device may be a digital twin entity. The digital twin entity is used to simulate the process of load balancing based on configuration parameters. In this example, the digital twin entity may also provide the first network device with information such as the predicted number of satellites, satellite coverage time in different areas, satellite capacity, and total satellite travel time. This embodiment of the present application does not impose any restrictions on this.

[0146] Furthermore, in conjunction with the above example, before the first network device obtains configuration parameters from the third network device, the first network device may send seventh information to the third network device. Accordingly, the third network device receives the seventh information from the first network device. The seventh information includes a twin object, twin parameters, and ephemeris information, so that the third network device can determine the configuration parameters based on the seventh information. The twin object includes at least one physical network object, and the twin parameters include configuration parameters corresponding to each physical network object in the at least one physical network object.

[0147] After the first network device obtains the configuration parameters from the third network device, if the first network device still needs to update the configuration parameters, it can resend the seventh information to the third network device so that the third network device can re-determine the configuration parameters.

[0148] It is understandable that since the ephemeris information is affected by multiple factors, it is difficult to simply determine the time parameter and / or position parameter. Therefore, the above-mentioned method 1 is more suitable for the case where the first network device itself does not have strong computing capabilities.

[0149] Optionally, the first network device can be an EMS or an NMS. If the first network device is an EMS, the digital twin entity can be deployed in the first network device. In this case, the digital twin entity can be called a digital twin entity branch, and the simulation environment of the digital twin entity branch and the independently deployed digital twin entity needs to be the same. If the simulation environment of the digital twin entity branch deviates, the digital twin entity branch cannot normally simulate the process of load balancing based on configuration parameters, and an independently deployed digital twin entity is required to simulate the process of load balancing based on configuration parameters.

[0150] Furthermore, the first network device needs to pre-build the digital twin entity branch. Specifically, the process of the first network device building the digital twin entity branch can be: NMS sends the fourth information (also referred to as the digital twin entity branch creation request) to the first network device, and accordingly, the first network device receives the fourth information from NMS, wherein the fourth information is used to indicate the configuration information of the digital twin entity branch. The first network device builds the digital twin entity branch based on the configuration information of the above-mentioned digital twin entity branch, and sends the fifth information to NMS, wherein the fifth information is used to indicate whether the data twin entity is created successfully. If the fifth information is used to indicate that the digital twin entity branch is unsuccessful, the fifth information can also indicate the reason for the unsuccessful creation of the digital twin entity branch.

[0151] However, if the NMS wants the service provided by the data twin entity branch, the NMS can call the service provided by the data twin entity branch through the first network device.

[0152] In addition, the first network device may also have the ability to modify the digital twin entity branch. Specifically, the process of the first network device modifying the digital twin entity branch can be: the first network device sends a digital twin entity branch modification request to the third network device, and accordingly, the third network device can receive the digital twin entity branch modification request from the first network device, wherein the digital twin entity branch modification request is used to indicate the identification of the digital twin entity branch and the information to be modified (for example, added information, modified information, etc.). The third network device can modify the digital twin entity branch based on the digital twin entity branch modification request.

[0153] Method 2 is for the first network device to determine the configuration parameters on its own. In Method 2, the first network device may receive ephemeris information and determine the configuration parameters based on the ephemeris information. In this case, the configuration parameters typically include time parameters and / or location parameters.

[0154] In some examples, the first network device may receive ephemeris information from the second network device, and may also receive ephemeris information from other network devices (eg, satellites). This embodiment of the present application does not impose any limitations on this.

[0155] Optionally, the first network device can determine the configuration parameters in a variety of ways. For example, the first network device determines the configuration parameters through a neural network model. Specifically, the first network device can input the ephemeris information into the neural network model to obtain the configuration parameters. For another example, the first network device can calculate the coverage area of ​​the satellite, or the coverage area of ​​the satellite within the target time period, through artificial intelligence (AI) and ephemeris information, and determine the configuration parameters based on the coverage area of ​​the satellite calculated above. For example, as shown in Figure 11, satellite 1 covers area 1 at 10:00, area 2 at 10:30, and area 3 at 11:00; or the coverage area of ​​the satellite within the target time period.

[0156] Of course, the above is only an exemplary description of the implementation method of the first network device obtaining configuration parameters. The first network device can also obtain configuration parameters through other methods. For example, when the first network device is an EMS, the first network device can also obtain configuration information from the NMS side. This application does not impose any restrictions on this.

[0157] As a possible implementation, in the case where the first network device is an EMS, the second network device may be a source access network device, so that the first network device may obtain configuration parameters from the NMS, wherein the above-mentioned configuration parameters may be carried in the first modification management object entity message recorded in the above S101, and the configuration parameters are sent to the source access network device, so that the EMS, the NMS, and the source access network device can all know the configuration parameters. In the case where the first network device is an NMS, the second network device may be an EMS, so that the first network device may send configuration parameters to the EMS, wherein the above-mentioned configuration parameters may be carried in the first modification management object entity message recorded in the above S101, and the EMS resends the configuration parameters to the source access network device, so that the EMS, the NMS, and the source access network device can all know the configuration parameters.

[0158] Furthermore, optionally, when the second network device is the source access network device, the source access network device and the fourth network device (i.e., the target access network device) may also negotiate to modify configuration parameters. The implementation process of the second network device (i.e., the source access network device) and the fourth network device (i.e., the target access network device) negotiating to modify configuration parameters can be understood with reference to the relevant descriptions of S109 to S110 above, and will not be repeated here.

[0159] S804: The first network device sends first information to the second network device. Correspondingly, the second network device receives the first information from the first network device.

[0160] The first information is used to instruct to perform load balancing based on configuration parameters.

[0161] In one possible implementation, the second network device may be an access network device with a load greater than or equal to a load threshold. Thus, the first network device may instruct the second network device, through the first information, to perform load balancing based on configuration parameters. The load balancing may be an operation that instructs the terminal to switch to a fourth network device, where the fourth network device may be an access network device with a load less than the load threshold.

[0162] Optionally, the communication method described in the embodiments of the present application can be applied not only to TN networks, but also to NTN networks. However, different types of networks adapt to different configuration parameters. For example, the configuration parameters adapted to the TN network may include at least one of the following: time parameters, location parameters, or signal strength parameters. For another example, the configuration parameters adapted to the NTN network may include at least one of the following: time parameters, location parameters, signal strength parameters, or ephemeris information. In view of this, the first network device can also determine the configuration parameters suitable for the network type based on the network type. That is, the first network device can provide targeted instructions for load balancing of different types of networks so that the second network device can better perform load balancing, thereby better improving the load balancing effect. In view of this, in this case, the second information can also be used to indicate the execution of load balancing based on target parameters, wherein the target parameters are determined from the configuration parameters based on the network type.

[0163] In addition, optionally, the above-mentioned target parameters can also be determined based on the actual network situation (for example, the distribution of each terminal in the communication network). For example, if the terminals are distributed more concentratedly, the target parameters can give priority to location parameters; if the terminals are distributed more dispersedly, the target parameters can give priority to time parameters or ephemeris information.

[0164] As a possible implementation, in the case where the first network device is an EMS, the second network device may be a source access network device, so that the first network device may obtain the first information from the NMS, wherein the above-mentioned first information may be carried in the second modification management object entity message recorded in the above-mentioned S103, and the first information is sent to the source access network device, so that the EMS, the NMS, and the source access network device may all obtain the first information. In the case where the first network device is an NMS, the second network device may be an EMS, so that the first network device may send the first information to the EMS, wherein the above-mentioned first information may be carried in the second modification management object entity message recorded in the above-mentioned S103, and the EMS may resend the first information to the source access network device, so that the EMS, the NMS, and the source access network device may all obtain the first information.

[0165] Optionally, before S804 , the first network device may further instruct the second network device to enable a load balancing function, so that the second network device can directly perform load balancing based on the configuration parameters after receiving the first information.

[0166] The present application provides a communication method in which a first network device can obtain configuration parameters and send first information to instruct load balancing based on the configuration parameters. Since the configuration parameters described in the present application may include at least one of a time parameter, a location parameter, or ephemeris information, and the at least one of the time parameter, location parameter, or ephemeris information can better control the number of terminals performing handovers than a signal strength parameter, the method is more adaptable to NTN scenarios and can more effectively control load balancing between various NTN cells.

[0167] In one possible implementation, before S804, in order to ensure that load balancing can be performed normally as much as possible, the first network device can work with the third network device to verify the configuration parameters obtained above to determine the feasibility of the configuration parameters indicated by the second information. In this way, the first network device can subsequently control whether to perform load balancing based on the feasibility of the configuration parameters indicated by the second information. In view of this, as shown in Figure 8, the communication method provided in this embodiment of the application also includes the following S802 to S803.

[0168] S802: The first network device sends second information to the third network device. Correspondingly, the third network device receives the second information from the first network device.

[0169] The second information is used to indicate the configuration parameters acquired by the first network device.

[0170] Optionally, the second information can also be used to indicate a twin object and / or a twin parameter. Of course, the above is only an exemplary description of the second information. The second information can also be used to indicate other information, and the embodiment of the present application does not impose any restrictions on this. The description of the twin object and the twin parameter can be understood with reference to the description of the corresponding position above, which will not be repeated here.

[0171] S803: The third network device sends third information to the first network device. Correspondingly, the first network device receives the third information from the third network device.

[0172] The third information is used to indicate the feasibility of the configuration parameters indicated by the second information.

[0173] For example, the feasibility of the configuration parameter indicated by the second information can be expressed as a percentage. For example, the feasibility of the configuration parameter indicated by the second information is 80%. Of course, the above is only an exemplary description of the representation of the feasibility of the configuration parameter indicated by the second information. The feasibility of the configuration parameter indicated by the second information can also be expressed in other ways, and the embodiments of the present application do not impose any limitation on this.

[0174] Optionally, before S803, the third network device may simulate and verify the configuration parameters indicated by the second information, obtain simulation verification results, and generate third information based on the simulation verification results, wherein the simulation verification results may be used to indicate the feasibility of the configuration parameters indicated by the second information.

[0175] Further, optionally, after the first network device learns the feasibility of the configuration parameters indicated by the second information, S804 may be replaced by S804A.

[0176] S804A: When the feasibility of the configuration parameters indicated by the second information meets preset requirements, the first network device sends the first information to the second network device. Correspondingly, the second network device receives the first information from the first network device.

[0177] For example, when the feasibility of the configuration parameter indicated by the second information can be expressed as a percentage, the preset requirement can be that the feasibility is greater than or equal to a feasibility threshold (e.g., 90%). The feasibility threshold can be set by the third network device based on actual conditions or experience, and the embodiments of the present application do not impose any restrictions on this.

[0178] Furthermore, if the feasibility of the configuration parameters indicated by the second information does not meet preset requirements, in order to enable load balancing, the first network device may modify the configuration parameters indicated by the second information, obtain the modified configuration parameters, and send third information to the second network device. Accordingly, the second network device receives the third information from the first network device. The third information is used to instruct the execution of load balancing based on the modified configuration parameters.

[0179] Optionally, before sending the third information, the first network device may further verify the feasibility of the modified configuration parameters in conjunction with the third network device, and send the third information to the second network device if the feasibility of the modified configuration parameters meets preset requirements.

[0180] In addition, when the feasibility of the configuration parameters indicated by the second information does not meet the preset requirements, the fourth information can also be used to indicate the modified configuration parameters, so that the first network device can directly send the third information to the second network device without modifying the configuration parameters indicated by the second information, thereby reducing the processing burden of the first network device.

[0181] It should be noted that the communication method described above involves the first network device jointly verifying the feasibility of the configuration parameters indicated by the second information with the third network device. However, the first network device may also jointly verify the load balancing effect achieved by the configuration parameters indicated by the second information with the third network device. For example, if the third network device verifies that load balancing based on the configuration parameters indicated by the second information can result in a load difference between the second network device and the fourth network device of less than or equal to 5 bps, the first network device may further send the first information to the second network device.

[0182] Optionally, the network type includes a TN type and an NTN type, so that the communication method described in this application can be applied to a TN scenario and / or an NTN scenario, enriching the application scenarios of the solution provided in this application.

[0183] Optionally, as shown in FIG12 , the communication method described in the embodiment of the present application is described below by taking the first network device as an EMS and the second network device as a source access network device as an example:

[0184] S1201: The NMS sends a first modify MOI attributes message to the EMS. The EMS receives the first modify MOI attributes message from the NMS.

[0185] The first modify MOI attributes message may include configuration parameters, which may include at least one of the following: time parameters, location parameters, ephemeris information, or signal strength information.

[0186] S1202: The EMS sends configuration parameters to the source access network device. The source access network device receives the configuration parameters from the EMS.

[0187] Optionally, before S1202 , the EMS needs to select a source access network device based on actual network conditions.

[0188] S1203: The NMS sends a second message for modifying attributes of a managed object entity to the EMS. The EMS receives the second message for modifying attributes of a managed object entity from the NMS.

[0189] The second message for modifying the attributes of the managed object entity includes the first information.

[0190] S1204: The EMS sends first information to the source access network device. The source access network device receives the first information from the EMS.

[0191] In one possible implementation, the EMS determines to enable the load balancing switch based on actual network conditions and sends a message instructing the source access network device to enable the load balancing switch. The source access network device receives the message instructing the source access network device to enable the load balancing switch from the EMS.

[0192] Optionally, as shown in Figure 13, the communication method described in the embodiment of the present application is explained below by taking the first network device as EMS, the second network device as the source access network device, the third network device as the digital twin entity, and the third network device deployed in the first network device as an example: the difference from the communication method shown in Figure 12 is mainly that the communication method shown in Figure 13 can verify the configuration parameters in conjunction with the third network device.

[0193] S1301. The NMS sends a first digital twin service request message to the digital twin entity. Correspondingly, the digital twin entity receives the first digital twin service request message from the NMS.

[0194] The first digital twin service request message may include at least one of the following: a configuration parameter, a twin object, or a twin parameter. For configuration parameters, twin objects, or twin parameters, please refer to the description of the corresponding positions above for understanding, and will not be repeated here.

[0195] S1302: The digital twin entity sends a first digital twin service request reply message to the NMS. The NMS receives the digital twin service request reply message from the first digital twin entity.

[0196] Among them, the first digital twin business request reply message may include the feasibility of the configuration parameters and / or the modified configuration parameters.

[0197] It should be noted that when the feasibility of the configuration parameters does not meet the preset conditions, the twin service request reply message will carry the modified configuration parameters (for example, modified time parameters, modified location parameters, modified signal strength parameters, etc.).

[0198] In addition, if the EMS wants to call the digital twin entity again, the above S1301 to S1302 can be executed again between the NMS and the digital twin entity.

[0199] S1303: If the feasibility of the configuration parameters meets the preset conditions, the NMS sends a first message for modifying attributes of a management object entity to the EMS. The EMS receives the first message for modifying attributes of a management object entity from the NMS.

[0200] S1304: The EMS sends configuration parameters to the source access network device. The source access network device receives the configuration parameters from the EMS.

[0201] S1305: The NMS sends a second message for modifying attributes of a managed object entity to the EMS. The EMS receives the second message for modifying attributes of a managed object entity from the NMS.

[0202] S1306: The EMS sends the first information to the source access network device. The source access network device receives the first information from the EMS.

[0203] It can be understood that the above S1303 to S1306 can be understood by referring to the above S1201 to S1204, and will not be repeated here.

[0204] Optionally, as shown in Figure 14, the communication method recorded in the embodiment of the present application is explained below by taking the first network device as EMS, the second network device as the source access network device, and the third network device as a digital twin entity as an example: the difference from the communication method shown in Figure 12 is mainly that the communication method shown in Figure 14 can determine the configuration parameters by the third network device.

[0205] S1401. The NMS sends a second digital twin service request message to the digital twin entity. Correspondingly, the digital twin entity receives the second digital twin service request message from the NMS.

[0206] The second digital twin service request message may include at least one of the following: ephemeris information, twin object, or twin parameter. For ephemeris information, twin object, or twin parameter, please refer to the description of the corresponding position above for understanding, which will not be repeated here.

[0207] S1402: The digital twin entity sends a second digital twin service request reply message to the NMS. The NMS receives the digital twin service request reply message from the second digital twin entity.

[0208] Among them, the second digital twin business request reply message may include configuration parameters, number of satellites, satellite coverage time in different areas, satellite capacity, or total satellite driving time.

[0209] In addition, if the EMS wants to call the digital twin entity again, the above S1401 to S1402 can be executed again between the NMS and the digital twin entity.

[0210] S1403: If the feasibility of the configuration parameters meets the preset conditions, the NMS sends a first message for modifying attributes of a managed object entity to the EMS. The EMS receives the first message for modifying attributes of a managed object entity from the NMS.

[0211] S1404: The EMS sends configuration parameters to the source access network device. The source access network device receives the configuration parameters from the EMS.

[0212] S1405: The NMS sends a second message for modifying attributes of a managed object entity to the EMS. The EMS receives the second message for modifying attributes of a managed object entity from the NMS.

[0213] S1406: The EMS sends the first information to the source access network device. The source access network device receives the first information from the EMS.

[0214] It can be understood that the above S1403 to S1406 can be understood by referring to the above S1201 to S1204, and will not be repeated here.

[0215] Optionally, as shown in Figure 15, the communication method recorded in the embodiment of the present application is explained below by taking the second network device as the source access network device as an example: the difference from the communication method shown in Figure 12 is mainly that the communication method shown in Figure 15 is mainly aimed at the interaction between access network devices.

[0216] S1501: A source access network device sends a mobility change request message to a target access network device. Correspondingly, the target access network device receives the mobility change request message from the source access network device.

[0217] The mobility change request message may include configuration parameters.

[0218] S1502: The target access network device determines whether to perform mobility change based on configuration parameters.

[0219] S1503: The target access network device sends a mobility change acknowledgement message to the source access network device. Correspondingly, the source access network device receives the mobility change acknowledgement message from the target access network device.

[0220] The mobility change response message is used to indicate that the configuration parameters are approved, or the mobility change response message is used to indicate that the configuration parameters are not approved and carries the configuration parameters modified by the target access network device.

[0221] S1504: When both the target access network device and the source access network device agree on the configuration parameters, the source access network device exchanges resource usage information with the target access network device.

[0222] S1505: When the usage of the target resource meets the preset conditions, the source access network device sends switching indication information to the terminal based on the configuration parameters. Correspondingly, the terminal receives the switching indication information from the source access network device.

[0223] The switching indication information is used to instruct the terminal to switch to the target access network device.

[0224] It should be noted that the above is only an exemplary description of the communication method. For communication methods in other situations (for example, the first network device is NMS and the source access network device is EMS), you can refer to the description of the corresponding location for understanding, and will not repeat them here.

[0225] The above primarily describes the solutions provided by the embodiments of the present application from the perspective of interaction between various network elements. Accordingly, the embodiments of the present application also provide a communication device for implementing the various methods described above. The communication device may be a network device in the above method embodiments, or a device including the above network device, or a component usable for a network device; alternatively, the communication device may be a terminal device in the above method embodiments, or a device including the above terminal device, or a component usable for a terminal device. It is understood that, to implement the aforementioned functions, the communication device includes hardware structures and / or software modules corresponding to the respective functions. Those skilled in the art will readily appreciate that, in conjunction with the various exemplary units and algorithm steps described in the embodiments disclosed herein, the present application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or in a hardware-driven manner by computer software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this application.

[0226] In the embodiment of the present application, the communication device can be divided into functional modules according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be understood that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0227] For example, taking the communication device as the terminal device in the above method embodiment as an example, Figure 16 shows a schematic structural diagram of a communication device 160. The communication device 160 includes a processing module 1601 and a transceiver module 1602. The transceiver module 1602, which may also be referred to as a transceiver unit, is used to implement transceiver functions and may be, for example, a transceiver circuit, a transceiver, a transceiver, or a communication interface.

[0228] When the communication device 160 shown in FIG16 is the first network device in the above embodiment:

[0229] In one possible implementation:

[0230] The processing module 1601 is used to instruct the transceiver module 1602 to obtain configuration parameters and send first information, wherein the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information; the first information is used to instruct to perform load balancing based on the configuration parameters.

[0231] In some embodiments, the time parameter is used to indicate the time when load balancing is performed, and the location parameter is used to indicate the area where load balancing is performed.

[0232] In some embodiments, the processing module 1601 is further configured to instruct the transceiver module 1602 to receive configuration parameters from a third network device.

[0233] In some embodiments, the processing module 1601 is also used to instruct the transceiver module 1602 to send second information to the third network device, and the second information is used to indicate the configuration parameters obtained by the first network device; the processing module 1601 is also used to instruct the transceiver module 1602 to receive third information from the third network device, and the third information is used to indicate the feasibility of the configuration parameters indicated by the second information.

[0234] In some embodiments, when the feasibility of the configuration parameters indicated by the second information meets preset requirements, the processing module 1601 is further configured to instruct the transceiver module 1602 to send the first information to the second network device.

[0235] In some embodiments, the processing module 1601 is further configured to instruct the transceiver module 1602 to receive ephemeris information; the processing module 1601 is further configured to determine configuration parameters based on the ephemeris information.

[0236] In some embodiments, the configuration parameters further include a signal strength parameter, where the signal strength parameter is used to indicate a signal strength range for performing load balancing.

[0237] In some embodiments, the first information is further used to instruct to perform load balancing based on a target parameter, wherein the target parameter is determined from a configuration parameter based on a network type.

[0238] In some embodiments, the network type includes a terrestrial network TN type and a non-terrestrial network NTN type.

[0239] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0240] In the embodiment of the present application, the first network device is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the first network device can take the form of the communication device 700 shown in Figure 7.

[0241] For example, the processor 701 in the communication device 700 shown in FIG7 may call the computer-executable instructions stored in the memory 703 to enable the communication device 700 to execute the communication method in the above method embodiment.

[0242] Specifically, the functions / implementation processes of the transceiver module 1602 and the processing module 1601 in FIG16 can be implemented by the processor 701 in the communication device 700 shown in FIG7 calling computer-executable instructions stored in the memory 703. Alternatively, the functions / implementation processes of the processing module 1601 in FIG16 can be implemented by the processor 701 in the communication device 700 shown in FIG7 calling computer-executable instructions stored in the memory 703, and the functions / implementation processes of the transceiver module 1602 in FIG16 can be implemented by the communication interface 704 in the communication device 700 shown in FIG7.

[0243] Since the first network device 160 provided in the embodiment of the present application can execute the above-mentioned communication method, the technical effects that can be obtained can refer to the above-mentioned method embodiment and will not be repeated here.

[0244] When the communication device 160 shown in FIG16 is the second network device in the above embodiment:

[0245] In one possible implementation:

[0246] The processing module 1601 is used to instruct the transceiver module 1602 to receive first information, where the first information is used to instruct to perform load balancing based on configuration parameters, where the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information.

[0247] In some embodiments, the time parameter is used to indicate the time when load balancing is performed, and the location parameter is used to indicate the area where load balancing is performed.

[0248] In some embodiments, the configuration parameters further include a signal strength parameter, where the signal strength parameter is used to indicate a signal strength range for performing load balancing.

[0249] In some embodiments, the first information is further used to instruct to perform load balancing based on a target parameter, wherein the target parameter is determined from a configuration parameter based on a network type.

[0250] In some embodiments, the network type includes a terrestrial network TN type and a non-terrestrial network NTN type.

[0251] Among them, all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0252] In the embodiment of the present application, the second network device is presented in the form of various functional modules divided in an integrated manner. The "module" here can refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above functions. In a simple embodiment, those skilled in the art can imagine that the second network device can take the form of the communication device 700 shown in Figure 7.

[0253] For example, the processor 701 in the communication device 700 shown in FIG7 may call the computer-executable instructions stored in the memory 703 to enable the communication device 700 to execute the communication method in the above method embodiment.

[0254] Specifically, the functions / implementation processes of the transceiver module 1602 and the processing module 1601 in FIG16 can be implemented by the processor 701 in the communication device 700 shown in FIG7 calling computer-executable instructions stored in the memory 703. Alternatively, the functions / implementation processes of the processing module 1601 in FIG16 can be implemented by the processor 701 in the communication device 700 shown in FIG7 calling computer-executable instructions stored in the memory 703, and the functions / implementation processes of the transceiver module 1602 in FIG16 can be implemented by the communication interface 704 in the communication device 700 shown in FIG7.

[0255] Since the second network device 160 provided in this embodiment can execute the above communication method, the technical effects that can be obtained can refer to the above method embodiments and will not be repeated here.

[0256] It should be understood that one or more of the above modules or units can be implemented by software, hardware, or a combination of the two. When any of the above modules or units is implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method flow. The processor can be built into an SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip. In addition to the core used to execute software instructions to perform calculations or processing within the processor, it can further include necessary hardware accelerators, such as field programmable gate arrays (FPGAs), PLDs (programmable logic devices), or logic circuits that implement dedicated logic operations.

[0257] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a digital signal processing (DSP) chip, a microcontroller unit (MCU), an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a dedicated digital circuit, a hardware accelerator or a non-integrated discrete device, which can run the necessary software or not rely on the software to execute the above method flow.

[0258] In one possible implementation, an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), which includes a processor for implementing the method in any of the above method embodiments. In one possible design, the communication device also includes a memory. The memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication device to execute the method in any of the above method embodiments. Of course, the memory may not be in the communication device. When the communication device is a chip system, it may be composed of a chip, or it may include a chip and other discrete devices, which is not specifically limited in the embodiment of the present application.

[0259] In one possible implementation, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is run on a communication device, the communication device can execute any of the above-mentioned method embodiments or any of its implementation methods.

[0260] In a possible implementation, an embodiment of the present application further provides a communication method, which includes any of the above method embodiments or any of its implementations.

[0261] In a possible implementation, an embodiment of the present application further provides a communication system, which includes the terminal device of the above method embodiment and the network device of the above method embodiment.

[0262] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware, or any combination thereof. When implemented using a software program, 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 according to the embodiments of the present application 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 media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0263] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by reviewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in the claims. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.

[0264] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

Claims

1. A communication method, characterized in that, Applied to a first network device, the method includes: Obtain configuration parameters, where the configuration parameters include at least one of time parameters, location parameters, and ephemeris information; Send a first message, where the first message is used to indicate performing load balancing based on the configuration parameters.

2. The method according to claim 1, wherein The time parameter is used to indicate the time for performing load balancing, and the location parameter is used to indicate the area for performing the load balancing.

3. The method according to claim 1, wherein The obtaining the configuration parameters includes: Receive the configuration parameters from a third network device.

4. The method according to any one of claims 1 to 3, characterized in that The method further includes: Send a second message to the third network device, where the second message is used to indicate the configuration parameters obtained by the first network device; Receive a third message from the third network device, where the third message is used to indicate the feasibility of the configuration parameters indicated by the second message.

5. The method according to claim 4, wherein The sending the first message includes: When the feasibility of the configuration parameters indicated by the second message meets a preset requirement, send the first message to a second network device.

6. The method according to claim 1, characterized in that, When the configuration parameters include the time parameter and / or the location parameter, the obtaining the configuration parameters includes: Receive the ephemeris information; Based on the ephemeris information, determine the configuration parameters.

7. The method according to any one of claims 1-6, characterized in that, The configuration parameters further include a signal strength parameter, where the signal strength parameter is used to indicate the signal strength range for performing the load balancing.

8. The method according to any one of claims 1-7, characterized in that, The first message is further used to indicate performing the load balancing based on target parameters, where the target parameters are determined from the configuration parameters based on the network type.

9. The method according to claim 8, characterized in that, The network type includes a terrestrial network TN type and a non-terrestrial network NTN type.

10. A communication method, characterized in that, Applied to a second network device, the method includes: Receive a first message, where the first message is used to indicate performing load balancing based on configuration parameters, where the configuration parameters include at least one of time parameters, location parameters, and ephemeris information.

11. The method according to claim 10, wherein The time parameter is used to indicate the time for performing load balancing, and the location parameter is used to indicate the area for performing the load balancing.

12. The method according to claim 10 or 11, characterized in that The configuration parameters further include a signal strength parameter, where the signal strength parameter is used to indicate the signal strength range for performing the load balancing.

13. The method according to any one of claims 10 to 12, characterized in that, The first message is further used to indicate performing the load balancing based on target parameters, where the target parameters are determined from the configuration parameters based on the network type.

14. The method according to claim 13, wherein The network type includes a terrestrial network TN type and a non-terrestrial network NTN type.

15. A communication device, characterized in that, Includes: Functional units for performing the functions of the method according to any one of claims 1-9, or functional units for performing the functions of the method according to any one of claims 10-14; where the actions performed by the functional units are implemented by hardware or by hardware executing corresponding software.

16. A communication device, characterized in that, The communication device includes a processor; the processor is used to run computer programs or instructions, or is used to make the communication device perform the method according to any one of claims 1-9 through logic circuits, or make the communication device perform the method according to any one of claims 10-14.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions or programs. When the computer instructions or programs run on a computer, the communication device is caused to execute the method described in any one of claims 1-9, or the communication device is caused to execute the method described in any one of claims 10-14.

18. A communication method, characterized in that a first network device obtains configuration parameters, where the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information; the first network device sends first information to a second network device, where the first information is used to indicate performing load balancing based on the configuration parameters; load balancing; the second network device receives the first information from the first network device, where the first information is used to indicate performing load balancing based on configuration parameters, where the configuration parameters include at least one of a time parameter, a location parameter, and ephemeris information.

19. A communication system, characterized in that, including: a communication device for executing the method described in any one of claims 1-9 and a communication device for executing the method described in any one of claims 10-14.

Images