Direct data bus between modular devices

[0001] The present disclosure relates generally to information handling systems. More particularly, the present disclosure relates to communication between modular devices in data centers and similar environments.

[0002] As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use, such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.

[0003] Space constraints in conventional multi-module chassis architectures do not permit a direct connection between adjacent modules in a chassis bay once the adjacent modules have been placed into the chassis. The compact design of modular systems makes it practically impossible to access ports of a module from the rear or the sides, e.g., on a modular server that for cost reasons typically does not have any ports at its front side, to make cable connections, even if the chassis is not fully loaded. Accordingly, it would be desirable to have systems and methods that allow to overcome the accessibility problems and other shortcomings of existing modular designs, while maintaining and, ideally, increasing communication bandwidth.

[0016] In the following description, for purposes of explanation, specific details are set forth in order to provide an understanding of the disclosure. It will be apparent, however, to one skilled in the art that the disclosure can be practiced without these details. Furthermore, one skilled in the art will recognize that embodiments of the present disclosure, described below, may be implemented in a variety of ways, such as a process, an apparatus, a system/device, or a method on a tangible computer-readable medium.

[0017] Components, or modules, shown in diagrams are illustrative of exemplary embodiments of the disclosure and are meant to avoid obscuring the disclosure. It shall also be understood that throughout this discussion that components may be described as separate functional units, which may comprise sub-units, but those skilled in the art will recognize that various components, or portions thereof, may be divided into separate components or may be integrated together, including, for example, being in a single system or component. It should be noted that functions or operations discussed herein may be implemented as components. Components may be implemented in software, hardware, or a combination thereof.

[0018] Furthermore, connections between components or systems within the figures are not intended to be limited to direct connections. Rather, data between these components may be modified, re-formatted, or otherwise changed by intermediary components. Also, additional or fewer connections may be used. It shall also be noted that the terms “coupled,” “connected,” “communicatively coupled,” “interfacing,” “interface,” or any of their derivatives shall be understood to include direct connections, indirect connections through one or more intermediary devices, and wireless connections. It shall also be noted that any communication, such as a signal, response, reply, acknowledgement, message, query, etc., may comprise one or more exchanges of information.

[0019] Reference in the specification to “one or more embodiments,” “preferred embodiment,” “an embodiment,” “embodiments,” or the like means that a particular feature, structure, characteristic, or function described in connection with the embodiment is included in at least one embodiment of the disclosure and may be in more than one embodiment. Also, the appearances of the above-noted phrases in various places in the specification are not necessarily all referring to the same embodiment or embodiments.

[0020] The use of certain terms in various places in the specification is for illustration and should not be construed as limiting. The terms “include,” “including,” “comprise,” and “comprising” shall be understood to be open terms and any examples are provided by way of illustration and shall not be used to limit the scope of this disclosure.

[0021] A service, function, or resource is not limited to a single service, function, or resource; usage of these terms may refer to a grouping of related services, functions, or resources, which may be distributed or aggregated. The use of memory, database, information base, data store, tables, hardware, cache, and the like may be used herein to refer to system component or components into which information may be entered or otherwise recorded. The terms “data,” “information,” along with similar terms, may be replaced by other terminologies referring to a group of one or more bits, and may be used interchangeably. The words “optimal,” “optimize,” “optimization,” and the like refer to an improvement of an outcome or a process and do not require that the specified outcome or process has achieved an “optimal” or peak state.

[0022] It shall be noted that: (1) certain steps may optionally be performed; (2) steps may not be limited to the specific order set forth herein; (3) certain steps may be performed in different orders; and (4) certain steps may be done concurrently.

[0023] Any headings used herein are for organizational purposes only and shall not be used to limit the scope of the description or the claims. Each reference/document mentioned in this patent document is incorporated by reference herein in its entirety.

[0024] It shall also be noted that although embodiments described herein may be within the context of modular devices located in a chassis, aspects of the present disclosure are not so limited. Accordingly, the aspects of the present disclosure may be applied or adapted for use in other contexts that do not involve a chassis.

[0025] In this document, the terms “bay,” “module bay” may be used interchangeably. Similarly, the terms “module” and “modular device” are used interchangeably. “Connection” refers to any type of connection, including electrical, mechanical, optical, and electro-optical connection.

