WO2020142801A1

WO2020142801A1 - A civil construction site control system and method of use

Info

Publication number: WO2020142801A1
Application number: PCT/AU2019/051415
Authority: WO
Inventors: Aaron Krenske
Original assignee: Position Partners Pty Ltd
Current assignee: Position Partners Pty Ltd
Priority date: 2019-01-10
Filing date: 2019-12-19
Publication date: 2020-07-16
Anticipated expiration: 2021-07-10
Also published as: AU2019421123A1; JP2022518193A; JP7495413B2; AU2019421123B2

Abstract

The invention concerns a system and method for the automatic control of the dissemination of project file data and real time kinematic (RTK) correction on a civil construction site, which includes: at least one virtual boundary partially defining the civil construction site; at least one rover device having a global navigation satellite system (GNSS) antenna and at least one modem; and at least one remotely accessible server for providing the RTK correction data and the project file data for the civil construction site to the rover device and for determining a position of the rover device relative to the virtual boundary. The RTK correction data and the project file data is transmitted to the rover device when it enters the at least one virtual boundary and at least the project file data is removed from the one rover device when the rover device exits the at least one virtual boundary.

Description

A CIVIL CONSTRUCTION SITE CONTROL SYSTEM AND METHOD OF USE TECHNICAL FIELD

[0001] The present invention relates to a system and method for the control of at least project file data on a civil construction site.

BACKGROUND

[0002] Most civil construction sites utilise precise positional data derived from satellite- based positioning systems for the collection of survey data and to guide the operation of earth working equipment, such as, e.g., excavators, dozers and motor graders, on site. Such civil construction sites also utilise hand held, pole-mounted satellite positioning systems for the inspection of work and for quality assurance purposes.

[0003] Such systems, whether vehicle mounted or hand held, usually further use real-time kinematic (RTK) positioning systems to enhance the positional data derived from global navigation satellite systems (GNSS) such as, e.g., GPS, GLONASS, Galileo and BeiDou. RTK positioning systems generally measure the phase of a GNSS signal’s carrier wave together with other information content of the signal and rely on one or more fixed base stations to provide real-time corrections (RTK corrections) and up to centimetre-level accuracy. Depending on the set up, the RTK corrections can be broadcast from a single fixed base station on site or via a network of RTK base stations, known as a Continuously Operating Reference Station (CORS) network.

[0004] In modern construction sites, the RTK corrections are broadcast to mobile units, known as rovers, operably associated with personnel and earth working equipment on site. Each rover device typically includes an antenna for receiving the GNSS-derived positional data and a modem for receiving the broadcast RTK corrections and applying them against the GNSS- derived positional data for enhanced positional information.

[0005] However, a problem with such systems is that the process of onboarding new rover devices when they arrive on site is time consuming and arduous, typically requiring configuration of the modem of the rover device so that it may receive RTK corrections and project file data for the site. The configuration process usually involves manually inputting correct server addresses/ports and login details on each individual rover device.

[0006] Another problem with such systems is the risk of misconfiguring rover devices through the inadvertent input of incorrect project file data for a site and/or a failure to receive RTK corrections, and the subsequent problems caused by those misconfigured rover devices on site. Such problems are unfortunately not uncommon and can add irrecoverable costs to a project when not picked up early on.

[0007] Yet further problems arise from the use of such systems on large project sites, wherein multiple project files may exist for different sub-areas of a site. In such scenarios, a failure to accurately monitor the internal movements of rover devices within the project site may result in inaccuracies and irrecoverable costs again incurred by misconfigured rover devices.

SUMMARY OF INVENTION

[0008] Embodiments of the present invention provide a system and a method for the control of at least project file data on a civil construction site, which may at least partially overcome at least one of the abovementioned problems or provide the consumer with a useful or commercial choice.

[0009] According to a first aspect of the present invention, there is provided a civil construction site control system including:

at least one virtual boundary at least partially defining a civil construction site;

at least one rover device, said rover device including at least one global navigation satellite system (GNSS) antenna and at least one modem; and

at least one remotely accessible server for providing real time kinematic (RTK) correction data and project file data for the civil construction site to the at least one rover device and for determining a position of the at least one rover device relative to the at least one virtual boundary,

wherein the RTK correction data and the project file data is transmitted to the at least one rover device when the rover device enters the at least one virtual boundary and the RTK correction data and the project file data is removed from the at least one rover device when the rover device exits the at least one virtual boundary.

[0010] According to a second aspect of the present invention, there is provided a civil construction site control system including:

at least one rover device operatively associated with an operator or vehicle, said rover device having at least one GNSS antenna and at least one modem;

at least one remotely accessible server in communication with the at least one modem for providing RTK correction data and project file data to the rover device and for determining a position of the rover device relative to the at least one virtual boundary; and

a display device operatively connected to the at least one rover device for interfacing with the at least one GNSS antenna and the at least one modem and displaying the project file data,

