Method for realizing common software of switch product in same-chip scheme

Abstract

The invention provides a method for realizing common software of a switch product in a same-chip scheme. The method comprises the following steps of: 1, defining one or more hardware configuration files according to different hardware specifications; and step 2, when the switch is started, the system reads a boot environment configuration file, and the boot environment configuration file automatically loads a corresponding hardware configuration file. Through the shared software framework and the dynamic link library mechanism, software updating can be carried out on multiple types of products at a time, repeated operation is greatly reduced, updating efficiency is improved, and time and labor cost is reduced; a unified software framework and an online upgrading mechanism enable the publishing process to be more concise and efficient, so that repeated work is reduced, and the publishing complexity is reduced; software sharing is achieved, the number of software versions is reduced, the maintenance cost is reduced, the flexibility of fault processing and version rollback is improved through a continuous monitoring and online upgrading mechanism, and the efficiency and flexibility of the whole production process are enhanced.

Description

Technical Field

[0001] The present invention relates to the technical field of switches, and in particular to a method for implementing common software for switch products with the same chip solution. Background Art

[0002] In the current switch technology field, there is a common phenomenon: each switch product is equipped with exclusive software, and the software of different products cannot be used interchangeably. This means that even if they are switch products of the same series, if they have differences in hardware specifications, such as different numbers of ports (such as 16 ports, 24 ports), different bus specifications (such as different data transmission rates and bandwidths), or inconsistent media types (such as electrical ports, optical ports), they all have independent software versions. This traditional model of one product corresponding to one software has brought many significant problems;

[0003] First, when it comes to software updates, since the software of each product needs to be handled separately, developers have to perform independent update operations for each software, which is a lot of repetitive work. Moreover, after the update, in order to ensure the stability and functional integrity of the software, each software needs to be verified and tested one by one. This not only consumes a lot of time and human resources, but also easily leads to insufficient verification of certain software versions due to human negligence, thus introducing potential risks;

[0004] Secondly, in the software release phase, it is also necessary to formulate a release plan for each software, prepare release documents, and conduct post-release tracking and support. This repetitive work greatly increases the complexity of the release process and reduces work efficiency;

[0005] In addition, since each product has its own specific software version, the number of software versions will increase dramatically as the number of product types increases. This has caused great trouble to production management. At the same time, too many software versions have also increased maintenance costs, making it more difficult to deal with software failures or version rollbacks, reducing the efficiency and flexibility of the entire production process;

[0006] Therefore, a method for realizing shared software for switch products with the same chip solution is proposed. Summary of the invention

[0007] In view of this, the embodiments of the present invention hope to provide a method for implementing common software for switch products with the same chip solution, so as to solve or alleviate the technical problems existing in the prior art and at least provide a beneficial option.

[0008] In order to solve the above technical problems, a technical solution adopted by the present application is: a method for implementing common software for switch products with the same chip solution, comprising the following steps:

[0009] Step 1: Define one or more hardware profiles according to different hardware specifications;

[0010] Step 2: When the switch starts, the system reads a boot environment configuration file, and the boot environment configuration file automatically loads the corresponding hardware configuration file;

[0011] Step 3: Automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment configuration file;

[0012] Step 4: interacting with the operating system through a shared software framework based on the loaded dynamic link library;

[0013] Step 5: Based on the support of the software framework, the dynamic link library executes its software functions and decouples from the hardware configuration, and at the same time, performs functional verification;

[0014] Step 6: After the switch is started, the system continuously monitors the hardware status, network connection status, software function execution and performance indicators;

[0015] Step 7: The system provides an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through the remote interface while the switch is running.

[0016] As a further preferred embodiment of the present technical solution, in step one, the hardware configuration file includes hardware configuration information corresponding to specific hardware specifications, and the hardware configuration information includes the number of ports, port rate, memory size and special hardware feature identifiers.

[0017] As a further preferred embodiment of the present technical solution, in step 2, the boot environment configuration file includes instructions for selecting a hardware configuration file and system startup control parameters.

[0018] As a further preferred embodiment of the present technical solution, in step three, the dynamic link library includes software functions implemented for the hardware configuration file, and the software functions include port management, data packet forwarding and routing decision.

[0019] As a further preferred embodiment of the present technical solution, in step 4, the software framework provides a unified interface to support communication and collaboration between different dynamic link libraries, and the software framework supports dynamic loading and unloading of dynamic link libraries.

