CN113411244A

CN113411244A - Cross-domain QoS (quality of service) adjusting method and device

Info

Publication number: CN113411244A
Application number: CN202110556529.1A
Authority: CN
Inventors: 张丽雅
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-30
Filing date: 2017-09-30
Publication date: 2021-09-17
Also published as: CN109600291A; CN109600291B

Abstract

The application provides a cross-domain QoS adjusting method and a device, wherein the method comprises the following steps: the method comprises the steps that a coordinator receives the name and the target bandwidth of a target cross-domain QoS adjustment strategy template of a service, a service access path corresponding to an access point to be adjusted in a combined VPN is determined, single-domain QoS configuration of a domain corresponding to a segmented VPN included in the service access path is determined from at least one cross-domain QoS adjustment strategy template corresponding to a service type strategy template of the service obtained in advance according to the name and the target bandwidth of the target cross-domain QoS adjustment strategy template and the domain corresponding to the segmented VPN included in the service access path, the single-domain QoS configuration is sent to a corresponding controller, and each cross-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy of a bandwidth interval in at least one domain. Therefore, QoS adjustment is carried out on the end-to-end service in a unified and automatic mode under the scene of multi-technology and multi-domain mixed coexistence.

Description

Cross-domain QoS (quality of service) adjusting method and device

The application is a divisional application of an application with application date of 09 and 30 in 2017, application number of 201710922825.2 and invented name of 'cross-domain QoS adjustment method and device' submitted to the intellectual property office of China.

Technical Field

The present application relates to communications technologies, and in particular, to a Quality of Service (QoS) adjustment method and apparatus.

Background

With the rapid growth of network services and the rapid development of communication networks, the demands of users on the networks are also increasing, and users want to obtain faster rate, lower delay, and the like. In the face of complex network and user demands, QoS is becoming a key measure of network performance. QoS is a technique used to solve problems such as network delay and congestion.

Currently, the sales pattern of network services by operators is usually reduced to packages and bandwidth, but an end-to-end service usually passes through various domains (e.g., access domain, metropolitan area and CORE (CORE) domain, etc.). The existing QoS adjustment method for a Virtual Private Network (VPN) service mainly includes: a Three-Layer VPN model (Layer Three Virtual Private Network Service. L3sm) and a Two-Layer VPN model (Layer Two Virtual Private Network Service, L2SM) proposed by The Internet Engineering Task Force (IETF). The two sub-tables describe the connection relationship between a Site (Site) and a network side Edge (PE) device in the L3VPN and the L2VPN and the QoS characteristics.

The L2SM and the L3SM describe Qos technologies of the two-layer VPN and the three-layer VPN by using different Qos models, for example, Qos parameters such as Committed Information Rate (CIR) and Committed Burst Size (CBS) are defined in L2SM, and the L3SM uses abstract bandwidth values, both of which describe only Qos requirements when the Site accesses. As an end-to-end service spans an access Network, a metropolitan Area, an IPcore domain, and the like, a scenario where multiple technologies and multiple domains coexist may occur, for example, an end-to-end service includes a Virtual Local Area Network (VLAN) technology at an access side, an L2VPN at the metropolitan Area and an L3VPN at the IPcore domain, and the defects of L3SM and L2SM cause that the end-to-end service cannot adopt a uniform QoS adjustment.

Disclosure of Invention

The application provides a cross-domain QoS adjustment method and a cross-domain QoS adjustment device, so that QoS adjustment is performed on end-to-end services in a unified and automatic mode under the scene of multi-technology and multi-domain mixed coexistence.

A first aspect of the present application provides a cross-domain QoS adjusting method, including:

receiving the name and the target bandwidth of a target cross-domain quality of service (QoS) adjustment strategy template of a service;

determining a service access path corresponding to an access point to be adjusted in a combined Virtual Private Network (VPN), wherein the service access path comprises at least one segmented VPN, each segmented VPN corresponds to a domain, and the access point to be adjusted is the access point of the service;

determining single-domain QoS configuration of a domain corresponding to a segmented VPN included in the service access path from at least one pre-acquired cross-domain QoS adjustment strategy template corresponding to the service type strategy template of the service according to the name of the target cross-domain QoS adjustment strategy template, the target bandwidth and the domain corresponding to the segmented VPN included in the service access path, wherein each cross-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy of a bandwidth interval in at least one domain;

and sending the single-domain QoS configuration of the domain corresponding to the segmented VPN included in the service access path to a corresponding controller.

Optionally, the method further includes:

receiving at least one bandwidth interval corresponding to the service input by a user and at least one domain passed by the service;

respectively generating a single-domain QoS adjustment strategy of each domain through which the service passes for each bandwidth region corresponding to the service to obtain at least one cross-domain QoS adjustment strategy;

and binding and issuing the service type strategy and the generated at least one cross-domain QoS regulation strategy.

Optionally, determining, according to the name of the target cross-domain QoS adjustment policy template, the target bandwidth, and a domain corresponding to a segment VPN included in the service access path, a single-domain QoS configuration of the domain corresponding to the segment VPN included in the service access path from at least one cross-domain QoS adjustment policy template corresponding to the service type policy template of the service, which is obtained in advance, includes:

determining the target cross-domain QoS adjustment strategy template from at least one cross-domain QoS adjustment strategy template corresponding to the service type strategy template according to the name of the target cross-domain QoS adjustment strategy template and the target bandwidth;

acquiring a single-domain QoS adjustment strategy of a domain corresponding to each segmented VPN included in the service access path according to the target cross-domain QoS adjustment strategy template;

allocating a role label of TP to a domain corresponding to each segmented VPN included in the service access path;

when the domain corresponding to the segmented VPN included on the service access path is not allocated with the role label of TP, determining the single-domain QoS configuration of the domain corresponding to the segmented VPN according to the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN;

and when the domain corresponding to the segmented VPN needs to be allocated with the role label of the TP, determining the QoS configuration of the TP on the domain corresponding to the segmented VPN according to the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN and the allocated role label of the TP.

Optionally, allocating a role label of a TP to the domain of each segment VPN included in the service access path includes:

when a fixed main domain is not arranged on the service access path, allocating a default role label user side network interface UNI for a first TP on the service access path, allocating a default role label network side network interface NNI for an inter-domain interface of a domain where the first TP is located, and allocating role labels NULL for all TPs of other domains on the service access path, wherein NULL represents that the TPs have no default role labels;

and when a fixed main domain exists on the service access path, alternately allocating default role labels UNI and NNI to all TPs on the service access path, wherein the role label of the first TP on the service access path is UNI.

Optionally, the method further includes:

and when the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN on the service access path comprises a role label strategy of TP, and the role label strategy of TP indicates that a user-defined role label is allocated to the domain, allocating the TP user-defined role label to the domain corresponding to the segmented VPN according to a domain connection relationship, wherein the priority of the user-defined role label is higher than that of the default role label.

Optionally, allocating a TP custom role label to the domain corresponding to the segment VPN according to the domain connection relationship, including:

acquiring a TP list of a domain corresponding to the segmented VPN;

reading an unprocessed TP from a TP list of a domain corresponding to the segmented VPN, and judging whether the unprocessed TP stores a next hop segmented VPN or not;

if the unprocessed TP has a next hop segmented VPN, distributing a custom role label from the segmented VPN to the next hop segmented VPN for the unprocessed TP;

if the unprocessed TP does not have a next hop segmented VPN, allocating a default role label UNI to the unprocessed TP;

and returning to the execution step: reading an unprocessed TP from the TP list of the domain corresponding to the segmented VPN, and judging whether the unprocessed TP stores the next hop segmented VPN or not until the role labels of all TPs in the TP list of the domain corresponding to the segmented VPN are distributed.

Optionally, determining a service access path corresponding to the access point to be adjusted in the combined VPN includes:

when the service has a fixed home domain, the access point is taken as a source, the fixed home domain is taken as a destination, reachable TPs from the source to the destination are calculated, and segmented VPNs passed by the reachable TPs form the service access path; alternatively, the first and second electrodes may be,

and when the service has no fixed main domain, calculating reachable TPs from the source to the destination by taking the access points as the source and the termination TPs of the service as the destination, wherein the segmented VPNs passed by the reachable TPs form the service access path.