wherein the RTK correction data and the project file data is transmitted to the at least one rover device via the at least one modem when the rover device enters the at least one virtual boundary and the RTK correction data and the project file data is removed from the at least one rover device when the rover device exits the at least one virtual boundary.

[0011] Advantageously, the system and method of the present invention provide a means for automatically controlling access to civil construction site specific data thereby removing the arduous and time-consuming task of manually onboarding a rover device. Moreover, by removing the need to manually onboard a rover device, the risk of misconfiguring a rover device and the downstream problems a misconfigured rover device presents are at least reduced if not obviated. Lastly, the automatic interaction between the at least one virtual boundary, the at least one rover device and the at least one remotely accessible server provides a means for more accurately monitoring the internal movements of a rover device on a large civil construction site.

[0012] As indicated above, the system is for use on civil construction sites for controlling rover device access to RTK correction data and project file data. A person skilled in the art, however, will appreciate that the system may ultimately be used on other sites where access control of data is desired.

[0013] As used herein, the term“civil construction site” may include any construction site where civil structures are being constructed and/or maintained, such as, e.g., roads, bridges, canals, dams, airports, sewerage systems, pipelines, railways, transportation embankments, levees and building foundations.

[0014] As used herein, the term“project file data” may include any data relevant to the construction of the civil structure or structures on the site. For example, the project file data may include 3D designs, radio settings, server logins and/or IP address job files.

[0015] The at least one virtual boundary may be of any suitable size, shape and form for at least partially defining the civil construction site.

[0016] Typically, the at least one virtual boundary may define a geographical perimeter around or partly around the civil construction site.

[0017] In some embodiments, however, the civil construction site may include more than one virtual boundary. For example, large construction sites may include at least two, at least three, at least four, at least five, at least six, at least seven, at least eight, at least nine or even at least 10 virtual boundaries each defining a sub-area of the site. [0018] Generally, the boundary may include a geo-fence utilising a GNSS or radio frequency identification (RFID) to define a geographical boundary around the civil construction site, preferably GNSS, more preferably GPS.

[0019] The at least one virtual boundary may typically be set by a project manager or the like. Generally, the project manager or the like may use mapping software to define the boundary on top of a satellite view of the site. The boundary may be adjustable.

[0020] The geo-fence may be an active or passive geo-fence.

[0021] The at least one virtual boundary is preferably hosted by the at least one remotely accessible server.

[0022] As indicated, the system includes at least one rover device having at least one GNSS antenna and at least one modem. The rover device may be sized and shaped to be mobile and be operably associated with an operator or vehicle on site. The rover device may be operably associated in any suitable way.

[0023] For example, if operably associated with an operator, the rover device may be sized and shaped to be carried by the operator, such as, e.g., in a pocket or backpack, or on a pole carried by the operator.

[0024] If operably associated with a vehicle, the rover device may be sized and shaped to be mounted to the vehicle. The rover device may be directly or indirectly mounted to the vehicle. For example, in some such embodiments, the rover device may be mounted on a pole mounted to the vehicle. In other such embodiments, the rover device may be mounted to or near a cutting edge of the vehicle. The vehicle may preferably be earth working equipment, such as, e.g., a dozer, a grader, an excavator or the like.

[0025] The GNSS system or antenna may be configured to receive radio waves from artificial satellites for determining positional coordinates of the rover device, preferably GNSS satellites, more preferably at least four GNSS satellites.

[0026] Typically, the rover device may further include a GNSS receiver associated with at least one GNSS antenna for receiving output from the antenna.

[0027] The at least one modem may be configured to be in communication with the at least one remotely accessible server for the transmission of data between the at least one modem and the server. In some embodiments, the at least one modem may be a cellular modem. In other embodiments, the at least one modem may be a radio modem. [0028] The data may include data corresponding to positional information and/or identification information of the rover device. The data may also include RTK correction data and project file data from the server. The server may be in communication with a source of RTK correction data, such as, e.g., a single fixed base station on site or via a network of RTK base stations, known as a Continuously Operating Reference Station (CORS) network, typically the latter.

[0029] Generally, the rover device may further include a controller for controlling operation of the at least one GNSS antenna and the at least one modem. The controller may be operatively connected to the at least one GNSS antenna and the at least one modem and any other electric components of the rover device.

[0030] The rover device may also include at least one display for interfacing the controller and enabling a user to interact with the rover device.

[0031] In some embodiments, the controller may be associated with the at least one display. For example, the controller and/or the at least one display may include a touchscreen to allow a user to interact with the rover device and control various aspects of functionality of the rover device.

[0032] In other embodiments, the rover device may include a keypad or touchpad including one or more keys or buttons for controlling various aspects of functionality of the rover device.

[0033] In some embodiments, the controller and/or the at least one display may be part of an external computing device, such as, e.g., a computer, a tablet, a smart phone, a smart watch or a PDA). The external computing device may be connected to the rover device by a wired connection or a wireless connection via a wireless network (e.g., Wi-Fi (WLAN) communication, RF communication, infrared communication, or Bluetooth™), preferably the latter.

