SFU-LAN port service automatic adaptation configuration method based on equipment type mapping

Abstract

The invention relates to the technical field of passive optical networks, and discloses an SFU-LAN port service automatic adaptation configuration method based on equipment type mapping, which comprises the following steps: an optical line terminal configures a VLAN channel comprising at least two equipment planning VLANs and a default VLAN, and establishes a mapping relationship between an equipment type identified by a network equipment MAC address prefix and the equipment planning VLAN; issuing the configuration and the mapping relation to the SFU-ONU and storing the configuration and the mapping relation; when the LAN side equipment is accessed, the SFU-ONU extracts an uplink message source MAC prefix, and adds a corresponding equipment planning VLAN label or a default VLAN label for forwarding after matching the equipment type; when a downlink message is processed, a target MAC prefix is extracted, and corresponding label forwarding is stripped after matching. According to the invention, the installation complexity and the later maintenance cost can be reduced in a large-scale SFU-ONU deployment scene.

Description

Technical Field

[0001] This application relates to the technical field of passive optical networks, and in particular to a method for automatic service adaptation configuration of SFU-LAN ports based on device type mapping. Background Technology

[0002] In Passive Optical Networks (PONs), the Home User Unit-type Optical Network Unit (SFU-ONU) serves as a key node connecting the Optical Line Terminal (OLT) and Local Area Network (LAN) devices, and is widely used in scenarios with centralized access for multiple devices, such as hotels, schools, and apartments. In existing technologies, the LAN ports of the SFU-ONU typically employ a fixed Virtual Local Area Network (VLAN) configuration mechanism. This means that each LAN port is pre-bound to a specific VLAN, and all devices connected to that LAN port (such as cameras, wireless access points, and computers) interact with the OLT through this fixed VLAN, thereby achieving network isolation and service differentiation between devices on different LAN ports.

[0003] However, this fixed VLAN configuration method has significant limitations: in scenarios with mixed access of multiple types of devices, different devices connected to the same LAN port (such as cameras and wireless APs connected at the same time) cannot achieve VLAN isolation according to device type, and can only share the VLAN bound to the LAN port, resulting in mixed service data; at the same time, the rule of "specified device corresponding to specified LAN port" must be strictly followed during on-site installation (such as cameras must be connected to LAN1 port bound to VLAN10, and wireless APs must be connected to LAN2 port bound to VLAN20). Once the wrong port is plugged in, it will cause VLAN matching errors and trigger service anomalies. In large-scale SFU-ONU deployment scenarios, this greatly increases the complexity of installation and the cost of subsequent maintenance.

[0004] As can be seen from the above, how to reduce installation complexity and subsequent maintenance costs in large-scale SFU-ONU deployment scenarios still needs to be addressed. Summary of the Invention

[0005] To reduce installation complexity and subsequent maintenance costs in large-scale SFU-ONU deployment scenarios, this application provides an automatic service adaptation configuration method for SFU-LAN ports based on device type mapping.

[0006] Firstly, this application provides a method for automatic service adaptation and configuration of SFU-LAN ports based on device type mapping, employing the following technical solution: A method for automatic service adaptation configuration of SFU-LAN port based on device type mapping includes: The optical line terminal is configured with multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. At the same time, a mapping relationship between the device type and the planned VLAN is configured. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device. The optical line terminal sends multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships. When a LAN-side network device connects to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packets, extracts the source MAC address prefix of the uplink packets sent by the network device, and matches the corresponding device type according to the mapping relationship. If a device type is matched, the uplink packet is added with the corresponding planned VLAN tag and then forwarded to the optical line terminal. If no device type is matched, the uplink packet is added with the default VLAN tag and then forwarded to the optical line terminal. When the SFU-ONU processes downlink packets carrying VLAN tags sent by the optical line terminal, it extracts the destination MAC address prefix of the downlink packet, matches the corresponding device type according to the mapping relationship, and if a device type is matched, it strips the device-planned VLAN tag corresponding to the downlink packet and forwards it to the corresponding LAN-side network device. If no device type is matched, it strips the default VLAN tag of the downlink packet and forwards it to the corresponding LAN-side network device.