[0020] As a further preferred embodiment of the present technical solution, in step five, the functional verification includes a port management function test, a data packet forwarding function test, a routing decision function test and an overall system performance test.

[0021] As a further preferred embodiment of the present technical solution, in step six, the hardware status includes temperature, voltage, and fan speed; the network connection status includes real-time statistics and analysis of network traffic; the software function execution status includes resource occupancy of each functional module; and the performance indicators include throughput, latency, and packet loss rate of the switch.

[0022] As a further preferred embodiment of the present technical solution, in step seven, the online upgrade mechanism includes a version compatibility check function and a rollback function. The online upgrade mechanism automatically backs up the current hardware configuration file, dynamic link library and software framework before upgrading. If a problem occurs in the new version of the hardware configuration file, dynamic link library or software framework, it automatically or manually rolls back to the previous stable version.

[0023] As a further preferred embodiment of the present technical solution, the boot environment configuration file also includes security verification information for verifying the integrity and source legitimacy of the hardware configuration file before loading it.

[0024] As a further preferred embodiment of the present technical solution, the software framework also supports plug-in expansion, allowing third-party developers to develop new functional modules based on open API interfaces and integrate them into the system as dynamic link libraries.

[0025] To solve the above technical problems, another technical solution adopted by the present application is: a common software system is realized for a switch product with the same chip solution, including a hardware configuration module, a boot environment module, a dynamic link library management module, a software framework module, a function verification module, a monitoring module and an online upgrade module;

[0026] The hardware configuration module is used to generate one or more hardware configuration files according to different hardware specifications, wherein the hardware configuration files include hardware configuration information corresponding to specific hardware specifications, such as the number of ports, port speed, memory size, and special hardware feature identifiers;

[0027] The boot environment module is used to read a boot environment configuration file, wherein the boot environment configuration file includes instructions for selecting a hardware configuration file and system startup control parameters, as well as security verification information;

[0028] The dynamic link library management module is used to automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment module, and the dynamic link library includes port management, data packet forwarding and routing decision functions implemented for the hardware configuration file;

[0029] The software framework module is used to provide a unified interface, support communication and collaboration between different dynamic link libraries, and interact with the operating system to provide a software operating environment for the entire system;

[0030] The function verification module is used to verify the software functions of the system, including port management function test, data packet forwarding function test, routing decision function test and overall system performance test;

[0031] The monitoring module is used to continuously monitor the hardware status, network connection status, software function execution and performance indicators;

[0032] The online upgrade module is used to provide an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through a remote interface while the switch is running.

[0033] The embodiment of the present invention has the following advantages due to the adoption of the above technical solution:

[0034] 1. The present invention uses a shared software framework and dynamic link library mechanism to achieve a one-time software update for multiple products, greatly reducing repeated operations, improving update efficiency, and reducing time and labor costs;

[0035] 2. The present invention makes the publishing process more concise and efficient, reduces repetitive work, and reduces the complexity of publishing through a unified software framework and online upgrade mechanism;

[0036] 3. The present invention reduces the number of software versions and reduces maintenance costs by achieving software sharing. At the same time, through continuous monitoring and online upgrade mechanisms, it improves the flexibility of handling faults and version rollbacks, thereby enhancing the efficiency and flexibility of the entire production process.

[0037] The above summary is for illustrative purposes only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments and features described above, further aspects, embodiments and features of the present invention will be readily apparent by reference to the accompanying drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or technical descriptions will be briefly introduced below. 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 paying creative work.

[0039] Figure 1 A schematic diagram of a flow chart of a method for implementing a common software for a switch product with a same chip solution according to the present invention;

[0040] Figure 2 The present invention is a schematic diagram of the functional modules of a switch product with the same chip solution to realize a common software system. DETAILED DESCRIPTION

[0041] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0042] It should be clear that the following embodiments of the present disclosure are described by specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other in the absence of conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0043] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.

[0044] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The drawings only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0045] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0046] Figure 1 1 is a flowchart of a method for implementing a common software method for a switch product with the same chip solution according to an embodiment of the present invention. It should be noted that if there are substantially the same results, the method of the present application is not limited to the method of the same chip solution. Figure 1 The process sequence shown is limited. Figure 1As shown: A method for implementing common software for switch products with the same chip solution, comprising the following steps:

