Network card equipment management system, computer equipment, method and storage medium

Abstract

The invention discloses a network card device management system, a computer device, a method and a storage medium, and relates to the technical field of network card design, the network card device management system comprises a network card device containing network card hardware and a storage device storing network card firmware of the network card device, the network card hardware and the network card firmware are isolated through the storage device, and the network card hardware and the network card firmware are separated. When the operating system of the computer equipment is started, the network card firmware is loaded from the storage equipment, and the network card does not need to be provided with Flash storage, so that the maintenance is simpler, the maintenance cost is reduced, new network protocols and functions can be supported more easily, the compatibility is high, the technical problems of poor compatibility in hardware and firmware levels, high network card cost and the like in the related technology are solved, and the user experience is improved. The technical effects of reducing the manufacturing cost, enhancing the compatibility and the like are achieved.

Description

Technical Field

[0001] The present application relates to the technical field of network card design, and in particular to a network card device management system, computer equipment, method and storage medium. Background Art

[0002] With the rapid development of data center equipment rooms, network cards (NICs), as key components for achieving network connectivity, have a direct impact on the performance and security of the entire network. However, traditional NIC management methods face significant challenges in hardware compatibility and firmware updates, including but not limited to poor compatibility and high costs. This poor compatibility is reflected in the diverse operating systems used by clients across various industries, coupled with the independent ecosystem requirements of different NIC vendors. This makes driver and firmware upgrades not only dependent on specific operating systems and kernel versions, but also increases maintenance difficulty and complexity. Furthermore, the cost of NICs continues to rise, encompassing not only direct material and manufacturing costs, but also R&D costs and other indirect expenses, ultimately passing on increased data center costs to users. Summary of the Invention

[0003] The present application provides a network card device management system, computer device, method and storage medium to at least solve the problems of poor compatibility at the hardware and firmware levels and high network card costs in related technologies.

[0004] The present application provides a network card device management system, including: a network card device, the network card device includes network card hardware; a storage device, the storage device stores network card firmware of the network card device, and the network card hardware and the network card firmware are isolated by the storage device. When the operating system of the computer device is started, the network card firmware is loaded from the storage device.

[0005] The present application also provides a computer device, including the above-mentioned network card device management system.

[0006] The present application also provides a network card device management method, which is used for the above-mentioned network card device management system, wherein the method includes the following steps: storing a first firmware file of the network card device to a storage device; when the operating system of the computer device is started, loading the network card device through the first firmware file; after entering the operating system, obtaining the driver file and the second firmware file of the network card device, and installing the driver file and the second firmware file to the operating system.

[0007] The present application also provides a network card device management method, which is used for the above-mentioned network card device management system, wherein the method includes the following steps: storing a first firmware file of the network card device to a storage device; integrating a driver file and a second firmware file of the network card device into an operating system of a computer device; when the operating system starts, loading the driver file and the second firmware file, and loading the network card device through the first firmware file.

[0008] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned network card device management methods are implemented.

[0009] Through this application, since it contains a network card hardware network card device and a storage device that stores the network card firmware of the network card device, it is possible to isolate the network card hardware and the network card firmware through the storage device. When the operating system of the computer device is started, the network card firmware is loaded from the storage device. The network card does not need to set up Flash (Flash Memory) storage, maintenance is simpler, and maintenance costs are reduced. It can also more easily support new network protocols and functions, and has high compatibility. It solves the technical problems of poor compatibility at the hardware and firmware levels and high network card costs in related technologies, and achieves technical effects such as reducing manufacturing costs and enhancing compatibility. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0011] Figure 1 A schematic diagram of the structure of a network card device management system provided according to an embodiment of the present application;

[0012] Figure 2 A general network card hardware topology diagram of the related technology provided according to one embodiment of the present application;

[0013] Figure 3 A network card hardware topology diagram showing the separation of network card hardware and firmware according to an embodiment of the present application;

[0014] Figure 4 A flowchart of installing a driver, Oprom, and Firmware in a network card device management method according to one embodiment of the present application is provided;

[0015] Figure 5 A flowchart of installing a driver, Oprom, and Firmware in another network card device management method provided in accordance with an embodiment of the present application is provided;

[0016] Figure 6 A flowchart of a network card device management method provided according to an embodiment of the present application;

