WO2017008579A1

WO2017008579A1 - Method and device for realizing qos service

Info

Publication number: WO2017008579A1
Application number: PCT/CN2016/083035
Authority: WO
Inventors: 胡忠花
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-07-14
Filing date: 2016-05-23
Publication date: 2017-01-19
Also published as: CN106357553A; CN106357553B

Abstract

Disclosed are a method and device for realizing a QoS service, the method comprising: configuring a TRUNK port to apply for a QoS service superposition request; determining physical member ports contained in the TRUNK port; and selecting one of the determined physical member ports contained in the TRUNK port, and using a traffic management chip port corresponding thereto to access a QoS service. By means of the embodiments of the present invention, when a QoS service is accessed at a TRUNK port, a physical member port in the TRUNK port is accessed rather than using a dedicated TRUNK port resource, i.e. a logical port using a physical port, thereby saving TRUNK port hardware resources, and expanding the number of TRUNK ports that can support the QoS service.

Description

Method and device for implementing QoS service

Technical field

This document relates to, but is not limited to, the field of computer technology, and in particular, to a method and an apparatus for implementing a quality of service (QoS) service for a trunk (TRUNK) port.

Background technique

The trunk (TRUNK) technology, which is a link aggregation technology, can be implemented by binding multiple physical links into one logical link: between the server and the server, between the switch and the switch, and between the router and the router. One or more ports are connected in parallel and transmitted at the same time to increase the link bandwidth and improve the link throughput. When a link is abnormally connected, the communication can still be communicated to maximize the processing capacity of the entire network.

Quality of Service (QoS) technology, the quality of service is relative to the network service. While guaranteeing the service quality of a certain type of service, it is harming the service quality of other services, because the sum of network resources is limited, as long as there is a robbing of network resources. In the case of service quality, for example, the total bandwidth of the network is 100 megabits per second (Mbps), while the BT (bit torrent) download occupies 90 Mbps, and other services can only occupy the remaining 10 Mbps. Limiting the maximum bandwidth occupied by BT downloads is 50 Mbps, which improves the service quality of other services, enabling other services to occupy a minimum of 50 Mbps of bandwidth, but this is premised on damaging the quality of service of BT services. QoS technology is implemented on the traffic management chip.

The QOS service is implemented on the trunk port to meet the QOS requirements of the user. On the other hand, the advantages of the TRUNK port are also well reflected. As shown in Figure 1, the QOS service needs to be implemented on the TRUNK port. The interface module and the traffic management chip module are required. There is an additional TRUNK port hardware resource, that is, the number of TRUNK ports that can support QoS scheduling in the related art is limited.

Therefore, how to solve the problem that the number of the trunk ports that can support the QoS scheduling in the related art is limited is a technical problem to be solved by those skilled in the art.

Summary of the invention

The following is an overview of the topics detailed in this document. This Summary is not intended to limit the scope of the claims.

The embodiment of the invention provides a method and a device for implementing a QoS service, which can solve the problem that the number of TRUNK ports that can support QoS scheduling is limited.

An embodiment of the present invention provides a method for implementing a QoS service, which includes: configuring a TRUNK interface to apply for a QoS service overlay request; determining a physical member port included in the TRUNK interface; and selecting a physical component included in the determined TRUNK interface The member port accesses the QoS service by using its corresponding traffic management chip port.

Optionally, the one physical member port included in the selected TRUNK port accessing the QoS service by using the corresponding traffic management chip port includes:

The traffic management chip port corresponding to the selected physical member port is determined according to the correspondence between the interface module port and the traffic management chip port, and the determined use state of the traffic management chip port is set to be used by the TRUNK port, and the QoS service is used. The configuration information is written to the traffic management chip to run.

Optionally, after the accessing the QoS service, the implementation method further includes:

And the determined traffic management chip port distributes the service packet of the QoS service to the physical member port included in the TRUNK port.

The QoS service of the trunk port is released, and the usage state of the traffic management chip port corresponding to the physical member port included in the TRUNK port is set to be used by the physical member port corresponding to the traffic management chip port.

Optionally, determining the physical member ports included in the TRUNK interface includes:

