GB2518620A

GB2518620A - Headless wireless device

Info

Publication number: GB2518620A
Application number: GB1317018.8A
Authority: GB
Inventors: Andrew Winton; Robert Edge
Original assignee: Ultra Electronics Ltd
Current assignee: Ultra Electronics Ltd
Priority date: 2013-09-25
Filing date: 2013-09-25
Publication date: 2015-04-01
Anticipated expiration: 2033-09-25
Also published as: GB2518620B; GB201317018D0

Abstract

A headless computing device capable of wireless communication includes a first wireless interface 12. a second wireless interface 14, and a configuration system.The first wireless interface 12 is operable to connect wirelessly to a network. The second wireless interface 14 is configured as an access point and is operable to receive a wireless connection from a remote device 16. The configuration system is operable to configure the first wireless interface 12. The configuration unit is controllable via the second wireless interface 14. This removes the need for an intermediate device to help the headless device connect wirelessly to a network.

Description

HEADLESS WIRELESS DEVICE

The present invention relates to headless wireless devices and methods of connecting them to wireless networks.

BACKGROUND

A typical wireless enabled device consists of: a graphics display, an input device, a processing unit and a wireless interface. These are common place, e.g. smart phones, tablets and mobile games devices. See FIG 1.

A wireless enabled device can also be headless. By headless we refer to a device which does not have a standard computer human interface. Standard computer human interfaces include visual display units and input devices. We also refer headless to mean a device which does have standard computer human interfaces but where those interfaces are not accessible, for example due to SyOPs a cryptographic device may enforce separation by disabling the standard input/output devices. See FIG 2a.

Headless wireless devices can be difficult to configure because of the absence of standard computer human interfaces.

Attempts have been made to address this problem which are limited in their success.

One solution is to pre-configure the headless device. This works only when it is known in advance which networks the device will be used in, for example a known work-place network. This solution fails if the user enters an area with a network which is not preconfigured, such as a hotel network.

Another solution is to add an intermediate computing device which acts as a router between the headless device and the new wireless network where the intermediate device has a fixed known SSID and password which a preconfigured headless device can connect to. The intermediate device then shows to the user the available networks. This would solve problems encountered both when entering a new WiFi zone and also when confronted with a Captive Portal.

However, there are limitations with this solution. If the known SSID and password which are fixed became compromised it would not be easy to change this.

Changing the fixed SSID and password would face similar problems to the pre-configured solution. Furthermore, the intermediate computing device would be required to always be present during communications, powered and running the routing functionality. It would need to have input/output capability to allow the user to configure access to a new wireless access point. It would introduce latency into the system. It would increase costs of the final solution.

An alternative proposal from Texas Instruments is their Smart Config CC3000 solution. It listens for a certain UDP packet on a network which the device has not connected to yet, much like you can see the SSID of a network even though you are not connected to that network yet. The user presses a button on the device, the TI device enters a config mode and will use the next UDP packet in the correct format to configure the device. Although this solution can be used to configure a WiFi device, there are some limitations.

Firstly, it does not solve the Captive Portal problem and so cannot be used in such situations. Secondly, this solution is tied to using TI hardware in your device.

Thirdly, a user needs to be physically next to the device to set it into config mode by pressing a push button to enter config mode.

Aspects of the present invention seek to provide an improved headless wireless device and method or at least provide a useful alternative to existing technology.

According to an aspect of the invention there is provided a headless computing device capable of wireless communication, including: a first wireless interface operable to connect wirelessly to a network; a second wireless interface configured as an access point and being operable to receive a wireless connection from a remote device; and a configuration system operable to configure the first wireless interface, the configuration unit being controllable via the second wireless interface.

Preferred embodiments of the present invention enable a headless device to be remotely configured, for example by a secure wireless connection, to enable it to connect to a new network. This can be done without physical interaction with the headless device; it can be done by means of a remote device such as a user's tablet or smartphone.

Preferred embodiments of the invention remove the need for an intermediate device between the headless device and the network. Once a remote device has been used to configure the headless device, the headless device can be connected directly to the network, even if the remote device is disconnected.

Preferably, the configuration system includes a web server, the web server being operable to provide a web page to a remote device via the second wireless interface and being operable to configure the first wireless interface in response to data received via the web page from a remote device.

