CN117896326A - Network data transmission method, network device, electronic device and computer readable medium - Google Patents

Abstract

The present disclosure provides a network data transmission method, the method comprising: receiving messages to be forwarded of different user terminals, and determining flow classification of the messages to be forwarded; matching the message to be forwarded to a corresponding target scheduling queue based on the flow classification of the message to be forwarded; the target scheduling queue is associated with a target shared traffic management scheduler, and the target shared traffic management scheduler manages the target scheduling queue, and the target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on scheduling queue requirements of the user terminal. The present disclosure also provides a network device, an electronic device, and a computer readable medium.

Description

Network data transmission method, network device, electronic device, and computer readable medium

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a network data transmission method and a network device, an electronic device, and a computer-readable medium.

Background technique

With the rapid development of computer networks, more and more important data are transmitted on the network, and QoS (Quality of Service) technology is used to ensure the quality of data transmission. However, with the expansion of the user scale and the increase in the types of services, the requirements for network equipment are getting higher and higher. For example, it is required to refine and distinguish business traffic, and also to uniformly manage and hierarchically schedule transmission objects such as multiple users, multiple services, and multiple traffic. Therefore, relevant technicians proposed HQoS (Hierarchical Quality of service) technology. HQoS technology assembles the scheduling strategy of network transmission into a hierarchical tree structure. The tree structure includes multiple levels of nodes, such as root nodes and leaf nodes. The root node is the convergence point of traffic. Each root node is equipped with a scheduler (Scheduler), and each leaf node is equipped with a scheduling queue (Queue). The scheduler can schedule and manage the scheduling queue of the leaf node, thereby realizing hierarchical management of network transmission.

Summary of the invention

The present invention provides a network data transmission method, a network device, an electronic device, and a computer-readable medium.

In a first aspect, an embodiment of the present disclosure provides a network data transmission method, which includes:

Receiving messages to be forwarded from different user terminals, and determining flow classifications of the messages to be forwarded;

Based on the flow classification of the message to be forwarded, the message to be forwarded is matched to the corresponding target scheduling queue; wherein, the target scheduling queue is associated with a target shared traffic management scheduler, and the target scheduling queue is managed by the target shared traffic management scheduler, and the target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on the scheduling queue requirements of the user terminal.

In some embodiments, the step of determining the target shared traffic management scheduler and the target scheduling queue includes:

Determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements;

The at least one target scheduling queue is associated with the target shared traffic management scheduler.

In some embodiments, determining a target shared traffic management scheduler from a resource pool based on the scheduling queue requirement includes:

Searching the resource pool based on the scheduling queue requirements, and determining a candidate traffic management scheduler that meets the scheduling queue requirements;

Determining whether the candidate traffic management scheduler meets a preset matching condition;

In a case where the candidate traffic management scheduler satisfies the matching condition, the candidate traffic management scheduler is determined as the target shared traffic management scheduler.

In some embodiments, searching the resource pool based on the scheduling queue requirement to determine a candidate traffic management scheduler that meets the scheduling queue requirement includes:

Searching for an enabled scheduler in the resource pool based on the scheduling queue requirement;

In the case that the enabled scheduler cannot meet the scheduling queue requirement, a non-enabled scheduler in the resource pool is searched to determine a candidate traffic management scheduler that meets the scheduling queue requirement.

In some embodiments, the traffic management schedulers in the resource pool are arranged in a preset order; and searching the resource pool based on the scheduling queue requirement includes:

Searching the traffic management scheduler in the resource pool based on the scheduling queue demand order starting from the search mark; wherein the search mark is to determine the location of the shared traffic management scheduler of the previous user terminal;

When there is no candidate traffic management scheduler that meets the scheduling queue requirement from the search mark to the end of the preset sequence, the search continues from the beginning of the preset sequence.

In some embodiments, the resource pool includes a plurality of scheduler groups, each of the scheduler groups includes a preset number of the traffic management schedulers; searching the resource pool based on the scheduling queue requirements includes:

The resource pool is searched based on the scheduling queue requirement at the granularity of the scheduler group.

In some embodiments, the matching condition includes one or more of the following: the type of the candidate traffic management scheduler matches, and the number of queues of the candidate traffic management scheduler is less than or equal to a preset total number of queues.

In some embodiments, before determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirement, the method further includes:

Determine whether the user terminal corresponding to the scheduling queue requirement meets the sharing condition; wherein the sharing condition includes that the user terminal meets the preset terminal configuration condition and/or the user terminal meets the service configuration condition.

In some embodiments, before determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirement, the method further includes:

Configuration information is received, and the scheduling queue requirement is determined based on the configuration information.

In a second aspect, an embodiment of the present disclosure provides a network device, comprising:

A receiving module, used for receiving messages to be forwarded from different user terminals and determining flow classification of the messages to be forwarded;

