AU2018232916A1

AU2018232916A1 - Integrated network communications device

Info

Publication number: AU2018232916A1
Application number: AU2018232916A
Authority: AU
Inventors: Bernard Edward Jackson; Joseph Lejowa
Original assignee: Jackson Care Tech Pty Ltd
Current assignee: JACKSON CARE TECHNOLOGIES Pty Ltd
Priority date: 2013-05-23
Filing date: 2018-09-18
Publication date: 2018-10-04
Also published as: AU2014202838A1

Abstract

C: \Interwovn\NRPortbl\DCC\DER\17732779_l.doc-18 09 2018 A communications device including: a main housing, a first Ethernet port and a second Ethernet port, the first Ethernet port configured to receive power from power sourcing equipment (PSE) in accordance with a Power-over-Ethemet (PoE) protocol, an input circuit 5 coupled to the first Ethernet port and configured to receive the power, a power injector circuit coupled to the second Ethernet port to provide power to the second Ethernet port from the input circuit, a processor coupled to the input circuit to receive power, and coupled to the first Ethernet port and the second Ethernet port to receive data, and a power controller for signalling with the PSE in accordance with the PoE protocol for the PSE to provide power to 10 the first Ethernet port, wherein the power injector circuit is coupled to provide power to the second Ethernet port independently from the processor.

Description

INTEGRATED NETWORK COMMUNICATIONS DEVICE

[001] This is a divisional of Australian Patent Application No. 2014202838, the originally filed specification of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[002] The present invention relates to a communications device, a communications system, and a communication component, e.g., a powered device (PD) having power over Ethernet (PoE) capabilities.

BACKGROUND

[003] PoE systems are able to pass electrical power along Ethernet cabling in conjunction with data. Typically power is supplied over two more of the differential pairs of wires that are used in Ethernet cables and the power comes from a pre-determined power supply such as an Ethernet switch or alternatively power can be inj ected into the Ethernet cable run by a midspan power supply.

[004] One of the advantages of PoE is that as it provides both power and data connections in a single cable then additional cabling is not required. This is particularly attractive when the power demands of a device, i.e. a powered device (PD) is low. A common application is IP telephones or wireless LAN access ports and remote Ethernet switches.

[005] Communication technology, and in particular multi-point communications in which a facility, such as a hospital or similar, requires a large number of communication devices, each of which needs to be connected to some form of network. On a traditional PoE network each device would be considered to be a powered device in that it would be connected directly to the PSE and depending upon its distance from the PSE there would be positioned a midspan somewhere along the Ethernet cable run.

[006] In large facilities, due to the nature of each communication device being only a PD this would necessitate vast amounts of Ethernet cabling to ensure that each of the PD’s had a discreet link to the power sourcing equipment (PSE) and on activation the PSE would power up the PoE link over each discreet Ethernet cable connecting the PSE to each of the vast number of PD communication devices.

[007] The installation of such systems then becomes very complex and invasive, being very problematic to retro-fit to existing facilities.

[008] As such, PoE networks in large facilities, are not readily used or alternatively their usefulness is reduced due to the issues surrounding installation and maintenance.

[009] In addition, large facilities such as hospitals and aged care facilities have traditionally used separate proprietary communication architectures that require a separate infrastructure in the facility itself. This increases the operational load on the hospital/aged care facility and at the same time does not provide the functionality or flexibility to adapt to the facility’s changing needs.

[010] It is desired to address or ameliorate one or more disadvantages or limitations associated with the prior art, or to at least provide a useful alternative.

SUMMARY

[011] In accordance with present invention, there is provided a communications device including: a main housing, a first Ethernet port and a second Ethernet port, the first Ethernet port configured to receive power from power sourcing equipment (PSE) in accordance with a Power-over-Ethemet (PoE) protocol, an input circuit coupled to the first Ethernet port and configured to receive the power, a power injector circuit coupled to the second Ethernet port to provide power to the second Ethernet port from the input circuit, a processor coupled to the input circuit to receive power, and coupled to the first Ethernet port and the second Ethernet port to receive data, and a power controller for signalling with the PSE in accordance with the PoE protocol for the PSE to provide power to the first Ethernet port, wherein the power injector circuit is coupled to provide power to the second Ethernet port independently from the processor.

[012] The present invention also provides a communications system, including a plurality of communication devices each being the communications device above, wherein the first Ethernet port of a downstream one of the devices is connected to the second Ethernet port of an upstream one of the devices for the upstream device to supply power and Ethernet data to the downstream device using an Ethernet cable.