A second aspect of the present application provides a cross-domain QoS adjusting apparatus, including:

the receiving module is used for receiving the name and the target bandwidth of a target cross-domain quality of service (QoS) adjustment strategy template of the service;

the system comprises a processing module, a Virtual Private Network (VPN) module and a Virtual Private Network (VPN) module, wherein the processing module is used for determining a corresponding service access path of an access point to be adjusted in a combined VPN, the service access path comprises at least one segmented VPN, each segmented VPN corresponds to one domain, and the access point to be adjusted is the access point of the service;

the processing module is further configured to determine, according to the name of the target cross-domain QoS adjustment policy template, the target bandwidth, and a domain corresponding to a segment VPN included in the service access path, a single-domain QoS configuration of a domain corresponding to a segment VPN included in the service access path from at least one cross-domain QoS adjustment policy template corresponding to a service type policy template of the service, which is obtained in advance, where each cross-domain QoS adjustment policy template includes a single-domain QoS adjustment policy in which a bandwidth interval is in at least one domain;

and the sending module is used for sending the single domain QoS configuration of the domain corresponding to the segmented VPN included in the service access path to the corresponding controller.

Optionally, the receiving module is further configured to receive at least one bandwidth interval corresponding to the service and input by a user, and at least one domain through which the service passes;

the processing module is further configured to generate a single-domain QoS adjustment policy for each domain through which the service passes for each bandwidth region corresponding to the service, respectively, to obtain at least one cross-domain QoS adjustment policy;

the sending module is further configured to bind and issue the service type policy and the generated at least one cross-domain QoS adjustment policy.

Optionally, the determining, by the processing module, a single-domain QoS configuration of a domain corresponding to a segment VPN included in the service access path from at least one cross-domain QoS adjustment policy template corresponding to a service type policy template of the service, which is obtained in advance, according to the name of the target cross-domain QoS adjustment policy template, the target bandwidth, and the domain corresponding to the segment VPN included in the service access path, includes:

Optionally, the allocating, by the processing module, a role label of a TP to the domain of each segment VPN included in the service access path includes:

Optionally, the processing module is further configured to:

Optionally, the allocating, by the processing module, a TP custom role label to the domain corresponding to the segment VPN according to the domain connection relationship includes:

acquiring a TP list of a domain corresponding to the segmented VPN;

Optionally, the determining, by the processing module, a service access path corresponding to the access point to be adjusted in the combined VPN includes:

when the service has a fixed main domain, the coordinator takes the access point as a source and the fixed main domain as a sink, calculates reachable TP from the source to the sink, and the segmented VPN passed by the reachable TP forms the service access path; alternatively, the first and second electrodes may be,

and when the service has no fixed home domain, the coordinator takes the access point as a source and the termination TP of the service as a sink, calculates the reachable TP from the source to the sink, and the segmented VPN passed by the reachable TP forms the service access path.

Optionally, in the method provided in the first aspect and the second aspect of the present application, the single domain QoS adjustment policy includes a QoS adjustment policy of at least one of the following levels: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy.

Optionally, the single-domain QoS adjusting policy further includes: and the role label strategy of the terminal point TP is used for indicating whether to distribute a user-defined role label for the domain.

Optionally, in the methods provided in the first aspect and the second aspect of the present application, the QoS adjustment policy at the network element level includes: the QoS adjustment strategy of the network element level of the incoming direction and the QoS adjustment strategy of the network element level of the outgoing direction, wherein the QoS adjustment strategy of the interface level comprises the following steps: the QoS adjustment policy of the ingress interface level and the QoS adjustment policy of the egress interface level, where the QoS adjustment policy of the flow level includes: a QoS adjustment strategy of an incoming direction flow level and a QoS adjustment strategy of an outgoing direction flow level.

Optionally, in the method provided in the first aspect and the second aspect of the present application, the single domain QoS configuration includes QoS configuration of at least one of the following levels: QoS configuration of network element level, QoS configuration of interface level and QoS configuration of flow level;

the QoS configuration of the TP comprises at least one of the following levels of QoS configuration: interface level QoS configuration and flow level QoS configuration.

A third aspect of the present application provides a cross-domain QoS adjusting apparatus, which includes a processor, a memory, and a transceiver, where the memory is configured to store instructions, and the transceiver is configured to communicate with other devices, and the processor is configured to execute the instructions stored in the memory, so as to cause the terminal device of the cross-domain QoS adjusting apparatus to perform the operations of the method according to the first aspect of the present application.

A fourth aspect of the present application provides a chip system, which is applied to a cross-domain QoS adjustment apparatus, and includes: at least one processor configured to execute stored instructions to cause the cross-domain QoS adjustment apparatus to perform operations of a method as described in the first aspect of the present application.

A fifth aspect of the present application provides a computer program product for use in a cross-domain QoS adjustment apparatus, the computer program product comprising instructions which, when executed by a computing apparatus, cause the cross-domain QoS adjustment apparatus to perform the operations of the method according to the first aspect of the present application.

A sixth aspect of the present application provides a computer-readable storage medium for use in a cross-domain QoS adjustment apparatus, the computer-readable storage medium storing instructions that, when executed by a computing apparatus, cause the cross-domain QoS adjustment apparatus to perform the operations of the method according to the first aspect of the present application.

The method and the device for cross-domain QoS adjustment determine a corresponding service access path of an access point to be adjusted in a combined VPN by receiving the name and the target bandwidth of a target cross-domain QoS adjustment strategy template of a service, determine single-domain QoS configuration of a domain corresponding to a segmented VPN included in the service access path from at least one cross-domain QoS adjustment strategy template corresponding to a service type strategy template of the service acquired in advance according to the name and the target bandwidth of the target cross-domain QoS adjustment strategy template and the domain corresponding to the segmented VPN included in the service access path, and send the single-domain QoS configuration to a corresponding controller, wherein each cross-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy of a bandwidth interval in at least one domain. Therefore, QoS adjustment is carried out on the end-to-end service in a unified and automatic mode under the scene of multi-technology and multi-domain mixed coexistence.

Drawings

FIG. 1 is a schematic diagram of cross-domain enterprise interconnection;

FIG. 2 is a schematic diagram of a network architecture suitable for use in the present application;

FIG. 3 is a schematic structural diagram of a QoS adjustment policy template;

fig. 4 is a flowchart of a cross-domain QoS adjustment method according to an embodiment of the present application;

fig. 5 is a flowchart of a cross-domain QoS adjustment method according to a second embodiment of the present application;

fig. 6 is a flowchart of a cross-domain QoS adjustment policy template arrangement method according to a third embodiment;

fig. 7 is a flowchart of a method for determining a service access path according to the fourth embodiment;

FIG. 8 is a flowchart illustrating a method for assigning role labels of TPs according to example five;

FIG. 9 is a diagram illustrating a scenario of cross-domain QoS adjustment;

fig. 10 is a schematic structural diagram of a cross-domain QoS adjusting apparatus according to a sixth embodiment of the present application;

fig. 11 is a schematic structural diagram of a cross-domain QoS adjusting apparatus according to a seventh embodiment of the present application.

Detailed Description

The application provides a cross-domain QoS adjusting method, which is applied to a cross-domain scene, wherein an end-to-end service in the cross-domain scene usually passes through a plurality of different domains, the plurality of different domains may be located in different countries, provinces or cities, and technologies used by the plurality of domains may be different. Fig. 1 is a schematic diagram of interconnection of cross-domain enterprises, and as shown in fig. 1, the cross-domain enterprises have four branches: branch 1, branch 2, branch 3, branch 4, each branch being a subsidiary or point of transaction. The 4 branches can be located in different countries, provinces or cities, and the like, and the 4 branches can realize mutual communication by purchasing a cross-domain combined VPN, wherein the combined VPN refers to a VPN consisting of a plurality of associated segmented VPNs, each segmented VPN corresponds to one domain, and the segmented VPNs are also called segmented VPNs.