The headless device preferably includes a routing system configured to route data received via the first wireless interface to a device connected via the second wireless interface and vice versa.

Preferred embodiments enable a remote device connected via the second wireless interface to log the headless device in to a captive portal via the first wireless interface.

Embodiments include a control system for controlling non-network-related operation of the headless device, the control system being controllable via the first and/or second wireless interface. This can mean that features other than the wireless connection of the headless device can be controlled. Such features can include, for example, changing channels where the headless device is a television.

Other examples are given below.

In embodiments, the control system is configured to seek authorisation via the first and/or second wireless interface, preferably via the first wireless interface, of commands or requests received via the first and/or second wireless interface before acting on said commands or requests. This can provide an additional security feature for example to ensure that an operator of the remote device has permission to perform the operation he or she is attempting.

The headless device can include a security element, such as a locking mechanism, for securing a building, vehicle or container, the security element being controllable by the control system.

The headless device can include a monitoring unit, and the headless device can be configured to provide data from the monitoring unit via the first wireless interface and/or via the second wireless interface.

The headless device can be included in a computing device including a user input unit wherein the user input unit is prevented from configuring the headless device.

According to an aspect of the invention there is provided a method of connecting a headless computing device capable of wireless communication to a wireless network via a first wireless interface, including: receiving a connection from a remote device via a second wireless interface; receiving configuration commands from the remote device via the second wireless interface; configuring the first wireless interface using the configuration commands and connecting the headless device to the network via the first wireless interface.

The method can include sending to the remote device details of available networks to which connection can be made via the first wireless interface.

The method can include sending to the remote device a web page using which a user of the remote device can provide the configuration commands.

The method can include, after connecting to the network, routing data between the remote device and the network.

A programmable component can be configured to perform the method.

Program code can be provided for performing the method when executed on a programmable component.

Preferred embodiments of the invention solve all of the above-described problems with generic hardware at a reduced cost.

Preferred embodiments are able to configure headless wireless devices. Preferred embodiments are also able to configure headless wireless devices which are mobile and need to connect to a new wireless network. Preferred embodiments can also connect such devices into networks which require the user to enter login details or payment to use the network such as a captive portal.

Preferred embodiments of the invention provide a system for connecting a headless internet device into a new wireless network. The headless device makes use of a second wireless interface and remote wireless computer for configuration.

Once connected to the new wireless network captive portal login request are routed to the remote wireless computer for payment and authentication enabling the headless wireless device to be fully configured and connected.

According to an aspect of the invention, there is provided a method for configuring a headless wireless device to join a new wireless network, comprising: a second wireless interface on the device to be configured; a remote wireless enabled device to connect to the second interface on the device to be configured; processing on the device to be configured to route packets and configuration information to the remote wireless enabled device; which upon user interaction results in the device to be configured being able to connect to the new wireless network.

Preferably, the device will route network packets between the new network and the remote wireless enabled device.

Preferably, the routing of network packets enables the remote wireless enabled device to show captive portal login page.

Preferred embodiments of the invention are described below, by way of example only, with reference to the accompanying drawings, in which: Figure 1 is a schematic diagram of various known types of wireless device; Figure 2a is a schematic diagram of a laptop including a cryptographic device enforcing separation of user interface components from a wireless component; Figure 2b is a schematic diagram of a web-cam; Figure 3 is a schematic system diagram of an embodiment of the invention; and Figure 4 is a schematic system diagram of another embodiment of the invention.

A system diagram of a preferred embodiment is represented in FIG 3. Here we have a headless device 10 to be configured. Examples of headless devices to which embodiments of the invention can be applied are shown in Figure 2.

The headless device 10 includes a control system or unit 11, such as a processor, a first wireless interface 12, and a second wireless interface 14. The headless device 10 can also include a memory 15 for temporarily or permanently storing data such as buffer data, configuration settings and the like. In addition, the memory 15 stores executable program code which is executable by the control unit 11 in order to provide the functionality discussed below.

In this embodiment the wireless interfaces are WiFi interfaces. However, different wireless protocols and specifications can be used in other embodiments. In this embodiment the first wireless interface is provided by a first wireless communication unit and the second wireless interface is provided by a second wireless communication unit. However, in other embodiments, a single wireless communication unit can be configured to provide both the first and second wireless interfaces. The wireless communication unit(s) can be for example transceivers or wireless radios.