A matching module is used to match the message to be forwarded to the corresponding target scheduling queue based on the flow classification of the message to be forwarded; wherein the target scheduling queue is associated with a target shared traffic management scheduler, and the target shared traffic management scheduler manages the target scheduling queue, and the target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on the scheduling queue requirements of the user terminal.

A selection module, configured to determine a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements;

An associating module is used to associate the at least one target scheduling queue with the target shared traffic management scheduler.

In some embodiments, the selection module includes:

A searching unit, configured to search the resource pool based on the scheduling queue requirement and determine a candidate traffic management scheduler that meets the scheduling queue requirement;

A judging unit, used to judge whether the candidate traffic management scheduler meets a preset matching condition;

A determining unit is used to determine the candidate traffic management scheduler as the target shared traffic management scheduler if the candidate traffic management scheduler meets the matching condition.

In some embodiments, further comprising:

A judgment module is used to judge whether the user terminal corresponding to the scheduling queue demand meets the sharing condition; wherein the sharing condition includes that the user terminal meets the preset terminal configuration condition and/or the user terminal meets the service configuration condition.

In some embodiments, further comprising:

A configuration module, used for receiving configuration information;

The association module is further used to determine the scheduling queue requirement based on the configuration information.

In a third aspect, an embodiment of the present disclosure provides an electronic device, characterized in that it includes:

one or more processors;

A storage device having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement the method provided according to the present disclosure;

One or more I/O interfaces are connected between the processor and the memory and are configured to implement information interaction between the processor and the memory.

In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method provided according to the present disclosure.

The network transmission method provided by the embodiment of the present disclosure associates a target scheduling queue with a target shared traffic management scheduler, and the target shared traffic management scheduler manages the target scheduling queue. The target scheduling queue can be a scheduling queue for different user terminals. When messages to be forwarded from different user terminals are received, the messages to be forwarded are matched to the corresponding target scheduling queues based on the flow classification of the messages to be forwarded. One target shared traffic management scheduler can manage messages to be forwarded from different user terminals, and one target shared traffic management scheduler no longer corresponds to one user terminal, which reduces the demand for target shared traffic management schedulers, alleviates the problem of limited number of target shared traffic management schedulers, and saves hardware resources.

BRIEF DESCRIPTION OF THE DRAWINGS

In the accompanying drawings of the embodiments of the present disclosure:

FIG1 is an application scenario diagram of an embodiment of the present disclosure;

FIG2 is a flow chart of a network data transmission method provided by an embodiment of the present disclosure;

FIG3 is a flow chart of step S202 in an embodiment of the present disclosure;

FIG4 is a flow chart of S301 in an embodiment of the present disclosure;

FIG5 is a block diagram of a network device provided by an embodiment of the present disclosure;

FIG6 is a block diagram of another network device provided in an embodiment of the present disclosure;

FIG7 is a flow chart of a method for network data transmission provided by an embodiment of the present disclosure;

FIG8 is a schematic diagram of a target shared traffic management scheduler providing traffic management services for two user terminals in an implementation of the present disclosure;

FIG. 9 is a block diagram of a composition of an electronic device provided in an embodiment of the present disclosure.

Detailed ways

In order to enable those skilled in the art to better understand the technical solution of the present disclosure, the network data transmission method and network device provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

The present disclosure will be described more fully below with reference to the accompanying drawings, but the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as being limited to the embodiments set forth below. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete, and will enable those skilled in the art to fully understand the scope of the present disclosure.

The accompanying drawings of the embodiments of the present disclosure are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification, and are used together with the detailed embodiments to explain the present disclosure, and do not constitute a limitation of the present disclosure. By describing the detailed embodiments with reference to the accompanying drawings, the above and other features and advantages will become more apparent to those skilled in the art.

In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

The terms used in the present disclosure are only used to describe specific embodiments and are not intended to limit the present disclosure. The term "and/or" as used in the present disclosure includes any and all combinations of one or more related enumerated items. The singular forms "one" and "the" as used in the present disclosure are also intended to include plural forms, unless the context clearly indicates otherwise. The terms "including", "made of..." as used in the present disclosure specify the presence of the features, wholes, steps, operations, elements and/or components, but do not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and/or groups thereof.

Unless otherwise defined, all terms (including technical and scientific terms) used in this disclosure have the same meaning as those commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined in this disclosure.

The present disclosure is not limited to the embodiments shown in the drawings, but includes modifications of the configurations formed based on the manufacturing process. Therefore, the regions illustrated in the drawings have schematic properties, and the shapes of the regions shown in the drawings illustrate the specific shapes of the regions of the elements, but are not intended to be limiting.

Network equipment is a network device that connects user terminals to the Internet. For example, a network device used in a home can connect multiple user terminals used by family members to the Internet through the network device. Another example is a network device used in a company, where multiple user terminals used by employees can connect to the Internet through the network device. Different user terminal services have different requirements for network resources. For example, Voice over Internet Protocol (VoIP) services based on IP require less bandwidth but have higher requirements for latency. Video services do not have high requirements for latency but have high requirements for bandwidth; ordinary Internet services have ordinary requirements for both latency and bandwidth.

