GB2595843A

GB2595843A - Safety system

Info

Publication number: GB2595843A
Application number: GB2005523.2A
Authority: GB
Inventors: Kimitri Andrew
Original assignee: Raynestorm Ltd
Current assignee: Raynestorm Ltd
Priority date: 2020-04-16
Filing date: 2020-04-16
Publication date: 2021-12-15
Also published as: GB202005523D0

Abstract

A safety system 100 comprises a light system that is configured to project light beams onto a ground surface, to thereby define a boundary 106 on the ground surface. The safety system is configured to detect when a user device 108a-108c crosses the boundary. In this manner, it is possible to detect when a person carrying the user device, e.g. smartphone, crosses the boundary. The safety system may be used in a construction site, for example to define a boundary corresponding to a safety perimeter around a piece of heavy machinery 102 or an area of the construction site. This may serve to improve safety of the construction site.

Description

SAFETY SYSTEM

FIELD OF THE INVENTION

The present invention relates to a safety system for detecting when a person crosses a boundary.

BACKGROUND OF THE INVENTION

There may be many hazards on a construction site, due to the nature of construction work and the types of equipment and machinery used in construction sites. Accordingly, ensuring that a construction site is safe is a primary concern in the construction industry, to try and reduce a risk of accidents which might result in injury to construction workers.

Various measures may be taken in order to improve construction site safety and the wellbeing of construction workers. An important measure is to conduct regular training of personnel, to make them aware of potential risks on the construction site, as well as how to minimise those risks.

Other measures include careful design and planning of a construction site, to ensure that personnel can safely move around the construction site.

Additionally, potentially hazardous areas or machinery in the construction site may be clearly marked, in order to inform personnel of potential hazards. Access to such potentially hazardous areas or machinery may also be restricted for safety reasons. Thus, only workers who are qualified to work in those areas or with such machinery may be allowed to access them. Typically, access to such potentially hazardous areas or machinery may be restricted by placing barriers or fencing around them in order to keep people at a safe distance. In some cases an identity check may be performed (e.g. by a security officer) to allow a worker into a potentially hazardous area. As an example, it may be desirable to establish a safety perimeter around a piece of heavy machinery, to ensure that workers not involved in operation of the heavy machinery remain at a safe distance. However, such safety measures are not always effective, and in some cases they can be difficult or impractical to implement. For example, in the case of heavy machinery that is a vehicle which may move across the construction site, it may be impractical to place barriers around it. Instead, warning lights on the vehicle are often used, to make workers aware of the potential hazard. In some cases, high-visibility cones may temporarily be placed around the vehicle, in order to indicate a safety perimeter around the vehicle.

SUMMARY OF THE INVENTION

At its most general, the present invention provides a safety system that is configured to detect when a person crosses a boundary. The boundary is defined by projecting a beam of light onto the ground. The system may be used in a construction site, or any other suitable environment. For example the safety system may be used to define a boundary corresponding to a safety perimeter around a piece of heavy machinery or an area of the construction site. This may enable safety of the construction site to be improved.

The light beam projected onto the ground may serve as a visual indicator of the boundary. For example, the light beam projected onto the ground may serve as a visual indicator of a safety perimeter (e.g. in a construction site). Additionally, detecting when a person crosses the boundary may facilitate enforcing the boundary, as well as minimising a risk of accident and/or injury when a person does cross the boundary. For example, the system may Generate an alert indicating that the boundary has been crossed, and/or machinery operating in an area defined by the boundary may be stopped.

As the boundary is defined by a light beam rather than by a physical object, this may facilitate moving the boundary. Thus, in contrast to situations where physical barriers are used, the boundary defined using the safety system of the invention may be quickly and easily moved to a new location.

As an example, the safety system of the invention may be used to define a boundary around a vehicle, such that the boundary moves together with the vehicle. Then, the system may detect when a person enters a safety perimeter around the vehicle.

This may be particularly beneficial in the context of heavy machinery in a construction site, where it may be impractical to place physical barriers around the heavy machinery, as the heavy machinery may need to be regularly moved around the construction site.

According to a first aspect of the invention, there is provided a safety system comprising a light system configured to project a light beam onto a ground surface, thereby defining a boundary on the ground surface, wherein the safety system is configured to detect when a user device crosses the boundary.

The light system may be any suitable system fcr projecting a beam of light onto the ground surface, in order to define the boundary on the ground surface. The light system may include a light source (e.g. a lamp or projector) which is configured to project the light beam. In some cases, the light system may include multiple light sources, which are configured to project multiple light beams onto the ground surface such that together they define the boundary.

The light system may include suitable optical components for projecting and/or focusing the light beam on the ground surface.

The boundary on the ground surface may be defined by a location at which the light beam projected by the light system is incident on the ground surface.

The boundary on the ground surface may have any shape or size, depending on a use of the safety system. The shape and size of the boundary may be adjusted by adjusting the light beam, e.g. by adjusting a shape of the light beam and/or a position at which the light beam is incident on the ground surface.

The boundary on the ground surface may define an area, i.e. the boundary may enclose an area on the ground surface. In this manner it, may be possible to detect when a person enters a particular area, e.g. in a construction site. For example, the boundary may define an area in a construction site, and/or an area around a piece of heavy machinery. In some cases, the boundary may define an area around a vehicle.

Alternatively the boundary may correspond to a border or threshold between two areas. In this manner, it may be possible to detect when a person passes from one area to another. For example, the boundary may correspond to a threshold of a doorway or a gateway, or some other passage between two areas.

The safety system is configured to detect when a user device crosses the boundary. In this manner, it is possible to detect when a person carrying the user device crosses the boundary. So, for example, workers in a construction site may be issued with user devices that they must carry when on-site, such that the safety system can detect when one of the workers crosses the boundary. This may serve to improve safety of the construction site, e.g. by automatically detecting when a worker enters an area that may potentially be hazardous. Of course, the safety system may be used in environments other than construction sites.

The safety system may detect when a user device crosses the boundary using any suitable means, some of which are discussed below. Thus, in addition to the light system, the safety system of the invention may include a detection system for detecting when a user device crosses the boundary. Such a detection system may include a computing device (e.g. a smartphone), and/or a remote server.

The safety system may be configured to determine a position of the user device relative to the boundary, so that the safety system can detect when the user device crosses the boundary.

As an example, the user device may be a smartphone or other personal computing device having suitable software installed thereon. Alternatively, the user device may be an electronic device such as an electronic tag or the like.

In some cases, the safety system may be communicatively coupled with the user device. This may facilitate determining a position of the user device relative to the boundary, so that the safety system can detect when the user device crosses the boundary.

As the boundary is defined by projecting a light beam onto the ground surface, it may be difficult at certain times of the day to see the boundary (e.g. when the boundary is located in direct sunlight). As a result, a person may accidentally cross the boundary, as they may not see it. Thus, the safety system of the invention enables detection of a user device crossing the boundary, even in conditions where the boundary may not be visible. This may serve to ensure safety at all times of day and in different weather conditions.

The safety system may be further configured tc determine an identifier of a user device that crosses the boundary. In this manner, the safety system may identify which user device crossed the boundary. For example, the user device may have an identifier that can be provided to the safety system via any suitable means. In some cases, the safety system may be configured to read an identifier from the user device, or the safety system may be configured to receive an identifier which is broadcast by the user device. The identifier may, for example, be information that is stored on the user device and that serves to uniquely identify the user device. The identifier may be in the form of an identification code, user or account name, or similar.

The safety system may be configured to record (i.e. store) information indicative of the identifier of a user device that crosses the boundary. Such information may, for example, be stored in a remote server of the safety system. The safety system may be further configured to, based on the identifier of the user device, determine an identity of a person carrying the user device. In this manner, the safety system may identify a person who has crossed the boundary, based on the identifier of the user device that they are carrying. By identifying a person who crossed the boundary, it may be possible to take appropriate measures to improve safety of the site. For example, further training (e.g. safety training) may be offered to a person who was determined to have crossed the boundary. Additionally alternatively, a warning or a sanction may be issued to a person who was determined to have crossed the boundary.

The safety system may include a database in which a plurality of user devices is registered. The database may store a respective identifier for each of the plurality of user devices. The database may associate each of the registered user devices with a respective person's identity. In this manner, the safety system can look up the corresponding identity based on the identifier of the user device that was detected to have crossed the boundary.

