CN110278118A - End-to-end service quality assurance system - Google Patents

Abstract

The present invention provides an end-to-end service quality assurance system, including a first-level business orchestrator deployed on a national core cloud, and a second-level business orchestrator deployed on a provincial/prefecture-level core cloud, wherein the first-level service orchestrator The service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and the secondary service orchestrator are respectively connected to Internet SP/CP clients; the primary service orchestrator and the secondary service orchestration The first-level service scheduler and/or the second-level service scheduler obtains scheduling instructions in response to the service request of the Internet SP/CP client; the first-level service scheduler and/or the second-level service scheduler responds to all The orchestration instruction acquires a QoS configuration policy corresponding to the service request, and delivers the QoS configuration policy to the terminal. This solution can carry out the whole network, cross-layer and cross-domain, end-to-end, multi-service, fast and efficient QoS quality assurance through the first-level service orchestrator and the second-level service orchestrator.

Description

End-to-end service quality assurance system

technical field

The invention relates to Internet technology, in particular to an end-to-end service quality assurance system.

Background technique

With the rapid development of mobile Internet, users have higher and higher requirements for mobile Internet service quality and wired network service quality in mobile scenarios, and as business development continues to pose more challenges to the network, business traffic increases This leads to increased network load, slow network response, insufficient link bandwidth, and increasing investment in capacity expansion.

The quality of service guarantee in the prior art is based on segmentation, and a certain segment of the network is guaranteed by using the backbone network, metropolitan area network or mobile network segmentation guarantee mechanism, wherein the guarantee mechanism is based on hop-by-hop behavior control. .

However, the quality of service assurance of the prior art is not efficient enough.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide an end-to-end service quality assurance system, which makes the end-to-end service quality assurance more efficient.

A first aspect of the embodiments of the present invention provides an end-to-end service quality assurance system, including a first-level service orchestrator deployed on a national core cloud, and a second-level service orchestrator deployed on a provincial/prefecture-level core cloud , and a fixed-mobile integrated bearer network deployed on the edge cloud, wherein the primary service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and the secondary service orchestrator are respectively connected to the the Internet SP/CP client; the first-level service scheduler and the second-level service scheduler are respectively connected to terminals;

The primary service orchestrator and/or the secondary service orchestrator obtains orchestration instructions in response to the service request of the Internet SP/CP client;

The primary service scheduler and/or the secondary service scheduler, in response to the orchestration instruction, obtains a QoS configuration policy corresponding to the service request, and delivers the QoS configuration policy to the terminal.

Optionally, in a possible implementation manner of the first aspect, the terminal includes at least a mobile network core network device, an optical line terminal, a metropolitan area network device, and/or a provincial/prefecture-level core cloud egress routing switching device.

Optionally, in a possible implementation manner of the first aspect, the mobile network core network device includes a mobile network service gateway deployed on an edge cloud, and the metropolitan area network device includes a multi-service network deployed on the edge cloud. Aggregation gateway;

Wherein, the mobile network service gateway includes the U-plane of the mobile network service gateway and the C-plane of the mobile network service gateway; the multi-service convergence gateway includes the U-plane of the multi-service convergence gateway and the C-plane of the multi-service convergence gateway;

The U-plane of the mobile network service gateway is deployed on the edge cloud, and is used to connect to the mobile network convergence node and carry the mobile network service of the mobile network convergence node;

The C-plane of the mobile network service gateway is deployed on the provincial/prefecture-level core cloud, and is used to connect to the U-plane of the mobile network service gateway and control the mobile network service;

The U-plane of the multi-service convergence gateway is deployed on the edge cloud, connected to the U-plane of the mobile network service gateway and the fixed network data service, and connects the U-plane of the mobile network service gateway to the fixed network data service. into the edge cloud;

The C-plane of the multi-service aggregation gateway is deployed on the provincial/prefecture-level core cloud, and is used to control the fixed network data service.

Optionally, in a possible implementation manner of the first aspect, the secondary service orchestrator is connected to a mobile network core network device, and in response to the orchestration instruction, acquires a differentiated QoS guarantee policy corresponding to the terminal;

The mobile network data gateway initiates a QCI dedicated bearer establishment process according to the QoS guarantee policy, triggers the application end through a mobility management entity, and establishes and bears a dedicated bearer network according to the feedback of the application end.

Optionally, in a possible implementation manner of the first aspect, the secondary service orchestrator is connected to the optical line terminal, and responds to the orchestration instruction to perform differentiated QoS quality assurance based on data streams of different services of different users. .

Optionally, in a possible implementation manner of the first aspect, the secondary service orchestrator is connected to a metropolitan area network device, defines a QoS queue traffic policy in response to the orchestration instruction, and sends the QoS queue traffic policy to the the multi-service convergence gateway;

The multi-service aggregation gateway is configured to configure corresponding DSCP marks on each traffic ingress port of the fixed network and mobile network according to the QoS queue traffic policy, and map the DSCP marks to QoS queues on the egress port.

