IP Library Granted Patent US 12,432,133
Granted Patent B2
US 12,432,133 · App. 18/416,882 · Granted Sep 30, 2025

Source-provisioned services infrastructure

Inventors: Patrice Brissette (Gatineau, CA); Thierry Couture (Mont-Royal, CA); Karen Michele Cadora (Boulder, CO); Jiri Chaloupka (San Jose, CA); Suresh Basavarajappa (San Jose, CA)
Assignee: Cisco Technology, Inc.
H04L45/02H04L12/4641H04L12/66H04L45/74
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,432,133
App. No.
18/416,882
Granted
Sep 30, 2025
Kind
B2
Abstract

Techniques for a head-end node in one or more network autonomous systems to utilize a protocol to instantiate services on tail-end nodes. The head-end node can use a service request mechanism that is enabled by the protocol to request service instantiation on the tail-end node without a network operator having to manually configure the tail-end node, or even having access to the tail-end node. Additionally, the protocol may provide mechanisms to define handling attributes for traffic of the service (e.g., quality of service (QoS) attributes, Maximum Transmission Unit (MTU) settings, etc.), service acknowledgement mechanisms for the head-end node to determine that the service was instantiated on the tail-end node, and so forth. In this way, a head-end node can be used to instantiate a service on a tail-end node without a network operator having to have direct access to the tail-end node to manually configure the tail-end node.

Claims (72)

1. A method for a first router to utilize a protocol to provide information to a second router that is usable to install a service on the second router, the method comprising:

generating, at the first router, an advertisement message indicating a service that is installed on the first router and configures the first router to establish network paths with other devices that have the service installed;

populating the advertisement message with a service request Type-Length-Value (TLV), the service request TLV including the information for installing the service on the second router, the information including at least one of:

a service identifier that identifies the service that is being requested to be installed on the second router; or

service-location information indicating a location at which the second router installs the service,

wherein the service configures the first router and second router to establish a network path; and

sending, from the first router, the advertisement message to the second router such that the second router installs the service and is configured to establish the network path with the first router.

2. The method of claim 1 , wherein the service-location information includes:

a Media Access Control (MAC) address associated with onboarding the second router with the service; and

an indication of a Virtual Local Area Network (VLAN) over which the second router is onboarded with the service.

3. The method of claim 1 , further comprising:

populating the advertisement message with a service-acknowledgement TLV, the service-acknowledgement TLV comprising:

a service identifier that indicates that the service was installed on the second router; and

an Internet Protocol (IP) address associated with the second router.

4. The method of claim 3 , further comprising:

installing the service on the second router; and

sending, from the second router, an acknowledgement message to the first router, the acknowledgement message indicating that the service was installed on the second router.

5. The method of claim 1 , further comprising:

populating the advertisement message with a service attribute TLV, the service attribute TLV comprising at least one of:

quality-of-service (QOS) information indicating an amount of bandwidth allocated for the service; or

a maximum transmission unit (MTU) for packets communicated by the service.

6. The method of claim 1 , further comprising:

populating the advertisement message with a service measurement TLV, the service measurement TLV comprising a request to provide measurement information indicating a round-trip delay associated with the advertisement message and an acknowledgement message.

7. The method of claim 1 , wherein the advertisement message includes a Yang data TLV.

8. A head-end router comprising:

one or more processors; and

one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

generating, at the head-end router, an advertisement message indicating a service that is installed on the head-end router and configures the head-end router to establish network paths with other devices that have the service installed;

populating the advertisement message with a service request Type-Length-Value (TLV), the service request TLV including information for installing the service on a tail-end router, the information including at least one of:

a service identifier that identifies the service that is being requested to be installed on the tail-end router; or

service-location information indicating a location at which the tail-end router installs the service,

wherein the service configures the head-end router and tail-end router to establish a network path; and

sending, from the head-end router, the advertisement message to the tail-end router such that the tail-end router installs the service and is configured to establish the network path with the head-end router.

9. The head-end router of claim 8 , wherein the service-location information includes:

a Media Access Control (MAC) address associated with onboarding the tail-end router with the service; and

an indication of a Virtual Local Area Network (VLAN) over which the tail-end router is onboarded with the service.

10. The head-end router of claim 8 , further comprising:

populating the advertisement message with a service-acknowledgement TLV, the service-acknowledgement TLV comprising:

a service identifier that indicates that the service was installed on the tail-end router; and

