Large scale test network and method for implementing the same

Abstract

The application provides a large-scale test network implementation method, and relates to the technical field of computer networks, and the method comprises the following steps: using static routing or an IGP protocol at the edge, using VRF technology on a router, and implementing deployment of a wide-area test network, wherein the wide-area test network comprises a test router and a core router, and the VRF technology divides the wide-area test network into at least one core network slice; when a user applies for a test, the core network slice is managed by the test router, the access of a user equipment is completed, and the test is completed, wherein the access mode comprises static routing access and IGP access. The application implements the construction of a large-scale test network by using the above scheme.

Description

Technical Field

[0001] This application relates to the field of computer network technology, and in particular to large-scale experimental networks and their implementation methods. Background Technology

[0002] As the internet faces numerous challenges in security, performance, and scalability, research on the future internet is in full swing. The purpose of future internet experimental facilities is to support the experimental infrastructure for this research. The history of internet development is a process of continuous exploration and error tolerance. Numerous studies have already addressed the challenges of current internet scalability, security, and performance. However, due to the vast scope of the existing internet, some new ideas are difficult to deploy on it. Therefore, research on future internet experimental facilities has been launched. This requires experimental facilities to comprehensively consider research from different directions, integrate these technologies to form core equipment, and finally conduct large-scale tests of these technologies and equipment in conjunction with large-scale experimental networks.

[0003] Currently, various test network technologies exist; however, solutions for wide-area, large-scale test networks are limited. Most test networks focus on small-scale local area networks (LANs), and even wide-area test networks try to utilize existing backbone network resources to connect smaller test networks scattered across different locations. The reason for this lies in the need to address three key issues when building a wide-area backbone test network. First, there's the issue of isolation between tests. Since it's a test, unexpected failures are possible, and if a failure in one test leads to a problem for the entire backbone network, it will cause significant issues. Second, there's the need for realism and observability. Using a real network for testing ensures high consistency with the production environment, and the results can be readily applied to existing networks. This requires realistic network configurations, real resources used, and realistic observation results. Third, and most importantly, is the issue of economic efficiency. Wide-area networks have high operating costs, and they should accommodate as many parallel tests as possible to fully utilize the capabilities of a large-area network. If a large network can only conduct one test at a time, economic efficiency is difficult to guarantee.

[0004] Traditional test network facilities typically use virtual routers, where the lower-layer network topology is invisible to the upper-layer test. The advantage of this approach is that it can support a variety of tests. However, the disadvantages are also obvious: on the one hand, this mode leads to a decrease in routing performance, making it difficult to achieve a test environment that is close to the throughput of the live network; on the other hand, this mode also increases complexity, reduces observation capabilities, and is not conducive to analyzing test results. Summary of the Invention

[0005] This application aims to at least partially address one of the technical problems in the related art.

[0006] Therefore, the first objective of this application is to propose a method for implementing a large-scale experimental network, which enables the construction of a large-scale experimental network. Based on this network, distributed and wide-area network experiments can be conducted, and multiple experiments can be conducted concurrently and isolated from each other. Each node in the experiment comes from a real network, so the experimental results can be observed.

[0007] The second objective of this application is to propose a large-scale experimental network.

[0008] To achieve the above objectives, the first aspect of this application proposes a method for implementing a large-scale experimental network, comprising: deploying a wide-area experimental network by using static routing or IGP protocols at the edge and VRF technology on the router, wherein the wide-area experimental network includes experimental routers and core routers, and VRF technology divides the wide-area experimental network into at least one core network slice; when a user applies for a test, the core network slice is managed through the experimental router to complete the access of the user equipment and complete the test, wherein the access method includes static routing access and IGP access.

[0009] Optionally, in one embodiment of this application, the user-side router access is completed using a static routing access method, including:

[0010] Pre-configured core network slices are provided to test users via the VRF experimental router.

[0011] On the test router, static routes across VPNs were used to enable access from the local node to remote nodes and from the public VRF to the sliced ​​VRF.