HQoS technology can perform hierarchical scheduling of network resources, that is, hierarchical scheduling of network resources is achieved through the traffic management scheduler, which alleviates the bandwidth crowding between different user terminal services. For home network devices, the bandwidth of the entire home is set, and various home services are uniformly scheduled, such as setting high-priority services to crowd out low-priority services.

Although the relevant network equipment can alleviate the bandwidth crowding between different user terminal services, there is a corresponding relationship between the user terminal and the traffic management scheduler, that is, in the same time period, a traffic management scheduler can only provide services for one user terminal. On the one hand, the processing capacity of the traffic management scheduler is often much greater than the needs of the user terminal, and the utilization rate of the traffic management scheduler is low. On the other hand, the number of traffic management schedulers in the network equipment is limited, and it can only provide services for a limited number of user terminals, which is not conducive to the expansion of network equipment.

Based on this, an embodiment of the present disclosure provides a network data transmission method to improve the utilization rate of the traffic management scheduler and facilitate the expansion of network equipment.

FIG1 is an application scenario diagram of an embodiment of the present disclosure. As shown in FIG1 , a network device 10 includes a plurality of traffic management schedulers 11, each of which can provide traffic management services for at least one user terminal 20, and the network device 10 and the user terminal 20 can achieve communication connection through a network 30. Among them, the traffic management scheduler 11 uses HQoS technology to perform hierarchical management of traffic. For example, the HQoS technology provides a root node and a plurality of leaf nodes, and the plurality of leaf nodes are associated with the root node, and the root node manages the leaf nodes associated with it. Each root node corresponds to a traffic management scheduler 11, and each leaf node corresponds to a scheduling queue, so the traffic management scheduler 11 can manage multiple scheduling queues. In the embodiment of the present disclosure, the scheduling queue can be a scheduling queue of different user terminals 20, that is, the traffic management scheduler 11 can manage the traffic of different user terminals. The network 30 can be a wireless network and a wired network.

In a first aspect, referring to FIG. 2 , an embodiment of the present disclosure provides a network data transmission method, which can be applied to a network device, including:

Step S201: receiving messages to be forwarded from different user terminals, and obtaining flow classifications of the messages to be forwarded.

In step S201, the flow classification of the message to be forwarded can be determined by identifying a tag of the message to be forwarded.

In some embodiments, the user terminal uses HQoS technology to classify and mark the sent messages, and the traffic management scheduler can determine the flow classification of the message to be forwarded by identifying the mark of the message to be forwarded. For example, the user terminal can classify and mark the sent messages through class-based marking technology.

In some embodiments, when configuring the HQoS service, the user terminal can configure the message forwarding function to automatically identify the flow classification of the message to be forwarded. The flow classification includes but is not limited to the priority, network protocol and access control parameters of the message to be forwarded.

Step S202: Match the message to be forwarded to the corresponding target scheduling queue based on the flow classification of the message to be forwarded.

The target scheduling queue is associated with a target shared traffic management scheduler, and the target scheduling queue is managed by the target shared traffic management scheduler. The target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on the user's scheduling queue requirements.

In the disclosed embodiment, the target shared traffic management scheduler can provide traffic management services for multiple user terminals, and can perform hierarchical management on multiple scheduling queues associated therewith, such as matching high-priority scheduling queues to corresponding target scheduling queues to obtain wider bandwidth services or shorter latency services.

In some embodiments, the target scheduling queue has a queue number, and the queue number is associated with a priority. After the target shared traffic management scheduler determines the priority of the message to be forwarded, it determines the target queue number based on the association between the queue number and the priority, and then forwards the message to be forwarded to the target scheduling queue corresponding to the target queue number.

The network transmission method provided by the embodiment of the present disclosure associates a target scheduling queue with a target shared traffic management scheduler, and the target shared traffic management scheduler manages the target scheduling queue. The target scheduling queue can be a scheduling queue for different user terminals. When messages to be forwarded from different user terminals are received, the messages to be forwarded are matched to the corresponding target scheduling queues based on the flow classification of the messages to be forwarded. One target shared traffic management scheduler can manage messages to be forwarded from different user terminals, and one target shared traffic management scheduler no longer corresponds to one user terminal, which reduces the demand for target shared traffic management schedulers, alleviates the problem of limited number of target shared traffic management schedulers, and saves hardware resources.

In some embodiments, as shown in FIG. 3 , in step S202 , the step of determining a target shared traffic management scheduler and a target scheduling queue includes:

Step S301: determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on scheduling queue requirements.