Obtain the member port IDs of all physical member interfaces of the TRUNK interface.

The physical member port included in the trunk port is determined according to the obtained member port identifier.

Optionally, the implementing method further includes:

Obtain the member port ID of all physical member interfaces after the change of the TRUNK interface.

Add and/or delete physical member ports in the trunk port based on the member port IDs of all physical member interfaces.

The embodiment of the invention further provides a quality of service QoS service implementation device for a link aggregation TRUNK interface, which includes:

The configuration module is configured to configure the TRUNK interface to apply for a QoS service overlay request.

The determining module is configured to determine a physical member port included in the trunk port;

The control module is configured to select a physical member port included in the determined TRUNK port, and access the QoS service by using the corresponding traffic management chip port.

Optionally, the control module is configured to:

Optionally, the control module is further configured to:

After the QoS service is accessed, the determined traffic management chip port is configured to distribute the service packet of the QoS service to the physical member port included in the TRUNK port.

Optionally, the control module is further configured to: after accessing the QoS service, cancel the QoS service of the trunk port, and set the usage state of the traffic management chip port corresponding to the physical member port included in the TRUNK port. Used for the physical member port corresponding to the traffic management chip port.

Optionally, the determining module is configured to:

Optionally, the control module is further configured to:

Advantageous effects of embodiments of the present invention:

An embodiment of the present invention provides a method for implementing a QoS service for a trunk port. When a Trunk service is accessed by a TRUNK interface, a dedicated TRUNK port resource is used, but is accessed to a physical member port of the TRUNK port, that is, logic. The port uses the physical port, which saves the hardware resources of the trunk port and expands the number of trunk ports that can support QoS services. This solves the problem that the number of trunk ports that can support QoS scheduling in the prior art is limited.

Compared with the related art, the technical solution provided by the present invention includes: configuring a TRUNK interface to apply for a QoS service overlay request; determining a physical member port included in the TRUNK interface; selecting a physical member port included in the determined TRUNK interface, and using the corresponding The traffic management chip port accesses the QoS service. In the embodiment of the present invention, when the QoS service is accessed by the trunk port, the physical port of the logical port is used instead of the dedicated TRUNK port, and the logical port uses the physical port, which saves the hardware resources of the TRUNK port. The number of TRUNK ports that can support QoS services is expanded, which solves the problem that the number of TRUNK ports that can support QoS scheduling in the prior art is limited.

Other aspects will be apparent upon reading and understanding the drawings and detailed description.

BRIEF abstract

1 is a hardware structure diagram of a QOS service implemented by a TRUNK port in the related art;

2 is a schematic structural diagram of an apparatus for implementing a QoS service according to a first embodiment of the present invention;

3 is a flowchart of a method for implementing a QoS service according to a second embodiment of the present invention;

4 is a flowchart of a method for implementing a QoS service according to a third embodiment of the present invention;

FIG. 5 is a structural diagram of hardware implementation of a QOS service implemented by a trunk port according to a third embodiment of the present invention; FIG.

FIG. 6 is a structural diagram of a message format in a third embodiment of the present invention.

Embodiments of the invention

Embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

First embodiment:

2 is a schematic structural diagram of an apparatus for implementing a QoS service according to a first embodiment of the present invention. As shown in FIG. 2, in this embodiment, an apparatus for implementing a QoS service according to an embodiment of the present invention includes:

The configuration module 21 is configured to configure the TRUNK interface to apply for a QoS service overlay request.

The determining module 22 is configured to determine a physical member port included in the TRUNK port;

The control module 23 is configured to select a physical member port included in the determined TRUNK port, and access the QoS service by using the corresponding traffic management chip port.

Optionally, in some embodiments, the control module 23 in the foregoing embodiment is configured to: Corresponding relationship between the interface module port and the traffic management chip port, determining the traffic management chip port corresponding to the selected physical member port, setting the usage status of the determined traffic management chip port to the TRUNK port, and writing the configuration information of the QoS service The traffic management chip runs.