[0012] Plan the public VRF and public IGP processes, configure sub-interfaces on the physical interfaces connecting the test router and the core router, and add the sub-interfaces to the public VRF on the test router side;

[0013] Plan the public VRF and public IGP processes on the core router, configure sub-interfaces on the physical interfaces connecting the core router and the test router, add the sub-interfaces to the public VRF on the core router side, and form an IGP neighbor with the test router.

[0014] Optionally, in one embodiment of this application, the user-side router access is completed using the IGP access method, including:

[0015] The test router VRF provides several pre-configured core network slices to test users, and plans a corresponding number of independent IGP processes to be applied to each core network slice.

[0016] On the core router, routes are mutually referenced between the independent IGP process and the public IGP process. By controlling the Tag, routes belonging to the corresponding core network slice in the public VRF are introduced into the virtual slice.

[0017] The core router is used to plan the public VRF, each independent IGP process with the same process ID as the access router, and the public IGP process. Each independent IGP process and the public IGP process are associated with the public VRF.

[0018] To achieve the above objectives, a second aspect of the present invention proposes a large-scale experimental network, which is implemented by the above-described method for implementing a large-scale experimental network.

[0019] The method for implementing a large-scale experimental network in this application embodiment uses VRF technology to divide the wide-area experimental network into several slices. Each slice operates independently with isolated resources. Even if one slice fails, it does not affect the network operation of other slices. Slices can communicate with each other through a common switching center. The interconnection topology of nodes within a slice is visible to the experimental users, who can observe the actual operating status of the network and view the IP addresses of backbone routers along the route using tools such as traceroute.

[0020] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0021] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein:

[0022] Figure 1 This is a flowchart illustrating a method for implementing a large-scale experimental network as provided in Embodiment 1 of this application.

[0023] Figure 2 This is a large-scale experimental network logical architecture diagram according to an embodiment of this application;

[0024] Figure 3 This is a node logic architecture diagram of an embodiment of this application;

[0025] Figure 4 This is a schematic diagram of static routing access according to an embodiment of this application;

[0026] Figure 5 This is a schematic diagram of IGP access according to an embodiment of this application. Detailed Implementation

[0027] The embodiments of this application are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application.

[0028] The following description, with reference to the accompanying drawings, describes a large-scale experimental network and its implementation method according to embodiments of this application.

[0029] Figure 1 This is a flowchart illustrating a method for implementing a large-scale experimental network as provided in Embodiment 1 of this application.

[0030] like Figure 1 As shown, the implementation method of this large-scale experimental network includes the following steps:

[0031] Step 101: Deploy a wide area test network by using static routing or IGP protocol at the edge and VRF technology on the router. The wide area test network includes test routers and core routers. VRF technology divides the wide area test network into at least one core network slice.

[0032] This embodiment proposes a large-scale white-box experimental network based on VRF (Virtual Route Forwarding). VRF is a VPN (Virtual Private Network) construction technology aimed at resolving conflicts between different enterprises with the same private network address range. To prevent conflicts, identical private network addresses are placed in different VRF tables. Since a device may connect to multiple users simultaneously, these users' (routes) need to be isolated from each other. This is where VRF comes in; each user on the device corresponds to a VRF. In addition to maintaining a global IP routing table, the device also maintains an independent IP routing table for each VRF; this routing table is called the VRF routing table. It is important to note that the global IP routing table and each VRF routing table are independent or isolated from each other. Each VRF table has two main attributes: Route Distinguisher (RD) and Route Target (RT). The RD (Route Distinguisher) is used to distinguish local VRFs; this attribute is only valid locally. An 8-byte RD (Route Registry) plus a 4-byte IPv4 address constitutes a 96-bit VPNv4 route, transforming a non-unique IPv4 address into a unique VPN-IPv4 address. This VPNv4 route is transmitted (distinguished) within the ISP domain. The RD tags routes within a VRF (Virtual Radio Service), thus achieving address reuse without conflicts. RT (Route Tag) is an extended community attribute of BGP, divided into Import RT and Export RT, used for route import and export policies, respectively. Configuring import and export RT controls route sending and receiving. When exporting a route from a VRF table, the VRF route is tagged using an export RT. When importing a route into a VRF table, only routes whose RT tags match any import RT in the VRF table will be imported.