The scheduling queue requirement is determined based on the configuration information set by the user terminal in the network device. The scheduling queue requirement includes but is not limited to the number of scheduling queues and the flow classification of the scheduling queues. The configuration information of the user terminal in the network device includes but is not limited to the queue information such as priority queue (PQ), shaping queue (SHAPER), weighted fair queue (WFQ), etc. When the user terminal completes the configuration of the configuration information, the scheduling queue requirement is determined.

In some embodiments, the resource pool includes traffic management schedulers and scheduling queues. When the user does not set the HQoS service, all traffic management schedulers and scheduling queues are in the resource pool, that is, all traffic management schedulers and scheduling queues are not used.

In some embodiments, the resource pool manages the traffic management scheduler through a bitmap sequence. For example, a 32-bit bitmap sequence is used to record the enabling status of each traffic management scheduler. In the bitmap sequence, each bit represents the usage status of a traffic management scheduler. For example, "00000000001111000000000000111100", where "0" indicates that the traffic management scheduler is not enabled (not occupied/not used), and "1" indicates that the traffic management scheduler is enabled (occupied/used).

The scheduling queue requirement includes the required number of scheduling queues. When the network device receives the HQoS configuration request sent by the user terminal, it generates a shared traffic management scheduler request, and then selects a target traffic management scheduler and a target scheduling queue from the resource pool.

Step S302: associate at least one target scheduling queue with a target shared traffic management scheduler.

The number of scheduling queues required by the user terminal can be determined according to the scheduling queue requirements. After selecting the target traffic management scheduler and the target scheduling queue from the resource pool, the target scheduling queue is associated with the target traffic management scheduler, that is, the target scheduling queue is attached to the target traffic management scheduler.

In some embodiments, the network device may select multiple target scheduling queues from a resource pool, and the multiple target scheduling queues have different priorities. The multiple target scheduling queues with different priorities are all scheduled and managed by the traffic management scheduler.

In the disclosed embodiment, the traffic management scheduler is stored in a resource pool and is uniformly managed by the resource pool, and the usage and loading of the traffic management scheduler are recorded, so that the network device can quickly and accurately determine the target traffic management scheduler.

In some embodiments, as shown in FIG. 4 , step S301, determining a target shared traffic management scheduler from a resource pool based on a scheduling queue requirement, includes:

Step S401, searching a resource pool based on the scheduling queue requirements, and determining a candidate traffic management scheduler that meets the scheduling queue requirements.

In step S401, the disabled traffic management scheduler can meet the scheduling queue requirements of the user terminal, and the enabled traffic management scheduler can also meet the scheduling queue requirements of the user terminal. For example, although the traffic management scheduler provides traffic management services for a certain user terminal, the scheduling queue requirements of the user terminal are less than the traffic management service capabilities that the traffic management scheduler can provide. Therefore, the disabled traffic management scheduler and some enabled traffic management schedulers can be used as candidate traffic management schedulers.

For example, if a user terminal requires 3 scheduling queues, and the traffic management scheduler can provide traffic management for 16 scheduling queues, the traffic management scheduler can also provide traffic management for 13 scheduling queues. Therefore, the traffic management scheduler can provide traffic management services for user terminals that require less than 13 scheduling queues.

Step S402, determining whether the candidate traffic management scheduler meets a preset matching condition.

The matching condition includes one or more of the following: the type of the candidate traffic management scheduler matches, the number of queues in the candidate traffic management scheduler is less than the preset total number of queues. The type of the candidate traffic management scheduler includes but is not limited to PQ, SHAPER, and WFQ types. The total number of queues of the candidate traffic management scheduler is determined by the hardware of the candidate traffic management scheduler.

For example, determine whether the type of the candidate traffic management scheduler meets the user terminal's requirements for the type of scheduling queues. If not, skip the candidate traffic management scheduler; if so, determine whether the number of queues of the candidate traffic management scheduler is less than or equal to the preset total number of queues. If so, the matching condition is met; if not, the matching condition is not met.

Step S403: When the candidate traffic management scheduler meets the matching condition, the candidate traffic management scheduler is determined as the target shared traffic management scheduler.

In the disclosed embodiment, candidate traffic management schedulers are first determined, and then a target traffic management scheduler is selected from the candidate traffic management schedulers based on matching conditions. This allows the target traffic management scheduler to be quickly determined, thereby improving the efficiency of selecting the target traffic management scheduler.

In some embodiments, when the candidate traffic management scheduler meets the matching conditions, it can be further determined whether the single-speed queue and the dual-speed queue match, and when the single-speed queue and the dual-speed queue also match, the candidate traffic management scheduler is determined as the target shared traffic management scheduler.

In some embodiments, when the candidate traffic management scheduler meets the matching conditions and the single-speed queue and the dual-speed queue also match, it is further determined that the number of queues of the candidate traffic management scheduler is less than or equal to the preset total number of queues. When the number of queues of the candidate traffic management scheduler is less than or equal to the preset total number of queues, the candidate traffic management scheduler is determined as the target shared traffic management scheduler.