As is described below, the second wireless interface is for configuration; the first wireless interface is for accessing a network. As described below the second wireless interface operates a network different from the network to which the first wireless interface connects.

Figure 3 shows a remote wireless enabled device 16 and a wireless access point 18 to a public network 20, such as the Internet. Access to the public network 20 may be restricted by a captive portal 22 between the access point 18 and the public network 20. Although the network 20 is described as being a public network, this is just a typical example; the network to which the headless device can connect does not need to be public; it can be any kind of network to which it is desired to connect the headless device 10.

The second wireless interface 14 is configured as an access point. For example, the second wireless interface can include a DHCP server to give IP addresses to remote devices accessing the second wireless interface. Preferably, the second wireless interface 14 is configured as an access point to a secure network.

The control unit 11 is configured as a routing unit to provide routing ability to transfer packets from the first wireless interface to the second wireless interface.

The control unit 11 is configured to provide NAT ability to allow a remote device connected to the second wireless interface to communicate with a network to which the first wireless interface is connected.

The device 10 includes a web server, provided by the control unit 11. The web server is operable to provide a web page to a remote device via the second wireless interface. The control unit 11 is operable to receive details of available networks from the first wireless interface and to provide these details of available networks in a web page provided to a remote device. The web page is configured to allow a user to select an appropriate network for the first wireless interface and if appropriate to provide configuration settings for that network.

In response to data received via the web page, the control unit is operable to appropriately configure the first wireless interface 12.

The device 10 includes a DNS server, provided by the control unit 11, so the user does not need to remember a number.

The control unit 11 can also be configured to control operation of the headless device in other non-network-related ways in response to commands or requests received via the first or second wireless interface, depending on the specific functionality of the headless device, examples of which are provided below.

In response to receipt of commands or requests via the second wireless interface, the control unit 11 can be configured to correspond with a remote authorisation unit via the first wireless interface in order to obtain authorisation for the commands or requests. The control unit 11 can be configured to send a signed authorisation request to the authorisation unit and only to act on the commands or requests in response to an authorisation approval response from the authorisation unit.

The steps for configuring the device 10 are as follows: The device 10 to be configured enables the second wireless interface 14. This is configured as a wireless access point, with DHCP. This is a secure access point with details and passwords known to a user.

The user connects to this access point with a remote wireless enabled device 16, such as one of the types depicted in Figure 1.

The user accesses a web page on the web server of the headless device 10 by use of the now connected remote wireless enabled device 16.

The web page shows available networks which can be seen from the first wireless interface 12.

The user can select a wireless network from the list shown, such as that represented by access point 18.

Upon user interaction, the control unit 11 changes the configuration of the first wireless interface 12 in order to connect to the selected network, in this case network 20 via access point 18.

The control unit 11 of the headless device 10 also changes routing tables and enables packet forwarding and network address translation from the remote wireless device 16 to the network 20.

At this point the remote wireless device 16 is able to connect to the network 20.

If however, a captive portal 22 is operational further steps are required before full access to the network is available.

The captive portal 22 intercepts web traffic to show the captive portal login page to the user on the remote wireless enabled device 16. This is possible as the headless device 10 acts as a router.

Once the user has entered captive portal login and/or payment details, access to the public network 20 is allowed. When this happens the remote wireless enabled device 16 can access the public network.

At this point the headless device 10 can also access the public network 20.

As can be seen by the above description, embodiments of the present invention enable a headless device to be remotely configured to enable it to connect to a new network. This can be done without physical interaction with the headless device; it can be done by means of an intuitive app provided on a user's tablet or smartphone for example.

Preferred embodiments of the invention also remove the need for an intermediate device between the headless device and the network. Once a remote device has been used to configure the headless device, the headless device is connected directly to the network, even if the remote device is disconnected.

Preferred embodiments of the invention can be used on a crypto graphic device, such as that shown in Figure 2.

In crypto graphic devices, the security operating procedure of the system divide the system into a red side and a black side. The procedures prevent the keyboard and monitor (red side) from being directly connected to the processing unit responsible for configuring of the Wifi (black side). A Red I Black separation is enforced to separate red side Plaintext [also known as PT] from black side Ciphertext [also known as CT], with the only route from the red side to the black side being through the encryption engine. This effectively stops any form of Plaintext data from the Red side keyboard being sent to the Black side external Wifi. However, accessing and configuring the Black side Wifi connection from another Black side device as described above solves this problem and does not break the Red / Black separation.