[0026] FIG. 1 depicts a common cassis 100 that is partitioned into four module bays 104-110 denoted as “module bay 1” through “module bay 4.” Each of bay (or slot) 104-110 is designed to accommodate a removable modular device, such as an input/output module that once placed into chassis 100 may communicate (112) with one or more other devices coupled to chassis 100, e.g., over backplane 120 (or mid-plane), orthogonal connectors, or similar chassis technology that facilitates modular connectivity.

[0027] As depicted in FIG. 2, each removable module 212-218 may be inserted or mounted into a respective module bay that is designed to accommodate a module and locked in place by using opposing insertion/removal lever 206, 208, disused in greater detail below with reference to FIG. 5. Chassis 200 in FIG. 2 comprises module bays 104-110 and backplane 120. Backplane 120 is designed to provide connectivity between modules (or sleds) 212-218, e.g., network servers, network switches, Fibre channel switches, management modules, pass-thru modules, fans, power supplies, storage devices, other types of modules that can be inserted into bays 104-110. Each module (e.g., 212) contains an interface (e.g., 210) that is designed to couple to backplane 120. Interface 210 may be a bus port, an orthogonal connection that allows access to the back of chassis 200, or any other standardized interface known in the art. In operation, modules 212-218 placed into adjacent bays 104-110 may communicate with each other over common backplane 120 connection. For example, module 212 may use backplane 120 to communicate with non-adjacent module 218 using any suitable communication known the relevant art.

[0028] FIG. 3 shows a common modular chassis 300 that contains network interface 330 to communicate with an external network 350, e.g., the cloud. A person of skill in the art will understand that network interface 330 itself may also be implemented in a modular fashion.

[0029] In operation, at some point, virtually all data traffic must traverse backplane 120 (or other device) in order to communicate with other entities, even when data is passed only between adjacent modules. For example, modules 214 and 216 communicate with each other over communication path 310, i.e., via backplane 120. In practice, data traveling back and forth on backplane 120 introduces a greater latency than if adjacent modules could directly communicate with each other, e.g., over a common interface.

[0030] Therefore, various embodiments presented herein allow modular devices, such as modules in chassis to directly communicate with each other without additional cabling, without having to open the chassis to make a connection, and without having to communicate with each other over a single backplane as in existing architectures.

[0031] FIG. 4A and FIG. 4B illustrate an exemplary coupling mechanism for establishing a communication between modules, according to embodiments of the present disclosure. FIG. 4A comprises wedge 410, plate 411, spring 412, spring holder 414, and a latch assembly that may comprise lock latch 402, connector engaging arm 408, insertion/removal lever 406, and lock post 404 that limits the motion of lock latch 402. Although not shown in FIG. 4A, wedge 410, which represents any type of housing, may comprise one or more connectors, i.e., any type of electrical, optical, electro-optical, or other connector, such as copper, fiberoptic, or silicon photonic connector to enable a fiberoptic connection between two fiberoptic cables, a silicon wave guide connection between silicon wave guide couplers, and the like. As depicted in FIG. 4A spring 412 is in a resting position.

[0032] In operation, in embodiments, as indicated by the arrows in FIG. 4B, once pivotable lever 406 is rotated, here, in a counter-clockwise direction around a pivot axis, e.g., by manual operation or by an actuator assembly (not shown), connector engaging arm 408 may exert force on wedge 410 such as to move plate 411 and, thus, wedge 410 outward of opening 418, thereby, stretching spring 412. In embodiments, pushing wedge 410 in direction of an adjacent module (not shown) may allow one or more connectors in wedge 410 to mate with one or more connectors located in an adjacent module (not shown) located near wedge 410.

[0033] In embodiments, a locking mechanism may, in response to lock latch 402 engaging with lock post 404, advantageously, further establish a desired communicative connection, e.g., at the same time that lever 406 is being releasably locked in place by lock post 404.

[0034] It is understood that lever 406 may be rotated in any suitable direction to enable wedge 410 to move in a desired direction to make a communicative connection. It is further understood that similar or different mechanisms—whether locking or non-locking—may be employed to create a removable mechanical/and or electrical connection between wedge 410 and an adjacent module. For example, as a person of skill in the art will appreciate, in embodiments, wedge 410 may be spring-loaded, i.e., spring 412 may be compressed, when wedge 410 is engaged to facilitate a suitable mechanical/electrical contact between wedge 410 and a counterpart component. Conversely, spring 412 may be decompressed when wedge 410 is in a resting position. In addition, any type of actuator known in the art, e.g., a software-controlled actuator may be used to facilitate the rotation or motion, e.g., a suitable linear motion, or any combination thereof that may be enabled by any motion translation mechanism known in the art, e.g., to ensure the reliability, repeatability, and safety of the resulting connection.