In some embodiments, step S401, searching the resource pool based on the scheduling queue requirements to determine a candidate traffic management scheduler that meets the scheduling queue requirements, includes: searching the resource pool for an enabled scheduler based on the scheduling queue requirements; when the enabled scheduler cannot meet the scheduling queue requirements, searching the resource pool for an unenabled scheduler to determine a candidate traffic management scheduler that meets the scheduling queue requirements.

Some of the traffic management schedulers in the resource pool are enabled, and some are disabled. If you directly select candidates from the disabled traffic management schedulers, you can quickly determine the target traffic management scheduler. However, this will reduce the utilization of the traffic management scheduler, which is not conducive to providing traffic management services for more user terminals. First search for enabled traffic management schedulers, and then search for disabled traffic management schedulers, which can improve the utilization of traffic management schedulers and expand the service capacity of network devices.

In some embodiments, the traffic management schedulers in the resource pool are arranged in a preset order, such as the traffic management schedulers are arranged in a set sequence number order.

Searching for a resource pool based on scheduling queue requirements includes: starting from a search mark, searching for a traffic management scheduler in the resource pool based on the scheduling queue requirements order; wherein the search mark is used to determine the position of the shared traffic management scheduler of the previous user terminal; if there is no candidate traffic management scheduler that meets the scheduling queue requirements from the search mark to the end of the preset sequence, continuing the search from the starting position of the preset sequence.

It should be noted that the network device serially executes the shared traffic management scheduler request of the user terminal, and the network device determines the location of the target traffic management scheduler for the previous user terminal as a search mark. When the network device executes the shared traffic management scheduler request of the next user terminal, it first starts to select from the search mark, that is, first determines whether the traffic management scheduler that provides services to the previous user terminal can be used as the target traffic management scheduler.

The disclosed embodiment searches the resource pool starting from the search mark to determine the target traffic management scheduler, which can improve the utilization rate of the traffic management scheduler and expand the service capacity of the network device.

In some embodiments, the resource pool includes multiple scheduler groups, each scheduler group includes a preset number of traffic management schedulers.

Searching for a resource pool based on a scheduling queue requirement includes: searching for a resource pool based on a scheduling queue requirement with a scheduler group as a granularity.

For example, 32 traffic management schedulers are divided into four scheduler groups, each of which includes eight traffic management schedulers. When searching for a resource pool, you can search by scheduler group. If all eight traffic management schedulers in a scheduler group are not enabled, you can directly search for the next scheduler group. If there is an enabled traffic management scheduler in the scheduler group, determine whether the enabled traffic management scheduler can be determined as the target traffic management scheduler.

The disclosed embodiment searches for resource pools at a granularity of a scheduler group, which can improve the efficiency of the search, thereby improving the efficiency of determining a target traffic management scheduler.

In some embodiments, in step S301, before determining the target shared traffic management scheduler and at least one target scheduling queue from the resource pool based on the scheduling queue requirements, it also includes: determining whether the user terminal corresponding to the scheduling queue requirements meets the sharing conditions; wherein the sharing conditions include that the terminal configuration of the user terminal meets the preset terminal configuration conditions and/or the service configuration of the user terminal meets the service configuration conditions.

If the user terminal meets the preset sharing conditions, the network device can provide a shared traffic management scheduler for the user terminal. If the user terminal does not meet the preset sharing conditions, the network device cannot provide a shared traffic management scheduler for the user terminal.

In the embodiments of the present disclosure, the terminal configuration of the user terminal includes a custom queue (Custom Queue, CQ) and a class based queue (CBQ), but cannot be PQ, SHAPER, or WFQ. The service configuration of the user terminal can be CQ, CBQ, PQ, SHAPER, or WFQ. In other words, in the sharing conditions, there are certain restrictions on the terminal configuration of the user terminal, while there are no restrictions or fewer restrictions on the service configuration of the user terminal.

If the user terminal meets the sharing conditions, the network device can provide the target shared traffic management scheduler and target scheduling queue for the user terminal and provide hierarchical traffic management for the user terminal. If the user terminal does not meet the sharing conditions, the network device can directly give up providing the target shared traffic management scheduler.

In some embodiments, before step S301, determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on scheduling queue requirements, it also includes: receiving configuration information, and determining scheduling queue requirements based on the configuration information.

The configuration information may be HQoS service configuration information. Compared with QoS service configuration information, HQoS service configuration information may differentiate services based on service levels, and may perform traffic management and scheduling for multiple services of multiple user terminals.

Configuration information is sent by the user terminal to the network device, and includes interface information, flow policy, etc. Based on the configuration information, the scheduling queue requirements can be determined. For example, flow classification can be determined based on the flow policy, and scheduling queue requirements can be determined based on the flow type and bandwidth requirements.

In a second aspect, an embodiment of the present disclosure provides a network device to improve the utilization rate of a traffic management scheduler and facilitate capacity expansion.