Embodiments of the invention can also be used on a mobile IF camera, without the need to physically access the camera. When the camera enters a new location it can be configured with a remote wireless device.

Embodiments of the invention can also be used on an internet enabled TV. Users may consider the standard television remote as cumbersome and difficult to use.

Embodiments of the invention enable a user to make use of their preferred tablet device for controlling and configuring their television. In this embodiment, the control unit can be configured to control the television, such as by changing channels, in response to commands received via the second wireless interface.

This embodiment also means if the original TV remote were mislaid, there would be an alternative method for changing channels etc. Embodiments of the invention can also be used in a cargo monitoring situation.

Where RFIDs give limited information, typically static in nature, a continuous monitoring and recording situation such as provided by embodiments of the invention is advantageous. Such an embodiment is depicted schematically in Figure 4. In this embodiment, the headless device 10 can include or be embedded in a locking mechanism 24 and monitoring unit 26. The monitoring unit 26 can be configured to monitor conditions inside a cargo container 28 on a vehicle, monitor the duration of a journey, monitor the location of the container 28, or any other parameter for which a measurement is desired. The locking mechanism can be operable to lock or unlock a door 30 of the container 28. The container may for example be used for carrying high value cargo.

The control unit 11 in this embodiment is operable to control the locking mechanism 24 to lock or unlock the door 30 and to receive measurements from the monitoring unit 26.

The control unit 11 can be operable to control the locking mechanism 24 in response to commands received from a remote device 16 via the second wireless interface. In addition, the control unit 11 can be operable to provide data from the monitoring unit 26 to the remote device 16 via the second wireless interface in response to a request for that data received from the remote wireless device 16.

The control unit 11 can be configured, in response to receiving a command or a request for data from the remote device 16, to send a request for authorisation to a remote authorisation unit via the first wireless interface 12 and only to act upon the command or to provide the data to the remote device 16 in response to an authorisation approval response from the authorisation unit 32.

In this embodiment, where the vehicle moves from a location with WiFi signal to a location without and then to a different location with a different WiFi signal, it can be seen that the ability to be able to remotely configure the headless device 10 to access each WiFi zone in turn without physically interacting with the device 10 is an advantage.

As the vehicle arrives at a depot or service station for example, the device 10 can connect to a local depot or service station WiFi in the manner described above.

When an authorised person wishes to request a feature of the lock and monitoring mechanism, he or she can send a signed request from their remote wireless device 16 to the device 10 via the second wireless interface.

As described above, the control unit 11 can process and act on the request locally, or the control unit 11 can send another signed command via the local depot or service station Wifi to the authorisation unit 32, such as shipping Head Quarters, for processing.

Such requests can include requests such as: unlock doors, check GPS route taken, check temperature range over duration of transport, upload telemetry to HO, enter overnight lockdown with movement tamper and alarm mode.

The request can in some embodiments be sent to the authorisation unit 32 for authorisation with various other monitoring information for processing at the authorisation unit 32.

The authorisation unit 32 can return an authorisation approval response and/or a command, possibly not the one requested, to the device 10 for processing and being acted upon by the control unit 11.

In other embodiments, request or commands can be received via the first wireless interface and acted on by the control unit 11 or, in some cases, authorisation can be sought via the second wireless interface in a manner corresponding to that described above.

All optional and preferred features and modifications of the described embodiments and dependent claims are usable in all aspects of the invention taught herein. Furthermore, the individual features of the dependent claims, as well as all optional and preferred features and modifications of the described embodiments are combinable and interchangeable with one another.

It is to be appreciated that certain embodiments of the invention as discussed herein may be incorporated as code (e.g., a software algorithm or program) residing in firmware and/or on computer useable medium having control logic for enabling execution on a computer system having a computer processor. Such a computer system typically includes memory storage configured to provide output from execution of the code which configures a processor in accordance with the execution. The code can be arranged as firmware or software, and can be organized as a set of modules such as discrete code modules, function calls, procedure calls or objects in an object-oriented programming environment. If implemented using modules, the code can comprise a single module or a plurality of modules that operate in cooperation with one another.

