A system supporting parallel access of multiple optical modules

Abstract

A system supporting parallel access of multiple optical modules includes a network interface card (NIC), a multi-channel interface module, and a NIC controller. The multi-channel interface module is connected to the NIC and has at least two optical module slots. The NIC controller includes a compatibility management module configured to: when an optical module is detected inserted into an optical module slot, independently perform an identity adaptation operation for each active optical module slot—specifically, intercepting read requests to the optical module's identity identifier area, obtaining the actual identity information returned by the optical module, querying a compatibility mapping table to obtain corresponding replacement identity information, and returning the replacement identity information to replace the actual identity information. This system effectively overcomes the compatibility bottleneck during parallel access of multiple optical modules, promoting network expansion and performance improvement.

Description

Technical Field

[0001] This invention relates to the field of computer network technology, and in particular to a system that supports parallel access of multiple optical modules. Background Technology

[0002] In traditional switches, network interface cards (NICs) and the switch are typically designed separately. The NIC connects to the switch as an independent hardware device via interfaces such as PCIe. When connecting an optical module to the NIC, compatibility verification is required. Because optical modules from different manufacturers differ in identification, communication protocols, and performance parameters, when multiple optical modules of different models or manufacturers are connected in parallel to the same NIC or switch, issues such as NIC conflicts, protocol incompatibility, or unsupported drivers can easily occur, leading to system identification anomalies, data transmission interruptions, or even device malfunctions. Especially in scenarios with extremely high requirements for network bandwidth and stability, such as data centers and cloud computing, compatibility issues when multiple optical modules are connected in parallel have become a key bottleneck restricting network expansion and performance improvement.

[0003] A search revealed a Chinese patent with publication number CN116015437A that discloses a method for obtaining target network interface card (NIC) information and target optical module information. Based on this information, the patent queries a compatibility list, which includes compatibility test results between the NIC and optical modules from multiple different manufacturers, and outputs these results. Since optical modules with different manufacturer and hardware specifications are considered different optical modules, the compatibility list, including test results, accurately determines the compatibility of the NIC and optical module. This avoids the problem of inconsistent definitions of undefined fields during NIC identification, even if optical modules from different manufacturers have the same structure, leading to network connectivity issues.

[0004] However, the above technical solutions only address the compatibility query issue between the network card and a single optical module, and do not address the collaborative working mechanism when multiple different optical modules are connected to the same system in parallel. When more optical modules need to work in parallel, the number of corresponding network cards needs to be increased. This not only occupies more PCIe slot resources, limiting the motherboard's expansion capabilities, but also significantly increases hardware costs. Summary of the Invention

[0005] To address the shortcomings of existing technologies, the present invention aims to provide a system that supports parallel access of multiple optical modules, thereby solving the problem that a single network interface controller cannot simultaneously and collaboratively manage the parallel operation of multiple optical modules from different manufacturers or models.

[0006] In view of the above situation and to overcome the defects of the prior art, the present invention provides a system that supports parallel access of multiple optical modules, including a network card for data interaction with an external network and for providing a network access interface for the system;

[0007] A multi-channel interface module is connected to the network card, and the multi-channel interface module is provided with at least two optical module slots;

[0008] A network interface controller, connected to the network interface card and the multi-channel interface module, is used to control the data transmission of the network interface card and coordinate the working status of each optical module slot in the multi-channel interface module.

[0009] The network interface controller includes a compatibility management module, configured to: when an optical module is detected inserted into the optical module slot, perform an identity adaptation operation independently for each optical module slot in the working state. The identity adaptation operation includes: intercepting the read request for the identity identification area of ​​the optical module, obtaining the actual identity information returned by the optical module, querying the compatibility mapping table to obtain the corresponding replacement identity information, and returning the replacement identity information to replace the actual identity information.

[0010] More preferably, the compatibility management module is further configured as follows:

[0011] When the inserted optical modules are detected to be from the same manufacturer and series of products, the compatibility management module classifies them into the same adaptation group and shares the basic adaptation parameters.

