Method, device and system for load balancing of a bearer network based on core network traffic statistics

Abstract

The application provides a kind of based on core network traffic statistics, bearer network load balancing method, device and system, the method comprises: according to the statistical result of core network control plane network element SMF forwarding constructs bearer network traffic component diagram, wherein the statistical result is obtained by the traffic information statistics of core network user plane network element UPF to multiple GTP-U tunnels and the statistical result is sent to core network control plane network element SMF;When link congestion occurs in bearer network, according to the bearer network traffic component diagram, obtain the to-be-scheduled traffic for scheduling to other non-congestion links in the current congestion link, change the flow diversion rule of bearer network access router side and change the path of the to-be-scheduled traffic in the bearer network to schedule the to-be-scheduled traffic to other non-congestion links, realize bearer network load balancing.The application can realize the identification and load balancing of data stream granularity under the condition that bearer network equipment capacity is limited and bearer network does not identify GTP-U packet header.

Description

Technical Field

[0001] This application relates to the field of mobile communications, and in particular to a method, apparatus and system for load balancing of bearer networks based on core network traffic statistics. Background Technology

[0002] A 5G system consists of an access network, a transport network, and a core network. The access network and core network are defined in 3GPP. The transport network is the information transmission network connecting the access network and the core network. Typically, when load balancing is required on the transport network, the transport network equipment identifies the five-tuple of received data packets (source and destination IP, transport layer protocol, and source and destination ports) and then performs flow-based load balancing. However, for 5G network transport networks, the data streams of multiple users accessing the same base station are encapsulated within the same GTP-U tunnel. The transport network needs to read the contents of the IP header, transport layer header, and GTP-U header to complete flow-based load balancing. However, for devices with limited processing capabilities, this mechanism is too cumbersome and difficult to implement.

[0003] Existing load balancing solutions assume that different data flows can be easily identified and distinguished. However, for the transport network, effectively identifying different data flows requires delving into the data payload of the GTP-U tunnel for analysis and identification, which places very high demands on the processing capabilities of the transport network equipment. When the capacity of the transport network equipment is limited, it becomes difficult to achieve granular identification and load balancing of data flows. Summary of the Invention

[0004] In view of this, embodiments of this application provide a method, apparatus and system for load balancing of bearer networks based on core network traffic statistics, so as to eliminate or improve one or more defects existing in the prior art.

[0005] One aspect of this application provides a bearer network load balancing method based on core network traffic statistics, the method comprising the following steps:

[0006] A traffic composition map of the bearer network is constructed based on the statistical results forwarded by the core network control plane element SMF. The statistical results are obtained by the core network user plane element UPF from traffic information statistics of multiple GTP-U tunnels and the statistical results are sent to the core network control plane element SMF.

[0007] When link congestion occurs in the bearer network, the traffic to be scheduled in the currently congested link is obtained according to the traffic composition map of the bearer network. The traffic diversion rules on the access router side of the bearer network are changed and the path of the traffic to be scheduled in the bearer network is changed so as to schedule the traffic to be scheduled to other non-congested links, thereby realizing load balancing of the bearer network.

[0008] In some embodiments of this application, the GTP-U tunnel is established by the core network user plane element UPF and the access network element gNB through a bearer network.

[0009] In some embodiments of this application, the core network user plane element UPF selects an IP address from the UPF pool as the tunnel endpoint IP, so that when receiving data packets sent from the access network element gNB, the bearer network access switch directs the data packets to the GTP-U tunnel corresponding to the endpoint IP by identifying the source IP, destination IP and ToS fields of the data packets.

[0010] In some embodiments of this application, the step of constructing a bearer network traffic composition map based on the statistical results of SMF forwarding from the core network control plane element includes:

[0011] Based on the flow value of each carrier network tunnel in the statistical results and the corresponding carrier network tunnel, the flow distribution of different carrier network tunnels in the whole network is obtained, and the carrier network flow composition map is constructed.

