# US 12,009,998 B1 · Core network support for application requested network service level objectives > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,009,998 B1 - Document ID: US12009998B1 - Status: Granted - Kind: B1 - Application number: 18/202,080 - Filed: 2023-05-25 - Granted: 2024-06-11 - Earliest claimed: 2023-05-25 - Assignees: Cisco Technology, Inc. - Applicants: Cisco Technology, Inc. - Inventors: Saswat Praharaj; Fabio R. Maino; Alberto Rodriguez Natal; Pradeep Kumar Kathail; Bruce McDougall - Web page: https://patentgrep.com/patent/US12009998B1 ## CPC - H04L 41/5019: Ensuring fulfilment of SLA - H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Techniques for informing a network of an application's service-level agreement (SLA) objective(s) so the network can ensure the SLA is met end-to-end, thereby allowing core network support of deterministic SLA and application-based routing without using network-based application recognition (NBAR) and/or compromising user privacy. The techniques may include receiving a first connection request to establish a network-domain connection between different network domains that meets or exceeds a service level objective. Based on the first connection request, the network-domain connection may be established between the different network domains to meet or exceed the service-level objective. In some examples, a second connection request may be received to establish a tunnel between a source application and a destination application, which are disposed in the different network domains. Based on the second connection request, the techniques may include establishing the tunnel between the source application and the destination application utilizing the network-domain connection. ## Claims ### Claim 1 A method performed at least partially by a controller associated with a software-defined wide area network (SD-WAN), the method comprising: receiving an initial connection request to establish, on behalf of a source application, a network-domain connection between a source network domain and a destination network domain, the initial connection request including a requested network service level agreement (SLA) for the network-domain connection; establishing, between the source network domain and the destination network domain, the network-domain connection having a network SLA that meets or exceeds the requested network SLA along a middle mile portion of a network path associated with the network-domain connection, the middle mile portion including one or more underlay transport networks; receiving a subsequent connection request to establish, on behalf of the source application, a virtual tunnel between the source application and a destination application, the source application disposed in the source network domain and the destination application disposed in the destination network domain; and establishing the virtual tunnel between the source application and the destination application utilizing the network-domain connection such that traffic sent between the source application and the destination application is handled according to the requested network SLA along the middle mile portion of the network path. ### Claim 2 (depends on 1) The method of claim 1, wherein establishing the network-domain connection comprises programming an underlay transport network of the one or more underlay transport networks disposed between the source network domain and the destination network domain with the requested SLA for the network-domain connection. ### Claim 3 (depends on 2) The method of claim 2, wherein the underlay transport network is programmed by the controller via an application programming interface (API) exposed by the underlay transport network. ### Claim 4 (depends on 1) The method of claim 1, wherein the requested network SLA for the network-domain connection includes at least one of: a minimum bandwidth objective, a maximum jitter objective, a maximum loss objective, or or a maximum latency objective. ### Claim 5 (depends on 1) The method of claim 1, further comprising associating a unique identifier with the network-domain connection, wherein establishing the virtual tunnel between the source and the destination utilizing the network-domain connection is based at least in part on the subsequent connection request including the unique identifier. ### Claim 6 (depends on 1) The method of claim 1, wherein the subsequent connection request includes at least one of: a source subnet prefix or a source internet protocol (IP) address, a destination subnet prefix or a destination IP address, and a unique identifier associated with the network-domain connection. ### Claim 7 (depends on 1) The method of claim 1, wherein the source network domain and the destination network domain are different virtual private clouds (VPCs), virtual routing and forwarding (VRF) instances, or virtual local area networks (VLANs) present in at least one of an on-premises enterprise network, an edge network, a co-located network, or a cloud provider network. ### Claim 8 A system associated with a controller of a software-defined wide area network (SD-WAN) disposed between a source network domain and a destination network domain, the system comprising: one or more processors; and one or more non-transitory computer-readable media storing instructions that, when executed, cause the one or more processors to perform operations comprising: receiving an initial connection request to establish, on behalf of a source application, a network-domain connection between the source network domain and the destination network domain, the initial connection request including a requested network service level agreement (SLA) for the network-domain connection; establishing, between the source network domain and the destination network domain, the network-domain connection having a network SLA that meets or exceeds the requested network SLA along a middle mile portion of a network path associated with the network-domain connection, the middle mile portion including one or more underlay transport networks; receiving a subsequent connection request to establish, on behalf of the source application, a virtual tunnel between the source application and a destination application, the source application disposed in the source network domain and the destination application disposed in the destination network domain; and establishing the virtual tunnel between the source application and the destination application utilizing the network-domain connection such that traffic sent between the source application and the destination application is handled according to the requested network SLA along the middle mile portion of the network path. ### Claim 9 (depends on 8) The system of claim 8, wherein establishing the network-domain connection comprises programming an underlay transport network of the one or more underlay transport networks disposed between the source network domain and the destination network domain with the requested SLA for the network-domain connection. ### Claim 10 (depends on 9) The system of claim 9, wherein the underlay transport network is programmed, by the controller, via an application programming interface (API) exposed by the underlay transport network. ### Claim 11 (depends on 8) The system of claim 8, wherein the requested network SLA for the network-domain connection includes at least one of: a minimum bandwidth objective, a maximum jitter objective, a maximum loss objective, or or a maximum latency objective. ### Claim 12 (depends on 8) The system of claim 8, the operations further comprising associating a unique identifier with the network-domain connection, wherein establishing the virtual tunnel between the source and the destination utilizing the network-domain connection is based at least in part on the subsequent connection request including the unique identifier. ### Claim 13 (depends on 8) The system of claim 8, wherein the subsequent connection request includes at least one of: a source subnet prefix or a source internet protocol (IP) address, a destination subnet prefix or a destination IP address, and a unique identifier associated with the network-domain connection. ### Claim 14 (depends on 8) The system of claim 8, wherein the source network domain and the destination network domain are different virtual private clouds (VPCs), virtual routing and forwarding (VRF) instances, or virtual local area networks (VLANs) present in at least one of an on-premises enterprise network, an edge network, a co-located network, or a cloud provider network. ### Claim 15 One or more non-transitory computer-readable media storing instructions that, when executed, cause one or more processors to perform operations comprising: receiving an initial connection request to establish, on behalf of a source application, a network-domain connection between a source network domain and a destination network domain, the initial connection request including a requested network service level agreement (SLA) for the network-domain connection; establishing, between the source network domain and the destination network domain, the network-domain connection having a network SLA that meets or exceeds the requested network SLA along a middle mile portion of a network path associated with the network-domain connection, the middle mile portion including one or more underlay transport networks; receiving a subsequent connection request to establish, on behalf of the source application, a virtual tunnel between the source application and a destination application, the source application disposed in the source network domain and the destination application disposed in the destination network domain; and establishing the virtual tunnel between the source application and the destination application utilizing the network-domain connection such that traffic sent between the source application and the destination application is handled according to the requested network SLA along the middle mile portion of the network path. ### Claim 16 (depends on 15) The one or more non-transitory computer-readable media of claim 15, wherein establishing the network-domain connection comprises programming, via an exposed application programming interface (API), an underlay transport network of the one or more underlay transport networks disposed between the source network domain and the destination network domain with the requested network SLA for the network-domain connection. ### Claim 17 (depends on 15) The one or more non-transitory computer-readable media of claim 15, wherein the requested network SLA for the network-domain connection includes at least one of: a minimum bandwidth objective, a maximum jitter objective, a maximum loss objective, or or a maximum latency objective. ### Claim 18 (depends on 15) The one or more non-transitory computer-readable media of claim 15, the operations further comprising associating a unique identifier with the network-domain connection, wherein establishing the virtual tunnel between the source and the destination utilizing the network-domain connection is based at least in part on the subsequent connection request including the unique identifier. ### Claim 19 (depends on 15) The one or more non-transitory computer-readable media of claim 15, wherein the subsequent connection request includes at least one of: a source subnet prefix or a source internet protocol (IP) address, a destination subnet prefix or a destination IP address, and a unique identifier associated with the network-domain connection. ### Claim 20 (depends on 15) The one or more non-transitory computer-readable media of claim 15, wherein the source network domain and the destination network domain are different virtual private clouds (VPCs), virtual routing and forwarding (VRF) instances, or virtual local area networks (VLANs) present in at least one of an on-premises enterprise network, an edge network, a co-located network, or a cloud provider network.