Network slice implementation method, system, device and readable storage medium

Abstract

The application discloses a network slice implementation method, system, device and readable storage medium. The method comprises the following steps: creating a plurality of slice channels at a physical port, and establishing a mapping relationship between each slice channel and a channelized sub-interface expected to be created by a user; configuring a committed bandwidth value and a peak bandwidth value of each slice channel in response to a bandwidth of each expected channelized sub-interface configured by the user; establishing a member group based on each slice channel, and performing traffic scheduling on a Qos queue in each member group based on a preset scheduling algorithm. Compared with the prior art, the application does not change the operation of the user side, directly creates a slice channel on the physical port, and performs the function of the channelized sub-interface. The method can realize the function of the network slice based on only secondary scheduling, thereby reducing the scheduling cost. Meanwhile, the application can be applied to an aggregation port, so that the aggregation port has the network slice characteristic. Therefore, the scheme has stronger adaptability and can be dynamically adjusted based on the load condition in the use scene.

Description

Technical Field

[0001] The present invention belongs to the field of network communication technology, and specifically relates to a network slicing implementation method, system, device and readable storage medium. Background Art

[0002] Network slicing resource reservation technology is key to providing differentiated SLA guarantees in network slicing solutions. This technology divides the forwarding resources in the physical network into multiple, isolated resources, each allocated to different network slices. This ensures that sufficient resources are available within the network slice to meet service needs while also preventing or controlling resource contention and preemption between different network slices. Common resource reservation technologies used in network slicing solutions include FlexE interfaces, channelized sub-interfaces, and slice channels.

[0003] The current network slicing queue model implements channelized sub-interfaces, slice channels, and QoS queues by multiplexing HQoS technology (at least three levels of scheduling). FlexE interfaces rely on hardware ports that support FlexE features, while channelized sub-interfaces and slice channels rely on chipsets that support HQoS. This places high demands on hardware and increases the cost of feature support.

[0004] Furthermore, if physical ports are aggregated into an aggregate port, a scheduling policy for the aggregate port to each physical port must be added, further increasing the scheduling burden on the hardware. Therefore, the usability of network slicing for aggregate ports in existing technologies is relatively poor. Due to hardware limitations, aggregate ports generally do not support network slicing.

[0005] In response to the above technical problems, it is necessary to provide an improved network slicing implementation strategy.

[0006] The information disclosed in this background technology section is only intended to enhance understanding of the overall background of the invention and should not be regarded as an admission or any form of suggestion that the information constitutes the prior art already known to a person skilled in the art. Summary of the Invention

[0007] The purpose of the present invention is to provide a network slicing implementation method, system, device and readable storage medium, which can simplify QoS scheduling, reduce the cost of network slicing solutions and improve the adaptability of the solutions without changing the user experience.

[0008] In order to achieve the above object, a specific embodiment of the present invention provides the following technical solutions:

[0009] In a first aspect, the present invention provides a method for implementing network slicing, comprising:

[0010] Creating multiple slice channels on the physical port and establishing a mapping relationship between each slice channel and the channelized sub-interface that the user wants to create;

[0011] In response to the expected bandwidth of each channelized sub-interface configured by the user, configuring a committed bandwidth value and a peak bandwidth value of each slice channel;

[0012] A member group is established based on each slice channel, and traffic scheduling is performed on the Qos queues in each member group based on a preset scheduling algorithm.

[0013] In one or more embodiments of the present invention, the method further comprises:

[0014] The committed bandwidth value of the slice channel is less than or equal to the peak bandwidth value of the same slice channel;

[0015] The sum of the peak bandwidth values ​​of the slice channels corresponding to the expected channelized sub-interface is equal to the expected channelized sub-interface bandwidth.

[0016] In one or more embodiments of the present invention, the method further comprises:

[0017] Select a network layer interface from the slice channel corresponding to the desired channelized sub-interface;

[0018] Calculating the sum of the peak bandwidths of the slice channels of the non-network layer interface corresponding to the desired channelized sub-interface;

[0019] The peak bandwidth value of the network layer interface is configured as the difference between the bandwidth value of the expected channelized sub-interface and the sum.

[0020] In one or more embodiments of the present invention, the method further comprises:

[0021] If the physical ports are aggregated into an aggregation port, then the bandwidth weight of each physical port under the aggregation port is obtained;

