WO2017030530A1

WO2017030530A1 - In-line device

Info

Publication number: WO2017030530A1
Application number: PCT/US2015/045280
Authority: WO
Inventors: James S. Hiscock
Original assignee: Hewlett Packard Enterprise Development Lp
Priority date: 2015-08-14
Filing date: 2015-08-14
Publication date: 2017-02-23

Abstract

In example implementations of an in-line device, the in-line device includes a DATA module, a power over Ethernet (PoE) module in communication with the DATA module and a Bluetooth low energy (BLE) module in communication with the PoE module. The DATA module can establish a first connection to an Ethernet switch with power sourcing equipment (PSE) capability and a second connection to a network device. The PoE may draw power from the first connection and provide power via the second connection. The BLE module receives power from the PoE module and provides location services.

Description

IN-LINE DEVICE

BACKGROUND

[0001] Location services is a feature that can be used to improve features and services for the devices. Some devices are not shipped or manufactured with location services. Some manufacturers are deploying devices that provide location services using a universal serial bus (USB) device. However, some devices are not manufactured with USB ports.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] FIG. 1 is a block diagram of an example in-line device of the present disclosure;

[0003] FIG. 2 is a block diagram of another example in-line device of the present disclosure;

[0004] FIG. 3 is a block diagram of another example in-line device of the present disclosure;

[0005] FIG. 4 is a block diagram of another example in-line device of the present disclosure;

[0006] FIG. 5 is an example diagram of a state machine of a combining function;

[0007] FIG. 6 is a flowchart of an example method for performing the combining function; and

[0008] FIG. 7 is a flowchart of an example method for powering the in-line device. DETAILED DESCRIPTION

[0009] The present disclosure provides an in-line device that can provide location services via a Bluetooth low energy (BLE) module to those devices that do not have a USB port. As discussed above, location services is a feature that can be used to improve features and services for the devices. Some devices are not shipped or manufactured with location services. Some manufacturers are deploying devices that provide location services using a universal serial bus (USB) device. However, some devices are not built with USB ports.

[0010] Example implementations of the present disclosure provide an in-line device that may provide location services via a BLE module to a network device that does not have a USB port. In one example, the in-line device may be located between a male Ethernet connection of a cable and a female Ethernet connection between an Ethernet switch and the network device.

[0011] FIG. 1 illustrates a block diagram of an example in-line device 100 of the present disclosure. In one example, the in-line device 100 may include a DATA module 102, a power over Ethernet (PoE) module 104 and a Bluetooth low energy (BLE) module 106. The DATA module 102, the PoE module 104 and the BLE module 106 may be deployed as electronic hardware (e.g., circuits, resistors, capacitors, transistors, processors or application specific integrated circuit (ASIC) chips, memory, and the like) within the in-line device 100.

[0012] The DATA module 102 may include a first connection 112 to an Ethernet switch 110 with power sourcing equipment (PSE) capability. The first connection 1 2 may include a two-way communication path to transmit and receive data packets in both directions. The first connection 112 may also receive power over Ethernet from the Ethernet switch 110 (also referred to as the PSE 110). In one example, the DATA module 102 may include a female Ethernet connection to establish the first connection 112 with a male Ethernet connection on the cable from the Ethernet switch 110.

[0013] The DATA module 102 may also include a second connection 114 to a network device 108 (also referred to as a powered device (PD) 108). The second connection 114 may include a two-way communication path to transmit and receive data packets in both directions. The second connection 114 may also provide power over Ethernet to the network device 108. In one example, the DATA module 102 may include a male Ethernet connection to establish the second connection 114 with a female Ethernet connection to the network device 108.

[0014] In some implementations, the network device 108 may be any type of device that would benefit from location services provided by the BLE module 106. The network device 108 may not have any USB ports, but may have an Ethernet port. For example, the network device 108 may be an access point, a computer (e.g., a lap top computer, a desktop computer, etc.), and the like.

[0015] In one example, the PoE module 104 may be electrically coupled with the DATA module 102. The PoE module 104 may draw power from the first connection and provide power to the network device via the second connection.