[0007] Optionally, the method further includes: The planned VLANs for the devices include a first planned VLAN and a second planned VLAN. The first planned VLAN corresponds to the camera device type, and the second planned VLAN corresponds to the wireless AP device type.

[0008] Optionally, the method further includes: The MAC address prefix is ​​the first three bytes of the network device's MAC address, and the SFU-ONU extracts these first three bytes and matches them with the mapping relationship.

[0009] Optionally, the method further includes: The optical line terminal sends multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU in the form of configuration files.

[0010] Optionally, the method further includes: The default VLAN is used to adapt to network devices that are not defined in the mapping relationship, including general network terminals such as computers and printers.

[0011] Optionally, the method further includes: After adding a VLAN tag to the uplink packet, the SFU-ONU forwards it to the optical line terminal through its WAN port.

[0012] Optionally, the method further includes: The SFU-ONU stores the received VLAN channel configurations and mapping relationships in a local non-volatile storage unit, which can still be read and used after the SFU-ONU restarts.

[0013] Secondly, this application provides an SFU-LAN port service automatic adaptation and configuration system based on device type mapping, which adopts the following technical solution: An SFU-LAN port service automatic adaptation configuration system based on device type mapping includes: The optical line terminal configuration module configures multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. It also configures the mapping relationship between the device type and the planned VLAN. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device. The configuration distribution and storage module allows the optical line terminal to distribute multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships. The uplink packet processing module, when a LAN-side network device connects to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packet, extracts the source MAC address prefix of the uplink packet sent by the network device, matches the corresponding device type according to the mapping relationship, if a device type is matched, adds the corresponding planned VLAN tag for the uplink packet and forwards it to the optical line terminal; if no device type is matched, adds the default VLAN tag for the uplink packet and forwards it to the optical line terminal. The downlink packet processing module, when processing downlink packets carrying VLAN tags sent by the optical line terminal by the SFU-ONU, extracts the destination MAC address prefix of the downlink packet, matches the corresponding device type according to the mapping relationship, and if a device type is matched, it strips the device-planned VLAN tag corresponding to the downlink packet and forwards it to the corresponding LAN-side network device. If no device type is matched, it strips the default VLAN tag of the downlink packet and forwards it to the corresponding LAN-side network device.

[0014] Thirdly, this application provides an SFU-LAN port service automatic adaptation and configuration system based on device type mapping, which adopts the following technical solution: An SFU-LAN port service automatic adaptation configuration system based on device type mapping includes a processor, wherein the processor runs a program of the SFU-LAN port service automatic adaptation configuration method based on device type mapping described above.

[0015] Fourthly, this application provides a storage medium, which adopts the following technical solution: A storage medium storing a program for the SFU-LAN port service automatic adaptation configuration method based on device type mapping as described in any one of the above.

[0016] In summary, this application includes at least one of the following beneficial technical effects: Through the collaborative design of the optical line terminal and SFU-ONU, dynamic adaptation of SFU-LAN port services is achieved, bringing two core technical benefits: First, it breaks through the limitations of traditional fixed LAN port VLANs of SFU-ONU. By identifying device types through MAC address prefixes and automatically matching VLAN tags, multiple types of devices (such as cameras, wireless APs, and ordinary PCs) can be flexibly connected to the same LAN port. This enables precise isolation and forwarding of service data according to device type, significantly improving the flexibility and adaptability of the LAN-side network. Second, through preset mapping relationships and automated processing logic, manual intervention is removed from the service configuration process, significantly optimizing the efficiency of the entire process of equipment deployment and maintenance.