[013] The present invention also provides a communications component for a Power-over-Ethernet (PoE) system including: a first Ethernet port and a second Ethernet port, the first Ethernet port configured to receive power from power sourcing equipment (PSE) in accordance with a PoE protocol, an input circuit coupled to the first Ethernet port and configured to receive the power, a power injector circuit coupled to the second Ethernet port to provide power to the second Ethernet port from the input circuit, a processor coupled to the input circuit to receive power, and coupled to the first Ethernet port and the second Ethernet port to receive the data, and a power controller for signalling with the PSE in accordance with the PoE protocol for the PSE to provide power to the first Ethernet port, wherein the power injector circuit is coupled to provide power to the second Ethernet port independently from the processor.

BRIEF DESCRIPTION OF THE DRAWINGS

[014] Embodiments of the invention are described more fully hereinafter with reference to the accompanying drawings, in which: [015] Figure 1 is a schematic view of an embodiment of present invention; and [016] Figure 2 is a schematic view of an embodiment of present invention in a linked configuration.

DETAILED DESCRIPTION

[017] A communication device (10), as shown in Figure 1, has a first Ethernet port or connector (12) and a second Ethernet port or connector (14). The device (10) may be configured as a single device with all components in a main housing. Alternatively, the device (10) may be an apparatus with a plurality of electrically and electronically connected housings with the same functionality as the device (10) as described herein. The device (10) or apparatus can be referred to as a component in a Power-over-Ethemet (PoE) system. Alternatively the device (10) or apparatus can be referred to as including a PoE component in a PoE system where the PoE component includes PoE data and power connections and couples to other elements of the device (10) or apparatus, e.g., displays, buttons, microphones, etc. The first and second Ethernet connectors may be labelled as "PoE in" and "PoE out" respectively and maybe of the RJ45 type. The first Ethernet connection (12) is connected to a PoE Power Sourcing Equipment (PSE), e.g., a switch and/or midspan device, via an Ethernet input cable (11), such as a CAT5 or 6 cable (or higher category), and both power and data is provided by this cable. The Ethernet input cable (11) also provides a connection to a central Ethernet switch (either in the PSE or separate), and therethrough to a central data server, e.g., running an Internet Protocol for data communications with the device (10).

[018] Power from the PSE can be provided through an input circuit, which includes the data wire pairs (16) and/or the spare wire pairs (18) of the first Ethernet connector (12), in accordance with the IEEE802.3af or 802.3at PoE standard. Power supplied along the data wire pairs (16) can be filtered out using a PoE filter (20) (e.g., a magnetics filter) so as to provide data only to the switch (22), and from there to an outgoing data wire pair (42) of the second Ethernet connector (14) and to a processor (24) of the device (10), e.g., a commercially available microprocessor, which performs functions for the device (10) in cooperation with a memory, instructions and other subcomponents (e.g., lights, microphone, buttons, etc.). The filter (2) also recombines data from the processor (24) and from the outgoing data wire pair (42) of the second Ethernet connector (14) onto the data wire pairs (16) for communication with the upstream devices or the Ethernet switch and central server. Power filtered from the data wire pairs (16) passes through a full wave bridge (FWB) rectifier (25) in the input circuit, which provides polarity correction should the polarity of the incoming DC power be inadvertently reversed from the normal arrangement of+48 V on pair {4,5} and ground on pair {7,8} (e.g., by cross over cables). A FWB rectifier (25) in the input circuit is positioned along the spare wire pair (18) for the same reason.

[019] Power from either the data wire pairs (16) or the spare pairs (18) is then provided to a power controller in the form of a PD controller (30) which then allows power to pass through wire (32) to one or more of the outgoing spare wire pairs (40) of the second Ethernet connector (14). The wire (32) provides (at least in part) a power injector circuit that injects power into the wire pairs of the second Ethernet connector (14). The PD controller (30) and wires between the FWB rectifiers (25) and the second Ethernet connector can also form part of the power injector circuit. The power injector circuit may be substantially formed of wires and un-powered (passive) electronic components, e.g., resistors in the PD controller (30).

[020] In some embodiments, the power injector circuit may also be connected to one or more of the data wire pairs (42), e.g., by a switch, to supply power over a data wire pair (42), thus requiring a further filter similar to filter (20) to add the data signals to the PoE-level DC on the data wire pairs (42). The switch may be controlled by the PD controller (30) and/or the processor (24) during configuration of the device (10) and before powering the second Ethernet connector (14). In other embodiments using only the spare wire pairs (40), there is no need for the further filter, thus simplifying construction of the device (10), which can be applicable for low-power devices, e.g., healthcare devices such as nurse-call buttons etc.