[0016] In one example, the BLE module 106 may be electrically coupled with the PoE module 104. The BLE module 106 may be powered by the PoE module 104 with power drawn initially from the first connection 112. The BLE module 106 may provide location services to the network device 108 that otherwise does not have location service capabilities.

[0017] Although the in-line device 100 is illustrated as a separate device that sits between an Ethernet connection to the Ethernet switch 110 and the network device 108, it should be noted that the in-line device 100 may be deployed as part of a portion of an Ethernet cable. For example, the male connector of an Ethernet cable from the Ethernet switch 10 may be modified to include the features of the in-line device 100.

[0018] FIG. 1 illustrates a basic design of the in-line device 100 of the present disclosure. Depending on a cost or complexity that is needed for a particular application, different variations of the DATA module 102 and the PoE module 104 can be deployed. Additional modules may also be deployed to provide greater functionality.

[0019] FIG. 2 illustrates an in-line device 200 that uses a DATA module 202 having a layer 1 bit level repeater 250. Layer 1 may refer to the Physical layer in the seven layer International Standards Organization (ISO) Open System Interconnection (OSI) networking model. The repeater 250 may include lines 212 and 214 for transmission (Tx) to the Ethernet switch 1 10 and lines 216 and 218 for reception (Rx) from the Ethernet switch 110. The repeater 250 may also include lines 220 and 222 for transmission (Tx) to the network device 108 and lines 224 and 226 for reception (Rx) from the network device 108.

[0020] In one example, the DATA module 202 may also include voltage lines 205 and 206 that are fed into a voltage in (Vin) port of the PoE module 204. The DATA module 202 may also include voltage lines 208 and 210 from a voltage out (Vout) port of the PoE module 204. The DATA module 202 is shown as a single pair Tx and Rx Ethernet implementation, but the DATA module 202 could also support 4 pair Ethernet implementations (not shown).

[0021] In one example, in-line device 200 may provide non-disruptive pass through of data packets between the Ethernet switch 110 and the network device 108, while providing location services with the BLE module 206. For example, the PoE 204 may draw a portion of the power from the Ethernet switch 110 to power the BLE 206, and pass through the majority of the remaining amount of power to the network device 108 almost as if the in-line device 200 were absent.

[0022] In addition, the PoE 204 may not participate in the discovery and classification steps of the network device 108. For example, the Ethernet switch 110 may perform discovery and classification by sending signals to the network device 108. The signals from the Ethernet switch 110 may simply pass through the PoE 204 to the network device 108.

[0023] FIG. 3 illustrates a block diagram of another example in-line device 300 of the present disclosure. The in-line device 300 may include a DATA module 302, a PoE module 304 and a BLE module 306 similar to the in-line devices 100 and 200. In some implementations, the in-line device 300 may also include a management module 308. The management module 308 provides the in-line device 300 with additional capabilities and features, as discussed below.

[0024] In one example, the DATA module 302 may be a three port switch. The DATA module 302 may be a layer 2 switch (e.g., a data link layer) in a 7 layer ISO OSI networking model that relays data packets. For example, a first port may be used for transmission and reception of data packets to and from the Ethernet switch 110, a second port may be used for transmission and reception of data packets to and from the network device 108, and a third port may be used for transmission and reception of data packets to and from the

management module 308.

[0025] In one implementation, the PoE module 304 may be coupled to, directly or indirectly, with the DATA module 302. The PoE module 304 may include a power controller 3 0 and a power store 312. In one example, the power controller 310 may receive and transmit power from the DATA 302. The DATA 302 may receive power from the Ethernet switch 10 and transmit power to the network device 108 via the PoE module 304, as described above.

[0026] In one example, the power controller 310 may take additional power that can be stored in the power store 312. For example, the power store 312 may store power like a battery. The amount of power that is stored in the power store 312 or dissipated from the power store 312 may be controlled by the power controller 310 and in response to control signals from the management module 308. In one example, the BLE 306 may be coupled to, directly or indirectly, with the PoE module 304 and powered by the PoE module 304.