Optionally, in a possible implementation manner of the first aspect, the secondary orchestrator is connected to a provincial/prefecture-level core cloud egress routing switching device, and defines a QoS level policy in response to the orchestration instruction, and assigns the QoS The level policy is sent to the routing switching device;

The routing switching device marks the QoS level of the data traffic according to the QoS level policy.

Optionally, in a possible implementation manner of the first aspect, both the primary service orchestrator and the secondary service orchestrator are provided with an API interface, and communicate with the Internet SP/CP client through the API interface. connect;

The API interface is used to receive the programming instruction input by the user from the Internet SP/CP client.

Optionally, in a possible implementation manner of the first aspect, a backbone network router is also included;

The backbone network router is connected to the first-level service orchestrator, and is used for deploying the QoS quality assurance of the backbone network in response to the orchestration instruction of the first-level service orchestrator.

A second aspect of the embodiments of the present invention provides an end-to-end service quality assurance method, including a first-level service orchestrator deployed on a national core cloud, and a second-level service orchestrator deployed on a provincial/prefecture-level core cloud , wherein the secondary service orchestrator connects the terminal and the primary service orchestrator; the method includes:

Obtain a service request, and obtain an arrangement instruction corresponding to the service request;

Obtain a QoS configuration policy corresponding to the service request according to the orchestration instruction and the secondary service orchestrator, and deliver the QoS configuration policy to the corresponding terminal.

In a third aspect of the embodiments of the present invention, an end-to-end service quality assurance device is provided, including a first-level service orchestrator deployed on a national core cloud, and a second-level service orchestrator deployed on a provincial/prefecture-level core cloud , wherein the secondary service orchestrator connects the terminal and the primary service orchestrator; the device includes:

an instruction module, used to obtain a service request, and obtain an arrangement instruction corresponding to the service request;

An execution module, configured to acquire a QoS configuration policy corresponding to the service request according to the orchestration instruction and the secondary service orchestrator, and deliver the QoS configuration policy to the corresponding terminal.

In a fourth aspect of the embodiments of the present invention, a device is provided, including: a memory, a processor, and a computer program, where the computer program is stored in the memory, and the processor executes the computer program to execute the second aspect of the present invention and various said methods that may be involved in the second aspect.

A fifth aspect of the embodiments of the present invention provides a readable storage medium, where a computer program is stored in the readable storage medium, and when the computer program is executed by a processor, is used to implement the second and second aspects of the present invention Various methods may be involved.

An end-to-end service quality assurance system provided by the present invention realizes the end-to-end QoS of the layered architecture by deploying the first-level service orchestrator in the national core cloud and the second-level service orchestrator in the provincial/prefecture-level core cloud. Guarantee, in which the first-level service orchestrator and the second-level service orchestrator respond to the orchestration instructions and are responsible for managing the allocation of required resources and the organization, orchestration, collaboration, and deployment of services. The provider provides a unified view of resources and services, and can effectively manage and schedule resources across the entire network. According to the characteristics of each service, the service type is divided and the corresponding QoS guarantee policy is matched. Through the first-level service orchestrator and The secondary service orchestrator can provide QoS quality assurance throughout the entire network, cross-layer and cross-domain, end-to-end, multi-service, fast and efficient, and improve service experience.

Description of drawings

1 is a schematic structural diagram of an end-to-end service quality assurance system provided by an embodiment of the present invention;

2 is a schematic structural diagram of a secondary service orchestrator connecting a terminal in an end-to-end service quality assurance system provided by an embodiment of the present invention;

3 is a schematic flowchart of an end-to-end service quality assurance method provided by an embodiment of the present invention;

4 is a schematic structural diagram of an end-to-end service quality assurance device provided by an embodiment of the present invention;

FIG. 5 is a schematic diagram of a hardware structure of a device provided by an embodiment of the present invention.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments It is only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

The terms "first", "second", "third", "fourth", etc. (if present) in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to Describe a particular order or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein.

It should be understood that, in various embodiments of the present invention, the size of the sequence numbers of each process does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present invention. Implementation constitutes any limitation.

It should be understood that in the present invention, "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to Those steps or elements that are expressly listed may instead include other steps or elements that are not expressly listed or are inherent to the process, method, product or apparatus.

It should be understood that, in the present invention, "plurality" refers to two or more. "And/or" is only an association relationship that describes the associated objects, indicating that there can be three kinds of relationships, for example, and/or B, it can mean that A exists alone, A and B exist at the same time, and B exists alone. . The character "/" generally indicates that the associated objects are an "or" relationship. "Contains A, B and C", "contains A, B, C" means that A, B, and C are all contained, "contains A, B or C" means that one of A, B, and C is contained, "Comprising A, B and/or C" means including any one or any two or three of A, B, and C.

It should be understood that in the present invention, "B corresponding to A", "B corresponding to A", "A corresponds to B" or "B corresponds to A" means that B is associated with A, according to A B can be determined. Determining B based on A does not mean determining B based only on A, but also determining B based on A and/or other information. The matching between A and B means that the similarity between A and B is greater than or equal to a preset threshold.

