Virtual local area network conflict handling method, storage medium, electronic device and computer program product

Abstract

Provided in the embodiments of the present disclosure is a virtual local area network conflict handling method, the method comprising: determining a plurality of connected devices having virtual local area network conflicts and virtual local area network information of each connected device; creating a flexible-Ethernet client for each connected device on a first physical port connected to a resource pool of broadband remote access servers, and creating a virtual Ethernet interface on each flexible-Ethernet client; and, on the basis of the virtual local area network information of each connected device, creating a same virtual local area network on the corresponding virtual Ethernet interface.

Description

Virtual LAN conflict resolution methods, storage media, electronic devices and computer program products

[0001] Cross-reference to related applications

[0002] This disclosure is based on Chinese Patent Publication No. 2024114288075, filed on October 12, 2024, entitled "Virtual Local Area Network Conflict Handling Method, Storage Medium, Electronic Device and Computer Program Product", and claims priority to that patent disclosure. The entire contents disclosed therein are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communications, and more specifically, to a virtual local area network (VLAN) conflict resolution method, storage medium, electronic device, and computer program product. Background Technology

[0004] Currently, the focus of operators' upgrades to the bearer network is on resource pooling transformation of data centers (DCs). In traditional bearer networks, optical line terminals (OLTs) interconnect with broadband remote access servers (BRASs) through aggregation switches or direct physical ports. It is only necessary to ensure that the virtual local area networks (VLANs) of the OLTs connected to that BRAS physical port do not conflict within a specific area (for OLTs directly connected to the physical port, this is within that port; for those connected via aggregation switches, it is within that aggregation switch).

[0005] However, during the BRAS resource pooling transformation, multiple BRAS need to be centralized under a single data center leaf node (DC-leaf). This causes the service traffic on the originally dispersed low-speed ports (such as 5GE / 10GE) to converge to the high-speed ports (such as 50GE / 100GE) of the DC-leaf, thereby causing VLAN conflicts on the high-speed ports that connect the DC-leaf and the BRAS resource pool.

[0006] There are currently three main methods for resolving VLAN conflicts, but each method has its limitations:

[0007] 1. Reconfiguring the VLANs of the existing OLT according to the plan is a labor-intensive method that affects existing network services and is difficult to implement in the existing network, making it hard to promote.

[0008] 2. Perform VLAN translation / remapping on the DC-leaf device to translate / remap conflicting VLANs to non-conflicting VLANs. The drawback of this method is that related functions need to be developed on the DC-leaf, which is not supported by all devices. In addition, these conflicting VLAN mapping relationships need to be saved during the forwarding process, which consumes some additional forwarding table entry resources.

[0009] 3. Increase the physical ports between DC-leaf and resource pool. This method requires expanding the physical ports and fiber optic resources at the DC-leaf and resource pool exits, which will increase hardware costs and is usually unacceptable to operators.

[0010] In summary, there is still no good solution to the problem of VLAN conflicts on high-speed ports caused by data center resource pooling transformation in related technologies. Summary of the Invention

[0011] This disclosure provides a virtual local area network (VLAN) conflict resolution method, storage medium, electronic device, and computer program product.

[0012] According to one embodiment of this disclosure, a method for handling virtual local area network (VLAN) conflicts is provided. The method includes: determining multiple connected devices with VLAN conflicts and VLAN information for each connected device; creating multiple flexible Ethernet clients for the multiple connected devices on a first physical port that interfaces with a broadband access server resource pool, and creating a virtual Ethernet interface on each flexible Ethernet client, wherein each connected device corresponds to one flexible Ethernet client and one virtual Ethernet interface; and creating the same VLAN on the corresponding virtual Ethernet interface according to the VLAN information of each connected device.

[0013] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, which stores a computer program configured to perform the steps in any of the above method embodiments when executed.

[0014] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, the memory storing a computer program, the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0015] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments. Attached Figure Description

[0016] Figure 1 is a hardware structure block diagram of the electronic device operating according to the method embodiment of this disclosure;

[0017] Figure 2 is a flowchart illustrating a virtual local area network (VLAN) conflict resolution method according to an embodiment of the present disclosure.