The safety system may be further configured to keep a record of instances when a user device crossed the boundary. In other words, the safety system may be configured to store data (or information) related to instances when a user device crossed the boundary. In this manner, the safety system may keep track of instances when the boundary was crossed. This may, for example, facilitate monitoring safety of an area defined by the boundary. A system administrator may then access the record maintained by the safety system, e.g. to check whether the boundary has been crossed, and if so how many times. This may enable the system administrator to implement appropriate measures for improving safety or security of the site.

The safety system may include a remote server configured to store the data related to the instances when a user device crossed the boundary. The safety system may further be configured to generate a user interface for accessing the data, e.g. via the internet.

The safety system may include a local controller configured to store the data related to the instances when a user device crossed the boundary. The local controller may be communicatively coupled with the remote server, so that the information can be transmitted from the local controller to the remote server. This may serve to ensure that data continues to be recorded at the controller even when connection to the remote server is lost (e.g. due to a problem at the remote server, or to 8 failure in communication with the remote server).

The safety system may be configured to record various data related to instances when the boundary was crossed by a user device. Such data may include: an identifier of the user device, an identity of a person who crossed the boundary (e.g. determined based on the identifier of the user device), a time at which the boundary was crossed, and/or a duration over which the user device remained within the boundary. Recording such data may ensure that the safety system keeps an accurate record of instances when the boundary was crossed, which may facilitate monitoring safety of a site.

The safety system may be configured to record various data related to the boundary during instances when the boundary was crossed by a user device. For example, such data may include an indication of a location of the boundary at a time when the boundary was crossed by the user device. This may, for example, be relevant where the boundary is movable, e.g. where the safety system is used with a vehicle. The safety system may include a global positioning system (GPS) module configured to provide a location of the boundary. The safety system may be configured to record a shape and/or dimension of the boundary at a time when the boundary was crossed by the user device. This may be relevant, for example, be relevant where the shape and/or size of the boundary is adjustable.

The safety system may be configured to record an identity of a person who is operating in an area defined by the boundary, at a time when the boundary is crossed by the user device. For example, where the boundary defines an area around a vehicle or heavy machinery, the safety system may be configured to record an identity of a person operating the vehicle or heavy machinery. The safety system may, for example, determine an identity of the person operating in the area defined by the boundary based on an identifier of a user device carried by that person.

The safety system may be further configured to generate an alert in response to detecting that a user device has crossed the boundary. Such an alert may serve to inform a person in the vicinity of the boundary that the boundary has been crossed, and therefore that there may be a safety risk. This may enable appropriate action to be taken, in order to reduce the risk of an accident. The alert may take any suitable form, and may be achieved in a variety of different ways.

In some embodiments, the alert may include an alert generated at the user device that crossed the boundary. In this manner, a person carrying the user device may be informed that they have crossed the boundary. This serve to inform the person that they may be in a potentially hazardous area, which may prompt them to leave the area. The alert at the user device may for example be an audio alert (e.g. an alarm), and/or a visual alert (e.g. an alert message displayed on a screen of the user device, and/or a flashing light on the user device). The alert at the user device may also be in the form of a vibration of the user device.

In some embodiments, the alert may include a modulation of the light beam projected onto the ground surface. For example, the light beam projected onto the ground surface may flash, and/or change colour. In this manner, anyone in the vicinity of the boundary may be informed that the boundary has been crossed, such that there may be a risk to safety.

In some embodiments, the alert may include an alert generated at a device located in an area defined by the boundary (i.e. at a device other than the user device that crossed the boundary). In this manner, a person operating in the area defined by the boundary may be informed that someone else has crossed the boundary. The person operating in the area may then take an appropriate action to ensure safety (e.g. they may stop the task they are currently performing). For example, the person operating in the area may have a user device, and the alert may be generated at the user device carried by that person. Where the person is operating a vehicle or machinery, the alert may be generated at the vehicle or machinery.

Of course, any combination of the alerts mentioned above may be used.

In some cases, the safety system may be configured to stop (e.g. shut down) machinery operating in an area defined by the boundary, in response to detecting that a user device has crossed the boundary.

The light system may include a plurality of light sources, each light source being configured to project a respective light beam onto the ground surface, wherein together the respective light beams define the boundary on the ground surface. This may facilitate arranging the boundary according to a desired shape and size, as well as facilitate defining a boundary having a complex shape. This may also facilitate adjusting a shape and size of the boundary, e.g. as the light sources may be movable relative to one another. The light sources may be arranged such that the light beams projected onto the ground surface form a continuous boundary.

In some embodiments, the boundary may comprise a plurality of sections, and the safety system may be further configured to determine which section of the boundary was crossed by the user device. In this manner, it may be possible to identify where a person crossed the boundary. This may provide useful information for assessing safety of a site. A section of the boundary may correspond to a portion or length of the boundary.

Where the light system includes a plurality of light sources, each light source may serve to define a respective section of the boundary. Thus, each of the respective light beams projected by the light sources may define a respective section of the boundary on the ground surface.

Where the safety system is configured to keep a record of instances when a user device crossed the boundary, the safety system may be configured to store information indicative of which section of the boundary was crossed by the user device. In some embodiments, the safety system may comprise the user device, and the user device may be configured to detect when it crosses the boundary. Thus, the user device may be part of the safety system, with the user device being configured to detect when it crosses the boundary. This may enable accurate and reliable detection of the user device crossing the boundary. Additionally, by performing such detection locally at the user device, this may reduce a processing load in other parts of the safety system. This may also reduce an amount of communication that is required between different parts of the system (e.g. between the user device and a remote server of the system). As an example, the user device may be a smartphone having software (e.g. an "app") installed thereon which is configured to detect when the smartphone crosses the boundary.

In some cases, the safety system may comprise a plurality of user devices, each user device being configured to detect when it crosses the boundary. As discussed above, each user device may have a unique identifier, which enables an identity of a person carrying the user device to be determined. Performing detection of crossing the boundary locally at each of the user devices may avoid having to centrally process location data for a large number of user devices. Accordingly, this configuration may enable efficient detection of when a user device crosses the boundary.

The safety system may further comprise a remote server, the user device being communicatively coupled to the remote server; and, following detecting that the user device has crossed the boundary, the user device being configured to transmit to the remote server information indicative of the user device crossing the boundary. In this manner, a local detection at the user device may be communicated to the remote server. As a result, the safety system may become centrally alerted to the fact that a person has crossed the boundary. The user device may be communicatively coupled to the remote server via any suitable communication means. For example, the user device may be communicatively coupled to the remote server over the internet, or some other suitable network. The information transmitted by the user device to the remote server may include a variety of data, including: an indication that the boundary was crossed, a time at which the boundary was crossed, a duration for which the boundary was crossed, an identifier of the user device and/or an identity of a person carrying the user device. Where the boundary includes a plurality of sections, the data may include an indication of which section of the boundary was crossed.

The user device may be configured to transmit the information to the remote server in response to detecting that it has crossed the boundary, e.g. immediately following the detection. Additionally or alternatively, the user device may be configured to transmit a report to the remote server at regular time intervals (e.g. every half hour or every hour).

Each report may include information indicative of whether the user device crossed the boundary during the last time interval.

The remote server may be configured to store the information received from the user device. Thus, the remote server may keep a record of instances when a user device crossed the boundary, as discussed above. The remote server may include the database mentioned above which associates the user device identifier with e person's identity.

The remote server may be a computing system that is connected to the internet. As an example, the remote server may be a cloud server.

Where the safety system includes a plurality cf user devices, each of the user devices may be communicatively coupled to the remote server. Then, following one of the user devices detecting that it has crossed the boundary, that user device may transmit to the remote server information indicative of that user device crossing the boundary. In this manner, the remote server may maintain a central record of all the times the boundary was breached by the plurality of user devices. This may facilitate monitoring of the boundary, as all of the relevant data may be collected at a single location.

The remote server may be configured to take certain actions in response to receiving information indicative that a user device has crossed the boundary. For example, the remote server may be configured to cenerate an alert in response to receiving information indicative that a user device has crossed the boundary. The alert may take various forms, as discussed above. For example, the remote server may be configured to provide a notification to the user device that crossed the boundary, and/or to provide a notification to a user device of a person operating in an area defined by the boundary. In some cases, the remote server may be configured to control the light system. Then, the remote server may be configured to control the light system to modulate the light beam projected by the light system (e.g. to cause the light beam to flash and/or change colour).