[0017] Figure 7 The present invention provides a flowchart of a method for managing a network card device according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0019] It should be noted that, in the description of this application, the terms "comprises," "includes," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. The terms "first," "second," etc., in this application are used to distinguish similar objects, and are not used to describe a particular order or sequence.

[0020] Currently, in general data center implementation plans, the network cards used generally adopt a design with Flash memory. This design allows the network card to load the necessary firmware and configuration information directly from the built-in Flash memory at startup, ensuring that the device can quickly enter the working state. Flash memory not only supports instant updates of firmware and configurations to adapt to the ever-changing network environment and needs, but also, due to its non-volatile nature, ensures that all settings and data of the network card are saved even in the event of a power outage, eliminating the need for reconfiguration at each startup. This design greatly improves the reliability and flexibility of the network card, allowing data centers to more efficiently manage and maintain network equipment while reducing the risk of service interruptions due to configuration loss. In addition, the presence of Flash memory also simplifies the process of remote management and batch updates, further enhancing the operation and maintenance efficiency of the data center.

[0021] However, the current technical solution of using a network card with Flash memory in the overall server design has some known defects. First, adding Flash memory will increase the manufacturing cost of the network card, which includes not only the cost of the hardware itself, but also involves additional design and testing costs, thereby increasing the overall deployment cost. Second, as a component in an electronic device, Flash memory is one of the potential failure points. Possible damage or failure problems may cause the network card to not work properly, increasing the instability of the system. Third, from a security perspective, the data in the Flash memory is easily targeted by malicious attacks, and the data may be tampered with or replaced, posing a threat to network security. In addition, the update and maintenance of Flash memory requires specialized tools and processes, further increasing management complexity and potential security risks. These problems make it challenging for data centers to pursue an efficient, reliable and secure network environment.

[0022] In response to the defects of the above-mentioned related technologies, the embodiments of the present application propose a design solution without Flash storage for network card products with large traffic in the market. Network cards without Flash storage have certain advantages in solving technical problems. The following are some technical problems that it can solve or optimize.

[0023] Because they eliminate Flash memory, Flash-free NICs can reduce manufacturing costs, a key consideration for network devices with limited budgets or those that require large deployments. For example, firmware can be updated remotely over the network without physical access to the device. This improves network management efficiency and convenience. Traditional NICs require boot code and configuration information to be loaded from Flash memory, which can take time. Flash-free NICs can boot quickly through other methods, such as loading from external memory, thereby improving network connection responsiveness. In virtualized environments, virtual machines may require frequent network configuration changes. Flash-free NICs, without relying on fixed Flash memory to store configuration information, can adapt more flexibly to such changes. Since Flash-free NICs do not need to worry about the lifespan or damage of Flash memory, maintenance is relatively simplified, reducing maintenance costs and improving device reliability. With the continuous advancement of network technology, new network protocols and features are constantly emerging. Flash-free NICs are not limited by Flash memory capacity and performance, making it easier to support these new protocols and features.

[0024] In summary, the Flash-free network card proposed in the embodiment of the present application has certain advantages in terms of cost, flexibility, security, startup speed, adaptability to virtualized environments, simplified maintenance processes, and support for new network protocols and functions.

[0025] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0026] Specifically, Figure 1 This is a schematic diagram of the structure of a network card device management system provided by the embodiment of the present application. Figure 1 As shown, the system includes: a network card device 101, a network card hardware 102, a storage device 103 and a network card firmware 104.

[0027] Among them, the network card device 101 includes network card hardware 102; the storage device 103 stores the network card firmware 104 of the network card device 101, and the network card hardware 102 and the network card firmware 104 are isolated by the storage device 103. When the operating system of the computer device is started, the network card firmware 104 is loaded from the storage device 103. The network card device 101 is a NIC (Network Interface Card), which is used to realize the data transmission function between the computer and the network; the network card hardware 102 is the physical part of the network card device 101, including all required electronic components, but does not include firmware or drivers. It should be noted that the network card hardware 102 in the embodiment of the present application is no longer equipped with Flash memory; the network card firmware 104 is a special type of software stored in a non-volatile memory, used to control and manage the behavior of the network card hardware 102; the storage device 103 is an external storage medium that replaces the Flash memory, such as a server hard disk, SSD (Solid State Drive), etc., used to store the network card firmware 104.

