A Metropolitan Area Network Architecture Based on Service Orchestrator

Abstract

The invention discloses a metropolitan area network architecture based on service choreographer which comprises an application end, a service choreographer and an SDN controller, wherein the service choreographer is connected with the application end through a north interface and with the SDN controller through a south interface of Rest, and the SDN controller is connected with a metropolitan areanetwork, wherein the application end is used for initiating a service request. The service choreographer is used for uniformly arranging, configuring and distributing network services of all metropolitan area networks. The SDN controller is used for processing the service request. The application end at least comprises a Web UI end and a service opening system end. The method of the invention cancarry out flexible and customized programming based on user requirements; it can be scheduled and adjusted based on the traffic of the whole network. The invention breaks the traditional network equipment closed management and control mode, rapid deployment to build the entire network.

Description

technical field [0001] The invention relates to the Internet field, in particular to a network architecture of a metropolitan area network based on a service orchestrator. Background technique [0002] With the integration of fixed and mobile networks and the rapid development of government and enterprise services, the types of services carried by the metropolitan area network are becoming more and more abundant. With the growth of the network scale, the number of network elements is also increasing rapidly, and the configuration instructions and styles of equipment from different manufacturers are different. In the process of adapting network elements and equipment from different manufacturers in the existing network The network element-by-network configuration mode requires a large configuration workload, long configuration time, multiple configuration levels, low configuration accuracy, and slow service response. [0003] The monitoring of the network in the existing MAN...

AI Technical Summary

Problems solved by technology

[0003] The monitoring of the network in the existing MAN network framework is based on the overall service flow level, based on the state collection and perception of different service flows, and on this basis, the automatic routing optimization and protection capabilities for subdivided service flows are not yet available. Not available, manual intervention is required, network element configuration is performed one by one, the response time is slow, and corresponding actions cannot be taken automatically and quickly based on abnormal conditions in the network to ensure service security and user experience

[0004] With the development of cloud computing, mobile Internet and other application modes and changes in traffic models, it is often necessary for the network to actively "adapt" to business traffic so that applications can change as needed. However, the current network management is mainly device-oriented Rather than business management, the perspective is more based on nodes rather than a global perspective. Therefore, many unsolvable problems have arisen:

[0005] (1) Slow business deployment and long online cycle: devices are scattered, and need to be deployed one by one when the service is activated, and manual configuration requires a lot of deployment workload; there are many services, complex configuration, manual configuration is prone to errors, and the activation cycle is long

[0006] (2) Traffic scheduling is difficult and lacks flexibility:

[0007] Due to the lack of perspective of the entire network, the devices select routes based on their respective routes, and the shortest route is selected instead of the optimal route, resulting in low bandwidth utilization; service flow routing cannot be automatically and quickly adjusted according to changes in network conditions, and user experience cannot be guaranteed.

Traditional policy routing and traffic engineering have large limitations and complex configurations, and cannot dynamically adapt to changes in network status and application requirements.

[0008] (3) The operation and maintenance experience of network maintenance personnel is poor: network management methods are limited, mainly manual, and require high skills for network maintenance personnel

There is no visual presentation of traffic and services, which makes it impossible to quickly identify and locate faults, making O&M difficult

[0009] (4) The network opening capability is weak and unable to adapt to the network requirements of the business:

[0011] To sum up, the existing network architecture can no longer meet the requirements of network complexity and business flexibility, and the existing network architecture needs to be further improved

Images