Additionally or alternatively to the remote server, the system may further comprise a local controller. The user device may be communicatively coupled to the local controller, e.g. via a wireless connection such as Bluetooth or Wi-Fi. Following detecting that the user device has crossed the boundary, the user device may be configured to transmit to the controller information indicative of the user device crossing the boundary. In this manner, a record may be kept at the controller of instances when a user device crossed the boundary. The controller may be configured to store any of the types of data discussed above relating to when a user device crosses the boundary. Keepinc a local (e.g. on-site) record in the controller may serve to ensure that the system can reliably keep track of user devices crossing the boundary. For example, this may serve to ensure that data continues to be recorded even when connection to the remote server is lost (e.g. due to a problem at the remote server, or to a failure in communication with the remote server).

The local controller may include any suitable computing device. In some cases, the local controller may be the same controller which is used for controlling the light system.

The local controller may be communicatively coupled to the remote server and configured to transmit to the remote server information relating to instances when a user device crossed the boundary. Thus, records which are stored locally at the controller may be transmitted to the remote server. In such a case, the user device need not transmit information indicative of it crossing the boundary directly to the remote server, and instead such information may be transmitted to the server via the controller.

In some embodiments, the user device may comprise a GPS module, and may be configured to detect when it crosses the boundary based on an output of the GPS module. In this manner, the user device may determine when it crosses the boundary based on a location of the user device determined from the GPS module. This may provide a reliable and accurate means for detecting when the user device crosses the boundary. The GPS module may be configured to output a location of the user device. The user device may be configured to determine when it crosses the boundary by comparing a location of the user device (obtained from the GPS module) with a location of the boundary.

The user device may be configured to store information indicative of a location of the boundary. In this manner, the user device may detect when it crosses the boundary based on the output from the CPS module and the information that is indicative of the location of the boundary. For example, the user device may store information such as coordinates, a shape, and/or a size of the boundary. In some cases, the user device may receive the information indicative of a location of the boundary from the remote server. For example, the remote server may be configured to transmit the information indicative of a location of the boundary to the user device when the safety system is activated.

Where the boundary comprises a plurality of sections, the user device may be configured to determine which section of the boundary is crossed based on the output from the GPS module.

In some embodiments, the safety system may further comprise a signal emitter, and the user device may be configured to: receive a signal emitted by the signal emitter; and determine when the user device crosses the boundary based on the signal received from the signal emitter. This may enable the user device to accurately determine when it crosses the boundary. For example, the user device may be configured to determine when the user device crosses the boundary based on a strength of the signal received from the signal emitter.

The user device may be configured to determine a distance between the user device and the signal emitter based on a strength of the signal received from the signal emitter. Then, based on the determined distance between the user device and the signal emitter, the user device may determine its location relative to the boundary (and thus whether it has crossed the boundary).

A location of the signal emitter relative to the boundary may be known to the user device, to enable the user device to determine the location of the user device relative to the boundary based on the received signal. For example, the emitter may be located at the boundary, or at a known location within the boundary. In some cases, information indicative of the location of the signal emitter relative to the boundary may be provided to the user device by the remote server. For example, the remote server may be configured to transmit the information indicative of the location of the signal emitter relative to the boundary to the user device when the safety system is activated. Information indicative of the location of the signal emitter relative to the boundary may include a location (e.g. coordinates) of the signal emitter, and a location (e.g. coordinates) of the boundary. Additionally or alternatively, the information indicative of the location of the signal emitter relative to the boundary may be included in the signal emitted by the signal emitter.

The emitter may be a radiofrequency emitter that is configured to emit a radiofrequency signal. The radiofrequency signal can then be received by the user device, such that the user device can determine a distance to the emitter based on a strength of the received signal. As an example, the emitter may be an iBeacon proximity device.

The signal emitter may be located within a housing of a light source of the light system. In this manner, the signal emitter may be integrated with the light system. This may avoid having to mount the light system and emitter separately, thus facilitating installation and configuration of the safety system. This may also facilitate locating the emitter at a known location relative to the boundary. As a result, an accuracy with which detection of a user device crossing the boundary can be improved.

In some embodiments, the safety system may comprise a plurality of signal emitters, and: each of the signal emitters may be configured to emit a signal comprising a respective identifier; and the user device may be configured to receive the signals emitted by the plurality of signal emitters and determine, based on the received signals, when the user device crosses the boundary and a section of the boundary was crossed. Thus, using the signals received from the plurality of emitters, the user device can determine which section of the boundary it has crossed. Similarly to the discussion above, the user device may be configured to determine its position relative to the boundary based on the strengths of the signals received from the plurality of emitters. For example, the user device may triangulate its position based on the strengths of the signals received from the plurality of emitters. The locations of the plurality of emitters relative to the boundary may be known to the user device, so that the user device can determine its location relative to the boundary.

By including identifiers in the signals from the signal emitters, the user device can distinguish between the signals from the different emitters. This may enable the user device to determine its position relative to the boundary based on the different signals received.

In some cases, each of the plurality of signal emitters may be associated with a respective zone of the boundary. This may facilitate determining which section of the boundary was crossed. In such a case, each of the plurality of emitters may have a respective threshold distance associated therewith. Then, if the user device determines that it is at a distance less than a threshold distance for one of the emitters, the user device may determine that it has crossed a section of the boundary corresponding to that emitter. The user device may determine which section of the boundary it has crossed based on the identifier received from the emitter whose threshold was crossed.

Where the light system includes a plurality of light sources, each of the plurality of emitters may be located within a housing of a respective light source. In this manner, a light source may serve to define a section of the boundary via the light beam projected by that light source, whilst the emitter integrated within that light source may serve to detect when a user device crosses that section of the boundary. Such integration of the emitters with the light system may greatly simplify setting up of the safety system.

In some embodiments, the safety system may further comprise a proximity sensor configured to detect the user device, and the safety system may be configured to determine when the user device crosses the boundary based on an output from the proximity sensor. Such a setup may enable accurate detection of when the user device crosses the boundary. The proximity sensor may be any suitable sensor for detecting a presence of the user device. The proximity sensor may be configured to detect the user device when the user device crosses the boundary. For instance, the output of the sensor may be indicative of a presence of the user device within the boundary, when the user device crosses the boundary.

The proximity sensor may be configured to detect a distance to the user device. Thus, the output of the proximity sensor may be indicative of a distance between the proximity sensor and the user device. The proximity sensor may be configured to detect a distance to the user device using any suitable sensing means.

The proximity sensor may be at a known location relative to the boundary, such that the detected distance between the user device and the proximity sensor can be used to detect when the user device crosses the boundary. For example, the proximity sensor may be located at the boundary, or within the boundary.

The proximity sensor may itself be configured to determine when the user device crosses the boundary.

Alternatively, the output from the proximity sensor may be used by another part of the safety system to perform the determination. For example, the proximity sensor may be communicatively coupled to a local controller or a remote server of the safety system, which is configured to determine when the user device crosses the boundary based on the received output from the proximity sensor.

The proximity sensor may be configured to receive (or detect) a signal emitted from the user device and determine the distance to the user device based on the signal from the user device. As an example, the proximity sensor may include a radiofrequency receiver. The user device may then be configured to emit a signal (e.g. a radiofrequency signal) that is received by the proximity sensor. The proximity sensor may be configured to determine a distance to the user device based on a strength of the signal received from the user device. The signal emitted by the user device may include information (e.g. an identifier) for identifying the user device and/or a person carrying the user device. In this manner, the safety system may determine who has crossed the boundary.

The proximity sensor may be located within a housing of a light source of the light system. In this manner, the proximity sensor may be integrated with the light system. This may avoid having to mount the light system and proximity sensor separately, thus facilitating installation and configuration of the safety system. This may also facilitate locating the proximity sensor at a known location relative to the boundary. As a result, an accuracy with which detection of a user device crossing the boundary can be improved.

In some embodiments, the safety system may comprise a plurality of proximity sensors, and: each of the proximity sensors may be associated with a respective section of the boundary; and the safety system may be configured to determine, based on outputs from the plurality of proximity sensors, when the user device crosses the boundary and which section of the boundary was crossed. Thus, using a plurality of proximity sensors, it may be possible to determine which section of the boundary was crossed. The locations of the plurality of proximity sensors relative to the boundary may be known, so that the safety system can determine the user device's position relative to the boundary based on the distances determined by the proximity sensors.

In some cases, each of the plurality of proximity sensors may be configured to detect when the user device crosses the section of the boundary associated with that proximity sensor. In some case, each of the plurality of proximity sensors may be configured to detect a respective distance to the user device. Each of the plurality of proximity sensors may have a respective threshold distance associated therewith. Then, if one of the proximity sensors detects that the user device is at a distance of less than the threshold distance for that proximity sensor, the safety system may determine that the section of the boundary corresponding to that proximity sensor was crossed.