Optionally, in some embodiments, the control module 23 in the foregoing embodiment is further configured to: after accessing the QoS service, control the determined traffic management chip port to distribute the service packet of the QoS service to the TRUNK port. Physical member port.

Optionally, in some embodiments, the control module 23 in the foregoing embodiment is further configured to: after accessing the QoS service, cancel the QoS service of the TRUNK interface, and manage the traffic corresponding to the physical member port included in the TRUNK interface. The usage status of the chip port is set to be used by the physical member port corresponding to the traffic management chip port.

Optionally, in some embodiments, the determining module 22 in the foregoing embodiment is configured to: obtain a member port identifier of all the physical member ports of the TRUNK port; and determine a physical member port included in the TRUNK port according to the obtained member port identifier. .

Optionally, in some embodiments, the control module 23 in the foregoing embodiment is further configured to: obtain the member port identifier of all physical member interfaces after the change of the TRUNK interface; and perform the TRUNK port according to the member port identifier of all the physical member interfaces after the change. Physical member port addition and/or deletion operations.

Second embodiment:

FIG. 3 is a flowchart of a method for implementing a QoS service according to a second embodiment of the present invention. As shown in FIG. 3, in the embodiment, the QoS service implementation method provided by the embodiment of the present invention includes the following steps:

S301: Configure a trunk port to apply for a QoS service overlay request.

S302: Determine a physical member port included in the TRUNK port.

S303: Select a physical member port included in the determined TRUNK port, and access the QoS service by using the corresponding traffic management chip port.

Optionally, in some embodiments, the physical member port included in the TRUNK interface determined by the selection in the foregoing embodiment uses the corresponding traffic management chip port to access the QoS service, including: according to the interface module port and the traffic management chip. The corresponding relationship between the ports determines the traffic management chip port corresponding to the selected physical member port, sets the determined usage status of the traffic management chip port to the TRUNK port, and writes the configuration information of the QoS service to the traffic management chip.

Optionally, in some embodiments, after accessing the QoS service, the method in the foregoing embodiment further includes: controlling the determined traffic management chip port to distribute the service packet of the QoS service to the physical member included in the TRUNK interface. mouth.

Optionally, in some embodiments, after accessing the QoS service, the method in the foregoing embodiment further includes: releasing the QoS service of the TRUNK interface, and configuring the traffic management chip port corresponding to the physical member port included in the TRUNK interface. The usage status is set to be used by the physical member port corresponding to the traffic management chip port.

Optionally, in some embodiments, determining, by the foregoing embodiment, the physical member port included in the TRUNK interface includes: obtaining a member port identifier of all the physical member interfaces of the TRUNK interface, and determining, according to the obtained member port identifier, that the TRUNK port is included. Physical member port.

Optionally, in some embodiments, the method in the foregoing embodiment further includes: obtaining a member port identifier of all the physical member interfaces after the change of the TRUNK interface, and performing the physical member port of the TRUNK interface according to the member port identifier of all the physical member interfaces after the change Add and/or delete operations.

It should be noted that the QoS service implementation method in the embodiment of the present invention may be implemented by a traffic management chip.

The embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used to implement the foregoing QoS service.

The embodiments of the present invention are further explained in the context of actual application scenarios.

Third embodiment:

4 is a flowchart of a method for implementing a QoS service according to a third embodiment of the present invention. As shown in FIG. 4, the method for implementing a QoS service provided in this embodiment includes the following steps:

S401: Device initialization.

Initial state: There is no TRUNK access to the QOS service. The 10 physical member ports (physical ports) of the interface module correspond to the 10 physical ports of the traffic management chip, as shown in Table 1 below. The physical member ports of the interface module in the same row in Table 1 are in a one-to-one correspondence relationship with the traffic management chip ports.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口Traffic management chip port
物理成员口1Physical member port 1	PORT0PORT0
物理成员口2Physical member port 2	PORT1PORT1
物理成员口3Physical member port 3	PORT2PORT2
物理成员口4Physical member port 4	PORT3PORT3
物理成员口5 Physical member port 5	PORT4PORT4
物理成员口6 Physical member port 6	PORT5PORT5
物理成员口7 Physical member port 7	PORT6PORT6
物理成员口8 Physical member port 8	PORT7PORT7
物理成员口9 Physical member port 9	PORT8PORT8
物理成员口10 Physical member port 10	PORT9PORT9