[0018] Figure 3 is a schematic diagram of the structure of the bearer network before the data center resource pooling transformation in one embodiment of this disclosure;

[0019] Figure 4 is a schematic diagram of VLAN conflicts occurring during the data center resource pooling transformation process in one embodiment of this disclosure;

[0020] Figure 5 is a schematic diagram of the network architecture of the bearer network after the data center resource pooling transformation in one embodiment of this disclosure. Detailed Implementation

[0021] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0022] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0023] This disclosed embodiment can be applied to the scenario of data center (DC) resource pooling transformation. Multiple Broadband Remote Access Servers (BRAS) need to be centralized into a data center leaf node (DC-leaf). The service traffic on the originally scattered low-speed ports (such as 5GE / 10GE) needs to be aggregated to the high-speed ports (such as 50GE / 100GE) of the DC-leaf, and then connected to the BRAS resource pool through the high-speed ports of the DC-leaf. VLANs on each BRAS may conflict.

[0024] The method embodiments provided in this disclosure can be run in network nodes of a communication network. Network nodes may include, but are not limited to, electronic devices such as switches, routers, and broadband access servers.

[0025] Figure 1 is a hardware structure block diagram of the electronic device operating according to an embodiment of the method of this disclosure. As shown in Figure 1, the electronic device 100 may include one or more (only one is shown in Figure 1) processors 102 (processors 102 may include, but are not limited to, processing devices such as microprocessors (MCUs) or field-programmable gate arrays (FPGAs)) and a memory 104 for storing data. Those skilled in the art will understand that the structure shown in Figure 1 is merely illustrative and does not limit the structure of the electronic device described above. For example, the electronic device may also include more or fewer components than shown in Figure 1, or have a different configuration than that shown in Figure 1.

[0026] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the virtual local area network conflict handling method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0027] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor. The transmission device is used to receive or transmit data via a network. Specific examples of the network may include a wireless network or a wired network. In one example, the transmission device includes a Network Interface Controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet.

[0028] The embodiments disclosed herein can be deployed on data center leaf (DC-leaf) nodes, such as DC-leaf routers or switches, or on the egress devices of resource pools, such as BRAS, switches, and other devices.

[0029] The FlexE technology used in this disclosure is a multi-rate sub-interface transport technology based on Ethernet over multi-physical layer links, supporting aggregation, channelization, and sub-rates. Each 100GE physical port can be divided into 20 5GE sub-channels, and the FlexE Client can allocate bandwidth in integer multiples of 5GE. This technology has long been a standard and is used in high-speed ports of bearer network equipment (currently, 100GE / 50GE ports are commonly used).

[0030] This embodiment provides a virtual local area network (VLAN) conflict resolution method running on the above-mentioned electronic device. Taking a DC-leaf node as an example, Figure 2 is a flowchart of the VLAN conflict resolution method according to an embodiment of this disclosure. As shown in Figure 2, the process may include steps S202, S204 and S206.

[0031] Step S202: Determine the multiple connected devices that have virtual LAN conflicts and the virtual LAN information of each connected device.

[0032] In some embodiments, the connection device in step S202 includes at least one of the following: a direct-connect physical port, wherein each direct-connect physical port is connected to an optical line terminal (OLT); and an aggregation switch, wherein each aggregation switch is connected to multiple optical line terminals. This disclosure does not limit the number of each type of connection device.

[0033] In one exemplary embodiment, the direct-connect physical port and / or the hierarchical junction switch (HJSW) is connected to the DC-leaf node via a metro-leaf (M-leaf) node.

[0034] In some embodiments, the virtual local area network (VLAN) information in step S202 includes at least one of the following: a VLAN identifier for one optical line terminal connected to the directly connected physical port; VLAN identifiers for multiple optical line terminals connected to the aggregation switch; wherein each optical line terminal is configured with one or more virtual local area networks (VLANs). In this embodiment, the VLAN identifier is a unique identifier for each VLAN configured within a single connected device; for example, the VLAN identifier can be represented as a VLAN ID.

[0035] Step S204: Create multiple flexible Ethernet clients for the multiple connected devices on the first physical port that interfaces with the broadband access server resource pool, and create a virtual Ethernet interface on each of the flexible Ethernet clients.

