AU2003255114A1

AU2003255114A1 - Network management method based on quality of the service

Info

Publication number: AU2003255114A1
Application number: AU2003255114A
Authority: AU
Inventors: Erping Kou; Qiao Li; Nian Wang; Anyuan Xiong; Bo Xu
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2002-09-23
Filing date: 2003-08-13
Publication date: 2004-04-08
Anticipated expiration: 2023-08-13
Also published as: CN1270476C; AU2003255114B2; BRPI0314671B1; CN1486019A; WO2004028082A1; BR0314671A

Description

VERIFICATION OF TRANSLATION International Patent Application No. PCT/CN2003/00067 2 I, lizeyan of UNITALEN ATTORNEYS AT LAW am the translator of the document attached and I state that the following is a true translation to the best of my knowledge and belief of International Patent Application No. PCT/CN2003/00067 2 filed on August 13, 2003. DATED this 22 day of March , 2005 (Signature of trans tor) -- am -- r,-,4- RAel, Aanmere qrnfav\004818290 Printed 22 March 2005 (14:34) page 1 OP040141 (original)

--

NETWORK MANAGEMENT METHOD BASED ON QUALITY OF SERVICE Field of the Invention The present invention relates to a network management method, 5 particularly to a network management method based on Quality of Service (QoS). Background of the Invention In today' s broadband metropolitan area network, usually the 10 entire network comprises a device on the access layer, a device on the convergence layer, a device on the backbone layer, and a network management platform. When traffics are provided through the network, an IDC (Internet Data Center, which provides network content service) is also required to provide 15 specific service features. To manage the users, usually a user management platform (e.g., radius server (authentication and accounting server) or another similar device) is also necessary; Unified management and accounting for the network users is carried out through a special authentication and accounting 20 protocol (radius protocol: Remote Authentication Dial-In User Service, RFC2865 and RFC2866) between the platform and the network devices and between the platform and the IDC. In the traditional Internet Protocol (IP) network, all messages are treated identically; each router treats all 25 messages with FIFO policy, it exerts its best-effort to send the messages to the destinations, but doesn't provide any guarantee for the message transmission performance (e.g., reliability, delay, etc.) . As new applications over IP network emerge increasingly, such as VoIP (Voice over IP), OP040141 (original) -2 videoconference, Virtual Private Network (VPN), crucial data traffics, they put forth new requirements for the QoS of IP network. The best-effort services of traditional IP network can't meet the demand of these applications. For instance, users 5 are intolerant to overlong time delay of massage transmission for VoIP service. Comparatively speaking, common access services such as electrical mail (email) and File Transfer Protocol (FTP) are insensitive to time delay. QoS means different QoS levels to different demands, for example, 10 decreasing message loss rate, avoiding and managing network congestion, flow shaping, setting message priority, and other network application requirements. Usually, different user types have different requirements for QoS. To reach the mutual agreement on the requirements of 15 the user and actual implementation of QoS in the network, a service level agreement (SLA) has to be signed between the user and the Internet Service Provider (ISP), which covering bandwidth allocation, time delay range, and message priority, etc. In a policy-based network, to control network devices on 20 different layers effectively so as to set parameters related with QoS as specified in the SLA, a special platform called policy server (PS) is necessary, which incoperates with the device on network backbone layer and convergence layer through a special protocol (Common Open Policy Service (COPS) , RFC2748) 25 to apply for and issue QoS policies. Since the user management, traffic management, and network QoS management are distributed on different devices, the incorporation between the existing network QoS technology and the actual applications is not so tight. Due to the design OP040141 (original) -3 drawback, means for uniform mutual interaction between service control devices and network control devices is unavailable, resulting in difficulty in unified management and control of network QoS and users and thus hindering further development 5 of the broadband network. In addition, the complexity of the policy server and its protocol and processing flow not only aggravates network load but also makes it impossible to manage under-layer devices (e.g., L2 switch); therefore, in some degree, the policy server is still unable to ensure satisfactory 10 end-to-end QoS. Sunmary of the Invention An object of the present invention is to provide a network management method based on QoS, which can incorporate network 15 QoS management with user management and traffic management organically to improve network QoS and efficiency. To attain said object, the network management method based on QoS according to the present invention comprises the following steps: 20 step 1: an authentication and accounting server (radius server) customizing a corresponding QoS policy for a specific network application; step 2: a user applying for a required priority level of QoS from an Internet Data Center (IDC) and providing traffic 25 selection information; the IDC storing the information and forwarding the information to the radius server; step 3: the radius server authenticating the user and determining a QoS policy for the user according to the user's attribute and the applied traffic type, and, during exchanging OP040141 (original) -4 user authentication information with the device on the convergence layer, sending the specific QoS policy to the device on the convergence layer, and configuring the device on the convergence layer with the QoS policy, while the device on the 5 convergence layer configuring the device on the access layer with the QoS policy; step 4: the radius server cooperating with the device on the access layer, the convergence layer and the backbone layer to provide service for the user according to the user traffic 10 type with the pre-customized QoS policy. The user applying for required priority level of QoS from the IDC in step 2 is accomplished through the portal page layout provided by the IDC. Said step 3 further comprises the following steps: 15 step 31: the radius server determining the QoS policy for the user according to the traffic selection information from user and the pre-customized QoS policy for the traffic type, sending the policy and the corresponding port information of the device to the device on the convergence layer, and 20 configuring the user with the accounting policy according to the user's private information and the applied service; step 32: after receiving the policy and the corresponding port information of the device, the device on the convergence layer configuring the corresponding QoS processing mode on the 25 corresponding device port, and sending the QoS policy for configuring the user's corresponding port and priority sign to the L2 device; step 33: the device on the convergence layer and the device on the access layer returning an acknowledgement message to the OP040141 (original) -5 device on upper layer respectively to indicate the QOS policy is configured successfully; the device on the backbone layer performing queue dispatching directly according to the priority sign assigned for the IP packets by the device on the convergence 5 layer, and then, after all of the devices are configured successfully, carrying out the specific service; at the same time, the radius server beginning to perform accounting for the user according to the configured accounting policy. Said step 31 further comprises: if the service for the user 10 is a bi-directional one, sending the QoS policy provided for the user to the device on the convergence layer where the called party is. Configuring the corresponding QoS processing mode on the corresponding device port in step 32 comprises: configuring a 15 traffic stream classifying rule used to distinguish the traffic of the specific user, and configuring the QoS policy for the traffic. In step 32, if the user terminal sets the priority of the QoS policy by itself, the corresponding user port will be 20 configured to trust the user traffic as high priority. The present invention utilizes the radius server in the traditional network to customize corresponding QoS policy for a specific network application, which comprises: determining a QoS policy for the user according to the user' s attribute and 25 the traffic type applied during authentication of the user, and sending the specific QoS policy to the device on the convergence layer and the access layer, and finally, according to the user traffic, cooperates with the device on the access layer, the convergence layer, and the backbone layer to provide the service OP040141 (original) -6 for the user utilizing the pre-customized QoS policy; said solution can not only take full advantage of existing network devices and simplify the policy configuration process but also incorporates traffic management with network management. In the 5 actual implementation, to achieve close incorporation between network QoS policy configuration and network QoS, only trivial modification to the software is required instead of adding special and expensive policy servers; in addition, the solution supports management down to the access layer; therefore, it 10 overcomes the disadvantage of traditional policy server (i.e., only supports management on the convergence layer and the backbone layer) , improves utilization rate of network devices, and protects networking investment of the operator on a certain degree, so that the operator can seek for new business 15 opportunities for the network and therefore promotes network development; it can be seen that the present invention can incorporate network QoS management with user management and traffic management organically and improve network QoS and efficiency. 20 Brief Description of the Drawings Fig.1 is the flow diagram of an embodiment of the method according to the present invention; Fig.2 is the structural diagram of a network implemented 25 with the method of the present invention. Detailed Description of the Embodiments The present invention in its nature is to utilize the existing devices (e.g., radius server and broadband access OP040141 (original) -7 server (BAS)) in the network to incorporate network QoS management with user and traffic management organically through an interaction flow for QoS policy-related information, in order to avoid the complex control mode of policy server, 5 decrease network complexity, and solve the problems resulted from separation between service and control. Hereunder the present invention will be described with reference to the attached drawings. Fig.2 is the structural diagram of a network implemented 10 with the method of the present invention. As shown in Fig.2, the backbone layer is usually implemented with a Gigabits switch router (GSR) by mesh connections, and the network shall have high-capacity, high-speed, high-efficiency, and powerful routing capability; the access layer shall employ low-cost 15 devices as far as possible, such as L2 switch, ADSL (Asymmetric Digital Subscriber Loop) access devices, etc., which shall be easy to manage and highly adaptive to the environment; the convergence layer, as the demarcation between L2 and L3 in the MAN, shall have intelligent feature and user management 20 capability, and is the key to implement network management feature based on QoS. The IDC provide specific services for the entire network, including e-mail server, Video On Demand server, etc. Fig.1 is the flow diagram of an embodiment of the method 25 of the present invention; Implementing the present invention according to Fig.1 requires the following steps: step 1: expanding the radius server as a traffic management platform, and then customizing a corresponding QoS policy for a specific network application; during the policy customization process, OP040141 (original) -8 a QoS level shall be determined first according to the user's attribute and the traffic type, then, a corresponding QoS policy shall be determined according to the QoS level, with reference to various factors including the user traffic type, the applied 5 bandwidth, the upper and lower limits of bandwidth, the jitter, the service priority, the traffic monitoring parameters, the service available duration, whether the service is bidirectional, and the corresponding accounting policy, etc.; usually, different services require specific accounting 10 policies; even the same service may require different accounting policies if there are different service levels or service hours configured for it. When a user accesses the network, the broadband access server (BAS) on the convergence layer performs fundamental 15 Network access authentication for the user and then assigns a network address for the user, so that the user obtains the basic authority for network access; at the same time, the user's fundamental network access information is logged on the traffic management platform. With the default access control rules 20 configured on the BAS, any user traffic is treated on the "bast-effort" principle. If the user requires QoS guarantee from the service provider (i.e., IDC), the user applies for a service authority from IDC through the portal page layout provided by IDC in step 2. From the page layout, the user chooses 25 an expected QoS service mode, e.g., QoS level, and inputs the corresponding user name and password, and then provides the requested service; BAS forwards the obtained user's private information, the traffic selection information, and the device port connecting the user to the IDC. The IDC stores above OP040141 (original) -9 information, and forwards the information to the radius server. In step 3, the radius server authenticates the user, determines the QoS policy for the user according to the user's attribute and the applied traffic type, and sends the QoS policy to the 5 BAS device on the convergence layer when exchanging the user's authentication information with the device on the convergence layer, and configures the BAS device on the convergence layer with the QoS policy accordingly; the BAS configures the device on the access layer with the QoS policy, corresponding to the 10 service, customized for it, e.g., configures priority of the corresponding user access port, priority of the corresponding user traffic, etc.; finally, in step 4, the radius server cooperates the devices on the access layer, the convergence layer and the backbone layer to provide the service for the user 15 utilizing the pre-customized QoS policy. In above process, it is necessary to determine whether the user applying for QoS is a legal one in either of the following two ways: 1) the IDC determines whether the user is a legal one according to the user subscription information; if so, the IDC 20 sends the user authentication message, along with the information about the chosen traffic type and the device port connecting the user, to the radius server via the interface between the IDC and the radius server; 2) the IDC doesn't perform authentication for the user, instead, it sends all of the user 25 information to the radius server directly, which compares the received information with the recorded subscription user information to determine whether the user is a legal one. If the user has passed the authentication successfully at the IDC or the radius server, the radius server determines a OP040141 (original) -10 QoS policy for the user according to the traffic selection information obtained from IDC, with reference to the QoS policy (e.g., the bandwidth required for VoD service, the time delay, and the priority parameters) for the traffic type 5 pre-customized on the traffic management platform, and sends the policy and the corresponding device port information to the BAS, along with the radius message for authentication acknowledgement. If the service requires bidirectional traffic streams (e.g., video-conference), the traffic 10 management platform will also send a similar policy to the BAS device for the called party. At the same time, the radius server will set an accounting policy for the user according to the user's private information and the applied service. When receiving above policy, the BAS on the convergence 15 layer may configure a corresponding QoS processing mode on the corresponding device port, e.g., set down traffic classifying rules to distinguish traffic from a specific user and set down the QoS policy (e.g., the bandwidth limitation, the mode for modifying priority sign, the mode for processing breaching 20 traffic, etc.) for the traffic. The BAS on the convergence layer sends the QoS policy for setting the port and priority sign (e.g., set high priority for the traffic from/to the port) to the device on L2 (i.e., access layer) ; if the user terminal sets the priority of the QoS policy 25 by itself, the traffic of the trusted user from the corresponding port may be set as a high priority. If the QoS policy is sent and configured successfully, the device on the convergence layer (i.e., BAS) and the device on the access layer returns an acknowledgement message to the OP040141 (original) -11 device on upper layer respectively to indicate the QOS policy has be configured successfully; the device on the backbone layer doesn't perform any specific configuration for the user, instead, it performs queue dispatching directly according to 5 the priority sign set for the IP packets by the device on the convergence layer; then, when all of the devices are configured successfully, the service will be provided, and the radius server will carry out accounting for the user according to the established accounting policy. 10 When the service is over (e.g., the user disconnects, the user is short of deposit, or the service terminates automatically (e.g. , the movie demanded by the user terminates) , or the service time limit has been reached), the radius server informs the device on the convergence layer to delete the QoS 15 policy related with the user, and, at the same time, terminates the QoS treatment for the user traffic stream. In addition, the device on the convergence layer informs the L2 switch to delete the relevant QoS policy at the port. If the QoS policy is deleted successfully, the devices on the layers will return an 20 acknowledgement for QOS policy deletion to the devices on upper layers, respectively. The traffic management platform will perform accounting for the user according to the user type, the traffic type (bandwidth, priority, etc.) , and the corresponding accounting policy. If the accounting is to be performed by the 25 BAS, the traffic management platform will also inform the BAS of terminating the accounting, besides sending the message to delete the QoS policy.