[0027] The management module 308 may provide four functions for the inline device 300. The management module 308 may provide a first function serving as the PSE to the network device 108 that is downstream, a second function as the PD to the Ethernet switch 1 10 that is upstream. The third function may be to coordinate and translate the power request information as well as the power availability information. The management module 308 may provide a fourth function managing the BLE 306.

[0028] For example, the management module 308 may also be responsible for managing the BLE module 306. For example, the management module 308 may provide additional intelligence to the BLE module 306 in addition to a passive beacon emitted by the BLE module 306. In some implementations, the management module 308 may be capable of exchanging messages with nearby network devices to discover new network devices, answer inquiry messages from neighboring devices, provide a status or status updates of the BLE module 306, and the like. The management module 308 may use any management protocol (e.g., Simple Network Management Protocol) to communicate and manage the BLE module 306.

[0029] As noted above, the management module 308 may serve two roles. Acting as the PSE and the PD for the in-line device 300, the management module 308 may perform PD functions such as asking for power from the Ethernet switch 110. In one example, the management module 308 identifies itself as a type 2 PD device in the initial discovery and classification steps to the upstream Ethernet switch 110. If the Ethernet switch 110 is a type 2 PSE, then after the in-line device 300 powers up, the management module 308 may communicate the ongoing power needs using link layer discovery protocol (LLDP) packets as specified by the IEEE 802.3at standard. The power request sent by the management module 308 to the upstream Ethernet switch 1 10 may be a sum of the power required by the in-line device 300 and the power the inline device 300 will send to the network device 108.

[0030] Acting as the PSE, the management module 308 may coordinate discovery functions, classification functions, determine an amount of power used by the network device 108 based on the discovery and classification sets defined in the IEEE 802.3at specification, supply the amount of power the network device 108 uses and continuously monitor and update the power needs of the network device 108 as specified by the IEEE 802.3at standard. Once the network device 108 is classified, the requested power may be delivered to the network device 108. For example, upon initialization, if the network device 108 is a type 2 PD, then the management module 308 may send and receive Ethernet LLDP packets to and from the network device 108 to communicate both the ongoing power needs of the network device 108 and the power available to the network device 108.

[0031] The management module 308 may continue to monitor the power requested by the network device 108 via an exchange of Ethernet data packets. When the power requested by the network device 108 changes, the

management module 308 may update the amount of power that is delivered to the network device 108. For example, the management module 308 may send a control signal to the power controller 310 to release less or more power from the power store 312.

[0032] In one example, the management module 308 may include a processor and a non-transitory memory or storage medium. The non-transitory memory or storage medium may store instructions associated with the functions performed by the management module 308 and the processor may execute the instructions stored in the memory.

[0033] The management module 308 may also intercept, generate and modify Ethernet packets exchanged between the Ethernet switch 110 and the network device 108. For example, via the three port switch of the DATA module 302, Ethernet packets between the Ethernet switch 110 and the network device 108 may be routed through the management module 308. The management module 308 may read the Ethernet packet and modify the Ethernet packet to include a requirement of the in-line device 300.

[0034] FIG. 4 illustrates another version of an in-line device 400. The in-line device 400 may act as a full PD 404, for the cable side, and as a full PSE 406, for the network device side. The in-line device 400 may request enough power for both the circuitry of the in-line device 400 and the network device 108. The in-line 400 device may also perform the discovery and classification steps on the network device (PD) 108 to determine if the network device needs PoE power and how much power, if it is a type 1 or 2 PD.

[0035] The in-line device 400 may act as a PD 404 to the upstream PSE 110. The PD 404 may identify itself as a type 2 PD and if the upstream PSE 110 is a type 2 PSE, then after the in-line device 400 powers up, the in-line device 400 may communicate the ongoing power needs using LLDP packets as specified by IEEE 802.3at standard. The power request sent by the in-line device 400 to the upstream PSE 110 may be a sum of the power required by the in-line device 400 and the power the in-line device 400 may send to the network device 108.

[0036] The in-line device 400 may also act as a PSE 406 to the network device 108. If the PD (network device) 108 is a type 2 PD, then the in-line device 400 may perform on going power monitoring and allocation for the network device 108 using LLDP Ethernet packets. The combining function 402 may interface with the PD 404 and the PSE 406 and monitors the in-line device power requirements (IN.pwr) 408, to dynamically request power and relay power availabilities to each power consumer and each power supplier, in an ongoing manner.