In the example shown in fig. 1, the combined VPN comprises 6 segmented VPNs (domains): the domain access method comprises a domain A, a domain B, a domain C, a domain D, a domain E and a domain F, wherein the domain A and the domain F are metropolitan areas, the domain B is a core domain, and the domain E is an access domain. The service from branch 1 to branch 4 needs to pass through domain a, domain B, domain F and domain E in turn, when the service passes through each domain, each domain includes two Termination Points (TP), the TP is a network interface, in the example shown in fig. 1, the TP passed through in turn is TP1, TP2 … …, TP8, TP7 and TP8 belong to domain a, TP5 and TP6 belong to domain B, TP3 and TP4 belong to domain F, and TP1 and TP2 belong to domain E, wherein domain a adopts optical transport network-Ethernet Virtual Private Line (OTN-EVPL) technology, domain B adopts L3VPN technology, domain F adopts L2VPN technology, and domain E adopts VLAN technology.

The cross-domain enterprise interconnection shown in fig. 1 mainly has the following problems:

(1) managing scribing: the method comprises four domains, namely a domain A, a domain B, a domain F and a domain E, of which the branches 1 to 4 are accessed, wherein different domains are respectively located in different cities, provinces or countries, and Qos adjustment strategies of each domain need to be designed independently and are different.

(2) Technical scribing: the techniques used by the domains of the branch 1-branch 4 approach vary, and are exemplary: the technology used in the Access domain includes Ethernet Passive Optical Network (EPON)/Gigabit Passive Optical Network (GPON)/Customer Premise Equipment (CPE), etc., the technology used in the metro area includes Access Network IP (Internet Protocol Radio Access Network, IPRAN), Optical Transport Network (OTN), etc., and the technology used in the CORE domain includes Optical CORE, IP CORE, and Qos adjustment strategies required by each technology are different.

(3) QoS complexity and Multi-Vendor (MV) capabilities: the cross-domain service under the cross-domain scene relates to equipment of multiple manufacturers, the equipment of each manufacturer has different capabilities, the QoS self parameters are various and difficult to unify, and the cross-domain service refers to the service passing through multiple domains.

(4) Path dynamics: due to different locations of branches of enterprises, access points and service access paths are different, QoS adjustment strategies of all access paths cannot be fully planned, and different paths lead to different QoS linkage strategies.

(5) Client appeal intellectualization: when a customer requires to adjust the grade and the Bandwidth of the branch 1, the Demand is simple, the TP of each domain needs to be adjusted in a segmented mode during actual adjustment, the adjustment complexity is high, maintenance is difficult, and self-help Bandwidth-on-Demand (BOD) of tenants cannot be achieved.

In order to solve the above problems in the cross-domain scenario, the present application provides a cross-domain QoS adjusting method, fig. 2 is a schematic diagram of a network architecture applicable to the present application, and as shown in fig. 2, the network architecture includes three layers of models: a Service Model Level (Service Model Level), a Network Model Level (Network Model Level), and a Network element Model Level (Network element Model Level). The service model layer describes the end-to-end network seen by the user, such as the full connectivity (L3 vpnfulllmsh) L3VPN service of branch 1 to branch 4 of fig. 1. The network element of the service model layer is an Orchestrator (or), the Orchestrator is mainly responsible for decomposing an end-to-end cross-domain QoS adjustment policy of the service model layer into network-level QoS configuration of each domain, the network element of the network model layer is a Controller (Controller), and the Controller is mainly responsible for decomposing the network-level QoS configuration into network-level QoS configuration.

Optionally, as shown in fig. 2, the coordinator includes a service template design module and a service instance management module, where the service template design module includes three sub-modules, a service type template design sub-module, a universe QoS template management sub-module, and a QoS adjustment policy design sub-module. The business type template design submodule is used for designing a business type strategy template according to the characteristics of the business types sold by the operators, and the business type strategy template comprises business type strategies. The global QoS template management submodule has the following two main functions: and acquiring QoS data in the single domain from a controller, and creating a single-domain QoS adjustment strategy template according to the acquired QoS data in the single domain, wherein the single-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy. The QoS adjustment strategy design submodule is used for generating a cross-domain QoS adjustment strategy template for the end-to-end service according to the data of the service type template design submodule and the universe QoS template management submodule.

Fig. 3 is a schematic structural diagram of a QoS adjustment policy template, and as shown in fig. 3, each service type policy corresponds to one or more cross-domain QoS adjustment policy templates, where a service type policy includes a service type, a service definition, and other related information of a service, and each cross-domain QoS adjustment policy template includes a single-domain QoS adjustment policy whose bandwidth interval is in at least one domain. Each single domain QoS policy includes one or more of the following: the QoS regulation strategy of the network element level in the incoming direction, the QoS regulation strategy of the network element level in the outgoing direction, the QoS regulation strategy of the interface level in the incoming direction, the QoS regulation strategy of the interface level in the outgoing direction, the QoS regulation strategy of the flow level in the incoming direction, the QoS regulation strategy of the flow level in the outgoing direction and the role label strategy of TP.

The service instance management module comprises a cross-domain service distribution submodule, a cross-domain BOD submodule and a cross-domain service path calculation submodule, wherein the cross-domain service distribution submodule is used for carrying out cross-domain service distribution, the cross-domain BOD submodule is used for cross-domain BOD, the cross-domain service path calculation submodule is used for calculating a service access path of the cross-domain service when the service is distributed or the cross-domain BOD is carried out, and single-domain QoS configuration of each domain is determined according to a single-domain QoS adjustment strategy of each domain passed by the service access path.

The controller comprises a single-domain QoS adjustment strategy template management module and a single-domain service instance management module, wherein the single-domain QoS adjustment strategy template management module is used for: and acquiring QoS data in a single domain from the network elements of each domain, managing a single-domain QoS adjustment strategy template and managing a network element level QoS adjustment strategy template. The single domain service instance management module is used for single domain service distribution and single domain BOD, and decomposing the single domain QoS configuration into the Qos configuration of the network element level when the service or the BOD is distributed.

The network element comprises a QoS adjustment strategy template management module at the network element level and a single-station service instance management module, wherein the QoS adjustment strategy template management module at the network element level is used for managing the QoS adjustment strategy template at the network element level, and the single-station service instance management module is used for issuing single-station services and BOD (body of Integrated design).

Referring to fig. 3, the whole network is composed of three layers of a coordinator, a controller and a network element (router). The coordinator provides a defined interface of the cross-domain QoS adjustment strategy for an Operator (Operator) through an independent Restful interface, and provides an interface for a Tenant (Tenant) to specify the name and the bandwidth of a cross-domain QoS adjustment strategy template when service subscription and BOD are carried out. The coordinator and the controller are in butt joint through a Restful/Netconf interface, and the controller and the router layer are in mutual communication through a Netconf/Cli/Snmp interface.

Based on the cross-domain scenario shown in fig. 1 and the network architectures shown in fig. 2 and fig. 3, the cross-domain QoS adjustment method provided by the present application aims to solve the problem that the prior art cannot implement cross-domain QoS adjustment of an end-to-end service.

The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The several exemplary embodiments may be combined, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.

Fig. 4 is a flowchart of a cross-domain QoS adjusting method provided in an embodiment of the present application, where the method provided in this embodiment is executed by a cross-domain QoS device, and the cross-domain QoS device may be a coordinator or other devices, as shown in fig. 4, the method of this embodiment includes the following steps:

step S101, receiving the name and the target bandwidth of the target cross-domain QoS adjustment strategy template of the service.

The name and target bandwidth of the target cross-domain QoS adjustment policy template for the traffic may be input or selected by the tenant at the time of the service issuance or BOD. The name of the target cross-domain QoS adjustment policy template may be gold, silver, platinum, etc., for example. One service defines one or more cross-domain QoS adjustment policy templates, where the target cross-domain QoS adjustment policy template belongs to one or more cross-domain QoS adjustment policy templates corresponding to the service, and each cross-domain QoS adjustment policy template corresponds to a bandwidth interval, where the bandwidth interval may be, for example, 10-20M, 20-30M, and the like. The bandwidth interval comprises discrete values or continuous interval values, and the target bandwidth input by the tenant is required to be within the bandwidth interval. If the bandwidth interval is a discrete value, the tenant can only input the appointed discrete bandwidth value. If the bandwidth interval is a continuous interval value, the tenant may enter all values within this range.

And step S102, determining a corresponding service access path of the access point to be adjusted in the combined VPN.