Table 1

S402: The TRUNK port applies for the QOS service overlay process:

This step includes:

The configuration module configures the unique identifier (ID) of the TRUNK. For example, the TRUNK 64 adds five physical member interfaces (1, 5, 7, and 8) to the TRUNK 64, and then configures the QoS service to the TRUNK 64.

The configuration module transparently transmits the parameter TRUNK 64, the member port ID (1, 5, 7, and 8) and the QoS tree to the table management module.

The determining module transparently transmits the parameter TRUNK 64, the member port ID (1, 5, 7, 8), and the QOS tree to the control module of the traffic management chip.

After receiving the determined information, the control module of the traffic management chip sets the PORT corresponding to the physical member ports (1, 5, 7, and 8) to be unused (idle), as shown in Table 2. In the second behavior example, the usage of the traffic management chip port corresponding to the physical member port 2 is PORT1. The physical member port 2 is mapped to use the traffic management chip port PORT1 for access QoS service.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0未使用PORT0 is not used
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4未使用PORT4 is not used
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6未使用PORT6 is not used
物理成员口8 Physical member port 8	PORT7未使用PORT7 is not used
物理成员口9 Physical member port 9	PORT8使用PORT8 use
物理成员口10 Physical member port 10	PORT9使用PORT9 use

Table 2

Then, from the corresponding PORT of (1, 5, 7, 8), a PORT is traversed for TRUNK 64. The PORT 0 corresponding to the physical member port 1 is idle, and PORT0 is used as the PORT of the TRUNK 64. The usage is shown in Table 3.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0TRUNK64使用PORT0TRUNK64 use
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4未使用PORT4 is not used
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6未使用PORT6 is not used
物理成员口8 Physical member port 8	PORT7未使用PORT7 is not used
物理成员口9 Physical member port 9	PORT8使用PORT8 use
物理成员口10 Physical member port 10	PORT9使用PORT9 use

table 3

The traffic management chip control module generates the scheduler and queue information used by the QOS scheduling in the QOS tree, and backfills the queue number to the determining module, and sends the QOS configuration information to the SDK for writing to the chip.

Thereafter, the QOS scheduling is performed on PORT 0. After accessing the QOS user, all background services are also switched to PORT0. PORT0 will eventually distribute the packets to the physical member ports (1, 5, 7, and 8) of the interface module. In the related art, only the TRUNK interface can be sent to all the physical member interfaces, and the physical member interfaces cannot be distributed to other physical member interfaces. In the embodiment of the present invention, the packets of the physical member interface are encapsulated in the 4B when sent to other physical member interfaces. The header is shown in Figure 6. The 4B header is populated with the destination member port (this case will contain four types of packet headers filled with 1, 5, 7, and 8 respectively), and the message can be correctly distributed to other physical member interfaces. The physical member port implements the QOS of the TRUNK port.

In summary, the QOS takes effect on the physical member ports that are added to the TRUNK interface, which saves the hardware resources of the TRUNK part.

S403: Adding physical member ports of the TRUNK interface:

The configuration module configuration port 9 is newly added to the TRUNK64.

The configuration module transparently transmits the parameter TRUNK64 and member port IDs (1, 5, 7, 8, and 9) to the table management module.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0TRUNK64使用PORT0TRUNK64 use
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4未使用PORT4 is not used
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6未使用PORT6 is not used
物理成员口8 Physical member port 8	PORT7未使用PORT7 is not used
物理成员口9 Physical member port 9	PORT8未使用PORT8 is not used
物理成员口10 Physical member port 10	PORT9使用PORT9 use

Table 4

The determining module transparently transmits the parameter TRUNK64, the original member port ID (1, 5, 7, 8), and the new member port ID (1, 5, 7, 8, 9) to the traffic management chip control module.

The traffic management chip management module determines that the physical member 9 is to be added to the TRUNK 64 by comparing the changes of the physical member port IDs before and after. Set PORT8 corresponding to port 9 to unused (idle). The usage is shown in Table 4.