[0034] In preferred embodiments, the controller and/or the at least one display may be of integral construction with the rover device. Typically, in such embodiments, the controller may be in the form of a microcomputer including one or more processors and a memory. The processors may preferably be low power processors. The processors may have multiple inputs and outputs coupled to other electronic components of the rover device.

[0035] For example, the processors may have at least one input coupled to the GNSS receiver associated with the at least one GNSS antenna for receiving satellite positional information. The processors may likewise have at least one output coupled to the at least one modem for transmitting the satellite positional information to the at least one remotely accessible server. Further, the processors may have at least one input coupled to the at least one modem for receiving the RTK correction data from the at least one remotely accessible server and for applying the correction data against the satellite positional information to obtain corrected positional information.

[0036] The rover device may further include a power source for powering the electrical components of the rover device.

[0037] In some embodiments, the power source may include an on-board power source, such as, e.g., one or more batteries or capacitors.

[0038] In other embodiments, the power source may include a photovoltaic solar panel, an inverter and one or more batteries for storing electricity generated and from which the rover device may draw power.

[0039] In some embodiments, the rover device may be addressable and may report its location to the at least one remotely accessible server when polled, for example.

[0040] The at least one remotely accessible server may be any appropriate server computer, distributed server computer, cloud-based server computer, server computer cluster or the like. The server may typically include one or more processors and one or more memory units containing executable instructions/software to be executed by the one or more processors.

[0041] As indicated above, the server may generally be in communication with a source of RTK correction data, such as, e.g., a single fixed base station on site or via a network of RTK base stations, known as a Continuously Operating Reference Station (CORS) network, typically the latter.

[0042] The server may also be in communication with a source of the project file data, typically a computing device controlled by a project manager or the like of the civil construction site. The computing device may include at least one processor, at least one memory unit and at least one display. The computing device may be in the form of a desktop computer, a laptop computer, a tablet device, a smart phone, a smart watch or a PDA, for example.

[0043] The remotely accessible server is configured to transmit communications to and receive communications from the at least one rover device and/or a computing device of the project manager or the like over any suitable communications network or networks.

[0044] The communications may be received and transmitted over a communications network, which may include, among others, the Internet, LANs, WANs, GPRS network, a mobile communications network, a radio network (UHF-band), etc., and may include wired and/or wireless communication links, preferably the latter.

[0045] The communications may preferably be received and transmitted via a private network connection established between the rover device and the remotely accessible server and/or between the computing device controlled by the project manager or the like and the remotely accessible server.

[0046] For example, in some embodiments, the private network connection may be a secure communication session across an encrypted communication channel such as Hypertext Transfer Protocol Secure (HTTPS), Transport Layer Security / Secure Sockets Layer (TLS/SSL) or some other secure channel.

[0047] In preferred embodiments, however, the private network connection may be a VPN connection established using an encrypted layered tunnelling protocol and authentication methods, including identifiers, passwords and/or certificates.

[0048] For example, in some embodiments, the at least one rover device may be assigned a unique identifier that may also be registered with the at least one server. In use, the server may establish a VPN connection with the rover device upon authenticating the identifier assigned to the rover device.

[0049] In such embodiments, the server may be in communication with at least one database containing a plurality of identifiers. The identifiers may be rover device identifiers. The server may look-up an identifier in the database to authenticate a rover device. Preferably, the server may be linked to or may maintain the database containing the plurality of identifiers.

[0050] In some embodiments, the server may monitor the communications network for connection requests from the at least one rover device. Upon receiving a request, the server may determine a location of the rover device relative to the at least one virtual boundary and/or authenticate an identity of the rover device. Typically, the server may determine the location of the rover device relative to the at least one virtual boundary based on positional information provided by the rover device together with the connection request.

[0051] In other embodiments, the at least one rover device may broadcast positional information and/or identification information to the at least one remotely accessible server. The information may be broadcast when polled or according to a schedule, typically the latter.

[0052] The rover device may preferably be configured to broadcast the information according to a predetermined schedule. For example, the rover device may broadcast the information at about 1 minute intervals, about 2 minute intervals, about 3 minute intervals, about 4 minute intervals, about 5 minute intervals, about 6 minute intervals, about 7 minute intervals, about 8 minute intervals, about 9 minute intervals, about 10 minute intervals, about 15 minute intervals, about 20 minute intervals, about 25 minute intervals, about 30 minute intervals, about 35 minute intervals, about 40 minute intervals, about 45 minute intervals, about 50 minute intervals, about 55 minute intervals, or even at about 60 minute intervals or more.

[0053] Responsive to the rover device being located within the boundary and its identity being authenticated, the server may establish a secure connection with the rover device and transmit RTK correction data and the project file data to the rover device, preferably a VPN connection. Typically, the server may determine whether the rover device is within the boundary based on the positional information provided by the rover device.