[0012] When the inserted optical modules are detected to be from different manufacturers or different product series, the compatibility management module classifies them into different adaptation groups, coordinates the resource allocation and working mode between each adaptation group, and dynamically allocates data bandwidth according to the specifications and performance of the optical modules in each adaptation group.

[0013] More preferably, the network interface card controller further includes:

[0014] The multiplexing module is used to split the uplink data stream from the network card into multiple sub-streams and route them to each active optical module slot, and to multiplex the sub-streams from each optical module slot into a downlink data stream and send it back to the network card controller.

[0015] The virtualization driver module virtualizes the network card into multiple independent network interface devices, which are then bound to each active optical module slot.

[0016] More preferably, the compatibility management module maintains an independent port information structure for each active optical module slot at the driver layer;

[0017] The identity adaptation operation is performed independently based on the port information structure, and includes:

[0018] Based on the target port number carried in the I2C read command, the request is associated with the corresponding port information structure;

[0019] Using the current network interface controller's identifier and the port information structure, independently query the compatibility mapping table to obtain the replacement identity information specific to that port and then replace it;

[0020] The original identity information, replacement identity information, and adaptation status of each port are maintained independently in the corresponding port information structure.

[0021] More preferably, the compatibility management module maintains the compatibility mapping table, which is a read-only resource shared by multiple ports; the compatibility management module ensures that concurrent query operations on the compatibility mapping table from different ports are idempotent and consistent.

[0022] More preferably, the compatibility mapping table is dynamically generated by the compatibility management module, and the generation process includes:

[0023] Enumerate and identify the manufacturer identifier of the network interface controller;

[0024] Based on the identified manufacturer identifier, the corresponding compatibility entry is loaded from a pre-stored global compatibility database.

[0025] Based on the loaded compatibility entries, a runtime mapping table is generated, which contains the mapping relationship between the network card manufacturer identifier, the original optical module manufacturer identifier, and the replacement manufacturer identifier.

[0026] More preferably, when the inserted optical module is a new model or a new model not recorded in the global compatibility database, the compatibility management module will trigger a compatibility learning process:

[0027] Obtain the identity information, performance parameters, and communication protocol version of the optical module.

[0028] The above information is matched with the hardware specifications of the network interface card controller. If the basic communication protocol is compatible, temporary adaptation parameters are automatically generated and added to the temporary extension area of ​​the compatibility mapping table. At the same time, a model registration request is sent to the global compatibility database. After the database completes the model authentication, the temporary adaptation parameters are updated to formal entries and fixed to the compatibility mapping table.

[0029] More preferably, the compatibility learning process further includes:

[0030] Read and record the specifications of the new optical module model;

[0031] The specifications of the new optical module are compared and analyzed with the optical module information already recorded in the compatibility mapping table;

[0032] Based on the comparative analysis results, match one or more known optical module models with the most similar specifications from the compatibility mapping table;

[0033] Using the compatibility scheme corresponding to the known optical module model as a basis, an initial adaptation strategy is generated and applied for the new optical module model.

[0034] In a further preferred embodiment, the compatibility learning process further includes: after adopting an initial adaptation strategy, monitoring the fluctuation of key performance indicators within a preset time period; if the key performance indicators are all stable within a preset threshold range, the initial adaptation strategy is determined to be effective, and the adaptation parameters of the new optical module are formally added to the compatibility mapping table.

[0035] More preferably, the key performance indicator includes the bit error rate.

[0036] Compared with existing technologies, the present invention has the following beneficial effects: First, by setting a compatibility management module in the network interface card controller, when multiple optical modules from different manufacturers or models are accessed in parallel, the identity adaptation operation can be performed independently for each optical module slot. By intercepting reading requests, obtaining actual identity information, and querying the compatibility mapping table to replace the identity information, the system identification anomaly caused by identity conflict and protocol incompatibility is effectively solved. This enables parallel collaborative work of different optical modules in the same system, effectively breaks through the compatibility bottleneck when multiple optical modules are accessed in parallel, and promotes network expansion and performance improvement. Attached Figure Description