S404: Physical member port deletion of the TRUNK interface:

Configuration module configuration 7 port is deleted from TRUNK64

The configuration module transparently transmits the parameter TRUNK64 and member port IDs (1, 5, 8, and 9) to the table management module.

The determining module transparently transmits the parameter TRUNK64, the original member port ID (1, 5, 7, 8, 9) and the new member port ID (1, 5, 8, 9) to the traffic management chip control module.

The traffic management chip control module compares the changes of the member ports before and after, and determines that the 7 ports are deleted from the TRUNK64. The physical member port 7 reassigns the PORT, and the PORT4 corresponding to the 5-port traversal is marked as idle, and the PORT4 is assigned as the new PORT of the physical member port 7. The usage is shown in Table 5.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0TRUNK64使用PORT0TRUNK64 use
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4使用PORT4 use
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6未使用PORT6 is not used
物理成员口8 Physical member port 8	PORT7未使用PORT7 is not used
物理成员口9 Physical member port 9	PORT8未使用PORT8 is not used
物理成员口10 Physical member port 10	PORT9使用PORT9 use

table 5

S405: The service is released, and the TRUNK port is released:

The configuration module releases all QOS services on the TRUNK64.

The configuration module transparently transmits the parameter TRUNK64, the member port ID (1, 5, 8, and 9) and the QOS tree to the table management module.

The determining module transparently transmits the parameter TRUNK64, the member port ID (1, 5, 8, 9) and the QOS tree to the control module of the traffic management chip.

The traffic management chip control module reclaims the scheduler and queue used by the QOS scheduling, and restores the default value of the QOS parameters to the SDK for writing to the chip.

The traffic management chip management module releases PORT0 used by TRUNK64 to be idle. The usage is shown in Table 6.

接口模块的物理成员口Physical member port of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0未使用PORT0 is not used
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4使用PORT4 use
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6未使用PORT6 is not used
物理成员口8 Physical member port 8	PORT7未使用PORT7 is not used
物理成员口9 Physical member port 9	PORT8未使用PORT8 is not used
物理成员口10 Physical member port 10	PORT9使用PORT9 use

Table 6

The existing physical member ports (1, 5, 8, and 9) of TRUNK64 are assigned new PORTs. The allocation principle starts from the smallest index. The usage is shown in Table 7.

The invention implements the QOS of the TRUNK port by using the physical port member port, and saves the port hardware resources of the interface module and the traffic management chip module. In the case of limited resources, it can work well.

接口模块的物理成员Physical member of the interface module	流量管理芯片端口的使用情况Traffic Management Chip Port Usage
物理成员口1Physical member port 1	PORT0使用PORT0 use
物理成员口2Physical member port 2	PORT1使用PORT1 use
物理成员口3Physical member port 3	PORT2使用PORT2 use
物理成员口4Physical member port 4	PORT3使用PORT3 use
物理成员口5 Physical member port 5	PORT4使用PORT4 use
物理成员口6 Physical member port 6	PORT5使用PORT5 use
物理成员口7 Physical member port 7	PORT6使用PORT6 use
物理成员口8 Physical member port 8	PORT7使用PORT7 use
物理成员口9 Physical member port 9	PORT8使用PORT8 use
物理成员口10 Physical member port 10	PORT9使用PORT9 use

Table 7

Comparing FIG. 1 with FIG. 5, it can be seen that the difference in hardware between the embodiment and the related art in the implementation of the TRUNK port QOS method includes: the embodiment of the present invention saves the port resources of the interface module and the traffic management chip, so the hardware difference It is obvious that FIG. 1 is a hardware structure of a port module of a related art interface and a traffic management chip. It is assumed that ports 1 to 10 of the port module are physical ports, port 11 is a trunk port, and ports 0 to PORT 9 of the traffic management chip module are physical ports. PORT10 to PORT13 are the TRUNK ports. FIG. 5 is a schematic diagram of the hardware structure of the embodiment of the present invention. The hardware structure of the port part of the embodiment of the present invention is omitted from the TRUNK port. The interface module includes only 1 to 10 physical member ports, and the traffic management chip only Including the PORT0 to PORT9 physical ports, the hardware part of the embodiment of the present invention is simpler and more resource-saving.