[0035] FIG. 5 illustrates exemplary modules comprising a coupling mechanism for establishing a communication between modules according to embodiments of the present disclosure. In embodiments, module 516 in FIG. 5 comprises opposing levers 406, 506, wedge 510, and module 514 comprises receptacle 520 designed to accept wedge 510. In embodiments, an assembly comprising wedge 510 and spring 412 allows wedge 510 to withdraw into module 516, e.g., until wedge 510 reaches receptacle 520 on module 514, at which point spring-loaded wedge 510 injects itself into receptacle 520, thereby, enabling a connection between a connector in wedge 510 and a complimentary connector in receptacle 520.

[0036] As an example, assuming that module 514 is stationary, module 516 may be coupled to module 514 by moving module 516 next module 514, e.g., by sliding module 516 next to module 514 along a common axis to position wedge 510 near receptacle 520, e.g., until wedge 510 and receptacle 520 are aligned, such as to allow wedge 510 to slide into receptacle 520 as guided by the complimentary shapes of both wedge 510 and receptacle 520. In embodiments, wedge 510 and receptacle 520 may be shaped in a manner such that wedge 510, acting like a guide, may slide in and out of receptacle 520. In effect, this allows any number of modules (e.g., 514 and 516) to effortlessly mate (e.g., in adjacent slots to establish a connectivity between the adjacent devices as well as a backplane connectivity via interface 530) at otherwise inaccessible locations and without the need for additional tools.

[0037] In embodiments, in line with the lever action described above with reference to FIG. 4A and FIG. 4B, levers 406, 506 in FIG. 5 may perform a dual function of locking module 516 in place and establish an communicative connection between module 514 and module 516. For example, an electrical connection may be established between module 514 and module 516 at the same time when lever 406 and/or lever 506 are activated, e.g., by a user. In embodiments, this may be accomplished by using a mechanical assembly (not shown) that uses an action of or one or more insertion/removal levers (e.g., 406) to also enable the electrical connection, e.g., by ensuring a proper seating of one or more connections of a direct bus that couples modules 514 and 516. It is understood any devices herein may comprise differing components and vary in performance and functionality, size, and shape.

[0038] FIG. 6 illustrates a modular system comprising four exemplary modules that comprise coupling mechanisms according to embodiments of the present disclosure. Modular system 600 may comprise a chassis, cage, or any other enclosure that may comprise wedge 510, spring 412, backplane connection 420, and modules 512-518. In embodiments, modular system 600 may accept any type and combination of devices, components, or modules 512-518, e.g., network servers, network switches, or storage devices. In data center type implementations, system 600 may allow users to customize a data center.

[0039] In embodiments, wedge 510 may be used to mate two adjacent modular devices (e.g., modules 514, 516) by establishing a direct bus connection. In this manner, data may directly pass between modular devices without the need for connectivity path 310 involving backplane 420, while still allowing for primary backplane connection 420. Advantageously, by enabling module 514 and module 516 to communicate directly over a shared link, bandwidth and dedicated ports (e.g., switch ports) on backplane 420 may be freed, thus, alleviating traffic flowing on backplane connection 420, i.e., increasing the bandwidth available to backplane connection 420 and allowing better control of data traffic. In addition, communication latency may be reduced as information, such as control signals, need not travel across multiple interfaces involving common backplane 420.

[0040] It is noted that although only a single direct connection between module 514 and module 516 is shown in FIG. 6, any number and type of connections may be implemented in this or a similar matter at various locations on a module. Further, unlike existing designs that are limited to communicating over a common backplane, module 514 and module 516 may communicate on different paths over different busses and in different directions, in addition to common backplane 420. Furthermore, embodiments allow module 514 and module 516 to communicate with each other and other devices in chassis 600, even if one of a number of paths/interfaces becomes temporarily congested or permanently unavailable for data traffic. Advantageously, this allows for link failover and load balancing techniques to be applied.

[0041] It is understood that although not shown, system 600 may comprise printed circuit board elements, additional communication or processing elements, etc., and may use any communication or management protocol known in the art.