[0012] In some embodiments of this application, the step of obtaining the traffic to be scheduled on the currently congested link for scheduling to other non-congested links based on the traffic composition map of the bearer network, changing the traffic redirection rules on the bearer network access router side, and changing the path of the traffic to be scheduled through the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network, includes:

[0013] The scheduling characteristics of the traffic to be scheduled are obtained, a non-congestion path is planned for the traffic to be scheduled, and the scheduling characteristics and the non-congestion path are sent to the switch on the ingress side of the bearer network, so that the switch can identify the data packets in the data plane and encapsulate the matched data for load balancing into a new bearer network tunnel.

[0014] Another aspect of this application provides a bearer network load balancing method based on core network traffic statistics, the method comprising the following steps:

[0015] Statistical results were obtained by analyzing the flow information of multiple GTP-U tunnels.

[0016] The statistical results are sent to the core network control plane element (SMF), which then forwards the statistical results to the bearer network controller. The bearer network controller then constructs a bearer network traffic composition map based on the statistical results. When link congestion occurs in the bearer network, it uses the bearer network traffic composition map to obtain the traffic to be scheduled on the currently congested link for redirection to other non-congested links. It then modifies the routing rules on the bearer network access router side and changes the path of the traffic to be scheduled through the bearer network to redirect the traffic to other non-congested links, thereby achieving bearer network load balancing.

[0017] A third aspect of this application provides a bearer network load balancing device based on core network traffic statistics, the device comprising:

[0018] The bearer network traffic composition map construction module is used to construct a bearer network traffic composition map based on the statistical results of forwarding by the core network control plane network element SMF. The statistical results are obtained by the core network user plane network element UPF performing traffic information statistics on multiple GTP-U tunnels and sending the statistical results to the core network control plane network element SMF.

[0019] The load balancing module is used to obtain the traffic to be scheduled to other non-congested links in the currently congested link according to the traffic composition map of the bearer network when link congestion occurs, change the traffic diversion rules on the bearer network access router side and change the path of the traffic to be scheduled in the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby realizing load balancing of the bearer network.

[0020] A fourth aspect of this application provides a bearer network load balancing system based on core network traffic statistics, the system comprising:

[0021] The access network element gNB is used to establish a GTP-U tunnel with the core network user plane element UPF through the bearer network.

[0022] The core network user plane network element UPF establishes the GTP-U tunnel with the access network element gNB through the bearer network. The core network user plane network element UPF is used to execute the bearer network load balancing method based on core network traffic statistics described in the second aspect above.

[0023] The core network control plane element SMF is used to receive statistical results and forward the statistical results to the bearer network controller;

[0024] The bearer network controller is used to execute the bearer network load balancing method based on core network traffic statistics described in the first aspect above.

[0025] The fifth aspect of this application provides an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the bearer network load balancing method based on core network traffic statistics described in the first and second aspects above.

[0026] The sixth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the bearer network load balancing method based on core network traffic statistics described in the first and second aspects above.

[0027] This invention provides a method, apparatus, and system for load balancing of a bearer network based on core network traffic statistics. The method includes: constructing a bearer network traffic composition map based on statistical results forwarded by the core network control plane element SMF, wherein the statistical results are obtained by the core network user plane element UPF performing traffic information statistics on multiple GTP-U tunnels and sending the statistical results to the core network control plane element SMF; when link congestion occurs in the bearer network, obtaining the traffic to be scheduled on the currently congested link for scheduling to other non-congested links according to the bearer network traffic composition map, changing the traffic redirection rules on the bearer network access router side, and changing the path of the traffic to be scheduled through the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network. This invention can achieve data flow granularity identification and load balancing under conditions where the bearer network equipment capacity is limited and the bearer network does not recognize GTP-U packet headers.

[0028] Additional advantages, objectives, and features of this application will be set forth in part in the description which follows, and will in part become apparent to those skilled in the art upon review of the following description, or may be learned by practice of the application. The objectives and other advantages of this application can be realized and obtained by means of the structures specifically pointed out in the specification and drawings.

