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 disclosure relates to the field of communication technologies, and in particular, to a network data transmission method, a network device, an electronic device, and a computer readable medium.

Background

With the rapid development of computer networks, more and more important data is transmitted over the network, and QoS (Quality of Service, i.e., quality of service) technology is used to guarantee the quality of data transmission. However, as the scale of users increases, the demands on network devices are higher and higher, for example, the demands for differentiating traffic flow are finer, and unified management and hierarchical scheduling of transmission objects such as multiple users, multiple services, and multiple traffic are also required. Accordingly, related arts propose the HQoS (Hierarchical Quality of service, layered quality of service) technique. The HQoS technique is a tree structure in which scheduling policies for network transmissions are assembled into layers. The tree structure includes multiple levels of nodes, such as: root nodes and leaf nodes. The root nodes are aggregation points of traffic, each root node is provided with a Scheduler, and each leaf node is provided with a scheduling Queue (Queue). The scheduler can perform scheduling management on the scheduling queues of the leaf nodes, so that hierarchical management of network transmission is realized.

Disclosure of Invention

The disclosure provides a network data transmission method, network equipment, electronic equipment and computer readable medium.

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

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, 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.

In some embodiments, the step of determining the target shared traffic management scheduler and the target scheduling 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.

In some embodiments, 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.

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

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.

In some embodiments, 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.

In some embodiments, 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.

In some embodiments, the matching condition includes one or more of a type match of the candidate traffic management scheduler, a number of queues of the candidate traffic management scheduler being less than or equal to a preset total number of queues.

In some embodiments, before the determining the target shared traffic management scheduler and the at least one target dispatch queue from the resource pool based on the dispatch queue demand, further comprises:

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.

In some embodiments, before the determining the target shared traffic management scheduler and the at least one target dispatch queue from the resource pool based on the dispatch queue demand, further comprises:

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

In a second aspect, embodiments of the present disclosure provide a network device, comprising:

the receiving module is used for receiving messages to be forwarded of different user terminals and determining 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.

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.

In some embodiments, the selecting module includes:

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.

In some embodiments, 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.

In some embodiments, 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.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

one or more processors;

A storage device having one or more programs stored thereon, which when executed by the one or more processors, cause the one or more processors to implement a method provided in accordance with the present disclosure;

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

In a fourth aspect, the disclosed embodiments provide a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a method provided in accordance with the disclosure.

According to the network transmission method provided by the embodiment of the disclosure, the target scheduling queues are associated with the target shared traffic management schedulers, the target scheduling queues are managed by the target shared traffic management schedulers, the target scheduling queues can be scheduling queues of different user terminals, when messages to be forwarded of 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 the messages to be forwarded of different user terminals, and the target shared traffic management scheduler is not one user terminal, so that the demand of the target shared traffic management scheduler is reduced, the problem that the number of the target shared traffic management schedulers is limited is solved, and hardware resources are saved.

Drawings

In the drawings of the embodiments of the present disclosure:

fig. 1 is an application scenario diagram of an embodiment of the present disclosure;

fig. 2 is a flowchart of a network data transmission method according to an embodiment of the present disclosure;

FIG. 3 is a flowchart of step S202 in an embodiment of the present disclosure;

FIG. 4 is a flowchart of S301 in an embodiment of the present disclosure;

fig. 5 is a block diagram of a network device according to an embodiment of the present disclosure;

fig. 6 is a block diagram of another network device according to an embodiment of the present disclosure;

fig. 7 is a flowchart of a method for network data transmission according to an embodiment of the present disclosure;

FIG. 8 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 an electronic device according to an embodiment of the disclosure.

Detailed Description

In order to enable those skilled in the art to better understand the technical solutions of the present disclosure, the following describes in detail a network data transmission method and a network device provided by embodiments of the present disclosure with reference to the accompanying drawings.

The present disclosure will be described more fully hereinafter with reference to the accompanying drawings, but the embodiments shown may be embodied in different forms and should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The accompanying drawings, which are included to provide a further understanding of embodiments of the disclosure and are incorporated in and constitute a part of this specification, illustrate the disclosure and together with the detailed embodiment, do not limit the disclosure. The above and other features and advantages will become more readily apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