[0028] It can be understood that the embodiment of the present application proposes an innovative network card architecture, in which the network card firmware 104 is stored on an independent storage device 103. When the computer starts the operating system, the required network card firmware 104 is loaded from the storage device 103. This design reduces hardware costs and achieves effective isolation between the network card hardware 102 and the network card firmware 104.

[0029] In an embodiment of the present application, the network card hardware 102 includes a circuit board, and a processor, a data converter, an expansion bus, a management bus, a serial communication bus, a physical interface and a sideband interface arranged on the circuit board, wherein the data converter is connected to the physical interface via the serial communication bus, and the processor is connected to the data converter, the expansion bus, the management bus and the sideband interface.

[0030] Among them, the circuit board is the main physical carrier of the network card, carrying all electronic components and connection lines; the processor: usually called the microcontroller or CPU (Central Processing Unit) on the NIC, is responsible for handling various tasks on the network card, such as protocol stack processing, packet filtering, etc.; the data converter is responsible for converting digital signals into analog signals or converting analog signals into digital signals for transmission through physical media; the expansion bus is a high-speed communication channel used to connect the network card with other system components; the management bus is used to manage and monitor the status and configuration of the network card, supporting remote management and diagnostic functions; the serial communication bus is an interface used to transmit data between different components; the physical interface is the interface on the network card that is actually connected to the network medium and is responsible for data transmission at the physical layer; the sideband interface is used to provide additional control or management functions, usually used in conjunction with the management bus, allowing more detailed control and status monitoring of the network card.

[0031] It can be understood that the network card hardware 102 of the embodiment of the present application is composed of a circuit board and various key components integrated thereon, including a processor, a data converter, an expansion bus, a management bus, a serial communication bus, a physical interface and a sideband interface, wherein the data converter is connected to the physical interface through the serial communication bus, and is responsible for converting the digital signal into an analog signal suitable for transmission on the physical medium. The processor serves as the core control unit of the network card, is connected to the data converter, the expansion bus, the management bus and the sideband interface, coordinates the work of each component, and handles complex network tasks, ensuring that the network card can transmit and process data efficiently and reliably, while providing powerful management and maintenance functions.

[0032] It should be noted that the network card device 101 of the embodiment of the present application no longer has a built-in traditional first memory, namely the Flash memory and its related circuits. The first memory was originally used to store the firmware of the network card device 101. After removing the Flash memory, the network card firmware 104 will be stored on the storage device 103, such as the server's hard disk, SSD or other forms of persistent storage media. When the computer starts the operating system, the network card firmware 104 will be loaded from the storage device 103 to the network card device 101, thereby realizing the effective separation of the network card hardware 102 and the firmware, reducing the number of components of the network card device 101, reducing the manufacturing cost of the network card, and improving the flexibility and security of the system, and simplifying the maintenance process.

[0033] In the embodiment of the present application, the network card firmware 104 includes a first firmware and a second firmware, wherein the first firmware is a driver for starting the network card device 101 , and the second firmware is a driver for updating the network card device 101 .

[0034] Among them, the first firmware is obtained by incorporating the Oprom (Option ROM) file into the BIOS code of the server. Its main function is to be loaded and executed by the BIOS (Basic Input / Output System) or UEFI (Unified Extensible Firmware Interface) firmware when the computer starts to initialize and configure specific hardware devices, which is used to start the driver of the network card device 101; the second firmware is Firmware, which is generally stored in the EEPROM (Electrically Erasable Programmable Read-Only Memory) or FLASH (Flash Memory) chip in the device, and can be upgraded by the user through a refresh program, and is used to update the driver of the network card device 101.

[0035] It can be understood that the network card firmware 104 in the embodiment of the present application is divided into two functional modules, the first firmware and the second firmware, which respectively undertake different tasks. Specifically, the first firmware is mainly used to support the initial startup and configuration process of the network card device 101. When the computer system is powered on, the first firmware will be loaded into the network card hardware 102 to complete the basic initialization of the network card, including the allocation of hardware resources, the configuration of registers, and the loading of the driver required for interaction with the operating system, ensuring that the network card can be correctly identified and enter a usable state before the operating system takes over; the second firmware focuses on realizing the security update function of the network card firmware 104, which can be upgraded by the user through a refresh program and is used to update the driver of the network card device 101.