[0054] Responsive to the rover device being located outside of the boundary and its identity being authenticated, the server may delete the project file data from the rover device, if present. In such embodiments, the server may establish a secure connection with the rover device and address a memory unit of the rover device to determine whether it contains project file data specific for the civil construction site, again preferably a VPN connection. Responsive to the memory unit of the rover device containing the project file data, the server may delete the data from the memory unit.

[0055] In some embodiments, the server may maintain a most current version of the project file data. Accordingly, the server may overwrite a server version of the project file data with a rover device version of the project file data in response to determining that the rover device version is the most current version of the project file data. In some such embodiments, the server may copy the rover device version to the server and determine whether the rover device version is the most current version prior to overwriting the server version. In other such embodiments, the server may determine whether the rover device version is the most current version prior to copying the rover device version to the server. Once copied, the rover device version may be deleted.

[0056] Responsive to the identity of the rover device being unable to be authenticated, the server may not establish a secure connection with the rover device. The server may instead transmit an alert notification to a computing device of the project manager or the like advising of the unidentified rover device.

[0057] The alert notification may be an electronic notification and may be effected by way of Short Message Service (SMS) protocol, Unstructured Supplementary Service Data (USSD) protocol, over a secure Internet connection, or by way of data communication enabled by a software application installed on the computing device.

[0058] Additionally and in some embodiments, the server may further block connection requests from the at least one rover device unable to be authenticated.

[0059] In some embodiments, the system may include software configured to be run on the rover device, the remotely accessible server and/or the computing device of the project manager or the like. The software may preferably be interactive. In some embodiments, the software may be in the form of an application (i.e., an app) configured to be run on a smart phone or mobile device, for example.

[0060] In other embodiments, the remotely accessible server may include a web server providing a graphical user interface through which the project manager or the like may interact with the system and the remotely accessible server. The web server may accept requests, such as HTTP requests and serve responses, such as HTTP responses, along with optional data content, such as web pages (e.g., HTML documents) and linked objects. Generally, the web server may enable the project manager and the like to receive and transmit communications with the remotely accessible server and with rover devices via the remotely accessible server.

[0061] In some embodiments, the at least one remotely accessible server may include more than one server. For example, the at least one remotely accessible server may include: a connection server for establishing a network connection with the at least one rover device; a file server responsible for maintaining a database of the project file data, said file server being in communication with the connection server; a map server at least responsible for hosting the at least one virtual boundary, said map server being in communication with the connection server; and a CORS server responsible for maintaining a database of the RTK corrections, said CORS server being in communication with the connection server.

[0062] In some such embodiments, the file server, the map server and/or the CORS server may only communicate with the at least one rover device via the connection server.

[0063] In other such embodiments, the file server, the map server and/or the CORS server may directly communicate with the at least one rover device once the connection server has authenticated the identity of the at least one rover device.

[0064] Generally, however, the computing device of the project manager or the like may communicate directly with the file server and/or the map server (e.g., to amend the virtual boundary and/or the project file data).

[0065] According to a third aspect of the present invention, there is provided a method of controlling project file data on a civil construction site, said method including:

establishing at least one virtual boundary at least partially defining the civil construction site;

monitoring a position of at least one rover device relative to the at least one virtual boundary, said rover device including at least one GNSS antenna and at least one modem;

responsive to the at least one rover device entering the at least one virtual boundary, transmitting RTK correction data and project file data from at least one remotely accessible server to the at least one rover device; and

responsive to the at least one rover device exiting the at least one virtual boundary, removing at least the project file data from the at least one rover device.

[0066] The method may include one or more characteristics or features of the system as hereinbefore described.

[0067] The establishing may typically include establishing a geo-fence utilising a GNSS or radio frequency identification (RFID) to define a geographical boundary around a perimeter of the civil construction site or a part thereof, preferably GNSS, more preferably GPS.

[0068] The establishing may generally be carried out by a project manager or the like using mapping software to define the boundary on top of a satellite view of the construction site. The boundary may preferably be adjustable.

[0069] In some embodiments, the establishing may include establishing more than one virtual boundary for the civil construction site. For example, the establishing may include establishing at least two, at least three, at least four, at least five, at least six, at least seven, at least eight, at least nine or even at least 10 virtual boundaries for the construction site, each at least partially defining a sub-area of the site.

[0070] The monitoring of the position of the at least one rover device may generally be undertaken by the at least one remotely accessible server. The server may also host the at least one virtual boundary.

[0071] In some embodiments, the rover device may be addressable and may report its location to the at least one remotely accessible server when polled, for example. In such embodiments, the server may address the at least one rover device according to a predetermined schedule to monitor the rover device’s location relative to the at least one virtual boundary.

[0072] In other embodiments, the at least one remotely accessible server may monitor a communications network for connection requests from the at least one rover device. Upon receiving a request, the server may determine a location of the rover device relative to the at least one virtual boundary and/or authenticate an identity of the rover device. Typically, the server may determine the location of the rover device relative to the at least one virtual boundary based on positional information provided by the rover device together with the connection request.