Embodiments of the disclosure and features of embodiments may be combined with each other without conflict.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The term "and/or" as used in this disclosure includes any and all combinations of one or more of the associated listed items. As used in this disclosure, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises," "comprising," "including," "includes," "including," "having," "including," "made of … …" and/or "comprising," when used in this disclosure, specify the presence of stated features, integers, steps, operations, elements, and/or components, but does not preclude the presence or addition of one or more other features, integers, 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 commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

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

The network device is a network device in which a user terminal is connected to the internet. For example, a network device used by a family, and a plurality of user terminals used by family members may be connected to the internet through the network device. For another example, a network device used by a company, and a plurality of user terminals used by an employee may be connected to the internet through the network device. The network resources are required differently by different user terminal services. For example, voice over IP (Voice over Internet Protocol, voIP) traffic requires less bandwidth but requires higher latency. The video service has low time delay requirement, but has higher requirement on bandwidth; the common internet service has common time delay and bandwidth requirements.

The HQoS technology can perform layered scheduling on network resources, namely, the layered scheduling of the network resources is realized through a flow management scheduler, so that bandwidth occupation among different user terminal services is relieved. For the home network device, the bandwidth of the whole home is set, and various services of the home are uniformly scheduled, such as setting high-priority services to occupy low-priority services.

Although the related network equipment can relieve bandwidth occupation among different user terminal services, the corresponding relationship exists between the user terminal and the traffic management scheduler, namely, one traffic management scheduler can only provide service for one user terminal in the same time period. On the one hand, the processing power of the traffic management scheduler is often far greater than the demands of the user terminals, and the utilization rate of the traffic management scheduler is low. On the other hand, the number of the flow management schedulers in the network equipment is limited, and the service can be provided for only a limited number of user terminals, so that the capacity expansion of the network equipment is not facilitated.

Based on this, the embodiment of the disclosure provides a network data transmission method, so as to improve the utilization rate of the traffic management scheduler and facilitate the capacity expansion of the network device.

Fig. 1 is an application scenario diagram of an embodiment of the present disclosure. As shown in fig. 1, the 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 implement a communication connection through a network 30. Wherein the traffic management scheduler 11 adopts the HQoS technique to hierarchically manage traffic. For example, the HQoS technique provides a root node and a plurality of leaf nodes associated with the root node, the root node managing the leaf nodes associated therewith. Each root node corresponds to one traffic management scheduler 11 and each leaf node corresponds to one scheduling queue, so that the traffic management scheduler 11 can manage a plurality of scheduling queues. In the embodiment of the present disclosure, the scheduling queue may be a scheduling queue of different user terminals 20, that is, the traffic management scheduler 11 may manage traffic of different user terminals. The network 30 may be a wireless network or a wired network.

In a first aspect, referring to fig. 2, an embodiment of the present disclosure provides a network data transmission method, which is applicable to a network device, including:

step S201, receiving messages to be forwarded of different user terminals, and obtaining flow classification of the messages to be forwarded.

In step S201, the flow classification of the message to be forwarded may be determined by identifying the label of the message to be forwarded.

In some embodiments, the user terminal adopts the HQoS technology, and can classify the sent message, and the traffic management scheduler can determine the flow classification by identifying the label of the message to be forwarded. For example, the user terminal may sort and tag the outgoing messages by a class-based tagging (Cl-based tagging) technique.

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

Step S202, 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 the resource pool based on scheduling queue requirements of users.

In the embodiment of the disclosure, the target shared traffic management scheduler may provide traffic management services for a plurality of user terminals, and may perform hierarchical management on a plurality of scheduling queues associated with the target shared traffic management scheduler, for example, match a scheduling queue with a high priority to a corresponding target scheduling queue, so as to obtain a wider bandwidth service or a service with a shorter delay.

In some embodiments, the target dispatch queue has a queue number associated with a priority. After the target shared flow management scheduler determines the priority of the message to be forwarded, the target queue number is determined according to the association relation between the queue number and the priority, and then the message to be forwarded is forwarded to a target scheduling queue corresponding to the target queue number.

According to the network transmission method provided by the embodiment of the disclosure, the target scheduling queues are associated with the target shared traffic management schedulers, the target scheduling queues are managed by the target shared traffic management schedulers, the target scheduling queues can be scheduling queues of different user terminals, when messages to be forwarded of 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 the messages to be forwarded of different user terminals, and the target shared traffic management scheduler is not one user terminal, so that the demand of the target shared traffic management scheduler is reduced, the problem that the number of the target shared traffic management schedulers is limited is solved, and hardware resources are saved.

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.