5 , a network device 500 provided in an embodiment of the present disclosure includes:

The receiving module 501 is used to receive messages to be forwarded from different user terminals and obtain flow classifications of the messages to be forwarded.

The matching module 502 is used to match the message to be forwarded to the corresponding target scheduling queue based on the flow classification of the message to be forwarded; wherein, the target scheduling queue is associated with the target shared traffic management scheduler, and the target scheduling queue is managed by the target shared traffic management scheduler, and the target shared traffic management scheduler and the target scheduling queue are determined from the resource pool based on the scheduling queue requirements of the user terminal.

The network device provided by the embodiment of the present disclosure associates a target scheduling queue with a target shared traffic management scheduler, and the target shared traffic management scheduler manages the target scheduling queue. The target scheduling queue can be a scheduling queue for different user terminals. When messages to be forwarded from different user terminals are received, the messages to be forwarded are matched to the corresponding target scheduling queues based on the flow classification of the messages to be forwarded. One target shared traffic management scheduler can manage messages to be forwarded from different user terminals, and one target shared traffic management scheduler no longer corresponds to one user terminal, thereby reducing the demand for target shared traffic management schedulers, alleviating the problem of limited number of target shared traffic management schedulers, and saving hardware resources.

In some embodiments, the network device 500 further includes a table management module (not shown in the figure) for storing user configuration information, which is set by the user through a user terminal.

In some embodiments, as shown in FIG. 6 , the network device 600 includes a receiving module 601 and a matching module 602 . The roles and functions of the receiving module 601 and the matching module 602 are the same as those of the receiving module 501 and the matching module 502 , and are not described in detail herein.

The network device 600 further includes a selection module 603 and an association module 604, wherein:

The selection module 603 is used to determine a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements.

The association module 604 is configured to associate at least one target scheduling queue with a target shared traffic management scheduler.

In some embodiments, the selection module 603 includes:

A search unit, used to search a resource pool based on the scheduling queue requirements and determine a candidate traffic management scheduler that meets the scheduling queue requirements;

A determination unit, used to determine whether the candidate traffic management scheduler meets a preset matching condition;

The determining unit is used to determine the candidate traffic management scheduler as the target shared traffic management scheduler when the candidate traffic management scheduler meets the matching condition.

In some embodiments, the network device 600 also includes: a judgment module 605, which is used to judge whether the user terminal corresponding to the scheduling queue requirement meets the sharing condition; wherein the sharing condition includes that the user terminal meets the preset terminal configuration condition and/or the user terminal meets the service configuration condition.

In some embodiments, the network device 600 further includes a configuration module 606, wherein the configuration module 606 is used to receive configuration information; and the association module 604 is used to determine a scheduling queue requirement based on the configuration information.

In some embodiments, the network device 600 further includes a request module 607 for initiating a sharing request based on a scheduling queue requirement.

The network device 600 provided in the embodiment of the present disclosure may be a router, or a switch or other device.

In order to better understand the network data transmission method and network device of the embodiments of the present disclosure, two user terminals are taken as an example and further described in combination with Figures 6 and 7.

In step S701, the network device is started and initialized. During initialization, the user terminal is not connected to the network device, the network device is not connected to the HQoS service, the shared traffic management scheduler and the scheduling queue are in the resource pool, and the shared traffic management scheduler is not occupied. Assume that there are 32 shared traffic management schedulers in the resource pool, and the Bitmap sequence is "0000000000000000000000000000000000".

In step S702, the network device receives the HQoS service request of the first user terminal, and transparently transmits the HQoS service request to the table management module through the configuration module 606. Assume that the HQoS service request includes 3 nodes, and the scheduling queue requirements of each node are as follows: the scheduling queue requirement of the first node is PQ high priority and speed limit requirement; the scheduling queue requirement of the second node is PQ medium priority and speed limit requirement; the scheduling queue requirement of the third node is PQ low priority and speed limit requirement.

In step S703, the table management module transmits the HQoS service request to the request module 607, for example, transmits the scheduling queue requirement to the request module 607, and the judgment module 605 determines whether the first user terminal meets the sharing condition. If the sharing condition is met, step S704 is executed. If the sharing condition is not met, exit.

In step S704, the selection module 603 queries the resource pool to obtain a shared traffic management scheduler.

For example, the enabled shared traffic management scheduler is queried from the resource pool. If the enabled shared traffic management scheduler cannot satisfy the first user terminal, the disabled shared traffic management scheduler is queried to determine the target shared traffic management scheduler. During the query process, the query is performed starting from the shared traffic management scheduler corresponding to the search tag. If there is still no candidate shared traffic management scheduler that meets the scheduling queue requirements at the end of the query, the query is started from the head of the queue in the resource pool. Moreover, the query can be performed according to the scheduler group. For example, the 32 shared traffic management schedulers in the resource pool can be divided into four scheduler groups, each scheduler group includes eight shared traffic management schedulers.