[0037] Figure 1 This is the system topology diagram of the present invention.

[0038] Figure 2 This is a topology diagram of one embodiment of the system of the present invention.

[0039] Figure 3 This is a flowchart of the identity adaptation operation method of the present invention.

[0040] Figure 4 This is a flowchart of the compatibility mapping table generation process of the present invention.

[0041] Figure 5 This is a flowchart of the compatibility learning process method of the present invention. Detailed Implementation

[0042] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0043] To facilitate understanding of the methods and systems provided in the embodiments of this application, the background of the embodiments of this application will be introduced before introducing the embodiments of this application.

[0044] In traditional switches, network interface cards (NICs) and the switch are typically designed separately. The NIC connects to the switch as an independent hardware device via interfaces such as PCIe. When connecting an optical module to the NIC, compatibility verification is required. Because optical modules from different manufacturers differ in identification, communication protocols, and performance parameters, when multiple optical modules of different models or manufacturers are connected in parallel to the same NIC or switch, issues such as NIC conflicts, protocol incompatibility, or unsupported drivers can easily occur, leading to system identification anomalies, data transmission interruptions, or even device malfunctions. Especially in scenarios with extremely high requirements for network bandwidth and stability, such as data centers and cloud computing, compatibility issues when multiple optical modules are connected in parallel have become a key bottleneck restricting network expansion and performance improvement.

[0045] A search revealed a Chinese patent with publication number CN116015437A that discloses a method for obtaining target network interface card (NIC) information and target optical module information. Based on this information, the patent queries a compatibility list, which includes compatibility test results between the NIC and optical modules from multiple different manufacturers, and outputs these results. Since optical modules with different manufacturer and hardware specifications are considered different optical modules, the compatibility list, including test results, accurately determines the compatibility of the NIC and optical module. This avoids the problem of inconsistent definitions of undefined fields during NIC identification, even if optical modules from different manufacturers have the same structure, leading to network connectivity issues.

[0046] However, the above technical solutions only address the compatibility query issue between the network card and a single optical module, and do not address the collaborative working mechanism when multiple different optical modules are connected to the same system in parallel. When more optical modules need to work in parallel, the number of corresponding network cards needs to be increased. This not only occupies more PCIe slot resources, limiting the motherboard's expansion capabilities, but also significantly increases hardware costs and device power consumption.

[0047] Please see Figure 1 In one specific embodiment, the present invention provides a system that supports parallel access of multiple optical modules, including: a network interface card (NIC), a multi-channel interface module, and a NIC controller.

[0048] The network interface card (NIC) is used to interact with external networks (such as switches, routers, or peer servers) and provides a standard network access interface (such as a PCIe interface) for the entire system, enabling high-speed data transmission with the host system.

[0049] The multi-channel interface module is connected to the physical layer (PHY) of the network interface card via a high-speed bus (such as an enhanced SFI interface or a parallel optical channel). This module has at least two optical module slots (e.g., standard or enhanced slots such as SFP+, QSFP+, QSFP-DD, etc.) for physically inserting and connecting optical modules of different types and manufacturers. Each optical module slot has independent power supply, an I2C management interface, and a high-speed data channel.

[0050] The network interface card (NIC) controller is the core processing unit of the system, typically integrated into the NIC's application-specific integrated circuit (ASIC) or field-programmable gate array (FPGA). It connects to the NIC's media access control (MAC) layer and the driver circuitry of the multi-channel interface module, responsible for controlling data transmission and coordinating the operational status of the optical module slots within the multi-channel interface module. The NIC controller mainly includes a compatibility management module, a multiplexing module, and a virtualization driver module.

[0051] The working principle of the system of the present invention and the collaborative working method of each module are explained in detail below.

[0052] Compatibility management module and identity adaptation operation