"If" as used herein may be interpreted as "at" or "when" or "in response to determining" or "in response to detecting," depending on the context.

First, the terms involved in the present invention are explained:

QCI: QCI (QoS Class Identifier) is a scale value used to measure specific packet forwarding behavior (such as packet loss rate, packet delay budget) provided to SDF (service data flow), and it is applied to both GBR and Non- GBR bearer is used to specify the control bearer-level packet forwarding method defined in the access node (such as scheduling weight, admission threshold, queue management threshold, link layer protocol configuration, etc.), which are pre-configured by the operator into the access network node .

DSCP: DSCP Differentiated Services Code Point (Differentiated Services Code Point), IETF released the QoS classification standard of Diff-Serv (Differentiated Service) in December 1998. It uses the used 6 bits and the unused 2 bits in the service class TOS identification byte of the IP header of each data packet to distinguish the priority by encoding the value.

COS (Code Of Service): Service code, marked with QoS in the Layer 2 packet header.

IPRAN: IPRAN (Internet Protocol Radio Access Network): It is an IP-based mobile backhaul network and an overall router/switch solution optimized and customized for IP-based base station backhaul application scenarios.

PCC (Policy Control and Charging): It is an architecture that maps the QoS requirements of application-level session service data streams to IP-CAN, and accesses the QoS requirements of bearer-level services of the transmission network to ensure data transmission. The charging policy implements the charging function at the service data flow level.

Internet SP/CP: SP: Service Provider, refers to the direct provider of mobile Internet service content application services, responsible for developing and providing services suitable for mobile phone users according to the requirements of users; CP: content provide, that is, "content provision", is Refers to mobile data service content providers, or mobile value-added service content providers. It also means "product".

QoS (Quality of Service) refers to the ability of a network to use various basic technologies to provide better service capabilities for specified network communications. It is a network security mechanism and is used to solve problems such as network delay and congestion. a technology.

The technical solutions of the present invention will be described in detail below with specific examples. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

With the rapid development of mobile Internet, users have higher and higher requirements for mobile Internet service quality and wired network service quality in mobile scenarios, hoping to achieve low-latency, non-blocking, and high-quality Internet services; With the development of the Internet, the IP network that initially takes the bearer as the main function is gradually transforming into the network that takes the operation of value-added services as the main function. The development of services constantly poses more challenges to the network. The increase in service traffic leads to heavier network load, slow network response, insufficient link bandwidth, and increasing investment in capacity expansion. The existing QoS guarantee is based on segmentation, and a certain segment of the network is guaranteed by the mechanism of guaranteeing the backbone network, metropolitan area network or IPRAN segmentation. The current network QoS guarantee measures are best-effort rather than guaranteed, and the guarantee mechanism is based on hop-by-hop behavior control rather than end-to-end guarantee. Guarantee for a certain type of business, for example, mobile network guarantees the QoS of mobile network users based on the PCRF platform, but does not support QoS guarantee for fixed mobile integrated services. In addition, different services have different QoS requirements, and the level of service quality provided by the network and the requirements of the services are not in a one-to-one mapping relationship, or even cannot be mapped. Therefore, the end-to-end QoS guarantee of services has become an important problem to be solved by service providers at present.

In order to solve the above technical problems, the present invention provides an end-to-end service quality assurance system, which can implement different QoS guarantees according to different service providers, and implement different QoS guarantee strategies according to different service requests, thereby improving the efficiency of QoS guarantees .

Referring to FIG. 1, it is a schematic structural diagram of an end-to-end service quality assurance system provided by an embodiment of the present invention, including a first-level service orchestrator deployed on a national core cloud, a second-level service orchestrator deployed on a provincial/prefecture-level core cloud The first-level service orchestrator, wherein the second-level service orchestrator connects the terminal and the first-level service orchestrator, as follows:

First, the core cloud and edge cloud in this embodiment are specifically described. The core cloud in this embodiment includes a national core cloud and a provincial/prefecture-level core cloud with powerful computing and storage capabilities. The core cloud has powerful storage and storage capabilities. A cloud computing service center composed of server clusters with computing power. Users can use various services provided by the core cloud according to their own needs. Transparent cloud computing services. The edge cloud in this embodiment is composed of server nodes distributed in different networks and regions, provides corresponding auxiliary functions for the core cloud, and cooperates with the core cloud to quickly and elastically provide cloud computing services to users.

In this embodiment, the first-level service orchestrator is deployed on the national core cloud, the second-level service orchestrator is deployed on the provincial/prefecture-level core cloud, the service orchestrator is deployed hierarchically, and is connected to the core cloud for cloud computing Network coordination, in which the first-level service orchestrator invokes the QoS guarantee capability of the second-level service orchestrator; the second-level service orchestrator is responsible for the implementation of the QoS guarantee of each service network in the province. QoS guarantee of the network.