[0073] In yet other embodiments, the at least one rover device may broadcast positional information and/or identification information to the at least one remotely accessible server. The information may be broadcast according to a predetermined schedule. In such embodiments, the server may determine the position of the rover device relative to the boundary based on the positional information broadcast by the rover device.

[0074] Said responsive steps may preferably further include a step of authenticating an identity of the at least one rover device prior to the transmission or deletion of the RTK correction data and the project file data. Said responsive steps may also preferably be automatically carried out by the at least one remotely accessible server.

[0075] In some embodiments, the identity of the at least one rover device may be authenticated through the use of a private network connection between the at least one remotely accessible server and the rover device and authentication methods, including identifiers, passwords and/or certificates.

[0076] For example, in some such embodiments, the at least one rover device may have earlier been assigned a unique identifier that may also be registered with the at least one server. In use, the server may establish a secure connection with the rover device upon authenticating the identifier assigned to the rover device, preferably a VPN connection.

[0077] Responsive to the position of the rover device being determined to be within the boundary (i.e. , entering) and its identity being authenticated, the server may establish a secure connection with the rover device and transmit RTK correction data and the project file data to the rover device, again preferably a VPN connection.

[0078] Responsive to the rover device being located outside of the boundary (i.e., exiting) and its identity being authenticated, the server may delete the project file data from the rover device, if present. In such embodiments, the server may establish a secure connection with the rover device and address a memory unit of the rover device to determine whether it contains project file data specific for the civil construction site, preferably a VPN connection. Responsive to the memory unit of the rover device containing the project file data, the server may delete the data from the memory unit. In some embodiments, the server may also delete the RTK correction data.

[0079] In some embodiments, the server may compare a rover device version of the project file data with a server version of the project file data prior to deleting the rover device version. In such embodiments, if the rover device version is the most current version of the project file data, the server may overwrite the server version with the rover device version.

[0080] Responsive to the identity of the rover device not being authenticated, the server may not establish a connection with the rover device. The server may instead transmit an alert notification to a computing device of the project manager or the like advising of the unidentified rover device.

[0081] Any of the features described herein can be combined in any combination with any one or more of the other features described herein within the scope of the invention.

[0082] The reference to any prior art in this specification is not, and should not be taken as an acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.

BRIEF DESCRIPTION OF DRAWINGS

[0083] Preferred features, embodiments and variations of the invention may be discerned from the following Detailed Description which provides sufficient information for those skilled in the art to perform the invention. The Detailed Description is not to be regarded as limiting the scope of the preceding Summary of Invention in any way. The Detailed Description will make reference to a number of drawings as follows:

[0084] Figure 1 is an illustration of a civil construction site control system according to an embodiment of the present invention;

[0085] Figure 2 is a schematic showing use of the system as shown in Figure 1 ;

[0086] Figure 3 is another schematic showing use of the system as shown in Figure 1 ;

[0087] Figure 4 is yet another schematic showing use of the system as shown in Figure 1 ; and

[0088] Figure 5 is a flowchart showing steps in a method of the system shown in Figure 1. DETAILED DESCRIPTION

[0089] Figure 1 shows a civil construction site control system (100) according to an embodiment of the present invention for controlling the distribution of project data files on a civil construction site (900).

[0090] The system (100) includes: a geo-fence (120; at least one virtual boundary) defining a perimeter or boundary of the civil construction site (900); a GPS rover (130; i.e., rover device) operably associated with earth working equipment (800), the GPS rover (130) including a GPS antenna (132) and a cellular modem (134); and at least one remotely accessible server (140) for providing real time kinematic (RTK) correction data and project file data for the civil construction site (900) to the GPS rover (130) and for determining a position of the GPS rover (130) relative to the geo-fence (120). In use, the server (140) transmits the RTK correction data and the project file data to the GPS rover (130) when it enters the geo-fenced area and its identity has been authenticated. Conversely, when the GPS rover (130) exits the geo-fenced area, the server (140) deletes the RTK correction data and the project file data from the GPS rover (130).

[0091] Referring to Figure 1 , the geo-fence (120) utilises GPS to define a geographical boundary around the construction site (900).

[0092] The geo-fence (120) is hosted by the server (140) and is set by a project manager (600) using mapping software on a computing device (700) in communication with the server (140). Generally, the mapping software may enable the project manager (600) to define the geo-fence (120) atop a satellite view of the civil construction site (900). The geo-fence (120) is adjustable. In some embodiments, the geo-fence (120) may be adjusted by entering or uploading co-ordinates to determine a centre and outside boundary of the civil construction site (900).

[0093] As indicated, the GPS rover (130) has a GPS antenna (132) and a cellular modem (134) and is sized and shaped to be mobile and be operably associated with the earth working equipment (800). The rover (130) can be operably associated with the earth working equipment (800) in any suitable way.

[0094] For example, in some embodiments, the GPS rover (130) can be mounted on a pole mounted to the earth working equipment (800). In other embodiments, the GPS rover (130) can be directly mounted to the earth working equipment (800).

[0095] The GPS antenna (132) is configured to receive radio waves from GPS satellites (1000) for determining positional coordinates of the rover (130). The GPS antenna (132) is associated with a GPS receiver.