"00000000

00000000

00000000

00000000"

If all the shared traffic management schedulers in the first scheduler group are not enabled with shared traffic management, the next scheduler group is queried, and the queried shared traffic management scheduler is determined as the target shared traffic management scheduler.

For the above three node scheduling queue requirements, you can select a target shared traffic management scheduler as the root node and three target scheduling queues as leaf nodes. Modify the Bitmap sequence, such as:

"00000000

00000000

00000000

00000001”

"1" means the shared traffic management scheduler is enabled, and "0" means the shared traffic management scheduler is not enabled.

In step S705, the association module 604 attaches the target shared traffic management scheduler to the root node, and associates the target scheduling queue with the target shared traffic management scheduler. The Bitmap sequence is sent to the table management module for updating.

In step S706, a message to be forwarded sent by the first user terminal is received, a flow classification of the message to be forwarded is obtained, and a target scheduling queue is matched based on the flow classification of the message to be forwarded, and then the message to be forwarded is sent to the corresponding target scheduling queue.

In step S707, an HQoS service request from a second user terminal is received.

In step S708 , the HQoS service request is transparently transmitted to the table management module through the configuration module 606 .

In step S709, the table management module transparently transmits the HQoS service request to the request module 607, and the judgment module 605 judges whether the second user terminal meets the sharing condition. If the sharing condition is met, step S710 is executed; if not, step S710 is exited.

In step S710, the selection module 603 queries the resource pool to obtain a shared traffic management scheduler. The query method is the same as step S704 and will not be repeated here.

The shared traffic management scheduler determined in step S710 may be a shared traffic management scheduler determined by the first user terminal, that is, the shared traffic management scheduler provides traffic management services for both the first user terminal and the second user terminal.

In step S711, if the shared traffic management scheduler determined in step S710 is different from the shared traffic management scheduler determined by the first user terminal, the execution method is the same as step S705; if the shared traffic management scheduler determined in step S710 is the same as the shared traffic management scheduler determined by the first user terminal, the association module 604 associates the target scheduling queue with the target shared traffic management scheduler. The Bitmap sequence is sent to the table management module for updating.

In step S712, a message to be forwarded sent by the second user terminal is received, a flow classification of the message to be forwarded is obtained, and a target scheduling queue is matched based on the flow classification of the message to be forwarded, and then the message to be forwarded is sent to the corresponding target scheduling queue.

Through the above steps S701 to S712, the target shared traffic management scheduler can provide traffic management services for the first user terminal and the second user terminal. Figure 8 shows a schematic diagram of a target shared traffic management scheduler providing traffic management services for the first user terminal and the second user terminal. In Figure 8, the scheduling queues Q1-Q3 are the target scheduling queues for the first user terminal, the scheduling queues Q5-Q6 are the target scheduling queues for the second user terminal, and the target shared traffic management scheduler 801 provides three priorities, namely the gold scheduling queue, the silver scheduling queue, and the bronze scheduling queue with gradually decreasing priorities. The target shared traffic management scheduler can limit the speed of the scheduling queues Q1 and Q4. Figure 8 shows that the first user terminal and the second user terminal share the target shared traffic management scheduler, and different scheduling queues can be managed in a hierarchical manner. The target shared traffic management scheduler 801 sends the scheduling queues to the server or other user terminals through port 802.

In a third aspect, an embodiment of the present disclosure also provides an electronic device.

9 , the electronic device includes: at least one processor 901; at least one memory 902, and one or more I/O interfaces 903, connected between the processor 901 and the memory 902; wherein the memory 902 stores one or more computer programs that can be executed by at least one processor 901, and the one or more computer programs are executed by at least one processor 901 so that the at least one processor 901 can execute the above-mentioned data processing method.

Among them, the processor is a device with data processing capabilities, including but not limited to the central processing unit (CPU); the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I/O interface (read-write interface) is connected between the processor and the memory, and can realize information exchange between the memory and the processor, including but not limited to the data bus (Bus), etc.

The present disclosure also provides a computer-readable storage medium on which a computer program is stored, wherein the computer program implements the above-mentioned data method when executed by a processor/processing core. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

Those skilled in the art will appreciate that all or some of the steps, systems, and functional modules/units in the apparatus disclosed above may be implemented as software, firmware, hardware, or a suitable combination thereof.

In hardware implementations, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation.

Some physical components or all physical components may be implemented as software executed by a processor, such as a central processing unit (CPU), a digital signal processor or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-temporary medium) and a communication medium (or temporary medium). As known to those of ordinary skill in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules or other data). Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage; read-only compact disk (CD-ROM), digital versatile disk (DVD) or other optical disk storage; magnetic cassettes, magnetic tapes, disk storage or other magnetic storage; any other medium that can be used to store desired information and can be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

The present disclosure has disclosed example embodiments, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly stated, features, characteristics, and/or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and/or elements described in conjunction with other embodiments. Therefore, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims (16)