The differences between the implementation methods and the related technologies in implementing the TRUNK port QOS method in the embodiments of the present invention include:

In the TRUNK interface application and the superimposed QOS service flow, the determining module transparently transmits the TRUNKID, the TRUNK physical member port ID, and the QOS tree information to the traffic management chip control module, and the related technology only needs to transparently transmit the TRUNK ID and the QOS in this step. The information management chip control module sets the PORT corresponding to all physical member ports of the trunk port to be idle, and then selects the PORT corresponding to a physical member port of the TRUNK port to be used by the TRUNK port. The port is marked for use, and TRUNK is used. In this step, the traffic management chip control module applies for a TRUNK port from the TRUNK port resource; the traffic management chip control module generates a scheduler, queue information, and configuration parameters for the QOS tree. Trigger the SDK to write to the chip. The QOS scheduling can be implemented on the TRUNK interface. After the scheduling is complete, the physical member interface of the TRUNK interface sends the packets to other physical member interfaces. The packets of the physical member interfaces of the related technologies cannot be sent to other physical member interfaces. In the embodiment of the present invention, when the packet is sent as a physical member port of the TRUNK interface, the header of the encapsulation 4B is as shown in FIG. 6, and the header of the 4B is filled with the destination physical member port.

In the process of adding and deleting physical member interfaces of the trunk port, the QOS service is online. The configuration module adds or deletes physical member interfaces. The configuration module transparently transmits the TRUNKID, the new TRUNK physical member port ID, and the QOS tree information to the determining module. In this step, the related technology only needs to transparently transmit the TRUNKID and QOS tree information; determine that the module transparently transmits the TRUNKID, the new TRUNK member port ID, the old physical member port ID, and the QOS tree information to the traffic management chip control module. In this step, only the TRUNKID and QOS tree information is transparently transmitted. The traffic management chip control module compares the ID values of the new and old physical member interfaces to determine which physical member interfaces are added and which are deleted physical member interfaces. The physical port of the member interface is set to be idle. The physical member port that is deleted from the TRUNK is reassigned. The related technology does not perform this step.

During the release of the trunk port, the configuration module configures the trunk port to release all QOS services. The configuration module transparently transmits the TRUNKID, the TRUNK physical member ID, and the QOS tree information to the determining module. The module transmits the TRUNKID, the TRUNK member ID, and the QOS tree information. To the traffic management chip control module, the related technology only needs to transparently transmit the TRUNKID and QOS tree information in this step; the traffic management chip control module triggers the SDK, the queue recovery information, the deactivation information, and the configuration information to trigger the SDK. The chip is written to the chip; the traffic management chip control module sets the physical member port corresponding to the TRUNK port to be idle, and reassigns all physical member ports of the TRUNK to the physical port. In this step, the TRUNK port resource used by the TRUNK port is released. .

In summary, through the implementation of the embodiments of the present invention, the following beneficial effects exist:

The related art traffic management chip module includes N hardware resources of the TRUNK port, and the number of TRUNK ports supporting the QOS is at most N. The disadvantage is that resources are consumed, and the port module and the traffic management chip module must reserve resources for the trunk port. When the module resources are limited, the number of TRUNK ports that can support QOS is limited, and the number of TRUNK ports that support QOS cannot be fully matched. Then, the maximum number of TRUNK ports supporting QOS can be equal to the total number of ports. In the solution of the embodiment of the present invention, when the trunk port is connected to the QOS service, the TRUNK port resource is used instead of the physical member port of the TRUNK port, that is, the logical port uses the physical port, which saves the hardware resources of the TRUNK port. And expand the number of trunk ports that can support QOS services.