[0029] Those skilled in the art will understand that the purposes and advantages that can be achieved with this application are not limited to those specifically described above, and that the above and other purposes that this application can achieve will be more clearly understood from the following detailed description. Attached Figure Description

[0030] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, do not constitute a limitation thereof. The components in the drawings are not drawn to scale but are merely for illustrating the principles of this application. For ease of illustration and description of certain parts of this application, corresponding portions in the drawings may be enlarged, i.e., may appear larger relative to other components in an exemplary device actually manufactured according to this application. In the drawings:

[0031] Figure 1 This is a flowchart illustrating a load balancing method for bearer networks based on core network traffic statistics in one embodiment of this application.

[0032] Figure 2 This is a flowchart illustrating a bearer network load balancing method based on core network traffic statistics executed by the core network user plane network element UPF in another embodiment of this application.

[0033] Figure 3 This is a schematic diagram of a load balancing device for a bearer network based on core network traffic statistics, as described in another embodiment of this application. Detailed Implementation

[0034] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the embodiments and accompanying drawings. Here, the illustrative embodiments and their descriptions are used to explain this application, but are not intended to limit it.

[0035] It should also be noted that, in order to avoid obscuring this application with unnecessary details, only the structures and / or processing steps closely related to the solution according to this application are shown in the accompanying drawings, while other details that are not closely related to this application are omitted.

[0036] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, element, step, or component, but does not exclude the presence or addition of one or more other features, elements, steps, or components.

[0037] It should also be noted that, unless otherwise specified, the term "connection" in this article can refer not only to a direct connection, but also to an indirect connection involving an intermediary.

[0038] In the following description, embodiments of the present application will be illustrated with reference to the accompanying drawings. In the drawings, the same reference numerals represent the same or similar parts, or the same or similar steps.

[0039] The integration of satellite and 5G is a development trend in mobile communication networks. Terrestrial mobile communication networks can leverage satellite networks to achieve seamless global information interconnection and efficient, ubiquitous access, showing great promise.

[0040] A satellite-5G converged system consists of an access network, a bearer network, and a core network. The access network and core network are defined in 3GPP. The bearer network is the information transmission network connecting the access network and the core network, and can be a terrestrial network or a satellite network.

[0041] The core network is divided into the user plane and the control plane. The main network element on the user plane is the User Plane Function (UPF), which is primarily responsible for routing and forwarding data packets in the 5G core network user plane. As a 5GC network user plane element, the UPF mainly supports UE service data addressing, encapsulation, routing and forwarding, data and service identification, action and policy execution, etc. The UPF is controlled and managed by the 5G control plane, executing service flow processing according to various policies issued by the control plane. In addition to the above functions, the UPF also has functions such as application monitoring, data flow QoS processing, traffic usage reporting, IP management, mobility adaptation, policy control, and charging, which can be referenced in 3GPP TS 23.501 specification. All core network data must be forwarded through the UPF before flowing to the external network. The core network control plane mainly includes network elements such as the SMF and PCF, which are mainly responsible for session management, UE IP address allocation and management, UPF selection and control, policy execution, and QoS control.

[0042] For the access network, the main network element is the gNB, which includes both control plane and data plane functions. It is mainly responsible for user access, radio resource management, terminal data transmission services, and phased array payload control functions.

[0043] For the connection between the access network and the core network, the logical interface currently primarily uses GTP-U tunnels to carry user plane data. The physical interface, however, requires a bearer network to connect the access network and the core network. In particular, when using a satellite network as the bearer network, the distribution and demands of users within the satellite network's coverage area vary, leading to uneven traffic distribution on the satellite network. Some satellites are idle, while others are heavily loaded, resulting in uneven resource utilization and decreased network efficiency. Therefore, effective load balancing techniques are needed in satellite networks to improve satellite link utilization.

[0044] The following examples will provide a detailed description.

