WO2020124575A1 - 一种通信设备 - Google Patents
一种通信设备 Download PDFInfo
- Publication number
- WO2020124575A1 WO2020124575A1 PCT/CN2018/122756 CN2018122756W WO2020124575A1 WO 2020124575 A1 WO2020124575 A1 WO 2020124575A1 CN 2018122756 W CN2018122756 W CN 2018122756W WO 2020124575 A1 WO2020124575 A1 WO 2020124575A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bus
- controller
- communication device
- buses
- message
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/40—Bus structure
- G06F13/4004—Coupling between buses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40169—Flexible bus arrangements
- H04L12/40176—Flexible bus arrangements involving redundancy
- H04L12/40182—Flexible bus arrangements involving redundancy by using a plurality of communication lines
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/40169—Flexible bus arrangements
- H04L12/40176—Flexible bus arrangements involving redundancy
- H04L12/40189—Flexible bus arrangements involving redundancy by using a plurality of bus systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L2012/40208—Bus networks characterized by the use of a particular bus standard
- H04L2012/40215—Controller Area Network CAN
Definitions
- This application relates to the field of communications, and in particular to a communications device.
- the communication equipment adopts MicroTCA chassis, and the controller in the chassis passes the IPMB0 bus.
- the IPMB0 bus adopts two redundant I2C bus networking methods, namely, IPMB0-A and IPMB0-B.
- the present application provides a communication device to solve the problems of poor communication device stability and low communication efficiency in the prior art.
- the present application provides a communication device, the communication device includes: a first controller and a plurality of second controllers; a plurality of first buses and a second bus, the first controller respectively through the first bus and The second bus communicates with the second controller; wherein, the first bus is a star bus or a network bus, the first controller receives messages from the second controller through the second bus, and sends rounds through the first bus Inquire the message to the second controller.
- the communication device includes a first controller and several second controllers; several first buses and several second buses, and the first controller communicates with the second controller through the first bus and the second bus, respectively ;
- the first bus is a star bus or a network bus, using a star bus or a network bus, the first controller can be connected to several second controllers respectively, each connection point does not interfere with each other, solved A single node failure will pull the entire bus to a fixed level, resulting in the problem of inability to communicate and improve the stability of the system.
- the first controller receives messages from the second controller through the second bus, and sends a polling message to the second controller through the first bus.
- the first bus and the second bus respectively carry different messages to resolve message conflicts. Problems to improve the communication efficiency of the system.
- FIG. 1 is a schematic structural diagram of a communication device in the prior art
- FIG. 2 is a schematic structural diagram of an embodiment of a communication device of the present application.
- FIG. 3 is a schematic diagram of the format of the IPMI protocol of this application.
- FIG. 6 is a schematic structural diagram of another embodiment of a communication device of the present application.
- FIG. 1 is a schematic structural diagram of a communication device in the prior art.
- the communication device 100 includes several first controllers 11, several second controllers 12, a first bus 13 and a second bus 14. Among them, the first controller 11 and the second controller 12 are communicatively connected through the first bus 13 and the second bus 14.
- Both the first bus 13 and the second bus 14 are I2C buses. As shown in FIG. 1, in the networking mode of the first bus 13, the first controller 11 and multiple second controllers 12 are connected through the same node. If the node fails, the first bus 13 will be pulled to a fixed level, thereby affecting the communication effect of the first bus 13.
- the networking mode of the second bus 14 is the same as the networking mode of the first bus 13 and will not be repeated here.
- the second controller 12 actively sends a report message to the first controller 11 through the first bus 13 or the second bus 14, and the first controller 11 alternately selects the first bus 13 and the second bus 14 A polling message is sent to the second controller 12.
- the first controller 11 sends a polling message and the second controller 12 sends a report message, and the first bus 13 or the second bus 14 is used at the same time, communication conflicts are likely to occur, affecting the communication effect and communication efficiency.
- FIG. 2 is a schematic structural diagram of an embodiment of the communication device of the present application.
- the communication device 200 includes a first controller 21, several second controllers 22, several first buses 23 and a second bus 24.
- the first controller 21 communicates with the second controller 22 through the first bus 23 and the second bus 24, respectively.
- the first bus 23 uses a star connection, the first controller 21 receives the message from the second controller 22 through the first bus 23, and sends a polling message to the second controller 22 through the second bus 24.
- the first bus 23 is an I2C bus
- the second bus 24 is a CAN bus.
- the first controller 21 and the plurality of second controllers 22 are communicatively connected through the first bus 23.
- the I2C bus between the first controller 21 and each second controller 22 is connected by an independent node.
- the connection node between the first controller 21 and a certain second controller 22 fails, the first The first bus 23 between the controller 21 and this second controller 22 cannot communicate normally.
- the first bus 23 communication between the first controller 21 and other second controllers 22 will not be affected, and it can still communicate normally.
- the first controller and several second controllers are connected through the same node.
- the communication between the first controller and several second controllers will be problematic.
- the I2C bus adopts a star connection mode, which can effectively solve the problem that the single-node failure in the prior art affects the entire bus and cannot communicate.
- the polling message transmitted between the first controller 21 and the second controller 22 is carried by the first bus 23, that is, the I2C bus, and the report message is carried by the second bus 24, that is, the CAN bus.
- polling messages are only transmitted through the I2C bus.
- the second controller rotates the second bus to transmit the reported message. The transmission method of this embodiment solves the problem of message collision .
- the second bus needs to carry the polling message and the reporting message, but the polling message and the reporting message cannot be transmitted at the same time.
- the first controller transmits the polling message through the second bus, it needs to be staggered from the time when the second controller transmits the reported message through the second bus, so as to avoid the problem of message collision, and thus the polling efficiency of the communication device is reduced.
- both the first bus 23 and the second bus 24 only carry a single message, which can also improve the efficiency of transmitting messages, for example, increase the polling efficiency of the first controller 21, thereby improving the transmission efficiency of the communication device 200.
- the first controller 21 may continue to transmit the polling message through the second bus 24, that is, the CAN bus.
- the second bus 24 can serve as a backup line of the first bus 23. At this time, the second bus 24 carries the polling message and the report message.
- the communication device 200 may further include a third bus (not shown in the figure).
- the third bus serves as a backup line of the first bus 23, and the third bus may be an I2C bus or a CAN bus.
- the communication message of the first bus 23 is carried by the third bus.
- the third bus can also be used as a backup line of the second bus 24, which will not be repeated here.
- the use of the third bus is not limited to the backup line, and the third bus may also carry the polling message transmitted between the first controller 21 and the second controller 22. Specifically, when the first controller 21 sends the polling message to the second controller 22, the two buses of the first bus 23 and the third bus are alternately selected, which can also solve the problem of conflict between the polling message and the reported message.
- the third bus may also carry messages other than polling messages and reporting messages, such as fault messages, etc., so as to expand the types of messages transmitted between the first controller 21 and the second controller 22.
- FIG. 3 is a schematic diagram of the format of the IPMI protocol of the present application
- FIG. 4 is a schematic diagram of the format of the CAN bus carrying the reported message of the present application
- 5 is a schematic diagram of the format of the CAN bus carrying the polling message in this application.
- the contents of the IPMI protocol include:
- the first bus 23 is an I2C bus
- the second bus 24 is a CAN bus.
- the communication protocol of the CAN bus needs to be compatible with the IPMI protocol.
- the communication protocol of the CAN bus is optimized so that the CAN bus can carry the report message. Specifically, part of the content of the IPMI protocol is inserted into the CAN protocol.
- the optimized contents of the CAN bus include:
- the arbitration field also includes response slave address (rsSA) and other content
- the data field also includes network function code (netFn), cmd (command number) and alarm identification (alarm ID) Etc.
- the CAN bus can also serve as the first bus 23, that is, the backup line of the I2C bus.
- the CAN bus as a backup line needs to carry the polling message sent by the first controller 21 to the second controller 22, and the CAN protocol also needs to insert part of the content of the IPMI protocol. For details, see FIG. 5.
- the optimized contents of the CAN bus include:
- the arbitration field also includes response slave address (rsSA) and INDEX function, etc.
- the data field also includes network function code (netFn), cmd (command number) and data bytes (Data Byte) and other content.
- the first controller 21 sends a polling message to the second controller 22 through the I2C bus or the CAN bus.
- the polling message period is related to the baud rate and the message length.
- the maximum length of the IPMI message is 44 bytes.
- each message takes 8ms. When there is no conflict with the reported message, it can be polled more than 20 times per second, and the bus efficiency is increased by more than 3 times compared with the existing technology.
- the communication device 200 may also use other I2C baud rates, such as 400K.
- the I2C protocol is defined to the data link layer, and the I2C bus adopts a synchronous transmission method, which can transmit multiple bytes at a time. It has a strong universality and is suitable for transmitting multiple bytes of polling messages.
- the CAN protocol is also defined to the data link layer.
- the CAN bus uses asynchronous transmission, and the data field in the CAN protocol is 8 bytes.
- an application layer data packet corresponds to a frame of data link The frame of the layer, so a data packet of the application layer protocol can only transmit up to 8 bytes.
- the polling message is transmitted through the CAN bus. Under the CAN standard baud rate of 100K, the CAN protocol splits the polling message into multiple data packets for transmission. Since the number of bytes of each data packet can only be up to 8, the time taken to transmit each data packet is short, and the efficiency of the bus can be improved accordingly.
- the communication device 200 may also use other CAN baud rates, such as 10K/20K/50K/125K/250K/500K/800K/1000K.
- the first controller 21 includes a carrier management controller (MCMC), and the second controller 22 includes an enhanced module management controller (EMMC); in other embodiments, the first controller 21 and the second controller 22 may be Other controllers will not be repeated here.
- MCMC carrier management controller
- EMMC enhanced module management controller
- both the first bus 23 and the second bus 24 in the communication device 200 may be CAN buses, and the CAN bus carries the polling message and/or the report message by inserting part of the content of the IPMI protocol into the CAN protocol , Please refer to Figure 4 and Figure 5 for details.
- both the first bus 23 and the second bus 24 in the communication device 200 may be I2C buses, and the networking mode of the I2C bus is a star connection.
- the transmission efficiency of the communication device 200 is improved by optimizing the bus connection mode and the bus protocol; specifically, by optimizing the networking mode of the I2C bus to a star or network mode, it can effectively avoid single Node failure affects the entire bus communication problem; the communication device 200 carries the polling message through the I2C bus and the reporting message through the CAN bus, thereby solving the problem of conflict between the periodic polling message of the first controller 21 and the reporting message of the second controller 22 At the same time, it also increases the frequency of the first controller 21 polling the second controller 22; further optimization of the CAN protocol, so that the CAN bus can carry reporting messages and polling messages, the CAN bus can also be used as a backup bus of the I2C bus, When the I2C bus fails, the CAN bus carries the polling message to improve the stability of the communication device 200.
- FIG. 6 is a schematic structural diagram of another embodiment of the communication device of the present application.
- the communication device 300 includes a first controller 31, several second controllers 32, several first buses 33 and a second bus 34.
- the first controller 31 communicates with the second controller 32 through the first bus 33 and the second bus 34, respectively.
- the first bus 33 is a network bus.
- the first controller 31 receives messages from the second controller 32 through the first bus 33 and sends a polling message to the second controller 32 through the second bus 34.
- the first bus 33 is an I2C bus
- the second bus 34 is a CAN bus.
- the first controller 31 and the plurality of second controllers 32 are communicatively connected through the first bus 33, and the plurality of first controllers 31 are communicatively connected through the first bus 33, and the plurality of second controllers 32 are connected through the first
- the bus 33 is connected for communication.
- the networking mode of the first bus 33 is set to a network connection mode.
- the I2C bus between the first controller 31 and each second controller 32 is connected by an independent node.
- the connection node between the first controller 31 and a certain second controller 32 fails, the first The controller 31 and this second controller 32 cannot communicate normally. The communication between the first controller 31 and other second controllers 32 will not be affected, and it can still communicate normally.
- an I2C bus connection is used between several first controllers 31, and an I2C bus connection is used between several second controllers 32.
- an I2C bus can be used to establish a communication relationship between several first controllers 31 and transmit communication messages. Further, when a communication node between a first controller 31 and a second controller 32 fails and cannot send a polling message, the first controller 31 can forward the communication message through other first controllers 31 to continue A polling message is sent to the second controller 32, thereby improving the stability of the communication device 300.
- an I2C bus can be used to establish a communication relationship between several second controllers 32 and transmit communication messages. Further, when a communication node between a second controller 32 and the first controller 31 fails and cannot send a report message, the second controller 32 can forward the communication message through other second controllers 32 and continue to The first controller 31 sends a polling message, thereby improving the stability of the communication device 300.
- the network-connected I2C bus is used between the first controllers 31 and the second controllers 32 of the communication device 300, and the first controllers 31 or the second controllers 32 are all A communication connection can be established through an I2C bus; further, the first controller 31 can also forward communication messages through other first controllers 31, and the second controller 32 can also forward communication messages through other second controllers 32, improving communication equipment. 300 stability.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Small-Scale Networks (AREA)
Abstract
本申请提出了一种通信设备。该通信设备包括:第一控制器和若干第二控制器;若干第一总线和/或第二总线,第一控制器分别通过第一总线和第二总线与第二控制器进行通信连接;其中,第一总线是星型总线或网型总线,第一控制器通过第二总线接收来自第二控制器的消息,且通过第一总线发送轮询消息至第二控制器。本申请的第一总线采用星型总线或网型总线提高宽通信设备稳定性,第一总线和第二总线分别承载不同的消息,避免消息冲突,提高通信设备的通信效率。
Description
本申请涉及通信领域,具体涉及一种通信设备。
通信设备采用MicroTCA机框,机框内的控制器通过IPMB0总线,IPMB0总线采用两条冗余I2C总线方式组网,即IPMB0-A和IPMB0-B两条总线。
现有I2C总线结构的MicroTCA机框,在工作时会存在单节点故障将整个总线拉成固定电平,从而导致整个总线不能通信的问题,造成通信设备稳定性降低。IPMB0总线上,存在着两个方向的消息,一是MCMC(载波管理控制器)定期向EMMC(增强模块管理控制器)发送的轮询消息,用以获取各个EMMC设备的运行状态;二是EMMC主动向MCMC发起的上报消息,此类消息为突发性消息,且MCMC轮询时交替选择IPMB0-A和IPMB0-B两条总线,如此,上报消息和轮询消息就会存在冲突的问题,影响通信设备的通信效率。
本申请提供一种通信设备,以解决现有技术中,通信设备稳定性差和通信效率低的问题。
为解决上述技术问题,本申请提供了一种通信设备,该通信设备包括:第一控制器和若干第二控制器;若干第一总线和第二总线,第一控制器分别通过第一总线和第二总线与第二控制器进行通信连接;其中,第一总线是星型总线或网型总线,第一控制器通过第二总线接收来自第二控制器的消息,且通过第一总线发送轮询消息至第二控制器。
在本申请中,通信设备包括第一控制器和若干第二控制器;若干第一总线和若干第二总线,第一控制器分别通过第一总线和第二总线与第二控制器进行通信连接;其中,第一总线是星型总线或网型总线,采用星型总线或网型总线,第一控制器可以分别与若干第二控制器连接,每个连接点之间互不干扰,解决了单节点故障会将整个总线拉成固定电平,导致不能通信的问题,提高系统的稳定性。
此外,第一控制器通过第二总线接收来自第二控制器的消息,且通过第一 总线发送轮询消息至第二控制器,第一总线和第二总线分别承载不同的消息,解决消息冲突的问题,提高系统的通信效率。
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。其中:
图1是现有技术中通信设备的结构示意图;
图2是本申请通信设备一实施例的结构示意图;
图3是本申请IPMI协议的格式示意图;
图4是本申请CAN总线承载上报消息的格式示意图;
图5是本申请CAN总线承载轮询消息的格式示意图;
图6是本申请通信设备另一实施例的结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚、完整地描述。可以理解的是,此处所描述的具体实施例仅用于解释本申请,而非对本申请的限定。另外还需要说明的是,为了便于描述,附图中仅示出了与本申请相关的部分而非全部结构。基于本申请中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
请参见图1,图1是现有技术中通信设备的结构示意图。
如图1所示,通信设备100包括若干第一控制器11、若干第二控制器12、第一总线13和第二总线14。其中,第一控制器11和第二控制器12通过第一总线13和第二总线14进行通信连接。
第一总线13和第二总线14均为I2C总线。如图1所示第一总线13的组网方式中,第一控制器11与多个第二控制器12通过同一节点进行连接。该节点出现故障,会将第一总线13拉成固定电平,从而影响第一总线13的通信效果。第二总线14的组网方式与第一总线13的组网方式相同,在此不再赘述。
进一步地,现有技术中,第二控制器12通过第一总线13或第二总线14主 动向第一控制器11发送上报消息,第一控制器11交替选择第一总线13和第二总线14向第二控制器12发送轮询消息。第一控制器11发送轮询消息和第二控制器12发送上报消息,同时使用第一总线13或第二总线14时,容易发生通信冲突,影响通信效果和通信效率。
为解决上述技术问题,本申请提供了一种通信设备,具体请参阅图2~图5,图2是本申请通信设备一实施例的结构示意图。
如图2所示,通信设备200包括第一控制器21、若干第二控制器22、若干第一总线23和第二总线24。
第一控制器21分别通过第一总线23和第二总线24与第二控制器22进行通信连接。其中,第一总线23采用星型连接方式,第一控制器21通过第一总线23接收来自第二控制器22的消息,且通过第二总线24发送轮询消息至第二控制器22。
具体地,第一总线23为I2C总线,第二总线24为CAN总线。第一控制器21和若干第二控制器22通过第一总线23进行通信连接。
如图2所示,第一控制器21和每个第二控制器22之间的I2C总线均采用独立节点连接。采用上述星型连接方式,第一控制器21在与多个第二控制器22发送轮询消息时,第一控制器21与某个第二控制器22之间的连接节点出现故障,第一控制器21与这个第二控制器22之间第一总线23无法正常通信。第一控制器21与其他第二控制器22之间的第一总线23通信不会受到影响,仍然可以正常通信。
现有技术中,第一控制器与若干第二控制器通过同一节点进行连接,当该节点出现故障时,第一控制器与若干第二控制器的通信都会出现问题。本实施例I2C总线采用星型连接方式可以有效解决现有技术中单节点故障影响整个总线不能通信的问题。
本实施例中,第一控制器21与第二控制器22之间传输的轮询消息由第一总线23即I2C总线承载,上报消息由第二总线24即CAN总线承载。在正常情况下,轮询消息只通过I2C总线传输。相对于现有技术中第一控制器交替选择第一总线和第二总线传输轮询消息,第二控制器旋转第二总线传输上报消息,本实施例的这种传输方式解决了消息冲突的问题。
进一步地,现有技术中,第二总线需要承载轮询消息和上报消息,而轮询消息和上报消息不能同时传输。第一控制器通过第二总线传输轮询消息时,需 要和第二控制器通过第二总线传输上报消息的时间错开,才能避免消息冲突的问题,如此通信设备的轮询效率降低。本实施例中,第一总线23和第二总线24都只承载单一消息,也可以提高传输消息的效率,例如提高第一控制器21的轮询效率,进而提高通信设备200的传输效率。
进一步地,在本实施例中,当第一控制器21与某个第二控制器22之间的I2C总线连接节点出现故障,第一控制器21与这个第二控制器22之间无法正常传输轮询消息时,第一控制器21可以通过第二总线24即CAN总线继续传输轮询消息。在这种情况下,第二总线24可以作为第一总线23的备份线路。此时,第二总线24承载轮询消息和上报消息。
进一步地,在其他实施例中,通信设备200还可以包括第三总线(图中未示出),第三总线作为第一总线23的备份线路,第三总线可以为I2C总线或CAN总线。当第一总线23出现故障时,第一总线23的通信消息由第三总线承载。第三总线也可以作为第二总线24的备份线路,在此不再赘述。
第三总线的用途不局限于备份线路,第三总线也可以承载第一控制器21与第二控制器22之间传输的轮询消息。具体地,第一控制器21发送轮询消息至第二控制器22时,交替选择第一总线23和第三总线两条总线,同样可以解决轮询消息与上报消息冲突的问题。
在其他实施例中,第三总线也可以承载轮询消息和上报消息以外的消息,例如故障消息等,以此扩充第一控制器21与第二控制器22之间传输的消息种类。
上述总线优化和消息承载的设置均可通过协议优化实现,具体请参阅图3~图5,图3是本申请IPMI协议的格式示意图,图4是本申请CAN总线承载上报消息的格式示意图,图5是本申请CAN总线承载轮询消息的格式示意图。
对于上述格式示意图中的IPMI命令格式可参阅下表:
如图3所示,IPMI协议的内容包括:
响应从地址(rsSA)---网络功能码(netFn)/响应逻辑单元号(rsLUN)---校验码(Checksum)
响应从地址(rsSA)---网络功能码(netFn)/响应逻辑单元号(rsLUN)---cmd(命令号)---数据字节(Data byte)---校验码(Checksum)
响应从地址(rsSA)---网络功能码(netFn)/响应逻辑单元号(rsLUN)---校验码(Checksum)
响应从地址(rsSA)---网络功能码(netFn)/响应逻辑单元号(rsLUN)---cmd(命令号)---完成码(Completion Code)---数据字节(Data byte)---校验码(Checksum)
在本实施例中,第一总线23为I2C总线,第二总线24为CAN总线,当CAN总线承载上报消息时,CAN总线的通信协议需要兼容IPMI协议。在本实施例中,CAN总线的通信协议优化,以使CAN总线能够承载上报消息,具体 地,CAN协议中插入部分IPMI协议的内容。
如图4所示,CAN总线优化后的内容包括:
帧开始---仲裁域(响应从地址)---控制域---数据域(网络功能码+命令号+警报识别)---CRC域---ACK域---帧结束
优化后的CAN总线中,仲裁域(Arbitration)还包括响应从地址(rsSA)等内容,数据域(Data field)还包括网络功能码(netFn)、cmd(命令号)和警报识别(alarm ID)等内容。
如上述描述,CAN总线也可以作为第一总线23,即I2C总线的备份线路。当I2C总线出现故障时,CAN总线作为备份线路就需要承载第一控制器21发送至第二控制器22的轮询消息,CAN协议也需要插入部分IPMI协议的内容,具体请参阅图5。
如图5所示,CAN总线优化后的内容包括:
帧开始---仲裁域(响应从地址+索引)---控制域---数据域(网络功能码+命令号+数据字节)---CRC域---ACK域---帧结束
优化后的CAN总线中,仲裁域(Arbitration)还包括响应从地址(rsSA)和INDEX函数等内容,数据域(Data field)还包括网络功能码(netFn)、cmd(命令号)和数据字节(Data byte)等内容。
在本实施例中,第一控制器21通过I2C总线或CAN总线向第二控制器22发送轮询消息,轮询消息周期与波特率及消息长度有关。IPMI消息长度最大为44字节,在100K的I2C标准波特率下,每条消息耗时8ms。在没有与上报消息冲突的情况下,每秒可轮询20次以上,总线效率相对于现有技术增加了3倍以上。在其他实施例中,通信设备200也可以采用其他I2C波特率,如400K等。I2C协议定义到数据链路层,且I2C总线采用同步传输方式,一次可以传输多个字节,具有很强的普适性,适合传输多个字节的轮询消息。
CAN协议同样定义到数据链路层,CAN总线采用异步传输方式,且CAN协议中的数据域为8个字节,在定义应用层协议的时候,一个应用层的数据包对应一帧数据链路层的帧,因此应用层协议一个数据包最多只能传输8个字节。通过CAN总线传输轮询消息,在100K的CAN标准波特率下,CAN协议将轮询消息拆分到多个数据包再进行传输。由于每个数据包的字节数最多只能为8,传输每个数据包的耗时短,总线的效率可随之提高。在其他实施例中,通信设备200也可以采用其他CAN波特率,如 10K/20K/50K/125K/250K/500K/800K/1000K等。
其中,第一控制器21包括载波管理控制器(MCMC),第二控制器22包括增强模块管理控制器(EMMC);在其他实施例中,第一控制器21和第二控制器22可以为其他控制器,在此不再赘述。
在其他实施例中,通信设备200中的第一总线23和第二总线24均可为CAN总线,且CAN总线通过在CAN协议中插入IPMI协议的部分内容实现承载轮询消息和/或上报消息,具体请参阅图4和图5。或者,通信设备200中的第一总线23和第二总线24均可为I2C总线,且I2C总线的组网方式为星型连接方式。
本实施例中,通过对总线连接方式的优化和总线协议的优化,改善通信设备200的传输效率;具体地,通过将I2C总线的组网方式优化为星型或网型方式,可以有效避免单节点故障影响整个总线通信的问题;通信设备200通过I2C总线承载轮询消息,通过CAN总线承载上报消息,从而解决了第一控制器21定期轮询消息和第二控制器22上报消息冲突的问题,同时也提高第一控制器21轮询第二控制器22的频率;进一步通过对CAN协议的优化,使得CAN总线可以承载上报消息和轮询消息,CAN总线也可以作为I2C总线的备份总线,当I2C总线出现故障时,CAN总线承载轮询消息,提高通信设备200的稳定性。
为解决上述技术问题,本申请还提供了一种通信设备,具体请参阅图6,图6是本申请通信设备另一实施例的结构示意图。
如图6所示,通信设备300包括第一控制器31、若干第二控制器32、若干第一总线33和第二总线34。
第一控制器31分别通过第一总线33和第二总线34与第二控制器32进行通信连接。其中,第一总线33是网型总线,第一控制器31通过第一总线33接收来自第二控制器32的消息,且通过第二总线34发送轮询消息至第二控制器32。
具体地,第一总线33为I2C总线,第二总线34为CAN总线。第一控制器31和若干第二控制器32通过第一总线33进行通信连接,且若干第一控制器31之间通过第一总线33进行通信连接,若干第二控制器32之间通过第一总线33进行通信连接。第一总线33的组网方式设置为网型连接方式。
如图6所示,第一控制器31和每个第二控制器32之间的I2C总线均采用独立节点连接。采用上述网型连接方式,第一控制器31在与多个第二控制器32发送轮询消息时,第一控制器31与某个第二控制器32之间的连接节点出现故 障,第一控制器31与这个第二控制器32之间无法正常通信。第一控制器31与其他第二控制器32之间的通信不会受到影响,仍然可以正常通信。
进一步地,若干第一控制器31之间采用I2C总线连接,若干第二控制器32之间采用I2C总线连接。
具体地,若干第一控制器31之间可以采用I2C总线建立通信关系,传输通信消息。进一步地,当某个第一控制器31与第二控制器32之间的通信节点出现故障,无法发送轮询消息,该第一控制器31可以通过其他第一控制器31转发通信消息,继续向第二控制器32发送轮询消息,从而提高通信设备300的稳定性。
具体地,若干第二控制器32之间可以采用I2C总线建立通信关系,传输通信消息。进一步地,当某个第二控制器32与第一控制器31之间的通信节点出现故障,无法发送上报消息,该第二控制器32可以通过其他第二控制器32转发通信消息,继续向第一控制器31发送轮询消息,从而提高通信设备300的稳定性。
在本实施例中,通信设备300的若干第一控制器31和若干第二控制器32之间采用网型连接的I2C总线,若干第一控制器31之间或若干第二控制器32之间均可以通过I2C总线建立通信连接;进一步地,第一控制器31还可以通过其他第一控制器31转发通信消息,第二控制器32还可以通过其他第二控制器32转发通信消息,提高通信设备300的稳定性。
以上对本申请实施例所提供的通信设备进行了详细介绍,本文中应用了具体个例对本申请的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本申请的方法及其核心思想;同时,对于本领域的一般技术人员,依据本申请的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本申请的限制。
Claims (12)
- 一种通信设备,其中,所述通信设备包括:第一控制器和若干第二控制器;若干第一总线和/或若干第二总线,所述第一控制器分别通过所述第一总线和所述第二总线与所述第二控制器进行通信连接;其中,所述第一总线是星型总线或网型总线,所述第一控制器通过所述第二总线接收来自所述第二控制器的消息,且通过所述第一总线发送轮询消息至所述第二控制器。
- 根据权利要求1所述的通信设备,其中,所述第一总线为I2C总线,所述第二总线为CAN总线。
- 根据权利要求2所述的通信设备,其中,所述第二总线作为所述第一总线的备份线路,当所述第一总线出现故障时,所述第一总线的通信消息由所述第二总线承载。
- 根据权利要求3所述的通信设备,其中,所述通信设备包括第三总线,所述第三总线作为所述第一总线或所述第二总线的备份线路;当所述第一总线或所述第二总线出现故障时,所述第一总线或所述第二总线的通信消息由所述第三总线承载。
- 根据权利要求3所述的通信设备,其中,所述第一控制器和所述第二控制器之间采用IPMI协议进行通信,所述第二总线承载IPMI消息。
- 根据权利要求5所述的通信设备,其中,当所述第一控制器通过所述CAN总线接收来自所述第二控制器的消息时,所述CAN总线协议的仲裁域包括响应从地址,所述CAN总线协议的数据域包括网络功能码、命令号和警报识别。
- 根据权利要求5所述的通信设备,其中,当所述第一控制器通过所述CAN总线发送轮询消息至所述第二控制器时,所述CAN总线协议的仲裁域包括响应从地址和索引,所述CAN总线协议的数据域包括网络功能码、命令号和数据字节。
- 根据权利要求5所述的通信设备,其中,所述第一控制器通过所述第一总线每秒发送20次以上轮询消息至所述第二控制器。
- 根据权利要求1所述的通信设备,其中,所述第一控制器包括载波管理控制器,所述第二控制器包括增强模块管理控制器。
- 根据权利要求1所述的通信设备,其中,所述第一总线和所述第二总线均为CAN总线,或所述第一总线和所述第二总线均为I2C总线。
- 根据权利要求1所述的通信设备,其中,所述第一控制器专门通过所述第一总线接收来自所述第二控制器的消息,专门通过所述第二总线发送轮询消息至所述第二控制器。
- 根据权利要求1所述的通信设备,其中,所述通信设备包括基站或服务器。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/122756 WO2020124575A1 (zh) | 2018-12-21 | 2018-12-21 | 一种通信设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2018/122756 WO2020124575A1 (zh) | 2018-12-21 | 2018-12-21 | 一种通信设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020124575A1 true WO2020124575A1 (zh) | 2020-06-25 |
Family
ID=71102471
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2018/122756 WO2020124575A1 (zh) | 2018-12-21 | 2018-12-21 | 一种通信设备 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2020124575A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101394301A (zh) * | 2007-09-21 | 2009-03-25 | 华为技术有限公司 | 小型电信和计算通用硬件平台系统、装置及其通信方法 |
EP2207304A1 (en) * | 2007-10-30 | 2010-07-14 | Huawei Technologies Co., Ltd. | General hardware platform, corresponding architecture system, and power supply method for advanced mezzanine card |
CN201576280U (zh) * | 2009-10-21 | 2010-09-08 | 北京国基科技股份有限公司 | 智能平台管理接口 |
CN106874228A (zh) * | 2017-01-23 | 2017-06-20 | 中航光电科技股份有限公司 | 基于i2c总线的控制器及通信方法、多控制器间的通信方法 |
-
2018
- 2018-12-21 WO PCT/CN2018/122756 patent/WO2020124575A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101394301A (zh) * | 2007-09-21 | 2009-03-25 | 华为技术有限公司 | 小型电信和计算通用硬件平台系统、装置及其通信方法 |
EP2207304A1 (en) * | 2007-10-30 | 2010-07-14 | Huawei Technologies Co., Ltd. | General hardware platform, corresponding architecture system, and power supply method for advanced mezzanine card |
CN201576280U (zh) * | 2009-10-21 | 2010-09-08 | 北京国基科技股份有限公司 | 智能平台管理接口 |
CN106874228A (zh) * | 2017-01-23 | 2017-06-20 | 中航光电科技股份有限公司 | 基于i2c总线的控制器及通信方法、多控制器间的通信方法 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5286346B2 (ja) | プロセス制御システムおよびアプリケーション情報を通信する方法 | |
US10523547B2 (en) | Methods, systems, and computer readable media for multiple bidirectional forwarding detection (BFD) session optimization | |
CN112491492B (zh) | 一种时隙协商的方法和设备 | |
CN102724030A (zh) | 一种高可靠性的堆叠系统 | |
JPH0616631B2 (ja) | ネットワ−クにおけるステ−ション装置 | |
JP7305882B2 (ja) | スロットネゴシエーション方法およびデバイス | |
EP2472793A1 (en) | Method, device and system for transmitting e1 bidirectional looped network data | |
KR101179431B1 (ko) | 이더캣 네트워크 시스템 및 이의 운용 방법 | |
JP2016500503A (ja) | プロトコル例外状態を用いたデータ伝送プロトコル | |
CN104486128A (zh) | 一种实现双控制器节点间冗余心跳的系统及方法 | |
CN101917318A (zh) | 一种高低速总线系统连接装置及高低速总线系统 | |
CN105337895A (zh) | 一种网络设备主机单元、网络设备子卡以及网络设备 | |
CN108462537B (zh) | 一种一主多从通信的实现方法 | |
CN103036724A (zh) | 状态信息传输方法、网络设备及组合设备 | |
CN111585791B (zh) | 一种数据同步配置方法、系统及存储介质 | |
WO2014044190A1 (zh) | 以太网数据传输速率的调整方法及装置 | |
US20050141555A1 (en) | Method for generating commands for network controller modules of peripheral devices | |
CN117149678A (zh) | 一种多主多从的rs485总线仲裁系统和方法 | |
WO2020124575A1 (zh) | 一种通信设备 | |
CN115174370B (zh) | 一种分布式混合数据确定性传输装置及方法 | |
CN101132337A (zh) | 一种基于e1传输的2m环路网络系统 | |
JP6118464B2 (ja) | ポートステータス同期化方法、関連のデバイス、及びシステム | |
US11438192B2 (en) | Managed switch with physically distributed ports | |
JP6499625B2 (ja) | 通信装置及び通信方法 | |
WO2018076903A1 (zh) | 一种动态时间分配方法及装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 18944121 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09/11/2021) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 18944121 Country of ref document: EP Kind code of ref document: A1 |