Among them, the primary service orchestrator and secondary service orchestrator are connected to the Internet SP/CP client respectively; the primary service orchestrator and secondary service orchestrator are respectively connected to terminals; the primary service orchestrator on the national core cloud and the provincial / The secondary service orchestrator on the prefecture-level core cloud is used to obtain the orchestration instruction in response to the service request of the Internet SP/CP client; and respond to the orchestration instruction to obtain the QoS configuration policy corresponding to the service request, and deliver the QoS configuration policy to the terminal. In some embodiments, the secondary service orchestrator may obtain the QoS configuration policy corresponding to the service request in response to the orchestration instruction of the primary service orchestrator. In other embodiments, the secondary service orchestrator may directly respond to the Internet SP/ The service request of the CP client obtains the orchestration instruction, and responds to the orchestration instruction to obtain the QoS configuration policy corresponding to the service request.

For example, a list of mapping relationships between service requests and orchestration instructions is preset in the primary service orchestrator and secondary service orchestrator, so that the primary service orchestrator and/or secondary service orchestrator can receive the service request , obtain the corresponding orchestration instruction. For another example, the first-level service scheduler and the second-level service scheduler are preset with a list of mapping relationships between the orchestration instruction and the QoS configuration policy, so that the first-level service scheduler and the second-level service scheduler can receive the orchestration instruction. , obtain the corresponding QoS configuration policy. The service request includes a service type, such as a game type, and the primary service orchestrator and/or secondary service orchestrator extracts the QoS of the corresponding type from the pre-stored multiple QoS guarantee policies according to the service type in the service request. Guarantee the strategy and issue it.

In some embodiments, in order to meet different service requirements of different terminals, different QoS guarantees are required, the user sends a service request to the first-level service orchestrator through the Internet SP/CP client, and the first-level service orchestrator generates a corresponding service request. Arrange the instructions, and send them down to invoke the QoS guarantee capability of the secondary service orchestrator.

In some embodiments, the secondary service orchestrator receives the orchestration instruction, manages the allocation of required resources and the organization, orchestration, coordination and deployment of services, and generates a QoS configuration policy corresponding to the orchestration instruction. The high-level service orchestrator is connected to the terminal, and is responsible for the implementation of QoS guarantee capabilities, that is, the QoS configuration policy is issued to the terminal for implementation.

The above-mentioned embodiment provides an end-to-end service quality assurance system, which implements an end-to-end layered architecture by deploying a first-level service orchestrator in a national core cloud and a second-level service orchestrator in a provincial/prefecture-level core cloud. QoS assurance, in which the first-level service orchestrator and/or the second-level service orchestrator is responsible for managing the allocation of required resources and the organization, orchestration, coordination and deployment of services in response to the orchestration instructions, and is responsible for the implementation of QoS assurance capabilities, which are implemented by the service orchestrator. The unified distribution of QoS configuration for each network element in the entire network greatly reduces the workload of manual configuration for each device, improves service response and product development speed, improves network automation operation level, and improves service support capabilities.

Because service characteristics and service requirements have an important impact on QoS planning, before considering QoS planning, they should be classified according to service characteristics and needs. Afterwards, consider the QoS planning of each service and whether some services can share QoS queues. According to the characteristics of each service, the service type is divided and the corresponding QoS guarantee policy is matched.

On the basis of the above-mentioned embodiment, the terminal connected to the secondary service orchestrator can be in various forms. Referring to FIG. 2 , an end-to-end service quality assurance system provided by an embodiment of the present invention is connected to the secondary service orchestrator. Schematic diagram of the terminal structure. As shown in FIG. 2 , the terminals may include mobile network core network equipment, optical line terminals, metropolitan area network equipment and/or provincial/prefecture-level core cloud egress routing switching equipment.

In some embodiments, the mobile network core network equipment includes a mobile network service gateway deployed on the edge cloud, and the metropolitan area network equipment includes a multi-service aggregation gateway deployed on the edge cloud, as follows:

In some embodiments, the mobile network service gateway includes the U-plane of the mobile network service gateway and the C-plane of the mobile network service gateway; the multi-service convergence gateway includes the U-plane of the multi-service convergence gateway and the C-plane of the multi-service convergence gateway, wherein the mobile network and fixed All data services of the network (excluding VoLTE and 3G voice services) are uniformly accessed by the U-plane of the multi-service aggregation gateway at the aggregation node.

In other embodiments, the mobile network service gateway may be deployed in a distributed manner, and the U-plane of the mobile network service gateway may be deployed on the edge cloud to connect to the mobile network convergence node and carry the mobile network service of the mobile network convergence node. The content source of the edge cloud or the Internet can be accessed through the U-plane of the multi-service aggregation gateway; the C-plane of the mobile network service gateway can be deployed in the provincial/prefecture-level core cloud, which is used to connect the U-plane of the mobile network service gateway and control the mobile network service gateway. network business.

In other embodiments, the fixed network forwarding control is separated, and the multi-service convergence gateway U-plane forwards uniformly, and the control layer is uniformly responsible for the multi-service convergence gateway C-plane deployed centrally in the province or city. Among them, the U-plane of the aggregation gateway can be deployed on the edge cloud, connected to the U-plane of the mobile network service gateway and the fixed network data service, and enables the U-plane of the mobile network service gateway and the fixed network data service to access the edge cloud; the multi-service aggregation gateway C It can be deployed in the provincial/prefecture-level core cloud to control fixed network data services.