[0033] In this embodiment, a wide-area test network is designed. By using Virtual Router (VRF) technology on user-side routers, test routers, and core routers, the wide-area test network is divided into several slices. Each slice operates independently, with isolated resources. Even if one slice fails, it does not affect the network operation of other slices. Slices can communicate through a common switching center. The interconnection topology of nodes within a slice is visible to test users, allowing them to observe the actual operating status of the network and view the IP addresses of backbone routers along the path using tools such as traceroute. Figure 2 As shown.

[0034] In this embodiment, the experimental network includes a core router, experimental routers, and user equipment. The main functions of the core router are core forwarding and boundary interconnection. The experimental router mainly handles the allocation and interconnection of pre-configured core network slice resources, access for self-developed equipment or the experimental network, slicing for experimental sites, and interconnection of corresponding slice resources with experimental sites. The access router mainly provides access, including providing access to existing network users and providing experimental networks without pre-configured slices. The access router provides raw network slices to experimental users. These raw slices are built based on VRF and do not run any internal routing processes; users design and configure their own routing policies. Figure 3 As shown. The test network utilizes static routing or internal routing protocols at the edge and VRF on the routers to deploy a wide-area, large-scale test network, enabling a user-visible backbone network, a pre-configurable network, and plug-and-play functionality for test users.

[0035] Step 102: When a user applies for a trial, the core network slice is managed through the trial router to complete the access of the user equipment and complete the trial. The access methods include static route access and IGP access.

[0036] In this embodiment, a large-scale experimental network implementation based on static routing is proposed. Each experiment corresponds to a wide-area experimental network slice, an address block, and several access nodes. The address block is allocated to each access node, and each access node connects to the experimental router via static routing, with the experimental router serving as the default gateway. The experimental router and the core router run a common IGP process, and the interconnection address between the experimental router and the core router is assigned a sub-interface. Static routes are advertised to the common IGP using RT and RD methods. Regardless of the number of experimental slices, there is only one common IGP process. Specifically, the steps are as follows:

[0037] Pre-configured core network slices are provided to test users through the experimental router VRF (based on different physical / sub-interface VLANs).

[0038] The test router enables access from the local node to remote nodes and from the public VRF to the sliced ​​VRF via static routes across VPNs.

[0039] Plan a public VRF (VPN-WhiteBox) and a public IGP process (process 2). Configure a sub-interface on the physical interface connecting the test router and the core router, and add the sub-interface to the public VRF on the test router side.

[0040] Plan a public VRF (VPN-WhiteBox) and a public IGP process (process 2) on the core router. Configure a sub-interface on the physical interface connecting the core router and the test router. Add the sub-interface to the public VRF on the core router side to form an IGP neighbor with the test router.

[0041] An IGP can be an ISIS protocol, an OSPF protocol, or any internal routing protocol supported by the router. The logic for using the ISIS protocol is as follows: Figure 4 As shown.

[0042] Below is a sample configuration, assuming that each VRF corresponds to a 2001:db8:: / 32 aggregated address space, each node VRF corresponds to a / 40 refined address space, and the routing protocol is ISIS.

[0043] User equipment (CE equipment) configuration

[0044] #Using the loopback port to simulate white-box slicing users

[0045] interface LoopBack100

[0046] ipv6 address 2001:db8:100::100 / 40

[0047] interface GigabitEthernet1 / 5 / 4.1001

[0048] MTU 9600

[0049] statistic enable

[0050] IPv6 MTU 9600

[0051] vlan-type dot1q1001

[0052] ipv6 address 2001:db8:100::2 / 64

[0053] #User test network summary routing points to PE device

[0054] ipv6 route-static 2001:db8::32 2001:db8:100::1

[0055] Configuring the test router (PE device)

[0056] #Configure a slice VPN and a backbone public VPN

[0057] IP VPN Instance Slice 1001

[0058] IPv6-family

[0059] route-distinguisher 38272:1001

[0060] apply-label per-instance