[0045] This application provides a load balancing method for a bearer network based on core network traffic statistics, which can be executed by a bearer network load balancing device based on core network traffic statistics. See [link to relevant documentation]. Figure 1 The load balancing method for the bearer network based on core network traffic statistics specifically includes the following:

[0046] Step 110: Construct a traffic composition map of the bearer network based on the statistical results forwarded by the core network control plane element SMF. The statistical results are obtained by the core network user plane element UPF from traffic information statistics of multiple GTP-U tunnels and the statistical results are sent to the core network control plane element SMF.

[0047] Step 120: When link congestion occurs in the bearer network, obtain the traffic to be scheduled in the currently congested link for other non-congested links according to the traffic composition map of the bearer network, change the traffic diversion rules on the bearer network access router side and change the path of the traffic to be scheduled in the bearer network to schedule the traffic to be scheduled to other non-congested links, so as to achieve load balancing of the bearer network.

[0048] Specifically, the core network user plane element (UPF) performs traffic information statistics on multiple GTP-U tunnels and sends the statistical results to the core network control plane element (SMF). The SMF forwards the statistical results to the bearer network controller, which then constructs a bearer network traffic composition map based on the statistical results. When the occupancy rate of a link in the bearer network reaches a preset congestion threshold, the system first obtains the traffic to be scheduled on the currently congested link for redirection to other non-congested links based on the bearer network traffic composition map. Then, it modifies the routing rules on the bearer network access router side and changes the path of the traffic to be scheduled in the bearer network to redirect the traffic to other non-congested links. This effectively identifies data flow granularity and achieves load balancing even when the bearer network equipment capacity is limited and the bearer network does not recognize GTP-U packet headers.

[0049] It should be noted that this solution is applicable to situations where satellite networks or terrestrial networks are used as 5G bearer networks, and GTP-U tunnels can also be replaced by SR-MPLS, SRV6, and other traffic engineering tunnels.

[0050] To further improve the accuracy of traffic information statistics for multiple GTP-U tunnels by the core network user plane element UPF, step 110 includes:

[0051] Step 111: The GTP-U tunnel is established by the core network user plane element UPF and the access network element gNB through the bearer network.

[0052] In step 111, the core network user plane element UPF and the access network element gNB establish a GTP-U tunnel through the bearer network.

[0053] Specifically, the core network user plane element UPF selects an IP address from the UPF pool as the tunnel endpoint IP, so that when receiving data packets sent from the access network element gNB, the bearer network access switch redirects the data packets to the GTP-U tunnel corresponding to the endpoint IP by identifying the source IP, destination IP and ToS fields of the data packets.

[0054] Specifically, the core network user plane element UPF selects an IP address from the UPF pool as the tunnel endpoint IP, with the selection principle primarily based on even distribution of services. During the transmission of data packets from the access network element gNB to the core network user plane element UPF, the first hop for the data packet is the access switch of the bearer network. The bearer network access switch then identifies the source IP, destination IP, and ToS fields of the data packet and redirects it to the GTP-U tunnel corresponding to the endpoint IP, thereby effectively improving the accuracy of data packet transmission within the tunnel.

[0055] It should be noted that the core network user plane element UPF reserves an address for each access network element gNB to establish a GTP-U tunnel. The recommended allocation rule is that the IP addresses available to each access network element gNB belong to the same subnet segment. In this way, the bearer network can reduce the number of entries through longest prefix matching and segment aggregation.

[0056] Furthermore, the identification of data packets is not limited to the source IP, destination IP, and ToS fields; it can also include other fields in the outer header of the GTP-U tunnel.

[0057] Step 112: Constructing the bearer network traffic composition map based on the statistical results of SMF forwarding of core network control plane network elements includes: obtaining the traffic distribution of different bearer network tunnels in the whole network based on the traffic value of each bearer network tunnel in the statistical results and the bearer network tunnel corresponding to that tunnel, and constructing the bearer network traffic composition map.