Optional embodiments of the invention can be understood as including the parts, elements and features referred to or indicated herein, individually or collectively, in any or all combinations of two or more of the parts, elements or features, and wherein specific integers are mentioned herein which have known equivalents in the art to which the invention relates, such known equivalents are deemed to be incorporated herein as if individually set forth.

Although illustrated embodiments of the present invention have been described, it should be understood that various changes, substitutions, and alterations can be made by one of ordinary skill in the art without departing from the present invention which is defined by the recitations in the claims below and equivalents thereof.

Claims

CLAIMS1. A headless computing device capable of wireless communication, including: a first wireless interface operable to connect wirelessly to a network; a second wireless interface configured as an access point and being operable to receive a wireless connection from a remote device; and a configuration system operable to configure the first wireless interface, the configuration unit being controllable via the second wireless interface.
2. A headless device according to claim 1, wherein the headless device is mobile and/or portable.
3. A headless device according to claim 1 or 2, wherein the configuration system includes a web server, the web server being operable to provide a web page to a remote device via the second wireless interface and being operable to configure the first wireless interface in response to data received via the web page from a remote device.
4. A headless device according to any preceding claim, including a routing system configured to route data received via the first wireless interface to a device connected via the second wireless interface and vice versa.
5. A headless device according to claim 4, wherein the routing system is arranged to receive communications from a said remote device connected via the second wireless interface and to use said communications to log the headless device in to a captive portal via the first wireless interface.
6. A headless device according to any preceding claim, wherein the headless device is arranged to directly access a network via the first wireless interface independently of a said remote device in response to a connection via the first wireless interface being made.
7. A headless device according to any preceding claim, including a control system for controlling non-network-related operation of the headless device, the control system being controllable via the first and/or second wireless interface.
8. A headless device according to claim 7, wherein the control system is configured to seek authorisation via the first and/or second wireless interface, preferably via the first wireless interface, of commands or requests received via the first and/or second wireless interface before acting on said commands or requests.
9. A headless device according to claim 7 or 8, wherein the headless device includes a security element for securing a building, vehicle or container, the security element being controllable by the control system.
10. A headless device according to claim 9, wherein the security element includes a locking mechanism for locking a door.
11. A headless device according to any preceding claim, wherein the headless device includes a monitoring unit, and wherein the headless device is configured to provide data from the monitoring unit via the first wireless interface andlor via the second wireless interface.
12. A headless device according to claim 11, wherein the headless device is configured to provide data from the monitoring unit via the first and/or second wireless interface in response to a request received via the first and/or second wireless interface and the headless device is configured to seek authorisation of a said request via the first andlor second wireless interface, preferably via the first wireless interface, before providing said data via the second wireless interface.
13. A container including a headless device according to any preceding claim.
14. A vehicle including a headless device according to any of claims 1 tol2 and/or including a container according to claim 13.
15. A computing device including a headless device according to any of claims 1 to 8 and a user input unit; wherein the user input unit is prevented from configuring the headless device.
16. A computing device according to claim 15, operable to access a network via the first wireless interface of the headless device.
17. A method of connecting a headless computing device capable of wireless communication to a wireless network via a first wireless interface, including: receiving a connection from a remote device via a second wireless interface; receiving configuration commands from the remote device via the second wireless interface; configuring the first wireless interface using the configuration commands and connecting the headless device to the network via the first wireless interface.
18. A method according to claim 17, including sending to the remote device details of available networks to which connection can be made via the first wireless interface.
19. A method according to claim 17 or 18, including sending to the remote device a web page using which a user of the remote device can provide the configuration commands.
20. A method according to any of claims 17 to 19, including, after connecting to the network, routing data between the remote device and the network.
21. A method according to claim 20, wherein routing data includes logging the headless device into a captive portal using data provided by the remote device.
22. A method according to any of claims 17 to 21, including receiving control instructions from the remote device and controlling non-network-related operation of the headless device in response to the control instructions.
23. A method according to claim 22, including seeking authorisation via the first and/or second wireless interface, preferably via the first wireless interface, for the control instructions before controlling operation of the headless device in response to the control instructions.
24. A method according to claim 22 or 23, wherein the headless device includes a locking mechanism for locking a door and controlling operation of the headless device includes locking and/or unlocking the locking mechanism.
25. A programmable component configured to perform the method of any of claims 17 to 24.
26. Program code for performing the method of any of claims l7to 24 when executed on a programmable component.