[0061] vpn-target 38272:1001export-extcommunity

[0062] vpn-target 38272:1001import-extcommunity

[0063] #Configure backbone public VPN

[0064] IP VPN Instance VPN WhiteBox

[0065] IPv6-family

[0066] # Configure the ISIS process for the backbone public VPN and import static routes into ISIS, restricting the import to only sliced ​​40-bit routes via routing policies.

[0067] isis 2vpn-instance vpn-WhiteBox

[0068] is-level level-2

[0069] cost-style wide

[0070] network-entity 02.1829.0020.0002.00

[0071] #

[0072] IPv6 enable topology IPv6

[0073] ipv6 import-route static route-policy W-Box

[0074] #

[0075] route-policy W-Box permit node 10

[0076] if-match ipv6 address prefix-list W-Slice

[0077] #

[0078] route-policy W-Box deny node 1000

[0079] #

[0080] ip ipv6-prefix W-Slice index 10permit 2001:db8::20less-equal 40

[0081] Configuring the test router (PE device)

[0082] # Sub-interface connected to CE

[0083] interface GigabitEthernet1 / 0 / 9.1001

[0084] vlan-type dot1q 1001

[0085] MTU 9600

[0086] ip binding vpn-instance slice1001

[0087] IPv6 enable

[0088] ipv6 address 2001:db8:100::1 / 64

[0089] IPv6 MTU 9600

[0090] statistic enable

[0091] # Sub-interface connected to P - Public VPN, the VPN address can be set according to convention.

[0092] interface FlexE2 / 0 / 1000.2

[0093] vlan-type dot1q 2

[0094] MTU 9600

[0095] ip binding vpn-instance vpn-WhiteBox

[0096] IPv6 enable

[0097] ipv6 address 2001:203:2:10::1 / 64

[0098] IPv6 MTU 9600

[0099] statistic enable

[0100] isis ipv6 enable 2

[0101] isis circuit-type p2p

[0102] # Configure static routes within the slice to remote nodes, specifying the destination VPN as the backbone public VPN.

[0103] ipv6 route-static vpn-instance slice1001 2001:db8::32vpn-instancevpn-WhiteBox tag 1

[0104] # Configure static routes across VPNs, specifying the destination VPN as a slice VPN

[0105] ipv6 route-static vpn-instance vpn-WhiteBox 2001:db8:100::40vpn-instance slice1001 tag 1

[0106] Configuration of the core router (P device)

[0107] #Configure backbone public VPN

[0108] IP VPN Instance VPN WhiteBox

[0109] IPv6-family

[0110] This embodiment provides a large-scale experimental network implementation for IGP access. Specifically, users connect to experimental routers using the IGP protocol. Each experimental router runs an IGP process for a specific slice and interconnects with the IGP processes in the user-side routers. The core router runs a common VRF and a common IGP process. The experimental routers tag each slice of routes learned from the user side, indicating the attributes of the slice corresponding to the route, and then advertise the tagged routes to the common IGP. Each independent experimental IGP process needs to run simultaneously on the core router. The specific configuration steps are as follows:

[0111] 1) Provide several pre-configured core network slices to test users through the test router VRF (based on different physical / sub-interface VLANs), and plan a corresponding number of independent IGP processes to be applied to each core network slice (CE in each VRF publishes its own routing prefix through IGP).

[0112] 2) On the core router, route referencing is performed between the independent IGP process and the public IGP process. Tag control is used to ensure that only routes belonging to the corresponding core network slice within the public VRF are introduced into the virtual slice.

[0113] 3) The core router plans a public VRF (VPN-WhiteBox, same as static / VRF slice), independent IGP processes with the same process ID as the access router, and a public IGP process (process 2, same as static / VRF slice). All independent IGP processes and the public IGP process are associated with the public VRF.

[0114] An IGP can be an ISIS protocol, an OSPF protocol, or any internal routing protocol supported by the router. The logic for using the ISIS protocol is as follows: Figure 5 As shown.

[0115] Below is a specific use case. The address block used is 2001:db8:: / 32, with 8 ISIS slices pre-configured, marked as 2041 to 2048, and RD marks as 38272:2401, etc.