[0047] Step 1: Define one or more hardware configuration files according to different hardware specifications. Specifically, for example, for a switch product with 24 ports, Gigabit Ethernet bus specifications, and copper cable media, create a corresponding hardware configuration file hw_profile_24port.txt. The file contains hardware configuration information, such as the number of ports is 24, the port rate is Gigabit, the memory size is a specific value, and the special hardware feature identifier. At the same time, for another switch product with a different number of ports and features, a corresponding hardware configuration file is also created.

[0048] Step 2: When the switch starts, the system reads a boot environment configuration file boot_env.txt, which automatically loads the corresponding hardware configuration file. Specifically, the boot environment configuration file boot_env.txt contains instructions for selecting hardware configuration files and system startup control parameters. For example, the variable boardmode l in the boot environment configuration file boot_env.txt can specify the name of the hardware configuration file to be loaded. If the value of boardmode l is 24port_mode l, the system will automatically load the hw_profile_24port.txt hardware configuration file.

[0049] Step 3: Automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment configuration file; specifically, the dynamic link library is made of hardware-related interfaces, and when loaded, it will read the variable boardmode l in the boot environment configuration file boot_env.txt to determine the specification description at the software level. For example, if the hw_profile_24port.txt hardware configuration file is loaded, the corresponding dynamic link library lib24port.dll will be loaded, which implements software functions for specific hardware configurations, including port management, data packet forwarding, and routing decisions.

[0050] Step 4: The loaded dynamic link library interacts with the operating system through a shared software framework; specifically, the software framework provides a unified interface to support communication and collaboration between different dynamic link libraries. For example, when an application needs to perform a data packet forwarding operation, the corresponding dynamic link library function can be called through the software framework. At the same time, the software framework supports dynamic loading and unloading of dynamic link libraries, so that specific hardware function modules can be updated or replaced as needed during system operation.

[0051] Step 5: Based on the support of the software framework, the dynamic link library executes its software functions and decouples from the hardware configuration to ensure the independence and maintainability of the software functions. At the same time, functional verification is performed; specifically, functional verification includes port management function testing, data packet forwarding function testing, routing decision function testing, and overall system performance testing. For example, by sending specific test data packets to verify whether the data packet forwarding function is correct, check whether the port status is normal, etc.

[0052] Step 6: After the switch is started, the system continuously monitors the hardware status, network connection status, software function execution and performance indicators;

[0053] Step 7: The system provides an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through the remote interface while the switch is running.

[0054] When the product is manufactured, the product name, MAC address, and serial number are configured through the parameters of the boot environment configuration file. For example, specific variables are set in boot_env.txt to specify information such as the product name, MAC address range, and starting value of the serial number. This ensures that each switch product has a unique identification and configuration.

[0055] In one embodiment, specifically, in step 1, the hardware configuration file includes hardware configuration information corresponding to specific hardware specifications, and the hardware configuration information includes the number of ports, port speed, memory size, and special hardware feature identifiers. The hardware configuration file is an important component of the same chip solution switch product to implement the common software method. It contains detailed configuration information corresponding to specific hardware specifications, and provides important support and guarantee for the startup, operation, and software function implementation of the switch;

[0056] The port quantity information indicates the total number of physical ports supported by the switch. Different models of switches may have different numbers of ports depending on the application scenarios and design requirements. For example, an entry-level switch may have only 8 ports, while an enterprise-level switch may have 48 ports or more.

[0057] Port rate refers to the data transmission rate that the switch port can support. With the development of network technology, the port rate is also constantly improving, from the early 10Mbps, 100Mbps to today's 1Gbps, 10Gbps, and even higher. The maximum rate supported by each port or port group will be clearly listed in the hardware configuration file;

[0058] Memory size is a key resource for the switch to process and store data. The hardware configuration file records the total memory capacity of the switch, which helps the software to properly allocate and manage memory resources during operation. For high-performance switches, sufficient memory capacity is an important factor to ensure its processing capability and stability.

[0059] Special hardware feature identifiers include but are not limited to: support for specific types of network protocols (such as IPv6, MPLS, etc.), specific security functions (such as hardware-level encryption and decryption, firewall, etc.), support for specific expansion modules (such as fiber optic interface modules, wireless access modules, etc.). The existence of these special hardware features enables the switch to meet more diverse network requirements and application scenarios.