[0022] In response to the channelized sub-interface bandwidth configured by the user, based on the bandwidth weight of the physical port, calculate the expected channelized sub-interface bandwidth of each physical port configured under the aggregation port;

[0023] Based on the expected channelized sub-interface bandwidth of each physical port, the committed bandwidth value and the peak bandwidth value of each slice channel are configured.

[0024] In one or more embodiments of the present invention, configuring the committed bandwidth value and the peak bandwidth value of each slice channel includes:

[0025] Based on the committed bandwidth value and peak bandwidth value of the slice channel corresponding to the expected channelized sub-interface under the user-configured aggregation port, and the weights of each physical port aggregated on the aggregation port, the committed bandwidth value and peak bandwidth value of each slice channel are configured.

[0026] In one or more embodiments of the present invention, configuring the committed bandwidth value and the peak bandwidth value of each slice channel includes:

[0027] Based on the committed bandwidth value of the slice channel corresponding to the desired channelized sub-interface under the aggregation port configured by the user, and the weight of each physical port of the aggregation and the aggregation port, the committed bandwidth value of each slice channel is configured;

[0028] The peak bandwidth of the slice channel corresponding to the desired channelized sub-interface under the user-configured aggregation port is used as the peak bandwidth of each slice channel.

[0029] In one or more embodiments of the present invention, the preset scheduling algorithm is a weighted deficit round-robin scheduling algorithm.

[0030] In a second aspect, the present invention provides a network slicing implementation system, comprising:

[0031] A creation module, configured to create multiple slice channels on a physical port and establish a mapping relationship between each slice channel and a channelized sub-interface that the user desires to create;

[0032] a configuration module, configured to configure a committed bandwidth value and a peak bandwidth value of each slice channel in response to each expected channelized sub-interface bandwidth configured by a user;

[0033] The scheduling module is used to establish member groups based on each slice channel and perform traffic scheduling on the Qos queues in each member group based on a preset scheduling algorithm.

[0034] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, wherein the memory and the processor are communicatively connected to each other, computer instructions are stored in the memory, and the processor executes the network slicing implementation method by executing the computer instructions.

[0035] In a fourth aspect, the present invention provides a computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute the network slicing implementation method.

[0036] Compared with the prior art, the network slicing implementation method provided by the present invention does not change the operation on the user side. Based on the channelized sub-interface bandwidth configured by the user, the queue model is configured to the chip through software, and a slice channel is directly created on the physical port. Since there is a mapping relationship between the slice channel and the desired channelized sub-interface, the function of the channelized sub-interface can be replaced by setting the committed bandwidth value and the peak bandwidth value. The network slicing implementation method provided by the present invention can realize the function of network slicing based only on secondary scheduling, reducing the scheduling cost. Furthermore, the present invention can be applied to aggregated ports to give them network slicing characteristics. At the same time, by improving the configuration logic of the peak bandwidth value of the slice channel, the solution has stronger adaptability and can be dynamically adjusted based on the load conditions in the actual usage scenario. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0038] Figure 1 1 is a schematic diagram of the transmission process of a slice message in one embodiment of the present invention;

[0039] Figure 2 1 is a flow chart of a method for implementing network slicing in one embodiment of the present invention;

[0040] Figure 3 This is a structural block diagram of a network slicing implementation system in one embodiment of the present invention;

[0041] Figure 4 It is a structural block diagram of an electronic device in one embodiment of the present invention. DETAILED DESCRIPTION

[0042] In order to enable those skilled in the art to better understand the technical solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0043] Unless expressly stated otherwise, throughout the specification and claims, the term "comprise" or variations such as "include" or "comprising", etc., will be understood to include the stated elements or components but not to exclude other elements or other components.

[0044] In one technical solution, there is a method for implementing network slicing, such as Figure 1 The figure shows the transmission process of sliced ​​packets in a specific embodiment of this technical solution. Sliced ​​packets first enter a QoS queue and undergo QoS queue shaping based on a preset scheduling algorithm. Each shaped QoS queue is then dispatched to a channelized sub-interface as a member of the corresponding member group of the slice channel. After shaping, the channelized sub-interface sends the sliced ​​packets in sequence to the physical port and performs port shaping.