[0036] In the embodiment of the present application, the storage device 103 includes a first area and a second area, wherein the first firmware is transplanted to the first area, and the second firmware is transplanted to the second area.

[0037] Among them, the first area is a designated partition or storage space in the storage device 103, which stores the first firmware and can provide the necessary initialization code when the system starts to ensure that the network card can be correctly identified and configured; the second area is another designated partition or storage space in the storage device 103, which stores the second firmware and can support the firmware security update process, allowing the network card firmware 104 to be upgraded, repaired or new functions to be added.

[0038] It can be understood that the storage device 103 of the embodiment of the present application includes two independent areas, namely the first area and the second area. The first area is used to store the first firmware, that is, the firmware responsible for the initial startup and configuration process of the network card device 101. When the computer starts, the first firmware will be loaded into the network card hardware 102 to complete the hardware initialization and docking with the operating system to ensure that the network card can work normally; the second area is used to store the second firmware, whose main function is to support secure updates of the firmware. In this way, the second firmware provides a flexible and secure mechanism to update the network card firmware 104, improves the flexibility and security of firmware management, simplifies hardware design, reduces manufacturing costs, and enhances the overall reliability of the system. By storing the firmware in different areas, these key components can be managed and updated more efficiently.

[0039] In an embodiment of the present application, a third firmware is provided in the first area, and a memory is provided in the second area, wherein the third firmware is used for startup and hardware management of the computer device.

[0040] Among them, the third firmware is BIOS, which includes a part specifically used for computer device startup and hardware management. Specifically, the BIOS code can include the first firmware and related hardware initialization code. The memory is hardware storage and can be transplanted into the second firmware.

[0041] It can be understood that the storage device in the embodiment of the present application is divided into two independent functional areas. A third firmware is also provided in the first area. The third firmware is BIOS, which includes codes for computer device startup and hardware management, such as BIOS Code. A memory is provided in the second area, into which the second firmware and related update files can be transplanted, making firmware updates more flexible. Firmware updates can be remotely deployed through the network or other means without relying on the built-in Flash memory of the network card. At the same time, the memory can be transplanted into the second firmware, providing a convenient and secure way to manage and update the network card firmware.

[0042] In the embodiment of the present application, the network card firmware 104 is installed in the form of a binary source code package.

[0043] Among them, binary source code packages refer to compiled programs or library files that can be run directly on a specific hardware platform and can be installed or updated without further compilation.

[0044] It can be understood that the embodiment of the present application installs the network card firmware 104 in the form of a binary source code package, which means that the firmware has been compiled into a machine code format suitable for a specific hardware platform. Users only need to download these binary files and use appropriate tools to install them on the network card. This method not only simplifies the firmware deployment process, but also improves the flexibility and convenience of updates, while enhancing the security and stability of the system.

[0045] In an embodiment of the present application, the firmware is installed in the form of a binary source code package, including: identifying the target requirements of the network card firmware 104, where the target requirements include installation requirements and upgrade requirements; obtaining the target file of the network card firmware 104 according to the target requirements; generating a binary source code package according to the target file, and installing or upgrading the network card firmware 104 through the binary source code package.

[0046] Among them, the target requirements may include installation requirements and upgrade requirements. Installation requirements refer to the requirements when installing the network card firmware 104 for the first time, including selecting the correct firmware version, ensuring compatibility, etc.; upgrade requirements refer to the requirements when updating the existing network card firmware 104, usually involving checking the current firmware version, downloading the new version firmware, backing up the old version, etc.; the target file is the network card firmware 104 file obtained according to the target requirements, packaged into a binary source code package, which can be directly used to install or upgrade the network card firmware 104.

[0047] It can be understood that the embodiment of the present application installs the firmware in the form of a binary source code package. First, it is necessary to identify the target requirements of the network card firmware 104, including determining the installation requirements and upgrade requirements. The installation requirements involve selecting the correct firmware version to ensure compatibility with the system and hardware; the upgrade requirements require confirming the current firmware version and deciding whether to download a new firmware version and how to back up the existing firmware, etc. Next, according to the target requirements, the corresponding target file of the network card firmware 104 is obtained. The target file is usually a compiled binary source code file. Use appropriate tools or scripts to package these target files into a binary source code package for easy distribution and installation. Finally, the network card firmware 104 is installed or upgraded through the generated binary source code package to ensure that the network card device 101 can work normally and has the latest functions and repairs.