[0058] In step 112, the bearer network controller obtains the traffic distribution of different bearer network tunnels in the whole network based on the traffic value of each bearer network tunnel in the statistical results and the bearer network tunnel corresponding to that tunnel, thereby constructing a bearer network traffic composition map and effectively recording the traffic distribution of different bearer network tunnels in the whole network.

[0059] To further achieve load balancing of the bearer network, step 120 includes:

[0060] Step 121: The step of obtaining the traffic to be scheduled on the currently congested link for other non-congested links based on the traffic composition map of the bearer network, changing the traffic redirection rules on the bearer network access router side and changing the path of the traffic to be scheduled on the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network, includes:

[0061] The scheduling characteristics of the traffic to be scheduled are obtained, a non-congestion path is planned for the traffic to be scheduled, and the scheduling characteristics and the non-congestion path are sent to the switch on the ingress side of the bearer network, so that the switch can identify the data packets in the data plane and encapsulate the matched data for load balancing into a new bearer network tunnel.

[0062] In step 121, the bearer network controller first obtains the scheduling characteristics of the traffic to be scheduled, then plans a non-congestion path for the traffic to be scheduled, and finally sends the scheduling characteristics and the non-congestion path to the switch on the ingress side of the bearer network. This enables the switch to identify the data packets in the data plane and encapsulate the matched data for load balancing into a new bearer network tunnel, thereby achieving load balancing of the bearer network tunnel and reducing the processing pressure on the bearer network.

[0063] This application also provides a bearer network load balancing method based on core network traffic statistics, executed by the core network user plane network element UPF. Figure 2 The method includes the following steps:

[0064] Step 210: Perform traffic flow statistics on multiple GTP-U tunnels to obtain statistical results.

[0065] Step 220: Send the statistical results to the core network control plane element SMF, so that the core network control plane element SMF forwards the statistical results to the bearer network controller. The bearer network controller constructs a bearer network traffic composition map based on the statistical results. When link congestion occurs in the bearer network, it obtains the traffic to be scheduled in the currently congested link for scheduling to other non-congested links based on the bearer network traffic composition map, changes the traffic diversion rules on the bearer network access router side, and changes the path of the traffic to be scheduled in the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network.

[0066] From a software perspective, this application also provides a bearer network load balancing device based on core network traffic statistics for executing all or part of the aforementioned bearer network load balancing method based on core network traffic statistics. See [link to relevant documentation]. Figure 3 The aforementioned load balancing device for bearer networks based on core network traffic statistics specifically includes the following components:

[0067] The bearer network traffic composition map construction module 11 is used to construct a bearer network traffic composition map based on the statistical results of forwarding by the core network control plane element SMF. The statistical results are obtained by the core network user plane element UPF performing traffic information statistics on multiple GTP-U tunnels and sending the statistical results to the core network control plane element SMF.

[0068] The load balancing module 12 is used to obtain the traffic to be scheduled to other non-congested links in the currently congested link according to the traffic composition map of the bearer network when link congestion occurs, change the traffic diversion rules on the bearer network access router side and change the path of the traffic to be scheduled in the bearer network to schedule the traffic to be scheduled to other non-congested links, so as to realize the load balancing of the bearer network.

[0069] The embodiment of the bearer network load balancing device based on core network traffic statistics provided in this application can be used to execute the processing flow of the embodiment of the bearer network load balancing method based on core network traffic statistics in the above embodiment. Its function will not be repeated here, but can be referred to the detailed description of the embodiment of the bearer network load balancing method based on core network traffic statistics above.

[0070] This application also provides a load balancing system for a bearer network based on core network traffic statistics, which includes the following:

[0071] The access network element gNB is used to establish a GTP-U tunnel with the core network user plane element UPF through the bearer network.

[0072] The core network user plane element UPF establishes the GTP-U tunnel with the access network element gNB through the bearer network. The core network user plane element UPF is used to execute the bearer network load balancing method based on core network traffic statistics described in the foregoing embodiments.

[0073] The core network control plane element SMF is used to receive statistical results and forward the statistical results to the bearer network controller;