[0045] As can be seen, this technical solution employs a multi-level network slicing queue model, requiring traffic scheduling at each level. This includes scheduling from physical interfaces to channelized sub-interfaces, scheduling from channelized sub-interfaces to sliced ​​channels, and scheduling from sliced ​​channels to QoS queues. For aggregated ports, this also involves scheduling from aggregated ports to physical ports. Therefore, this technical solution inevitably imposes high hardware requirements and high scheduling costs.

[0046] The inventors of this invention identified the major shortcomings of existing technologies and proposed a novel implementation strategy based on these shortcomings: by using the CPU to calculate bandwidth based on the conventional QoS characteristics of the chip, using sliced ​​channels to replace the functions of channelized sub-interfaces, thus reducing the scheduling hierarchy. By combining software and hardware, network slicing functionality is packaged together, significantly increasing the universality of network slicing solutions without compromising user experience.

[0047] Please refer to Figure 2 FIG2 is a flow chart of a method for implementing network slicing according to an embodiment of the present invention. The method for implementing network slicing specifically includes the following steps:

[0048] S201: Create multiple slice channels on a physical port, and establish a mapping relationship between each slice channel and a channelized sub-interface that the user desires to create;

[0049] It should be noted that network slicing is a new network architecture that provides multiple logical networks on a shared network infrastructure, each serving a specific business type or industry user. Each network slice can flexibly define its own logical topology, SLA requirements, reliability, and security levels to meet the differentiated needs of different businesses, industries, or users.

[0050] Network slicing resource reservation technology is key to providing differentiated SLA guarantees in network slicing solutions. Common resource reservation technologies used in network slicing solutions include, but are not limited to, Flex channels and channelized sub-interfaces.

[0051] A channelized sub-interface is a sub-interface of a channelized Ethernet physical port. By using different channelized sub-interfaces to carry different types of services and configuring bandwidth based on the channelized sub-interfaces, bandwidth between different channelized sub-interfaces on the same physical interface is strictly isolated, eliminating the problem of services competing for bandwidth between different sub-interfaces. Compared to channelized sub-interfaces, Flex-channel has no sub-interface model and is simpler to configure. Flex-channel supports M-level bandwidth allocation granularity, meeting the bandwidth requirements of enterprise users and making it more suitable for scenarios where network slices can be quickly created on demand.

[0052] In one technical solution, Flex-channel is used in conjunction with channelized sub-interfaces. Channelized sub-interfaces can be used to provide larger-scale slice resource reservations for specific industries or business types. Flex-channels can then be used within these industry or business type slices to allocate finer-grained slice resources for different enterprise users. Through hierarchically scheduled network slicing, flexible and refined resource management is achieved.

[0053] It is understandable that the function of the channelized sub-interface will cause more load pressure during the implementation process. Therefore, in order to simplify the load pressure of traffic scheduling in the network slice, the solution's high dependence on multi-level QoS scheduling is reduced. In one embodiment of the present invention, in order to maintain the user experience on the user side, the user still sets the expected channelized sub-interface bandwidth. However, in fact, the channelized sub-interface is cancelled, and the slice channel is directly set on the physical port. The channelized sub-interface function is packaged out by software to realize the network slicing function. On the other hand, in order to maintain the network slicing function without being affected, a mapping relationship between each of the slice channels and the channelized sub-interface that the user expects to create can be established.

[0054] It is understood that users can configure multiple channelized sub-interfaces, and the same channelized sub-interface can correspond to one or more slice channels. Therefore, the mapping relationship between the aforementioned slice channels and the channelized sub-interfaces that users want to create is the prerequisite for implementing the channelized sub-interface function.

[0055] S202: In response to the expected channelized sub-interface bandwidth configured by the user, configure the committed bandwidth value and the peak bandwidth value of each slice channel;

[0056] In network slicing, channelized sub-interfaces ensure exclusive bandwidth, preventing bandwidth preemption. Sliced ​​channels directly connected to physical ports can be allocated exclusive bandwidth by setting committed and peak bandwidth values.

[0057] The committed information rate (CIR) refers to the rate at which packets can be transmitted per second, which is also the minimum bandwidth maintained by the corresponding interface. The peak information rate (PIR) refers to the maximum rate at which packets can be transmitted or forwarded.