[0116] User equipment (CE equipment) configuration

[0117] #Using the loopback port to simulate white-box slicing users

[0118] interface LoopBack100

[0119] ipv6 address 2001:db8:101::100 / 40

[0120] isis 2041

[0121] is-level level-2

[0122] cost-style wide

[0123] network-entity 11.2041.0100.0001.00

[0124] #

[0125] IPv6 enable topology IPv6

[0126] #

[0127] #

[0128] interface GigabitEthernet1 / 5 / 4.2041

[0129] MTU 9600

[0130] statistic enable

[0131] IPv6 MTU 9600

[0132] isis ipv6 enable 2041

[0133] vlan-type dot1q 2041

[0134] ipv6 address 2001:db8:101::2 / 64

[0135] Configuring the test router (PE device)

[0136] #Configure a slice VPN and a backbone public VPN

[0137] IP VPN Instance Slice 2401

[0138] ipv6-familyroute-distinguisher 38272:2401

[0139] apply-label per-instance

[0140] vpn-target 38272:2401export-extcommunity

[0141] vpn-target 38272:2401import-extcommunity

[0142] #Configure the ISIS process for the slice VPN

[0143] isis 2041vpn-instance slice2041

[0144] is-level level-2

[0145] cost-style widenetwork-entity 11.2041.0020.0002.00

[0146] #

[0147] IPv6 enable topology IPv6

[0148] #

[0149] Configuring the test router (PE device)

[0150] # Sub-interface connected to CE

[0151] interface GigabitEthernet1 / 0 / 9.2401

[0152] vlan-type dot1q 2401

[0153] MTU 9600

[0154] ip binding vpn-instance slice2401

[0155] ipv6 enableipv6 address 2001:db8:101::1 / 64

[0156] IPv6 MTU 9600

[0157] statistic enable isis ipv6 enable 2401

[0158] # Sub-interface connected to P - Sliced ​​VPN, the VPN address can be set according to convention.

[0159] interface FlexE2 / 0 / 1000.2401

[0160] vlan-type dot1q 2401

[0161] MTU 9600

[0162] ip binding vpn-instance slice2401

[0163] IPv6 enable

[0164] ipv6 address 2001:203:2:10::1 / 64

[0165] IPv6 MTU 9600

[0166] statistic enable

[0167] isis ipv6 enable 2401

[0168] isis circuit-type p2p

[0169] Configuration of the core router (P device)

[0170] #Configure backbone public VPN

[0171] IP VPN Instance VPN WhiteBox

[0172] IPv6-family

[0173] # Configure the ISIS process for the backbone public VPN, tagging the slice process when the public process routes routes: isis 2vpn-instance vpn-WhiteBox

[0174] is-level level-2

[0175] cost-style widenetwork-entity 02.1829.0020.0010.00

[0176] #

[0177] IPv6 enable topology IPv6

[0178] ipv6 import-route isis 2401tag 2401

[0179] ipv6 import-route isis 2402tag 2402

[0180] ipv6 import-route isis 2403tag 2403

[0181] ipv6 import-route isis 2404tag 2404

[0182] ipv6 import-route isis 2405tag 2405

[0183] ipv6 import-route isis 2406tag 2406

[0184] ipv6 import-route isis 2407tag 2407

[0185] ipv6 import-route isis 2408tag 2408

[0186] #

[0187] Configuration of the core router (P device)

[0188] # Configure the ISIS process for the slice VPN, and use tag-based filtering when the slice process routes public processes (using route-policy).

[0189] #

[0190] isis 2401vpn-instance vpn-WhiteBox

[0191] is-level level-2

[0192] cost-style wide

[0193] network-entity 11.2401.0020.0010.00

[0194] #

[0195] IPv6 enable topology IPv6

[0196] ipv6 import-route isis 2route-policy 2401

[0197] #

[0198] #

[0199] route-policy 2401permit node 10

[0200] if-match tag 2401

[0201] #

[0202] route-policy 2401deny node 1000