[0096] The cellular modem (134) is configured to be in communication with the at least one remotely accessible server (140) for the transmission of data between the cellular modem (134) and the server (140).

[0097] The data includes data corresponding to positional information and/or identification information of the rover (130) as well as the RTK correction data and project file data from the server (140). The server (140) is in communication with a source of RTK correction data in the form of a network of RTK base stations, known as a Continuously Operating Reference Station (CORS) network.

[0098] The rover (130) furthers include a controller in the form of a microcomputer for controlling operation of the GPS antenna (132) and the cellular modem (134). The controller is integrally formed with the rover (130) and operatively connected to GPS antenna (132) and cellular modem (134) and other electric components of the rover (130).

[0099] The rover (130) includes a display (136) for interfacing the controller and enabling a user to interact with the rover (130).

[00100] The rover (130) is addressable and reports its location to the server (140) when polled.

[00101] The server (140) includes one or more processors and one or more memory units containing executable instructions/software to be executed by the one or more processors.

[00102] As indicated above, the server (140) is in communication with the Continuously Operating Reference Station (CORS) network for providing the RTK correction data.

[00103] The server (140) is also in communication with a source of the project file data, typically a database associated with the server (140). The database is accessible to the computing device (700) controlled by the project manager (600) so that the project file data may be amended as needed.

[00104] The server (140) is configured to transmit communications to and receive communications from the GPS rover (130) and/or the computing device (700) of the project manager (600) over a communications network, which may include, among others, the Internet, LANs, WANs, GPRS network, a mobile communications network, a radio network (UHF-band), etc. [00105] The communications are received and transmitted via a private network connection established between the rover (130) and the server (140) and/or between the computing device (700) controlled by the project manager (600) and the server (140).

[00106] Generally, the private network connection is a secure connection, such as, e.g., a VPN connection established using an encrypted layered tunnelling protocol and authentication methods, including identifiers, passwords and/or certificates.

[00107] The GPS rover (130) is assigned a unique identifier that is also registered with the server (140). In use, the server (140) establishes a VPN connection with the rover (130) upon authenticating the identifier assigned to the rover (130).

[00108] The server (140) determines the location of the rover (130) relative to the geo-fence (120) based on positional and/or identification information broadcast by the rover (130). The information is broadcast according to a predetermined schedule.

[00109] Figures 2 to 4 show various scenarios of use of the system (100).

[00110] In the scenarios, there is provided a first construction site (900A) having a first geo fence (120A) located adjacent a second construction site (900B) having a second geo-fence (120B).

[0011 1] Furthermore, in the scenarios there is provided a connection server (140A) for establishing a VPN connection with an authenticated GPS rover (130A, 130B, 130C); a file server (140B) for maintaining a database of the project file data specific for the first and second construction site (900A, 900B); a map server (140C) responsible for hosting the first and second geo-fences (120A, 120B); and a CORS server (140D) responsible for maintaining the specific RTK corrections.

[00112] The file server (140B), the map server (140C) and the CORS server (140D) communicate with an authenticated rover (130) via the connection server (140A).

[00113] The file server (140B) and the map server (140C) are directly accessible to the computing device (700) controlled by the project manager (600) so that the project file data and geo-fences (120A, 120B) may be amended as needed.

[00114] Referring to Figure 2, this figure show GPS rovers (130A) associated with earth working equipment (800A) in the first construction site (900A).

[00115] The GPS rovers (130A) broadcast their location and their identifiers to the connection server (140A), which determines the rovers’ (130A) locations relative to the geo fence (120A). Responsive to the server (140A) determining that the rovers (130A) are within the geo-fenced area and authenticating the identifiers assigned to the rovers (130A), the connection server (140A) establishes a VPN connection with the rovers (130A).

[00116] Upon establishing the VPN connection with the rovers (130A), the CORS server (140D) and the file server (140B) respectively transmit the RTK correction data and the project file data to the rovers (130A) via the connection server (140A).

[00117] Referring to Figure 3, this figure shows a rover (130B) associated with earth working equipment (800B) that has moved from the first construction site (900A) and a first geo-fence (120A) to the second construction site (900B) and a second geo-fence (120B).

[00118] Like in Figure 2, the GPS rover (130B) broadcasts its location and identity to the connection server (140A). The connection server (140A) authenticates the identifier assigned to the rover (130B) and determines its location relative to the first and second geo-fences (120A, 120B).

[00119] Responsive to the connection server (140A) determining that the rover (130B) has left the first geo-fence (120A) and is now within the second geo-fence (120B), the connection sever (140A) establishes a VPN connection with the rover (130B) and addresses a memory unit of the rover (130B) to determine whether it contains RTK correction data and project file data specific for the first construction site (900A). Responsive to the memory unit of the rover (130B) containing the specific RTK correction data and project file data, the server (140A) deletes the data from the memory unit.