[0053] The compatibility management module is the core component for resolving compatibility issues arising from the parallel access of multiple optical modules. Its core function is to perform "identity adaptation operations".

[0054] When an optical module is inserted into any slot of the multi-channel interface module and powered on, the network interface controller will detect its presence. The compatibility management module is configured to perform the following identity adaptation operation independently for each optical module slot when an optical module is detected to be inserted into a slot and in a working state:

[0055] Step S1: Intercept the read request. When the network card's basic driver or firmware attempts to read the identification area of ​​an optical module in a certain optical module slot via the I2C bus (usually a specific storage address storing information such as manufacturer code, model code, and serial number), the compatibility management module intercepts this read request at the driver layer or hardware abstraction layer.

[0056] Step S2: Obtain actual identity information. The compatibility management module forwards the read request to the actual optical module and obtains the original, actual identification information (i.e., "actual identity information") returned by the optical module.

[0057] Step S3: Query and Replace. The compatibility management module uses the current network interface card (NIC) controller's identifier (e.g., chip ID) and the obtained optical module's actual identity information as a key to query the internally maintained compatibility mapping table. This mapping table predefines the mapping relationship from "NIC controller model + optical module actual identity" to "NIC controller-recognizable replacement identity". The corresponding "replacement identity information" is then retrieved.

[0058] Step S4: Information Return. The compatibility management module returns the retrieved "replacement identity information" to the upper-layer driver or firmware, replacing the original "actual identity information." In this way, the network card driver "sees" an adapted, standard identity that it can correctly recognize and drive, thus avoiding problems such as driver loading failure and link inactivation failure caused by identity conflicts or inconsistencies in undefined fields.

[0059] Optical module grouping and dynamic resource management

[0060] Furthermore, the compatibility management module has intelligent group management capabilities:

[0061] When multiple inserted optical modules are detected to be from the same manufacturer and series, the compatibility management module groups them into the same adapter group. Optical modules within the group can share basic adapter parameters and driver configurations, simplifying management overhead.

[0062] When the inserted optical modules are detected to be from different manufacturers or belong to different series (such as a 10G SFP+ and a 25G SFP28), the compatibility management module classifies them into different adaptation groups. It coordinates the resource allocation and working modes among the adaptation groups. For example, based on the specifications and performance (bandwidth, power consumption) of the optical modules within each adaptation group, it dynamically allocates PCIe channel bandwidth and data buffer resources to ensure that high-performance optical modules can obtain sufficient resources and optimize the overall system throughput.

[0063] Data Stream Forwarding and Interface Virtualization

[0064] To enable parallel data transmission across multiple optical modules, the multiplexing module and virtualization driver module within the network interface controller work together:

[0065] The multiplexing module is responsible for the decomposition and aggregation of data streams. For uplink data (from the network to the host), it splits the single high-speed data stream from the NIC MAC layer into multiple sub-streams according to configuration strategies (such as round-robin or load-based), and routes them to the corresponding transmit channels of each active optical module slot through internal crossbar switches. For downlink data (from the host to the network), it performs the opposite operation, aligning and recombining the multiple sub-streams from each optical module slot, multiplexing them into a single high-speed data stream, and sending it back to the NIC controller for uploading to the host.

[0066] Virtualization driver module: At the operating system level, this module virtualizes a physical network interface card (NIC) into multiple independent network interface devices (e.g., eth0, eth1, eth2, etc.). Each virtual network interface (VF) is directly bound to an active optical module slot on the multi-channel interface module. Thus, in the operating system or virtual machine monitor, each optical module logically appears as if connected to an independent NIC, allowing for independent configuration of IP addresses, VLANs, load balancing policies, etc., greatly enhancing system flexibility and manageability.

[0067] Independent port adaptation management