The mobile network service gateway and multi-service aggregation gateway deployed on the edge cloud well meet the requirements of edge cloud access, security, billing, and QoS assurance. Operators give full play to the advantages of abundant mobile network, fixed network access network resources and localized support services to provide terminals (third parties) with IAAS layer-based edge cloud resources (computing, storage, network) and multi-service access network resources The cloud-network integration product of the company realizes the capability opening and realization of edge cloud and access network.

Correspondingly, network operators can allow third parties to access the infrastructure of the edge cloud for application development, deploy various applications in the edge cloud, such as cloud games, Internet of Things applications, high-definition video and other content, and conduct cloud computing in areas close to target users. Network collaboration provides users with low-latency, large-bandwidth, and stable high-quality services. By deploying content including third-party hotspot applications on the edge cloud, access the mobile network service gateway and multi-service aggregation gateway. For mobile and fixed network service requests that have been distributed to the hotspot content of the edge cloud, the edge cloud provides services nearby, reducing the bandwidth occupation of the network above the mobile network service gateway and the multi-service aggregation gateway. In addition, for some specific applications (such as video surveillance, security monitoring, big data analysis, etc.), a large amount of data needs to be stored at the network edge. Abstract, compress and cache, and then send to the core cloud. This will greatly reduce the data traffic sent to the core cloud, thereby saving transmission network bandwidth.

The configuration of various forms of terminals to implement QoS guarantee policies is described below with examples.

In some embodiments, the terminal may be a mobile network core network device. The secondary service orchestrator is connected to the mobile network core network equipment, and responds to the orchestration command to obtain the differentiated QoS guarantee policy of the corresponding terminal; the mobile network data gateway initiates the QCI dedicated load establishment process according to the QoS guarantee policy, which is triggered by the mobility management entity to the application side, and establish and bear the dedicated bearer network according to the feedback of the application side.

Correspondingly, the standard Rx interface is used between the secondary service orchestrator and the mobile network core network equipment. The secondary service orchestrator provides standard and Internet-based REST/JSON interface methods to third-party applications, which simplifies the integration difficulty of third parties. Through QoS delay optimization: high-priority QCI labels are applied to mobile gaming, securities, and mobile video services, and packet data is preferentially scheduled through differentiated scheduling policies. The secondary service orchestrator responds to the orchestration instruction corresponding to the service request, opens the policy control and charging guarantee policies to third-party applications, and dynamically applies for differentiated PCC guarantee policies for third-party applications, such as: setting the QCI guarantee level, user Access resource allocation maintains priority, bearer bandwidth, etc. The core network equipment of the mobile network supports issuing QoS policies to the PDN gateway according to the relevant parameters of the Rx interface, including the adjustment of parameters such as GBR/MBR/QCI/ARP.

Core network side: The mobile network service gateway initiates the QCI dedicated bearer establishment process according to the QoS policy issued by the mobile network core network equipment, and triggers it to the wireless network side through the mobility management entity, and establishes and bears the dedicated bearer network according to the feedback from the wireless side. The core network element moving network service gateway needs to support QCI to DSCP mapping;

Wireless side: Taking the mobile game business as an example, according to the QCI dedicated load establishment process triggered by the core network, a dedicated load network is established for mobile game users and the results are fed back to the core network side. The core network and the wireless side together form the QCI dedicated carrier network, which is connected with the public network mobile game server to form the mobile game end-to-end service flow. The base station needs to support QCI to DSCP mapping.

The last mile of the mobile network accounts for 70% of the end-to-end delay, and wireless optimization is the focus of its QoS policy configuration. The secondary service orchestrator and the mobile network core Network equipment connection, providing network acceleration and QoS guarantee services for 4G users, reducing delay.

In some embodiments, the termination may be an optical line termination. The secondary service orchestrator is connected to the optical line terminal, and responds to the orchestration command to perform differentiated QoS quality assurance based on the data streams of different users and different services.

Specifically, the provincial orchestrator is connected to the optical line terminal of the broadband access device. In terms of flow classification, each service flow is marked with 802.1p based on the data flow labels of different users and different services, or it is trusted that different users transmitted by the upstream device are different. The priority of data flow packets of the service; in terms of traffic supervision, an independent service virtual port can be established for a special service, and the service flow is mapped to the service virtual port. Different service flows of different users are mapped to different service virtual ports. Differentiation; in queue scheduling, scheduling is performed according to the priority of the 802.1p COS field, and the secondary service scheduler can perform differentiated QoS quality assurance for the optical line terminal based on the data flow of different users and different services.

In some embodiments, the terminal may be a metropolitan area network device. The secondary service orchestrator is connected to the MAN equipment, and responds to the orchestration command to define the QoS queue traffic policy, and sends the QoS queue traffic policy to the multi-service aggregation gateway; Configure the corresponding differentiated service code point mark on each traffic ingress port of the mobile network, and map the DSCP mark to the QoS queue on the egress port.