The above is only an alternative embodiment of the present invention, and is not intended to limit the present invention in any way. Any simple modification, equivalent change, combination or modification of the above embodiments according to the technical essence of the present invention still belongs to The scope of protection of the technical solution of the present invention.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be performed by a program to instruct related hardware, such as a processor, which may be stored in a computer readable storage medium, such as a read only memory, disk or optical disk. Wait. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiment may be implemented in the form of hardware, for example, by implementing an integrated circuit to implement its corresponding function, or may be implemented in the form of a software function module, for example, being executed by a processor and stored in a memory. Programs/instructions to implement their respective functions. The invention is not limited to any specific form of combination of hardware and software. ”

The embodiments disclosed in the present application are as described above, but the descriptions are only for the purpose of understanding the present application, and are not intended to limit the present application, such as the specific implementation method in the embodiments of the present invention. Any modifications and changes in the form and details of the embodiments may be made by those skilled in the art without departing from the spirit and scope of the disclosure. The scope defined by the appended claims shall prevail.

Industrial applicability

The above technical solution saves the hardware resources of the trunk port and realizes the expansion of the trunk port that can support the QoS service.

Claims

A method for implementing a quality of service QoS service, where the implementation method includes:

Configure the trunk trunk port to apply for QoS service overlay request.

Determining a physical member port included in the trunk port;

Selecting a physical member port included in the determined TRUNK port, and accessing the QoS service by using its corresponding traffic management chip port.
The implementation method of claim 1, wherein the selecting a physical member port included in the determined TRUNK port to access the QoS service by using the corresponding traffic management chip port comprises:

The traffic management chip port corresponding to the selected physical member port is determined according to the correspondence between the interface module port and the traffic management chip port, and the determined use state of the traffic management chip port is set to be used by the TRUNK port, and the QoS service is used. The configuration information is written to the traffic management chip to run.
The implementation method of claim 2, after the accessing the QoS service, the implementation method further includes:

And the determined traffic management chip port distributes the service packet of the QoS service to the physical member port included in the TRUNK port.
The implementation method of claim 1, after the accessing the QoS service, the implementation method further includes:

The QoS service of the trunk port is released, and the usage state of the traffic management chip port corresponding to the physical member port included in the TRUNK port is set to be used by the physical member port corresponding to the traffic management chip port.
The implementation method of any one of claims 1 to 4, wherein the determining the physical member port included in the TRUNK port comprises:

Obtain the member port IDs of all physical member interfaces of the TRUNK interface.

The physical member port included in the trunk port is determined according to the obtained member port identifier.
The implementation method of claim 5, the implementing method further comprising:

Obtain the member port ID of all physical member interfaces after the change of the TRUNK interface.

Add and/or delete physical member ports in the trunk port based on the member port IDs of all physical member interfaces.
An apparatus for implementing a quality of service QoS service, where the implementation apparatus includes:

The configuration module is configured to configure the TRUNK interface to apply for a QoS service overlay request.

The determining module is configured to determine a physical member port included in the trunk port;

The control module is configured to select a physical member port included in the determined TRUNK port, and access the QoS service by using the corresponding traffic management chip port.
The implementation device of claim 7, wherein the control module is configured to:

The traffic management chip port corresponding to the selected physical member port is determined according to the correspondence between the interface module port and the traffic management chip port, and the determined use state of the traffic management chip port is set to be used by the TRUNK port, and the QoS service is used. The configuration information is written to the traffic management chip to run.
The implementation device of claim 8, the control module is further configured to:

After the QoS service is accessed, the determined traffic management chip port is configured to distribute the service packet of the QoS service to the physical member port included in the TRUNK port.
The implementation device of claim 7, the control module is further configured to: after accessing the QoS service, cancel the QoS service of the TRUNK port, and manage traffic corresponding to the physical member port included in the TRUNK port. The usage status of the chip port is set to be used by the physical member port corresponding to the traffic management chip port.
The implementation device according to any one of claims 7 to 10, wherein the determining module is configured to:

Obtain the member port IDs of all physical member interfaces of the TRUNK interface.

The physical member port included in the trunk port is determined according to the obtained member port identifier.
The implementation device of claim 11, the control module is further configured to:

Obtain the member port ID of all physical member interfaces after the change of the TRUNK interface.

Add and/or delete physical member ports in the trunk port based on the member port IDs of all physical member interfaces.