[0048] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus the necessary general hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0049] According to the network card device management system provided in the embodiment of the present application, by containing a network card hardware network card device and a storage device that stores the network card firmware of the network card device, it is possible to isolate the network card hardware and the network card firmware through the storage device. When the operating system of the computer device is started, the network card firmware is loaded from the storage device. The network card does not need to be set up with Flash storage, maintenance is simpler, maintenance costs are reduced, and new network protocols and functions can be supported more easily. It has high compatibility, achieving the technical effect of reducing manufacturing costs and enhancing compatibility.

[0050] The network card device management method is further described below through a specific embodiment.

[0051] This embodiment mainly designs a new solution for designing network card hardware without Flash. Figure 2 As shown in the following example. Figure 2 As shown in the figure, in this topology, Flash requires separate storage. The Flash primarily stores the Oprom and firmware required for network card startup. When the NIC is powered on, the BIOS loads the Oprom and firmware. After the operating system enters, the driver takes over the NIC. The NIC Flash contains the Oprom and firmware, representing two independent storage areas.

[0052] Figure 3 This is the solution to be implemented in this embodiment, which mainly simplifies the design of the network card, removes the Flash storage from the network card design, and transplants the Oprom and Firmware into the bios code and hardware storage respectively. In this way, the firmware can be made into a binary source code package like a driver. The absence of Flash storage means that the configuration and firmware update of the network card firmware can be more flexible. Figure 2 Flash needs to be burned by a burner before leaving the factory. After leaving the factory, the firmware file in the Flash needs to be refreshed online with a separate software tool. Figure 3 In this solution, the firmware file is no longer stored in the Flash memory of the network card, but is loaded from an external storage device or the network. Therefore, the firmware update process becomes simpler and more direct, and can be implemented through standard operating system mechanisms (such as driver updates) or existing package management tools, avoiding the need to develop a separate refresh tool for each network card device. There is no need to burn the Flash with a burner before leaving the factory, and there is no need to develop a separate software tool to achieve online refresh of the firmware file after leaving the factory.

[0053] Figure 4 Implementation plan: Figure 3Based on this solution, the Oprom file can be integrated into the BIOS code of each vendor's server. The Oprom driver will automatically load at startup, and once the network card is recognized, the device will be quickly identified in the BIOS. The device can then be loaded over the network, enabling diskless operating system booting. After entering the operating system, the driver and firmware files for the device are obtained in advance and installed into the system using standard driver installation methods. Restarting the operating system quickly loads the driver and firmware.

[0054] Figure 5 Implementation plan: Figure 3 Based on this solution, the Oprom file can be integrated into the BIOS code of each vendor's server. The driver and firmware files are also integrated into the client's operating system. The client operating system automatically loads the driver and firmware upon startup, and automatically loads the network card when it recognizes it.

[0055] Through the above Figure 3-Figure 5 The technical solution of the present application achieves the following beneficial effects:

[0056] Reduced manufacturing costs: Since the Flash memory and its related circuits are omitted, the manufacturing cost of the network card will be reduced accordingly.

[0057] More efficient resource utilization: The Flash-free design enables the network card to more flexibly utilize external resources, such as the network or external storage, to store and load firmware and configuration information, thereby optimizing resource usage.

[0058] More flexible firmware updates: Flash-free network cards can update firmware to disk like drivers, improving the flexibility and convenience of updates. No burning fixtures or software are required, and firmware can be installed via a binary source code package, making upgrades and installation easier and more maintainable.

[0059] Firmware and configuration are more secure: Network cards without Flash memory have no Flash memory, so they cannot be tampered with or illegally accessed through Flash, ensuring network security.

[0060] More stable device operation: This ensures that the network card can operate stably without Flash memory, without frequent failures or restarts.

[0061] It should be noted that since there is no Flash memory, the network card's firmware needs to be stored in an external device or loaded through the network. Therefore, the network card is required to have a reliable firmware storage and loading mechanism to ensure the security and integrity of the firmware. A solution can be to use external storage, such as a hard disk, to store the firmware and load the firmware from the external storage when the network card starts.