Wherein, the scheduling queue requirement is determined according to the configuration information set by the user terminal in the network equipment. Scheduling queue requirements include, but are not limited to, the number of scheduling queues and the flow classification of the scheduling queues. Configuration information of the ue at the network device includes, but is not limited to, queue information such as Priority Queue (PQ), shaping Queue (SHAPER), weighted fair Queue (Weighted Fair Queuing, WFQ), etc. When the user terminal completes the configuration of the configuration information, the scheduling queue requirement is determined.

In some embodiments, a traffic management scheduler and a scheduling queue are included in the resource pool. When the user does not set the HQoS service, all the traffic management schedulers and the scheduling queues are in the resource pool, i.e. all the traffic management schedulers and the scheduling queues are not used.

In some embodiments, the resource pool is a traffic management scheduler managed by a Bitmap (Bitmap) sequence. Such as recording the enablement of each traffic management scheduler using a 32-bit Bitmap sequence in which each bit represents the usage status of one traffic management scheduler. For example, "00000000001111000000000000111100", where "0" indicates that the traffic management scheduler is not enabled (unoccupied/unused) and "1" indicates that the traffic management scheduler is enabled (occupied/used).

Wherein the schedule queue requirements include a number of requirements for the schedule queue. When the network equipment receives a request for configuring HQoS issued by the user terminal, and generates a request for sharing the traffic management scheduler, then a target traffic management scheduler and a target scheduling queue are selected from the resource pool.

Step S302, associating at least one target scheduling queue with a target shared traffic management scheduler.

The number of the scheduling queues required by the user terminal can be determined according to the scheduling queue requirements. And after the target traffic management scheduler and the target scheduling queue are selected from the resource pool, the target scheduling queue is associated with the target traffic management scheduler, namely, the target scheduling queue is hung to the target traffic management scheduler.

In some embodiments, the network device may select a plurality of target scheduling queues from the resource pool, where the plurality of target scheduling queues have different priorities, and each of the plurality of target scheduling queues having different priorities is scheduled and managed by the traffic management scheduler.

In the embodiment of the disclosure, the flow management scheduler is stored in the resource pool and is uniformly managed by the resource pool, and the use and filling of the flow management scheduler are recorded, so that the network equipment can conveniently and quickly and accurately determine the target flow 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 demand, and determining a candidate flow management scheduler meeting the scheduling queue demand.

In step S401, the disabled traffic management scheduler may meet the scheduling queue requirement of the user terminal, and the enabled traffic management scheduler may also meet the scheduling queue requirement of the user terminal. For example, although the traffic management scheduler provides traffic management services for a certain user terminal, the scheduling queue requirement of the user terminal is smaller than the traffic management service capability that the traffic management scheduler can provide. Thus, an disabled traffic management scheduler and a partially enabled traffic management scheduler may be candidates for the traffic management scheduler.

For example, the user terminal needs 3 scheduling queue requirements, and the traffic management scheduler can provide traffic management of 16 scheduling queues, and at this time, the traffic management scheduler can also provide traffic management of 13 scheduling queues. Thus, the traffic management scheduler can provide traffic management services for user terminals with scheduling queue requirements less than 13.

Step S402, judging whether the candidate flow management scheduler meets the preset matching condition.

The matching condition comprises one or more of type matching of the candidate flow management schedulers and the fact that the number of queues in the candidate flow management schedulers is smaller than the preset total number of queues. Types of candidate traffic management schedulers include, but are not limited to, PQ, SHAPER, WFQ types. The total number of queues of a candidate traffic management scheduler is determined by the hardware of the candidate traffic management scheduler.

For example, judging whether the type of the candidate traffic management scheduler meets the type requirement of the user terminal on the scheduling queue, if not, skipping the candidate traffic management scheduler; if yes, judging that the number of the queues of the candidate flow management scheduler is smaller than or equal to the preset total number of the queues, and if yes, meeting a matching condition; if not, the matching condition is not satisfied.