[0060] In one embodiment, specifically, in step 2, the boot environment configuration file includes instructions for selecting a hardware configuration file and system startup control parameters, wherein the core part of the boot environment configuration file is the instructions for selecting the hardware configuration file, and these instructions usually specify the path or name of the hardware configuration file through variables or specific identifiers. For example, an environment variable hw_config_pata can be used to store the complete path of the hardware configuration file, or all possible hardware configuration file options can be directly listed in the configuration file, and one of them can be selected through a flag or configuration item. When the switch is started, the boot environment will read these instructions, and find and load the corresponding hardware configuration file according to their instructions, so that the system can configure and initialize hardware resources according to the specifications and characteristics of the current hardware; in addition to the instructions for selecting the hardware configuration file, the boot environment configuration file also contains a series of control parameters required for system startup, which include startup timeout, startup sequence, security verification settings, debugging and logging, etc.

[0061] In one embodiment, specifically, in step 3, the dynamic link library includes software functions implemented for the hardware configuration file, and the software functions include port management, data packet forwarding, and routing decision-making, wherein port management is an important part of the switch software function, and the port management module in the dynamic link library is responsible for initializing, configuring, monitoring, and maintaining the physical ports of the switch, including opening and closing the ports, setting the speed and mode, and detecting and recovering the errors of the ports, etc. By reading the information such as the number of ports and the speed in the hardware configuration file, the port management module can ensure that each port can operate according to the predetermined specifications and parameters;

[0062] Packet forwarding is one of the basic functions of a switch. The packet forwarding module in the dynamic link library is responsible for receiving packets from ports and forwarding them to the target port or next-hop device based on the results of network protocols and routing decisions. During this process, the module uses the memory and cache resources of the switch to optimize forwarding performance and ensure the integrity and correctness of the packet.

[0063] Routing decision is the key to the correct transmission of data packets in a complex network environment. The routing decision module in the dynamic link library will make forwarding decisions based on network topology, routing table, protocol type and other information. By reading special hardware feature identifiers in the hardware configuration file (such as whether a specific routing protocol is supported), the routing decision module can flexibly adapt to different network environments and application requirements.

[0064] In one embodiment, specifically, in step 4, the software framework provides a unified interface to support communication and collaboration between different dynamic link libraries. Through the unified interface, different dynamic link libraries can easily exchange and share data. For example, a dll responsible for port management can provide port status information to a dll responsible for data packet forwarding through the interface to ensure that the data packet can be correctly forwarded to the target port. The software framework integrates the functions of each dynamic link library to form a complete switch software system. This integration not only improves the overall performance of the system, but also enables the system to flexibly respond to different network environments and application requirements;

[0065] The software framework supports dynamic loading and unloading of dynamic link libraries. By supporting dynamic loading, the software framework allows users to flexibly add or delete functional modules during the operation of the switch. This flexibility enables the switch system to be quickly adjusted and optimized according to actual needs. Similarly, when a dynamic link library is no longer needed, the software framework also supports unloading it from memory, which helps reduce the system burden and prevent potential resource leakage problems.

[0066] In one embodiment, specifically, in step 5, the functional verification includes a port management function test, a data packet forwarding function test, a routing decision function test, and an overall system performance test, wherein:

[0067] Port management function test, used to verify whether the port management module can correctly initialize, configure, monitor and maintain the physical ports of the switch;

[0068] Packet forwarding function test, used to verify whether the packet forwarding module can accurately and efficiently forward packets

[0069] Routing decision function test, used to verify whether the routing decision module can make correct forwarding decisions based on the network topology and routing table;

[0070] The overall system performance test is used to comprehensively evaluate the overall performance of the switch software system, including throughput, latency, concurrent processing capabilities, etc.

[0071] In one embodiment, specifically, in step six, the hardware status includes temperature, voltage, and fan speed; the network connection status includes real-time statistics and analysis of network traffic; the software function execution status includes resource usage of each functional module; the performance indicators include throughput, latency, and packet loss rate of the switch; through monitoring and evaluation of multiple aspects such as hardware status, network connection status, software function execution status, and performance indicators, the stability and efficiency of the switch during operation are ensured.

[0072] In one embodiment, specifically, in step seven, the online upgrade mechanism includes a version compatibility check function and a rollback function. The online upgrade mechanism automatically backs up the current hardware configuration file, dynamic link library and software framework before upgrading. If a problem occurs in the new version of the hardware configuration file, dynamic link library or software framework, it automatically or manually rolls back to the previous stable version. By introducing the online upgrade mechanism, the upgrade process of the switch software system becomes safer, more efficient and controllable. The version compatibility check function reduces the risks caused by version incompatibility. The automatic backup and rollback functions provide powerful recovery capabilities, ensuring that the system can be quickly restored when problems are encountered during the upgrade process. This not only improves the availability and stability of the system, but also reduces maintenance costs and time costs, providing network administrators with a more convenient and reliable upgrade experience.