The service access path comprises at least one segmented VPN, each segmented VPN corresponds to a domain, and the access point to be adjusted is the access point of the service. The combined VPN is a private network purchased or leased in a combined mode, the combined VPN comprises a plurality of segmented VPNs, and each segmented VPN corresponds to one domain. When the service is accessed to the combined VPN through different access points, service access paths corresponding to the service are different, the service access path refers to a set of segmented VPNs through which the service passes in the combined VPN, and the number of the segmented VPNs included in the service access path may be one or more. For a certain service, the tenant may designate to adjust all access points in the combined VPN, or may designate to adjust a certain access point, and if the tenant does not designate an access point, the tenant defaults to adjust all access points in the combined VPN, and the access point that needs to be adjusted is the access point to be adjusted. Taking the scenario shown in fig. 1 as an example, the user may specify to adjust the aps of branch 1 and branch 4, or may specify to adjust the aps of all branches, where the ap of branch 1 is TP8, the ap of branch 4 is TP1, and the aps of branch 2 and branch 4 are not labeled.

The service access path comprises a source and a sink, the source of the service access path is an access point of the service, and the sink of the service access path can be the access point or a fixed main domain of the service. A service may or may not have a fixed home domain. If the service has a fixed main domain, the destination of the access path of the service is the fixed main domain of the service. If the service has no fixed home domain, the service access path is hosted as an access point (end point of an end-to-end service). The main domain refers to a domain for bearing single domain service with the end-to-end characteristic of the combined VPN, which single domain service strategy is the main domain service strategy is specified in the single domain service strategy in the service definition stage, and the domain where the main domain service strategy is located is the main domain.

After determining the source and the destination of the service access path, determining the reachable path from the source to the destination, wherein the domain to which all TPs passed by the reachable path belong is the service access path. In the example shown in FIG. 1, where the source is TP1 and the sink is TP2, the reachable path passes through 8 TPs: TP8 … … TP1, TP7 and TP8 belong to domain a, TP5 and TP6 belong to domain B, TP3 and TP4 belong to domain F, and TP1 and TP2 belong to domain E, so that the traffic access path passes through four domains in total: domain a, domain B, domain F and domain E.

Step S103, according to the name of the target cross-domain QoS adjustment strategy, the target bandwidth and the domain corresponding to the segmented VPN included in the service access path, determining the single-domain QoS configuration of the domain corresponding to the segmented VPN included in the service access path from at least one cross-domain QoS adjustment strategy template corresponding to the service type strategy template of the service acquired in advance.

The cross-domain QoS adjustment strategy template of the service can be pre-arranged by the coordinator, or loaded to the coordinator after being arranged by an operator. Each service defines at least one cross-domain QoS adjustment strategy template, each cross-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy of a bandwidth interval in at least one domain, wherein the bandwidth intervals corresponding to different cross-domain QoS adjustment strategy templates are different, the domains included in different cross-domain QoS adjustment strategy templates are the same, but the single-domain QoS adjustment strategies of the domains may be different. For example, service 1 defines two cross-domain QoS adjustment policy templates: the system comprises a gold-level cross-domain QoS adjustment strategy template and a platinum-level cross-domain QoS adjustment strategy template, wherein a bandwidth interval corresponding to the gold-level cross-domain QoS adjustment strategy template is 10-20M, a bandwidth interval corresponding to the platinum-level cross-domain QoS adjustment strategy template is 20-30M, the two cross-domain QoS adjustment strategy templates respectively comprise three domains (such as an access domain A, a core domain B and a metropolitan area C), and single-domain QoS adjustment strategies of all the domains included in the two cross-domain QoS adjustment strategy templates are different.

Optionally, the single domain QoS adjustment policy includes a QoS adjustment policy of at least one of the following levels: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy. One network element includes multiple interfaces, and one interface can carry multiple different streams, i.e., network interfaces. The QoS adjustment policy at the network element level is applicable to all interfaces on the network element, and the coordinator defines the same QoS adjustment policy for all interfaces. The QoS adjustment policy of the interface level is only applicable to a certain interface, and the coordinator may define different QoS adjustment policies for different interfaces. The QoS adjustment policies at the flow level are applicable to flows, data on one interface may correspond to different flows, and the coordinator may define different QoS adjustment policies for different flows. The embodiment is merely an example, and the single domain QoS adjustment policy may further include other levels of QoS adjustment policies.

Optionally, the QoS adjustment policies for the ingress direction and the egress direction of the same domain may be different or the same. If the QoS adjustment strategies of the incoming direction and the outgoing direction of the same domain are the same, the incoming direction and the outgoing direction do not need to be defined, and if the QoS adjustment strategies of the incoming direction and the outgoing direction of the same domain are different, the incoming direction and the outgoing direction need to be defined. Correspondingly, the QoS adjustment policy at the network element level includes: the QoS adjustment strategy of the network element level of the incoming direction and the QoS adjustment strategy of the network element level of the outgoing direction, the QoS adjustment strategy of the interface level comprises: the QoS adjustment strategy of the ingress direction interface level and the QoS adjustment strategy of the egress direction interface level, the QoS adjustment strategy of the flow level comprises: a QoS adjustment strategy of an incoming direction flow level and a QoS adjustment strategy of an outgoing direction flow level.

Optionally, the single-domain QoS adjustment policy further includes: a role label policy of the TP, the role label policy of the TP to indicate whether to assign a custom role label for the domain.

The method comprises the steps that a coordinator finds a target cross-domain QoS adjustment strategy template from at least one cross-domain QoS adjustment strategy template of a service according to the name and the target bandwidth of the target cross-domain QoS adjustment strategy template, the target cross-domain QoS adjustment strategy template comprises single-domain QoS adjustment strategies of a plurality of domains, the single-domain QoS adjustment strategies of the domains corresponding to the segmented VPNs included in a service access path are obtained further according to the domains corresponding to the segmented VPNs included in the service access path, the single-domain QoS adjustment strategies of the domains corresponding to the segmented VPNs are decomposed respectively, and single-domain QoS configuration of the domains corresponding to the segmented VPNs is obtained. Taking the example shown in fig. 1 as an example, the service access path includes domains corresponding to 4 segmented VPNs: the target cross-domain QoS adjustment policy template includes single-domain QoS adjustment policies of 6 domains shown in fig. 1, and the coordinator decomposes the single-domain QoS adjustment policies of the domain a, the domain B, the domain F, and the domain E, respectively, to obtain single-domain QoS configurations of the domain a, the domain B, the domain F, and the domain E.

The single domain QoS configuration for each domain includes QoS configuration of at least one of the following levels: network element level QoS configuration, interface level QoS configuration, and flow level QoS configuration. One network element includes multiple interfaces, and one interface can carry multiple different streams, i.e., network interfaces. The QoS configuration at the network element level is applicable to all interfaces on the network element, for example, if the network element a includes 5 interfaces, the QoS configuration of all data carried on the 5 interfaces is the same. The QoS configuration at the interface level applies to all data carried on that interface, e.g. a network element comprises 5 interfaces, the QoS configuration of different interfaces may be different, and the same or different flows carried on each interface use the QoS configuration of that interface. The QoS configuration at the flow level applies to flows, data on one interface may correspond to different flows, and different flows use different QoS configurations.

The QoS adjustment policies for the ingress and egress directions of the same domain may be different or the same, and correspondingly, when the QoS adjustment policies for the ingress and egress directions of the same domain are different, the single-domain QoS configuration also includes the ingress and egress directions. The QoS configuration of the network element level comprises QoS configuration of an in-direction network element level and QoS configuration of an out-direction network element level, the QoS configuration of the interface level comprises QoS configuration of an in-direction interface level and QoS configuration of an out-direction interface level, and the QoS configuration of the flow level comprises QoS configuration of an in-direction flow level and QoS configuration of an out-direction flow level.

Optionally, the single domain QoS configuration further includes a QoS configuration of a TP, and the QoS configuration of the TP includes a QoS configuration of at least one of the following levels: interface level QoS configuration and flow level QoS configuration.

Step S104, the single domain QoS configuration of the domain corresponding to the segmented VPN included in the service access path is sent to the corresponding controller.