[0058] Specifically, in an embodiment of the present invention, the slice channel bandwidth is configured through the QoS Shape function, and the following multiple bandwidth modes can be combined through the committed bandwidth value and peak bandwidth value parameters of QoSShape. First, if the committed bandwidth value is 0, the bandwidth of the slice channel can be shared, following the "first come, first served" principle, and the value of the shared bandwidth is the value of the peak bandwidth; second, if the committed bandwidth value is equal to the peak bandwidth value, the bandwidth of the slice channel is exclusive to itself, and no one else is allowed to use it even if there is surplus bandwidth. The size of the exclusive bandwidth is equal to the value of the committed bandwidth or the peak bandwidth at this time; third, if the committed bandwidth value and the peak bandwidth value are both not 0, and the committed bandwidth value is less than the peak bandwidth value, then the bandwidth of the committed bandwidth value is exclusive to the slice channel, and the bandwidth of the difference between the peak bandwidth value and the committed bandwidth value is the shared bandwidth.

[0059] Preferably, in order to realize the function of the channelized sub-interface expected by the user and retain part of the shared bandwidth while maintaining exclusive bandwidth, in one embodiment of the present invention, the committed bandwidth value of the slice channel is less than or equal to the peak bandwidth value of the same slice channel; the sum of the peak bandwidth values ​​of each slice channel corresponding to the expected channelized sub-interface is equal to the bandwidth of the expected channelized sub-interface.

[0060] For example, the maximum bandwidth value of the physical port is 30G, the user configures the bandwidth value of channelized sub-interface 1 to be 10G, and the bandwidth value of channelized sub-interface 2 to be 15G. A total of 4 slice channels are created on the physical port side to perform the functions of the channelized sub-interface. The mapping relationship is established as slice channel 1 and slice channel 2 corresponding to the desired channelized sub-interface 1; slice channel 3 and slice channel 4 correspond to the desired channelized sub-interface 2. Based on the above-mentioned exclusive bandwidth function implementation, when defining slice channel 1 and slice channel 2, it is necessary to ensure that the sum of the corresponding peak bandwidths is equal to 10G (the bandwidth value of channelized sub-interface 1); slice channel 3 and slice channel 4 must ensure that the sum of the corresponding peak bandwidths is equal to 15G (the bandwidth value of channelized sub-interface 2).

[0061] It is understandable that the bandwidth configuration of the slice channel can be set based on the user end, or it can be evenly distributed or weighted based on a preset algorithm through software. The embodiment of the present invention does not limit this.

[0062] It should be noted that the technical solution of the present invention also includes: selecting a network layer interface from the slice channel corresponding to the expected channelized sub-interface; calculating the sum of the peak bandwidths of the slice channels of the non-network layer interfaces corresponding to the expected channelized sub-interface; and configuring the peak bandwidth value of the network layer interface to be the difference between the bandwidth value of the expected channelized sub-interface and the sum.

[0063] When the user terminal configures the bandwidth of the slice channels one by one, it is possible that the sum of the peak bandwidths of the final slice channels is less than the bandwidth of the channelized sub-interface. At this time, since the maximum transmission rate of the slice channel is the corresponding peak bandwidth during data transmission, part of the bandwidth of the channel sub-interface is wasted. Therefore, the present invention adopts the technical solution described in the above embodiment to pre-select the corresponding network layer interface. The user terminal does not participate in the bandwidth configuration of the slice channel corresponding to the network layer interface. After the bandwidth configuration of other slice channels is completed, the peak bandwidth of the slice channel corresponding to the network layer interface is configured based on the remaining bandwidth value of the expected channelized sub-interface.

[0064] For example, following the above specific embodiment, for the desired channelized sub-interface 1, slice channel 2 is selected as the network layer interface. The user terminal then only needs to configure the bandwidth value of slice channel 1. If the peak bandwidth of slice channel 1 is configured to 7G, the software will set the peak bandwidth of slice channel 2, corresponding to the network layer interface, to 3G to ensure that the bandwidth value of the desired channelized sub-interface 1 is not wasted.

[0065] S203: Establish member groups based on each slice channel, and perform traffic scheduling on the Qos queues in each member group based on a preset scheduling algorithm.