[0068] To ensure the accuracy and isolation of the adaptation process, the compatibility management module maintains an independent port information structure for each active optical module slot at the driver layer. This port information structure includes the port's original identity information, replacement identity information, current adaptation status, and runtime statistical parameters. This information is stored independently in the structures of different ports and does not interfere with each other. The adaptation operation only modifies the structure content corresponding to the current port and does not affect the adaptation status of other ports, thus preventing mutual interference between different optical module adaptation operations at the mechanism level. The identity adaptation operation is executed completely independently based on this port information.

[0069] Each I2C read / write operation carries the target port number. The compatibility management module associates the request with the corresponding port information (i.e., port information) based on the port number.

[0070] When querying the compatibility mapping table, the key used is "NIC controller identifier + port information + actual optical module identity" to ensure that even if two slots are filled with the same type of optical module, independent adaptation management can be performed (for example, assigning them different virtual MAC addresses).

[0071] Construction and sharing of compatibility mapping tables

[0072] The compatibility mapping table is a critical data structure. In one embodiment, it can be shared by compatibility management instances on multiple ports, existing as a read-only resource in a specific memory region of the kernel or firmware. The compatibility management module must ensure that concurrent query operations from different ports are idempotent and consistent, preventing data corruption due to concurrent access.

[0073] In another preferred embodiment, the compatibility mapping table can be dynamically generated by the compatibility management module:

[0074] Step S2-1: Enumeration and Identification. When the system starts, the compatibility management module first enumerates and identifies the manufacturer's identifier and hardware version number of the current network interface controller.

[0075] Step S2-2: Load entries. Based on the identified identifiers, load all compatibility entries related to the network interface controller from the system's pre-stored global compatibility database or downloaded from a remote server.

[0076] Step S2-3: Generate runtime table. A runtime mapping table for the current hardware environment is generated in memory. This table contains core mapping relationships such as "original optical module manufacturer identifier -> replacement manufacturer identifier" for quick lookup during identity adaptation operations.

[0077] To handle new optical module models or models not recorded in the mapping table, the compatibility management module has compatibility learning capabilities. When such an optical module is detected being inserted, the following process will be triggered:

[0078] Step L1: Information Reading and Recording. First, securely read and record the identity information, basic performance parameters, and communication protocol version of the new optical module model via the I2C interface.

[0079] Step L2: Compatibility Verification and Initial Learning. The above information is compared with the network interface card (NIC) controller's hardware specifications to verify basic communication protocol compatibility. If the basic protocols (such as modulation scheme and rate class) are compatible, the system will attempt to interact with the optical module using the most conservative parameters (such as default power consumption and basic equalization settings) and automatically generate a set of temporary adaptation parameters. These parameters are added to a temporary extension area of ​​the compatibility mapping table, allowing the optical module to enter "trial" operating mode. Simultaneously, the system sends a model registration and certification request to the global compatibility database backend.

[0080] Step L3: Intelligent Matching and Strategy Generation. Simultaneously, the system compares and analyzes the specifications of the new optical module with the massive amount of optical module information already recorded in the compatibility mapping table (e.g., comparing wavelength, transmission distance, power consumption, supported diagnostic functions, etc.). Based on the comparison results, the system matches one or more known optical module models with the most similar specifications. Then, using the mature compatibility solution corresponding to the known model as a foundation, an initial adaptation strategy is generated and applied for the new optical module.

[0081] Step L4: Monitoring and Consolidation. After adopting temporary adaptation parameters or an initial adaptation strategy, the compatibility management module will monitor the fluctuations of key performance indicators (such as bit error rate (BER), received optical power, and transmit bias current) within a preset time period (e.g., 5-10 minutes). Specific reference values ​​for the preset threshold range include received optical power between -15dBm and 0dBm, transmit bias current between 10mA and 100mA, and a BER not exceeding [a certain value]. If all the above key indicators remain stable within the corresponding preset threshold range, the temporarily generated adaptation parameters will be fixed into the local runtime compatibility mapping table, completing the compatibility learning of the new optical module model.