[0062] An embodiment of the present application further provides a computer device, which includes the above-mentioned network card device management system.

[0063] Figure 6 A flow chart of a network card device management method provided in an embodiment of the present application is provided. The method is used in the above-mentioned network card device management system. Figure 6 As shown, the method includes the following steps:

[0064] In step S201, a first firmware file of a network card device is stored in a storage device.

[0065] Among them, the first firmware file refers to the key firmware file Oprom used for startup and initialization in the network card device; the first firmware file of the network card device is stored in the storage device, specifically the first firmware file is stored in the first area of the storage device, and can be integrated into the BIOS code of the third firmware in the first area.

[0066] It is understandable that the embodiment of the present application removes the Flash memory in the network card. To manage the network card, it is first necessary to store the first firmware file of the network card device originally in the Flash memory to the storage device.

[0067] In step S202, when the operating system of the computer device is started, the network card device is loaded through the first firmware file.

[0068] The network card device is loaded through the first firmware file. Specifically, the first firmware driver is automatically loaded when the operating system of the computer device is started, and the device is quickly identified in the BIOS.

[0069] It can be understood that in the embodiment of the present application, when the operating system of the computer device is started, the process of loading the network card device through the first firmware file is as follows: when the operating system of the computer device is started, the third firmware will automatically load the first firmware file stored in its BIOS code. Since the first firmware file has been integrated into the third firmware, the third firmware can quickly identify the network card device at the initial startup stage, so that the network card device can be quickly identified and configured with the help of the third firmware, thereby ensuring that the operating system of the computer device can smoothly identify and use the network card device, which not only simplifies the hardware design, but also improves the startup efficiency and reliability of the system.

[0070] In step S203, after entering the operating system, the driver file and the second firmware file of the network card device are obtained, and the driver file and the second firmware file are installed into the operating system.

[0071] Among them, the driver file is the Driver (Device Driver) file. A device driver is a special program that enables computers and devices to communicate with each other, which is equivalent to the hardware interface. The operating system of the computer device can only control the operation of the hardware device through this interface. If the driver of a device is not installed correctly, it will not work properly. The driver file and the second firmware file of the network card device can be obtained from an external storage device or downloaded through the Internet.

[0072] It can be understood that after the computer enters the operating system, the embodiment of the present application needs to obtain the driver file and the second firmware file of the network card device from an external storage device or through network download in advance, and install both into the system according to the standard installation process. Specifically, the driver file will be loaded into the operating system kernel as a bridge between the operating system and the network card device, so that the operating system can identify and control the network card device; and the second firmware file will be loaded into the network card hardware to support its functional requirements during operation. After installation, the driver and firmware can be quickly loaded by restarting the operating system. In this way, the network card device can work normally in the operating system environment and have the latest functions and repairs, which simplifies the firmware update and management process and improves the flexibility and maintainability of the system.

[0073] For descriptions of features in the embodiment corresponding to the network card device management method, reference can be made to the relevant descriptions of the embodiment corresponding to the network card device management system, which will not be repeated here.

[0074] According to the network card device management method provided in the embodiment of the present application, the first firmware file of the network card device is stored in the storage device. When the operating system of the computer device is started, the network card device is loaded through the first firmware file, and after entering the operating system, the driver file and the second firmware file of the network card device are obtained, and the driver file and the second firmware file are installed in the operating system. After installation, the driver and firmware can be quickly loaded by restarting the operating system. In this way, the network card device does not need to set up Flash storage, which reduces costs, and has the latest functions and repairs, simplifies the firmware update and management process, and improves the flexibility and maintainability of the system.

[0075] Figure 7 A flow chart of a network card device management method provided in an embodiment of the present application is provided. The method is used in the above-mentioned network card device management system. Figure 7 As shown, the method includes the following steps:

[0076] In step S301, a first firmware file of a network card device is stored in a storage device.

[0077] It is understandable that the embodiment of the present application removes the Flash memory in the network card. To manage the network card, it is first necessary to store the first firmware file of the network card device originally in the Flash memory to the storage device.

[0078] In step S302, the driver file and the second firmware file of the network card device are integrated into the operating system of the computer device.

[0079] The driver file and the second firmware file are integrated through a package management tool or a driver installation program provided by the operating system of the computer device.