In step S403, in the 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 the embodiment of the disclosure, the candidate flow management schedulers are determined first, and then the target flow management schedulers are selected from the candidate flow management schedulers based on the matching conditions, so that the target flow management schedulers can be determined quickly, and the efficiency of selecting the target flow management schedulers is improved.

In some embodiments, if the candidate traffic management scheduler meets the matching condition, it may further determine whether the single-speed queue and the double-speed queue match, and if the single-speed queue and the double-speed queue also match, determine the candidate traffic management scheduler as the target shared traffic management scheduler.

In some embodiments, in a case that the candidate traffic management scheduler satisfies the matching condition and the single-speed queue and the double-speed queue are also matched, further determining that the number of queues of the candidate traffic management scheduler is less than or equal to a preset total number of queues, and determining the candidate traffic management scheduler as the target shared traffic management scheduler when the number of queues of the candidate traffic management scheduler is less than or equal to the preset total number of queues.

In some embodiments, step S401, searching a resource pool based on a scheduling queue requirement, determines a candidate traffic management scheduler that satisfies the scheduling queue requirement, includes: searching an enabled scheduler in the resource pool based on the scheduling queue requirement; and under the condition that the enabled scheduler cannot meet the demand of the scheduling queue, searching for the disabled scheduler in the resource pool, and determining a candidate traffic management scheduler meeting the demand of the scheduling queue.

Some of the traffic management schedulers in the resource pool are enabled traffic management schedulers, some are disabled traffic management schedulers, and if candidates are selected directly from the disabled traffic management schedulers, the target traffic management scheduler can be quickly determined, however, the utilization rate of the traffic management scheduler can be reduced, which is unfavorable for providing traffic management services for more user terminals. The enabled traffic management scheduler is searched first, and then the disabled traffic management scheduler is searched, so that the utilization rate of the traffic management scheduler can be improved, and the service capacity of the network equipment can be enlarged.

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

Searching a resource pool based on the scheduling queue demand, including: starting from the search mark, searching a flow management scheduler in the resource pool based on the scheduling queue demand sequence; wherein the search flag is used for determining the position of the shared traffic management scheduler of the previous user terminal; in the case that there is no candidate traffic management scheduler satisfying the schedule queue requirement from the search mark to the end of the preset order, the search is continued from the start position of the preset order.

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

According to the method and the device for searching the resource pool, the resource pool is searched from the search mark to determine the target flow management scheduler, so that the utilization rate of the flow management scheduler can be improved, and the service capacity of the network equipment is enlarged.

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

Searching a resource pool based on the scheduling queue demand, including: and searching a resource pool based on the scheduling queue requirement by taking the scheduler group as granularity.

Illustratively, the 32 traffic management schedulers are segmented into four scheduler groups, each scheduler group comprising eight traffic management schedulers. When searching the resource pool, the resource pool can be searched according to the scheduler groups, and if all eight traffic management schedulers in a certain scheduler group are not enabled, the next scheduler group can be directly searched. If an enabled traffic management scheduler exists in the scheduler group, it is determined whether the enabled traffic management scheduler can be determined as a target traffic management scheduler.

According to the method and the device for searching the resource pool, the scheduler group is used as granularity to search the resource pool, so that the searching efficiency can be improved, and the efficiency of determining the target flow management scheduler is improved.

In some embodiments, before determining the target shared traffic management scheduler and the at least one target dispatch queue from the resource pool based on the dispatch queue demand, at step S301, further comprises: judging whether a user terminal corresponding to the scheduling queue requirement meets a sharing condition or not; the sharing condition includes that the terminal configuration of the user terminal meets a preset terminal configuration condition and/or the service configuration of the user terminal meets a service configuration condition.

If the user terminal meets the preset sharing condition, the network device can provide the shared traffic management scheduler for the user terminal, and if the user terminal cannot meet the preset sharing condition, the network device cannot provide the shared traffic management scheduler for the user terminal.

In the embodiment of the present disclosure, the terminal configuration of the user terminal includes Custom Queue (CQ), CBQ (Class Based Queue, CBQ), but cannot be PQ, SHAPER, WFQ, and the service configuration of the user terminal may be CQ, CBQ, PQ, SHAPER, WFQ, in other words, in the sharing condition, there is a certain limitation on the terminal configuration of the user terminal, and there is no limitation or less limitation on the service configuration of the user terminal.