[021 ] Connected to the wire (32) is a DC-to-DC converter (36) configured and connected to draw power from the wire (32) and supply power to the processor (24) and other associated subcomponents. The converter (36) can convert a PoE DC voltage (e.g., 48 volts), provided by the PoE connection, to a circuit-level DC voltage (e.g., 5 volts) for the processor (24) and other circuit components of the device (10). The converter (36) can be a commercially available component.

[022] The PD controller (30), which can be a commercially available component, provides signalling in accordance with the appropriate IEEE protocol which includes: 1. signature detection to establish PoE compliancy so that when the device (10) is attached to a PSE, the PSE recognises the device (10) as a powered device in accordance with the PoE protocol (e.g., provision of a signature resistance such as 19-26.5 level); 2. classification to provide the power range of the device in accordance with the PoE protocol (e.g., provision of a class resistance representing power range, e.g., class 3 drawing a current of 26 to 30 mA and a power of 6.49 Watts, and provision of a type resistance representing protocol type, where type 1 is 8023af and type 2 is 802.3at); 3. normal operation wherein the standard operating current draw is provided (.e.g., at least 5-10mA for 60ms every 400ms) once classification is complete; and 4. continuing to receive power from the PSE until disconnection: after reconnection, the controller (30) resumes the signature detection procedure at step 1 above.

[023] Data is provided to the switch (22) to control the processor (24) and Ethernet data signals flow through the PoE magnetics filter (44) to and from the second Ethernet connector (14) by way of the outgoing data wire pair (42), thus including the downstream device in the Ethernet network.

[024] The communication device (10) as configured therefore now allows both power and data to pass through the device (10) such that a second communication device (60), as shown in Figure 2, may be operatively connected in series (or daisy chained) by connection of an Ethernet cable (62) to the second Ethernet connector (PoE out) (14) of device (10) and to the first Ethernet connector (PoE in) (63) of the second communication device (60). The device (10) provides a power over Ethernet communications system that can be connected to an existing power supply and provide independent pass-through power and data connections to additional ones of the devices attached in series thereto.

[025] The second communication device (60) has the same circuitry as the first communication device (1) and as so these devices may be linked one to the other to provide a linear network of devices all powered by PoE and capable of passing data information from one device to the other over the Ethernet cable network.

[026] When the first device (10) is connected to the PSE it identifies itself to the PSE as a PD so that the PSE supplies power in accordance with the PoE protocol. Once power is received by the device (10), power management circuitry in the PD controller (30) may provide a delay function to the inj ector power into the spare wire pairs (40), so that when the devices (10) are installed on site and there is a cycling of power, the devices do not all turn on at the same time but rather turn on one after the other in sequence with the pre-determined delay. The delay function can be provided by a delay circuit, including a timer and switch, in the PD controller (30). Alternatively in some configurations, the PD controller (30) may have no delay capability, and power will always flow from the PD controller (30) to the second connector (14) when connected to the first Ethernet connector (12). Having no delay circuit can make the PD controller (30) more robust, thus reducing errors due to power blockage or failure in the device (10).

[027] The PD controller (30) is powered independently of the processor (24). Thus, during re-booting of the processor (24) of the first device (10), the power flow across the first device (10) to the subsequent device (60) connected to the second Ethernet port is not affected. Rebooting may be required to update firmware on the device (10).

[028] The switch (22) is coupled to the first Ethernet port, the second Ethernet port and the processor for transmitting data between the first Ethernet port and the second Ethernet port independent of the processor, thus the data connection through the switch (22) is also independent of the processor (24). Thus data communications can continue between upstream and downstream devices while the processor (24) is rebooting or off or failed.

[029] When the first device (10) is daisy chained to additional devices, the PD controller (30) will inject power indefinitely into the spare wire pairs (40) of the second Ethernet connector ("PoE out") (14). As many devices (10) can be connected one to the other, without the need for additional cabling, there is a significant reduction in cabling costs as well as an improvement in device power and data management compared to star Ethernet configurations. The daisy chaining of the devices (10) can allow for simplified programming and firmware updates across the complete chain of devices, e.g., using Internet Protocol (IP) commands from the central server.