[0036] In this embodiment, each of the connection devices corresponds to a Flex Ethernet Client (FlexE Client) and a Virtual Ethernet Interface (VEI). The first physical port can be a high-speed port on the DC-leaf node, through which the DC-leaf node connects to the Broadband Remote Access Server (BRAS) resource pool.

[0037] In some embodiments, prior to step S204, the method may further include the following steps: determining the port bandwidth of the first physical port; and obtaining service traffic information of multiple optical line terminals connected to the multiple connection devices.

[0038] In some embodiments, step S204, which involves creating multiple flexible Ethernet clients for the multiple connected devices on the first physical port that interfaces with the broadband access server resource pool, may include the following steps: allocating the port bandwidth to the multiple connected devices based on the service traffic information of the multiple optical line terminals, thereby obtaining the allocated bandwidth for each connected device; and creating a flexible Ethernet client with the same bandwidth for each connected device on the first physical port based on the allocated bandwidth.

[0039] In this embodiment, by monitoring service traffic information, port bandwidth can be allocated according to actual service needs, ensuring efficient use of network resources and guaranteeing the service data transmission efficiency of each OLT.

[0040] In an exemplary embodiment, port bandwidth can be allocated to each optical line terminal proportionally according to the actual service traffic requirements of each optical line terminal, thereby determining the allocated bandwidth for each connected device. For example, a first physical port connects two connected devices: connected device 1 is a direct-connect physical port connected to OLT1, and connected device 2 is an aggregation switch connected to OLT2, OLT3, and OLT4. Since the actual service traffic of each OLT is the same, the allocated bandwidth ratio between connected device 1 and connected device 2 can be determined to be 1:3. Further, if the port bandwidth of the first physical port is 100GE, then connected device 1 can obtain an allocated bandwidth of 25GE, and connected device 2 can obtain an allocated bandwidth of 75GE, and FlexE Client1 and FlexE Client2 with bandwidths of 25GE and 75GE respectively can be created.

[0041] Step S206: Create the same virtual local area network on the corresponding virtual Ethernet interface according to the virtual local area network information of each of the connected devices.

[0042] By creating multiple flexible Ethernet clients on physical ports and creating virtual local area networks (VLANs) on corresponding virtual Ethernet interfaces according to existing VLAN planning through the above embodiments of this disclosure, the problem of VLAN conflicts on high-speed ports caused by data center resource pooling transformation in related technologies can be solved. Moreover, the implementation method is simple and achieves the technical effect of saving transformation costs.

[0043] In an exemplary embodiment, if two virtual local area networks (VLANs) VLAN1 and VLAN2 are configured on the optical line terminal (OLT1), then two identical virtual local area networks VLAN1 and VLAN2 also need to be created on the virtual Ethernet interface (VEI1) corresponding to OLT1.

[0044] In this embodiment, each VLAN on each connected device is mapped to a virtual Ethernet interface. Since the virtual Ethernet interfaces corresponding to each connected device are different, even if the VLAN IDs of the virtual LANs are the same, they are located on different virtual Ethernet interfaces and will not affect data transmission.

[0045] In some embodiments, step S206 may include: creating one or more virtual local area networks (VLANs) on the virtual Ethernet interface corresponding to the connected device based on one or more VLAN identifiers corresponding to each connected device, wherein each newly created VLAN corresponds to one VLAN identifier.

[0046] In this embodiment, the original VLAN plan can be retained, saving the time consumed by replanning VLANs and improving the efficiency of data center resource pooling transformation.

[0047] In this embodiment of the disclosure, through the above steps S202, S204 and S206, during the data center resource pooling transformation process, there is no need to replan VLANs or add new physical ports or DC-leaf. This can effectively avoid the VLAN conflict problem when multiple connected devices share the same physical port, improve the efficiency of data center resource pooling transformation, save costs, and have high network flexibility and scalability.