[0073] In one embodiment, specifically, the boot environment configuration file also includes security verification information for verifying the integrity and source legitimacy of the hardware configuration file before loading it. The security verification information is integrated into the boot environment configuration file, which means that before the switch starts and loads the hardware configuration file, the boot environment will first perform a verification process. This design ensures that the verification process is performed in the early stages of system startup, thereby improving the overall security of the system; the verification process should be designed as an automated process to reduce human intervention and potential errors. Once the boot environment detects that the hardware configuration file needs to be loaded, it will automatically perform the verification steps and decide whether to continue loading the configuration file based on the verification results; if the verification fails (i.e., the configuration file is incomplete or the source is not legal), the boot environment should be able to handle this situation and may trigger a rollback to the last known stable state or enter recovery mode, which helps ensure that the system can maintain stability and availability in the face of potential security threats.

[0074] In one embodiment, specifically, the software framework also supports plug-in extensions, allowing third-party developers to develop new functional modules based on open API interfaces and integrate them into the system as dynamic link libraries. By supporting plug-in extensions, the software framework provides an open, flexible, and extensible development platform for third-party developers, which not only promotes technological innovation and resource sharing, but also enhances the flexibility and maintainability of the system. As the ecosystem continues to develop and improve, the system will be able to continuously expand its functions and performance to meet increasingly complex business needs and network environments.

[0075] In summary, this embodiment implements a common software architecture for a switch product with the same chip solution by defining a hardware configuration file, configuring a boot environment, loading a dynamic link library, interacting with a software framework, verifying and decoupling functions, continuously monitoring, and upgrading online. This architecture not only improves the maintainability and scalability of the product, but also ensures the correctness and stability of the software functions.

[0076] Figure 2 Schematic diagram of the functional modules of a switch product with the same chip solution to realize a common software system according to an embodiment of the present application, such as Figure 2 As shown, a switch product with the same chip solution realizes a common software system, including a hardware configuration module, a boot environment module, a dynamic link library management module, a software framework module, a function verification module, a monitoring module and an online upgrade module;

[0077] The hardware configuration module is used to generate one or more hardware configuration files according to different hardware specifications. The hardware configuration files contain hardware configuration information corresponding to specific hardware specifications, such as the number of ports, port speed, memory size, and special hardware feature identifiers. These configuration files are the basis for subsequent system startup, configuration, and function implementation, ensuring that the system can accurately identify and utilize hardware resources;

[0078] The boot environment module is used to read the boot environment configuration file, which includes instructions for selecting the hardware configuration file and system startup control parameters, as well as security verification information. The security verification information is used to ensure the integrity and source legitimacy of the hardware configuration file to prevent unauthorized tampering or replacement. The boot environment module is also responsible for loading and initializing necessary system control parameters to lay the foundation for the normal operation of the system;

[0079] The dynamic link library management module is used to automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment module. The dynamic link library includes port management, data packet forwarding and routing decision functions implemented for the hardware configuration file. The dynamic link library management module also supports loading or unloading as needed during runtime, which enhances the flexibility and scalability of the system;

[0080] The software framework module is used to provide a unified interface, support communication and collaboration between different dynamic link libraries, and interact with the operating system to provide a software operating environment for the entire system. The software framework module defines the overall architecture and interface specifications of the system, so that each functional module can work according to the predetermined protocol and process. This design improves the modularity and maintainability of the system and reduces the complexity and cost of system development;

[0081] Functional verification module, used to verify the software functions of the system, including port management function test, data packet forwarding function test, routing decision function test and overall system performance test. The functional verification module also includes automated testing tools and testing processes to improve testing efficiency and accuracy;

[0082] The monitoring module is used to continuously monitor the hardware status, network connection status, software function execution and performance indicators. The monitoring module provides real-time system status information and alarm mechanism, allowing administrators to promptly discover and deal with potential problems; the monitoring module also supports data recording and analysis functions, providing data support for system optimization and troubleshooting;

[0083] The online upgrade module is used to provide an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through the remote interface while the switch is running. This function greatly simplifies the system upgrade and maintenance process and reduces the risk of business interruption caused by downtime for upgrades. At the same time, the online upgrade module also includes version compatibility check and rollback functions to ensure the security and reliability of the upgrade process.