Assume that the service access path passes through four domains in total: the coordinator sends the single domain QoS configuration of the domain A to the controller of the domain A, sends the single domain QoS configuration of the domain B to the controller of the domain B, sends the single domain QoS configuration of the domain F to the controller of the domain F, and sends the single domain QoS configuration of the domain E to the controller of the domain E. There may be one controller for each domain, or one controller may be shared by multiple domains.

After receiving the single-domain QoS configuration, the controller decomposes the single-domain QoS configuration into QoS configuration at network element level, i.e. decomposes the single-domain QoS configuration into network elements in the domain, and sends the QoS configuration of each network element to the network elements.

In this embodiment, a name and a target bandwidth of a target cross-domain QoS adjustment policy template of a service are received, a service access path corresponding to an access point to be adjusted in a combined VPN is determined, a single-domain QoS configuration of a domain corresponding to a segment VPN included in the service access path is determined from at least one cross-domain QoS adjustment policy template corresponding to a service type policy template of the service, which is obtained in advance, according to the name and the target bandwidth of the target cross-domain QoS adjustment policy template and a domain corresponding to the segment VPN included in the service access path, and the single-domain QoS configuration is sent to a corresponding controller, where each cross-domain QoS adjustment policy template includes a single-domain QoS adjustment policy of a bandwidth interval in at least one domain. Therefore, QoS adjustment is carried out on the end-to-end service in a unified and automatic mode under the scene of multi-technology and multi-domain mixed coexistence.

Fig. 5 is a flowchart of a cross-domain QoS adjusting method provided in an embodiment two of the present application, where this embodiment is a detailed description of an implementation manner of step S103 in the embodiment one, and as shown in fig. 5, the method provided in this embodiment includes the following steps:

step S201, according to the name and the target bandwidth of the target cross-domain QoS adjustment policy template, determining the target cross-domain QoS adjustment policy template from at least one cross-domain QoS adjustment policy template corresponding to the service type policy template.

Each cross-domain QoS adjustment policy template includes a single-domain QoS adjustment policy of a bandwidth interval in at least one domain, and the single-domain QoS adjustment policy refers to the description related to the first embodiment, which is not described herein again.

Step S202, according to the target cross-domain QoS adjustment strategy template, acquiring a single-domain QoS adjustment strategy of a domain corresponding to each segmented VPN included in the service access path.

Step S203, allocating a role label of TP to the domain corresponding to each segment VPN included in the service access path.

The role labels of the TPs include: the role self-definition role tags comprise default role tags and user-defined role tags, and the priority of the user-defined role is higher than that of the default role or not. The default role label is allocated to a certain domain and is autonomously determined by the coordinator, and whether a user-defined role label is allocated to the certain domain or not is indicated by a single-domain QoS (quality of service) adjustment strategy. The default roles include User-Network Interface (UNI) and Network-Network Interface (NNI).

The service access path comprises a plurality of segmented VPNs, domains corresponding to some segmented VPNs may only be allocated with default role labels, domains corresponding to some segmented VPNs may only be allocated with custom role labels, domains corresponding to some segmented VPNs may be allocated with default role labels and custom role labels, and domains corresponding to some segmented VPNs may not be allocated with default role labels and custom role labels.

Step S204, judging whether the domain corresponding to each segmented VPN included in the service access path is allocated with the role label of TP.

When the domain corresponding to the segment VPN included in the service access path does not have the role label of TP assigned, step S205 is executed, and when the domain corresponding to the segment VPN included in the service access path has the role label of TP assigned, step S206 is executed.

Step S205, according to the single domain QoS adjustment strategy of the domain corresponding to the segmented VPN, determining the single domain QoS configuration of the domain corresponding to the segmented VPN.

Step S206, determining the QoS configuration of the TP on the domain corresponding to the segmented VPN according to the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN and the role label of the allocated TP.

In this embodiment, when the role labels of two TPs in a single domain are different, the QoS configurations of the two TPs are also different, where the QoS configurations of the TPs include QoS configurations of at least one of the following levels: interface level QoS configuration and flow level QoS configuration. Optionally, if QoS configurations of an ingress direction and an egress direction of the same TP are different, the QoS configuration at the interface level includes: ingress interface level QoS configuration and egress interface level QoS configuration, the flow level QoS configuration comprising: QoS configuration at the ingress flow level and QoS configuration at the egress flow level.

In this embodiment, a target cross-domain QoS adjustment policy template is determined from at least one cross-domain QoS adjustment policy template corresponding to a service type policy template according to a name and a target bandwidth of the target cross-domain QoS adjustment policy template, a role label of TP is allocated to a domain corresponding to each segment VPN included in a service access path, and when a domain corresponding to a segment VPN included in the service access path is not allocated with a role label of TP, a coordinator determines a single-domain QoS configuration of a domain corresponding to the segment VPN according to a single-domain QoS adjustment policy of the domain corresponding to the segment VPN; when the domain corresponding to the segmented VPN is allocated with the role label of the TP, the coordinator determines the QoS configuration of the TP on the domain corresponding to the segmented VPN according to the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN and the allocated role label of the TP. Therefore, the intelligent flexible cross-domain QoS adjustment of the end-to-end service is realized.

On the basis of the first embodiment and the second embodiment, before the method is executed, at least one cross-domain QoS adjustment policy template corresponding to a service type policy template of a service is acquired, a third embodiment of the present application provides an arranging method for the cross-domain QoS adjustment policy template, fig. 6 is a flowchart of the arranging method for the cross-domain QoS adjustment policy template provided by the third embodiment, and as shown in fig. 6, the method provided by the present embodiment includes the following steps:

step S301, receiving at least one bandwidth interval corresponding to a service input by a user and at least one domain passed by the service.

The bandwidth interval corresponding to the service and the domain passed by the service are planned by the operator according to the service requirement and are provided to the coordinator through an interface on the coordinator, and the bandwidth interval corresponding to different services and the domain passed by different services may be different.

Step S302, generating single-domain QoS adjustment strategies of each domain through which the service passes for each bandwidth region corresponding to the service respectively to obtain at least one cross-domain QoS adjustment strategy.

Each bandwidth interval corresponds to a cross-domain QoS adjustment strategy, and when a single-domain QoS adjustment strategy of each domain through which a service passes is generated for each bandwidth interval, the coordinator can generate at least one level QoS adjustment strategy for each domain respectively according to the collected intra-domain QoS data. For example, the bandwidth interval corresponding to the service includes the following two intervals: 10-20M and 20-30M, the domains that the service passes through are three: and the access domain A, the core domain B and the metropolitan area C generate at least one level QoS adjustment strategy in the access domain A, the core domain B and the metropolitan area C for a bandwidth interval of 10-20M, and then generate at least one level QoS adjustment strategy in the access domain A, the core domain B and the metropolitan area C for a bandwidth interval of 20-30M. The at least one level of QoS adjustment policy includes: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy.

After at least one level of QoS adjustment policy is generated for each domain, optionally, a role label policy of TP may be further generated for each domain, where the role label policy of TP is used to indicate whether to allocate a custom role label for the domain.

Step S303, binding and issuing the service type strategy and the generated at least one cross-domain QoS regulation strategy.

On the basis of the first to third embodiments, a fourth embodiment of the present application provides a method for determining a service access path, that is, this embodiment is a description of a specific implementation manner of the step S102 and the step S202, and fig. 7 is a flowchart of the method for determining a service access path provided by the fourth embodiment, as shown in fig. 7, the method provided by this embodiment includes the following steps:

step S401, judging whether the service has a fixed main domain.

Illustratively, whether a service has a fixed home domain may be indicated by a service definition in a service type policy. Step S402 is performed when the service has a fixed home domain, and step S403 is performed when the service has no fixed home domain.

Step S402, with the access point as the source and the fixed main domain as the sink, the reachable TP from the source to the sink is calculated, and the segmented VPN passed by the reachable TP forms a service access path.

Since the service has a fixed home domain, the adjustment of QoS affects the TP from the access point to the fixed home domain, and therefore, the service access path needs to be calculated with the access point as a source and the fixed home domain as a sink.

The reachable TP from source to sink can be determined as follows: starting from a source, inquiring whether the source has a direct connection segmented VPN, if the source has the direct connection segmented VPN, bringing the segmented VPN into a reachable path set, bringing all TPs in the segmented VPN except the source into an unsearched TP set, and continuing searching. Assume that the direct-connected segmented VPN of the source has two TPs in addition to the source: TP2 and TP3 determine whether TP2 and TP3 have direct-connection segmented VPNs, respectively.