[0048] In some embodiments, before step S202, the method may further include the following steps: detecting whether there is a conflict in the virtual local area networks (VLANs) of the plurality of connected devices connected to the first physical port; and enabling flexible Ethernet functionality in response to the existence of a VLAN conflict. For example, during data center resource pooling transformation, or when VLANs change, it is possible to detect whether multiple VLANs aggregated by the DC-leaf node have the same VLAN ID. Only when a VLAN conflict exists is flexible Ethernet functionality enabled, and the steps in the above method embodiments are executed. If there is no conflict between multiple VLANs, the VLAN conflict resolution process in this embodiment can be skipped, thereby improving the efficiency of data center resource pooling transformation. However, this embodiment is not limited to this.

[0049] In some embodiments, after step S206, the method may further include the following steps: notifying a second device in the broadband access server resource pool to configure a second physical port according to the configuration information of the first physical port, wherein the second device is the peer device of the first device, and the second physical port is connected to the first physical port.

[0050] In this embodiment, the first device is the executing entity for steps S202 to S206 described above. The first device may include, but is not limited to, a router or switch of the DC-leaf node. The second device is located in the BRAS resource pool. The second device may include, but is not limited to, a broadband access server or switch. Through this embodiment, the configuration information of the first physical port and the second physical port can be synchronized, thereby ensuring the normal operation of data transmission.

[0051] In some embodiments, the configuration information of the first physical port includes at least one of the following:

[0052] The number of the plurality of connected devices;

[0053] The number of the multiple flexible Ethernet clients;

[0054] Virtual local area network information of the multiple connected devices;

[0055] Virtual LAN information of the multiple virtual Ethernet interfaces;

[0056] The allocated bandwidth of the multiple connected devices;

[0057] The bandwidth of the multiple flexible Ethernet clients.

[0058] In this embodiment, the first device can directly synchronize the relevant information of the created Flexible Ethernet Client and Virtual Ethernet Interface (including the Virtual LAN information of each Virtual Ethernet Interface) to the second device, or it can synchronize the relevant information of consecutive devices to the second device, allowing the second device to determine the corresponding Flexible Ethernet Client and Virtual Ethernet Interface information itself. For example, the second device can refer to the FlexE Client and VEI creation process in step S204 and the VLAN creation process in step S206 to complete the configuration of the second physical port.

[0059] Through the above embodiments of this disclosure, multiple flexible Ethernet clients can be created according to actual business needs, and virtual LANs can be divided on the corresponding virtual Ethernet interfaces. This solves the problem of VLAN conflicts on high-speed ports caused by data center resource pooling transformation in related technologies. The implementation method is simple, does not require reconfiguration of VLANs of the existing OLT, does not require additional forwarding table resources, and can be implemented on existing flexible Ethernet devices, which can save the cost of data center resource pooling transformation.

[0060] Figure 3 is a schematic diagram of the bearer network structure before data center resource pooling transformation in one embodiment of this disclosure. As shown in Figure 3, the bearer network includes the following structure:

[0061] A core router (CR) is a core layer device in the bearer network, responsible for handling a large number of data transmission tasks, processing data from the aggregation layer, and forwarding it correctly and efficiently to the next network node. A CR can connect to multiple broadband access servers.

[0062] A Broadband Access Server (BRAS), a critical network device located between the broadband access network and the backbone network, is responsible for authenticating users accessing the network to ensure that only authorized users can use network resources. In this embodiment, each BRAS can be connected to one OLT via a direct-connect physical port, or it can be connected to multiple OLTs via an aggregation switch.

[0063] The aggregation switch (HJSW) is responsible for aggregating and forwarding data from multiple access layer devices to the core layer devices. In this embodiment, each HJSW connects to multiple OLTs.

[0064] Optical Line Terminal (OLT) is used to manage access between the network and users. Each OLT can be configured with one or more VLANs.

[0065] In this embodiment, when planning VLANs, the bearer network in the related technology only needs to ensure that the VLANs of the OLTs connected to each BRAS do not conflict within the same area. For example, within a single directly connected physical port, it is necessary to ensure that the VLANs on the OLT connected to it do not conflict; within a single aggregation switch, it is necessary to ensure that the VLANs of multiple OLTs connected to this aggregation switch do not conflict.