If the user terminal meets the sharing condition, the network device may provide a target shared traffic management scheduler and a 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 condition, the network device may directly forgo providing the target shared traffic management scheduler.

In some embodiments, before determining the target shared traffic management scheduler and the at least one target dispatch queue from the resource pool based on the dispatch queue demand, at step S301, further comprises: and receiving configuration information and determining scheduling queue requirements based on the configuration information.

The configuration information may be QoS service configuration information, which may be used for service differentiation based on service class, and may be used for traffic management and scheduling of multiple services of multiple user terminals, compared to QoS service configuration information.

The configuration information is sent by the user terminal to the network device, and the configuration information includes interface information, flow strategy and the like. Scheduling queue requirements may be determined based on the configuration information. For example, a flow class may be determined based on a flow policy, and a scheduling queue requirement may be determined based on a type of flow and a bandwidth requirement.

In a second aspect, embodiments of the present disclosure provide a network device that improves the utilization of a traffic management scheduler and facilitates capacity expansion.

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

the receiving module 501 is configured to receive messages to be forwarded of different user terminals, and obtain flow classifications of the messages to be forwarded.

The matching module 502 is configured to match a message to be forwarded to a corresponding target scheduling queue based on a 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.

According to the network equipment provided by the embodiment of the disclosure, the target scheduling queues are associated with the target shared traffic management schedulers, the target scheduling queues are managed by the target shared traffic management schedulers, the target scheduling queues can be scheduling queues of different user terminals, when messages to be forwarded of 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 the messages to be forwarded of different user terminals, and the target shared traffic management scheduler is not one user terminal, so that the demand of the target shared traffic management scheduler is reduced, the problem that the number of the target shared traffic management schedulers is limited is solved, and hardware resources are saved.

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

In some embodiments, as shown in fig. 6, the network device 600 includes a receiving module 601 and a matching module 602, where 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 herein.

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

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

An association module 604 for associating at least one target dispatch queue with a target shared traffic management scheduler.

In some embodiments, the selection module 603 includes:

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;

and a determining unit configured to determine the candidate traffic management scheduler as the target shared traffic management scheduler in a case where the candidate traffic management scheduler satisfies the matching condition.

In some embodiments, the network device 600 further comprises; a judging module 605, configured to judge whether a user terminal corresponding to a scheduling queue requirement meets a sharing condition; the sharing condition comprises that the user terminal meets a preset terminal configuration condition and/or the user terminal meets a service configuration condition.

In some embodiments, the network device 600 further comprises a configuration module 606, wherein the configuration module 606 is configured to receive configuration information; the association module 604 is configured 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 the scheduling queue requirements.

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

In order to better understand the network data transmission method and the network device according to the embodiments of the present disclosure, two user terminals are taken as examples, and further described below with reference to fig. 6 and fig. 7.

In step S701, a network device is started and initialized. When in initialization, the user terminal is not connected to the network equipment, the network equipment is not connected to the HQoS service, the shared flow management scheduler and the scheduling queue are both in the resource pool, and the shared flow management scheduler is unoccupied. Suppose there are 32 shared traffic management schedulers in the resource pool, and the Bitmap sequence is "00000000000000000000000000000000".

In step S702, the network device receives the qos service request of the first user terminal, and passes the qos service request through to the table management module through the configuration module 606. Assuming that the HQoS traffic request includes 3 nodes, the scheduling queue requirements for each node are as follows: the scheduling queue requirement of the first node is a PQ high priority and a speed limiting requirement; the scheduling queue requirement of the second node is the priority in the PQ and the infinite speed requirement; the scheduling queue requirement of the third node is a PQ low priority and infinite speed requirement.

In step S703, the table management module transparently transmits the qos service request to the request module 607, for example, transparently transmits the scheduling queue requirement to the request module 607, and the determination module 605 determines whether the first user terminal satisfies the sharing condition, if the sharing condition is satisfied, the step S704 is executed, and if the sharing condition is not satisfied, the step is exited.

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

Illustratively, the enabled shared traffic management scheduler is queried from the resource pool, and if the enabled shared traffic management scheduler fails to satisfy the first user terminal, the disabled shared traffic management scheduler is queried to determine a target shared traffic management scheduler. In the query process, the shared traffic management scheduler corresponding to the search mark is used as a starting point for query, and if the candidate shared traffic management scheduler which still does not meet the scheduling queue requirement at the end is queried, the query is started from the head of the resource pool. Also, queries may be performed by scheduler groups. For example, the 32 shared traffic management schedulers in the resource pool may be divided into four scheduler groups, each scheduler group comprising eight shared traffic management schedulers.