1. A method of network data transmission, comprising:

receiving messages to be forwarded of different user terminals, and obtaining flow classification of the messages to be forwarded;

matching the message to be forwarded to a corresponding target scheduling queue based on the flow classification of the message to be forwarded; the target scheduling queue is associated with and managed by a target shared traffic management scheduler, and the target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on scheduling queue requirements of the user terminal.

2. The method of claim 1, wherein determining the target shared traffic management scheduler and the target dispatch queue comprises:

determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue demand;

the at least one target scheduling queue is associated with the target shared traffic management scheduler.

3. The method of claim 2, wherein the determining a target shared traffic management scheduler from a resource pool based on the scheduling queue demand comprises:

searching the resource pool based on the scheduling queue demand, and determining a candidate flow management scheduler meeting the scheduling queue demand;

judging whether the candidate flow management scheduler meets a preset matching condition or not;

and determining the candidate traffic management scheduler as the target shared traffic management scheduler in the case that the candidate traffic management scheduler meets the matching condition.

4. The method of claim 3, wherein the looking up the resource pool based on the scheduling queue demand, determining a candidate traffic management scheduler that meets the scheduling queue demand, comprises:

Searching an enabled scheduler in the resource pool based on the scheduling queue demand;

and searching for an disabled scheduler in the resource pool under the condition that the enabled scheduler cannot meet the scheduling queue demand, and determining a candidate traffic management scheduler meeting the scheduling queue demand.

5. A method according to claim 3, wherein the traffic management schedulers in the resource pool are arranged in a preset order; the searching the resource pool based on the scheduling queue requirement comprises the following steps:

sequentially searching the traffic management schedulers in the resource pool based on the scheduling queue demands from a search mark; wherein the search mark is used for determining the position of a shared flow management scheduler of a previous user terminal;

and continuing searching from the starting position of the preset sequence under the condition that no candidate traffic management scheduler meeting the scheduling queue requirement is arranged from the searching mark to the end of the preset sequence.

6. A method according to claim 3, wherein the resource pool comprises a plurality of scheduler groups, each scheduler group comprising a preset number of the traffic management schedulers; the searching the resource pool based on the scheduling queue requirement comprises the following steps:

And searching the resource pool based on the scheduling queue requirement by taking the scheduler group as granularity.

7. The method of claim 3, wherein the matching condition comprises one or more of a type of the candidate traffic management scheduler matching a requirement of the user terminal, a number of queues of the candidate traffic management scheduler being less than or equal to a preset total number of queues.

8. The method of any of claims 2 to 7, wherein prior to determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements, further comprising:

judging whether the user terminal corresponding to the scheduling queue requirement meets a sharing condition or not; the sharing condition includes that the user terminal meets a preset terminal configuration condition and/or the user terminal meets a service configuration condition.

9. The method of any of claims 2 to 7, wherein prior to determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements, further comprising:

and receiving configuration information and determining the scheduling queue requirement based on the configuration information.

10. A network device, comprising:

the receiving module is used for receiving messages to be forwarded of different user terminals and obtaining flow classification of the messages to be forwarded;

the matching module is used for matching the message to be forwarded to a corresponding target scheduling queue based on the flow classification of the message to be forwarded; the target scheduling queue is associated with a target shared traffic management scheduler, the target shared traffic management scheduler manages the target scheduling queue, and the target shared traffic management scheduler and the target scheduling queue are determined from a resource pool based on scheduling queue requirements of the user terminal.

11. The network device of claim 10, further comprising:

a selection module for determining a target shared traffic management scheduler and at least one target scheduling queue from a resource pool based on the scheduling queue requirements;

and the association module is used for associating the at least one target scheduling queue with the target shared flow management scheduler.

12. The network device of claim 11, wherein the selection module comprises:

the searching unit is used for searching the resource pool based on the scheduling queue demand and determining a candidate flow management scheduler meeting the scheduling queue demand;

The judging unit is used for judging whether the candidate flow management scheduler meets a preset matching condition or not;

and the determining unit is used for determining the candidate traffic management scheduler as the target shared traffic management scheduler in the case that the candidate traffic management scheduler meets the matching condition.

13. The network device of claim 11, further comprising;

the judging module is used for judging whether the user terminal corresponding to the scheduling queue requirement meets the sharing condition or not; the sharing condition includes that the user terminal meets a preset terminal configuration condition and/or the user terminal meets a service configuration condition.

14. The network device of claim 11, further comprising;

the configuration module is used for receiving configuration information;

the association module is further configured to determine the scheduling queue requirement based on the configuration information.

15. An electronic device, comprising:

one or more processors;

storage means having stored thereon one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-9;

One or more I/O interfaces coupled between the processor and the memory configured to enable information interaction of the processor with the memory.

16. A computer readable medium having stored thereon a computer program which, when executed by a processor, implements the method according to any of claims 1-9.