Where the light system includes a plurality of light sources, each of the plurality of proximity sensors may be located within a housing of a respective light source. In this manner, a light source may serve to define a section of the boundary via the light beam projected by that light source, whilst the proximity sensor integrated within that light source may serve to detect when a user device crosses that section of the boundary. Such integration of the proximity sensors with the light system may greatly simplify setting up of the safety system.

Multiple techniques are discussed above for detecting when the user device crosses the boundary, including detection by the user device itself (e.g. with a GE'S module, or by detecting a signal from a signal emitter) as well as detection using a proximity sensor. Of course, any of these techniques may be combined together. Use of multiple detection techniques together may improve an accuracy and reliability with which the safety system can detect when a user device has crossed the boundary. As an example, the user device may be configured to detect when it has crossed the boundary based on the output from its GPS module, and the signal received from the signal emitter.

In some embodiments, the light system is controllable to adjust the boundary. This may enable a location, shape, and/or size of the boundary to be adjusted. The light system may include any suitable mechanism for adjusting the boundary. As an example, the light system may include a light source which is mounted on a movable arm (e.g. a hydraulic arm), such that the position of the light source can be adjusted to adjust a position of the boundary. As another example, the light system may include optical components which can be controlled to adjust the boundary. The light system may include a controller for controlling (e.g. settinc and/or adjusting) the boundary. The controller may include an input interface, which may enable a user to set parameters (e.g. location, shape and/or size) of the boundary. The controller may the control the light system based on parameters set by the user via the input interface.

In some embodiments, the safety system may further comprise a camera configured to capture an image of the boundary. This may facilitate identifying a person who has crossed the boundary. For instance, this may be useful where a person is carrying someone else's user device, such that they cannot be identified based on the user device that they are carrying. The camera may be configured to capture an image of a person crossing the boundary, e.g. the camera may be positioned and oriented such that it is capable of capturing an image of a person who crosses the boundary. The camera may be a still camera (e.g. configured to capture still images), or a video camera (e.g. configured to capture a video recording). In some cases, the safety system may include multiple cameras, e.g. to cover different sections of the boundary.

The safety system may be configured to associate a captured image with a detection that the boundary was crossed by a user device. This may facilitate verifying an identity of a person who has crossed the boundary. For instance the safety system may associate a captured image with a detection that the boundary was crossed by a user device based on a time stamp of the image, and a time at which the boundary was crossed by the user device.

In some cases, the camera may be configured to capture an image in response to the safety system detecting that a user device has crossed the boundary. The safety system may thus automatically capture an image of a person crossing the boundary.

The safety system of the first aspect of the invention may be used in various different contexts. In one example, the safety system of the first aspect of the invention may be used with heavy machinery.

Thus, according to an embodiment of the invention, there is provided heavy machinery comprising a safety system according to the first aspect of the invention, wherein the light system is mounted on the heavy machinery and arranged to define a boundary on the ground surface around the heavy machinery. In this manner, the boundary may serve as a safety perimeter around the heavy machinery, such that the safety system may detect whenever a user device enters the safety perimeter. This may serve to ensure that people remain at a safe distance away from the heavy machinery.

The heavy machinery may be any type of heavy machinery, e.g. which may be used in a construction site or other work site. For example, heavy machinery may include diggers, cranes, vehicles (e.g. trucks or tractors), compactors, or similar.

Light sources of the light system may be mounted on an outside of the heavy machinery, such that they can project light beams onto the ground surface around the heavy machinery. The light sources may be mountable or securable to the heavy machinery via any suitable means.

The safety system may comprise a user interface disposed in a cockpit of the heavy machinery. This may enable an operator of the heavy machinery to view and/or interact with the user interface whilst they are operating the heavy machinery.

The user interface may include a display configured to display an alert when the safety system detects that a user device has crossed the boundary.

The user interface may include an input interface for receiving an input from a user. For example, the input interface may enable a user to activate and/or deactivate the safety system. The input interface may enable a user to set a parameter (e.g. location, shape and/or size) of the boundary. The light system may then be controlled according to the parameter input by the user. For example, the user may input into the user interface a distance of the boundary from the heavy machinery. Then, the light system may be controlled to define the boundary at the desired distance away from the heavy machinery.

Similarly, the safety system of the first aspect of the invention may be used with a vehicle. Thus, according to an embodiment of the invention, there is provided a vehicle comprising a safety system according to the first aspect of the invention, wherein the light system is mounted on the vehicle and arranged to define a boundary on the ground surface around the vehicle. The safety system may comprise a user interface disposed in a cockpit of the vehicle. Features discussed above in relation to configuration of the safety system with the heavy machinery may be applied to embodiments where the safety system is used with a vehicle.

According to a second aspect of the invention, there is provided a method comprising: projecting, with a light system, a light beam onto a ground surface to define a boundary on the ground surface; and detecting when a user device crosses the boundary. The method of the second aspect of the invention may be performed using the safety system of the first aspect of the invention. Therefore, any features discussed above in relation to the first aspect of the invention may be incorporated into the method of the second aspect of the invention.

In some embodiments, the method may further comprise determining an identifier of a user device that crosses the boundary.

In some embodiments, the method may further comprise determining an identity of a person carrying the user device, based on the identifier of the user device.

In some embodiments, the method may further comprise keeping a record of instances where a user device crossed the boundary.

In some embodiments, the method may further comprise generating an alert in response to detecting that a user device has crossed the boundary.

In some embodiments, the boundary may comprise a plurality of sections, and the method may further comprise determining which section of the boundary was crossed by the user device.

In some embodiments, the method may comprise detecting by the user device when it crosses the boundary.

In some embodiments, the user device may be communicatively coupled to a remote server, and the method may further comprise, following detecting by the user device that it has crossed the boundary, transmitting from the user device to the remote server information indicative of the user device crossing the boundary.

In some embodiments, the user device may comprise a GPS module, and the method may comprise detecting by the user device when it crosses the boundary based on an output from the GPS module.

In some embodiments, the method may further comprise: receiving, at the user device, a signal emitted by a signal emitter; and determining when the user device crosses the boundary based on the signal received from the signal emitter.

In some embodiments, the method may further comprise: receiving, at the user device, signals emitted by a plurality of signal emitters, where each signal emitter is configured to emit a signal comprising a respective identifier, and where each signal emitter is associated with a respective section of the boundary, and determining at the user device based on the received signals when the user device crosses the boundary and which section of the boundary was crossed.

In some embodiments, the method may comprise detecting, with a proximity sensor, a distance from the proximity sensor to the user device and, based on an output from the proximity sensor, determining when the user device crosses the boundary.

In some embodiments, the method may comprise receiving, at the proximity sensor, a signal emitted from the user device and determining the distance from the proximity sensor to the user device based on the signal from the user device.

In some embodiments, the method may comprise: with each of a plurality of proximity sensors, detecting a respective distance to the user device, where each of the plurality of proximity sensors is associated with a respective section of the boundary, and determining, based on outputs from the plurality of proximity sensors, when the user device crosses the boundary and which section of the boundary was crossed.

In some embodiments, the method may further comprise controlling the light system to adjust the boundary.

In some embodiments, the method may further comprise capturing, with a camera, an image of the boundary.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention will now be described by way of example with reference to the accompanying drawings, in which: Fig. 1 is a schematic illustration of a safety system according to an embodiment of the invention; Fig. 2 is a schematic side view of a piece of heavy machinery that includes a light system which forms part of a safety system according to an embodiment of the invention; Fig. 3 is a schematic front view of a light source of a light system which forms part of a safety system according to an embodiment of the invention; and Fig. 4 is a table illustrating a record kept by a safety system that is an embodiment of the invention, the record including information relating to instances when a boundary of the safety system was crossed.

DETAILED DESCRIPTION; FURTHER OPTIONS AND PREFERENCES Fig. 1 is a schematic view of a safety system 100 according to an embodiment of the invention. The safety system 100 includes a light system configured to project light beams onto a ground surface in order to define a boundary on the ground surface. The safety system 100 is further configured to detect when a user device crosses the boundary. The safety system 100 may be used in any suitable context, where it may be desirable to monitor crossing of a boundary. As an example, the safety system 100 may be used in a construction site, in order to monitor access to an area of the construction site that may be potentially hazardous. In the example shown, the safety system is used to monitor a boundary around a piece of heavy machinery 102. The heavy machinery 102 may be any type of heavy equipment that may be used in a construction site or other work site, such as a digger, a crane, a vehicle (e.g. a truck or tractor), a compactor, or similar.

As mentioned above, the safety system 100 includes a light system. The light system includes a set of light sources 104a-d, each of which is mounted on a respective side of the heavy machinery 102. Each of the light sources 104a-d is arranged to project a respective beam of light onto a ground surface on which the heavy machinery 102 is disposed. The light beams projected by the light sources 104a-d are illustrated by the dashed lines in Fig. 1. Together, the light beams projected by the light sources 104a-d onto the ground surface define a continuous boundary 106 around the heavy machinery 102. Fig. 1 shows a top view of the heavy machinery 102 and an area around the heavy machinery 102. In the example shown, there are four light sources 104a-d, each of the light sources being arranged to project a substantially straight line onto the ground surface. As a result, the boundary 106 may have a substantially rectangular shape. However, in other examples, the light system may include different numbers and/or arrangements of light sources, in order to define boundaries with different shapes on the ground surface.

Each of the light sources 104a-d may be in the form of a lamp or projector configured to project a beam of light that is shaped to define a respective section of the boundary 106.

Thus, the light beam projected by light source 104a may define a first section 106a of the boundary 106, the light beam projected by the light source 104b may define a second section 106b of the boundary 106, the light beam projected by light source 104c may define a third section 106c of the boundary 106, and the light beam projected by light source 104d may define a fourth section 106d of the boundary 106. The light sources 104a-d may include suitable optics for focusing the light beams on the ground surface around the heavy machinery 102, so that the boundary may be clearly defined. The light beams projected by the light sources 104a-d may be of any suitable colour. For example, the light beams may be red, to provide a visual warning to people in a vicinity of the heavy machinery 102.

The boundary 106 defines an area around the heavy machinery 102, and may act as a safety perimeter around the heavy machinery 102. For instance, the boundary 106 may be defined at what is deemed to be a safe distance away from the heavy machinery, e.g. to ensure that a person standing at the boundary 106 is not at risk from the heavy machinery 102. As an example, the boundary 106 may be defined 4 m or 5 m away from the heavy machinery 102. Of course, the distance at which the boundary 102 is defined from the heavy machinery 102 may depend on the type of heavy machinery 102. As the light sources 104a-d are mounted on the heavy machinery 102, the boundary 106 may move together with the heavy machinery 102. In particular, a position of the boundary 106 relative to the heavy machinery 102 may remain constant, regardless of movement of the heavy machinery 102 around a site. This may serve to ensure that a safety perimeter is continuously defined around the heavy machinery 102.

A plurality of user devices 108a-c are registered with the safety system 100, with the safety system 100 being configured to detect when any one of the user devices crosses the boundary 106. By detecting when a user device crosses the boundary 106, it may be possible to detect when someone crosses the boundary. For example, each worker on a construction may be required to carry a personal user device whilst they are on the construction site. In this manner, when a worker crosses the boundary 106, this may be detected by detecting that their user device has been carried across the boundary 106. In some embodiments, the user devices 108a-c may be considered as part of the safety system (e.g. where the user devices 108a-c take an active role in detecting crossing of the boundary 106). The user devices 108a-c may include any suitable type of electronic device, such as a smartphone or other portable computing device. The user devices 108a-c may include software installed thereon (e.g. an application) that is used for integrating the user devices 108a-c with the safety system 100. However, in some examples, the user devices 108a-c need not necessarily be in the form of a computing device, e.g. a user device may include any type of device capable of being detected by the safety system 100, such as an electronic tag or similar. The safety system 100 may utilise a variety of techniques for detecting when a user device crosses the boundary 106, several of which are discussed below.

In the example shown in Fig. 1, a first user device 108a is located outside the boundary 106, whilst a second user device 108b is located inside the boundary 106 (i.e. inside the area defined by the boundary 106). A third user device 108c is disposed in the heavy machinery 102. For example, the third user device 108c may be carried by an operator of the heavy machinery 102, who is located in a cockpit of the heavy machinery 102. The safety system 100 may be aware of the fact that the third user device 168c belongs to an operator of the heavy machinery 102. In this manner, the safety system 100 may not consider the presence of the third user device 108c inside the boundary as a breach of the boundary 106. For example, the operator may indicate via an application on the third user device 108c that they are operating the heavy machinery 102, such that they are recorded in the system as being allowed to be within the boundary 106.

The safety system 100 further includes a local controller 110 located in the cockpit of the heavy machinery 102. The controller 110 may include a display (e.g. a screen) for displaying information related to the safety system 100, and an input interface (e.g. a keyboard/keypad, and/or touchscreen) for receiving inputs from a user. The controller 110 may, for example, be implemented by a computing device (e.g. a tablet computer), or by an on-board computer of the heavy machinery 102. The controller 110 may be configured to control the light system. For instance, the controller 110 may be configured to control a shape and size of the boundary 106 defined on the ground surface, by controlling the light sources 104a-d. Various parameters of the light sources 104a-d may be controllable in order to control the shape and size of the boundary 106, such as a position, angle and/or focus of each of the light sources 104a-d. As an example, each of the light sources 104a-d may be mounted on the heavy machinery 102 via a respective controllable arm (e.g. a hydraulic arm), such that a position and angle of each light source 104a-d can be varied. In this manner, a user may input parameters for the boundary 106 (e.g. distance of the boundary 106 from the heavy machinery 102) via the input interface of the controller 110, and the controller 110 may control the light system accordingly to provide the desired boundary 106 around the heavy machinery 102. The controller 110 may also be configured to control functions of the heavy machinery 102. The controller 110 may be communicatively coupled to the user devices 108a-c via a wireless connection, e.g. via Wi-Fi or Bluetooth or similar, or via a cellular phone network.

The safety system 100 also includes a remote server 112.

The remote server 112 is communicatively coupled to the controller 110 and each of the user devices 108a-c that are registered with the safety system 100 via a network 114 (e.g. the internet). The controller 110 and the user devices 108a-c may access the network 114 wirelessly, e.g. via a cellular phone network.

The remote server 112 is configured to store information related to operation of the safety system 100. In particular, the remote server 112 is configured to store, for each of the user devices 108a-c, a respective identifier and identification information for a person associated with that user device. For example, prior to working on a site, a person may download an application onto their user device (e.g. smartphone), and register with the safety system 100 via the application. As part of the registration process, the person may be required to enter identification information, such as their name. The remote server 112 may then generate an identifier (e.g. an identification code) for the person's user device, and store the identifier together with the person's identification information in a user database in the remote server 112. In this manner, the user database in the remote server 112 may associate each user device to a corresponding person. This may enable the safety system 100 to determine who has crossed the boundary 106, based on a detection that one of the user devices 108a-c has crossed the boundary 106.

The remote server 112 is further configured to maintain a record of instances when the boundary 106 was crossed. In particular, each time the safety system 100 detects that a user device has crossed the boundary, the remote server may record (i.e. store) data such as the identifier of the user device that crossed the boundary 106, identity of the person who crossed the boundary 106, duration for which the boundary 106 was crossed, which section of the boundary 106 was crossed, or any other relevant data. The record maintained by the remote server 112 may be stored as a database, with entries in the database corresponding to different instances when the boundary 106 was crossed by a user device. Fig. 4 illustrates an example of a record of instances of crossing the boundary 106 that may be maintained by the remote server 112.

Additionally, the controller 110 may be configured to store a record of instances when the boundary was crossed by a user device. Thus, when the system 100 detects that a user device has crossed the boundary 106, the controller may store data similar to that discussed above in relation to the remote server 112. Storing such a record locally at the controller 110 may serve to ensure that the system 100 can continue to record data, even when connection to the remote server 112 is lost. The controller 110 may be configured to regularly transmit to the remote server 112 information indicative of instances when the boundary was crossed, to ensure that the record maintained at the remote server 112 is accurate and up-to-date.

The remote server 112 is configured to generate an interface for viewing the record of instances when the boundary 106 was crossed. For example, the interface may be viewable on a computer 116 which is communicatively coupled to the remote server 112 via the network 114. In this manner, a manager or person in charge may consult the record, in order to monitor crossing of the boundary 106. Thus, for instance, if the manager or person in charge sees from the record that a particular person is repeatedly crossing the boundary, they may assign that person to further safety training. The interface may be provided as a website that is accessible by the computer 116. Access to the interface may be restricted (e.g. the interface may be protected by a password, and/or require login details), such that only an authorised person may access the interface. In some cases, the interface generated by the remote server 112 may also be viewable via an application installed on one or more of the user devices 108a-c.

The safety system 100 may be configured to perform certain actions in response to detecting that a user device has crossed the boundary 106. For instance, when the safety system 100 detects that a user device has crossed the boundary 106, the safety system 100 may be configured to generate an alert. The alert may take various different forms. In one example, an alert may be generated at a user device that is detected to have crossed the boundary 106. So, in the case of Fig. 1, the safety system 100 may detect that the user device 108b has crossed the boundary 106. Then, an alert may be generated at the user device 108b. As another example, an alert may be generated at a user device of a person operating the heavy machinery 102 (i.e. user device 108c in the example of Fig. 1). An alert on one of the user devices may be in the form of a notification, an alarm and/or a vibration at the user device. An alert may also be generated at the controller 110. For example, a notification may appear on the display of the controller 110, to inform the person operating the heavy machinery 102 that the boundary 106 has been crossed. An alert may also be in the form of a modulation of the light beams projected by the light sources 104a-d. For example, the controller 110 may control the light sources 104a-d, in order to cause the light beams projected by the light sources 104a-d to flash and/or change colour. In this manner, people in the vicinity of the boundary 106 may be informed that someone has crossed the boundary 106. Of course, any combination of these different alert types may be used.

The generation of alerts may be controlled by different parts of the safety system 160. In one embodiment, the remote server 112 may be configured to control generation of alerts. Thus, when the safety system 100 detects that a user device has crossed the boundary 106, the remote server 112 may transmit a control signal to one or more of the controller 110 and user devices 108a-c, in order to cause generation of an alert at one or more of the controller 110 and user devices 108a-c. For example, to generate an alert via the light sources 104a-d, the remote server may transmit a control signal to the controller 110 which causes the controller 110 to, upon receipt of the control signal, to generate an alert with the light sources 104a-d. To generate an alert via a user device, the remote server 112 may transmit a control signal to the user device which causes the user device to, upon receipt of the control signal, generate an alert. As an example, the control signal from the remote server 112 to the user device may be in the form of a push notification. Alternatively, generation of an alert may be controlled directly at the controller 110 and/or the user devices 108a-c (e.g. rather than at the remote server 112).

In some embodiments, the safety system 100 may be configured to halt or otherwise deactivate the heavy machinery 102 when the system detects that a user device has crossed the boundary 106. This may avoid the heavy machinery 102 continuing to operate whilst someone is located inside the boundary 106. For example, in response to a detection that a user device has crossed the boundary, the remote server 112 may be configured to transmit a control signal to the controller 110, which causes the controller 110 to halt or otherwise deactivate the heavy machinery 102.

In some embodiments, the safety system 100 may further include one or more cameras (not shown) which are arranged to capture an image of the boundary 106. In this manner, an image may be captured of a person crossing the boundary 106. This may facilitate verifying an identity of a person who has crossed the boundary 106. The one or more cameras may be connected to the controller 110 such that they are controlled by the controller 110. The controller 110 may also be configured to store images captured by the one or more cameras. In some cases, the safety system 100 may be configured to capture an imace with the one or more cameras in response to a detection that a user device has crossed the boundary 106.

We will now describe various techniques that may be used by the safety system 100 for detecting when a user device crosses the boundary 106.

GPS-based detection One technique for detecting when a user device crosses the boundary 106 involves using a GPS location of the user device. In some embodiments, each of the user devices 108a-c is provided with a respective GPS module, which can be used to determine a location of the user device. The safety system 100 may then detect when one of the user devices crosses the boundary 106, based on the GPS location of that user device. Each of the user devices 108e-c may have an application installed thereon which is configured to monitor the location of the user device based on an output from the GPS module, and to detect when the user device crosses the boundary 106.

To enable the user devices to detect when they cross the boundary 106, each of the user devices is provided with coordinate information for the boundary 106. In this manner, each of the user devices 108a-c is aware of a geographical location of the boundary. In some examples, coordinate information for the boundary 106 may be determined by the controller 110. In such a example, an operator of the heavy machinery 102 may set parameters (e.g. shape and size) of the boundary 106 via the input interface on the controller 110.

The controller 110 may further determine a current location of the heavy machinery 102. The current location of the heavy machinery 102 may be obtained from a GPS module in the controller 110 or the heavy machinery 102, or from the GPS module of the operator's user device (i.e. the third user device 108c). Then, based on the parameters of the boundary 106 and the current location of the heavy machinery 102, the controller 110 may determine coordinate information for the boundary 106, i.e. coordinates that are indicative of a geographical location of the boundary 106. The controller 110 may then transmit the coordinate information for the boundary 106 to the remote server 112, which may in turn transmit the coordinate information to the user devices 108a-c. Alternatively, the controller 110 may transmit the coordinate information directly to the user devices 108a-c, e.g. over a cellular phone network, wireless local network, or by a communication protocol such as Bluetooth.

Using the coordinate information for the boundary 106, each user device may determine its location relative to the boundary, by comparing the output from its GPS module to the coordinate information. Based on such a comparison, a user device may then detect when it crosses the boundary 106. For example, a user device may determine that it has crossed the boundary 106 when the output from its GPS module indicates that it is located inside the boundary 106. The user device may also be configured to determine which section of the boundary 106 it has crossed. For example, the coordinate information for the boundary 106 may include an indication of locations of different sections of the boundary (e.g. sections 106a-d), so that the user device can determine which section of the boundary 106 it has crossed.

In the example of Fig. 1, the second user device 108b may thus detect that it has crossed the boundary 108b. Upon such detection, the user device 108b may notify other parts of the safety system 100. In particular, the user device 108b may transmit to the remote server 112 information indicative of the user device crossing the boundary (and, if applicable, which section of the boundary was crossed). The information transmitted by the user device 108b may include an identifier of the device, so that the remote server 112 can determine which device and person crossed the boundary 106. This information may be stored in a record maintained by the remote server 112, as discussed above. Upon receiving the information from the user device 108b, the remote server 112 may generate an alert, as discussed above. In some cases, the user device 108b itself may be configured to generate an alert (e.g. in the form of an alarm or vibration of the user device 108b), when it detects that it has crossed the boundary 106. In some cases, the user device 108b may be configured to transmit the information indicative of the user device crossing the boundary 106 to the controller 110 (e.g. rather than directly to the remote server 112). Then, such information may be transmitted by the controller 110 to the remote server 112.

Emitter-based detection Another technique for detecting when a user device crosses the boundary involves detection by the user device of a signal emitted by an emitter. In some embodiments, the safety system 100 may include a set of signal emitters. In such embodiments, the features in Fig. 1 indicated by reference numerals 118a-d correspond to signal emitters which are arranged around the heavy machinery 102. Each signal emitter is disposed in a respective one of the light sources 104a-d, e.g. in a housing of the light source. However, the signal emitters 118a-d need not necessarily be disposed in the light sources 104a-d, e.g. they may be disposed next to the light sources 104a-d or at different locations around the heavy machinery 102.

Each of the signal emitters 118a-d is configured to emit a signal that is receivable by user devices that are located in a vicinity of the boundary 106. The signal emitters 118a-d may for example be radiofrequency emitters that are configured to emit radiofrequency signals. As an example, iBeacon proximity devices may be used as the signal emitters 118a-d, such that they can communicate with the user devices via Bluetooth. The signal emitted by each signal emitter may include information identifying that signal emitter, e.g. an identifier. In this manner, a user device receiving signals from the signal emitters 118a-d may distinguish the received signals from one another. In some cases, the signal emitters 118a-d may be connected to the controller 110, such that the controller 110 can control the signals emitted by the signal emitters 118a-d.

The positions of the signal emitters 118a-d relative to the boundary 106 are known and provided to the user devices 108a-c. In this manner, a user device can determine its distance to the boundary, so that it can detect when it crosses the boundary. For example, the positions of the signal emitters 118a-d relative to the boundary 106 may be determined based on known locations of the signal emitters 118a-d (i.e. in the light sources 104a-d) and parameters (e.g. shape and size) of the boundary 106. Information indicative of the positions of the signal emitters 118a-d relative to the boundary 106 may be provided to the user devices 108a-c by the controller 110, and/or by the remote server 112. In some cases, such information may be included in the signals emitted by the signal emitters, such that it is directly provided to the user devices 108a-c. Additionally, similarly to the discussion above, the user devices 108a-c may be provided with coordinate information for the boundary 106, which may facilitate determining of a position relative to the boundary 106.

Upon receiving the signals from the signal emitters 118a-d, each of the user devices 108a-c may be configured to determine a distance or position relative to the boundary based on strengths of the received signals. In this manner, a user device may determine when it crosses the boundary 106. For example, if a user device determines, based on a signal strength from one of the signal emitters 118a-d, that its distance to the signal emitter is less than a distance from the signal emitter to the boundary, then the user device may determine that it has crossed the boundary. In some cases, the user devices 108a-c may perform triangulation calculations based on the strengths of the received signals, in order to determine their distance or position relative to the boundary 106.

The user devices 108a-c may also be configured to determine, based on the signals received from the signal emitters 118a-d, which section of the boundary was crossed.

This may be achieved in a variety of ways. In one example, a user device may perform a calculation (e.g. triangulation) based on the received signals to calculate its position relative to the boundary 106. In this manner, it may determine when it crosses the boundary 106, and which part of the boundary 106 has been crossed. In another example, each of the signal emitters 118a-d may be associated with a respective section of the boundary 106. Then, if a user device determines that it has come within a threshold distance of a signal emitter, it may determine that it has crossed a section of the boundary 106 corresponding to that signal emitter. For instance, signal emitter 118a may correspond to the first section 106a of the boundary 106, signal emitter 118b may correspond to the second section 106b of the boundary 106, signal emitter 118c may correspond to the third section 106c of the boundary 106, and signal emitter 118d may correspond to the fourth section 106d of the boundary 106.

Similarly to the discussion above, once one of the user devices 108a-c detects that it has crossed the boundary 106, it may transmit information indicative of the user device crossing the boundary. Also similarly to above, an alert may then be generated.

Proximity-sensor-based detection Another technique for detecting when a user device crosses the boundary 106 involves using proximity sensors around the heavy machinery 162. Thus, in some embodiments, the safety system 100 includes a set of proximity sensors arranged around the heavy machinery 102. In such embodiments, the features in Fig. 1 indicated by reference numerals 118a-d correspond to proximity sensors. For illustration purposes, the proximity sensors of these embodiments, and the signal emitters of the embodiments discussed above are represented by the same set of features in Fig. 1, i.e. the features indicated by reference numerals 118a-d may correspond to proximity sensors or signal emitters, depending on the embodiment under consideration. Of course, in some embodiments, the safety system 100 may include both proximity sensors and signal emitters.

Each proximity sensor is disposed within a respective one of the light sources 104a-d, e.g. in a housing of the light source. However, the proximity sensors 118a-d need not necessarily be disposed in the light sources 104a-d, e.g. they may be disposed next to the light sources 104a-d or at different locations around the heavy machinery 102.

The proximity sensors 118a-d may be any suitable type of proximity sensor for detecting when a user device crosses the boundary 106. The proximity sensors 118a-d may be connected to the controller 110 (e.g. via a wired or wireless connection), so that outputs from the proximity sensors 118a-d can be conveyed to the controller 110. In some examples, the proximity sensors 118a-d may include signal receivers which are configured to receive signals emitted by the user devices 108a-c. Each of the user devices 108a-c may be configured to emit a signal (e.g. a radiofreguency signal) that can be detected by the proximity sensors 118a-d. The signal emitted from each user device may include an identifier for identifying that user device. The user devices 108a-c may be configured to emit the signals continuously, or at regular intervals. In this manner, it is possible to identify which user device crossed the boundary 106 based on the identifiers contained in the emitted signals.

Upon receiving a signal from a user device, a proximity sensor may detect a strength of the received signal. The proximity may provide an output to the controller 110 which is indicative of the received signal strength from the user device. The controller 110 can then determine, based on the strength of the received signal, a distance between the proximity sensor and the user device. Where the signal from the user device is received by multiple ones of the proximity sensors 118a-d, the controller may be able to perform a calculation based on the signal strengths obtained from the different proximity sensors, in order to determine a location of the user device relative to the boundary 106 (e.g. such as a triangulation calculation).

The positions of the proximity sensors 118a-d relative to the boundary 106 are known by the controller 110. In this manner, the controller 110 can determine a distance or position of a user device relative to the proximity sensors 118a-d and thus to the boundary, based on the outputs from the proximity sensors 118a-d. In this manner, the controller 110 can detect when one of the user devices 108a-c crosses the boundary 106. For example, the positions of the proximity sensors 118a-d relative to the boundary 106 may be determined based on known locations of the proximity sensors 118a-d (i.e. in the light sources 104a-d) and parameters (e.g. shape and size) of the boundary 106. Additionally, the controller 110 may include coordinate information for the boundary 106, which may facilitate determining of a position of a user device relative to the boundary 106.

The controller 110 may also be configured to determine which section of the boundary 106 was crossed, based on the outputs from the proximity sensors 118a-d. For example, each of the proximity sensors 118E-d may be associated with a respective section of the boundary 106. Then, if the controller 110 determines that a user device has come within a threshold distance of one of the proximity sensors 118a-d, it may determine that the user device has crossed a section of the boundary 106 corresponding to that proximity sensors. For instance, proximity sensor 118a may correspond to the first section 106a of the boundary 106, proximity sensor 118b may correspond to the second section 106b of the boundary 106, proximity sensor 118c may correspond to the third section 106c of the boundary 106, and proximity sensor 118d may correspond to the fourth section 106d of the boundary 106.

Once the controller 110 detects that one of the user devices 108a-c has crossed the boundary 106, it may store information indicative of the user device crossing the boundary 106, and subsequently transmit such information to the remote server 112. The controller 110 may also determine which user device has crossed the boundary, based on the identifier included in the signal received from the user device. The controller 110 may include the user device's identifier in the information transmitted to the remote server 112.

Although the safety system 100 is described above in the context of monitoring a boundary around heavy machinery 102, it may of course be used in different contexts. For example, instead of heavy machinery 102, the safety system may be used with a vehicle. Of course, the safety system 100 need not necessarily be used with a piece of machinery or a vehicle, and can be used to monitor access to an area of Interest. For example, the boundary 106 may be used to enclose an area on a construction site to which access is to be monitored or restricted.

Although only a single boundary 106 is shown in Fig. 1, the safety system 100 may be configured to monitor multiple boundaries. For example, the safety system 100 may Include multiple light systems, each of which is configured to define a respective boundary on a ground surface. Each of the boundaries may be monitored using any of the techniques mentioned above, so that the safety system 100 can detect when any of the boundaries is crossed by a user device. As an example, a construction site may include several different areas which are potentially hazardous and therefore require monitoring. Accordingly, a boundary may be set up around each of these areas, so that the safety system 100 can detect when a person enters one of these areas.

Fig. 2 shows a schematic side view of a piece of heavy machinery 200 on which a light system is mounted. The light system is part of a safety system according to an embodiment of the invention. In the example shown, the heavy machinery 200 is a digger. Of course, in other examples, other types of heavy machinery or vehicle may be used.

The light system includes a set of light sources 202a-b which are mounted on a roof 203 of the heavy machinery 200. A first light source 202a of the light system is arranged to project a first light beam 264 onto a ground surface 206 around the heavy machinery 200, and a second light source 202b of the light system is arranged to project a second light beam 208 onto the ground surface 206. The first light source 202a is arranged to project the first light beam 204 onto a portion of the ground surface 206 behind the heavy machinery 200, whilst the second light source 202b is arranged to project the second light beam 208 onto a portion of the ground surface 206 in front of the heavy machinery 200. The first and second light beams 204, 208 serve to define respective portions of a boundary on the ground surface 206 around the heavy machinery 200. The light system may include further light sources (not shown in Fig. 2) which are arranged on other sides of the heavy machinery 200, to define further portions of the boundary. In some embodiments, the heavy machinery 200 may correspond to the heavy machinery 102 of Fig. 1, with the first and second light sources 202a-b respectively corresponding to light sources 104d and 104b of Fig. 1.

The first light source 202a is mounted on the roof 203 via a first arm 212, and the second light source 202b is mounted on the roof 203 via a second arm 214. The first and second arms 212, 214 may be movable and/or adjustable, in order to adjust a position and/or angle of the first and second light sources relative to the heavy machinery 200. This may enable the positions at which the first and second light beams 204, 208 are incident on the ground surface 206, so that a position and/or shape of the boundary defined by the light beams can be adjusted. As an example, the first and second arms 212, 214 may include hydraulic arms, articulated arms, or some other adjustable mechanism for movably mounting the light sources 202a-b to the roof 203.

The heavy machinery 200 includes a cockpit 210 in which controls for the heavy machinery 200 may be located. Thus, an operator of the heavy machinery 200 may be located in the cockpit 210 when the heavy machinery 200 is in use. A controller of the safety system (e.g. controller 110 of Fig 1) may be also be located in the cockpit 210, to enable an operator of the heavy machinery 200 to control the light system and/or other aspects of the safety system. The first and second arms 212, 214 may be controllable via the controller, in order to control the boundary defined on the ground surface 206 around the heavy machinery 200. For example, where the first and second arms 212, 214 include hydraulic arms, the controller may be configured to control movement of the hydraulic arms in order to adjust the positions and/or angles of the light sources 202a-b relative to the heavy machinery 200.

Fig. 3 shows a schematic front view of a light source 300 that may be part of a light system in a safety system according to the invention. The light source 300 includes a housing 302 in which a lighting assembly 304 is disposed. The lighting assembly 304 is configured to generate and project a light beam which can be directed at a ground surface in order to define a boundary (or a section thereof) on the ground surface. The lighting assembly 304 may, for example, include a light bulb together with suitable optical components for generating a light beam. The optical components may serve to shape and focus light emitted by the light bulb into a light beam.

Also disposed within the housing 302 of the light source 300 is detection element 306 which enables the safety system to detect when a user device crosses the boundary. The detection element 306 may take different forms, depending on the specific embodiment. In some embodiments, the detection element 306 may be in the form of a signal emitter which is configured to emit a signal that is receivable by the user device. The user device can then determine when it crosses the boundary based on the signal received from the signal emitter. So, the detection element 306 may, for example, correspond to one of the signal emitters 118a-d discussed above in relation to Fig. 1. In other embodiments, the detection element 306 can be in the form of a proximity sensor which is configured to detect a user device. In this manner, the safety system can determine when the user device crosses the boundary based on an output from the proximity sensor. Thus, the detection element 306 may, for example, correspond to one of the proximity sensors 118a-d discussed above in relation to Fig. 1. Of course, the safety system may employ both signal emitters and proximity sensors in order to detect when a user device crosses the boundary. Accordingly, the detection element 306 may include both a signal emitter and a proximity sensor.

Fig. 4 shows an example of a record 400 that may be maintained by a safety system according to an embodiment of the invention. The record 406 includes information relating to instances when a user device crossed a boundary of the safety system. The record 400 may, for example, be maintained by the remote server 112 of the safety system 100, described above. Additionally or alternatively, a similar record may be maintained by the controller 110 of the safety system 100.

The record 400 is in the form of a database (or table) which includes a series of entries, each entry corresponding to a different instance when a user device crossed a boundary. The "date" and "time" columns of record 400 respectively indicate a date and time at which a user device was detected by the safety system to have crossed a boundary. The "duration" column indicates an amount of time that the user device spent across the boundary, i.e. a duration for which the boundary was breached. The "location" column includes an indication of where the boundary was located at the time it was crossed. This may be particularly relevant where the boundary may move over time, e.g. where it is defined around a vehicle or some movable machinery. The location column may, for example, include GPS data obtained for a GPS module in the vehicle or machinery, and/or from user device belonging to an operator of the vehicle or machinery. Where the boundary is static (e.g. where it defines an area in a construction site), the "location" column may include an indication of a site where the boundary is located (such as a name of the site, or a GPS location of the site).

The "vehicle/machinery" column of record 400 indicates, where applicable, which vehicle or piece of machinery the boundary is defined around. So, in the example of Fig. 4, two breaches of a boundary around "Digger 1" were detected, and one breach of a boundary around "Truck 2" were detected. As discussed above, the safety system may be configured to simultaneously monitor multiple different boundaries, e.g. corresponding to different areas or pieces of machinery in a construction site. By identifying the location of the boundary, and which vehicle or machinery it is associated with, it may be possible to reliably determine which boundary was crossed. To further identify which boundary was breached, the record 400 may further include a column indicating an identifier (e.g. an identification code) for each boundary that was breached.

The "section" column indicates which section of the boundary was breached. As discussed above in relation to Fig. 1, a boundary may have multiple sections, and the safety system may be configured to detect which section of the boundary was breached. So, using the example of Fig. 1, the "section" column may indicate which of sections 106a-d was crossed by a user device.

The "user device" column indicates an identifier (e.g. identification code) of the user device that was detected to have crossed the boundary. The "person" column indicates a name of a person associated with the user device that was detected to have crossed the boundary. The "operator" column indicates, where applicable, a name of a person operating the machinery or vehicle when the boundary was crossed. In some cases, a person may identify themselves to the safety system as an operator of a vehicle or machinery prior to beginning operation of vehicle or machinery. For example, the person may use an application on their user device to provide such an indication to the safety system.

Of course, the record maintained by the safety system may take various different forms, and need not be in the form that is illustrated in Fig. 4. In particular, the record need not necessarily be stored in the form of a table, and any suitable type of data structure for recording the desired information can be used. In other embodiments, the record maintained by the safety system need not necessarily include all of the information shown in Fig. 4, or it may include further types of information.

Claims

CLAIMS1. A safety system comprising a light system configured to project a light beam onto a ground surface, thereby defining a boundary on the ground surface, wherein the safety system is configured to detect when a user device crosses the boundary.
2. A safety system according to claim 1, wherein the safety system is further configured to determine an identifier of a user device that crosses the boundary.
3. A safety system according to claim 2, wherein the safety system is configured to, based on the identifier of the user device, determine an identity of a person carrying the user device.
4. A safety system according to any preceding claim, wherein the safety system is further configured to keep a record of instances when a user device crossed the boundary.
5. A safety system according to any preceding claim, wherein the safety system is further configured to generate an alert in response to detecting that a user device has crossed the boundary.
6. A safety system according to any preceding claim, wherein the light system includes a plurality of light sources, each light source being configured to project a respective light beam onto the ground surface, wherein together the respective light beams define the boundary on the ground surface.
7. A safety system according to any preceding claim, wherein the boundary comprises a plurality of sections, and wherein the safety system is further configured to determine which section of the boundary was crossed by the user device.
8. A safety system according to any preceding claim, further comprising the user device, wherein the user device is configured to detect when it crosses the boundary.
9. A safety system according to claim 8, further comprising a remote server, wherein: the user device is communicatively coupled to the remote server; and following detecting that the user device has crossed the boundary, the user device is configured to transmit to the remote server information indicative of the user device crossing the boundary.
10. A safety system according to claim 8 or 9, wherein the user device comprises a GPO module, and wherein the user device is configured to detect when it crosses the boundary based on an output of the GE'S module.
11. A safety system according to one of claims 8 to 10, further comprising a signal emitter, wherein the user device is configured to: receive a signal emitted by the signal emitter; and determine when the user device crosses the boundary based on the signal received from the signal emitter.
12. A safety system according to claim 11, wherein the signal emitter is located within a housing of a light source of the light system.
13. A safety system according to one of claims 8 to 12, comprising a plurality of sicnal emitters, wherein: each of the signal emitters is configured to emit a signal comprising a respective identifier; and the user device is configured to receive the signals emitted by the plurality of signal emitters and determine, based on the received signals, when the user device crosses the boundary and a section of the boundary that was crossed.
14. A safety system according to any preceding claim, further comprising a proximity sensor configured to detect the user device, wherein the safety system is configured to determine when the user device crosses the boundary based on an output from the proximity sensor.
15. A safety system according to claim 14, wherein the proximity sensor is configured to receive a signal emitted from the user device and determine a distance to the user device based on the signal from the user device.
16. A safety system according to claim 14 or 15, wherein the proximity sensor is located within a housing of a light source of the light system.
17. A safety system according to one of claims 14 to 16, comprising a plurality of proximity sensors, wherein: each of the proximity sensors is associated with a respective section of the boundary; and the safety system is configured to determine, based on outputs from the plurality of proximity sensors, when the user device crosses the boundary and which section of the boundary was crossed.
18. A safety system according to any preceding claim, wherein the light system is controllable to adjust the boundary.
19. A safety system according to any preceding claim, further comprising a camera configured to capture an image of the boundary.
20. Heavy machinery comprising a safety system according to any preceding claim, wherein the light system is mounted on the heavy machinery and arranged to define a boundary on the ground surface around the heavy machinery.
21. Heavy machinery according to claim 20, wherein the safety system comprises a user interface disposed in a cockpit of the heavy machinery.
22. A method comprising: projecting, with a light system, a light beam onto a ground surface to define a boundary on the ground surface; and detecting when a user device crosses the boundary.
23. A method according to claim 22, further comprising determining an identifier of a user device that crosses the boundary.
24. A method according to claim 23, further comprising determining an identity of a person carrying the user device, based on the identifier of the user device.
25. A method according to one of claims 22 to 24, further comprising keeping a record of instances where a user device crossed the boundary.