And if the source does not have the direct connection segmented VPN, inquiring the next hop segmented VPN through the inter-domain connection relation, if the next hop segmented VPN exists, incorporating the next hop segmented VPN into the reachable path set, and incorporating all TPs except the entered TP in the next hop segmented VPN into the unsearched TP set. And executing the method on all the TPs in the unsearched set to obtain the accessible TPs. The next-hop segment VPN refers to another segment VPN to which the TP is connected through a Link (Link), and the direct-connection segment VPN refers to a segment VPN to which the TP is connected through a service relationship and the VPN (that is, the segment VPN in which the TP is located).

Step S403, with the access point as the source and the termination TP of the service as the sink, the reachable TP from the source to the sink is calculated, and the segmented VPN through which the reachable TP passes forms the service access path.

Since the service has no fixed main domain, the QoS adjustment affects all the end-to-end TPs of the service, and therefore, it is necessary to calculate a service access path using a boundary point of the service as a source and a sink, and an access point of the service and a termination TP of the service are both boundary points of the service.

On the basis of the second embodiment, a fifth embodiment of the present application provides a method for assigning a role label of a TP, that is, this embodiment describes a specific implementation manner of step S203 in the second embodiment, and fig. 8 is a flowchart of the method for assigning a role label of a TP, which is provided in the fifth embodiment, and as shown in fig. 8, the method provided in this embodiment includes the following steps:

step S501, judging whether the service has a fixed main domain.

Illustratively, whether a service has a fixed home domain may be indicated by a service definition in a service type policy. Step S502 is performed when the service has a fixed home domain, and step S503 is performed when the service has no fixed home domain.

And step S502, allocating default role labels UNI and NNI for all TPs on the service access path alternately.

The default role label of the first TP on the service access path is UNI, and assuming that there are 4 TPs on the service access path, the role labels of the 4 TPs are TP1(UNI) -TP2(NNI) -TP3(UNI) -TP4(NNI) in sequence.

Step S503, a default role label UNI is allocated to the first TP on the service access path, a default role label NNI is allocated to the inter-domain interface of the domain where the first TP is located, and a role label NULL is allocated to all TPs of other domains on the service access path.

That is, the coordinator allocates a default role label only to a domain (also referred to as an access domain) corresponding to the first segment VPN on the service access path, and does not allocate a default role label to a domain (also referred to as a forwarding domain) corresponding to other segment VPNs on the service access path, where NULL indicates that the TP has no default role label.

Step S504, when the single domain QoS adjustment strategy of the domain corresponding to the segmented VPN on the service access path comprises the role label strategy of TP, and the role label strategy of TP indicates that the domain is allocated with the self-defined role label, the domain corresponding to the segmented VPN is allocated with the TP self-defined role label according to the domain connection relationship.

Step S504 is an optional step, and if the role label policy of the TP included in the single domain QoS adjustment policy of a certain domain indicates that no custom role label is assigned to the domain, the coordinator does not perform step S504. Or, the operator only defines the default role tag for the service, and does not define the custom role tag for the service, the coordinator does not execute step S504.

The custom role labels are defined in terms of inter-domain connectivity, e.g., A, B two domains with a connectivity between a and B, then domain a may define a role label towards domain B: ab, domain B may define a role label, ba, toward domain a. Illustratively, the coordinator allocates TP custom role labels to domains corresponding to the segmented VPNs according to the following manner:

the method comprises the steps of obtaining a TP list of a domain corresponding to the sectional VPN, wherein the TP list of the domain corresponding to the sectional VPN comprises a plurality of TPs, reading an unprocessed TP from the TP list of the domain corresponding to the sectional VPN, judging whether the unprocessed TP stores a next hop sectional VPN, if the unprocessed TP stores the next hop sectional VPN, distributing a self-defined role label from the sectional VPN to the next hop sectional VPN for the unprocessed TP, if the unprocessed TP does not store the next hop sectional VPN, distributing a default role label UNI for the unprocessed TP, and traversing the TP list of the domain corresponding to the sectional VPN sequentially according to the method until the role labels of all TPs in the TP list of the domain corresponding to the sectional VPN are distributed. The next-hop segment VPN refers to another segment VPN to which the TP is connected through a Link (Link).

Fig. 9 is a schematic diagram of a scenario of cross-domain QoS adjustment, as shown in fig. 9, where an enterprise has branch 1 in city a and branch 2 in city B, and the enterprise purchases a cross-domain enterprise private line, where the cross-domain enterprise private line includes 5 segmented VPNs: VPN1 to VPN5, where VPN1 corresponds to an access domain, VPN2 corresponds to an ONT domain, VPN3 corresponds to an IP CORE domain, VPN4 corresponds to an OTN domain, VPN5 corresponds to a switch domain, a service access path passes through the above 5 segmented VPNs, and a service access path passes through 10 TPs: TP1 to TP 10. The cross-domain QoS adjustment strategy corresponding to the service comprises the following steps: the TP1 configures a QoS adjustment strategy of a flow level, the TP2 is not limited by speed, the TP3/TP4/TP7/TP8 is used for limiting speed of a port level, the TP5/TP6 is used for limiting speed of the port level and the flow level, the TP9 is configured with the QoS adjustment strategy of the port level, and the TP10 is configured with the QoS adjustment strategy of the flow level. The operator designs two cross-domain Qos adjustment strategy templates for the service, wherein the names of the two cross-domain Qos adjustment strategy templates are gold levels, and the adjustable bandwidth intervals are respectively [10M, 10M ], [20M and 30M ].

The cross-domain QoS adjusting method mainly comprises the following two processes: (1) arranging a cross-domain QoS adjustment strategy template; (2) and the decomposition process of the cross-domain QoS adjustment strategy is completed by the coordinator.

The arranging process of the cross-domain QoS adjustment strategy template can comprise the following steps:

(1.1) the operator determines the service type, such as enterprise private line, and determines the name, such as gold level, of the cross-domain QoS adjustment strategy template corresponding to the service type.

And (1.2) determining a bandwidth interval list for the cross-domain Qos adjustment strategy template. For example, two bandwidth intervals are determined: 10M, 20M, 30M), allowing the customer to select a bandwidth of 10M, or any value between 20M and 30M.

And (1.3) generating a single-domain QoS adjustment strategy of all domains for each bandwidth interval. For example, the bidirectional QoS adjustment policy for the OTN domain is generated as follows: only the interface level QoS adjustment policy is included.

And (1.4) if the role label of the TP needs to be distinguished in the single domain, generating a role label strategy of the TP, wherein the role label strategy of the TP comprises first indication information, and the first indication information is used for indicating whether the role label is allocated to the TP of the domain. For example, if the QoS adjustment policies of TP1 and TP2 of the access domain are different, the first indication information is generated, and a type of role label may be generated, where the role label is, for example, a default role label: UNI/NNI.

The decomposition process of the cross-domain QoS adjustment strategy can comprise the following steps:

(2.1) the tenant inputs or selects the name and bandwidth value of the cross-domain QoS adjustment policy template at the time of service release or Bod.

Illustratively, the cross-domain QoS adjustment policy is converted into the configuration of the access point according to the name and bandwidth value of the cross-domain QoS adjustment policy template input by the tenant, and if the QoS is adjusted for the entire combined VPN, the cross-domain QoS adjustment policy is converted into the QoS configuration parameters of all the access points under the entire combined VPN. For example, adjust branch 1 to gold 21M, then switch to TP1 to gold 21M.

And (2.2) calculating a service access path by taking the access point TP1 as a source and taking the main domain as a sink. In the scenario shown in fig. 9, the service has a fixed home domain, where the IP CORE is the fixed home domain.

(2.3) putting TP1 into the search set, wherein TP1 directly connects the segmented VPNs into segmented VPNs 1, and the segmented VPNs 1 are included in the service access path. An unsearched TP (i.e., TP2) is placed in the search set, TP1 is marked as processed, and then it is determined whether TP2 has a direct-connected segmented VPN. Since TP2 does not have a direct segment VPN, the next hop segment VPN, segment VPN2, is found. Segment VPN2 is included in the traffic access path and boundary TP3 of VPN2 is included in the search set. Repeatedly executing the steps until the fixed main domain is reached, and obtaining a service access path as follows: in the VPN1-VPN2-VPN3, TPs passing through a service access path sequentially comprise: TP1-TP2-TP3-TP4-TP 5.