[0080] It is understandable that the embodiment of the present application integrates the driver file and the second firmware file into the operating system of the computer device through a package management tool or a driver installation program provided by the operating system of the computer device.

[0081] In step S303, when the operating system is started, the driver file and the second firmware file are loaded, and the network card device is loaded through the first firmware file.

[0082] It can be understood that in the embodiment of the present application, when the operating system of the computer device is started, the driver file and the second firmware file will be automatically loaded and applied, thereby realizing rapid loading of the driver and firmware, and by loading the first firmware file, the network card device is quickly identified in the BIOS, thereby realizing rapid identification and loading of the network card device, simplifying the deployment process of the firmware and driver, and improving the flexibility and maintainability of the system, ensuring that the network card device can operate efficiently in the operating system environment.

[0083] For descriptions of features in the embodiment corresponding to the network card device management method, reference can be made to the relevant descriptions of the embodiment corresponding to the network card device management system, which will not be repeated here.

[0084] According to the network card device management method provided in the embodiment of the present application, by storing the first firmware file of the network card device in a storage device, the driver file and the second firmware file of the network card device are integrated into the operating system of the computer device, so that when the operating system starts, the driver file and the second firmware file are loaded, and the network card device is loaded through the first firmware file. In this way, the network card device does not need to set up Flash storage, which reduces costs, and has the latest functions and repairs, simplifies the firmware update and management process, and improves the flexibility and maintainability of the system.

[0085] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above-mentioned network card device management method embodiments when running.

[0086] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0087] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any of the above-mentioned network card device management method embodiments are implemented.

[0088] An embodiment of the present application also provides another computer program product, including a non-volatile computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps in any of the above-mentioned network card device management method embodiments.

[0089] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0090] The above describes in detail a network card device management system, computer device, method, and storage medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only intended to help understand the method and core concept of the present application. It should be noted that, for those skilled in the art, without departing from the principles of the present application, several improvements and modifications may be made to the present application, and such improvements and modifications also fall within the scope of protection of the claims of the present application.

Claims

1. A network card device management system, characterized in that: include: A network card device, wherein the network card device includes network card hardware; A storage device stores the network card firmware of the network card device, isolates the network card hardware and the network card firmware through the storage device, and loads the network card firmware from the storage device when the operating system of the computer device is started.

2. The network card device management system according to claim 1, wherein: The network card hardware includes a circuit board, and a processor, a data converter, an expansion bus, a management bus, a serial communication bus, a physical interface and a sideband interface arranged on the circuit board, wherein the data converter is connected to the physical interface via the serial communication bus, and the processor is connected to the data converter, the expansion bus, the management bus and the sideband interface.

3. The network card device management system according to claim 1 or 2, characterized in that: The network card firmware includes a first firmware and a second firmware, wherein the first firmware is used to start the driver of the network card device, and the second firmware is used to update the driver of the network card device.

4. The network card device management system according to claim 3, characterized in that: The storage device includes a first area and a second area, wherein the first firmware is transplanted into the first area, and the second firmware is transplanted into the second area.

5. The network card device management system according to claim 4, characterized in that: A third firmware is provided in the first area, and a memory is provided in the second area, wherein the third firmware is used for starting and hardware management of the computer device.

6. The network card device management system according to claim 1, characterized in that: The network card firmware is installed in the form of a binary source code package.

7. A computer device, characterized in that: The network card device management system includes any one of claims 1-6.

8. A network card device management method, characterized in that: The method is used in the network card device management system according to any one of claims 1 to 6, wherein the method comprises the following steps: Storing the first firmware file of the network card device in the storage device; When the operating system of the computer device is started, the network card device is loaded through the first firmware file; After entering the operating system, a driver file and a second firmware file of the network card device are obtained, and the driver file and the second firmware file are installed in the operating system.

9. A network card device management method, characterized in that: The method is used in the network card device management system according to any one of claims 1 to 6, wherein the method comprises the following steps: Storing the first firmware file of the network card device in the storage device; Integrating the driver file and the second firmware file of the network card device into the operating system of the computer device; When the operating system is started, the driver file and the second firmware file are loaded, and the network card device is loaded through the first firmware file.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the network card device management method according to claim 8 or 9.

Images