Service flow forwarding method and network equipment
By configuring the slice sharing bandwidth resource pool at the subinterface layer and dynamically adjusting the bandwidth of network slices, the problem of inflexible bandwidth resource management under the traditional static resource allocation method is solved, and the automated management and maximum utilization of network bandwidth resources are realized.
Patent Information
- Application Number
- CN202411350980.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-26
- Publication Date
- 2025-05-16
AI Technical Summary
In 5G and future networks, with the popularization of network slicing technology and the increase in the number of slicing, the traditional static resource allocation method has led to inflexible bandwidth resource management, making it difficult to meet the dynamic changes in different business needs.
By configuring a slice sharing bandwidth resource pool at the subinterface layer, dynamically adjusting the bandwidth of network slices, and forwarding of service traffic. The specific method includes obtaining the traffic rate of the service traffic, determining whether it exceeds the reserved bandwidth, if it exceeds the reserved bandwidth, applying for shared bandwidth resources to the sliced shared bandwidth resource pool, and sending service traffic based on the acquired shared bandwidth resources and reserved bandwidth.
It realizes dynamic adjustment of network slice bandwidth according to changes in network slice traffic, maximizes network resources, and realizes automated management of network bandwidth resources, avoiding the problems of resource waste and insufficient bandwidth.
Smart Images
Figure CN120018144A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a method and network device for forwarding service traffic. Background Art
[0002] In the development of 5G and future networks, Network-slice, as a key innovative technology, is widely used to provide customized network services.
[0003] like Figure 1 As shown in the figure, slice-id-based network slicing can create independent logical networks for different business needs, and each slice has independent resources and performance guarantees.
[0004] However, with the popularization of network slicing technology and the increase in the number of slices, the traditional static resource allocation method has gradually exposed some problems, such as inflexible bandwidth resource management. Summary of the invention
[0005] In order to overcome the problems existing in the related art, this specification provides a method and network device for forwarding business traffic.
[0006] According to a first aspect of an embodiment of this specification, a method for forwarding service traffic is provided, the method comprising:
[0007] Obtaining a first traffic rate of service traffic in a first slice;
[0008] Determining whether the first traffic rate is greater than a preset reserved bandwidth of the first slice;
[0009] If the first traffic rate is greater than the reserved bandwidth of the first slice, applying for shared bandwidth resources from the slice shared bandwidth resource pool of the sub-interface layer;
[0010] The service traffic is sent according to the acquired shared bandwidth resources and the reserved bandwidth.
[0011] Wherein, the method further comprises:
[0012] Configure slice shared bandwidth resource pool at the sub-interface layer.
[0013] The configuring of the slice shared bandwidth resource pool at the sub-interface layer includes:
[0014] Obtain physical bandwidth resources, and obtain a slice shared bandwidth resource pool from the physical bandwidth resources in proportion; or, obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidth of each slice.
[0015] The step of applying for shared bandwidth resources from a slice shared bandwidth resource pool at the sub-interface layer includes:
[0016] Send a request for shared bandwidth resources to the slice shared bandwidth resource pool;
[0017] The slice shared bandwidth resource pool sends shared bandwidth resources to the first slice according to the application request.
[0018] Wherein, the method further comprises:
[0019] After receiving the application request, the slice shared bandwidth resource pool determines whether the allocated shared bandwidth resources have reached a threshold;
[0020] If the threshold is reached, the remaining shared bandwidth resources are evenly divided according to the number of slices, and the evenly divided shared bandwidth resources are sent to the first slice.
[0021] Among them, if the first traffic rate is not greater than the reserved bandwidth of the first slice, the service traffic is sent according to the reserved bandwidth of the first slice.
[0022] It can be seen from the above embodiments that when the business traffic of a slice is greater than the reserved bandwidth, the slice can apply to the sub-interface layer for shared bandwidth resources for forwarding business traffic, thereby dynamically adjusting the bandwidth of the network slice according to changes in the network slice traffic, maximizing the use of network resources, and realizing automated management of network bandwidth resources.
[0023] According to a second aspect of an embodiment of this specification, a network device is provided, the network device comprising:
[0024] An acquisition module, used to acquire a first traffic rate of a service traffic in a first slice;
[0025] A judging module, configured to judge whether the first traffic rate is greater than a preset reserved bandwidth of the first slice;
[0026] A processing module is used to apply for shared bandwidth resources from a slice shared bandwidth resource pool of a sub-interface layer when the first traffic rate is greater than the reserved bandwidth of the first slice, and to send the service traffic according to the acquired shared bandwidth resources and the reserved bandwidth.
[0027] Wherein, the network device further includes:
[0028] The configuration module is used to configure the slice shared bandwidth resource pool at the sub-interface layer.
[0029] Among them, the configuration module is also used to obtain physical bandwidth resources, and obtain a slice shared bandwidth resource pool from the physical bandwidth resources in proportion; or, obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidth of each slice.
[0030] The processing module is specifically used to send an application request for shared bandwidth resources to a slice shared bandwidth resource pool, and the slice shared bandwidth resource pool sends shared bandwidth resources to the first slice according to the application request.
[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present specification. BRIEF DESCRIPTION OF THE DRAWINGS
[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the specification and, together with the description, serve to explain the principles of the specification.
[0033] Figure 1 This is a topological diagram of a network slice shown in this specification according to an exemplary embodiment.
[0034] Figure 2 It is a flowchart of a method for forwarding business traffic according to an exemplary embodiment of this specification.
[0035] Figure 3 This is a topological diagram of a network slice shown in this specification according to an exemplary embodiment. DETAILED DESCRIPTION
[0036] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with this specification. Instead, they are merely examples of devices and methods consistent with some aspects of this specification as detailed in the appended claims.
[0037] The terms used in this specification are for the purpose of describing specific embodiments only and are not intended to limit this specification. The singular forms "a", "the" and "the" used in this specification and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.
[0038] It should be understood that although the terms first, second, third, etc. may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this specification, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".
[0039] like Figure 1 The topology diagram of the network slice shown in the figure shows that in the implementation of slice-id-based network slicing, in order to ensure the service quality and performance of each slice, a bandwidth static reservation allocation method is usually adopted, that is, a fixed bandwidth is allocated to each slice in advance. In order to ensure that the traffic between slices does not affect each other, a group of TM queues will be allocated to each slice in the implementation, and the speed limit value of the slice will be bound to the queue. If the reserved bandwidth of slice slice 1 is 5Gbps and the reserved bandwidth of slice slice 2 is 6Gbps, when the service traffic rate of slice 1 is 6Gbps and the service traffic rate of slice 2 is 4Gbps, the service traffic on slice 1 will be lost due to insufficient bandwidth, and finally it can be forwarded through 5Gbps according to the bandwidth. Especially in multi-tenant and large-scale application scenarios, the service requirements of different slices have highly time-varying and uncertain characteristics. At certain times, some slices may have excess resources, while other slices may face resource shortages.
[0040] In order to solve the above technical problems, the present disclosure provides a method for forwarding business traffic, such as Figure 2 As shown, the method includes:
[0041] S201 obtains a first traffic rate of a service traffic in a first slice;
[0042] S202: Determine whether the first traffic rate is greater than a preset reserved bandwidth of the first slice;
[0043] S203: If the first traffic rate is greater than the reserved bandwidth of the first slice, apply for shared bandwidth resources from the slice shared bandwidth resource pool of the sub-interface layer;
[0044] S204 sends the service traffic according to the acquired shared bandwidth resources and reserved bandwidth.
[0045] In this embodiment, the administrator can pre-configure the sub-interface layer (such as Figure 1The slice shared bandwidth resource pool is configured at the L1 layer in the sub-interface layer. The slice shared bandwidth resource pool can obtain the slice shared bandwidth resource pool from the physical bandwidth resources in proportion by obtaining the physical bandwidth resources, or obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidths of each slice.
[0046] For example, assuming that the total physical bandwidth is 100G, and the proportion of the slice shared bandwidth resource pool is set to 80%, the slice shared bandwidth resource pool finally obtained is 80G. For another example, assuming that the sum of the preset reserved bandwidths of each slice under the sub-interface layer is 80G, and the physical bandwidth is 100G, at this time, it is determined that the sum of the preset reserved bandwidths of each slice is less than the physical bandwidth, then the sum of the preset reserved bandwidths of each slice 80G can be used as the shared bandwidth resource pool.
[0047] In actual application, the reserved bandwidth preset for each slice can be determined according to the service priority of each slice. For example, a high-priority slice can be allocated a higher reserved bandwidth, while a low-priority slice can be allocated a lower reserved bandwidth. In this embodiment, the reserved bandwidth can be understood as a guaranteed bandwidth, that is, it can guarantee the minimum bandwidth requirement of each slice service.
[0048] In this embodiment, the queue speed limit (shaper) of each slice can adopt the commit mode.
[0049] like Figure 3 As shown, assuming that the shared bandwidth resource pool configured at the L1 layer is 80G, the topology includes slice 1 (Slice1) and slice 2 (Slice2), wherein the reserved bandwidth of slice 1 is 5G, and the reserved bandwidth of slice 2 is 6G.
[0050] Assume that slice 1 needs to forward 6G of business traffic (i.e., the first traffic), but the reserved bandwidth of slice 1 is only 5G. At this time, slice 1 can apply for shared bandwidth resources from the slice shared bandwidth resource pool at the sub-interface layer. The slice shared bandwidth resource pool can allocate 1G of bandwidth to slice 1 from the slice shared bandwidth resource pool according to the request of slice 1. After that, slice 1 can send 6G of business traffic.
[0051] In another embodiment, assuming that the business traffic sent by slice 2 at this time is 4G, and the reserved bandwidth of slice 2 is 6G, it means that slice 2 has 2G bandwidth resources that are not used. At this time, after receiving the request of slice 1, the slice shared bandwidth resource pool can allocate the 2G unused bandwidth resources of slice 2 to slice 1, thereby avoiding the problem of resource waste caused by excessive reserved bandwidth.
[0052] In this embodiment, after the slice shared bandwidth resource pool allocates shared bandwidth resources to the slice, it can make an allocation record. The record can be presented in the form of a table item, which can include the allocated slice information and the allocated shared bandwidth resource status. The slice resources can be subsequently managed according to the table item. For example, assuming that it is found through the record that slice 1 sends resource application requests to the slice shared bandwidth resource pool multiple times within a period, one situation may indicate that the preset bandwidth of slice 1 is too small, and the administrator can adjust the preset bandwidth of slice 1. Another situation may indicate that slice 1 is likely to be attacked by traffic.
[0053] In this embodiment, when the slice shared bandwidth resource pool receives a request for shared bandwidth resources sent by the slice, it can determine whether the remaining resources of the slice shared bandwidth resource pool have reached a preset threshold, which can be 80% of the total resources of the slice shared bandwidth resource pool (the actual proportion can be set according to network requirements). When the preset threshold is not reached, it can be processed according to the above steps. When the preset threshold is reached, the remaining shared resources can be proportionally divided and the divided resources can be allocated to the slices.
[0054] It can be seen from the above embodiments that by configuring a slice shared bandwidth resource pool, there is no need to statically allocate bandwidth resources to each slice in the existing manner. Instead, a preset resource can be set for each slice (the preset resource can be determined according to the priority of the slice). When the slice forwards traffic, if it is found that the reserved bandwidth is insufficient, the slice shared bandwidth resource pool can be applied for shared bandwidth resources at any time, thereby realizing dynamic adjustment of the network slice bandwidth according to the actual traffic load, that is, the bandwidth of the network slice can be dynamically adjusted according to the change of the network slice traffic, the network resources can be maximized, and the automatic management of network bandwidth resources can be realized.
[0055] Based on the above method embodiments, the present disclosure further provides a network device, the network device comprising:
[0056] An acquisition module, used to acquire a first traffic rate of a service traffic in a first slice;
[0057] A judging module, configured to judge whether the first traffic rate is greater than a preset reserved bandwidth of the first slice;
[0058] A processing module is used to apply for shared bandwidth resources from a slice shared bandwidth resource pool of a sub-interface layer when the first traffic rate is greater than the reserved bandwidth of the first slice, and to send the service traffic according to the acquired shared bandwidth resources and the reserved bandwidth.
[0059] Wherein, the network device further includes:
[0060] The configuration module is used to configure the slice shared bandwidth resource pool at the sub-interface layer.
[0061] Among them, the configuration module is also used to obtain physical bandwidth resources, and obtain a slice shared bandwidth resource pool from the physical bandwidth resources in proportion; or, obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidth of each slice.
[0062] The processing module is specifically used to send an application request for shared bandwidth resources to a slice shared bandwidth resource pool, and the slice shared bandwidth resource pool sends shared bandwidth resources to the first slice according to the application request.
[0063] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.
[0064] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0065] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention claimed herein. The specification is intended to cover any variations, uses or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not claimed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.
[0066] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.
[0067] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.
Claims
1. A method for forwarding service traffic, characterized in that: The method comprises: Obtaining a first traffic rate of service traffic in a first slice; Determining whether the first traffic rate is greater than a preset reserved bandwidth of the first slice; If the first traffic rate is greater than the reserved bandwidth of the first slice, applying for shared bandwidth resources from the slice shared bandwidth resource pool of the sub-interface layer; The service traffic is sent according to the acquired shared bandwidth resources and the reserved bandwidth.
2. The method according to claim 1, characterized in that The method further comprises: Configure slice shared bandwidth resource pool at the sub-interface layer.
3. The method according to claim 2, characterized in that The configuring of the slice shared bandwidth resource pool at the sub-interface layer includes: Obtain physical bandwidth resources, and obtain a slice shared bandwidth resource pool from the physical bandwidth resources in proportion; or, obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidth of each slice.
4. The method according to claim 1, characterized in that The step of applying for shared bandwidth resources from a slice shared bandwidth resource pool at the sub-interface layer includes: Send a request for shared bandwidth resources to the slice shared bandwidth resource pool; The slice shared bandwidth resource pool sends shared bandwidth resources to the first slice according to the application request.
5. The method according to claim 4, characterized in that The method further comprises: After receiving the application request, the slice shared bandwidth resource pool determines whether the allocated shared bandwidth resources have reached a threshold; If the threshold is reached, the remaining shared bandwidth resources are evenly divided according to the number of slices, and the evenly divided shared bandwidth resources are sent to the first slice.
6. The method according to claim 4, characterized in that If the first traffic rate is not greater than the reserved bandwidth of the first slice, the service traffic is sent according to the reserved bandwidth of the first slice.
7. A network device, characterized in that: The network equipment includes: An acquisition module, used to acquire a first traffic rate of a service traffic in a first slice; A judging module, configured to judge whether the first traffic rate is greater than a preset reserved bandwidth of the first slice; A processing module is used to apply for shared bandwidth resources from a slice shared bandwidth resource pool of a sub-interface layer when the first traffic rate is greater than the reserved bandwidth of the first slice, and to send the service traffic according to the acquired shared bandwidth resources and the reserved bandwidth.
8. The network device according to claim 7, characterized in that: The network device also includes: The configuration module is used to configure the slice shared bandwidth resource pool at the sub-interface layer.
9. The network device according to claim 8, characterized in that: The configuration module is also used to obtain physical bandwidth resources and obtain a slice shared bandwidth resource pool from the physical bandwidth resources in proportion; or, obtain the preset reserved bandwidth of each slice under the sub-interface layer, and determine the slice shared bandwidth resource pool according to the sum of the preset reserved bandwidth of each slice.
10. The network device according to claim 7, characterized in that: The processing module is specifically used to send an application request for shared bandwidth resources to a slice shared bandwidth resource pool, and the slice shared bandwidth resource pool sends shared bandwidth resources to the first slice according to the application request.