Claims

1. A network management method based on Quality of Service QoS, comprising the following steps: 5 step 1: an authentication and accounting server, radius server customizing corresponding QoS policies for a specific network application; step 2: a user applying for a required priority level of QoS from an Internet Data Center IDC and providing traffic 10 selection information; the IDC storing the information and forwarding the information to the radius server; step 3: the radius server authenticating the user and determining a QoS policy for the user according to the user's attribute and the applied traffic type, and, during exchanging 15 user authentication information with the device on the convergence layer, sending the specific QoS policy to the device on the convergence layer, and configuring the device on the convergence layer with the QoS policy, while the device on the convergence layer configuring the device on the access layer 20 with the QoS policy; step 4: the radius server cooperating with the device on the access layer, the convergence layer and the backbone layer to provide service for the user according to the user traffic type with the pre-customized QoS policy. 25

2. The network management method based on QoS according to claim 1, wherein the user applying for the required priority level of QoS from the IDC in step 2 is accomplished through the portal page layout provided by the IDC.

3. The network management method based on QoS according to OP040141 (original) -13 claim 2, wherein said step 3 further comprises the following steps: step 31: the radius server determining the QoS policy for the user according to the traffic selection information from 5 user and the pre-customized QoS policy for the traffic type, sending the policy and the corresponding port information of the device to the device on the convergence layer, and configuring the user with the accounting policy according to the user's private information and the applied service; 10 step 32: after receiving the policy and the corresponding port information of the device, the device on the convergence layer configuring the corresponding QoS processing mode on the corresponding device port, and sending the QoS policy for configuring the user's corresponding port and priority sign to 15 the L2 device; step 33: the device on the convergence layer and the device on the access layer returning an acknowledgement message to the device on upper layer respectively to indicate the QOS policy is configured successfully; the device on the backbone layer 20 performing queue dispatching directly according to the priority sign assigned for the IP packets by the device on the convergence layer, and then, after all of the devices are configured successfully, carrying out the specific service; at the same time, the radius server beginning to perform accounting for the 25 user according to the configured accounting policy.

