CN116389484A - Data distribution service-based cross-Kubernetes cluster network intercommunication system and method - Google Patents
Data distribution service-based cross-Kubernetes cluster network intercommunication system and method Download PDFInfo
- Publication number
- CN116389484A CN116389484A CN202310463611.9A CN202310463611A CN116389484A CN 116389484 A CN116389484 A CN 116389484A CN 202310463611 A CN202310463611 A CN 202310463611A CN 116389484 A CN116389484 A CN 116389484A
- Authority
- CN
- China
- Prior art keywords
- cluster
- kubernetes
- routing
- routing information
- clusters
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 19
- 238000004891 communication Methods 0.000 claims abstract description 10
- 230000008569 process Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 claims description 4
- 230000001360 synchronised effect Effects 0.000 claims description 4
- 238000007726 management method Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 3
- RJKFOVLPORLFTN-LEKSSAKUSA-N Progesterone Chemical compound C1CC2=CC(=O)CC[C@]2(C)[C@@H]2[C@@H]1[C@@H]1CC[C@H](C(=O)C)[C@@]1(C)CC2 RJKFOVLPORLFTN-LEKSSAKUSA-N 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a system and a method for intercommunication among cross-Kubernetes cluster networks based on data distribution service, wherein an independent distributed routing gateway is deployed in the Kubernetes cluster and is responsible for communication with a Kubernetes network management module of each node in the cluster, and collecting routing information needing to be forwarded across the cluster; the distributed routing gateway publishes the collected routing information outwards through the DDS, subscribes the routing information which needs to be communicated across the clusters, synchronizes the received routing information to a network management module in the clusters, and performs routing synchronization on each node of the local clusters. The invention introduces the distributed routing gateway, realizes intercommunication by synchronizing routing information among clusters, can avoid the bottleneck of the traditional gateway and can save bandwidth resources; the method has flexibility, and one-to-one, one-to-many and many-to-many interconnection strategies can be configured among different clusters.
Description
Technical Field
The invention relates to a Kubernetes and data distribution service DDS technology, in particular to a system and a method for intercommunication among Kubernetes cluster networks based on data distribution service.
Background
The data distribution service (Data Distribution Service, DDS) is a new generation of distributed real-time communication middleware technical specification formulated by an object management organization OMG on the basis of HLA, CORBA and other standards, the DDS adopts a release/subscription system architecture, emphasizes the centering of data, provides rich QoS service quality strategies, can ensure real-time, efficient and flexible distribution of the data, and can meet various distributed real-time communication application requirements. The DDS information distribution middleware is a lightweight middleware technology capable of providing real-time information transmission.
The DDS data are identified through the Topic, the data are published by the data publisher according to the Topic, and the data subscriber can select the data subscribed to the specific Topic according to the actual service requirement. This Data-Centric publication-subscription model DCPS (Data-Centric publication-subscriber) is the core of the DDS.
Kubernetes is a portable, extensible, open-source platform that uses declarative configuration and automatically performs management of containerized applications based on configuration information. In all container orchestration tools (similarly, docker swarm/meso, etc.), kubernetes' ecosystem is larger, grows faster, and has more support, services, and tools available for user selection.
The network communication of Kubernetes mainly has the following several different scenarios:
1. Container-to-Container network
Kubernetes creates one network namespace for each Pod. Each Pod contains multiple containers (ctr) that are all in the same shared network namespace. All containers in a Pod use the same IP address and the same port space provided by the network namespace, and can communicate directly with another container in the same Pod through localhost.
2. Pod-to-Pod network
In Kubernetes, each Pod has a real IP address, and each Pod can use this IP address to communicate with other pods. With network namespace isolating each Pod to the respective network stack, the virtual ethernet device (virtual Ethernet device) connects each of the namespaces to the root, and the bridges connect the namespaces together again, at which point the Pod can send network messages to another Pod on the same node.
For Pod communication across hosts, this needs to be done by means of the host network. Each host node in the cluster is assigned a CIDR segment specifying the IP address segments available to the Pod on that node. Once the traffic sent to the CIDR segment reaches the node, the node is responsible for forwarding the traffic on to the corresponding Pod. In general, each node knows how to distribute data packets to the Pod running on that node. Once a packet arrives at the destination node, the packet is delivered in the same manner as packets between different Pod on the same node.
3. Pod-to-Service network
One Kubernetes Service manages the status of a set of Pod and can track the dynamic change of the IP address of a set of Pod. A Service has an IP address and serves as a "virtual IP address" for the IP addresses of a set of Pod. Any packets sent to the Service's IP address will be load balanced onto the Pod corresponding to that Service.
4. Internet-to-Service network
For the flow out of the external network, the following two modes are mainly adopted: (1) configuring an external network gateway for a VPC routing table; (2) Network address translation (NAT Network Address Translation) is provided to map the node's intranet address to an extranet address so that the extranet can access the nodes on the intranet.
For incoming flow, there are currently mainly two solutions: service LoadBalancer and Ingress Controller.
There is currently no efficient solution within the industry for communication across multiple Kubernetes clusters.
Disclosure of Invention
In order to solve the defects existing in the prior art, the invention aims to provide a system and a method for inter-Kubernetes cluster network intercommunication based on data distribution service.
In order to achieve the purpose of the invention, the technical scheme adopted by the invention is as follows:
a cross-Kubernetes cluster network intercommunication system based on data distribution service, wherein an independent distributed routing gateway is deployed in a Kubernetes cluster, and the distributed routing gateway is responsible for communicating with a Kubernetes network management module of each node in the cluster and collecting routing information needing to be forwarded across the cluster;
and the distributed routing gateway publishes the collected routing information outwards through the DDS, subscribes the routing information which needs to be communicated across clusters, synchronizes the received routing information to a network management module in the Kubernetes cluster, and performs routing synchronization on each node of the local cluster.
Further, the distributed routing gateway comprises a routing information collection module and a DDS module;
the routing information collection module is used for collecting routing information which needs to be forwarded across the local cluster by each node of the local cluster; and the DDS module publishes/subscribes to the route information of the cross-cluster communication.
Further, the distributed routing gateway is deployed in the cluster in the form of an independent node.
Further, the Kubernetes network management module is a Kubernetes network plug-in, such as a CNI plug-in or CoreDNS plug-in.
Further, the routing information includes a DNS record for each Service that refines the detailed routing to each Pod.
Further, for data traffic needing to be forwarded across clusters, the data traffic is drained to the distributed routing gateway by configuration according to a Kubernetes cluster network forwarding policy, and is responsible for sending the data traffic to the distributed routing gateway node of the corresponding remote cluster.
Further, in the configuration process of the routing gateway publishing and subscribing, interconnection and interworking between different clusters can be one-to-one or many-to-many.
A cross-Kubernetes cluster network intercommunication method based on data distribution service comprises the following steps:
(1) Deploying independent distributed routing gateways in a Kubernetes cluster;
(2) The distributed routing gateway is communicated with a network management module of the Kubernetes cluster, and the routing information of the local cluster is collected;
(3) The distributed routing gateway transmits the locally collected cluster routing information to the DDS module for external release;
(4) The distributed routing gateway module can subscribe the routing messages of other clusters according to configuration; after receiving the routing information from other clusters, the DDS module transmits the routing information to the distributed routing gateway for processing, and synchronizes the routing information to the network management module in the Kubernetes cluster, and the Kubernetes network management module synchronizes the routing information in the local cluster.
Further, the traffic in the Kubernetes cluster to be forwarded across the clusters is forwarded to the distributed routing gateway of the local cluster according to the queried routing information, and the distributed routing gateway forwards the traffic to the distributed routing gateway of the remote cluster according to the routing information synchronized across the clusters.
Compared with the prior art, the invention has the advantages that after the distributed routing gateway is introduced, the intercommunication can be realized by synchronizing the routing information among the Kubernetes clusters without the routing of all traffic passing through the gateway, so that the bottleneck of the traditional gateway can be avoided; bandwidth resources can be saved, when intercommunication is not needed, the routing information of other clusters is cancelled at any time, and the forwarding of the cross-cluster traffic is reduced, so that network congestion can be effectively avoided; the method has flexibility, and one-to-one, one-to-many and many-to-many interconnection strategies can be configured among different Kubernetes clusters.
Drawings
FIG. 1 is a schematic diagram of a distributed routing gateway synchronous routing information process;
FIG. 2 is a schematic diagram of a forwarding process across a distributed routing gateway for cluster-crossing traffic;
fig. 3 is a schematic diagram of many-to-many cluster interworking.
Detailed Description
The technical scheme of the invention is further described below with reference to the accompanying drawings and examples. The following examples are only for more clearly illustrating the technical solutions of the present invention and are not intended to limit the scope of protection of the present application.
As shown in fig. 1, in the inter-Kubernetes cluster network interworking system based on the data distribution service, a distributed routing gateway based on the data distribution service is added in the Kubernetes clusters, and the inter-cluster network interworking of the Kubernetes is realized by fully playing the flexible data distribution characteristic of the DDS, collecting and publishing/subscribing the routing information of the inter-cluster communication among the clusters.
In Kubernetes clusters, a separate distributed routing gateway is deployed. The routing gateway collects the routing information which needs to be forwarded across the local cluster by each node of the local cluster on one hand, and is responsible for publishing the collected routing information outwards through the DDS on the other hand. The distributed routing gateways in other clusters can subscribe routing messages which need to be communicated across the clusters according to the requirements of cluster interconnection and interworking planning, and then route synchronization is carried out on the received routing messages at each node of the local clusters. Traffic communicated across the cluster may be forwarded based on the routing information queried in the cluster.
In the Kubernetes cluster, an independent distributed routing gateway is deployed, and the distributed routing gateway comprises a routing information collection module and a DDS module. The routing information collection module is used for collecting routing information which needs to be forwarded across the local cluster by each node of the local cluster; and the DDS module is used for publishing/subscribing the route information of the cross-cluster communication, namely, the collected route information is published outwards through the DDS, and the route information which needs to be communicated with each other across clusters can also be subscribed.
The distributed routing gateway is deployed in the cluster in the form of independent nodes Pod, and can be scheduled to any Node according to a scheduling strategy of Kubernetes.
The distributed routing gateway works mainly in the following aspects:
the distributed routing gateway is responsible for communicating with the Kubernetes network management module of each node, and collecting the routing information of the cluster, wherein the routing information can be detailed routing refined to each Pod or DNS records of each Service. After the collection of the routing information is completed, the routing information is issued to the outside by the DDS module. The Kubernetes network management module is typically a Kubernetes network plug-in, such as a CNI plug-in or CoreDNS plug-in.
The distributed routing gateway is simultaneously responsible for processing the routing information sent by other subscribed clusters, forwarding the routing information to the Kubernetes network management module, and synchronizing the local clusters by the Kubernetes network management module.
The distributed routing gateway is used as a network forwarding/entry of the Kubernetes cluster, and for data traffic needing to be forwarded across the cluster, the data traffic is led to the distributed routing gateway by the configuration according to the Kubernetes cluster network forwarding strategy, and is responsible for sending the data traffic to a distributed routing gateway node of a corresponding remote cluster. After receiving the cross-cluster traffic, the distributed routing gateway of the opposite end forwards the traffic locally, and the Kubernetes network management module in the cluster is responsible for forwarding the traffic to the corresponding Pod or container.
In a common Kubernetes environment, traffic that needs to communicate with outside the cluster needs to be forwarded through a route of a traditional gateway to achieve interworking. When the cross-cluster traffic is large, the routing and forwarding performance of the gateway can be severely tested, and even the service of the user can be influenced due to the performance of the gateway.
After the introduction of the distributed routing gateway, interworking can be achieved by synchronizing routing information between Kubernetes clusters without the need for routing all traffic through the gateway. And the switching of opening and closing the flow forwarding among clusters can be realized according to the service requirement by finely controlling the intercommunication rule among clusters. Thereby avoiding performance limitations of the gateway.
According to the service requirement of the user, the flow intercommunication interconnection of the cross-Kubernetes clusters is finely controlled through the publishing and subscribing of the routing information among the Kubernetes clusters, when intercommunication is not needed, the routing information of other clusters is cancelled and subscribed at any time, the forwarding of the cross-cluster flow is reduced, and further network congestion can be effectively avoided.
As shown in fig. 2, the inter-Kubernetes cluster network interworking method based on the data distribution service of the present invention mainly comprises the following working procedures:
(1) Deploying independent distributed routing gateways in a Kubernetes cluster;
(2) The distributed routing gateway communicates with a network management module of the Kubernetes cluster (such as a Kubernetes network plug-in) and collects routing information of the local cluster;
(3) The distributed routing gateway transmits the locally collected cluster routing information to the DDS module for external release;
(4) The distributed routing gateway module can subscribe the routing messages of other clusters according to configuration; after receiving the routing information from other clusters, the DDS module transmits the routing information to the distributed routing gateway for processing, and synchronizes the routing information to the network management module in the Kubernetes cluster, and the Kubernetes network management module synchronizes the routing information in the local cluster.
And configuring policy routing through a Kubernetes network management module, and guiding the traffic needing to be forwarded across clusters to a distributed routing gateway. And forwarding the traffic to the distributed routing gateway of the remote cluster according to the routing information synchronized to the cross-cluster by the routing gateway, wherein the remote gateway is responsible for forwarding the traffic to a corresponding Pod or container in the cluster where the remote gateway is located.
Through the steps, interconnection and intercommunication of a plurality of Kubernetes clusters are realized.
As shown in fig. 3, in the configuration process of publishing and subscribing the routing gateway, interconnection and interworking between different clusters can be one-to-one or many-to-many. The method can flexibly configure two specific clusters for route intercommunication according to the actual needs of users, can also mutually communicate a plurality of clusters, and can change the publishing and subscribing strategy at any time so as to realize the accurate control of the cross-cluster flow.
The user can plan the interconnection and intercommunication demands among different Kubernetes clusters according to the service demands, and the interconnection and intercommunication among the clusters is realized through the distributed routing gateway. The publishing and subscribing strategy of the route can be changed at any time according to actual needs. Different Kubernetes clusters can be configured with one-to-one, one-to-many and many-to-many interconnection and intercommunication strategies.
Compared with the prior art, the invention has the advantages that after the distributed routing gateway is introduced, the intercommunication can be realized by synchronizing the routing information among the Kubernetes clusters without the routing of all traffic passing through the gateway, so that the bottleneck of the traditional gateway can be avoided; bandwidth resources can be saved, when intercommunication is not needed, the routing information of other clusters is cancelled at any time, and the forwarding of the cross-cluster traffic is reduced, so that network congestion can be effectively avoided; the method has flexibility, and one-to-one, one-to-many and many-to-many interconnection strategies can be configured among different Kubernetes clusters.
While the applicant has described and illustrated the embodiments of the present invention in detail with reference to the drawings, it should be understood by those skilled in the art that the above embodiments are only preferred embodiments of the present invention, and the detailed description is only for the purpose of helping the reader to better understand the spirit of the present invention, and not to limit the scope of the present invention, but any improvements or modifications based on the spirit of the present invention should fall within the scope of the present invention.
Claims (9)
1. A cross-Kubernetes cluster network intercommunication system based on data distribution service is characterized in that an independent distributed routing gateway is deployed in a Kubernetes cluster, and the distributed routing gateway is responsible for communicating with a Kubernetes network management module of each node in the cluster and collecting routing information needing to be forwarded across the cluster;
and the distributed routing gateway publishes the collected routing information outwards through the DDS, subscribes the routing information which needs to be communicated across clusters, synchronizes the received routing information to a network management module in the Kubernetes cluster, and performs routing synchronization on each node of the local cluster.
2. The data distribution service-based cross-Kubernetes cluster network interworking system of claim 1, wherein the distributed routing gateway comprises a routing information collection module and a DDS module;
the routing information collection module is used for collecting routing information which needs to be forwarded across the local cluster by each node of the local cluster; and the DDS module publishes/subscribes to the route information of the cross-cluster communication.
3. The data distribution service-based inter-Kubernetes cluster network interworking system of claim 1, wherein the distributed routing gateway is deployed in the cluster in the form of an independent node.
4. The data distribution service-based cross-Kubernetes cluster network interworking system of claim 1, wherein the Kubernetes network management module is a Kubernetes network plug-in, such as a CNI plug-in or CoreDNS plug-in.
5. The data distribution Service-based cross-Kubernetes cluster network interworking system of claim 1, wherein the routing information includes a detailed routing refined to each Pod, DNS record for each Service.
6. The data distribution service-based inter-Kubernetes cluster network interworking system of claim 1, wherein for data traffic that needs to be forwarded across clusters, the data traffic is directed to the distributed routing gateway by being configured according to the Kubernetes cluster network forwarding policy, which is responsible for sending the data traffic to the distributed routing gateway node of the corresponding remote cluster.
7. The inter-Kubernetes cluster network interworking system based on the data distribution service according to claim 1, wherein in the configuration process of the routing gateway publishing and subscribing, the interconnection and interworking between different clusters can be one-to-one or many-to-many.
8. A method for inter-Kubernetes cluster network interworking based on data distribution service, based on the inter-Kubernetes cluster network interworking system based on data distribution service of any one of claims 1 to 7, comprising the steps of:
(1) Deploying independent distributed routing gateways in a Kubernetes cluster;
(2) The distributed routing gateway is communicated with a network management module of the Kubernetes cluster, and the routing information of the local cluster is collected;
(3) The distributed routing gateway transmits the locally collected cluster routing information to the DDS module for external release;
(4) The distributed routing gateway module can subscribe the routing messages of other clusters according to configuration; after receiving the routing information from other clusters, the DDS module transmits the routing information to the distributed routing gateway for processing, and synchronizes the routing information to the network management module in the Kubernetes cluster, and the Kubernetes network management module synchronizes the routing information in the local cluster.
9. The method for interworking across Kubernetes clusters based on the data distribution service according to claim 8, wherein the traffic to be forwarded across clusters in the Kubernetes clusters is forwarded to the distributed routing gateway of the local cluster according to the queried routing information, and the routing gateway forwards the traffic to the distributed routing gateway of the remote cluster according to the routing information synchronized across clusters.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310463611.9A CN116389484A (en) | 2023-04-26 | 2023-04-26 | Data distribution service-based cross-Kubernetes cluster network intercommunication system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310463611.9A CN116389484A (en) | 2023-04-26 | 2023-04-26 | Data distribution service-based cross-Kubernetes cluster network intercommunication system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116389484A true CN116389484A (en) | 2023-07-04 |
Family
ID=86967538
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310463611.9A Pending CN116389484A (en) | 2023-04-26 | 2023-04-26 | Data distribution service-based cross-Kubernetes cluster network intercommunication system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116389484A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117081959A (en) * | 2023-10-17 | 2023-11-17 | 明阳产业技术研究院(沈阳)有限公司 | Network connectivity monitoring and recovering method, system, medium and equipment |
| CN117978806A (en) * | 2023-10-31 | 2024-05-03 | 北京比格大数据有限公司 | Method for realizing cross-cluster resource scheduling |
-
2023
- 2023-04-26 CN CN202310463611.9A patent/CN116389484A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117081959A (en) * | 2023-10-17 | 2023-11-17 | 明阳产业技术研究院(沈阳)有限公司 | Network connectivity monitoring and recovering method, system, medium and equipment |
| CN117081959B (en) * | 2023-10-17 | 2023-12-22 | 明阳产业技术研究院(沈阳)有限公司 | Network connectivity monitoring and recovering method, system, medium and equipment |
| CN117978806A (en) * | 2023-10-31 | 2024-05-03 | 北京比格大数据有限公司 | Method for realizing cross-cluster resource scheduling |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116389484A (en) | Data distribution service-based cross-Kubernetes cluster network intercommunication system and method | |
| Kiszka et al. | RTnet-a flexible hard real-time networking framework | |
| CN108881799B (en) | A kind of system and method carrying out view networked video meeting | |
| CN102244614B (en) | Message forwarding method, system and routing switch | |
| WO2013102253A1 (en) | System and method for providing p2p based reconfigurable computing and structured data distribution | |
| CN101702689B (en) | Transmission control method with balanced multicast service data load and access device thereof | |
| WO2015123879A1 (en) | Method for realizing network virtualization and related device and communication system | |
| RU2513918C1 (en) | Cluster router and cluster routing method | |
| JP5295273B2 (en) | Data stream filtering apparatus and method | |
| CN104618207A (en) | Heterogeneous FC-AE-1553 network system and exchange method | |
| CN110445526A (en) | Data transmission method, device, system, electronic equipment and storage medium | |
| KR101501913B1 (en) | Multicast quality of service module and method | |
| CN109768963A (en) | A kind of meeting unlatching method and system based on view networking | |
| CN102104528B (en) | Network system applied in rural area and service message transmission method | |
| CN101499951A (en) | Tunnel configuration method, virtual access node, virtual edge node and system | |
| CN100499549C (en) | Apparatus and base station equipment for transmitting IP message in WiMAX network | |
| CN101924698B (en) | Method, system and equipment for balancing two-layer domain load based on IP unicast route | |
| CN109617961A (en) | A kind of method and apparatus of the downloading view networked video video recording in internet | |
| CN109491783A (en) | A kind of acquisition methods and system of memory usage | |
| CN112910959B (en) | SDN-based network interconnection method for multiple Kubernetes clusters | |
| CN106506716B (en) | A kind of connection method of SDN controller in-band management and device | |
| CN112887127B (en) | vBRAS equipment and method for realizing transfer control separation | |
| CN109474661A (en) | A kind of processing method and system of network request event | |
| Kim et al. | SDN-based orchestration for interworking cloud and transport networks | |
| Nagaraj et al. | On the importance of traffic control subsystem in icn-based industrial networks |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Country or region after: China Address after: 12th Floor, Building 5, Jieyuan Financial City, No. 55 Andemen Street, Yuhuatai District, Nanjing City, Jiangsu Province, China 210012 Applicant after: AUTOCORE INTELLIGENT TECHNOLOGY (NANJING) Co.,Ltd. Address before: 210012 room 401-404, building 5, chuqiaocheng, No. 57, Andemen street, Yuhuatai District, Nanjing, Jiangsu Province Applicant before: AUTOCORE INTELLIGENT TECHNOLOGY (NANJING) Co.,Ltd. Country or region before: China |