[030] Additional Ethernet outlet ports may be configured into the device (10) to allow for network branching from a single device such that there may be one Ethernet in and two Ethernet out ports. The connection of the devices (10) in this manner allows for greater configuration capacity and improved data management from one communication device to another as well as the integration of additional PD’s such as lights, IP cameras.

[031] The devices (10,60) can include electronic circuitry and hardware components to provide specific functions, for example in a healthcare installation or hospital, e.g., the devices (10,60) can be nurse call points, voice-over-internet-protocol (VOIP) talkback devices, overdoor lights points, light-emitting-diode display points, etc.

[032] The device (10) includes the at least one computer processor (24) and computer-readable memory (e.g., memory chips or disks) configured to allow the device (10) to communicate using Ethernet protocols and the Internet Protocol (IP).

[033] The Ethernet protocol can be 10/100 MBit/s Ethernet. Daisy-chaining is provided according to the IEEE 802.3 Ethernet standard with full collision detection (CSMA/CD).

[034] The internet protocol can be IPv4 or IPv6. Each device (10,60) in the PoE network receives a different IP address (e.g., using the Dynamic Host Configuration Protocol, DHCP) and uses it to communicate signals and controls in accordance with their specific functions. After installation and powerup, the device (10) is programmable through the IP connection. Encryption can be provided by an IP security protocol implemented by the processor (24) and memory in the device (10).

[035] The computer processor (24) can communicate over the PoE network using messages, e.g., based on a lightweight text-based standard, such as JavaScript Object Notation (JSON). Event data representing an event message from one of the subcomponents of the device (10), e.g., a button-press event, can be generated, encrypted and sent by the processor (24) using a JSON data structure representing: a transaction identifier (ID), which can be randomly generated, a device identifier of the device (10) (e.g., a Media Access Control (MAC) address), a description of a type of the device (10), e.g., a nurse call button, a description of the specific function, e.g., a button press, and a priority of the event.

[036] The event message is transmitted through any other upstream PoE devices and the PSE to the central computer server over the PoE network, specifically back through the first Ethernet connector (12) and the input cable (11).

[037] The event message can be used for system diagnostics. If the central server or a connected PoE device detects an error, the central server or connected PoE device transmits a reboot message to the device (10) using IP on the PoE network to the device (10) to reboot. The processor (24) then performs a self reboot, which commences by generating, encrypting and transmitting a reboot message to the central server or upstream device, e.g., in a JSON data structure representing the following: a transaction ID, which can be randomly generated; a source serial number, which is the ID of the device; the source device type; a signal type; a signal type description, e.g., “Fault - Rebooting”; and a signal system description reported by the device (10), e.g., the fault that caused reboot.

[038] Upon the completion of a reboot, the device (10) sends a message to the server over the IP / PoE network to report a successful reboot. The successful-reboot message includes a JSON data structure that is generated, encrypted and transmitted by the processor (24). The successful-reboot message is similar to the reboot message, except for the signal type and signal type description, e.g., "Recovered".

[039] The self reboot does not affect the power distribution to other devices (60) in the PoE daisy chain because the power connection through the PD controller (30) is independent of the processor (24). The self reboot does not affect the data connection to other devices (60) in the PoE daisy chain because the data connection through the switch (22) is independent of the processor (24).

[040] The memory and processor (24) of the device (10) can be configured to ping (/. e., send a request for an acknowledgement of receipt of communication) to the upstream or downstream device (60) based on a received IP address and hardware identifier (e.g., MAC address) of the down-stream device (60). The pinging includes generating and transmitting ping messages using the Internet Protocol (IP) and the first Ethernet connector (12) and the second Ethernet connector (14) to the monitor responsiveness of other coupled upstream or downstream devices (10,60). The memory and the processor (24) are also configured to receive the ping messages using the Internet Protocol (IP) and the first Ethernet connector (12)and the second Ethernet connector (14), and to generate and transmit ping acknowledgements representing responsiveness of the device (10). The ping messages include data identifying an IP address and a hardware identifier of the sending and destination devices (10,60). The default pinging period can be about 10 seconds and pinging can continue as long as the down-stream device (60) is connected. If no ping response message is received by the processor (24) from the down-stream device (60), the processor generates and posts a not-responding message to the IP / PoE network. The not-responding message can be based on a JSON data structure. The device (10) can also reboot or power-cycle the down-stream device (60), and wait for ping responses to recommence. Alternatively, one device on the PoE network can ping other upstream and downstream devices, e.g., the display device in a healthcare facility can pin all other PoE devices on the same shared PSE. Rebooting can be performed using the re-boot messages. Alternatively, the PD controller (30) may be used to turn off the downstream PoE power supply, then turn it on again after a possible delay, e.g., using the delay function.