[0017] In large-scale SFU-ONU deployment scenarios, during the installation phase, the traditional approach strictly adheres to the rule of "designated devices corresponding to designated LAN ports" (e.g., cameras must be plugged into LAN1, and wireless APs must be plugged into LAN2). Incorrect plugging leads to service disruptions. In scenarios with hundreds or thousands of ONUs, such as hotels and schools, significant manpower is required to verify the port-device correspondence, resulting in extremely low installation efficiency. In contrast, this solution allows devices connected to any LAN port to be automatically identified and matched with the correct VLAN via MAC address prefixes, eliminating the need for manual port differentiation. Installation personnel can operate without specialized training, significantly reducing the probability of incorrect plugging and the cost of error correction. During the later maintenance phase, when devices are replaced, relocated, or new devices are added, the traditional approach requires reconfiguring LAN port VLAN bindings. In large-scale deployments, this necessitates operation on each ONU, which is time-consuming and error-prone. This solution only requires ensuring that the MAC prefix of the new device conforms to the mapping rules, and the SFU-ONU will automatically adapt without modifying the ONU configuration. This significantly reduces the workload and operational difficulty for maintenance personnel, indirectly reducing maintenance costs. Attached Figure Description

[0018] Figure 1 This is a flowchart illustrating an SFU-LAN port service automatic adaptation configuration method based on device type mapping, according to an exemplary embodiment.

[0019] Figure 2 This is a structural block diagram of an SFU-LAN port service automatic adaptation configuration system based on device type mapping, according to an exemplary embodiment. Detailed Implementation

[0020] The embodiments of this application are described in detail below, and examples of the embodiments are shown in the accompanying drawings.

[0021] In the description of this specification, the references to "certain embodiments," "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples" refer to specific features, structures, materials, or characteristics described in connection with the described embodiment or example, which are 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.

[0022] This application discloses an SFU-LAN port service automatic adaptation configuration method based on device type mapping, referring to... Figure 1 ,include: The S100 optical line terminal is configured with multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. At the same time, the mapping relationship between device type and planned VLAN is configured. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device.

[0023] The specific execution process of S100 includes the following steps: Step 1, in the detailed configuration of VLAN channels, the optical line terminal needs to complete the creation and parameter setting of multiple VLAN channels through its own configuration interface (such as the command line interface CLI, network management system EMS). Specifically, the VLAN type and number must first be determined: According to the actual business scenario (such as the equipment access requirements of hotels and schools), the optical line terminal needs to plan at least two types of VLANs, of which the number of planned VLANs for each device must be at least 2. Each VLAN corresponds to a specific type of device (such as cameras, wireless APs, IP phones, etc.) to achieve service isolation for similar devices. For example, for a hotel scenario, VLAN 100 can be configured to correspond to guest room cameras and VLAN 200 to correspond to corridor wireless APs. The default number of VLANs is 1, which is used to adapt to general devices that are not predefined (such as laptops carried by guests, front desk printers, etc.) to avoid such devices being unable to access the network due to the lack of corresponding planned VLANs. For example, VLAN 300 can be configured as the default VLAN. Secondly, the core parameters of the VLAN need to be configured. For each VLAN channel, the optical line terminal needs to set key parameters to ensure that the VLAN can transmit data normally. These include VLAN ID (assign a unique identifier to each VLAN, such as 100, 200, or 300, as the core identifier of the VLAN tag in the data frame), VLAN tag type (select the tag format according to the network architecture, such as ordinary 802.1Q tag or QinQ dual-layer tag, to ensure that the tag resolution rules between the optical line terminal and the SFU-ONU are consistent), forwarding priority (set priority for different VLANs, such as VLAN 100 of the camera has a higher priority than VLAN 200 of the wireless AP, to ensure the transmission quality of critical services such as video surveillance), and port binding rules (bind the uplink ports carrying these VLANs, such as the ports connected to the core switch, and the downlink ports, such as the PON ports connected to the SFU-ONU, on the optical line terminal side to ensure that VLAN data can flow bidirectionally between the optical line terminal and the SFU-ONU).