4. The network management method based on QoS according to claim 3, wherein said step 31 further comprises: if the service for the user is a bi-directional one, sending the QoS policy provided for the user to the device on the convergence layer OP040141 (original) -14 where the called party is.

5. The network management method based on QoS according to claim 3, wherein configuring the corresponding QoS processing mode on the corresponding device port in step 32 comprises: 5 configuring a traffic stream classifying rule used to distinguish the traffic of the specific user, and configuring the QoS policy for the traffic.

6. The network management method based on QoS according to claim 3, wherein in step 32, if the user terminal sets the 10 priority of the QoS policy by itself, configuring the priority of the traffic of the trusted user from the corresponding port as a high priority.

7. The network management method based on QoS according to claim 30, 4, 5 or 6, also comprising: when the service is over, 15 e.g., the user disconnects, the user is short of deposit, the service terminates automatically, or the service time limit has been reached, the radius server informing the device on the convergence layer to delete the QoS policy related with the user, and terminating the QoS treatment for the user traffic stream. 20

8. The network management method based on QoS according to claim 7, also comprising: when the service is over, the device on the convergence layer informing the device on the access layer to delete the QoS policy related with the service.

9. The network management method based on QoS according to 25 claim 8, also comprising: if the accounting is performed by the BAS, the radius server also informing the BAS to terminate the accounting when sending a message for QoS policy deletion to the BAS.

10. The network management method based on QoS according OP040141 (original) -15 to claim 9, wherein said device on the convergence layer is a broadband access server BAS; said device on the access layer is a L2 network switch.