[0203] #

[0204] Configuration of the core router (P device)

[0205] #Sub-interface connected to PE - Sliced ​​VPN

[0206] interface GigabitEthernet1 / 0 / 0.2401

[0207] vlan-type dot1q 2401

[0208] MTU 9600

[0209] ip binding vpn-instance vpn-WhiteBox

[0210] IPv6 enable

[0211] ipv6 address 2001:203:2:10::2 / 64

[0212] IPv6 MTU 9600

[0213] statistic enable

[0214] isis ipv6 enable 2401

[0215] isis circuit-type p2p

[0216] #

[0217] Configuration of the core router (P device)

[0218] # Sub-interface connected to the remote P device

[0219] interface GigabitEthernet1 / 0 / 1.2

[0220] vlan-type dot1q 2

[0221] MTU 9600

[0222] ip binding vpn-instance vpn-WhiteBox

[0223] IPv6 enable

[0224] ipv6 address 2001:203:10:19::1 / 64

[0225] IPv6 MTU 9600

[0226] statistic enable

[0227] isis ipv6 enable 2

[0228] isis circuit-type p2p

[0229] #

[0230] In this embodiment, a large-scale experimental network is proposed. By pre-setting network slices, the experimental network can be built quickly. Specifically, several static route slices and several slices using IGP access are pre-set on the experimental router and the core router. When an experimental user applies for an experiment, a static route or an experimental network slice using IGP is automatically assigned according to the requirements.

[0231] In this embodiment, a large-scale experimental network implementation is proposed. When static routing or IGP slicing does not meet the requirements, an original slice is allocated to the experimental user by using an access router. This original slice is built based on VRF and does not run any internal routing process. The user designs and configures the corresponding routing policy himself.

[0232] To implement the above embodiments, this application also proposes a large-scale experimental network, which is implemented by the method for implementing the large-scale experimental network described in the above embodiments.

[0233] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0234] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0235] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing custom logic functions or processes, and the scope of the preferred embodiments of this application includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as should be understood by those skilled in the art to which embodiments of this application pertain.

[0236] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of computer-readable media include: an electrical connection having one or more wires (electronic device), a portable computer disk drive (magnetic device), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Alternatively, the computer-readable medium may be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in a computer memory.

[0237] It should be understood that various parts of this application can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0238] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0239] Furthermore, the functional units in the various embodiments of this application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0240] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of this application.

Claims

1. A method for implementing a large-scale experimental network, characterized in that, include: A wide-area test network is deployed by using static routing or IGP protocols at the edge and VRF technology on the router. The wide-area test network includes test routers and core routers, and the VRF technology divides the wide-area test network into at least one core network slice. When a user applies for a trial, the core network slice is managed through the trial router to complete the access of the user equipment and complete the trial. The access methods include static route access and IGP access. The method of using static routing to complete the access of the user-side router includes: Pre-configured core network slices are provided to test users via the VRF experimental router. On the test router, static routes across VPNs were used to enable access from the local node to remote nodes and from the public VRF to the sliced ​​VRF. Plan the public VRF and public IGP processes, configure sub-interfaces on the physical interfaces connecting the test router and the core router, and add the sub-interfaces to the public VRF on the test router side; Plan the public VRF and public IGP processes on the core router, configure sub-interfaces on the physical interfaces connecting the core router and the test router, add the sub-interfaces to the public VRF on the core router side, and form an IGP neighbor with the test router.

2. The method as described in claim 1, characterized in that, The user-side router is connected via IGP, including: The test router VRF provides several pre-configured core network slices to test users, and plans a corresponding number of independent IGP processes to be applied to each core network slice. On the core router, routes are mutually referenced between the independent IGP process and the public IGP process. By controlling the Tag, routes belonging to the corresponding core network slice in the public VRF are introduced into the virtual slice. The core router is used to plan the public VRF, each independent IGP process with the same process ID as the access router, and the public IGP process. Each independent IGP process and the public IGP process are associated with the public VRF.

3. A large-scale experimental network, characterized in that, The test network is implemented by the method described in claims 1-2.

Images