[00120] Contemporaneously, the CORS server (140D) and the file server (140B) respectively transmit RTK correction data and project file data specific for the second construction site (900B) to the rover (130B) via the connection server (140A).

[00121] Referring to Figure 4, this figure shows a rover (130C) associated with earth working equipment (800C) that has exited the second construction site (900B).

[00122] Like in Figures 2 and 3, the GPS rover (130C) broadcasts its location and identity to the connection server (140A). The connection server (140A) authenticates the identifier assigned to the rover (130C) and determines its location relative to the second geo-fence (120B).

[00123] Responsive to the connection server (140A) determining that the rover (130C) is not within the second geo-fence (120B), the connection sever (140A) establishes a VPN connection with the rover (130C) and addresses a memory unit of the rover (130C) to determine whether it contains RTK correction data and project file data specific for the second construction site (900B). Responsive to the memory unit of the rover (130C) containing the specific RTK correction data and project file data, the server (140A) deletes the data from the memory unit.

[00124] A method (500) of using the system (100) as shown in Figure 1 is now described in detail with reference to Figure 5.

[00125] At step 510, a project manager (600) establishes an adjustable geo-fence (120) around a construction site (900) using software on a computing device (700) to define a boundary on top of a satellite view of the construction site (900). The geo-fence (120) is hosted by a remotely accessible server (140).

[00126] At step 520, the position of a GPS rover (130) having a GPS antenna (132) and a cellular modem (134) relative to the geo-fence (120) is monitored by a remotely accessible server (140). The server (140) monitors the position of the rover (130) relative to the geo-fence (120) based on the positional information broadcast by the rover (130).

[00127] At step 530, responsive to the server (140) determining that the rover (130) has entered the geo-fenced construction site (900) and authenticating an identity of the rover (130), the server (140) establishes a VPN connection with the rover (130) and automatically transmits RTK correction data and project file data specific for the construction site (900) to the rover (130) thus configuring the rover (130) for use on the construction site (900).

[00128] At step 540, responsive to the server (140) determining that the rover (130) has exited the geo-fenced construction site (900), the server (140) establishes a VPN connection with the rover (130) and automatically deletes the RTK correction data and project file data specific for the construction site (900) from the rover (130).

[00129] In the present specification and claims (if any), the word ‘comprising’ and its derivatives including‘comprises’ and‘comprise’ include each of the stated integers but does not exclude the inclusion of one or more further integers.

[00130] Reference throughout this specification to ‘one embodiment’ or ‘an embodiment’ means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearance of the phrases ‘in one embodiment’ or ‘in an embodiment’ in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more combinations. [00131] In compliance with the statute, the invention has been described in language more or less specific to structural or methodical features. It is to be understood that the invention is not limited to specific features shown or described since the means herein described comprises preferred forms of putting the invention into effect. The invention is, therefore, claimed in any of its forms or modifications within the proper scope of the appended claims (if any) appropriately interpreted by those skilled in the art.

Claims

1. A civil construction site control system including:

at least one remotely accessible server for providing real time kinematic (RTK) correction data and project file data for the civil construction site to the at least one rover device and for determining a position of the at least one rover device relative to the at least one virtual boundary, wherein the RTK correction data and the project file data is transmitted to the at least one rover device when the rover device enters the at least one virtual boundary and the RTK correction data and the project file data is removed from the at least one rover device when the rover device exits the at least one virtual boundary.

2. The system of claim 1 , wherein the at least one virtual boundary defines a geographical perimeter around or partly around the civil construction site.

3. The system of claim 2, wherein the at least one virtual boundary includes a geo-fence utilising a GNSS or radio frequency identification (RFID) to define the geographical perimeter.

4. The system of any one of claims 1 to 3, wherein the at least one virtual boundary is hosted by the at least one remotely accessible server.

5. The system of any one of claims 1 to 4, wherein the at least one rover device is operably associated with an operator.

6. The system of any one of claims 1 to 4, wherein the at least one rover device is operably associated with a vehicle.

7. The system of claim 6, wherein the at least one rover device is mounted on a pole mounted to the vehicle.

8. The system of claim 6, wherein the vehicle is earth working equipment and the at least one rover device is mounted to or near a cutting edge of the vehicle.

9. The system of any one of claims 1 to 8, wherein the at least one modem of the at least one rover is configured to be in communication with the at least one remotely accessible server for transmission of data between the at least one modem and the server.

10. The system of claim 9, wherein the data includes any one of the position of the at least one rover device relative to the at least one virtual boundary, identification information for the at least one rover device, the RTK correction data and the project file data.

11. The system of any one of claims 1 to 10, wherein the at least one remotely accessible server is in communication with a source of RTK correction data.

12. The system of claim 11 , wherein the source is selected from a single fixed base station on site or a network of RTK base stations.

13. The system of any one of claims 1 to 12, further including a display device operatively connected to the at least one rover device for interfacing with the at least one GNSS antenna and the at least one modem of the at least one rover device and displaying the project file data.

14. The system of any one of claims 1 to 13, wherein the at least one remotely accessible server is in communication with a source of the project file data.