[0074] The bearer network controller is used to execute the bearer network load balancing method based on core network traffic statistics as described in the foregoing embodiments.

[0075] This invention provides a method, apparatus, and system for load balancing of a bearer network based on core network traffic statistics. The method includes: constructing a bearer network traffic composition map based on statistical results forwarded by the core network control plane element SMF, wherein the statistical results are obtained by the core network user plane element UPF performing traffic information statistics on multiple GTP-U tunnels and sending the statistical results to the core network control plane element SMF; when link congestion occurs in the bearer network, obtaining the traffic to be scheduled on the currently congested link for scheduling to other non-congested links according to the bearer network traffic composition map, changing the traffic redirection rules on the bearer network access router side, and changing the path of the traffic to be scheduled through the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network. This invention can achieve data flow granularity identification and load balancing under conditions where the bearer network equipment capacity is limited and the bearer network does not recognize GTP-U packet headers.

[0076] This application also provides an electronic device, such as a central server, which may include a processor, a memory, a receiver, and a transmitter. The processor is used to execute the bearer network load balancing method based on core network traffic statistics mentioned in the above embodiments. The processor and memory can be connected via a bus or other means, taking a bus connection as an example. The receiver can be connected to the processor and memory via wired or wireless means.

[0077] The processor can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or combinations of the above types of chips.

[0078] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs, non-transitory computer-executable programs, and modules, such as the program instructions / modules corresponding to the bearer network load balancing method based on core network traffic statistics in the embodiments of this application. The processor executes various functional applications and data processing by running the non-transitory software programs, instructions, and modules stored in the memory, thereby implementing the image classification model training method based on reinforced federated domain generalization in the above method embodiments.

[0079] The memory may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created by the processor, etc. Furthermore, the memory may include high-speed random access memory and non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include memory remotely located relative to the processor, which can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0080] The one or more modules are stored in the memory, and when executed by the processor, the bearer network load balancing method based on core network traffic statistics in the embodiment is executed.

[0081] In some embodiments of this application, the user equipment may include a processor, a memory, and a transceiver unit. The transceiver unit may include a receiver and a transmitter. The processor, memory, receiver, and transmitter may be connected via a bus system. The memory is used to store computer instructions, and the processor is used to execute the computer instructions stored in the memory to control the transceiver unit to send and receive signals.

[0082] As one implementation method, the functions of the receiver and transmitter in this application can be implemented by transceiver circuits or dedicated transceiver chips, and the processor can be implemented by dedicated processing chips, processing circuits or general-purpose chips.

[0083] As another implementation approach, the server provided in this application embodiment can be implemented using a general-purpose computer. That is, the program code implementing the processor, receiver, and transmitter functions is stored in memory, and the general-purpose processor implements the processor, receiver, and transmitter functions by executing the code in memory.

[0084] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the aforementioned bearer network load balancing method based on core network traffic statistics. The computer-readable storage medium can be a tangible storage medium, such as random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, floppy disks, hard disks, removable storage disks, CD-ROMs, or any other form of storage medium known in the art.

[0085] Those skilled in the art will understand that the exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Whether implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. When implemented in hardware, it can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. The programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave.

[0086] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0087] In this application, features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, and / or combined with or in place of features of other embodiments.

[0088] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to the embodiments of this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A load balancing method for a bearer network based on core network traffic statistics, characterized in that, Performed by the bearer network controller, including: A traffic composition map of the bearer network is constructed based on the statistical results forwarded by the core network control plane element SMF. The statistical results are obtained by the core network user plane element UPF from traffic information statistics of multiple GTP-U tunnels and the statistical results are sent to the core network control plane element SMF. When link congestion occurs in the bearer network, the traffic to be scheduled in the currently congested link is obtained according to the traffic composition map of the bearer network. The traffic diversion rules on the access router side of the bearer network are changed and the path of the traffic to be scheduled in the bearer network is changed so as to schedule the traffic to be scheduled to other non-congested links, thereby realizing load balancing of the bearer network.