Specifically, the secondary service orchestrator is connected to the MAN equipment to complete the following tasks to ensure QoS quality:

Interaction with the metropolitan area network core router CR: In terms of service flow classification, the secondary service orchestrator sends configuration instructions to the metropolitan area network core router CR in response to the orchestration command, and divides the uplink and downlink traffic at the metropolitan area network core router CR based on the source. Deploy traffic classification based on features such as IP and destination IP, and re-mark the priority of special service packets to a higher priority. That is, QoS marking is performed for special service flows based on source and destination addresses. Then, queue scheduling is performed according to the QoS marking, and a corresponding scheduling algorithm can be used for queue scheduling, and at the same time, the QoS marking is transmitted to the next-level device.

Interaction with the multi-service access gateway: In the service flow classification, the orchestrator sends configuration instructions to the multi-service aggregation gateway, and the upstream and downstream traffic trust the upstream device packet priority. In priority processing, for upstream traffic, the fixed network broadband 802.1p priority is mapped to the DSCP value of the IP header field, and the QoS identification is transmitted to the upper-layer device; for downstream traffic, the DSCP value of the IP header field of the QoS identification is mapped to 802.1p for transmission. to fixed-line broadband equipment. For traffic policing, configure QoS profiles to limit the rate of committed information for special uplink and downlink services. When the U-plane of the multi-service aggregation gateway and the U-plane of the mobile network service gateway are interconnected, the DSCP value of the IP header field transmitted by the peer end is trusted to complete the configuration of the QoS queue traffic policy.

Specifically, the terminal may be a provincial/prefecture-level core cloud egress routing switching device. The second-level orchestrator is connected to the provincial/prefecture-level core cloud egress routing switching equipment, and responds to the orchestration command to define QoS level policies, and sends the QoS level policies to the routing switching equipment. The routing switching equipment marks the QoS level of data traffic according to the QoS level policy. , to provide high QoS guarantee for business flows that meet certain business rules.

In some embodiments, the terminal may be an IP RAN controller. The secondary orchestrator interfaces with the IP RAN controller as follows:

The aggregation node is about 10KM away from the wireless base station and wired CPE. The transmission delay of the optical backhaul network is usually within 0.1ms (7ms/1000km), and the optical transmission delay can be ignored. The main factors affecting the user experience are congestion, bit errors, and delays. QoS policies need to be deployed on the access side: IPRAN QoS assurance can be achieved by invoking the QoS assurance capability of the orchestration coordinator, and configuring GTP-U on the IPRAN aggregation device or access device. Layer IP header field DSCP value, or trust the DSCP value passed by the upstream device, and map it to the corresponding bits of MPLS EXP, and perform QoS scheduling based on the VPN network.

QoS configuration mainly involves three aspects: dividing services and marking QoS, trusting and mapping of QoS marking when entering IP RAN, and configuring QoS queues in IP RAN.

The classification and marking of services need to be configured on demand. For example, the private line type needs to be configured at the service access point; the mobile network service needs the cooperation of the core network and wireless network equipment, and the QoS mark is marked outside the IP RAN. The trust and mapping of QoS marks need to be configured uniformly. The QoS policy of IP RAN is mainly executed based on trust QoS marks and needs to be configured at the IP RAN entrance. The QoS queue in the device needs to be configured uniformly, but the guarantee can also play a certain role under the current configuration conditions. Involving queue scheduling, weight, rate limit, discarding rules and other issues, each manufacturer has its default configuration, and each model of equipment will also be different. The IPRAN should transparently transmit the QoS marking of the service, that is, the QoS operations (such as trust/distrust, remarking, etc.) within the IP RAN should not modify the QoS marking of the original packet.

In order to support users to perform dynamic and elastic QoS scheduling according to service operation conditions, on the basis of the above embodiment, referring to FIG. 2 , the details are as follows:

Both the first-level service orchestrator and the second-level service orchestrator are provided with API interfaces, and are connected to the Internet SP/CP client through the API interface. The API interface is used to receive the orchestration instructions input by the user from the Internet SP/CP client.

In some embodiments, the service orchestrator provides API interfaces and the like to third-party applications, and the third-party applications dynamically apply for QoS guarantee according to service requirements, and the first-level service orchestrator and the second-level service orchestrator provide third-party applications with standard and Internet The standardized REST/JSON interface method simplifies the integration difficulty of third parties, and third-party applications need to support API interfaces.

In the present invention, the first-level service scheduler and the second-level service scheduler call the API interface of the network device controller to complete the unified configuration and delivery of services, realize the service management and data configuration of each manufacturer's equipment, and shield the details of heterogeneous manufacturers. Programmable way Automate network configuration to simplify and speed deployment of network devices and services. Unified configuration delivery is suitable for configuration requirements scenarios that are frequently called repeatedly.

In order to improve the QoS guarantee for the entire network to perform all services, on the basis of the above embodiment, referring to FIG. 2 , a backbone network router is also included.