[0066] It is understandable that each slice channel will contain multiple Qos queues. In the chip, the slice channel corresponds to a member group, and the Qos queue is a member of the corresponding member group. The method of traffic scheduling for the Qos queues in each of the member groups may include but is not limited to: strict priority scheduling (Strict Priority), round-robin scheduling (Round Robin), weighted round-robin scheduling (Weighted Round Robin), etc. The embodiment of the present invention does not limit the choice of scheduling method. The scheduling algorithm can be selected based on the needs of the specific implementation scenario. In order to further simplify the implementation method of the network slicing solution, it is preferred to adopt the weighted deficit round-robin scheduling algorithm (Weighted Deficit Round Robin).

[0067] The use of link aggregation technology in existing technologies results in the addition of a new level of scheduling, namely the scheduling process from the aggregated port to the physical port, which makes the implementation process of network slicing become at least four levels of traffic scheduling, which is too complicated and difficult to apply. Therefore, in another embodiment of the present invention, the network slicing implementation method provided by the present invention can be further applied to the aggregated port (Linkagg port).

[0068] It's important to note that link aggregation technology increases link bandwidth by bundling multiple physical interfaces into a single logical interface without requiring hardware upgrades. While increasing device bandwidth, link aggregation also utilizes a backup link mechanism to effectively improve link reliability between devices, enhance network availability, and facilitate load balancing. The bandwidth of physical ports aggregated into the same LinkAg port is fixed.

[0069] In an exemplary embodiment, if the physical ports are aggregated into an aggregation port, the bandwidth weights of the physical ports under the aggregation port are obtained; in response to the channelized sub-interface bandwidth configured by the user, the expected channelized sub-interface bandwidth of each physical port configured under the aggregation port is calculated based on the bandwidth weight of the physical port; based on the expected channelized sub-interface bandwidth of each physical port, the committed bandwidth value and peak bandwidth value of each slice channel are configured.

[0070] It should be noted that the LinkAgg port bandwidth is equal to the total bandwidth of all UP physical interfaces under the LinkAgg port. When setting the channelized sub-interface bandwidth, sliced ​​channel bandwidth, and QoS queue bandwidth for a LinkAgg port, you can also switch to the CPU to calculate the bandwidth based on the weight of the UP member interfaces, and then configure the channelized sub-interface bandwidth, sliced ​​channel bandwidth, and QoS queue bandwidth for each UP member interface.

[0071] For example, in one embodiment, four physical ports are aggregated into the Linkagg interface: physical port 1, physical port 2, physical port 3, and physical port 4. The bandwidth of each physical port is 10G, with a weight ratio of 1:1:2:1. Before configuring the bandwidth of each desired channelized sub-interface, the status of each port must be determined. Physical ports in the DOWN state are ignored, and subsequent bandwidth allocation operations are performed only on ports in the UP state. If physical port 4 is in the DOWN state, bandwidth configuration is performed only on physical ports 1, 2, and 3.

[0072] Specifically, in order to cope with various implementation scenarios, the present invention provides two different expected channelized sub-interface bandwidth configuration strategies.

[0073] In an exemplary embodiment, the committed bandwidth value and peak bandwidth value of each slice channel are configured based on the committed bandwidth value and peak bandwidth value of the slice channel corresponding to the desired channelized sub-interface under the user-configured aggregation port, and the weights of each physical port aggregated on the aggregation port.

[0074] Continuing with the previous specific embodiment, the bandwidth configuration on the user side specifically includes: configuring a channelized sub-interface with a bandwidth of 20G; a slice channel 1 with a committed bandwidth value of 6G and a peak bandwidth value of 6G; and a slice channel 2 with a committed bandwidth value of 4G and a peak bandwidth value of 10G. It is understandable that the user terminal side is not aware of the status of each physical port under the corresponding aggregation port. After configuring a desired channelized sub-interface and the corresponding slice channel 1 and slice channel 2, it means that each physical port aggregated under the aggregation port creates a slice channel 1 and slice channel 2 corresponding to the desired channelized sub-interface.

[0075] Since the weight ratio of the physical ports in the UP state is 1:1:2, the peak bandwidth of the expected channelized sub-interface on each physical port is allocated based on the weight of the channelized sub-interface bandwidth on the aggregation port set by the user, which are 5G, 5G, and 10G respectively. Furthermore, the slice channel on each physical port is allocated the committed bandwidth value and peak bandwidth value of the slice channel configured by the user based on the weight of the physical port. Taking physical port 1 as an example, slice channel 1 with a committed bandwidth of 1.5G and a peak bandwidth of 1.5G and slice channel 2 with a committed bandwidth of 1G and a peak bandwidth of 2.5G are created on it.