2. The bearer network load balancing method based on core network traffic statistics according to claim 1, characterized in that, The GTP-U tunnel is established by the core network user plane element UPF and the access network element gNB through the bearer network.

3. The bearer network load balancing method based on core network traffic statistics according to claim 2, characterized in that, The GTP-U tunnel is established by the core network user plane element UPF and the access network element gNB through the bearer network, including: The core network user plane element UPF selects an IP address from the UPF pool as the tunnel endpoint IP, so that when receiving data packets sent from the access network element gNB, the bearer network access switch directs the data packets to the GTP-U tunnel corresponding to the endpoint IP by identifying the source IP, destination IP and ToS fields of the data packets.

4. The bearer network load balancing method based on core network traffic statistics according to claim 1, characterized in that, The construction of the bearer network traffic composition map based on the statistical results of SMF forwarding in the core network control plane includes: Based on the flow value of each carrier network tunnel and the carrier network tunnel corresponding to that flow value in the statistical results, the flow distribution of different carrier network tunnels in the whole network is obtained, and the carrier network flow composition map is constructed.

5. The bearer network load balancing method based on core network traffic statistics according to claim 1, characterized in that, The step of obtaining the traffic to be scheduled on the currently congested link for other non-congested links based on the traffic composition map of the bearer network, changing the traffic redirection rules on the bearer network access router side, and changing the path of the traffic to be scheduled on the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby achieving load balancing of the bearer network, includes: The scheduling characteristics of the traffic to be scheduled are obtained, a non-congestion path is planned for the traffic to be scheduled, and the scheduling characteristics and the non-congestion path are sent to the switch on the ingress side of the bearer network, so that the switch can identify the data packets in the data plane and encapsulate the matched data for load balancing into a new bearer network tunnel.

6. A load balancing method for a bearer network based on core network traffic statistics, characterized in that, Executed by the core network user plane element UPF, including: Statistical results were obtained by analyzing traffic flow information from multiple GTP-U tunnels; The statistical results are sent to the core network control plane element (SMF), which then forwards the statistical results to the bearer network controller. The bearer network controller then constructs a bearer network traffic composition map based on the statistical results. When link congestion occurs in the bearer network, it uses the bearer network traffic composition map to obtain the traffic to be scheduled on the currently congested link for redirection to other non-congested links. It then modifies the routing rules on the bearer network access router side and changes the path of the traffic to be scheduled through the bearer network to redirect the traffic to other non-congested links, thereby achieving bearer network load balancing.

7. A load balancing device for a bearer network based on core network traffic statistics, characterized in that, include: The bearer network traffic composition map construction module is used to construct a bearer network traffic composition map based on the statistical results of forwarding by the core network control plane network element SMF. The statistical results are obtained by the core network user plane network element UPF performing traffic information statistics on multiple GTP-U tunnels and sending the statistical results to the core network control plane network element SMF. The load balancing module is used to obtain the traffic to be scheduled to other non-congested links in the currently congested link according to the traffic composition map of the bearer network when link congestion occurs, change the traffic diversion rules on the bearer network access router side and change the path of the traffic to be scheduled in the bearer network to schedule the traffic to be scheduled to other non-congested links, thereby realizing load balancing of the bearer network.

8. A load balancing system for a bearer network based on core network traffic statistics, characterized in that, include: The access network element gNB is used to establish a GTP-U tunnel with the core network user plane element UPF through the bearer network. The core network user plane element UPF establishes the GTP-U tunnel with the access network element gNB through the bearer network. The core network user plane element UPF is used to execute the bearer network load balancing method based on core network traffic statistics as described in claim 6. The core network control plane element SMF is used to receive statistical results and forward the statistical results to the bearer network controller; A bearer network controller is used to execute the bearer network load balancing method based on core network traffic statistics as described in any one of claims 1 to 5.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the bearer network load balancing method based on core network traffic statistics as described in any one of claims 1 to 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the bearer network load balancing method based on core network traffic statistics as described in any one of claims 1 to 6.

Images