Source provisioning service infrastructure

By generating advertisement messages on the headend routers using the BGP protocol and pushing service request attributes to the tailend routers, the tedious problem of manually configuring tailend nodes by network operators is solved. This enables automatic service configuration of tailend routers, improves configuration efficiency and accuracy, and supports service expansion between autonomous systems.

CN117751568BActive Publication Date: 2026-07-24CISCO TECHNOLOGY INC
1 Cites 0 Cited by

Patent Information

Application Number
CN202280052330.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-12-10
Filing Date
2022-07-27
Publication Date
2026-07-24
Estimated Expiration
2042-07-27

AI Technical Summary

Technical Problem

In existing technologies, network operators need to manually configure the service instantiation process of tail nodes, which is cumbersome and error-prone, especially when they cannot be directly accessed in different autonomous systems, resulting in low configuration efficiency.

Method used

By utilizing the Border Gateway Protocol (BGP) to generate advertisement messages on the headend router, which include service request attributes, and pushing instantiation information to the tailend router, automatic service configuration of the tailend router is achieved, including service identifiers, location information, and processing attributes, thus avoiding manual configuration of the tailend node.

Benefits of technology

It enables automatic service instantiation on tail routers, eliminating the need for network operators to directly access tail nodes, thus improving configuration efficiency and accuracy, and supporting service expansion and management between autonomous systems.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

A head-end node in one or more network autonomous systems utilizes a protocol to instantiate a service on a tail-end node. The head-end node can use a service request mechanism enabled by the protocol to request service instantiation on the tail-end node without requiring the network operator to manually configure the tail-end node, or even to have access to the tail-end node. Furthermore, the protocol can provide mechanisms to define handling attributes (e.g., quality of service (QoS) attributes, maximum transmission unit (MTU) settings, etc.) for traffic of the service, a service confirmation mechanism for the head-end node to determine that the service has been instantiated on the tail-end node, etc. In this way, the head-end node can be used to instantiate a service on a tail-end node without the network operator needing to have direct access to the tail-end node to manually configure the tail-end node.
Need to check novelty before this filing date? Find Prior Art