[0076] Based on this implementation, network slicing is implemented under the aggregated port, and the bandwidth value is split according to the weight ratio of the physical port. It is suitable for scenarios with uniform traffic, and the bandwidth of the slice channel can be guaranteed according to the configuration.

[0077] It should be noted that the above embodiment may not guarantee the bandwidth of the slice channel when the Linkagg port is unevenly loaded. For example, when all traffic corresponding to slice channel 1 of the aggregation port is polarized only from physical port 1, the actual bandwidth of slice channel 1 is consistent with the bandwidth of slice channel 1 corresponding to physical port 1, becoming Cir = 1.5G, Pir = 1.5G, which is inconsistent with the user's expected Cir = 6G, Pir = 6G. Therefore, in order to cope with the use scenario of uneven load, the embodiment of the present invention proposes another implementation method as follows.

[0078] In another exemplary embodiment, the committed bandwidth value of each slice channel is configured based on the committed bandwidth value of the slice channel corresponding to the expected channelized sub-interface under the user-configured aggregation port, and the weights of the aggregation and each physical port of the aggregation port; the peak bandwidth value of the slice channel corresponding to the expected channelized sub-interface under the user-configured aggregation port is used as the peak bandwidth value of each corresponding slice channel.

[0079] This embodiment still uses the method of splitting bandwidth based on weights and then configuring committed bandwidth. However, for peak bandwidth, this implementation method directly issues it according to the user-configured value, that is, it allows over-allocation.

[0080] In the above specific embodiment, if this implementation is adopted, the peak bandwidth of the expected channelized sub-interface corresponding to each physical port is 20G. Furthermore, taking physical port 1 as an example, the peak bandwidth of slice channel 1 created on it is 6G, and the committed bandwidth is 1.5G; the peak bandwidth of slice channel 2 is 10G, and the committed bandwidth is 1G. At this time, even if the traffic of the slice channel is fully polarized, the user's bandwidth can still be guaranteed, avoiding data transmission congestion, data loss and other problems. It can be seen that this solution is suitable for scenarios with uneven traffic.

[0081] Please refer to Figure 3 As shown, based on the same inventive concept as the aforementioned network slicing implementation method, an embodiment of the present invention provides a network slicing implementation system 300, which includes: a creation module 301, a configuration module 302, and a scheduling module 303.

[0082] Specifically, the creation module 301 is used to create multiple slice channels on the physical port and establish a mapping relationship between each slice channel and the channelized sub-interface that the user expects to create; the configuration module 302 is used to configure the committed bandwidth value and peak bandwidth value of each slice channel in response to the bandwidth of each expected channelized sub-interface configured by the user; the scheduling module 303 is used to establish a member group based on each slice channel, and perform traffic scheduling on the Qos queues in each member group based on a preset scheduling algorithm.

[0083] Please refer to Figure 4 As shown, an embodiment of the present invention further provides an electronic device 400, which includes at least one processor 401, a memory 402 (for example, a non-volatile memory), a storage 403, and a communication interface 404, and the at least one processor 401, the memory 402, the storage 403, and the communication interface 404 are connected together via an internal bus 405. The at least one processor 401 is used to call at least one program instruction stored or encoded in the memory 402, so that the at least one processor 401 performs various operations and functions of the network slicing implementation method described in various embodiments of this specification.

[0084] In the embodiments of the present specification, the electronic device 400 may include but is not limited to: a personal computer, a server computer, a workstation, a desktop computer, a laptop computer, a notebook computer, a mobile electronic device, a smart phone, a tablet computer, a cellular phone, a personal digital assistant (PDA), a handheld device, a messaging device, a wearable electronic device, a consumer electronic device, and the like.

[0085] An embodiment of the present invention also provides a computer-readable medium, which carries computer-executable instructions. When the computer-executable instructions are executed by a processor, they can be used to implement various operations and functions of the network slicing implementation method described in the various embodiments of this specification.

[0086] The computer-readable medium in the present invention can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device.

[0087] In the present invention, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.