[0037] FIG. 5 illustrates an example state machine 500 run by the combining function 402 of FIG. 4. An initial state 502 may be when the PD 404 of the inline device 400 (ID.PD) is not yet powered up. The state machine 500 may transition into a state 504 if the PD 404 is granted power by a type 2 PSE from the upstream Ethernet switch or PSE 110 (UD.PSE). Alternatively, the state machine 500 may transition into a state 506 if the PD 404 is granted power by a type 1 PSE from the upstream Ethernet switch or PSE 110.

[0038] From state 504, the state machine 500 may transition into a state 508 if the PSE 406 of the in-line device 400 (IN. PSE) grants power to the network device 108 (ND.PD) and the network device 108 is a type 2 PD. At state 508, both the PSE 110 and the network device 108 are type 2 devices. As a result, the ongoing power information regarding both need and availability can occur using LLDP Ethernet packets.

[0039] Alternatively, the state machine 500 may transition to a state 510 if the PSE 406 grants power to the network device 108 and the network device is a type 1 PD. At the state 510, the PSE 110 is a type 2 device, but the network device 108 is a type 1 device. So instead of getting updated power needs of the network device 108 via LLDP Ethernet packets, the in-line device 400 can measure the power consumed by the network device and update the power requirement variable based on the measurement instead of the LLDP Ethernet packets.

[0040] From the state 506, the state machine 500 may transition into a state 512 if the PSE 406 grants power to the network device 108 and the network device 108 is a type 2 PD. At the state 512 the PSE 110 is a type 1 device so the initial power available information may be provided by the initial power discovery. The network device 108 is a type 2 device so the power needed by the network device is updated using LLDP Ethernet packets. [0041] Alternatively, the state machine 500 may transition to a state 514 if the PSE 406 grants power to the network device 108 and the network device is a type 1 PD. At the state 514, the PSE 110 is a type 1 device so the initial power available information may be provided by the initial power discovery. The actual power consumed by the network device 108 is measured and used to track the on-going power need for the network device 108.

[0042] Within the states 508 and 510, the amount of power available from the PSE 110 and amount of power needed by the network device 108 and the in-line device 400 may be continuously monitored and updated. Within the states 512 and 514, the amount of power available from the PSE 110 may be set to the initial request for power and the amount of power needed by the network device 108 and the in-line device 400 may be continuously monitored and updated.

[0043] For example, the amount of power available from the PSE 110 may be received and the amount of power needed by the network device 108 may be received based on the initial discover and classification steps to arrive at one of the states 508, 510, 512 or 514. The way the discover and classification steps are performed may depend on the type of network device 108 (e.g., type 1 or type 2). The total amount of power required may be assigned a sum of the power requested by the network device 108 and the power requested by the inline device 400. If the total power required is less than the power available from the PSE 110, then the power is granted to the network device 108 and the total amount of power to be requested from the PSE 110 may be updated to be the sum of the power requested by the network device 108 and the power requested by the in-line device 400.

[0044] If the total power required is greater than the power available from the PSE 110, then the power available to be granted to the network device 108 is updated to be equal to the power available from the PSE 110 minus the power needed by the in-line device 400. This method may be repeated by getting new values of power available from the PSE 110 and power needed by the network device 108.

[0045] FIG. 6 illustrates an example method 600 for performing a combining function. In one implementation, the method 600 may be performed by the combining function 402 of the in-line device 400 or by the management module 308 of the in-line device 300.

[0046] At block 602, the method 600 begins. At block 604, the method 600 receives, via a powered device (PD) of an in-line device, an amount of power available from an Ethernet switch with power sourcing equipment (PSE) capability. In one example, the amount of power available from the Ethernet switch may be received using a link layer discovery protocol (LLDP) packet for a type 2 PSE device. In another example, the amount of power available from the Ethernet switch may be received using an initial power discovery for a type 1 PSE device. For example, the manner in which the Ethernet switch does the classification step may tell the PD of the in-line device whether the Ethernet switch is a type 1 PSE device or type 2 PSE device. The PD of the in-line device may respond as a type 2 PD device.