[0024] Step 2, during the configuration of the device type and VLAN mapping relationship, the optical line terminal needs to establish the association rule of "device type → MAC address prefix → device planned VLAN". The specific operation is as follows: First, determine the MAC address prefix of the device type. The first 3 bytes (24 bits in total) of the MAC address of the network device is the "Organization Unique Identifier (OUI)" assigned by the manufacturer. Devices of the same type from the same manufacturer usually share a fixed OUI. For example, the MAC address prefix of a certain brand of camera is uniformly "00:1A:2B", and the MAC address prefix of a certain brand of wireless AP is uniformly "00:3C:4D". The optical line terminal determines the MAC prefix corresponding to each type of device by collecting the device manufacturer information that needs to be accessed in the target scenario (which can be manually entered or obtained from the device manufacturer's document). Next, a mapping table needs to be established. The optical line terminal creates a mapping table in its local configuration database. The table contains three core pieces of information: first, the MAC address prefix (first 3 bytes) of the network device; second, the device type corresponding to the prefix; and third, the planned VLAN ID associated with that device type. For example, a MAC address with the prefix 00:1A:2B corresponds to a camera device type, and the associated planned VLAN ID is 100; a MAC address with the prefix 00:3C:4D corresponds to a wireless AP device type, and the associated planned VLAN ID is 200. This table must ensure the uniqueness of "MAC prefix → device type" (i.e., one MAC prefix corresponds to only one type of device), and the correspondence of "device type → VLAN ID" must be consistent with the planned VLAN configured in the first step. Finally, the mapping relationship is verified and stored. After the optical line terminal is configured, it automatically verifies the integrity (e.g., whether there are MAC prefixes not associated with VLANs) and uniqueness (e.g., whether there are duplicate MAC prefixes). After successful verification, the mapping table is stored in the optical line terminal's non-volatile memory (e.g., Flash), ensuring that it can still be read after the optical line terminal restarts.

[0025] By pre-defining multiple VLAN channels (including planned VLANs and default VLANs) and the mapping relationship between device type and VLAN (based on MAC address prefix) on the optical line terminal side, core rules and judgment criteria are provided for the subsequent automatic adaptation of LAN port services by SFU-ONU. This not only builds a network isolation framework for different devices, but also supports the automated processing of the entire process. It avoids the limitation of strong binding between devices and LAN ports in traditional solutions from the source, and lays the foundation for reducing the installation complexity and maintenance costs of large-scale deployment.

[0026] The S200 optical line terminal sends multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships.

[0027] The specific execution process of S200 includes the following steps: Step 1, Configuration Distribution Operation on the Optical Line Terminal Side: After completing the configuration of the S100, the optical line terminal waits for the SFU-ONU to power on and completes identity authentication and link establishment through the PON protocol (i.e., the SFU-ONU successfully registers with the optical line terminal), and then initiates the configuration distribution process. First, the optical line terminal integrates the multiple VLAN channel configurations defined in the S100 (including the ID, tag type, forwarding priority, port binding rules, etc. of each VLAN) and the mapping relationship between device type and VLAN (including MAC address prefix, corresponding device type, associated VLAN ID, etc.), and packages them into a structured configuration file (such as using XML format or private protocol format to ensure standardized data organization); then, through the dedicated management channel between the optical line terminal and the SFU-ONU (such as extended fields based on the OMCI protocol, or custom private management messages), the configuration file is distributed to the SFU-ONU.

[0028] Step 2, SFU-ONU side receiving and storage operations: After receiving the configuration file from the optical line terminal, the SFU-ONU first performs an integrity check: it checks the file verification and confirms that the data has not been tampered with, and verifies the legality of VLAN parameter formats (such as whether the VLAN ID is within the valid range) and mapping relationship logic (such as whether the MAC prefix corresponds to the VLAN ID). After the verification passes, the SFU-ONU stores the VLAN channel configuration in the local service configuration area (this area is high-speed access storage, for subsequent packet processing modules to call in real time), and stores the mapping relationship between device type and VLAN in a non-volatile storage unit (such as EEPROM) to ensure that the configuration information is not lost after the SFU-ONU restarts or is powered off; finally, the SFU-ONU returns a confirmation message of successful configuration reception to the optical line terminal, marking the completion of S200 execution.

[0029] Through the execution process of S200, the configuration information is transmitted and solidified "from the optical line terminal to the SFU-ONU", enabling the SFU-ONU to obtain all the rules (VLAN parameters and mapping relationships) required for subsequent processing of uplink and downlink packets. On the one hand, this avoids the tedious operation of manually configuring VLANs on each SFU-ONU in the traditional solution, realizing the centralization and automation of configuration; on the other hand, it ensures that the SFU-ONU has the ability to independently determine the device type and adapt to VLANs, providing a data foundation for the automated execution of S300 (uplink packet processing) and S400 (downlink packet processing), and is a key bridge connecting "rule definition" and "service processing".

[0030] When a LAN-side network device connects to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packets, extracts the source MAC address prefix of the uplink packets sent by the network device, and matches the corresponding device type according to the mapping relationship. If a device type is matched, the uplink packet is labeled with the corresponding planned VLAN tag and then forwarded to the optical line terminal. If no device type is matched, the uplink packet is labeled with the default VLAN tag and then forwarded to the optical line terminal.

[0031] The S300 execution process is the core processing step of the SFU-ONU for automatically adapting and forwarding uplink packets sent by LAN-side devices. Specifically, it includes operations such as device access detection, MAC prefix extraction, type matching, and VLAN tag processing. The process is as follows: When a LAN-side network device (such as a camera, wireless AP, or computer) is connected to any LAN port of the SFU-ONU via a network cable, the SFU-ONU's port detection module will detect the device connection (triggered by a change in the link layer signal or a link layer broadcast message sent by the device), and then initiate the uplink packet processing procedure. First, the SFU-ONU extracts the first 3 bytes of the source MAC address (i.e., the manufacturer-assigned OUI prefix, such as "00:1A:2B" for a camera and "00:3C:4D" for a wireless AP) from the first or all subsequent uplink packets sent by the device. Then, the SFU-ONU calls the locally stored mapping table (i.e., the "MAC prefix → device type → VLAN ID" association rule stored in the S200) and compares and matches the extracted MAC prefix with the records in the table.

[0032] If a match is successful (e.g., the extracted "00:1A:2B" prefix corresponds to the "Camera" type in the table and is associated with VLAN 100), the SFU-ONU's VLAN tagging module will add the corresponding planned VLAN tag (e.g., VLAN 100 tag) to the uplink packet according to the VLAN parameters stored in the S200 (e.g., the tag type is 802.1Q). If a match fails (i.e., the extracted MAC prefix is ​​not recorded in the mapping table, such as the "00:5E:1F" prefix for a regular computer), a default VLAN tag (e.g., VLAN 300 tag) will be added to the packet. Finally, the SFU-ONU forwards the tagged uplink packet to the optical line terminal (optical line terminal) through its WAN port (the PON port connected to the optical line terminal), completing the entire uplink processing flow.

[0033] Through the execution process of the S300 described above, on the one hand, the device type is automatically identified and VLAN is matched by the MAC prefix, so that multiple devices can be flexibly connected to the same LAN port (such as cameras and wireless APs sharing a LAN port), and service isolation can be achieved without manual intervention; on the other hand, the process is completed autonomously by the SFU-ONU without relying on real-time commands from the optical line terminal, ensuring processing efficiency and network response speed. This provides key technical support for "devices can be plugged in at will and the network can be connected automatically" in large-scale deployment scenarios, and directly reduces the strict requirements for port binding during installation.

[0034] When the S400 processes downlink packets carrying VLAN tags sent by the optical line terminal to the SFU-ONU, it extracts the destination MAC address prefix of the downlink packet and matches the corresponding device type according to the mapping relationship. If a device type is matched, the device-planned VLAN tag corresponding to the downlink packet is stripped and forwarded to the corresponding LAN-side network device. If no device type is matched, the default VLAN tag of the downlink packet is stripped and forwarded to the corresponding LAN-side network device.

[0035] The S400 execution process involves the SFU-ONU performing VLAN tag stripping and precise forwarding of downlink packets sent by the optical line terminal. This includes downlink packet reception, destination MAC prefix extraction, device type matching, and VLAN tag stripping, as follows: When the optical line terminal (OLT) has downlink data to send to the LAN-side network device, it encapsulates the data into a downlink packet carrying a VLAN tag (the tag type is consistent with the S100 configuration, such as an 802.1Q tag), and sends it to the SFU-ONU via the PON link. After receiving the downlink packet, the WAN port (PON port) of the SFU-ONU first enters the downlink processing module, extracts the first 3 bytes of the destination MAC address of the packet (i.e., the target device's manufacturer OUI prefix, such as "00:1A:2B" for a camera and "00:5E:1F" for a regular PC); then, it calls the locally stored mapping table (the "MAC prefix → device type → VLAN ID" rule stored in the S200) and compares and matches the extracted destination MAC prefix with the records in the table.

[0036] If a match is successful (e.g., the extracted "00:1A:2B" prefix corresponds to the "camera" type and is associated with VLAN 100), and the VLAN tag carried in the packet matches the planned VLAN ID of the device type (e.g., the tag is VLAN 100), the SFU-ONU's VLAN tag processing module will strip the VLAN tag (remove the 802.1Q tag field). If a match fails (i.e., the destination MAC prefix is ​​not recorded in the mapping table), and the packet carries the default VLAN tag (e.g., VLAN 300), then the default VLAN tag will be stripped. Finally, the SFU-ONU forwards the stripped downlink packet to the target LAN-side network device through the corresponding LAN port (determined by the binding relationship between the packet's destination MAC address and the LAN port device, such as LAN1 port where the camera is connected), completing the entire downlink processing flow.

[0037] Based on the S400 execution process described above, "precise decapsulation and forwarding" from the optical line terminal to the LAN-side device is achieved, forming a closed loop with S300 (uplink processing): On the one hand, by stripping VLAN tags, it ensures that LAN-side devices (such as cameras, ordinary PCs, and other terminals without VLAN processing capabilities) can receive and parse the original packets, guaranteeing normal service communication; on the other hand, based on the destination MAC prefix matching logic, it ensures that downlink packets can be accurately forwarded to the corresponding device, avoiding service anomalies caused by VLAN tag residue or forwarding errors. This process eliminates the need for manual configuration of the LAN port and device mapping, further strengthening the "plug-and-play" feature. In large-scale deployment scenarios, it reduces maintenance costs caused by downlink data forwarding errors and, in conjunction with uplink processing, achieves automatic service adaptation across the entire link.

[0038] Based on the solutions in the embodiments of this application, the following explanation will be further illustrated with an example: Taking a large-scale SFU-ONU deployment in 100 guest rooms of a chain hotel as an example, in the traditional solution, each guest room's SFU-ONU must be installed strictly according to the rule of "LAN1 port connected to the guest room camera, LAN2 port connected to the wireless AP". The installation personnel need to check the port and device correspondence for each unit. If the wrong port is plugged in (such as the camera being connected to LAN2 port), it is necessary to replug it and manually configure the VLAN. It would take several hours to check all 100 guest rooms. In contrast, this solution pre-configures the following on the optical line terminal side through S100: VLAN100 corresponds to the camera (MAC prefix "00:1A:2B"), VLAN200 corresponds to the wireless AP (MAC prefix "00:3C:4D"), and VLAN300 is the default VLAN. The configuration is then distributed to all SFU-ONUs through S200. During installation, personnel do not need to distinguish between LAN ports. They can simply connect any camera or wireless AP to the LAN port of the SFU-ONU. The SFU-ONU will then extract the device's MAC prefix through the S300 and automatically match the VLAN tag for forwarding. The installation time for 100 guest rooms can be shortened to within 1 hour, significantly reducing the complexity of installation.

[0039] When five cameras in a hotel room on a certain floor need to be replaced due to malfunction, the traditional solution requires maintenance personnel to bring configuration tools to the site, log into the corresponding SFU-ONU for each camera, and reconfigure the LAN port VLAN binding for the new camera. If different floors are involved, this requires repeated trips. In this solution, as long as the new camera's MAC prefix is ​​still "00:1A:2B" (same brand equipment), it can be connected to any LAN port after replacement. The SFU-ONU will automatically identify the MAC prefix and match the VLAN100 tag through S300, without requiring maintenance personnel to manually modify the configuration. Even if the new camera is from another brand (MAC prefix "00:4E:5F"), the mapping relationship between the prefix and VLAN100 only needs to be supplemented on the optical line terminal side through S100, and then distributed to all SFU-ONUs in batches through S200. The replacement of five cameras can be completed remotely in the background without the need for on-site personnel, significantly reducing subsequent maintenance costs.

[0040] If the hotel later adds a printer (a general-purpose device) to each guest room, the traditional solution requires logging into each of the 100 SFU-ONUs to configure the default VLAN for the printer. If any printer is missed during the process, the printer in that guest room will not be able to connect to the network. This solution, through the default VLAN 300 preset by the S100, can directly adapt to all undefined general-purpose devices. When adding a printer, simply connect it to any LAN port of the SFU-ONU. The SFU-ONU will detect that the printer's MAC prefix is ​​not in the mapping relationship through the S300 and automatically add a VLAN 300 label for forwarding. There is no need for maintenance personnel to configure each device individually. Adding printers to 100 guest rooms can be completed within 10 minutes, further demonstrating the maintenance efficiency advantage in large-scale deployment scenarios.

[0041] This application discloses an SFU-LAN port service automatic adaptation and configuration system based on device type mapping, referring to... Figure 2 ,include: The optical line terminal configuration module 001 configures multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. At the same time, it configures the mapping relationship between device type and planned VLAN. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device. The configuration distribution and storage module 002 allows the optical line terminal to distribute multiple VLAN channel configurations and the mapping relationship between device types and planned VLANs to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships. Uplink packet processing module 003: When a LAN-side network device is connected to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packet, extracts the source MAC address prefix of the uplink packet sent by the network device, matches the corresponding device type according to the mapping relationship, if a device type is matched, adds the corresponding planned VLAN tag to the uplink packet and forwards it to the optical line terminal; if no device type is matched, adds the default VLAN tag to the uplink packet and forwards it to the optical line terminal. Downlink packet processing module 004, when processing downlink packets carrying VLAN tags sent by the optical line terminal by the SFU-ONU, extracts the destination MAC address prefix of the downlink packet, matches the corresponding device type according to the mapping relationship. If a device type is matched, the device-planned VLAN tag corresponding to the downlink packet is stripped and forwarded to the corresponding LAN-side network device. If no device type is matched, the default VLAN tag of the downlink packet is stripped and forwarded to the corresponding LAN-side network device.

[0042] This application also discloses an SFU-LAN port service automatic adaptation configuration system based on device type mapping, including a processor, wherein the processor runs a program of the SFU-LAN port service automatic adaptation configuration method based on device type mapping described above.

[0043] This application also discloses a storage medium storing a program for the SFU-LAN port service automatic adaptation configuration method based on device type mapping as described in any one of the above embodiments.

[0044] 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 automatic adaptation and configuration of SFU-LA port services based on device type mapping, characterized in that, include: The optical line terminal is configured with multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. At the same time, a mapping relationship between the device type and the planned VLAN is configured. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device. The optical line terminal sends multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships. When a LAN-side network device connects to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packets, extracts the source MAC address prefix of the uplink packets sent by the network device, and matches the corresponding device type according to the mapping relationship. If a device type is matched, the uplink packet is added with the corresponding planned VLAN tag and then forwarded to the optical line terminal. If no device type is matched, the uplink packet is added with the default VLAN tag and then forwarded to the optical line terminal. When the SFU-ONU processes downlink packets carrying VLAN tags sent by the optical line terminal, it extracts the destination MAC address prefix of the downlink packet, matches the corresponding device type according to the mapping relationship, and if a device type is matched, it strips the device-planned VLAN tag corresponding to the downlink packet and forwards it to the corresponding LAN-side network device. If no device type is matched, it strips the default VLAN tag of the downlink packet and forwards it to the corresponding LAN-side network device.

2. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: The planned VLANs for the devices include a first planned VLAN and a second planned VLAN. The first planned VLAN corresponds to the camera device type, and the second planned VLAN corresponds to the wireless AP device type.

3. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: The MAC address prefix is ​​the first three bytes of the network device's MAC address, and the SFU-ONU extracts these first three bytes and matches them with the mapping relationship.

4. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: The optical line terminal sends multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU in the form of configuration files.

5. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: The default VLAN is used to adapt to network devices that are not defined in the mapping relationship, including general network terminals such as computers and printers.

6. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: After adding a VLAN tag to the uplink packet, the SFU-ONU forwards it to the optical line terminal through its WAN port.

7. The SFU-LAN port service automatic adaptation configuration method based on device type mapping according to claim 1, characterized in that, The method also includes: The SFU-ONU stores the received VLAN channel configurations and mapping relationships in a local non-volatile storage unit, which can still be read and used after the SFU-ONU restarts.

8. A system for automatic service adaptation and configuration of SFU-LAN ports based on device type mapping, characterized in that, include: The optical line terminal configuration module configures multiple VLAN channels corresponding to virtual local area networks. The VLAN channels include at least two planned VLANs and one default VLAN. It also configures the mapping relationship between the device type and the planned VLAN. In the mapping relationship, the device type is uniquely identified by the MAC address prefix of the network device. The configuration distribution and storage module allows the optical line terminal to distribute multiple VLAN channel configurations and the mapping relationship between device type and planned VLAN to the SFU-ONU. The SFU-ONU receives and stores the VLAN channel configurations and mapping relationships. The uplink packet processing module, when a LAN-side network device connects to the LAN port of the SFU-ONU, the SFU-ONU processes the uplink packet, extracts the source MAC address prefix of the uplink packet sent by the network device, matches the corresponding device type according to the mapping relationship, if a device type is matched, adds the corresponding planned VLAN tag for the uplink packet and forwards it to the optical line terminal; if no device type is matched, adds the default VLAN tag for the uplink packet and forwards it to the optical line terminal. The downlink packet processing module, when processing downlink packets carrying VLAN tags sent by the optical line terminal by the SFU-ONU, extracts the destination MAC address prefix of the downlink packet, matches the corresponding device type according to the mapping relationship, and if a device type is matched, it strips the device-planned VLAN tag corresponding to the downlink packet and forwards it to the corresponding LAN-side network device. If no device type is matched, it strips the default VLAN tag of the downlink packet and forwards it to the corresponding LAN-side network device.

9. A system for automatic service adaptation and configuration of SFU-LAN ports based on device type mapping, characterized in that, Includes a processor, wherein the processor runs a program for the SFU-LAN port service automatic adaptation configuration method based on device type mapping as described in any one of claims 1-7.

10. A storage medium, characterized in that, The program stores the SFU-LAN port service automatic adaptation configuration method based on device type mapping as described in any one of claims 1-7.

Images