[0082] Step L5: Policy Validity Determination. If all key performance indicators remain stable within the preset security threshold range, the current adaptation policy is deemed valid, and the optical module is considered to be working stably. At this point, if a model certification approval receipt has been received from the global database, the system will update the temporary adaptation parameters or the verified valid initial policy into a formal compatibility entry and solidify it into the local compatibility mapping table. Afterward, when this model of optical module is inserted again, it can be directly recognized and driven normally. If the performance indicators are unstable, the system will mark the optical module as "incompatible," isolate it to prevent it from affecting other ports, and record detailed logs for administrator analysis.

[0083] In summary, this invention constructs an intelligent, flexible, and scalable multi-optical module parallel access solution through the collaboration of a network interface card controller and its built-in compatibility management module, multiplexing module, and virtualization driver module. It not only solves the identity compatibility problem when multiple optical modules operate in parallel, but also achieves full utilization of hardware resources and optimization of system performance through virtualization and dynamic resource management. Furthermore, its self-learning capability ensures forward compatibility with future new optical module models, significantly reducing data center operation and maintenance costs and upgrade complexity.

[0084] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

[0085] The embodiments and functional operations of the subject matter described in this specification can be implemented in the following ways: digital electronic circuits, tangibly implemented computer software or firmware, computer hardware, including the structures disclosed in this specification and their equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on one or more tangible non-transitory program carriers, for execution by a data processing device or to control the operation of the data processing device.

[0086] Alternatively or additionally, program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are then generated as coded information to be transmitted to an appropriate receiver device executed by data processing equipment. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or one or more combinations of the above.

[0087] The processing and logic flows described in this specification can be executed by one or more programmable computers, which execute one or more computer programs by processing input data and generating output to run functions. The processing and logic flows can also be executed by special-purpose logic circuitry, such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as special-purpose logic circuitry.

[0088] To transmit interactions with a user, embodiments of the subject matter described in this specification can be implemented on a computer having: a display device, such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user; and a keyboard and a positioning device, such as a mouse or trackball, which the user can use to send input to the computer. Other types of devices can also be used to transmit interactions with the user; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including sound input, voice input, or tactile input. Additionally, the computer can interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a webpage to a web browser on the user's client device in response to a received request from a web browser.

[0089] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather as descriptions of features that can embody specific embodiments of a particular invention. Specific features described in this specification within the context of an independent embodiment may also be implemented in combination with a single embodiment. Conversely, various features described within the context of a single embodiment may also be implemented independently in multiple embodiments, or in any suitable sub-combination. Furthermore, while features may be described for combination and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and the claimed combination may be redirected to a sub-combination or a variation thereof.

[0090] Similarly, although operations are described in the accompanying drawings in a specific order, it should not be construed as requiring that such operations be performed in the specific order shown or in sequential order, or that all illustrated operations be performed, in order to achieve the desired result. In certain cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that program components and systems can generally be integrated into a single software product or packaged into multiple software products.

[0091] Specific implementations of the subject matter have been described. Other implementations are within the scope of the following claims. For example, the activities described in the claims can be performed in a different order and still achieve the desired result. As an example, the processes described in the drawings do not necessarily require a specific order or sequence to be shown in order to achieve the desired result. In certain implementations, multitasking and parallel processing may be advantageous.

Claims

1. A system supporting parallel access of multiple optical modules, comprising a network interface card (NIC), characterized in that, Also includes: A multi-channel interface module, which is connected to the network card, and the multi-channel interface module is provided with at least two optical module slots; A network interface card (NIC) controller is connected to the NIC and the multi-channel interface module, and is used to control the data transmission of the NIC and coordinate the working status of each optical module slot in the multi-channel interface module. The network interface controller includes a compatibility management module, configured to: when an optical module is detected inserted into the optical module slot, perform an identity adaptation operation independently for each optical module slot in the working state. The identity adaptation operation includes: intercepting the read request for the identity identification area of ​​the optical module, obtaining the actual identity information returned by the optical module, querying the compatibility mapping table to obtain the corresponding replacement identity information, and returning the replacement identity information to replace the actual identity information.