[0047] At block 606, the method 600 receives, via a power sourcing equipment (PSE) of the in-line device, an amount of power needed by a network device. In one example, the amount of power needed by the network device may be received using a LLDP packet for a type 2 network device. In another example, the amount of power needed by the network device may be received using a measurement of an amount of power consumed by the network device for a type 1 network device. For example, the type of device (e.g., 1 or 2) of the downstream network device may determine what method is used to receive the amount of power needed by the network device.

[0048] At block 608, the method 600 calculates a total amount of power required, wherein the total amount of power required comprises a sum of the amount of power needed from the network device and an amount of power required by the in-line device.

[0049] At block 610, the method 600 determines whether the total amount of power required is less than or equal to the amount of power available. If the answer to block 610 is yes, the method 600 may proceed to block 612. If the answer to block 610 is no, the method 600 may proceed to block 614.

[0050] At block 612, when the total amount of power required is less than or equal to the amount of power available, the method 600 grants the amount of power needed by the network device and updates an amount of power requested from the Ethernet switch to be the total amount of power required. For example, the total amount of power required may be less than the amount of power that is available from the Ethernet switch. Thus, the amount of power to be requested from the Ethernet switch may be lowered to the total amount of power required in a subsequent loop of the method 600.

[0051] At block 614, when the total amount of power required is greater than the amount of power available, the method 600 updates the amount of power available that is reported to the network device by the PSE of the in-line device as the amount of power available from the Ethernet switch less the amount of power required by the in-line device. In other words, there is not enough power for the network device and the network device may lower the requested amount of power in a subsequent loop of the method 600.

[0052] From block 612 or block 614, the method 600 may return to block 604 and the method 600 may be continuously repeated to monitor the power available and needed between the Ethernet switch and the network device. In other words, the method 600 may loop infinitely to perform on-going

adjustments until the in-line device stops receiving power from the Ethernet switch (e.g., the Ethernet switch is turned off or the in-line device is

disconnected from the Ethernet switch).

[0053] FIG. 7 illustrates an example method 700 for powering an in-line device. In one implementation, the method 700 may be performed by the in-line device 100, 200, 300 or 400.

[0054] At block 702, the method 700 begins. At block 704, the method 700 establishes a first connection to an Ethernet switch with power sourcing equipment (PSE) capability and a second connection to a network device via a DATA module of the in-line device. For example, the connections may be established via either a layer 1 bit level repeater switch or a three port switch. The connection may be established between a male Ethernet connection on a cable and a female Ethernet connection.

[0055] At block 706, the method 700 draws power, via a power over Ethernet (PoE) module coupled to the Data module, from the first connection. In one example, the PoE module may have a power controller and a power store to store additional power.

[0056] At block 708, the method 700 provides power to the network device via the second connection and a Bluetooth low energy (BLE) module coupled to the PoE module, wherein the BLE module provides location services. For example, the power drawn by the PoE module may be provided to the BLE module and the network device.

[0057] In one example, a management module may be coupled to the DATA module, the PoE module and BLE module. The management module may coordinate a power request information from the network device, a power availability information from the Ethernet switch and a power requirement of the in-line device. For example, the management module may receive the power request information from the network device and add on the power requirement of the BLE module to calculate a total amount of power that is requested.

[0058] The method 700 may then return to block 706 and the method 700. In other words, the method 700 may be repeated continuously until the in-line device stops receiving power from the Ethernet switch (e.g., the Ethernet switch is turned off or the in-line device is disconnected from the Ethernet switch).

[0059] As a result, the in-line devices 100, 200, 300 and 400 may be used for network devices that do not have a USB port. The in-line devices 100, 200, 300 and 400 may utilize the Ethernet connections between the Ethernet switch 110 and the network device 108 to provide BLE location services to the network device 108.

[0060] It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be combined into many other different systems or applications. Various presently unforeseen or unanticipated alternatives, modifications, or variations, therein may be subsequently made which are also intended to be encompassed by the following claims.

Claims

1. An in-line device, comprising:

