WO2023114649A1 - Procédé de partage d'une connexion de commande - Google Patents

Procédé de partage d'une connexion de commande Download PDF

Info

Publication number
WO2023114649A1
WO2023114649A1 PCT/US2022/080876 US2022080876W WO2023114649A1 WO 2023114649 A1 WO2023114649 A1 WO 2023114649A1 US 2022080876 W US2022080876 W US 2022080876W WO 2023114649 A1 WO2023114649 A1 WO 2023114649A1
Authority
WO
WIPO (PCT)
Prior art keywords
tenant
controller
identifier
edge router
control connection
Prior art date
Application number
PCT/US2022/080876
Other languages
English (en)
Inventor
Srilatha Tangirala
Rahul Hardikar
Sheikh Qumruzzaman
Ravi Kiran CHINTALLAPUDI
Samir Thoria
Ajeet Pal Singh GILL
Vivek Agarwal
Original Assignee
Cisco Technology, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/709,877 external-priority patent/US11778038B2/en
Application filed by Cisco Technology, Inc. filed Critical Cisco Technology, Inc.
Priority to CA3234999A priority Critical patent/CA3234999A1/fr
Publication of WO2023114649A1 publication Critical patent/WO2023114649A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]

Definitions

  • the present disclosure relates generally to communication networks, and more specifically to systems and methods for sharing a control connection in a software-defined wide area network (SD-WAN) environment.
  • SD-WAN software-defined wide area network
  • Multi-tenancy is a concept that refers to the logical isolation of shared virtual compute, storage, and/or network resources.
  • multiple independent instances e.g., Layer-3 virtual routing and forwarding instances (VRFs) or Layer- 2 virtual local area network instances (VLANs)
  • VRFs Layer-3 virtual routing and forwarding instances
  • VLANs Layer- 2 virtual local area network instances
  • Service providers may use multi-tenancy to achieve effective utilization of network components.
  • FIGURE 1 illustrates an example system for sharing a control connection in an SD-WAN environment
  • FIGURE 2 illustrates an example method for sharing a control connection in an SD-WAN environment
  • FIGURE 3 illustrates an example computer system that may be used by the systems and methods described herein.
  • an edge router includes one or more processors and one or more computer-readable non-transitory storage media coupled to the one or more processors and including instructions that, when executed by the one or more processors, cause the edge router to perform operations.
  • the operations include onboarding a first tenant from a network management system and determining a mapping of a tenant identifier associated with the first tenant to a controller identifier associated with a controller.
  • the operations also include reserving a port number in a kernel for the first tenant and inserting the tenant identifier into a first control packet.
  • the operations further include communicating the first control packet to the controller via an encrypted control connection during a first peering session.
  • the first peering session shares the encrypted control connection with a second peering session.
  • the operations include onboarding a second tenant from the network management system.
  • the first tenant may be associated with the first peering session and a first VRF instance, and/or the second tenant may be associated with the second peering session and a second VRF instance.
  • the controller uses the tenant identifier to determine the first VRF instance.
  • the tenant identifier is a global, 16-bit identifier that uniquely identifies the first tenant.
  • the operations include establishing, by a daemon installed on the edge router, the encrypted control connection with the controller, notifying, by the daemon, an Overlay Management Protocol (OMP) of the encrypted control connection, and communicating, by the OMP, an association between the port number and the tenant identifier to the daemon.
  • OMP Overlay Management Protocol
  • the operations include receiving a second control packet from the controller via the encrypted control connection, decrypting the second control packet, identifying a destination port associated with the second control packet, writing the second control packet to the kernel, and/or determining, by the kernel, to place the second control packet on a socket based on the destination port.
  • the encrypted control connection is a Datagram Transport Layer Security (DTLS) control connection
  • the router is an SD-WAN edge router
  • the port is a Transmission Control Protocol (TCP) port.
  • DTLS Datagram Transport Layer Security
  • TCP Transmission Control Protocol
  • a method includes onboarding, by an edge router, a first tenant from a network management system and determining, by the edge router, a mapping of a tenant identifier associated with the first tenant to a controller identifier associated with a controller.
  • the method also includes reserving, by the edge router, a port number in a kernel for the first tenant and inserting, by the edge router, the tenant identifier into a first control packet.
  • the method further includes communicating, by the edge router, the first control packet to the controller via an encrypted control connection during a first peering session. The first peering session shares the encrypted control connection with a second peering session.
  • one or more computer-readable non- transitory storage media embody instructions that, when executed by a processor, cause the processor to perform operations.
  • the operations include onboarding a first tenant from a network management system and determining a mapping of a tenant identifier associated with the first tenant to a controller identifier associated with a controller.
  • the operations also include reserving a port number in a kernel for the first tenant and inserting the tenant identifier into a first control packet.
  • the operations further include communicating the first control packet to the controller via an encrypted control connection during a first peering session.
  • the first peering session shares the encrypted control connection with a second peering session.
  • Multi-tenancy in the control plane can be achieved by creating a separate control connection per-tenant. Separate control connections require the addition of more end points, which increases overhead on the system. With multiple control connections to the controllers, the cost to poll the connections increases. This makes it challenging to achieve higher scalability.
  • Certain embodiments of this disclosure include systems and methods for scaling out multi-tenancy on SD-WAN edge devices by developing a shared control plane infrastructure across the tenants, which allows the delivery of a cloud scale architecture.
  • a centralized network management system’s placement logic of the tenants’ association to the controllers allows for high performance optimization. By multiplexing several tenants into a shared control connection infrastructure, controllers can be more efficiently utilized to achieve higher scalability.
  • a network management system generates a global, 2 byte (16-bit) tenant identifier for each tenant and inserts the tenant identifier rather than a tenant name (which is 128 bytes long) into control packets to uniquely identify a tenant, which reduces the size of the control packets. This also helps in preventing fragmentation of the control packet between controllers (e.g., a controller or an orchestrator) and routers (e.g., an edge router).
  • the global tenant identifier is used in the stack on the edge router to infer the tenant keys for lookup, which reduces the storage space used in the databases/trees.
  • control plane interfaces are optimized to achieve multitenancy with minimal overhead such that the overall service and/or output using the system resources is increased.
  • the total number of control connections to controllers are reduced per-tenant compared to traditional multi-tenant solutions. For example, if a multi -tenant edge device has 100 tenants and each tenant is mapped to two controllers, 200 (2x100) control connections are used through one transport interface on the multi -tenant edge device. For a controller with eight transport interfaces, the total number of connections would be 100 connections per-tenant times two controllers times eight transport interfaces, or 1600 connections (100x2x8).
  • two controllers with eight transport interfaces and one connection per controller for all 100 tenants equals 16 control connections (1x2x8), which brings down the control connection count by 1584 connections. Reducing the number of control connections reduces the total resources used on the system. For example, the number of sockets used for creating the control connection is reduced. As another example, the amount of memory on the system is reduced. As still another example, the bandwidth is reduced since the number of hello packets sent every second on every control connection is reduced.
  • This disclosure describes systems and methods for sharing a control connection in an SD-WAN environment.
  • multi-tenancy is used to achieve effective utilization of SD-WAN components.
  • Multiple tenants are placed on a single edge device or single gateway.
  • tenants use overlapping prefixes.
  • Certain embodiments of this disclosure advertise each tenant’s route to a controller by sharing one secured control connection across all the tenants, which may reduce the operational cost and overhead on the system.
  • FIGURE 1 illustrates an example system 100 for sharing a control connection in an SD-WAN environment.
  • System 100 or portions thereof may be associated with an entity, which may include any entity, such as a business, company, or enterprise, that shares control connections in an SD-WAN environment.
  • the entity may be a service provider that provides services for sharing control connections.
  • the components of system 100 may include any suitable combination of hardware, firmware, and software.
  • the components of system 100 may use one or more elements of the computer system of FIGURE 3.
  • system 100 includes a network 110, a controller 120, controller identifier 122, OMP instances 124, a management node 130, tenants 132, tenant identifiers 134, a tenant-controller map 136, VRFs 138, an edge node 140, an orchestrator node 150, a control connection 160, peering sessions 162, packets 164, daemons 170, a tenant-port map 180, and port numbers 182.
  • Network 110 of system 100 is any type of network that facilitates communication between components of system 100.
  • Network 110 may connect one or more components of system 100.
  • One or more portions of network 110 may include an ad-hoc network, the Internet, an intranet, an extranet, a virtual private network (VPN), an Ethernet VPN (EVPN), a LAN, a wireless LAN (WLAN), a VLAN, a wide area network (WAN), a wireless WAN (WWAN), an SD-WAN, a metropolitan area network (MAN), a portion of the Public Switched Telephone Network (PSTN), a cellular telephone network, a Digital Subscriber Line (DSL), an Multiprotocol Label Switching (MPLS) network, a 3G/4G/5G network, a Long Term Evolution (LTE) network, a cloud network, a combination of two or more of these, or other suitable types of networks.
  • VPN virtual private network
  • EVPN Ethernet VPN
  • WLAN wireless LAN
  • VLAN wide area network
  • WAN wide area network
  • Network 110 may include one or more different types of networks.
  • Network 110 may be any communications network, such as a private network, a public network, a connection through the Internet, a mobile network, a WIFI network, etc.
  • Network 110 may include a core network, an access network of a service provider, an Internet service provider (ISP) network, and the like.
  • ISP Internet service provider
  • One or more components of system 100 may communicate over network 110.
  • network 110 is an SD-WAN.
  • Network 110 may include one or more nodes. Nodes are connection points within network 110 that receive, create, store and/or send data along a path. Nodes may include one or more redistribution points that recognize, process, and forward data to other nodes of network. Nodes may include virtual and/or physical nodes. Nodes may include one or more virtual machines, hardware devices, bare metal servers, and the like. As another example, nodes may include data communications equipment such as computers, routers, servers, printers, workstations, switches, bridges, modems, hubs, and the like. In certain embodiments, nodes use static and/or dynamic routing to send data to and/or receive data to other nodes of system 100. In the illustrated embodiment of FIGURE 1, nodes include controller 120, a management node 130, edge node 140, and an orchestrator node 150.
  • Controller 120 of system 100 monitors, operates, manages, troubleshoots, and/or maintains services related to network 110.
  • controller 120 is a centralized controller that oversees the control plane of network 110. Controller 120 may manage provisioning, maintenance, and/or security for network 110. In some embodiments, controller 120 is primarily involved in control plane communication and does not handle data traffic. However, controller 120 may control the flow of data traffic throughout network 110. In certain embodiments, controller 120 works with orchestrator node 150 of system 100 to authenticate edge node 140 as edge node 140 joins network 110. In certain embodiments, controller 120 is assigned a controller identifier 122. Controller identifier 122 is any representation that uniquely identifies controller 120. For example, controller identifier 122 may be a Unique Device Identifier (UDI).
  • UFI Unique Device Identifier
  • Management node 130 of system 100 is a centralized network management system that allows a user to configure and/or manage the overlay network of network 110.
  • management node 130 includes a dashboard (e.g., a graphical dashboard).
  • the dashboard of management node 130 may provide a visual window into network 110 that allows a user to configure and/or manage edge node 140.
  • management node 130 is software that runs on one or more servers of network 110. This server may be situated in a centralized location (e.g., a data center).
  • the software of management node 130 may run on the same physical server as the software of another network component (e.g., controller 120).
  • a user creates tenants 132 in the centralized network management system of management node 130.
  • Tenants 132 e.g., tenant 132a, tenant 132b, and tenant 132c
  • Tenants 132 are logical containers for application policies.
  • Tenants 132 may allow administrators to exercise domain-based access control.
  • tenants 132 are units of isolation from a policy perspective.
  • Tenants 132 may represent customers in a service provider setting, organizations or domains in an enterprise setting, groups of policies, and the like.
  • Tenants 132 may include one or more filters, contracts, outside networks, bridge domains, VRFs 138, application profiles, etc.
  • each tenant 132 (e.g., tenant 132a, tenant 132b, and tenant 132c) is associated with a tenant name (e.g., a tenant organization name). The tenant name is 128 bits long.
  • each tenant 132 (e.g., tenant 132a, tenant 132b, and tenant 132c) is associated with a tenant identifier 134 (e.g., tenant identifier 134a, tenant identifier 134b, and tenant identifier 134c).
  • Tenant identifiers 134 uniquely identify tenants 132.
  • tenant identifier 134a uniquely identifies tenant 132a
  • tenant identifier 134b uniquely identifies tenant 132b
  • tenant identifier 134c uniquely identifies tenant 132c.
  • management node 130 generates tenant identifiers 134.
  • Each tenant identifier 134 is a global, 16-bit identifier.
  • management node 130 generates tenant-controller map 136.
  • management node 130 may include a placement logic that generates tenantcontroller map 136 by mapping tenants 132 to controller 120 based on an expected device count.
  • Tenant-controller map 136 may be a JavaScript Object Notation (JSON) map, aYAML map, and the like.
  • tenant-controller map 136 includes a mapping of tenant identifier 134a to controller identifier 122, a mapping of tenant identifier 134b to controller identifier 122 and a mapping of tenant identifier 134c to controller identifier 122.
  • JSON JavaScript Object Notation
  • management node 130 communicates tenant-controller map 136 to orchestrator node 150 (see notation 190) and/or controller 120 (see notation 191). In some embodiments, management node 130 communicates tenant-controller map 136 to orchestrator node 150 (see notation 190) and/or controller 120 (see notation 191) once tenantcontroller map 136 is complete.
  • Edge node 140 of system 100 is a connection point (e.g., an edge router) within network 110 that receives, creates, stores, and/or communicates data along a path. Edge node 140 provides one or more interfaces for communicating with other nodes of network 110. In certain embodiments, edge node 140 is single device for connecting and/or securing enterprise traffic to the cloud. Edge node 140 may include one or more hardware devices, software (e.g., a cloud router) that runs as a virtual machine, and the like. In some embodiments, edge node 140 handles the transmission of data traffic.
  • edge node 140 onboards one or more tenants 132 from management node 130.
  • edge node 140 may be configured to define the infrastructure boundaries and/or resource limits that are applied automatically when a user makes a service request, via a dashboard of management node 130, to provision one or more tenants 132.
  • edge node 140 onboards one or more VRFs 138 associated with tenants 132.
  • VRF is a technology that allows multiple instances of a routing table to co-exist within the same router (e.g., edge node 140) at the same time.
  • VRFs 138 e.g., VRF 138al, VRF 138a2, VRF 138bl, VRF 138cl, and VRF 138c2
  • tenant networks e.g., contexts or private networks.
  • each VRF 138 is a unique Layer 3 forwarding and application policy domain.
  • Each VRF 138 may define a Layer 3 address domain.
  • edge node 140 may configure and/or assign one or more VRFs 138.
  • Each VRF 138 may be associated with one or more bridge domains.
  • VRFs 138 may be created for the logical device, which may provide a selection criteria policy for a device cluster.
  • a logical device may be selected based on a contract name, a graph name, the function node name inside the graph, etc.
  • tenant 132a includes VRF 138al and VRF 138a2
  • tenant 132b incudes VRF 138bl
  • tenant 132c includes VRF 138cl and VRF 138c2.
  • One or more VRFs 138 may be associated with a different department (e.g., finance, engineering, sales, human resources, marketing, etc.).
  • edge node 140 establishes and maintains connection 160 with controller 120 of network 110.
  • Connection 160 of system 100 is a secure, encrypted control plane connection.
  • connection 160 runs as a Datagram Transport Layer Security (DTLS) tunnel between edge node 140 and controller 120.
  • edge node 140 initiates one or more peering sessions 162 with controller 120 via connection 160. Peering sessions 162 are used to exchange control plane traffic between edge node 140 and controller 120.
  • DTLS Datagram Transport Layer Security
  • peering session 162a is associated with tenant 132a, VRF 138al, and VRF 138a2; peering session 162b is associated with tenant 132b and VRF 138bl; and peering session 162c is associated with tenant 132c, VRF 138cl, and VRF 138c2.
  • peering sessions 162 are OMP peering sessions 152.
  • OMP 124 is the protocol responsible for establishing and maintaining the control plane.
  • OMP 124 may orchestrate the overlay network communication, including connectivity among network sites, service chaining, and VPN or VRF topologies.
  • OMP 124 may distribute servicelevel routing information and related location mappings, data plane security parameters, routing policies, and the like.
  • OMP 124 is used to exchange routing, policy, and/or management information between edge node 140 and controller 120 in network 110.
  • OMP routes advertise VRFs 138 (e.g., VRF 138al) to which the routes belong.
  • an OMP hold time determines how long to wait before closing control connection 160. For example, if the peer (e.g., edge node 140 or controller 120) does not receive three consecutive keepalive messages within the hold time, connection 160 to the peer may be closed.
  • edge node 140 includes daemon 170a.
  • Daemon 170a is a computer program that runs as a background process (rather than being under the direct control of an interactive user). Daemon 170a may be locally installed on edge node 140.
  • daemon 170a brings up connection 160 with controller 120. Daemon 170a may bring up connection 160 only if connection 160 is set up for the first time to controller 120.
  • daemon 170a after connection 160 comes up, daemon 170a notifies OMP 124 of connection 160 by sending a control-device-add message via a Tunnel Table manager (TTM).
  • TTM Tunnel Table manager
  • OMP 124 reserves one or more port numbers 182 (e.g., Transmission Control Protocol (TCP) port numbers) on edge node 140.
  • Port numbers 182 e.g., port number 182a, port number 182b, and port number 182c
  • TCP Transmission Control Protocol
  • Port numbers 182 are numbers (e.g., a 16-bit unassigned number) used to identify each port for each transport protocol and/or address combination.
  • OMP 124 may reserve port number 182a in a kernel for peering session 162a (associated with tenant 132a); OMP 124 may reserve port number 182b in a kernel for peering session 162b (associated with tenant 132b); and OMP 124 may reserve port number 182c in a kernel for peering session 162c (associated with tenant 132c).
  • OMP 124 generates tenant-port map 180. OMP 124 may generate tenant-port map 180 by associating tenant identifiers 134 with reserved port numbers 182.
  • OMP 124 may associate tenant identifier 134a (representing tenant 132a) with reserved port number 182a; OMP 124 may associate tenant identifier 134b (representing tenant 132b) with reserved port number 182b; and OMP 124 may associate tenant identifier 134c (representing tenant 132c) with reserved port number 182c.
  • OMP 124 communicates tenant-port map 180 to local daemon 170a.
  • daemon 170a of edge node 140 communicates packets 164 to controller 120 via connection 160.
  • Packets 164 are formatted units of data carried by network 110. Packets 164 may be any suitable types of packets (e.g., TCP packets or User Datagram Protocol (UDP) packets). Packets 164 include control information, which provides data for delivering user data (e.g., payload).
  • daemon 170a communicates packet 164a to controller 120 via peering session 162a of connection 160; daemon 170a communicates packet 164b to controller 120 via peering session 162b of connection 160; and daemon 170a communicates packet 164c to controller 120 via peering session 162c of connection 160.
  • daemon 170a inserts an appropriate tenant identifier 134 into every packet 164. For example, in the illustrated embodiment of FIGURE 1, daemon 170a inserts tenant identifier 134a into packet 164a; daemon 170a inserts tenant identifier 134b into packet 164c; and daemon 170a inserts tenant identifier 134c into packet 164c.
  • daemon 170a communicates packets 164 via encrypted, secured connection 160 to controller 120.
  • Controller 120 may run multiple OMP instances 124, one per tenant 132.
  • controller 120 may run OMP instance 124a for tenant 132a; controller 120 may run OMP instance 124b for tenant 132b; and controller 120 may run OMP instance 124c for tenant 132c.
  • controller 120 includes daemon 170b.
  • Daemon 170b is a computer program that runs as a background process (rather than being under the direct control of an interactive user). Daemon 170b may be locally installed on controller 120.
  • daemon 170b maintains a mapping of tenant identifier 134 to tenant context for demultiplexing.
  • daemon 170b identifies the tenant context based on tenant identifier 134 (e.g., tenant identifier 134a, tenant identifier 134b, or tenant identifier 134c, respectively) and relays packet 164 to the appropriate OMP instance 124 (e.g., OMP instance 124a, OMP instance 124b, or OMP instance 124c, respectively).
  • OMP instance 124 e.g., OMP instance 124a, OMP instance 124b, or OMP instance 124c, respectively.
  • OMP peering comes up when peering session 162 (e.g., peering session 162a, peering session 162, or peering session 162c) is established.
  • daemon 170a of edge node 140 decrypts packet 164 and writes packet 164 to the kernel.
  • the kernel places packet 164 on the appropriate socket.
  • the kernel may place packet 164 on the appropriate socket based the destination port (e.g., port number 182) of packet 164.
  • the destination port is included in a four-tuple. Other information included in the four-tuple may also be used to place packet 164 on the appropriate socket.
  • Orchestrator node 150 of system 100 automatically orchestrates connectivity between edge node 140 and controller 120 of system 100.
  • orchestrator node 150 is software that runs as a process (e.g., a daemon) on edge node 140 and/or controller 120.
  • orchestrator node 150 has a persistent control plane connection (e.g., a DTLS tunnel connection) with controller 120.
  • a DTLS tunnel connection e.g., a DTLS tunnel connection
  • orchestrator node 150 communicates with edge node 140.
  • orchestrator node 150 may use a DTLS connection to communicate with edge node 140 when edge node 140 comes online.
  • Orchestrator node 150 may authenticate edge node 140 and facilitate the ability of edge node 140 to join network 110.
  • orchestrator node 150 receives (see notation 190) tenant-controller map 136 from management node 130. Orchestrator node 150 may communicate tenant-controller map 136 to edge node 140. For example, orchestrator node 150 may communicate (see notation 194) tenant-controller map 136 to edge node 140 in response to receiving (see notation 193) a request from edge node 140 for information related to a particular tenant 132 (e.g., tenant-controller map 136).
  • management node 130 of system 100 creates tenants 132 (e.g., tenant 132a, tenant 132b, and tenant 132c).
  • tenants 132 e.g., tenant 132a, tenant 132b, and tenant 132c.
  • a user e.g., a service provider
  • Management node 130 generates tenant-controller map 136, which maps tenants 132 to controller 120.
  • tenant-controller map 136 Once tenant-controller map 136 is complete, management node 130 communicates tenant-controller map 136 to orchestrator node 150 (see notation 190) and controller 120 (see notation 191).
  • Tenants 132 are then onboarded (see notation 192) onto edge node 140 from management node 130.
  • Edge node 140 requests (see notation 193) information associated with tenants 132 from orchestrator node 150, and orchestrator node 150 communicates (see notation 194) tenant-controller map 136 to edge node 140.
  • OMP 124 on edge node 140 reserves port number 182a, port number 182b, and port number 182c in kernels for tenant 132a, tenant 132b, and tenant 132c, respectively, and generates tenant-port map 180.
  • OMP 124 informs daemon 170a installed locally on edge node 140 about tenant-port map 180, and daemon 170a inserts appropriate tenant identifier 134 (e.g., tenant identifier 134a, tenant identifier 134b, or tenant identifier 134c) in every TCP control packet 164 (e.g., packet 164a, packet 164b, and packet 164c).
  • Edge node 140 then communicates control packets 164 (e.g., packet 164a, packet 164b, and packet 164c) to controller 120 via encrypted control connection 160.
  • Controller 120 runs OMP instance 124a, OMP instance 124b, and OMP instance 124c for tenant 132a, tenant 132b, and tenant 132c, respectively.
  • Daemon 170b installed locally on controller 120 maintains a mapping of tenant identifiers 134 to tenant context for demultiplexing.
  • daemon 170b locates the tenant context for tenant 132a based on tenant identifier 134a and communicates packet 164a to the appropriate OMP instance 124a.
  • controller 120 is more efficiently utilized to achieve higher scalability.
  • FIGURE 1 illustrates a particular number of networks 110, controllers 120, controller identifiers 122, OMP instances 124, management nodes 130, tenants 132, tenant identifiers 134, tenant-controller maps 136, VRFs 138, edge nodes 140, orchestrator nodes 150, control connections 160, peering sessions 162, packets 164, daemons 170, tenant-port maps 180, and port numbers 182, this disclosure contemplates any suitable number of networks 110, controllers 120, controller identifiers 122, OMP instances 124, management nodes 130, tenants 132, tenant identifiers 134, tenant-controller maps 136, VRFs 138, edge nodes 140, orchestrator nodes 150, control connections 160, peering sessions 162, packets 164, daemons 170, tenantport maps 180, and port numbers 182.
  • system 100 may include more or less than three tenants 132.
  • FIGURE 1 illustrates a particular arrangement of network 110, controller 120, controller identifiers 122, OMP instances 124, management node 130, tenants 132, tenant identifiers 134, tenant-controller map 136, VRFs 138, edge node 140, orchestrator node 150, control connection 160, peering sessions 162, packets 164, daemons 170, tenant-port map 180, and port numbers 182, this disclosure contemplates any suitable arrangement of network 110, controller 120, controller identifiers 122, OMP instances 124, management node 130, tenants 132, tenant identifiers 134, tenant-controller map 136, VRFs 138, edge node 140, orchestrator node 150, control connection 160, peering sessions 162, packets 164, daemons 170, tenant-port map 180, and port numbers 182.
  • FIGURE 1 describes and illustrates particular components, devices, or systems carrying out particular actions, this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable components, devices
  • FIGURE 2 illustrates an example method 200 for sharing a control connection in an SD-WAN environment.
  • Method 200 begins at step 205.
  • a first tenant is onboarded to a multi-tenant edge node.
  • the first tenant is onboarded from a network management system.
  • edge node 140 onboards (see notation 192) tenant 132a from a network management system of management node 130.
  • Method 200 then moves from step 210 to step 215, where the multitenant edge node determines a mapping of a first tenant identifier associated with the first tenant to a controller identifier associated with a controller.
  • the multi-tenant edge node receives the mapping from an orchestrator node.
  • edge node 140 may communicate (see notation 193) a request for information associated with tenant 132a to orchestrator node 150, and orchestrator node 150 may, in response to receiving the request, communicate (see notation 194) tenant-controller map 136 to edge node 140.
  • Method 200 then moves from step 215 to step 220.
  • the edge node determines whether an encrypted control connection has been established between the edge node and the controller. For example, referring to FIGURE 1, edge node 140 may determine whether daemon 170a has established connection 160 (e.g., aDTLS connection) with controller 120 of system 100. If the edge node determines that an encrypted control connection has been established between the edge node and the controller, method 200 advances from step 220 to step 230. If the edge node determines that an encrypted control connection has not been established between the edge node and the controller, method 200 moves from step 220 to step 225, where a program installed on the edge node establishes the encrypted control connection with the controller. For example, referring to FIGURE 1, daemon 170a installed on edge node 140 may establish connection 160 with controller 120. Method 200 then moves from step 225 to step 230.
  • connection 160 e.g., aDTLS connection
  • the program installed on the edge node notifies an OMP of the established encrypted control connection.
  • daemon 170a installed on edge node 140 notifies OMP 124 of established connection 160.
  • Method 200 then moves from step 230 to step 235, where the edge node reserves a first port number for the first tenant.
  • OMP 124 of edge node 140 may reserve port number 182a for tenant 132a.
  • OMP generates a tenant-port map that maps tenant identifiers to reserved port numbers.
  • OMP of edge node 140 may generate tenant-port map 180, which includes a mapping of tenant identifier 134a to port number 182a.
  • Method 200 then moves from step 235 to step 240.
  • the OMP communicates an association between the first port number and the first tenant identifier to the program installed on the edge node. For example, referring to FIGURE 1, OMP 124 communicates an association between tenant identifier 134a and port number 182a to daemon 170a. Method 200 then moves from step 240 to step 245, where the edge node inserts the first tenant identifier into the control packets for the first tenant. For example, referring to FIGURE 1, daemon 170a installed on edge node 140 may insert tenant identifier 134a into packets 164a for tenant 132a. Method 200 then moves from step 245 to step 250.
  • the edge node communicates the first control packet from the edge node to the controller via the encrypted control connection.
  • daemon 170a of edge node 140 may communicate packet 164a to controller 120.
  • Method 200 then moves from step 250 to step 255, where a second tenant is onboarded to the multi-tenant edge node.
  • the second tenant is onboarded from a network management system.
  • edge node 140 onboards (see notation 192) tenant 132b from a network management system of management node 130.
  • Method 200 then moves from step 255 to step 260, where the multitenant edge node determines a mapping of a second tenant identifier associated with the second tenant to the controller identifier associated with the controller.
  • the multi -tenant edge node receives the mapping from an orchestrator node.
  • edge node 140 may communicate (see notation 193) a request for information associated with tenant 132b to orchestrator node 150, and orchestrator node 150 may, in response to receiving the request, communicate (see notation 194) tenant-controller map 136 to edge node 140.
  • Tenant-controller map 136 includes a mapping of tenant identifier 134b associated with tenant 132b to controller identifier 122 associated with controller 120.
  • Method 200 then moves from step 260 to step 265.
  • the program installed on the edge node notifies the OMP of the established encrypted control connection.
  • daemon 170a installed on edge node 140 notifies OMP 124 of established connection 160.
  • Method 200 then moves from step 265 to step 270, where the edge node reserves a second port number for the second tenant.
  • OMP 124 of edge node 140 may reserve port number 182b for tenant 132b.
  • OMP generates a tenant-port map that maps tenant identifiers to reserved port numbers.
  • OMP of edge node 140 may generate tenant-port map 180, which includes a mapping of tenant identifier 134b to port number 182b.
  • Method 200 then moves from step 270 to step 275.
  • the edge node communicates an association between the first port number and the first tenant identifier to the program installed on the edge node. For example, referring to FIGURE 1, OMP 124 of edge node 140 communicates an association between tenant identifier 134b and port number 182b to daemon 170a. Method 200 then moves from step 275 to step 280, where the edge node inserts the second tenant identifier into the control packets for the second tenant. For example, referring to FIGURE 1, daemon 170a installed on edge node 140 may insert tenant identifier 134b into packets 164b for tenant 132b. Method 200 then moves from step 280 to step 285.
  • the edge node communicates the second control packet from the edge node to the controller via the encrypted control connection.
  • daemon 170a of edge node 140 may communicate packet 164b to controller 120 using peering session 162b via connection 160.
  • Method 200 then moves from step 285 to step 290, where method 200 ends.
  • controller 120 is more efficiently utilized to achieve higher scalability
  • FIGURE 2 illustrates particular steps of method 200 of FIGURE 2 as occurring in a particular order
  • this disclosure contemplates any suitable steps of method 200 of FIGURE 2 occurring in any suitable order.
  • this disclosure describes and illustrates an example method 200 for sharing a control connection in an SD- WAN environment including the particular steps of the method of FIGURE 2
  • this disclosure contemplates any suitable method for sharing a control connection in an SD-WAN environment, which may include all, some, or none of the steps of the method of FIGURE 2, where appropriate.
  • FIGURE 2 describes and illustrates particular components, devices, or systems carrying out particular actions
  • this disclosure contemplates any suitable combination of any suitable components, devices, or systems carrying out any suitable actions.
  • FIGURE 3 illustrates an example computer system 300.
  • one or more computer system 300 perform one or more steps of one or more methods described or illustrated herein.
  • one or more computer system 300 provide functionality described or illustrated herein.
  • software running on one or more computer system 300 performs one or more steps of one or more methods described or illustrated herein or provides functionality described or illustrated herein.
  • Particular embodiments include one or more portions of one or more computer system 300.
  • reference to a computer system may encompass a computing device, and vice versa, where appropriate.
  • reference to a computer system may encompass one or more computer systems, where appropriate.
  • computer system 300 may be an embedded computer system, a system-on-chip (SOC), a single-board computer system (SBC) (such as, for example, a computer-on-module (COM) or system-on-module (SOM)), a desktop computer system, a laptop or notebook computer system, an interactive kiosk, a mainframe, a mesh of computer systems, a mobile telephone, a personal digital assistant (PDA), a server, a tablet computer system, an augmented/virtual reality device, or a combination of two or more of these.
  • SOC system-on-chip
  • SBC single-board computer system
  • COM computer-on-module
  • SOM system-on-module
  • computer system 300 may include one or more computer system 300; be unitary or distributed; span multiple locations; span multiple machines; span multiple data centers; or reside in a cloud, which may include one or more cloud components in one or more networks.
  • one or more computer system 300 may perform without substantial spatial or temporal limitation one or more steps of one or more methods described or illustrated herein.
  • one or more computer system 300 may perform in real time or in batch mode one or more steps of one or more methods described or illustrated herein.
  • One or more computer system 300 may perform at different times or at different locations one or more steps of one or more methods described or illustrated herein, where appropriate.
  • computer system 300 includes a processor 302, memory 304, storage 306, an input/output (I/O) interface 308, a communication interface 310, and a bus 312.
  • processor 302 memory 304
  • storage 306 storage 306
  • I/O input/output
  • communication interface 310 communication interface 310
  • bus 312 bus 312.
  • processor 302 includes hardware for executing instructions, such as those making up a computer program.
  • processor 302 may retrieve (or fetch) the instructions from an internal register, an internal cache, memory 304, or storage 306; decode and execute them; and then write one or more results to an internal register, an internal cache, memory 304, or storage 306.
  • processor 302 may include one or more internal caches for data, instructions, or addresses. This disclosure contemplates processor 302 including any suitable number of any suitable internal caches, where appropriate.
  • processor 302 may include one or more instruction caches, one or more data caches, and one or more translation lookaside buffers (TLBs).
  • TLBs translation lookaside buffers
  • Instructions in the instruction caches may be copies of instructions in memory 304 or storage 306, and the instruction caches may speed up retrieval of those instructions by processor 302.
  • Data in the data caches may be copies of data in memory 304 or storage 306 for instructions executing at processor 302 to operate on; the results of previous instructions executed at processor 302 for access by subsequent instructions executing at processor 302 or for writing to memory 304 or storage 306; or other suitable data.
  • the data caches may speed up read or write operations by processor 302.
  • the TLBs may speed up virtual-address translation for processor 302.
  • processor 302 may include one or more internal registers for data, instructions, or addresses. This disclosure contemplates processor 302 including any suitable number of any suitable internal registers, where appropriate. Where appropriate, processor 302 may include one or more arithmetic logic units (ALUs); be a multi-core processor; or include one or more processors 302. Although this disclosure describes and illustrates a particular processor, this disclosure contemplates any suitable processor.
  • ALUs
  • memory 304 includes main memory for storing instructions for processor 302 to execute or data for processor 302 to operate on.
  • computer system 300 may load instructions from storage 306 or another source (such as, for example, another computer system 300) to memory 304.
  • Processor 302 may then load the instructions from memory 304 to an internal register or internal cache.
  • processor 302 may retrieve the instructions from the internal register or internal cache and decode them.
  • processor 302 may write one or more results (which may be intermediate or final results) to the internal register or internal cache.
  • Processor 302 may then write one or more of those results to memory 304.
  • processor 302 executes only instructions in one or more internal registers or internal caches or in memory 304 (as opposed to storage 306 or elsewhere) and operates only on data in one or more internal registers or internal caches or in memory 304 (as opposed to storage 306 or elsewhere).
  • One or more memory buses (which may each include an address bus and a data bus) may couple processor 302 to memory 304.
  • Bus 312 may include one or more memory buses, as described below.
  • one or more memory management units reside between processor 302 and memory 304 and facilitate accesses to memory 304 requested by processor 302.
  • memory 304 includes random access memory (RAM). This RAM may be volatile memory, where appropriate.
  • this RAM may be dynamic RAM (DRAM) or static RAM (SRAM). Moreover, where appropriate, this RAM may be singleported or multi-ported RAM.
  • Memory 304 may include one or more memories 304, where appropriate. Although this disclosure describes and illustrates particular memory, this disclosure contemplates any suitable memory.
  • storage 306 includes mass storage for data or instructions.
  • storage 306 may include a hard disk drive (HDD), a floppy disk drive, flash memory, an optical disc, a magneto-optical disc, magnetic tape, or Universal Serial Bus (USB) drive or a combination of two or more of these.
  • HDD hard disk drive
  • floppy disk drive flash memory
  • optical disc an optical disc
  • magneto-optical disc magnetic tape
  • USB Universal Serial Bus
  • Storage 306 may include removable or non-removable (or fixed) media, where appropriate.
  • Storage 306 may be internal or external to computer system 300, where appropriate.
  • storage 306 is non-volatile, solid-state memory.
  • storage 306 includes read-only memory (ROM).
  • this ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM), or flash memory or a combination of two or more of these.
  • This disclosure contemplates mass storage 306 taking any suitable physical form.
  • Storage 306 may include one or more storage control units facilitating communication between processor 302 and storage 306, where appropriate. Where appropriate, storage 306 may include one or more storages 306. Although this disclosure describes and illustrates particular storage, this disclosure contemplates any suitable storage.
  • I/O interface 308 includes hardware, software, or both, providing one or more interfaces for communication between computer system 300 and one or more I/O devices.
  • Computer system 300 may include one or more of these I/O devices, where appropriate.
  • One or more of these I/O devices may enable communication between a person and computer system 300.
  • an I/O device may include a keyboard, keypad, microphone, monitor, mouse, printer, scanner, speaker, still camera, stylus, tablet, touch screen, trackball, video camera, another suitable I/O device or a combination of two or more of these.
  • An I/O device may include one or more sensors. This disclosure contemplates any suitable I/O devices and any suitable I/O interfaces 308 for them.
  • I/O interface 308 may include one or more device or software drivers enabling processor 302 to drive one or more of these I/O devices.
  • I/O interface 308 may include one or more I/O interfaces 308, where appropriate. Although this disclosure describes and illustrates a particular I/O interface, this disclosure contemplates any suitable I/O interface.
  • communication interface 310 includes hardware, software, or both providing one or more interfaces for communication (such as, for example, packet-based communication) between computer system 300 and one or more other computer system 300 or one or more networks.
  • communication interface 310 may include a network interface controller (NIC) or network adapter for communicating with an Ethernet or other wire-based network or a wireless NIC (WNIC) or wireless adapter for communicating with a wireless network, such as a WI-FI network.
  • NIC network interface controller
  • WNIC wireless NIC
  • WI-FI network wireless network
  • computer system 300 may communicate with an ad hoc network, a personal area network (PAN), a LAN, a WAN, a MAN, or one or more portions of the Internet or a combination of two or more of these.
  • PAN personal area network
  • LAN local area network
  • WAN wide area network
  • MAN metropolitan area network
  • One or more portions of one or more of these networks may be wired or wireless.
  • computer system 300 may communicate with a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network, a 3G network, a 4G network, a 5G network, an LTE network, or other suitable wireless network or a combination of two or more of these.
  • WPAN wireless PAN
  • WI-FI such as, for example, a BLUETOOTH WPAN
  • WI-MAX such as, for example, a Global System for Mobile Communications (GSM) network
  • GSM Global System for Mobile Communications
  • 3G network 3G network
  • 4G 4G network
  • 5G network such as Long Term Evolution
  • LTE Long Term Evolution
  • Computer system 300 may include any suitable communication interface 310 for any of these networks, where appropriate.
  • Communication interface 310 may include one or more communication interfaces 310, where appropriate.
  • bus 312 includes hardware, software, or both coupling components of computer system 300 to each other.
  • bus 312 may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCIe) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, or another suitable bus or a combination of two or more of these.
  • Bus 312 may include one or more buses 312, where appropriate.
  • a computer-readable non-transitory storage medium or media may include one or more semiconductor-based or other integrated circuits (ICs) (such, as for example, field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disk drives (HDDs), hybrid hard drives (HHDs), optical discs, optical disc drives (ODDs), magneto-optical discs, magneto-optical drives, floppy diskettes, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM-drives, SECURE DIGITAL cards or drives, any other suitable computer-readable non-transitory storage media, or any suitable combination of two or more of these, where appropriate.
  • ICs such, as for example, field-programmable gate arrays (FPGAs) or application-specific ICs (ASICs)
  • HDDs hard disk drives
  • HHDs hybrid hard drives
  • ODDs optical disc drives
  • magneto-optical discs magneto-optical drives
  • references in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative. Additionally, although this disclosure describes or illustrates particular embodiments as providing particular advantages, particular embodiments may provide none, some, or all of these advantages.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Dans un mode de réalisation, un procédé comprend l'intégration, par un routeur de bordure, d'un premier locataire provenant d'un système de gestion de réseau et la détermination, par le routeur de bordure, d'un mappage d'un identifiant de locataire associé au premier locataire à un identifiant de dispositif de commande associé à un dispositif de commande. Le procédé comprend également la réservation, par le routeur de bordure, d'un numéro de port dans un noyau pour le premier locataire et l'insertion, par le routeur de bordure, de l'identifiant de locataire dans un premier paquet de commande. Le procédé comprend en outre la communication, par le routeur de bordure, du premier paquet de commande au dispositif de commande par l'intermédiaire d'une connexion de commande chiffrée pendant une première session d'appairage. La première session d'appairage partage la connexion de commande chiffrée avec une seconde session d'appairage.
PCT/US2022/080876 2021-12-14 2022-12-05 Procédé de partage d'une connexion de commande WO2023114649A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CA3234999A CA3234999A1 (fr) 2021-12-14 2022-12-05 Procede de partage d'une connexion de commande

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163265385P 2021-12-14 2021-12-14
US63/265,385 2021-12-14
US17/709,877 2022-03-31
US17/709,877 US11778038B2 (en) 2021-12-14 2022-03-31 Systems and methods for sharing a control connection

Publications (1)

Publication Number Publication Date
WO2023114649A1 true WO2023114649A1 (fr) 2023-06-22

Family

ID=85157134

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/080876 WO2023114649A1 (fr) 2021-12-14 2022-12-05 Procédé de partage d'une connexion de commande

Country Status (1)

Country Link
WO (1) WO2023114649A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180109493A1 (en) * 2013-12-18 2018-04-19 vIPtela Inc. Overlay management protocol for secure routing based on an overlay network
US20210067442A1 (en) * 2019-09-04 2021-03-04 Cisco Technology, Inc. Policy plane integration across multiple domains

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180109493A1 (en) * 2013-12-18 2018-04-19 vIPtela Inc. Overlay management protocol for secure routing based on an overlay network
US20210067442A1 (en) * 2019-09-04 2021-03-04 Cisco Technology, Inc. Policy plane integration across multiple domains

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CISCO: "Cisco SD-WAN Design Guide", September 2020 (2020-09-01), XP093028951, Retrieved from the Internet <URL:https://web.archive.org/web/20210806133945if_/https://www.cisco.com/c/en/us/td/docs/solutions/CVD/SDWAN/cisco-sdwan-design-guide.pdf> [retrieved on 20230303] *

Similar Documents

Publication Publication Date Title
US11005818B2 (en) Dynamic, user-configurable virtual private network
US10454821B2 (en) Creating and maintaining segment routed traffic engineering policies via border gateway protocol
US11991246B2 (en) Cloud scale multi-tenancy for RDMA over converged ethernet (RoCE)
US9800497B2 (en) Operations, administration and management (OAM) in overlay data center environments
US11533259B2 (en) Building a platform to scale control and data plane for virtual network functions
EP4066454A1 (fr) Politiques à base de groupes pour trafic inter-domaines
US11778038B2 (en) Systems and methods for sharing a control connection
US11218918B2 (en) Fast roaming and uniform policy for wireless clients with distributed hashing
US20210377221A1 (en) Systems and Methods for Costing In Nodes after Policy Plane Convergence
WO2023114649A1 (fr) Procédé de partage d&#39;une connexion de commande
CN116724546A (zh) 用于融合以太网上的RDMA（RoCE）云规模多租赁
WO2022146466A1 (fr) Mise en file d&#39;attente basée sur la classe pour trafic rdma évolutif multi-tenant
US12021746B2 (en) Inter-working of a software-defined wide-area network (SD-WAN) domain and a segment routing (SR) domain
US20230188502A1 (en) Systems and Methods for Achieving Multi-tenancy on an Edge Router
US20240056379A1 (en) System and Method for EVPN Multicast Optimization for Source Handling
US20230336480A1 (en) Efficient Handling of Fragmented Packets in Multi-Node All-Active Clusters
US20230188987A1 (en) Systems and Methods for Detecting Domain Changes in an SD-WAN Environment
CN113545130B (zh) 利用分布式散列的无线客户端的快速漫游和统一策略
US20230327994A1 (en) Systems and Methods for Handling Asymmetric SDWAN Traffic Flows
WO2023114650A1 (fr) Systèmes et procédés d&#39;obtention d&#39;une architecture mutualisée sur un routeur d&#39;extrémité
WO2022146470A1 (fr) Multi-tenancy à l&#39;échelle du nuage pour rdma sur ethernet convergé (roce)
CN116686277A (zh) 用于可扩展多租户rdma流量的基于类的排队
WO2023204984A1 (fr) Gestion efficace de paquets fragmentés dans des grappes entièrement actives à nœuds multiples

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22851259

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 3234999

Country of ref document: CA