an Internet Protocol (IP) address associated with the tail-end router.

11. The head-end router of claim 10 , further comprising:

installing the service on the tail-end router; and

sending, from the tail-end router, an acknowledgement message to the head-end router, the acknowledgement message indicating that the service was installed on the tail-end router.

12. The head-end router of claim 8 , further comprising:

populating the advertisement message with a service attribute TLV, the service attribute TLV comprising at least one of:

quality-of-service (QOS) information indicating an amount of bandwidth allocated for the service; or

a maximum transmission unit (MTU) for packets communicated by the service.

13. The head-end router of claim 8 , further comprising:

populating the advertisement message with a service measurement TLV, the service measurement TLV comprising a request to provide measurement information indicating a round-trip delay associated with the advertisement message and an acknowledgement message.

14. The head-end router of claim 8 , wherein the advertisement message includes a Yang data TLV.

15. A method for a tail-end router to install a service using information provided from a head-end router, the method comprising:

receiving, at the tail-end router, an advertisement message from the head-end router, the advertisement message including:

an indication of a service that is installed on the head-end router; and

a service request Type-Length-Value (TLV), the service request TLV including information for installing the service on the tail-end router, the information including at least one of:

a service identifier that identifies the service that is being requested to be installed on the tail-end router; or

service-location information indicating a location at which the tail-end router installs the service,

wherein the service configures the head-end router and the tail-end router to establish a network path;

installing the service on the tail-end router based at least in part on the service request TLV; and

using the service, establishing the network path with the head-end router.

16. The method of claim 15 , wherein the service-location information includes:

a Media Access Control (MAC) address associated with onboarding the tail-end router with the service; and

an indication of a Virtual Local Area Network (VLAN) over which the tail-end router is onboarded with the service.

17. The method of claim 15 , wherein the advertisement message includes a service-acknowledgement TLV, the service-acknowledgement TLV comprising:

a service identifier that indicates that the service was installed on the tail-end router; and

an Internet Protocol (IP) address associated with the tail-end router.

18. The method of claim 17 , further comprising:

sending, from the tail-end router, an acknowledgement message to the head-end router, the acknowledgement message indicating that the service was installed on the tail-end router.

19. The method of claim 15 , further comprising:

populating the advertisement message with a service attribute TLV, the service attribute TLV comprising at least one of:

quality-of-service (QOS) information indicating an amount of bandwidth allocated for the service; or

a maximum transmission unit (MTU) for packets communicated by the service.