2. The system supporting parallel access of multiple optical modules according to claim 1, characterized in that, The compatibility management module is also configured as follows: When the inserted optical modules are detected to be from the same manufacturer and series of products, the compatibility management module classifies them into the same adaptation group and shares the basic adaptation parameters. When the inserted optical modules are detected to be from different manufacturers or different product series, the compatibility management module classifies them into different adaptation groups, coordinates the resource allocation and working mode between each adaptation group, and dynamically allocates data bandwidth according to the specifications and performance of the optical modules in each adaptation group.

3. The system supporting parallel access of multiple optical modules according to claim 1, characterized in that, The network interface controller also includes: The multiplexing module is used to split the uplink data stream from the network card into multiple sub-streams and route them to each active optical module slot, and to multiplex the sub-streams from each optical module slot into a downlink data stream and send it back to the network card controller. The virtualization driver module virtualizes the network card into multiple independent network interface devices, which are then bound to each active optical module slot.

4. A system supporting parallel access of multiple optical modules according to claim 1, characterized in that, The compatibility management module maintains an independent port information structure for each active optical module slot at the driver layer; The identity adaptation operation is performed independently based on the port information structure, and includes: Based on the target port number carried in the I2C read command, the request is associated with the corresponding port information structure; Using the current network interface controller's identifier and the port information structure, independently query the compatibility mapping table to obtain the replacement identity information specific to that port and then replace it; The original identity information, replacement identity information, and adaptation status of each port are maintained independently in the corresponding port information structure.

5. A system supporting parallel access of multiple optical modules according to claim 4, characterized in that, The compatibility management module maintains the compatibility mapping table, which is a read-only resource shared by multiple ports. The compatibility management module ensures that concurrent query operations on the compatibility mapping table from different ports are idempotent and consistent.

6. A system supporting parallel access of multiple optical modules according to claim 5, characterized in that, The compatibility mapping table is dynamically generated by the compatibility management module, and the generation process includes: Enumerate and identify the manufacturer identifier of the network interface controller; Based on the identified manufacturer identifier, the corresponding compatibility entry is loaded from a pre-stored global compatibility database. Based on the loaded compatibility entries, a runtime mapping table is generated, which contains the mapping relationship between the network card manufacturer identifier, the original optical module manufacturer identifier, and the replacement manufacturer identifier.

7. A system supporting parallel access of multiple optical modules according to claim 6, characterized in that, When the inserted optical module is a new model or a new model not recorded in the global compatibility database, the compatibility management module will trigger a compatibility learning process: Obtain the identity information, performance parameters, and communication protocol version of the optical module. The above information is matched with the hardware specifications of the network interface card controller. If the basic communication protocol is compatible, temporary adaptation parameters are automatically generated and added to the temporary extension area of ​​the compatibility mapping table. At the same time, a model registration request is sent to the global compatibility database. After the database completes the model authentication, the temporary adaptation parameters are updated to formal entries and fixed to the compatibility mapping table.

8. The system according to claim 7, characterized in that, The compatibility learning process also includes: Read and record the specifications of the new optical module model; The specifications of the new optical module are compared and analyzed with the optical module information already recorded in the compatibility mapping table; Based on the comparative analysis results, match one or more known optical module models with the most similar specifications from the compatibility mapping table; Using the compatibility scheme corresponding to the known optical module model as a basis, an initial adaptation strategy is generated and applied for the new optical module model.

9. A system supporting parallel access of multiple optical modules according to claim 8, characterized in that, The compatibility learning process also includes: after adopting the initial adaptation strategy, monitoring the fluctuation of key performance indicators within a preset time period; if the key performance indicators are all stable within the preset threshold range, the initial adaptation strategy is determined to be effective, and the adaptation parameters of the new optical module are formally added to the compatibility mapping table.

10. A system supporting parallel access of multiple optical modules according to claim 9, characterized in that, The key performance indicators include the bit error rate.

Images