“00000000

00000000

00000000

00000000”

If the shared traffic management schedulers in the first scheduler group are all disabled, the next scheduler group is queried. And determining the queried shared traffic management scheduler as a target shared traffic management scheduler.

For the 3-node schedule queue requirement described above, one target shared traffic management scheduler may be selected as the root node and three target schedule queues as leaf nodes. Modifying the Bitmap sequence, such as:

“00000000

00000000

00000000

00000001”

where "1" is that the shared traffic management scheduler is enabled and "0" is that the shared traffic management scheduler is not enabled.

In step S705, the association module 604 hooks the target shared traffic management scheduler to the root node and associates the target dispatch 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, the flow classification of the message to be forwarded is matched with a target scheduling queue based on the flow classification of the message to be forwarded, and the message to be forwarded is sent to the corresponding target scheduling queue.

In step S707, an HQoS service request of the second user terminal is received.

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

In step S709, the table management module passes the HQoS service request to the request module 607, and the determination module 605 determines whether the second user terminal satisfies the sharing condition, if so, executes step S710, and if not, exits.

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

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 in the first user terminal, the execution mode is the same as that in 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, the message to be forwarded sent by the second user terminal is received, a flow classification of the message to be forwarded is obtained, the target scheduling queue is matched based on the flow classification of the message to be forwarded, and 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 may provide traffic management services for the first user terminal and the second user terminal. Fig. 8 shows a schematic diagram of a target shared traffic management scheduler providing traffic management services for a first user terminal and a second user terminal. In fig. 8, the scheduling queues Q1-Q3 are target scheduling queues of a first user terminal, the scheduling queues Q5-Q6 are target scheduling queues of a second user terminal, and the target shared traffic management scheduler 801 provides three priorities, namely a Gold (Gold) scheduling queue, a silver (silver) scheduling queue, and a Bronze (Bronze) scheduling queue, which gradually decrease in priority. The target shared traffic management scheduler may rate limit the scheduling queues Q1 and Q4. Fig. 8 illustrates that the first user terminal and the second user terminal share the target shared traffic management scheduler, and that different scheduling queues may be hierarchically managed. The target shared traffic management scheduler 801 sends the dispatch queue to a server or other user terminal via port 802.

In a third aspect, embodiments of the present disclosure further provide an electronic device.

Referring to fig. 9, the electronic apparatus 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 executable by the at least one processor 901, the one or more computer programs being executable by the at least one processor 901 to enable the at least one processor 901 to perform the data processing methods described above.

Wherein the processor is a device having data processing capabilities including, but not limited to, a Central Processing Unit (CPU) or the like; memory is a device with data storage capability including, but not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically charged 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 implement information interaction between the memory and the processor, which includes, but is not limited to, a data Bus (Bus), etc.

The disclosed embodiments also provide a computer readable storage medium having a computer program stored thereon, wherein the computer program when executed by a processor/processing core implements the data method described above. The computer readable storage medium may be a volatile or nonvolatile computer readable storage medium.

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

In a hardware implementation, the division between the 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 cooperatively by several physical components.

Some or all of the physical components may be implemented as software executed by a processor, such as a Central Processing Unit (CPU), digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as known to those skilled in the art. Computer storage media includes, but is not limited to, random access memory (RAM, more particularly SDRAM, DDR, etc.), read-only memory (ROM), electrically charged erasable programmable read-only memory (EEPROM), FLASH memory (FLASH), or other magnetic disk storage; a compact disk read-only (CD-ROM), digital Versatile Disk (DVD) or other optical disk storage; magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage; any other medium that can be used to store the desired information and that can be accessed by a computer. Furthermore, as is well known to those of ordinary skill in the art, 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 includes any information delivery media.

The present disclosure has disclosed example embodiments, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purpose of limitation. In some instances, it will be apparent to one skilled in the art that features, characteristics, and/or elements described in connection with a particular embodiment may be used alone or in combination with other embodiments unless explicitly stated otherwise. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the 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.