[0042] FIG. 7 depicts an alternative coupling mechanism for establishing a communication between two modules, according to embodiments of the present disclosure. In embodiments, coupling mechanism 700 comprises connector assembly 702, connector(s) 704, and receptacle 710. Connector 704 may comprise silicon photonic or fiberoptic waveguides or copper connections designed to couple to receptacle 710.

[0043] As depicted in FIG. 7, connector assembly 702 may comprise a concave portion or an indented tip that extends beyond the edge of connector 704. Receptacle 710 may have a convex or outward connection. In embodiments, the concave portion of concave portion may protect connector 704, e.g., from physical impact and potential damage when connector 704 is inserted into receptacle 710 to mate with receptacle 710.

[0044] It is understood that similar or different mechanisms may be used to facilitate removable connections between adjacent modules, e.g., to allow for ease of installation. For example, connector assembly 702 may be implemented using other shapes, e.g., those illustrated in FIG. 8A and FIG. 8B, which depict alternative coupling mechanisms for establishing a communication between two modules according to embodiments of the present disclosure. Connector assembly 802 in FIG. 8A has a shape that resembles a half circle. In embodiments, such shape may advantageously reduce friction when connector assembly 802 is inserted into receptacle 810. Receptacle 810 may have a complementary half-circle shape.

[0045] In embodiments, similar to FIG. 7, a connector assembly may comprise a concave portion or an indented tip that extends beyond the edge of connector 852, as in shown in FIG. 8B. FIG. 9A and FIG. 9B illustrate a waveguide coupling mechanism for establishing a communication between two modules according to embodiments of the present disclosure. The coupling mechanism may comprise connector 902, connector pins or guide pins 932, waveguide 920, 934, gear assembly 936, receptacle 910, and receive pin 924. Connector 902 in FIG. 9A may be implemented as a waveguide coupler. Gear assembly 936 may be controlled by a set of actuators (not shown) that may be driven by software or firmware. FIG. 10A and FIG. 10B illustrate an alternative waveguide coupling mechanism according to embodiments of the present disclosure. Components similar to FIG. 9A and FIG. 9B are labeled in a similar manner. As depicted in FIG. 10A and FIG. 10B, connector 902 may have a flat interface to make a flush connection with receptacle 1010.

[0046] FIG. 11 depicts a flowchart for an exemplary process for establishing a communication between modular devices according to embodiments of the present disclosure. In embodiments, process 1100 for coupling modular electronic devices may begin when, in response to a first module, which comprises a connector assembly, being moved along an enclosure of a second module, the connector assembly may be caused to at least partially retract (1105) inwardly into the first module. The connector assembly may comprise a connector and a connector mating interface. The enclosure of the second module may comprise a receptacle assembly that may comprise a receptacle and a receptacle mating interface.

[0047] In response to the connector assembly at least partially aligning with the receptacle assembly, the connector assembly maybe caused to move (1110) into the receptacle assembly.

[0048] Finally, in response to the connector assembly moving into the receptacle assembly, a releasable connection may be established (1115) between the connector mating interface and a receptacle mating interface, e.g., along a mating axis.

[0049] FIG. 12 depicts a block diagram of an information handling system, according to embodiments of the present disclosure. It will be understood that the functionalities shown for system 1200 may operate to support various embodiments of the present disclosure—although it shall be understood that such system may be differently configured and include different components, additional components, or fewer components.

[0050] The information handling system 1200 may include a plurality of I/O ports 1205, a network processing unit (NPU) 1215, one or more tables 1220, and a central processing unit (CPU) 1225. The system includes a power supply (not shown) and may also include other components, which are not shown for sake of simplicity.

[0051] In one or more embodiments, the I/O ports 1205 may be connected via one or more cables to one or more other network devices or clients. The network processing unit 1215 may use information included in the network data received at the node 1200, as well as information stored in the tables 1220, to identify a next device for the network data, among other possible activities. In one or more embodiments, a switching fabric may then schedule the network data for propagation through the node to an egress port for transmission to the next destination.

[0052] One skilled in the art will recognize no computing system or programming language is critical to the practice of the present disclosure. One skilled in the art will also recognize that a number of the elements described above may be physically and/or functionally separated into modules and/or sub-modules or combined together.

[0053] It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting to the scope of the present disclosure. It is intended that all permutations, enhancements, equivalents, combinations, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present disclosure. It shall also be noted that elements of any claims may be arranged differently including having multiple dependencies, configurations, and combinations.