In some embodiments, the backbone network router is connected to the first-level service orchestrator, and is configured to deploy the QoS quality assurance of the backbone network in response to the orchestration instruction of the first-level service orchestrator. In another embodiment, the edge cloud is connected to the national core cloud through a backbone network, and user terminals can use the services provided by the edge cloud nearby under the coordination of the national core cloud.

The present invention also provides an end-to-end service quality assurance method. Referring to FIG. 3 , it is a schematic flowchart of an end-to-end service quality assurance method provided by an embodiment of the present invention. The execution subject of the method shown in FIG. 3 may be an end-to-end service quality assurance device. The end-to-end service quality assurance device includes, for example, the first-level service orchestrator deployed on the national core cloud as shown in FIG. 1 , and the second-level service orchestrator deployed on the provincial/prefecture-level core cloud. The method shown in FIG. 3 includes steps S101-S102, which are as follows:

S101. Obtain a service request, and obtain an arrangement instruction corresponding to the service request.

S102: Acquire a QoS configuration policy corresponding to the service request according to the orchestration instruction, and deliver the QoS configuration policy to a corresponding terminal.

The method in the embodiment shown in FIG. 3 can correspondingly be used to execute the steps performed by the first-level service orchestrator and the second-level service orchestrator in the system embodiment shown in FIG. 1 , and the implementation principles and technical effects thereof are similar, and will not be repeated here.

The present invention also provides an end-to-end service quality assurance device. Referring to FIG. 4 , it is a schematic structural diagram of an end-to-end service quality assurance device provided by an embodiment of the present invention, including the first-level service orchestration deployed on the national core cloud. It is a secondary service orchestrator deployed on the provincial-level core cloud. The primary service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and secondary service orchestrator are respectively connected to the Internet SP/CP client. ; The primary service orchestrator and the secondary service orchestrator are respectively connected to the terminals; the device 40 includes:

The instruction module 41 is used to obtain the service request of the Internet SP/CP client, and obtain the arrangement instruction corresponding to the service request;

The execution module 42 is configured to obtain the QoS configuration policy corresponding to the service request according to the arrangement instruction, and deliver the QoS configuration policy to the corresponding terminal.

The device for end-to-end service quality assurance in the embodiment shown in FIG. 4 can correspondingly be used to execute the steps in the method embodiment shown in FIG. 3 , and the implementation principles and technical effects thereof are similar, and details are not described herein again.

5 is a schematic diagram of a hardware structure of a device provided by an embodiment of the present invention, the device 50 includes: a processor 51, a memory 52, and a computer program; wherein

The memory 52 is used to store computer programs, and the memory can also be flash memory. The computer program is, for example, an application program, a functional module, or the like that realizes the above-mentioned method.

The processor 51 is configured to execute the computer program stored in the memory, so as to realize each step executed by the terminal in the above method. For details, refer to the relevant descriptions in the foregoing method embodiments.

Optionally, the memory 52 may be independent or integrated with the processor 41 .

When the memory 52 is a device separate from the processor 41, the device may also include:

The bus 43 is used to connect the memory 42 and the processor 41 .

The present invention further provides a readable storage medium, where a computer program is stored in the readable storage medium, and when the computer program is executed by a processor, is used to implement the methods provided by the above-mentioned various embodiments.

The readable storage medium may be a computer storage medium or a communication medium. Communication media includes any medium that facilitates transfer of a computer program from one place to another. Computer storage media can be any available media that can be accessed by a general purpose or special purpose computer. For example, a readable storage medium is coupled to the processor such that the processor can read information from, and write information to, the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium may be located in application specific integrated circuits (Application Specific Integrated Circuits, ASIC for short). Alternatively, the ASIC may be located in the user equipment. Of course, the processor and the readable storage medium may also exist in the communication device as discrete components. The readable storage medium may be read only memory (ROM), random access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, optical data storage devices, and the like.

The present invention also provides a program product including execution instructions stored in a readable storage medium. At least one processor of the device can read the execution instruction from the readable storage medium, and the execution of the execution instruction by the at least one processor causes the device to implement the methods provided by the various embodiments described above.

In the embodiment of the above device, it should be understood that the processor may be a central processing unit (English: Central Processing Unit, referred to as: CPU), or other general-purpose processors, digital signal processors (English: Digital Signal Processor, referred to as: DSP) ), application specific integrated circuit (English: Application Specific Integrated Circuit, referred to as: ASIC) and so on. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the present invention can be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features thereof can be equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the embodiments of the present invention. scope.

Claims (13)