And (2.4) allocating a role label for the TP on the service access path according to the first indication information because the cross-domain QoS adjustment strategy template comprises the first indication information. For example: TP1(UNI) -TP2(NNI) -TP3(UNI) -TP4(NNI) -TP5 (UNI).

(2.5) determining a bandwidth interval to which the tenant input bandwidth belongs, for example, the bandwidth interval to which 21M belongs is [20M, 30M ], determining a target cross-domain QoS adjustment policy template according to the name of the cross-domain QoS adjustment policy template and the bandwidth interval, and determining a QoS adjustment policy of each TP in the service access path according to the role label of the TP of each domain. For example, TP1 belongs to an access domain, the role label is UNI, a Qos adjustment policy that TP1 needs to configure the flow level can be found in the target cross-domain Qos adjustment policy, and TP2 does not configure the Qos adjustment policy.

And (2.6) determining the QoS configuration of each TP in the service access path according to the QoS adjustment strategy of each TP in the service access path.

And (2.7) sending the QoS configuration of each TP to the corresponding controller. Illustratively, according to the controller in the domain where the TP is located sending the QoS configuration of the TP, for example, TP1, TP2 belonging to the access domain, finding the controller 1 corresponding to the access domain, and sending the QoS configuration of TP1 and TP2 to the controller 1. After receiving the QoS configuration of the TP, the controller decomposes the QoS configuration of the TP into network element level configuration and sends the network element level configuration to a corresponding network element.

Fig. 10 is a schematic structural diagram of a cross-domain QoS adjusting apparatus according to a sixth embodiment of the present application, and as shown in fig. 10, the cross-domain QoS adjusting apparatus according to the present embodiment includes:

a receiving module 11, configured to receive a name and a target bandwidth of a target cross-domain quality of service QoS adjustment policy template of a service;

a processing module 12, configured to determine a service access path corresponding to an access point to be adjusted in a combined virtual private network VPN, where the service access path includes at least one segment VPN, each segment VPN corresponds to a domain, and the access point to be adjusted is an access point of the service;

the processing module 12 is further configured to determine, according to the name of the target cross-domain QoS adjustment policy template, the target bandwidth, and a domain corresponding to a segment VPN included in the service access path, a single-domain QoS configuration of a domain corresponding to a segment VPN included in the service access path from at least one cross-domain QoS adjustment policy template corresponding to a service type policy template of the service, where each cross-domain QoS adjustment policy template includes a single-domain QoS adjustment policy of a bandwidth interval in at least one domain;

a sending module 13, configured to send the single domain QoS configuration of the domain corresponding to the segment VPN included in the service access path to the corresponding controller.

Optionally, the single domain QoS adjustment policy includes a QoS adjustment policy of at least one of the following levels: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy.

Optionally, the QoS adjustment policy at the network element level includes: the QoS adjustment strategy of the network element level of the incoming direction and the QoS adjustment strategy of the network element level of the outgoing direction, wherein the QoS adjustment strategy of the interface level comprises the following steps: the QoS adjustment policy of the ingress interface level and the QoS adjustment policy of the egress interface level, where the QoS adjustment policy of the flow level includes: a QoS adjustment strategy of an incoming direction flow level and a QoS adjustment strategy of an outgoing direction flow level.

Optionally, the receiving module 11 is further configured to receive at least one bandwidth interval corresponding to the service and input by a user, and at least one domain through which the service passes; the processing module 12 is further configured to generate, for each bandwidth region corresponding to the service, a single-domain QoS adjustment policy for each domain through which the service passes, respectively, to obtain at least one cross-domain QoS adjustment policy; the sending module 13 is further configured to bind and issue the service type policy and the generated at least one cross-domain QoS adjustment policy.

Optionally, the processing module 12 determines, according to the name of the target cross-domain QoS adjustment policy template, the target bandwidth, and a domain corresponding to the segment VPN included in the service access path, a single-domain QoS configuration of the domain corresponding to the segment VPN included in the service access path from at least one cross-domain QoS adjustment policy template corresponding to the service type policy template of the service, which is obtained in advance, specifically:

Optionally, the single domain QoS configuration includes QoS configuration of at least one of the following levels: QoS configuration of network element level, QoS configuration of interface level and QoS configuration of flow level; the QoS configuration of the TP comprises at least one of the following levels of QoS configuration: interface level QoS configuration and flow level QoS configuration.

Optionally, the processing module 12 allocates a role label of a TP to the domain of each segment VPN included in the service access path, specifically: when a fixed main domain is not arranged on the service access path, allocating a default role label user side network interface UNI for a first TP on the service access path, allocating a default role label network side network interface NNI for an inter-domain interface of a domain where the first TP is located, and allocating role labels NULL for all TPs of other domains on the service access path, wherein NULL represents that the TPs have no default role labels; and when a fixed main domain exists on the service access path, alternately allocating default role labels UNI and NNI to all TPs on the service access path, wherein the role label of the first TP on the service access path is UNI.

Optionally, the processing module 12 is further configured to: and when the single-domain QoS adjustment strategy of the domain corresponding to the segmented VPN on the service access path comprises a role label strategy of TP, and the role label strategy of TP indicates that a user-defined role label is allocated to the domain, allocating the TP user-defined role label to the domain corresponding to the segmented VPN according to a domain connection relationship, wherein the priority of the user-defined role label is higher than that of the default role label.

Optionally, the allocating, by the processing module 12, a TP custom role label to the domain corresponding to the segment VPN according to the domain connection relationship includes: acquiring a TP list of a domain corresponding to the segmented VPN, reading an unprocessed TP from the TP list of the domain corresponding to the segmented VPN, judging whether the unprocessed TP stores a next hop segmented VPN, and if the unprocessed TP stores the next hop segmented VPN, allocating a user-defined role label from the segmented VPN to the next hop segmented VPN for the unprocessed TP; if the unprocessed TP does not have a next hop segmented VPN, allocating a default role label UNI to the unprocessed TP; and returning to the execution step: reading an unprocessed TP from the TP list of the domain corresponding to the segmented VPN, and judging whether the unprocessed TP stores the next hop segmented VPN or not until the role labels of all TPs in the TP list of the domain corresponding to the segmented VPN are distributed.

Optionally, the determining, by the processing module 12, a service access path corresponding to the access point to be adjusted in the combined VPN includes: when the service has a fixed main domain, the coordinator takes the access point as a source and the fixed main domain as a sink, calculates reachable TP from the source to the sink, and the segmented VPN passed by the reachable TP forms the service access path; or, when the service has no fixed home domain, the coordinator uses the access point as a source and the termination TP of the service as a sink, calculates a reachable TP from the source to the sink, and a segmented VPN through which the reachable TP passes forms the service access path.

The cross-domain QoS adjusting apparatus of this embodiment may be configured to perform the methods shown in the first to fifth embodiments, and the specific implementation manner and the technical effect are similar, and are not described herein again.

Fig. 11 is a schematic structural diagram of a cross-domain QoS adjusting apparatus provided in a seventh embodiment of the present application, and as shown in fig. 11, the cross-domain QoS adjusting apparatus provided in this embodiment includes a processor 21, a memory 22, and a transceiver 23, where the memory 22 is used to store instructions, the transceiver 23 is used to communicate with other devices, and the processor 21 is used to execute the instructions stored in the memory 22, so that the terminal device of the cross-domain QoS adjusting apparatus executes the methods shown in the first to fifth embodiments, and specific implementation manners and technical effects are similar, and are not described again here.

It is understood that the processor used in the network device or the terminal device in the present application may be a Central Processing Unit (CPU), a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others.

The bus described herein may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Claims

1. A cross-domain quality of service (QoS) adjusting method is characterized by comprising the following steps:

acquiring single domain QoS configuration corresponding to at least one domain included in a service access path according to an identifier of a target cross-domain QoS adjustment strategy template of the service and the service access path, wherein the service access path includes at least one segment of path, and each segment of path corresponds to one domain;