[0084] For other details about the technical solutions implemented by each module in the system of the above embodiment, reference may be made to the description of a lead frame quality detection method, device and apparatus in the above embodiment, which will not be repeated here.

[0085] It should be noted that each embodiment in this specification is described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other. For system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0086] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0087] In the present disclosure, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. The block diagrams of the devices, devices, equipment, and systems involved in the present disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagram. As will be appreciated by those skilled in the art, these devices, devices, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including", "comprising", "having", etc. are open words, referring to "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used here refer to the words "and / or" and can be used interchangeably with them, unless the context clearly indicates otherwise. The words "such as" used here refer to the phrase "such as but not limited to", and can be used interchangeably with them.

[0088] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0089] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0090] Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

[0091] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0092] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A method for implementing common software for switch products with the same chip solution, characterized in that: The following steps are involved: Step 1: Define one or more hardware profiles according to different hardware specifications; Step 2: When the switch starts, the system reads a boot environment configuration file, and the boot environment configuration file automatically loads the corresponding hardware configuration file; Step 3: Automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment configuration file; Step 4: interacting with the operating system through a shared software framework based on the loaded dynamic link library; Step 5: Based on the support of the software framework, the dynamic link library executes its software functions and decouples from the hardware configuration, and at the same time, performs functional verification; Step 6: After the switch is started, the system continuously monitors the hardware status, network connection status, software function execution and performance indicators; Step 7: The system provides an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through the remote interface while the switch is running.

2. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step one, the hardware configuration file includes hardware configuration information corresponding to specific hardware specifications, and the hardware configuration information includes the number of ports, port speed, memory size, and special hardware feature identifiers.

3. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step 2, the boot environment configuration file includes instructions for selecting a hardware configuration file and system startup control parameters.

4. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step three, the dynamic link library includes software functions implemented for the hardware configuration file, and the software functions include port management, data packet forwarding and routing decision.

5. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step 4, the software framework provides a unified interface to support communication and collaboration between different dynamic link libraries, and the software framework supports dynamic loading and unloading of dynamic link libraries.

6. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step five, the functional verification includes port management function test, data packet forwarding function test, routing decision function test and overall system performance test.

7. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step six, the hardware status includes temperature, voltage, and fan speed; the network connection status includes real-time statistics and analysis of network traffic; the software function execution status includes resource occupancy of each functional module; and the performance indicators include throughput, latency, and packet loss rate of the switch.

8. The method for implementing common software for switch products with the same chip solution according to claim 1, characterized in that: In step seven, the online upgrade mechanism includes a version compatibility check function and a rollback function. The online upgrade mechanism automatically backs up the current hardware configuration file, dynamic link library and software framework before upgrading. If there is a problem with the new version of the hardware configuration file, dynamic link library or software framework, it automatically or manually rolls back to the previous stable version.

9. The method for implementing common software for switch products with the same chip solution according to claim 3, characterized in that: The boot environment configuration file also includes security verification information, which is used to verify the integrity and source legitimacy of the hardware configuration file before loading it.

10. A switch product with the same chip solution implements a common software system, characterized in that: It includes hardware configuration module, boot environment module, dynamic link library management module, software framework module, function verification module, monitoring module and online upgrade module; The hardware configuration module is used to generate one or more hardware configuration files according to different hardware specifications, wherein the hardware configuration files include the number of ports, port speed, memory size, and special hardware feature identifiers and hardware configuration information corresponding to specific hardware specifications; The boot environment module is used to read a boot environment configuration file, wherein the boot environment configuration file includes instructions for selecting a hardware configuration file and system startup control parameters, as well as security verification information; The dynamic link library management module is used to automatically load the corresponding dynamic link library according to the hardware configuration file loaded by the boot environment module, and the dynamic link library includes port management, data packet forwarding and routing decision functions implemented for the hardware configuration file; The software framework module is used to provide a unified interface, support communication and collaboration between different dynamic link libraries, and interact with the operating system to provide a software operating environment for the entire system; The function verification module is used to verify the software functions of the system, including port management function test, data packet forwarding function test, routing decision function test and overall system performance test; The monitoring module is used to continuously monitor the hardware status, network connection status, software function execution and performance indicators; The online upgrade module is used to provide an online upgrade mechanism, allowing the hardware configuration file, dynamic link library or software framework to be updated through a remote interface while the switch is running.

Images