1. an end-to-end service quality assurance system, is characterized in that, comprises the first-level business orchestrator deployed on the national core cloud, the second-level business orchestrator deployed on the provincial/prefecture-level core cloud, wherein, all The primary service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and the secondary service orchestrator are respectively connected to Internet SP/CP clients; the primary service orchestrator and the secondary service orchestrator are respectively connected to the Internet SP/CP client; Level service orchestrators are connected to the terminals respectively; The primary service orchestrator and/or the secondary service orchestrator obtains orchestration instructions in response to the service request of the Internet SP/CP client; The primary service scheduler and/or the secondary service scheduler, in response to the orchestration instruction, obtains a QoS configuration policy corresponding to the service request, and delivers the QoS configuration policy to the terminal. 2 . The system according to claim 1 , wherein the terminals include mobile network core network equipment, optical line terminals, metropolitan area network equipment and/or provincial/prefecture-level core cloud egress routing switching equipment. 3 . 3. The system according to claim 2, wherein the mobile network core network equipment comprises a mobile network service gateway deployed on an edge cloud, and the metropolitan area network equipment comprises a multi-service aggregation deployed on the edge cloud gateway; Wherein, the mobile network service gateway includes the U-plane of the mobile network service gateway and the C-plane of the mobile network service gateway; the multi-service convergence gateway includes the U-plane of the multi-service convergence gateway and the C-plane of the multi-service convergence gateway; The U-plane of the mobile network service gateway is deployed on the edge cloud, and is used to connect to the mobile network convergence node and carry the mobile network service of the mobile network convergence node; The C-plane of the mobile network service gateway is deployed on the provincial/prefecture-level core cloud, and is used to connect to the U-plane of the mobile network service gateway and control the mobile network service; The U-plane of the multi-service convergence gateway is deployed on the edge cloud, connected to the U-plane of the mobile network service gateway and the fixed network data service, and connects the U-plane of the mobile network service gateway to the fixed network data service. into the edge cloud; The C-plane of the multi-service aggregation gateway is deployed on the provincial/prefecture-level core cloud, and is used to control the fixed network data service. 4. The system according to claim 3, wherein the secondary service scheduler is connected to the mobile network core network device, and in response to the schedule instruction, obtains a differentiated QoS guarantee policy corresponding to the terminal; The mobile network data gateway initiates a QCI dedicated bearer establishment process according to the QoS guarantee policy, triggers the application end through a mobility management entity, and establishes and bears a dedicated bearer network according to the feedback of the application end. 5 . The system according to claim 3 , wherein the secondary service orchestrator is connected to the optical line terminal, and performs differentiated QoS quality assurance based on data streams of different services and different users in response to the orchestration instruction. 6 . 6. The system according to claim 3, wherein the secondary service orchestrator is connected to a metropolitan area network device, and defines a QoS queue traffic policy in response to the orchestration instruction, and sends the QoS queue traffic policy to the Multi-service aggregation gateway; The multi-service aggregation gateway is configured to configure corresponding DSCP marks on each traffic ingress port of the fixed network and mobile network according to the QoS queue traffic policy, and map the DSCP marks to QoS queues on the egress port. 7. The system according to claim 3, wherein the secondary orchestrator is connected with the provincial/prefecture-level core cloud egress routing switching device, and defines a QoS level policy in response to the orchestration instruction, and assigns the QoS level to the QoS level. sending the policy to the routing switching device; The routing switching device marks the QoS level of the data traffic according to the QoS level policy. 8. The system according to claim 3, wherein the primary service orchestrator and the secondary service orchestrator are all provided with API interfaces, and are connected with Internet SP/CP clients through the API interfaces ; The API interface is used to receive the programming instruction input by the user from the Internet SP/CP client. 9. The system of claim 1, further comprising a backbone network router; The backbone network router is connected to the first-level service orchestrator, and is used for deploying the QoS quality assurance of the backbone network in response to the orchestration instruction of the first-level service orchestrator. 10. An end-to-end service quality assurance method, comprising a first-level service orchestrator deployed on a national core cloud, and a second-level service orchestrator deployed on a provincial/prefecture-level core cloud, wherein all The primary service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and the secondary service orchestrator are respectively connected to Internet SP/CP clients; the primary service orchestrator and the secondary service orchestrator are respectively connected to the Internet SP/CP client; The level service orchestrators are respectively connected to the terminals; the method includes: Obtain the service request of the Internet SP/CP client, and obtain the arrangement instruction corresponding to the service request; According to the arrangement instruction, the QoS configuration policy corresponding to the service request is acquired, and the QoS configuration policy is delivered to the corresponding terminal. 11. An end-to-end service quality assurance device, characterized in that it comprises a primary service orchestrator deployed on a national core cloud, and a secondary service orchestrator deployed on a provincial/prefecture-level core cloud, wherein all The primary service orchestrator is connected to the secondary service orchestrator, and the primary service orchestrator and the secondary service orchestrator are respectively connected to Internet SP/CP clients; the primary service orchestrator and the secondary service orchestrator are respectively connected to the Internet SP/CP client; The level service orchestrators are respectively connected to the terminals; the device includes: an instruction module, used for acquiring the service request of the Internet SP/CP client, and acquiring the arrangement instruction corresponding to the service request; An execution module, configured to acquire a QoS configuration policy corresponding to the service request according to the arrangement instruction, and deliver the QoS configuration policy to the corresponding terminal. 12. A device, comprising: a memory, a processor and a computer program, wherein the computer program is stored in the memory, and the processor executes the computer program to execute the method of claim 10. 13. A readable storage medium, wherein a computer program is stored in the readable storage medium, and the computer program is used to implement the method of claim 10 when executed by a processor.