[0066] As shown in Figure 3, the bearer network includes BRAS1 and BRAS2. BRAS1 is connected to OLT1 via a direct physical port, and OLT1 is configured with VLAN 100 and VLAN 200. BRAS2 is connected to OLT2, OLT3, and OLT4 via an aggregation switch. OLT2 is configured with VLAN 100, OLT3 with VLAN 200, and OLT4 with VLAN 300.

[0067] Figure 4 is a schematic diagram illustrating VLAN conflicts occurring during data center resource pooling transformation in one embodiment of this disclosure. As shown in Figure 4, the transformed bearer network further includes:

[0068] The BRAS resource pool is formed by pooling multiple BRAS in the original bearer network. It is connected to the direct physical ports or aggregation switches in the original bearer network through DC-leaf nodes and M-leaf nodes.

[0069] DC-leaf nodes are used to directly connect to servers or storage devices. They have high-speed ports and can meet the access needs of a large number of servers in a data center. In this embodiment, the DC-leaf node is directly connected to the BRAS resource pool.

[0070] M-leaf nodes are used to connect network devices in different data centers or different locations within a city. In this embodiment, the M-leaf node is connected to multiple connection devices (aggregation switches and / or direct-connect physical ports).

[0071] As shown in Figure 4, during the data center resource pooling transformation, the four OLTs in the original bearer network are connected to the transformed pooled BRAS through the same physical port. VLAN (VLAN 100, VLAN 200) conflicts occur between the VLAN on OLT1 and the VLANs on OLT2 and OLT3 on the high-speed port between the DC-leaf and the resource pool. For example, the high-speed port could be a 100GE port.

[0072] Figure 5 is a schematic diagram of the network architecture of the bearer network after data center resource pooling transformation in one embodiment of this disclosure. As shown in Figure 5, according to the VLAN conflict handling method in the above embodiment, multiple FlexE Clients can be established on the high-speed physical port of the DC-leaf node according to the service bandwidth requirements, and VLANs can be configured on the VEI interfaces corresponding to these FlexE Clients to resolve VLAN conflicts.

[0073] Assuming the high-speed physical port is 100GE, the specific steps to resolve VLAN conflicts are as follows:

[0074] Beginning: When a VLAN conflict occurs as shown in Figure 4;

[0075] Step 1: Enable FlexE on the 100GE port of the DC-leaf router connected to the resource pool;

[0076] Step 2: On the 100GE port of the DC-leaf router connected to the resource pool, create FlexE Clients based on the actual user or traffic allocation to the OLT service bandwidth of that resource. For example, assuming that the traffic from OLT2, OLT3, and OLT4 to the resource pool is three times that from OLT1 to the resource pool, you can create FlexE Client1 and FlexE Client2 with bandwidths of 25GE and 75GE respectively on this 100G port, according to the FlexE 5GE granularity.

[0077] Step 3: Create the corresponding VEI1 interface on the FlexE Client 1 of the router where DC-leaf is located, and create VLAN 100 and VLAN 200 on this interface to associate with VLAN 100 and VLAN 200 on OLT1;

[0078] Step 4: Create the corresponding VEI2 interface on the FlexE Client 2 of the router where DC-leaf is located, and create VLAN 100, VLAN 200 and VLAN 300 on this interface, and associate them with VLAN 100, VLAN 200 and VLAN 300 on OLT2, OLT3 and OLT4.

[0079] Step 5: On the 100GE port of the DC-leaf router connected to the DC-leaf peer device resource pool (e.g., BRAS device or switch), use the same strategy as the DC-leaf router to configure two FlexE Client1 and FlexE Client2 according to the FlexE Client bandwidth and parameters configured in the DC-leaf router, and connect them to the FlexE Client on the DC-leaf router.

[0080] Step 6: Configure the corresponding VLANs on the two FlexE Client1 VEI1 and FlexE Client2 VEI2 ports on the 100GE port of the DC-leaf peer device resource pool that connects to the DC-leaf. Specifically, create VLAN 100 and VLAN 200 on the VEI1 interface of FlexE Client 1, and create VLAN 100, VLAN 200 and VLAN 300 on the VEI2 interface of FlexE Client 2.