INTERPRETATION

[041 ] Many modifications will be apparent to those skilled in the art without departing from the scope of the present invention.

[042] The reference in this specification to any prior publication (or information derived from it), or to any matter which is known, is not, and should not be taken as an acknowledgment or admission or any form of suggestion that the prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavour to which this specification relates.

Claims

THE CLAIMS DEFINING THE INVENTION ARE AS FOLLOWS:

1. A communications device including: a main housing, a first Ethernet port and a second Ethernet port, the first Ethernet port configured to receive power from power sourcing equipment (PSE) in accordance with a Power-over-Ethernet (PoE) protocol, an input circuit coupled to the first Ethernet port and configured to receive the power, a power injector circuit coupled to the second Ethernet port to provide power to the second Ethernet port from the input circuit, a processor coupled to the input circuit to receive power, and coupled to the first Ethernet port and the second Ethernet port to receive data, and a power controller for signalling with the PSE in accordance with the PoE protocol for the PSE to provide power to the first Ethernet port, wherein the power injector circuit is coupled to provide power to the second Ethernet port independently from the processor.
2. The communications device of claim 1, wherein the power controller provides a powered device (PD) signal to the PSE in accordance with the PoE protocol.
3. The communications device of claim 1 or 2, wherein the power controller includes a delay circuit to delay power injection during start up from the power injector circuit to the second Ethernet port.
4. The communications device of any one of the preceding claims, including a switch coupled to the first Ethernet port, the second Ethernet port and the processor, for transmitting data between the first Ethernet port and the second Ethernet port independent of the processor.
5. The communications device of any one of the preceding claims, wherein the first Ethernet port and the second Ethernet port are configured for Category 5 or 6 cables.
6. The communications device of any one of the preceding claims, wherein the PSE is an Ethernet switch or a PoE midspan power supply capable of providing power over an Ethernet cable.
7. The communications device of any one of the preceding claims, including a full-wave bridge rectifier connected to the first Ethernet port and the power injector circuit to correct the polarity of power from the first Ethernet port for the power injector circuit.
8. The communications device of any one of the preceding claims, including a DC-to-DC converter connected to the first Ethernet port and the processor for converting a PoE voltage from the first Ethernet port to a circuit-level voltage for the processor.
9. The communications device of any one of the preceding claims, including computer-readable memory and/or the processor configured to: receive the data from the first Ethernet port formatted according to the internet protocol (IP); send data to first Ethernet port and to the second Ethernet port formatted according to the internet protocol (IP).
10. The communications device of any one of the preceding claims, wherein the processor is configured to reboot independently of the power controller.
11. The communications device of any one of the preceding claims, wherein the power injector circuit is coupled to a spare wire pair in the second Ethernet port to provide power to the second Ethernet port.
12. A communications system, including a plurality of communications devices, each being the communications device of any one of the preceding claims, wherein the first Ethernet port of a downstream one of the devices is connected to the second Ethernet port of an upstream one of the devices for the upstream device to supply power and Ethernet data to the downstream device using an Ethernet cable, and each device has a different Internal Protocol (IP) address.
13. A communications component for a Power-over-Ethemet (PoE) system including: a first Ethernet port and a second Ethernet port, the first Ethernet port configured to receive power from power sourcing equipment (PSE) in accordance with a PoE protocol, an input circuit coupled to the first Ethernet port and configured to receive the power, a power injector circuit coupled to the second Ethernet port to provide power to the second Ethernet port from the input circuit, a processor coupled to the input circuit to receive power, and coupled to the first Ethernet port and the second Ethernet port to receive the data, and a power controller for signalling with the PSE in accordance with the PoE protocol for the PSE to provide power to the first Ethernet port, wherein the power injector circuit is coupled to provide power to the second Ethernet port independently from the processor.
14. The communications component of claim 13, including a memory and the processor configured to generate and transmit ping messages using the Internet Protocol (IP) and the first Ethernet port and the second Ethernet port to monitor responsiveness of other coupled upstream or downstream communications components.
15. The communications component of claim 13, including a memory and the processor configured to receive ping messages using the Internet Protocol (IP) and the first Ethernet port and the second Ethernet port, and to generate and transmit ping acknowledgements representing responsiveness of the communications component.
16. The communications component of claim 14 or 15, wherein the ping messages include data identifying an IP address and a hardware identifier of the communications component.