20. The method of claim 15 , wherein the advertisement message includes a Yang data TLV.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 18, 2024
From: BRISSETTE, PATRICE; COUTURE, THIERRY; CADORA, KAREN MICHELE; CHALOUPKA, JIRI; BASAVARAJAPPA, SURESH
To: CISCO TECHNOLGY, INC.
Reel/Frame 066173/0651 →
Continuity (3)
Continuation 17547735 · Dec 10, 2021
Provisional Application 63226906 · Jul 29, 2021
Related Publication 20240163197A1 · May 16, 2024
References Cited (66)
US 6823386B1 · Crump · 2004 [cited by examiner]
US 8380828B1 · Schlichter · 2013 [cited by examiner]
US 8861345B2 · Hares et al. · 2014 [cited by applicant]
US 9021459B1 · Qu · 2015 [cited by examiner]
US 9106530B1 · Wang · 2015 [cited by examiner]
US 9118429B2 · Bourakov · 2015 [cited by examiner]
US 9143557B2 · Guichard · 2015 [cited by examiner]
US 9614906B1 · Hegde · 2017 [cited by examiner]
US 9660891B2 · Marshall · 2017 [cited by applicant]
US 9998247B1 · Choudhury · 2018 [cited by examiner]
US 10116467B2 · Brissette et al. · 2018 [cited by applicant]
US 10135683B1 · Medved et al. · 2018 [cited by applicant]
US 11799929B1 · Nandy · 2023 [cited by examiner]
US 11929906B2 · Brissette · 2024 [cited by examiner]
US 20030117954A1 · De Neve et al. · 2003 [cited by applicant]
US 20030135645A1 · Oki · 2003 [cited by examiner]
US 20030156536A1 · Oki · 2003 [cited by examiner]
US 20060206597A1 · Kim · 2006 [cited by examiner]
US 20070047557A1 · Martini · 2007 [cited by examiner]
US 20070058568A1 · Previdi · 2007 [cited by examiner]
US 20070204002A1 · Calderone · 2007 [cited by examiner]
US 20070254661A1 · Chowdhury · 2007 [cited by examiner]
US 20100172350A1 · Spencer · 2010 [cited by examiner]
US 20100299414A1 · Nyman · 2010 [cited by applicant]
US 20110295978A1 · Pazos · 2011 [cited by examiner]
US 20120063779A1 · Zhang · 2012 [cited by examiner]
US 20120087319A1 · Raleigh · 2012 [cited by examiner]
US 20120089845A1 · Raleigh · 2012 [cited by examiner]
US 20120096513A1 · Raleigh · 2012 [cited by examiner]
US 20130117449A1 · Hares et al. · 2013 [cited by applicant]
US 20130166774A1 · Pruthi et al. · 2013 [cited by applicant]
US 20130250810A1 · Ho · 2013 [cited by examiner]
US 20140098671A1 · Raleigh · 2014 [cited by examiner]
US 20140376371A1 · Flinck et al. · 2014 [cited by applicant]
US 20150010301A1 · Previdi · 2015 [cited by examiner]
US 20150181415A1 · Raleigh · 2015 [cited by examiner]
US 20150312055A1 · Varga et al. · 2015 [cited by applicant]
US 20150341450A1 · Reunamaki · 2015 [cited by examiner]
US 20170026288A1 · Yang et al. · 2017 [cited by applicant]
US 20170064039A1 · Shen · 2017 [cited by examiner]
US 20170093834A1 · Natu et al. · 2017 [cited by applicant]
US 20170257228A1 · Chen · 2017 [cited by examiner]
US 20200014623A1 · Wang · 2020 [cited by examiner]
US 20200220806A1 · Gera et al. · 2020 [cited by applicant]
US 20210111999A1 · Gandhi et al. · 2021 [cited by applicant]
US 20210160310A1 · Azizullah et al. · 2021 [cited by applicant]
US 20220124024A1 · Liu · 2022 [cited by examiner]
US 20220132623A1 · Xu · 2022 [cited by examiner]
US 20220329486A1 · Nagaprakash · 2022 [cited by examiner]
US 20220345440A1 · Gao · 2022 [cited by examiner]
US 20220393936A1 · Chen · 2022 [cited by applicant]
US 20230034314A1 · Brissette · 2023 [cited by applicant]
US 20230130720A1 · Raleigh · 2023 [cited by examiner]
US 20230148236A1 · Brissette · 2023 [cited by applicant]
US 20230216775A1 · Xu · 2023 [cited by examiner]
US 20240163197A1 · Brissette · 2024 [cited by examiner]
CN 112769614A · 2021 [cited by applicant]
The PCT Search Report and Written Opinion mailed Oct. 6, 2022 for PCT application No. PCT/US2022/038529, 44 pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/547,735, mailed on Aug. 17, 2023, Inventor #1 Patrice Brissette, “Source—Provisioned Services Infrastructure,” 16 pages. [cited by applicant]
PCT Search Report and Written Opinion mailed Mar. 3, 2023 for PCT application No. PCT/US2022/048964, 16 pages. [cited by applicant]
Stephane Betge-Brezetz et al: “Pro-Active SLA Assurance for Next Generation Network”, Mar. 6, 2002 (Mar. 6, 2002), XP055286709, Retrieved from the Internet: URL:http://www-rp.lip6.fr/adanets/PublicDoc/Papers/wtc2002_;Pr… [cited by applicant]
Vukovic R et al: “Approach To E2E Service Assurance On the Mobile Internet”, Ericsson Review (Incl. On), Telefonaktiebolaget L M Ericsson, SE, No. 3, Jan. 1, 2001 (Jan. 1, 2001), pp. 140-149, XP001081071, ISSN: 0014-017… [cited by applicant]
Office Action for U.S. Appl. No. 17/970,077, Dated Oct. 24, 2024, Brissette, “On-Demand Service Instantiation”, 17 pages. [cited by applicant]
Office Action for European Application No. 22764934.0, Dated Jan. 16, 2025, 9 pages. [cited by applicant]
Office Action for U.S. Appl. No. 17/970,077 Dated Feb. 10, 2025, Brissette, “On-Demand Service Instantiation,” 18 pages. [cited by applicant]
Rekhter, et al., “A Border Gateway Protocol (BGP-4)”, Network Working Group, Jan. 2006, pp. 1-103. [cited by applicant]