a DATA module to establish a first connection to an Ethernet switch with power sourcing equipment (PSE) capability and a second connection to a network device;

a power over Ethernet (PoE) module coupled to the DATA module to draw power from the first connection and provide power via the second connection; and

a Bluetooth low energy (BLE) module coupled to the PoE module to receive power from the PoE module, the BLE module to provide location services.

2. The in-line device of claim 1 , further comprising:

a management module coupled to the DATA module, the PoE module and the BLE module.

3. The in-line device of claim 2, wherein the management module coordinates a power request information from the network device, a power availability information from the Ethernet switch and a power requirement of the in-line device.

4. The in-line device of claim 1 , wherein the DATA module comprises a female Ethernet connection for the first connection and a male Ethernet connection for the second connection.

5. The in-line device of claim 1 , wherein the DATA module comprises a layer 1 bit level repeater.

6. The in-line device of claim 1 , wherein the DATA module comprises a three port switch.

7. The in-line device of claim 1 , wherein the PoE module provides power to the network device for a non-disruptive pass-through of data through the DATA module.

8. A method, comprising:

establishing a first connection to an Ethernet switch with power sourcing equipment (PSE) capability and a second connection to a network device via a DATA module of an in-line device;

drawing power, via a power over Ethernet (PoE) module coupled to the Data module, from the first connection; and

providing power to the network device via the second connection and a Bluetooth low energy (BLE) module coupled to the PoE module, wherein the BLE module provides location services.

9. The method of claim 8, further comprising:

coordinating, via a management module coupled to the DATA module, the PoE module and the BLE module, a power request information from the network device, a power availability information from the Ethernet switch and a power requirement of the in-line device.

10. The method of claim 9, wherein the management module adds a power requirement of the in-line device to the power request information from the network device.

11. A method, comprising:

receiving, via a powered device (PD) of an in-line device, an amount of power available from an Ethernet switch with power sourcing equipment (PSE) capability;

receiving, via a power sourcing equipment (PSE) of the in-line device, an amount of power needed by a network device;

calculating a total amount of power required, wherein the total amount of power required comprises a sum of the amount of power needed from the network device and an amount of power required by the in-line device;

determining whether the total amount of power required is less than or equal to the amount of power available;

when the total amount of power required is less than or equal to the amount of power available, granting the amount of power needed by the network device and updating an amount of power requested from the Ethernet switch to be the total amount of power required; and

when the total amount of power required is greater than the amount of power available, updating the amount of power available that is reported to the network device by the PSE of the in-line device as the amount of power available from the Ethernet switch less the amount of power required by the inline device.

12. The method of claim 11 , wherein the amount of power available from the Ethernet switch is received using a link layer discovery protocol (LLDP) packet for a type 2 PSE device or an initial power discovery for a type 1 PSE device.

13. The method claim 11 , wherein the amount of power needed by a network device is received using a link layer discovery protocol (LLDP) packet for a type 2 network device or a measurement of an amount of power consumed by the network device for a type 1 network device.

14. An in-line device, comprising:

a powered device (PD) to receive an amount of power available from an Ethernet switch with power sourcing equipment (PSE) capability;

a power sourcing equipment (PSE) to receive an amount of power needed by a network device; and

a combining function to calculate a total amount of power required, wherein the total amount of power required comprises a sum of the amount of power needed from the network device and an amount of power required by the in-line device, to determine whether the total amount of power required is less than or equal to the amount of power available, to grant the amount of power needed by the network device and updating an amount of power requested from the Ethernet switch to be the total amount of power required when the total amount of power required is less than or equal to the amount of power available, and to update the amount of power available that is reported to the network device by the PSE of the in-line device as the amount of power available from the Ethernet switch less the amount of power required by the inline device when the total amount of power required is greater than the amount of power available.

15. The in-line device of claim 14, wherein the amount of power available from the Ethernet switch is received using a link layer discovery protocol (LLDP) packet for a type 2 PSE device or an initial power discovery for a type 1 PSE device and the amount of power needed by the network device is received using a link layer discovery protocol (LLDP) packet for a type 2 network device or a measurement of an amount of power consumed by the network device for a type 1 network device.