MCTP message transmission method, and device, storage medium and program product
By carrying the bus type identifier in the MCTP message, the limitation of the same bus type between different device nodes is resolved, enabling message transmission across bus types and expanding the application scope of the MCTP protocol.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- ZTE CORP
- Filing Date
- 2026-01-13
- Publication Date
- 2026-07-30
AI Technical Summary
In existing technologies, the transmission of MCTP messages between different device nodes requires that the bus type be the same, which limits the application scenarios of the MCTP protocol.
By carrying the transport bus type identifier in the MCTP message, the appropriate bus can be selected from multiple candidate transport buses for message forwarding, thus enabling message transmission across bus types.
This expands the application scenarios of the MCTP protocol, enabling flexible communication between device nodes of different bus types.
Smart Images
Figure CN2026072194_30072026_PF_FP_ABST
Abstract
Description
MCTP message transmission methods, devices, storage media, and program products
[0001] Cross-references to related applications
[0002] This application is based on and claims priority to Chinese Patent Application No. 202510099656.1, filed on January 21, 2025, the entire contents of which are incorporated herein by reference. Technical Field
[0003] This application relates to the field of communication equipment technology, and in particular to a method, device, storage medium and program product for transmitting MCTP messages. Background Technology
[0004] The Management Component Transport Protocol (MCTP) is a protocol used to transmit management information in computer systems. It is highly flexible and scalable, and can be used for communication between different device nodes (including at least one of controllers and devices). The transmission of MCTP messages between different device nodes can be implemented through buses such as Peripheral Component Interconnect Express (PCIe), Inter-Integrated Circuit (I2C), Improved Inter-Integrated Circuit (I3C), and Universal Asynchronous Receiver-Transmitter (UART).
[0005] However, in related technologies, the transmission of MCTP messages between different device nodes requires that the bus types of the different device nodes be the same, which limits the application scenarios of the MCTP protocol. Summary of the Invention
[0006] This application provides a method, device, storage medium, and program product for transmitting MCTP messages.
[0007] In a first aspect, embodiments of this application provide a method for transmitting MCTP messages, comprising: receiving a Management Component Transport Protocol (MCTP) message to be transmitted transmitted by a first device node, the MCTP message to be transmitted including a transmission bus type identifier; determining a first transmission bus among multiple candidate transmission buses based on the transmission bus type identifier; and forwarding the MCTP message to be transmitted through the first transmission bus.
[0008] Secondly, embodiments of this application provide a communication device, including: one or more processors; and a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement, for example, the MCTP message transmission method of the first or second aspect.
[0009] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements, for example, the MCTP message transmission method of the first or second aspect.
[0010] Fourthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements, for example, the MCTP message transmission method of the first or second aspect. Attached Figure Description
[0011] Figure 1 is a schematic diagram of the MCTP communication system provided in this application;
[0012] Figure 2 is a flowchart illustrating an embodiment of the MCTP message transmission method provided in this application;
[0013] Figure 3 is a schematic diagram of the MCTP protocol provided in this application;
[0014] Figure 4 is a schematic diagram of the MCTP message transmission process provided in this application;
[0015] Figure 5 is a schematic diagram of the transmission process of MCTP messages and response messages provided in this application;
[0016] Figure 6 is a structural schematic diagram of an embodiment of the communication device provided in this application. Detailed Implementation
[0017] To enable those skilled in the art to better understand the technical solutions of this application, the technical solutions provided in this application will be described in detail below with reference to the accompanying drawings.
[0018] Exemplary embodiments will be described more fully below with reference to the accompanying drawings; however, the described exemplary embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this application will be thorough and complete, and will enable those skilled in the art to fully understand the scope of this application.
[0019] As used herein, the term “and / or” includes any and all combinations of one or more related enumerated entries.
[0020] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application. As used herein, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that when the terms “comprising” and / or “made of” are used in this specification, the presence of a feature, integral, step, operation, element, and / or component is specified, but the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof is not excluded.
[0021] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.
[0022] Unless otherwise specified, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in common dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this application, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in the embodiments of this application.
[0023] In related technologies, the transmission of MCTP messages between different device nodes requires that the bus types of the different device nodes be the same. For example, if device node A transmits MCTP messages with device node B, and device node A uses a PCIe bus to send messages, then device node B needs to use a PCIe bus to receive messages; if device node C transmits MCTP messages with device node D, and device node C uses an I2C bus to send messages, then device node D needs to use an I2C bus to receive messages, and so on. It is not possible to transmit MCTP messages between two device nodes using different buses, thus limiting the application scenarios of the MCTP protocol.
[0024] Based on this, embodiments of this application provide a method, device, storage medium, and program product for transmitting MCTP messages. The method involves receiving a Management Component Transport Protocol (MCTP) message to be transmitted from a first device node. The MCTP message to be transmitted includes a transmission bus type identifier in the Device Node Identifier (Endpoint ID, EID) field. Based on the transmission bus type identifier, a first transmission bus is determined from multiple candidate transmission buses. The MCTP message to be transmitted is then forwarded using the first transmission bus through the Device Node Identifier field. Thus, because the MCTP message carries a transmission bus type identifier, the corresponding first transmission bus can be selected from multiple candidate transmission buses to send the MCTP message. This allows for flexible selection of multiple candidate transmission buses to forward the MCTP message to other device nodes, thereby broadening the application scenarios of the MCTP protocol.
[0025] The embodiments of this application will be further described below with reference to the accompanying drawings.
[0026] Figure 1 shows a schematic diagram of the architecture of the MCTP communication system provided in an embodiment of this application. As shown in Figure 1, the MCTP communication system includes at least one first device node, a bus routing node, a bus topology node, and at least one second device node.
[0027] The first device node is mainly responsible for sending MCTP messages during the communication process; it can also be called the source device node.
[0028] The bus routing node is connected to each first device node via a bus. Its main functions during communication are to receive MCTP messages transmitted by each first device node; parse the transmission bus type identifier from the received MCTP messages; determine the first transmission bus in the bus topology node based on the transmission bus type identifier; and forward the MCTP messages to be transmitted through the first transmission bus.
[0029] The bus topology node is connected between the bus routing node and at least one second device node. The bus topology node is equipped with various candidate transmission buses of different types, and any candidate transmission bus can be used to forward MCTP messages forwarded by the bus routing node to any second device node.
[0030] The second device node is mainly responsible for receiving MCTP messages forwarded by the bus routing node during the communication process and processing the received MCTP messages. This second device node can also be called the destination device node.
[0031] It should be noted that the aforementioned at least one first device node, bus routing node, bus topology node, and at least one second device node may belong to the same communication device. For example, each node may be a network card, a Baseboard Management Controller (BMC) chip, etc., in the communication device. Alternatively, the aforementioned at least one first device node, bus routing node, bus topology node, and at least one second device node may belong to different communication devices. For example, each node may be an independent communication device.
[0032] Those skilled in the art will understand that the structure of the MCTP communication system shown in FIG1 does not constitute a limitation on the embodiments of this application, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0033] Based on the above MCTP communication system, the following is an embodiment of the method for processing communication parameters for MCTP message transmission.
[0034] Please refer to Figure 2, which is a flowchart illustrating the MCTP message transmission method provided in this embodiment. This MCTP message transmission method is applied to the aforementioned bus routing node. As shown in Figure 2, the MCTP message transmission method includes the following steps S201 to S203.
[0035] Step 201: Receive the MCTP message of the management component transmission protocol to be transmitted from the first device node.
[0036] In this step, when the first device node sends the MCTP message to be transmitted, the bus routing node receives the MCTP message to be transmitted.
[0037] The aforementioned MCTP message to be transmitted includes a transmission bus type identifier, which is used to indicate the type of transmission bus. The transmission bus type identifier can be any form of identifier. In some embodiments, the transmission bus type identifier can be a field, an icon, etc.
[0038] The aforementioned MCTP message includes a transmission bus type identifier, which can be set by adding a new field to the MCTP protocol; or, the transmission bus type identifier can be set in an existing field of the MCTP protocol.
[0039] In some implementations, the aforementioned transport bus type identifier is located in at least one of the fields used to configure the device node identification number (EID) and the reserved fields in the MCTP message to be transmitted, thereby making it easier to set the transport bus type identifier in the MCTP message.
[0040] The device node identification number field may include at least one of the source device node identification number (Destination EID) and the destination device node identification number (Source EID).
[0041] For example, as shown in Figure 3, the original MCTP protocol structure can be configured in reserved field 31 as shown in Table 1, including the bus type indicator field (i.e., transmission bus type identifier).
[0042] Table 1 Bus Type Indication Fields
[0043] Alternatively, in the existing MCTP protocol, the transmission bus type identifier can be set in field 32 of the target device node identification number or field 33 of the source device node identification number.
[0044] The first device node and the bus routing node can be connected via a transmission bus (referred to as the "second transmission bus" here for easy distinction from the "first transmission bus" in the following text), that is, the bus routing node receives the MCTP message via the second transmission bus.
[0045] It should be noted that the aforementioned second transmission bus can be only one type of transmission bus. For example, the second transmission bus can be any one of PCIe, I2C, I3C, and UART, that is, the first device node transmits the MCTP message to be transmitted to the bus routing node only through this one type of transmission bus.
[0046] Alternatively, the second transmission bus may include multiple types of transmission buses. For example, the second transmission bus may be multiple transmission buses such as PCIe, I2C, I3C and UART, that is, the first device node can transmit the MCTP message to be transmitted to the bus routing node at the same time through these multiple transmission buses.
[0047] In some implementations, receiving the MCTP message to be transmitted from the first device node includes:
[0048] The system receives a first MCTP message transmitted by a first device node via a third transmission bus, and also receives a second MCTP message transmitted by the first device node via a fourth transmission bus, wherein the third and fourth transmission buses are transmission buses of different types.
[0049] The MCTP messages to be transmitted include a first MCTP message and a second MCTP message.
[0050] In this embodiment, the first device node can transmit the MCTP message to be transmitted to the bus routing node in parallel through different buses, thereby improving the efficiency of transmitting MCTP messages between the first device node and the bus routing node.
[0051] For example, the first device node mentioned above can simultaneously transmit MCTP messages to the bus routing node via both the I3C bus and the PCIe bus, and so on.
[0052] Step 202: Determine the first transmission bus from among multiple candidate transmission buses based on the transmission bus type identifier.
[0053] In this step, after receiving the MCTP message, the bus routing node parses the MCTP message to obtain the transmission bus type identifier, and determines the first transmission bus indicated by the transmission bus type identifier from the multiple candidate transmission buses of the bus topology node.
[0054] The first transmission bus mentioned above can be the transmission bus indicated by the transmission bus type identifier, and it can be the same transmission bus as the second transmission bus mentioned above. For example, if the second transmission bus is a PCIe bus, the first transmission bus can also be a PCIe bus, that is, the transmission bus type identifier is used to indicate a PCIe bus; or, if the second transmission bus is an I2C bus, the first transmission bus can also be an I2C bus, that is, the transmission bus type identifier is used to indicate an I2C bus, and so on.
[0055] In some implementations, the second transmission bus and the first transmission bus are different types of transmission buses, thereby enabling MCTP message forwarding across different types of buses and further expanding the application scenarios of the MCTP protocol.
[0056] For example, if the second transmission bus is a PCIe bus, the first transmission bus can also be an I2C bus, i.e., the transmission bus type identifier is used to indicate the I2C bus; or, if the second transmission bus is an I2C bus, the first transmission bus can also be a PCIe bus, i.e., the transmission bus type identifier is used to indicate the PCIe bus, and so on.
[0057] It should be noted that the first transmission bus mentioned above can be only one type of transmission bus. For example, the first transmission bus can be any one of PCIe, I2C, I3C and UART, that is, the bus routing node transmits the MCTP message to be transmitted to other device nodes only through this one type of transmission bus.
[0058] Alternatively, the first transmission bus mentioned above may also include multiple types of transmission buses. For example, the first transmission bus may be multiple transmission buses such as PCIe, I2C, I3C and UART. That is, the bus routing node can transmit the MCTP message to be transmitted to other device nodes at the same time through the multiple transmission buses, thereby realizing parallel transmission between the bus routing node and other device nodes and improving the efficiency of transmitting MCTP messages between the first device node and the bus routing node.
[0059] Furthermore, the number of transmission buses in the first transmission bus and the second transmission bus can be the same or different. Also, the transmission buses in the first transmission bus and the transmission buses in the second transmission bus can be the same or different.
[0060] In some implementations, at least one of the third and fourth transmission buses is a different type of transmission bus from the first transmission bus, thereby further expanding the application scenarios of the MCTP protocol.
[0061] In cases where the first transmission bus includes only one type of transmission bus and the second transmission bus includes multiple transmission buses, or where the first transmission bus includes only multiple types of transmission buses and the second transmission bus includes one type of transmission bus, or where both the first and second transmission buses include multiple types of transmission buses, the first and second transmission buses may have some different transmission buses or all different transmission buses.
[0062] For example, as shown in Figure 4, when the BMC (i.e., the first device node) transmits MCTP messages to the bus routing node simultaneously via the I3C bus and the PCIe bus (i.e., the second transmission bus includes the I3C bus and the PCIe bus), the bus routing node can transmit MCTP messages to other device nodes via the I2C bus, the I3C bus, and the PCIe bus (i.e., the first transmission bus includes the I2C bus, the I3C bus, and the PCIe bus).
[0063] Step 203: Forward the MCTP message to be transmitted via the first transmission bus.
[0064] In this step, the bus routing node can forward the MCTP message to be transmitted through the first transmission bus after determining the first transmission bus.
[0065] The aforementioned forwarding of the MCTP message to be transmitted via the first transmission bus can be achieved by the bus routing node sending the MCTP message to be transmitted to all device nodes connected to the first transmission bus; or it can be achieved by sending the MCTP message to be transmitted to some node devices connected to the first transmission bus.
[0066] In some implementations, multiple candidate transport buses are used to transmit MCTP messages to multiple second device nodes. Each candidate transport bus is connected to at least one second device node, and the MCTP message to be transmitted also includes a destination device node identification number.
[0067] The MCTP message to be transmitted is forwarded through the first transmission bus, including:
[0068] Based on the destination device node identification number, the target device node is determined from at least one second device node connected to the first transmission bus;
[0069] The MCTP message to be transmitted is forwarded to the target device node via the first transmission bus.
[0070] In this embodiment, the bus routing node can parse the E ID from the transmitted MCTP message and transmit the MCTP message to be transmitted to the destination device node corresponding to the EID through the first transmission bus, thereby achieving accurate transmission of the MCTP message.
[0071] For example, as shown in Figure 1, when the second device node 1 and the second device node 2 are simultaneously connected to the bus routing node device through the PCIe bus, and the bus routing node determines that the PCIe bus is the first transmission bus mentioned above, if the EID indicates the second device node 1, the bus routing node forwards the MCTP message to be transmitted to the second device node 1 (i.e., the destination device node) through the PCIe bus.
[0072] It should be noted that the information of each candidate transmission bus in the bus topology node can be pre-configured in the bus routing node device, and this configuration operation can be performed manually or automatically by the bus routing node. The pre-configured information can be a routing table, which indicates the aforementioned candidate transmission buses, etc.
[0073] In some implementations, before determining the first transmission bus from multiple candidate transmission buses based on the transmission bus type identifier, the method further includes:
[0074] Under preset conditions, the transmission bus connected to multiple second device nodes is detected to identify multiple candidate transmission buses.
[0075] In some implementations, the bus routing node device can detect the transmission buses connected to multiple second device nodes when preset conditions are met, and determine multiple candidate transmission buses, thereby enabling timely updates of the information of the candidate transmission buses configured in the bus routing node.
[0076] The aforementioned preset conditions can be any conditions used to trigger the bus routing node device to detect the transmission bus connected to multiple second device nodes. For example, the preset conditions can be that the running time reaches a preset duration.
[0077] In some implementations, the above method is applied to a bus routing node, with preset conditions including powering on the bus routing node, so that once the bus routing node is powered on, the information of the candidate transmission buses configured in the bus routing node can be updated.
[0078] It should be noted that after the target device node corresponding to the aforementioned destination device node identification number receives the MCTP message to be transmitted, the target device node can process the MCTP message to be transmitted, generate a response message, and send the response message to the bus routing node. The bus routing node device can then forward the response message to the first device node.
[0079] The target device node sends a response message to the bus routing node device, which can be done through the first transmission bus or through other transmission buses between the target device node and the bus routing node.
[0080] The aforementioned bus routing node forwards the response message to the first device node, which can be achieved by the bus routing node broadcasting the response message to all device nodes connected to it except the second device node, so that the first device node receives the response message.
[0081] In some implementations, the MCTP message to be transmitted also includes a source device node identifier (Destination EID) and a destination device node identifier (Source EID), with the source device identifier used to indicate the first device node;
[0082] The method also includes:
[0083] Based on the transmission bus type identifier, destination device node identification number, and source device node identification number, routing and forwarding information is generated;
[0084] Upon receiving an acknowledgment message, an acknowledgment message is sent to the first device node based on the routing information. The acknowledgment message is a message returned by the destination device node based on the MCTP message to be transmitted.
[0085] In this embodiment, the bus routing node generates forwarding information based on the transmission bus type identifier, destination device node identifier, and source device node identifier obtained from the MCTP message, and forwards the response message to the first device node based on the forwarding information, thereby improving the efficiency of forwarding the response message.
[0086] The forwarding information mentioned above may include information indicating the first device node, the destination device node, the first transmission bus, and the second transmission bus, etc. For example, this forwarding information may be as shown in Table 2 below:
[0087] Table 2 Forwarding Information
[0088] The above-mentioned sending of a response message to the first device node based on the routing information can be achieved by the bus routing node receiving the response message returned by the destination device node through the first transmission bus based on the transmission bus type identifier and the destination device node identification number, and sending a response message to the corresponding first device node based on the source device node identification number.
[0089] In this embodiment, the bus routing node receives a Management Component Transmission Protocol (MCTP) message to be transmitted from a first device node. The MCTP message includes a transmission bus type identifier. Based on the transmission bus type identifier, a first transmission bus is determined from multiple candidate transmission buses. The MCTP message is then forwarded through the first transmission bus. Thus, because the MCTP message carries a transmission bus type identifier, the bus routing node can select the corresponding first transmission bus from multiple candidate transmission buses to transmit the MCTP message. This means the bus routing node can flexibly select from multiple candidate transmission buses to forward the MCTP message to other device nodes, thereby broadening the application scenarios of the MCTP protocol.
[0090] Please refer to Figure 6, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device includes the aforementioned bus routing node. As shown in Figure 6, the communication device 600 includes:
[0091] One or more processors 610;
[0092] The memory 620 stores one or more programs that, when executed by one or more processors 610, cause the one or more processors 610 to implement the MCTP message transmission method described in any of the above embodiments.
[0093] Memory 620, as a non-transitory network system, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory 620 may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory 620 may include remotely located memories 620 relative to processor 610, which can be connected to processor 610 via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
[0094] The memory 620 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 620 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 620 and is called and executed by the processor 610.
[0095] The processor 610 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.
[0096] In some embodiments, the communication device further includes:
[0097] Input / output interfaces are used to implement information input and output;
[0098] The communication interface is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0099] The bus transmits information between various components of the device (e.g., processor 610, memory 620, input / output interface, and communication interface);
[0100] The processor 610, memory 620, input / output interface, and communication interface can communicate with each other within the device via a bus.
[0101] An embodiment of this application also provides a computer-readable storage medium storing computer-executable instructions for performing the MCTP message transmission method described in any of the embodiments above.
[0102] An embodiment of this application also provides a computer program product, including a computer program or computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer program or computer instructions from the computer-readable storage medium and executes the computer program or computer instructions, causing the computer device to perform a method for transmitting MCTP messages as described in any of the above embodiments.
[0103] In this embodiment, a Management Component Transport Protocol (MCTP) message to be transmitted is received from a first device node. The MCTP message includes a transport bus type identifier. Based on the transport bus type identifier, a first transport bus is determined from multiple candidate transport buses. The MCTP message is then forwarded through the first transport bus. Thus, because the MCTP message carries a transport bus type identifier, the corresponding first transport bus can be selected from multiple candidate transport buses to transmit the MCTP message. This allows for flexible selection of multiple candidate transport buses to forward the MCTP message to other device nodes, thereby broadening the application scenarios of the MCTP protocol.
[0104] The system architecture and application scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. Those skilled in the art will understand that as system architectures evolve and new application scenarios emerge, the technical solutions provided in this application are also applicable to similar technical problems.
[0105] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.
[0106] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.
[0107] It should be understood that in this application, "at least one (item)" means one or more, and "more than" means two or more. "And / or" is used to describe the relationship between related objects, indicating that three relationships can exist. For example, "A and / or B" can represent three cases: only A exists, only B exists, and both A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.
[0108] The above description, with reference to the accompanying drawings, illustrates some embodiments of this application, but does not limit the scope of this application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and spirit of this application shall be within the scope of this application.
Claims
1. A method for transmitting MCTP messages, comprising: Receive a Management Component Transmission Protocol (MCTP) message to be transmitted from a first device node, wherein the MCTP message to be transmitted includes a transmission bus type identifier; Based on the transmission bus type identifier, a first transmission bus is determined from a plurality of candidate transmission buses; The MCTP message to be transmitted is forwarded through the first transmission bus.
2. The method according to claim 1, wherein, The process of receiving the MCTP message to be transmitted from the first device node includes: Receive the MCTP message to be transmitted from the first device node via the second transmission bus. The second transmission bus and the first transmission bus are different types of transmission buses.
3. The method according to claim 1, wherein, The process of receiving the MCTP message to be transmitted from the first device node includes: The system receives a first MCTP message transmitted by the first device node via a third transmission bus, and a second MCTP message transmitted by the first device node via a fourth transmission bus, wherein the third and fourth transmission buses are transmission buses of different types. The MCTP message to be transmitted includes the first MCTP message and the second MCTP message.
4. The method according to claim 3, wherein, At least one of the third and fourth transmission buses is a transmission bus of a different type from the first transmission bus.
5. The method according to claim 1, wherein, The transmission bus type identifier is located in at least one of the fields used to configure the device node identification number (EID) and the reserved fields in the MCTP message to be transmitted.
6. The method according to claim 1, wherein, The various candidate transmission buses are used to transmit MCTP messages to multiple second device nodes. Each candidate transmission bus is connected to at least one second device node. The MCTP message to be transmitted also includes a destination device node identification number. The forwarding of the MCTP message to be transmitted via the first transmission bus includes: Based on the destination device node identification number, the target device node is determined from at least one of the second device nodes connected to the first transmission bus; The MCTP message to be transmitted is forwarded to the target device node via the first transmission bus.
7. The method according to claim 6, wherein, Before determining the first transmission bus from multiple candidate transmission buses based on the transmission bus type identifier, the method further includes: Under preset conditions, the transmission buses connected to the plurality of second device nodes are detected to determine the plurality of candidate transmission buses.
8. The method according to claim 7, wherein, The method is applied to a bus routing node, and the preset condition includes powering on the bus routing node.
9. The method according to claim 1, wherein, The MCTP message to be transmitted also includes a source device node identification number and a destination device node identification number, wherein the source device identification number is used to indicate the first device node; The method further includes: Based on the transmission bus type identifier, the destination device node identifier, and the source device node identifier, routing and forwarding information is generated; Upon receiving a response message, the response message is sent to the first device node according to the routing and forwarding information, wherein the response message is a message fed back by the destination device node based on the MCTP message to be transmitted.
10. A communication device, comprising: One or more processors; A memory that stores one or more programs, which, when executed by one or more processors, cause the one or more processors to perform the following: The method for transmitting MCTP messages according to any one of claims 1-9.
11. A computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement as follows: The method for transmitting MCTP messages according to any one of claims 1-9.
12. A computer program product comprising a computer program, which, when executed by a processor, implements, as follows: The method for transmitting MCTP messages according to any one of claims 1-9.