[0081] The steps described in this embodiment resolve the VLAN conflict issue on high-speed ports caused by data center resource pooling upgrades in related technologies. Conventional conflict resolution methods either require replanning the VLANs of existing OLTs, wasting manpower and being cumbersome, or require VLAN translation / remapping in the DC-leaf, consuming additional forwarding table resources, or require adding physical ports to the DC-leaf and resource pool, increasing hardware costs. This embodiment avoids these drawbacks. Service data from four OLTs can be accessed to the BRAS resource pool via VPN technology, allowing conflicting VLANs to pass through the same physical port without replanning their own VLANs. This VLAN conflict resolution method can be implemented in existing FlexE devices without designing new equipment or adding additional DC-leaf or physical ports, saving data center resource pooling upgrade costs and improving VLAN flexibility and scalability.

[0082] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solutions of the embodiments of this disclosure, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this disclosure.

[0083] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps in any of the above method embodiments.

[0084] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0085] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0086] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0087] Embodiments of this disclosure also provide a computer program product, including a computer program that, when executed by a processor, implements the steps in any of the method embodiments described above.

[0088] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0089] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0090] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for resolving conflicts in a virtual local area network (VLAN), characterized in that, The method includes: Identify multiple connected devices with VLAN conflicts and the VLAN information of each connected device; Multiple flexible Ethernet clients are created for the multiple connected devices on the first physical port that interfaces with the broadband access server resource pool, and a virtual Ethernet interface is created on each of the flexible Ethernet clients, wherein each of the connected devices corresponds to one flexible Ethernet client and one virtual Ethernet interface; The same virtual local area network is created on the corresponding virtual Ethernet interface based on the virtual local area network information of each of the connected devices.

2. The method according to claim 1, characterized in that, The connection device includes at least one of the following: Directly connected physical ports, wherein each of the directly connected physical ports is connected to an optical line terminal; An aggregation switch, wherein each of the aggregation switches connects to a plurality of the optical line terminals.

3. The method according to claim 2, characterized in that, The virtual local area network information includes at least one of the following: A virtual local area network identifier for one of the optical line terminals connected to the directly connected physical port; Virtual LAN identifiers for the plurality of optical line terminals connected to the aggregation switch; Each of the optical line terminals is equipped with one or more virtual local area networks.

4. The method according to claim 3, characterized in that, The step of creating the same virtual local area network (VLAN) on the corresponding virtual Ethernet interface based on the VLAN information of each of the connected devices includes: Based on one or more virtual LAN identifiers corresponding to each of the connected devices, one or more virtual LANs are created on the virtual Ethernet interface corresponding to the connected device, wherein each newly created virtual LAN corresponds to one virtual LAN identifier.

5. The method according to claim 1, characterized in that, The method further includes: Determine the port bandwidth of the first physical port; Obtain service traffic information of multiple optical line terminals connected to the multiple connection devices.

6. The method according to claim 5, characterized in that, The step of creating multiple flexible Ethernet clients for the multiple connected devices on the first physical port that interfaces with the broadband access server resource pool includes: Based on the service traffic information of the multiple optical line terminals, the port bandwidth is allocated to the multiple connection devices to obtain the allocated bandwidth for each connection device. On the first physical port, a flexible Ethernet client with the same bandwidth is created for each of the connected devices according to the allocated bandwidth.

7. The method according to claim 1, characterized in that, The method further includes: Detect whether there are any conflicts in the virtual local area networks of the multiple connected devices connected to the first physical port; In response to a conflict in the virtual LAN, the Flexible Ethernet feature is enabled.

8. The method according to claim 1, characterized in that, The method further includes: The second device in the broadband access server resource pool is notified to configure the second physical port according to the configuration information of the first physical port, wherein the second device is the peer device of the first device, and the second physical port is connected to the first physical port.

9. The method according to claim 8, characterized in that, The configuration information of the first physical port includes at least one of the following: The number of the plurality of connected devices; The number of the multiple flexible Ethernet clients; Virtual local area network information of the multiple connected devices; Virtual LAN information of the multiple virtual Ethernet interfaces; The allocated bandwidth of the multiple connected devices; The bandwidth of the multiple flexible Ethernet clients.

10. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 9.

11. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 9.

12. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 9.

Images