and sending the single-domain QoS configuration corresponding to at least one domain included in the service access path to a corresponding controller.

2. The method of claim 1, wherein an identification of the target cross-domain QoS adjustment policy template is used to indicate the target cross-domain QoS adjustment policy template, and wherein the identification comprises: template name, template number, and/or template index information.

3. The method according to claim 1 or 2, wherein the traffic access path is determined by an access point to be adjusted, the access point to be adjusted being an access point for the traffic.

4. The method of claim 3, wherein the traffic access path is a path corresponding to the access point to be adjusted in a combined Virtual Private Network (VPN), and wherein the traffic access path comprises at least one segment VPN, and each segment VPN corresponds to a domain.

5. The method according to any one of claims 1 to 4, wherein the method for obtaining the single domain QoS configuration corresponding to at least one domain included in the service access path according to the service access path and the identifier of the target cross-domain QoS adjustment policy template of the service comprises:

acquiring a target cross-domain QoS adjustment strategy template of a service according to the identification of the target cross-domain QoS adjustment strategy template of the service and a target bandwidth, wherein the target cross-domain QoS adjustment strategy template comprises a single-domain QoS adjustment strategy of a bandwidth interval corresponding to the target bandwidth in at least one domain;

acquiring a single domain QoS adjustment strategy corresponding to at least one domain according to the at least one domain corresponding to the path included in the service access path;

and acquiring single-domain QoS configuration corresponding to at least one domain according to the single-domain QoS adjustment strategy corresponding to the at least one domain.

6. The method of claim 4, wherein the single domain QoS adjustment policy comprises a QoS adjustment policy of at least one of the following levels: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy.

7. The method of claim 4 or 6, wherein the single domain QoS adjustment policy further comprises: and the role label strategy of the terminal point TP is used for indicating whether to distribute a user-defined role label for the domain.

8. The method of claim 6, wherein the network element level QoS adjustment policy comprises: the QoS adjustment strategy of the network element level of the incoming direction and the QoS adjustment strategy of the network element level of the outgoing direction, wherein the QoS adjustment strategy of the interface level comprises the following steps: the QoS adjustment policy of the ingress interface level and the QoS adjustment policy of the egress interface level, where the QoS adjustment policy of the flow level includes: a QoS adjustment strategy of an incoming direction flow level and a QoS adjustment strategy of an outgoing direction flow level.

9. The method according to any one of claims 1-8, further comprising:

10. The method according to any one of claims 1-5, further comprising:

and determining the target cross-domain QoS adjustment strategy template from at least one cross-domain QoS adjustment strategy template corresponding to the service type strategy template of the service according to the name of the target cross-domain QoS adjustment strategy template and the target bandwidth.

11. The method according to claim 4 or 5, wherein the method for obtaining the single domain QoS adjustment policy corresponding to at least one domain according to the at least one domain corresponding to the path included in the service access path comprises: and acquiring a single-domain QoS adjustment strategy of a domain corresponding to the segmented VPN included in the service access path according to the target cross-domain QoS adjustment strategy template and the domain corresponding to each segmented VPN included in the service access path.

12. The method according to claim 4 or 5, wherein the method for obtaining the single-domain QoS configuration corresponding to at least one domain according to the single-domain QoS adjustment policy corresponding to at least one domain comprises: allocating a role label of TP to a domain corresponding to each segmented VPN included in the service access path;

13. The method of claim 12, wherein the single domain QoS configuration comprises QoS configuration of at least one of the following levels: QoS configuration of network element level, QoS configuration of interface level and QoS configuration of flow level;

14. The method of claim 12, wherein assigning a role label of TP to the domain of each segment VPN included in the service access path comprises:

15. The method of claim 14, further comprising:

16. The method of claim 15, wherein assigning TP custom role labels to the domains corresponding to the segmented VPNs according to domain connection relationships comprises:

acquiring a TP list of a domain corresponding to the segmented VPN;

17. The method according to any of claims 1-8 and 13-16, wherein determining the corresponding traffic access path of the access point to be adjusted in the combined VPN comprises:

18. A cross-domain quality of service, QoS, adjustment apparatus, the apparatus comprising:

a processing module, configured to obtain a single domain QoS corresponding to at least one domain included in a service access path according to an identifier of a target cross-domain QoS adjustment policy template of the service and the service access path, configure the service access path to include at least one segment of path, where each segment of path corresponds to one domain;

and the sending module is used for sending the single domain QoS configuration corresponding to at least one domain included in the service access path to the corresponding controller.

19. The apparatus of claim 18, wherein an identification of the target cross-domain QoS adjustment policy template is used to indicate the target cross-domain QoS adjustment policy template, and wherein the identification comprises: template name, template number, and/or template index information.

20. The apparatus of claim 18, wherein the traffic access path is determined by an access point to be adjusted, and wherein the access point to be adjusted is an access point for the traffic.

21. The method of claim 20, wherein the traffic access path is a path corresponding to the access point to be adjusted in a combined Virtual Private Network (VPN), and wherein the traffic access path comprises at least one segment VPN, and wherein each segment VPN corresponds to a domain.

22. The apparatus of claim 18, wherein the processing module obtains, according to the identifier of the target cross-domain QoS adjustment policy template of the service and the service access path, a single-domain QoS configuration corresponding to at least one domain included in the service access path, includes:

23. The apparatus of claim 18, further comprising:

and the receiving module is used for receiving the identification of the target cross-domain QoS (quality of service) adjustment strategy template of the service and the target bandwidth.

24. The apparatus of claim 22, wherein the single domain QoS adjustment policy comprises a QoS adjustment policy of at least one of the following levels: a network element level QoS adjustment strategy, an interface level QoS adjustment strategy and a flow level QoS adjustment strategy.

25. The apparatus of claim 22 or 24, wherein the single domain QoS adjustment policy further comprises: and the role label strategy of the terminal point TP is used for indicating whether to distribute a user-defined role label for the domain.

26. The apparatus of claim 24, wherein the network element level QoS adjustment policy comprises: the QoS adjustment strategy of the network element level of the incoming direction and the QoS adjustment strategy of the network element level of the outgoing direction, wherein the QoS adjustment strategy of the interface level comprises the following steps: the QoS adjustment policy of the ingress interface level and the QoS adjustment policy of the egress interface level, where the QoS adjustment policy of the flow level includes: a QoS adjustment strategy of an incoming direction flow level and a QoS adjustment strategy of an outgoing direction flow level.

27. The apparatus of any one of claims 18-26,

the receiving module is further configured to receive at least one bandwidth interval corresponding to the service and input by a user, and at least one domain through which the service passes;

28. The apparatus of any one of claims 18-27, wherein the processing module is further configured to:

and determining the target cross-domain QoS adjustment strategy template from at least one cross-domain QoS adjustment strategy template corresponding to the service type strategy template according to the name of the target cross-domain QoS adjustment strategy template and the target bandwidth.

29. The apparatus according to claim 21 or 22, wherein the obtaining, by the processing module, the single-domain QoS adjustment policy corresponding to at least one domain according to the at least one domain corresponding to the path included in the service access path includes:

and acquiring a single-domain QoS adjustment strategy of a domain corresponding to the segmented VPN included in the service access path according to the target cross-domain QoS adjustment strategy template and the domain corresponding to each segmented VPN included in the service access path.

30. The apparatus according to claim 21 or 22, wherein the obtaining, by the processing module, the single-domain QoS configuration corresponding to the at least one domain according to the single-domain QoS adjustment policy corresponding to the at least one domain comprises:

31. The apparatus of claim 30, wherein the single domain QoS configuration comprises QoS configuration of at least one of the following levels: QoS configuration of network element level, QoS configuration of interface level and QoS configuration of flow level;

32. The apparatus of claim 30, wherein the processing module assigns a role label of TP to each domain of segment VPNs included in the service access path, comprising:

33. The apparatus of claim 32, wherein the processing module is further configured to:

34. The apparatus of claim 33, wherein the processing module assigns TP custom role labels to the domains corresponding to the segmented VPNs according to domain connection relationships, comprising:

acquiring a TP list of a domain corresponding to the segmented VPN;

35. The apparatus according to any of claims 18-26 and 31-34, wherein the processing module determines the corresponding traffic access path of the access point to be adjusted in the combined VPN, comprising: