CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application Serial No. 61/713,968, filed October 15, 2012, and titled "COMBINED DEVICE MANAGEMENT SYSTEM (CDMS)," the contents of which are incorporated herein in its entirety.

FIELD OF THE INVENTION

[0002] The disclosed subject matter pertains to systems and methods for managing multiple devices, and more particularly, systems and methods that employ a single device to command and control multiple terminals and network devices.

BACKGROUND

[0003] Electronic devices often need to communicate with each other over different types of communication links. In military applications, various communications standards may be required to allow different devices to communicate over wired and/or wireless communications channels.

BRIEF SUMMARY

[0004] In one implementation, a device management system includes a common bus configured to be communicatively coupled to a plurality of devices. The device management system also includes a plurality of connectors. Each of the connectors is configured to communicatively couple the common bus to a respective one of the devices and includes a plurality of conducting elements. The plurality of conducting elements transmits signals between the common bus and the respective one of the devices. The signals include: at least one power supply signal, at least one voice signal, at least one display signal, at least one serial communication signal, at least one request signal, at least one reset signal, at least one security signal, and at least one address signal.

[0005] In another implementation, a device management system includes a controller card. The controller card includes at least one processor configured to manage communications between devices communicatively coupled to the device management system and at least one connector. The at least one connector is configured to communicatively couple the controller to at least one input/output device and includes a plurality of conducting elements. The plurality of conducting elements transmits signals between the controller card and the at least one input/output device. The signals include: at least one power supply signal, at least one ground signal, at least one security signal, at least one display signal, and at least one voice signals.

[0006] In a third implementation, a device management system includes a low volume terminal (LVT) card. The LVT card includes at least one connector configured to communicatively couple the LVT card to at least one input/output device. The at least one connector also includes a plurality of conducting elements transmitting signals between the LVT card and the at least one input/output device. The signals include: at least one power supply signal, at least one standby signal, at least one ground signal, at least one zeroize signal, at least one long term transmit inhibit (LTTI) signal, at least one alarm signal, at least one voice signal, at least one push-to-talk signal, at least one voice signal, and at least one power control signal.

[0007] In a fourth implementation, a device management system includes a small tactical terminal (STT) card. The STT card includes at least one connector configured to communicatively couple the STT card to at least one input/output device. The connector includes a plurality of conducting elements transmitting signals between the STT card and the at least one input/output device. The signals include: at least one zeroize signal, at least one ground signal, at least one network selection signal, at least one voice signal, and at least one speaker output signal.

[0008] In a fifth implementation, a device management system includes an STT card. The STT card includes at least one connector configured to communicatively couple the STT card to at least one input/output device. The connector includes a plurality of conducting elements transmitting signals between the STT card and the at least one input/output device. The signals include: at least one power signal, at least one ground signal, at least one channel fail signal, at least one long term transmit inhibit (LTTI) signal, at least one emergency signal, at least one small tactical terminal-V (STT-V) fail signal, and at least one power control signal.

[0009] These and other aspects of the present disclosure will become more apparent from the following detailed description of embodiments of the present disclosure when viewed in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] FIG. 1 illustrates an overview of the CDMS, according to aspects of the presently disclosed subject matter; [0011] FIG. 2 illustrates a CDMS interfacing with one or more remote physical devices via one or more equipment connections and with a web browser via a network connection according to aspects of the presently disclosed subject matter;

[0012] FIG. 3 illustrates an exemplary 48-pin common bus connector;

[0013] FIG. 4 illustrates an exemplary controller card external connector layout;

[0014] FIG. 5 illustrates an exemplary low volume terminal (LVT) card external connector layout;

[0015] FIG. 6 illustrates an exemplary 4-pin connector operative to mate with a 4-pin connector on an LVT card;

[0016] FIG. 7 illustrates an exemplary small tactical terminal (STT) card external connector layout; and

[0017] FIG. 8 illustrates a schematic of an exemplary CDMS card.

DETAILED DESCRIPTION

[0018] A Combined Device Management System (CDMS) as disclosed herein may be used to manage communications between different devices. Using a controller card, external devices may be added to and/or removed from the CDMS without the need for time- consuming programming and/or reconfiguration. The remote devices and controller card may communicate via a common bus, allowing the CDMS to maintain a small footprint and allowing the controller card to efficiently manage communication and other requests from the external devices. The chassis of the CDMS is configured to be easily stacked and to easily accommodate a number of external devices while maintaining a small footprint. Additionally, the CDMS may be configured to allow a user to remotely monitor and/or control CDMS operations via a network interface. To achieve some of these advantages, specific connector pin configurations are used, allowing for efficient and intelligent signal grouping. Further, a common pin configuration is used for devices connecting to the common bus, allowing a plurality of devices to easily communicate via the common bus.

[0019] According to aspects of the presently disclosed subject matter, systems and methods employ a CDMS. As will be described in further detail below, the CDMS disclosed herein allows multiple devices to communicate with each other over a common bus, and allows new remote devices to be added or removed from the CDMS without requiring additional programming or configuration.

[0020] FIG. 1 illustrates an overview of an exemplary CDMS 100. In certain implementations, the CDMS 100 includes a single CDMS controller 10 that provides command and control capability for multiple remote devices (e.g., Tactical Data Link (TDL) terminals such as low volume terminals (LVTs) and or small tactical terminals (STTs), TDL support equipment, and network equipment). Further, the CDMS controller 10 may support multiple types of TDL terminals and network devices from a single device over a single web interface 30, (e.g., via a desktop web browser, a laptop web browser, a mobile web browser, etc.), allowing a user to control and/or monitor connected terminals and network devices locally or remotely.

[0021] In certain implementations, the CDMS controller 10 may use a single IP address to communicate with multiple devices, and to allow a user to configure and/or customize the CDMS 100. A user may configure the IP address of the CDMS controller 10 and install/add any required cards (e.g., LVTs and/or STTs) in any one of multiple, (e.g., six), on-board chassis slots. The cards may communicate over a common bus using communication request lines so that each card can communicate without interfering with the others. Voice signals from all cards with voice technology and an optional front panel voice connector may also be transmitted over the common bus. In other implementations, the CDMS controller 10 may communicate with other devices and/or be accessed via a plurality of IP addresses.

[0022] The CDMS controller 10 may include a single card used to control the operations of CDMS 100. Other cards that interface with the CDMS controller 10 may be optional. For example, in certain implementations, the CDMS controller 10 may communicate with one or more LVTs, while in other implementations, the CDMS controller 10 may only communicate with STTs. In certain implementations, the CDMS controller 10 may communicate with combinations of one or more LVTs and STTs.

[0023] The web interface 30 may automatically display information about each card installed in the CDMS 100 upon startup and initialization of the CDMS controller 10. The web interface 30 may also optionally include a control panel.

[0024] The CDMS 100 is scalable, and in certain implementations, its chassis may be stacked to expand the number of devices 50 (e.g., TDL terminals, TDL support equipment, and network equipment) that can be controlled from a single CDMS controller 10 while still maintaining a small footprint. In certain implementations, up to 127 devices 50 may be controlled by a CDMS controller 10 inside the CDMS 100.

[0025] The CDMS 100 is expandable and adaptable to support the addition and/or removal of cards during operation and is configured to support new control needs as they are identified. In some implementations, the CDMS 100 may be expanded using an expansion cable configured to allow additional devices 50 to be controlled by the CDMS controller 10. Further, in certain implementations, the CDMS 100 may employ a low profile 1U chassis for a small form factor.

[0026] FIG. 2 illustrates a CDMS interfacing with one or more remote physical devices via one or more equipment connections and with a web browser via a network connection, according to aspects of the present disclosed subject matter. The CDMS shown in FIG. 2 may, for example, be similar to CDMS 100 described above with respect to FIG. 1. The CDMS Chassis 205, for example, includes a controller card 210, one or more equipment cards 230, a liquid crystal display (LCD) interface 270, an RS-232 bus 280, and an RS-485 bus 240. The buses 240 and 280 are configured to allow communications between CDMS components such as, for example, the controller card 210, the one or more equipment cards 230, and the LCD interface 270. In the implementation of FIG. 2, the controller card 210 is similar to CDMS controller 10 described above with respect to FIG. 1. Further, the equipment cards 230 may be similar to the devices 50 that are controlled by and communicate with the CDMS controller 10, as described above with respect to FIG. 1.

[0027] In certain implementations, controller software resides on a small embedded computer (not shown) on the controller card 210. More specifically, the controller software may be stored on a non-transitory tangible medium such as, for example, a flash memory, a CD-ROM, a floppy disk, a hard drive, a digital versatile disk (DVD), or on other memory devices. The controller software may communicate with hardware interfaces using General Purpose Input Outputs (GPIOs) exposed by the Linux based operating system. The controller software may also support a small web server for control, configuration and/or status information via external web-browsers, such as a web browser(s) 220. In certain implementations, the web browser(s) 220 may display the web interface 30 described above.

[0028] The controller card 210 communicates with the web browser(s) 220 via a network connection 225. In certain implementations, the network connection may be an Ethernet connection. In other implementations, other types of connections (e.g., WiFi, Bluetooth, DSL, USB, etc.) may be used to connect the controller card 210 with the web browser(s) 220.

[0029] The controller card 210 may communicate with the equipment cards 230 (e.g., LVT cards and/or STT cards) via a common serial bus such as the bus 240. Use of a common bus allows the CDMS to maintain a small footprint and allows the controller card 210 to efficiently manage communication and other requests from the external devices. In certain implementations, all communications between the controller card 210 and the equipment cards 230 take place over the bus 240. Further, equipment cards 230 may communicate with external devices 250 such as, for example, monitoring sensors, communications terminals, cameras, etc., via equipment connections 260.

[0030] In certain implementations, the controller card 210 may also be configured to communicate with an LCD interface 270 coupled to the CDMS via a serial bus such as RS- 232 Bus 280. The LCD interface 270 may be coupled to the controller card and locally display information regarding the CDMS. For example, in an exemplary implementation, the LCD 270 is configured to display information about the status of the controller card 210 and/or other information about the equipment cards 230 coupled to the controller card 210. In certain implementations, this information may be different from the control and or monitoring information displayed on the web browser(s) 220, while in other implementations, the information displayed on the LCD 270 and the web browser(s) 220 may be similar.

[0031] Communications between CDMS cards (e.g., communications between the controller card 210 and one or more of the equipment cards 230 via the bus 240) may use a custom packet structure. In certain implementations, the packets may use the following structure, where '$' indicates the beginning of a new message, '*" indicates the beginning of a Cyclic Redundancy Check, and '\η' represents the end of a message:

$<Sender Address>,<Receiver Address>, <Message ID>, <Message Body>*<CRC Check>\n

[0032] The sender address represents the address of the physical slot address of the message sender. This value is a two character, hex encoded value in the range: [01- FF], with address [00] reserved for broadcast messages.

[0033] The receiver address represents the address of the intended recipient of the message. This value is a two character, hex encoded value in the range: [01, FF], with address [00] reserved for broadcast messages.

[0034] The Message ID is a unique identification number generated by a controller card, such as, for example, controller card 210. The valid range is that of an unsigned short [0,65535]. This is represented by a string in the actual message. The Message ID is used to facilitate bi-directional checking of messages that require responses and therefore need to be matched with some request within the controller card.

[0035] The content of the message body varies according to the type of message. In general, the message body is a series of comma delineated values. The first value is a verb, representing the type of action to perform or what action was performed. For example, if the controller card 210 would like to request discrete values '5' and '6' from an equipment card 230 (e.g., an LVT or STT), the message body would have the following format: GET,5,6

[0036] And the card response would have the following format:

GET_RES,5=0,6=1

[0037] In this implementation, return values are key-value pairs delineated by the equals sign. Also, the message structure allows the controller card 210 to request or update many discrete values with the same message. Similar to the example above is the SET action. A SET Message body for setting discretes '2' and '3 ' would have the following format:

SET,2=1,3=1

[0038] And the corresponding card response (that indicates that the value changes were successful):

SET_RES,2= 1,3=1

[0039] Valid verb types for a message body according to the present disclosure are listed below in Table 1 :

Table 1: Message Body Verb Types

[0040] FIG. 3 illustrates an exemplary 48-pin common bus connector. Connector 300 may be used, for example, with the bus 240 described above to provide the controller card 210 and/or the equipment card(s) 230 a connection to power supply pins and/or to common bus pins. These common bus pins may provide a variety of functionalities. For example, certain pins may be used for communication requests, allowing cards to communicate over the bus without interfering with other cards. For example, certain pins may allow communications between the controller card 210 and one or more of the equipment cards 230 (e.g., LVTs, and/or STTs). Further, certain pins may allow the controller card 210 to transmit or receive requests from new equipment cards that are added to a CDMS and/or allow the controller card to perform necessary operations when an equipment card is removed from the CDMS. Advantageously, cards may be added or removed from a CDMS without the need for additional programming or configuration, and these processes may be handled using communications via the connector 300. Other pins may allow a card to be reset. Certain pins may also support voice input and/or output functionality. An exemplary pinout for the connector 300 is listed below in Table 1.

Table 2: Common Bus Connector Pinout

[0041] FIG. 4 illustrates an exemplary controller card connector layout. A connector 400 is coupled to a controller card such as, for example, the controller card 210 and may include a D-Subminiature connector 410, a connector 420, and Light Emitting Diodes (LEDs) 430-450. PWR LED 430 may indicate when a controller card is powered on. The TX LED 440 and RX LED 450 may indicate when the controller card is transmitting and receiving data, respectively. In certain implementations, the connectors 410 and 420 may be female-type connectors. Further, the connector 410 may be a 15 pin connector, and connector 420 may be a standard network connector, such as, for example, an RJ45 connector.

[0042] The connector 410 may provide the controller card access to pins providing a variety of functionality and allow the connector card to connect to and communicate with a variety of external circuitry, including circuitry distinct from any attached LVTs and/or STTs. For example, a CDMS may incorporate a security system that may be used to control and monitor the security state of the device. If there is a legitimate security breach, the controller card may be configured to handle necessary security functions which are determined by the software modules for each card. In certain implementations, a security circuit coupled to the controller card may include a security relay that has 2 states, SECURE (energized) and NOT SECURE (not energized). The state of this relay is controlled by its Security Status, Security Bypass, and Security Output components.

[0043] In certain implementations the controller card may also be configured to communicate with an LCD panel (e.g., the LCD interface 270) on the CDMS. The LCD panel may, for example, be configured to display information about the status of the CDMS and/or other information of interest to a user. Again, this information may be distinct from the information displayed on a web interface such web interface 30, and may be displayed locally on the CDMS. In these implementations, the connector 410 may provide the controller card access to pins allowing the controller card to transmit and/or receive data from an incorporated LCD panel.

[0044] As described above, voice signals from cards with voice technology and an optional front panel voice connector may be implemented in certain implementations of the disclosed subject matter. Therefore, the connector 410 may also provide the controller card with access to pins carrying voice data signals.

[0045] An exemplary pinout for the connector 410 is listed below in Table 3: Table 3: Controller Card Connector 410 Pinout

[0046] As described above, a controller card, (e.g., the controller card 210) may be monitored and/or controlled remotely over a network connection. In certain implementations, the network connection may be an Ethernet connection. In addition to Ethernet controller circuitry, the controller card may also include a network connector such as the connector 420. An exemplary pinout for the connector 420 is listed below in Table 4:

Table 4: Controller Card Connector 420 Pinout

[0047] FIG. 5 illustrates an exemplary LVT card external connector layout. The LVT card connector 500 is coupled to an LVT card, and like controller card connector 400 described above, the LVT card connector 500 may include LEDs that indicate power, data/signal transmission, data/signal reception, etc. More specifically, the PWR LED 530 may indicate when the LVT card is powered on. The TX LED 540 and The RX LED 550 may indicate when the LVT card is transmitting and receiving data, respectively. Additionally, Connector 500 may include D-Subminiature connector 510, and 4 Pin female connector 520.

[0048] Connector 510 provides the LVT card access to pins providing a variety of functionality. Exemplary LVT card functionality is described in further detail below. Further, the LVT card may operate in a variety of different power states including, for example, ON, OFF, and Standby States.

[0049] In certain implementations, the LVT card may support zeroize functionality, allowing the card to retain or erase cryptographic data. The LVT card may also be configured to incorporate Long Term Transmit Inhibit (LTTI) functionality. LTTI functionality may include initiating the process of shutting down transmissions by the LVT card, including halting RF emission and taking necessary data processing actions so that normal functioning can be resumed as required. [0050] In certain implementations, the LVT card may include an air filter alarm and an air filter monitoring circuit. Voice and/or voice PTT circuitry may also be implemented, including both local and/or remote implementations. An exemplary pinout for connector 510 is listed below in Table 5 :

Table 5: Connector 510 Pinout

[0051] Connector 520 may provide the LVT card with access to pins carrying analog voice signal data. An exemplary pinout for connector 520 is listed below in Table 6:

Table 6: Connector 520 Pinout

[0052] FIG. 6 illustrates an exemplary 4-pin connector operative to mate with a 4-pin connector (e.g., the connector 520) on an LVT card. Connector 600 may include sleeve 610, tip 620, Ring 630, and Ring 640. Sleeve 610 may connect with pin 1 of connector 520 described above with respect to FIG. 5, tip 620 may connect with pin 2 of connector 520, Ring 630 may connect with Pin 3 of connector 520, and Ring 640 may connect with pin 4 of Connector 520.

[0053] FIG. 7 illustrates an exemplary small tactical terminal (STT) card external connector layout. The STT card connector 700 is coupled to an STT card, and like controller card connector 400 and LVT card connector 500, the connector 700 may include LEDs that indicate power, data/signal transmission, data/signal reception, etc. More specifically, PWR LED 730 may indicate when the STT card is powered on. TX LED 740 and RX LED 750 may indicate when the STT card is transmitting and receiving data, respectively. Additionally, the connector 700 may include D-Subminiature connectors 710 and 720.

[0054] The connector 710 may provide the STT card incorporated access to pins providing a variety of functionality. In certain implementations, the STT card may support zeroize functionality, allowing the card to retain or erase cryptographic data. Voice and/or voice PTT circuitry may also be implemented, including both local and/or remote implementations. The STT card may additionally support speaker output capabilities. An exemplary pinout for connector 710 is listed below in Table 7:

Table 7: Connector 710 Pinout

Pin Signal Name Description Specification I/O

CHANNEL VOICE

10 Push-To-Talk return Ground N/A PTT RTN

Logic 0: +3 V to +15 V

CHANNEL CONSOLE Console control

11 Logic 1 : -3 V to -15 V Out TX messages transmit

Baud: 57600 bps

12 N/A N/A N/A N/A

CHANNEL CONSOLE Console Control

13 Ground N/A GND Ground

REMOTE VOICE TX 0.25Vrms to 1.4Vrms ±3dB

14 Remote Voice Tx (+) In (+) Source Impedance: 150Ω ±10%

REMOTE VOICE TX (- 0.25Vrms to 1.4Vrms ±3dB

15 Remote Voice Tx (-) In ) Source Impedance: 150Ω ±10%

Source Impedance: 600Ω ± 10%

REMOTE VOICE RX

16 Remote Voice Rx (+) MIDS Voltage Level (Nominal): 7Vrms Out (+)

Apache Mode (Nominal): 0.387Vrms

Source Impedance: 600Ω ± 10%

REMOTE VOICE RX (-

17 Remote Voice Rx (-) MIDS Voltage Level (Nominal): 7Vrms Out )

Apache Mode (Nominal): 0.387Vrms

Transmit Enable: GND; Ρ<360Ω

18 REMOTE VOICE PTT Push-to-Talk Discrete In

Transmit Disable: Open >100kΩ

REMOTE VOICE PTT

19 Push-to-Talk Return Ground N/A RTN

Source Impedance: 600Ω ± 10%

20 SPEAKER OUT (+) Speaker Output (+) MIDS Voltage Level (Nominal): 7Vrms Out

Apache Mode (Nominal): 0.387Vrms

Source Impedance: 600Ω ± 10%

21 SPEAKER OUT (-) Speaker Output (-) MIDS Voltage Level (Nominal): 7Vrms Out

Apache Mode (Nominal): 0.387Vrms

22 N/A N/A N/A N/A

23 N/A N/A N/A N/A

24 N/A N/A N/A N/A

25 N/A N/A N/A N/A

26 N/A N/A N/A N/A

26 N/A N/A N/A N/A

[0055] The connector 720 may provide the STT card additional access to pins providing further functionality. For example, in certain implementations, the STT card may support LTTI functionality, initiating the process of shutting down transmissions by the STT, including halting RF emission and taking necessary data processing actions so that normal functioning can be resumed as required. Emergency signaling functionality, along with status and power control functionality may also be supported. An exemplary pinout for the connector 720 is listed below in Table 8:

Table 8: Connector 720 Pinout

[0056] FIG. 8 illustrates a schematic of an exemplary CDMS card. The schematic represents the physical dimensions of an exemplary controller card, LVT, STT or any other appropriate card designed to operate with a CDMS. The measurements shown in FIG. 8 are in inches.

[0057] The exemplary pinouts described above are arranged such that signals with common, similar, or related functionality are arranged in close proximity to each other. These arrangements allow the described connectors to efficiently handle communications between devices while allowing a CDMS to maintain a small footprint. As shown above and in the Figures, in these implementations, the connectors are configured such that the conducting elements are arranged in an array having one or more rows of consecutively numbered conducting elements (e.g., pins or pin receptacles). While specific connector pinouts are described herein, one of ordinary skill in the art would understand that in certain implementations, other pinouts may be used.

[0058] As disclosed above, a CDMS may be used to manage communications between different devices. Using a controller card, external devices may be added to and/or removed from the CDMS without the need for time-consuming programming and/or reconfiguration. The remote devices and controller card may communicate via a common bus, allowing the CDMS to maintain a small footprint and allowing the controller card to efficiently manage communication and other requests from the external devices. The chassis of the CDMS may be configured to be easily stacked and to easily accommodate a number of external devices while maintaining a small footprint. Additionally, the CDMS may be configured to allow a user to remotely monitor and/or control CDMS operations via a network interface. To achieve some of these advantages, specific connector pin configurations are used, allowing for efficient and intelligent signal grouping. Further, a common pin configuration is used for devices connecting to the common bus, allowing a plurality of devices to easily communicate via the common bus.

[0059] While the present disclosure has been described in connection with aspects of a number of exemplary embodiments, and implementations, the present disclosure is not so limited, but rather, covers various modifications, and equivalent arrangements. In addition, it is understood that the features described are not limited to the specific implementations described, but any number of these features may be combined in any way according to the principles of the presently disclosed subject matter.