[0088] It will be understood by those skilled in the art that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0089] The present invention is described with reference to flowcharts and / or block diagrams of methods, apparatuses, systems, and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0090] The foregoing descriptions of specific exemplary embodiments of the present invention are for purposes of illustration and description. These descriptions are not intended to limit the invention to the precise forms disclosed, and it is apparent that many variations and modifications are possible in light of the foregoing teachings. The exemplary embodiments have been selected and described for the purpose of explaining the specific principles of the invention and their practical application, thereby enabling those skilled in the art to realize and utilize a variety of exemplary embodiments of the invention and various options and modifications. The scope of the invention is intended to be defined by the claims and their equivalents.

[0091] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above and that the invention can be embodied in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the embodiments should be considered in all respects as illustrative and non-restrictive, and the scope of the invention is defined by the appended claims, not the foregoing description, and all variations within the meaning and range of equivalents of the claims are intended to be included therein. Any reference sign in a claim should not be construed as limiting the claim to which it relates.

[0092] Furthermore, it should be understood that although the specification is described in terms of embodiments, not every embodiment includes every feature described. The specification can include implicit combinations of explicitly mentioned features and / or explicit combinations of implicitely mentioned features. Each embodiment depends on the explicit combinations of features and / or the implicit combinations of features made specifically within that embodiment, and each such embodiment can be combined with every other such embodiment to create further embodiments.

Claims

1. A network slicing implementation method, characterized in that: include: Creating multiple slice channels on the physical port and establishing a mapping relationship between each slice channel and the channelized sub-interface that the user wants to create; Selecting a network layer interface from the slice channels corresponding to the expected channelized sub-interface; calculating the sum of the peak bandwidths of the slice channels of the non-network layer interfaces corresponding to the expected channelized sub-interface; and configuring the peak bandwidth value of the network layer interface to be the difference between the bandwidth value of the expected channelized sub-interface and the sum; If the physical ports are aggregated into an aggregate port, obtaining the bandwidth weights of the physical ports under the aggregate port; in response to the channelized sub-interface bandwidth configured by the user, calculating the expected channelized sub-interface bandwidth of each physical port configured under the aggregate port based on the bandwidth weights of the physical ports; Based on the expected channelized sub-interface bandwidth of each physical port, a committed bandwidth value and a peak bandwidth value of each slice channel are configured; wherein the committed bandwidth value of the slice channel is less than or equal to the peak bandwidth value of the same slice channel; and the sum of the peak bandwidth values ​​of the slice channels corresponding to the expected channelized sub-interface is equal to the expected channelized sub-interface bandwidth; A member group is established based on each slice channel, and traffic scheduling is performed on the Qos queues in each member group based on a preset scheduling algorithm.

2. The network slicing implementation method according to claim 1, characterized in that: Configuring the committed bandwidth and peak bandwidth of each slice channel includes: Based on the committed bandwidth value and peak bandwidth value of the slice channel corresponding to the expected channelized sub-interface under the user-configured aggregation port, and the weights of each physical port aggregated on the aggregation port, the committed bandwidth value and peak bandwidth value of each slice channel are configured.

3. The network slicing implementation method according to claim 1, characterized in that: Configuring the committed bandwidth and peak bandwidth of each slice channel includes: Based on the committed bandwidth value of the slice channel corresponding to the desired channelized sub-interface under the aggregation port configured by the user, and the weight of each physical port of the aggregation port, the committed bandwidth value of each slice channel is configured; The peak bandwidth of the slice channel corresponding to the desired channelized sub-interface under the user-configured aggregation port is used as the peak bandwidth of each slice channel.

4. The network slicing implementation method according to claim 1, characterized in that: The preset scheduling algorithm is a weighted difference round-robin scheduling algorithm.

5. A network slicing implementation system, applying the network slicing implementation method according to any one of claims 1 to 4, characterized in that: include: A creation module, configured to create multiple slice channels on a physical port and establish a mapping relationship between each slice channel and a channelized sub-interface that the user desires to create; a configuration module, configured to configure a committed bandwidth value and a peak bandwidth value of each slice channel in response to each expected channelized sub-interface bandwidth configured by a user; The scheduling module is used to establish member groups based on each slice channel and perform traffic scheduling on the Qos queues in each member group based on a preset scheduling algorithm.

6. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the network slicing implementation method according to any one of claims 1 to 4 by executing the computer instructions.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, which are used to enable a computer to execute the network slicing implementation method described in any one of claims 1 to 4.

Images