15. The system of claim 14, wherein the source is a computing device controlled by a project manager or the like of the civil construction site.

16. The system of claim 14 or claim 15, wherein the at least one remotely accessible server is configured to transmit communications to and receive communications from the at least one rover device and the source of the project file data and wherein the communications are received and transmitted over a communications network.

17. The system of claim 16, wherein the communications are received and transmitted via a private network connection established between the at least one rover device and the at least one remotely accessible server and between the source of the project file data and the at least one remotely accessible server.

18. The system of any one of claims 1 to 17, wherein the at least one remotely accessible server is in communication with at least one database containing a plurality of rover identifiers and wherein the server looks-up a rover identifier in the database to authenticate the at least one rover device.

19. The system of any one claims 1 to 18, wherein the at least one remotely accessible server monitors the communication network for connection requests from the at least one rover device and responsive to receiving a request the sever determines the location of the at least one rover device relative to the at least one virtual boundary and authenticates an identity of the at least one rover device.

20. The system of claim 19, wherein the at least one remotely accessible server determines the location of the at least one rover device based on positional information provided by the at least one rover device together with the connection request.

21. The system of claim 20, wherein the at least one rover device broadcasts positional information and identification information to the at least one remotely accessible server.

22. The system of claim 21 , wherein the positional information and identification information is broadcast when polled.

23. The system of claim 21 , wherein the positional information and identification information is broadcast according to a predetermined schedule.

24. The system of any one of claims 1 to 23, wherein responsive to the at least one rover device being located with the boundary and its identity authenticated, the at least one remotely accessible server establishes a secure connection to the at least one rover device and transmits at least the RTK correction data and the project file data to the at least one rover device.

25. The system of any one of claims 1 to 24, wherein responsive to the at least one rover device being located outside the boundary and its identity being authenticated, the at least one remotely accessible server deletes the project file data from the at least one rover device.

26. The system of claim 25, wherein the at least one remotely accessible server establishes a secure connection to at least one rover device and addresses a memory unit of the at least one rover device to determine whether the device container project file data specific for the civil construction site.

27. The system of any one of claims 1 to 26, wherein the at least one remotely accessible server maintains a current version of the project file data.

28. The system of any one of claims 1 to 27, wherein responsive to the identity of the at least one rover device being unable to be authenticated, the at least one remotely accessible server will not establish a secure connection with the at least one rover device.

29. The system of claim 28, wherein the at least one remotely accessible server transmits an alert notification to a computing device of the project manager or the like of the civil construction site advising of an unidentified said at least one rover device.

30. The system of any one of claims 1 to 29, wherein the at least one remotely accessible server includes a connection server for establishing a network connection with the at least one rover device; a file server responsible for maintaining a database of the project file data, said file server being in communication with the connection server; a map server at least responsible for hosting the at least one virtual boundary, said map server being in communication with the connection server; and a CORS server responsible for maintaining a database of the RTK corrections, said CORS server being communication with the connections server.

31. The system of claim 30, wherein the file server, the map server and the CORS server only communicate with the at least one rover device via the connections server.

32. The system of claim 30, wherein the file server, the map server and the CORS server directly communicate with the at least one rover device once the connections server has authenticated the identity of the at least one rover device.

33. A method of controlling project file data on a civil construction site, said method including: establishing at least one virtual boundary at least partially defining the civil construction site;

monitoring a position of at least one rover device relative to the at least one virtual boundary, said rover device including at least one GNSS antenna and at least one modem; responsive to the at least one rover device entering the at least one virtual boundary, transmitting RTK correction data and project file data from at least one remotely accessible server to the at least one rover device; and

34. The method of claim 33, wherein the establishing includes establishing a geo-fence utilising GNSS or radio frequency identification (RFID) to define a geographical boundary around a perimeter of the construction site or part thereof.

35. The method of claim 33 or claim 34, wherein the monitoring is undertaken by at least one remotely accessible server addressing the at least one rover device to monitor the device’s location relative to the at least one virtual boundary.

36. The method of claim 33 or claim 34, wherein the monitoring is undertaken by the at least one remotely accessible server monitoring a communications network for connection requests from the at least one rover device, wherein responsive to receiving a request, the server determines the location of the device relative to the at least one virtual boundary.

37. The method of claim 33 or claim 34, wherein the monitoring includes the at least one rover device broadcasting at least positional information to the at least one remotely accessible server.

38. The method of any one of claims 33 to 37, wherein said responsive steps further include authenticating an identity of the at least one rover device prior to transmission or deletion of the RTK correction data and the project file data.

39. The method of claim 38, wherein responsive to the position of the at least one rover device being determined to be within the boundary and its identity being authenticated, the at least one remotely accessible server establishes a secure connection with the at least one rover device and transmits the RTK correction data and the project file data to the at least one rover device.

40. The method of claim 38, wherein responsive to the at least one rover being determined to be exiting the boundary and its identity being authenticated, the at least one remotely accessible server deletes the project file data from the device.