CA2979080A1 - Improved service oriented system architecture for asset management networks - Google Patents
Improved service oriented system architecture for asset management networksInfo
- Publication number
- CA2979080A1 CA2979080A1 CA2979080A CA2979080A CA2979080A1 CA 2979080 A1 CA2979080 A1 CA 2979080A1 CA 2979080 A CA2979080 A CA 2979080A CA 2979080 A CA2979080 A CA 2979080A CA 2979080 A1 CA2979080 A1 CA 2979080A1
- Authority
- CA
- Canada
- Prior art keywords
- layer
- gateway
- assets
- application
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 claims abstract description 34
- 238000012800 visualization Methods 0.000 claims abstract description 31
- 238000007726 management method Methods 0.000 claims description 25
- 238000000034 method Methods 0.000 claims description 24
- 238000003860 storage Methods 0.000 claims description 9
- 238000013523 data management Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000009227 antibody-mediated cytotoxicity Effects 0.000 description 70
- 230000001413 cellular effect Effects 0.000 description 23
- 230000006870 function Effects 0.000 description 23
- 230000006399 behavior Effects 0.000 description 15
- 230000005540 biological transmission Effects 0.000 description 10
- 230000008569 process Effects 0.000 description 10
- 238000013461 design Methods 0.000 description 6
- 230000009429 distress Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 6
- 238000001514 detection method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000013507 mapping Methods 0.000 description 5
- 230000011664 signaling Effects 0.000 description 5
- 238000009826 distribution Methods 0.000 description 4
- 241000196324 Embryophyta Species 0.000 description 3
- 230000004913 activation Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 229910052741 iridium Inorganic materials 0.000 description 3
- GKOZUEZYRPOHIO-UHFFFAOYSA-N iridium atom Chemical compound [Ir] GKOZUEZYRPOHIO-UHFFFAOYSA-N 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000001133 acceleration Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000007717 exclusion Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000001404 mediated effect Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000001228 spectrum Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- 230000036642 wellbeing Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Physics & Mathematics (AREA)
- Educational Administration (AREA)
- Marketing (AREA)
- Development Economics (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Game Theory and Decision Science (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
- Meter Arrangements (AREA)
- Telephonic Communication Services (AREA)
Abstract
A system for managing a plurality of assets comprising: an enterprise user layer; a presentation layer; a device layer; optionally a remote user layer and optionally one of: a visualisation layer, a service layer, an OEM gateway layer, a gateway layer, a communications layer and an applications layer.
Description
Improved Service Oriented System Architecture for Asset Management Networks Background of the invention:
Existing tracking and messaging systems are often closed system architectures with intrinsic design features that make the feasibility of including alternative sensing devices, communications paths and information presentation features unattractive technically or commercially. Hardware that interfaces to sensors is often custom designed or propriety in nature which places constraints on the ability to interconnect new sensing equipment which has non-compatible physical or protocol features. Little consideration if any has been given to '10 pushing intelligence to the far edge of these systems where its application may allow user features to be more effectively created and transmission demands on low bandwidth, contested communications channels reduced. Features such as least cost routing between terrestrial and satellite based communications networks are increasingly desired but available implementations often lack configuration and operational feature richness.
1 5 The presentation/visualisation functions of these systems are similarly highly custom designed and often cannot accept position or message data from alternate sources for a variety of reasons including for example database schema, terminal/device identification, data transmission and update/polling rates.
Many users of such systems desire systems in which new sensing elements can be easily 20 added at low cost, a variety of communications links can be used to meet service coverage requirements. information can be presented and visualised in a uniform and harmonised manner regardless of the communications links and sensors and access to information is supported via cloud services.
The reference to any prior art in this specification is not, and should not be taken as, an 25 acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.
Summary of the Invention in one aspect of the invention, there is provided a system for managing a plurality of assets 30 comprising: an enterprise user layer; a presentation layer, a device layer; optionally a remote user layer and optionally one or more of: a visualisation layer, a service layer, an OEM
gateway layer, a gateway layer, a communications layer and an applications layer.
In another aspect, there is provided a computer-implemented system for configuring context-specific management and or tracking of a plurality of assets and i or devices the configurable system comprising: an enterprise user layer; a presentation layer; a device layer; optionally a remote user layer and optionally one or more of: a visualisation layer, a service layer, an OEM gateway layer, a gateway layer, a communications layer and an applications layer.
The application layer may be implemented in any suitable manner, for example it may be distributed between physically separate servers.
In another aspect of the invention, there is provided a server comprising an enterprise user layer for corporate operational and data management; a presentation layer to provide at least one data access option to a user, an applications layer for one or more applications; and a gateway layer to provide connectivity with one or more external devices.
In another aspect there is provided a computer-implemented system for context-specific 1 5 management and or tracking of a plurality of assets and / or devices, the system comprising an enterprise user layer, a presentation layer, a visualisation layer, a service layer, a communications layer, an applications layer, a gateway layer, a device layer and a remote user layer wherein the system optionally further comprises a plurality of gateway layers. which comprise an OEM gateway layer, a converged data gateway layer and a mobile gateway 20 layer.
In one aspect of the invention, there is provided a non-transitory computer-readable storage medium storing a computer program, the computer-readable storage medium comprising program instructions for receiving data from a plurality of assets and program instructions for receiving and executing one or more instn_totions from an enterprise user layer; and program
Existing tracking and messaging systems are often closed system architectures with intrinsic design features that make the feasibility of including alternative sensing devices, communications paths and information presentation features unattractive technically or commercially. Hardware that interfaces to sensors is often custom designed or propriety in nature which places constraints on the ability to interconnect new sensing equipment which has non-compatible physical or protocol features. Little consideration if any has been given to '10 pushing intelligence to the far edge of these systems where its application may allow user features to be more effectively created and transmission demands on low bandwidth, contested communications channels reduced. Features such as least cost routing between terrestrial and satellite based communications networks are increasingly desired but available implementations often lack configuration and operational feature richness.
1 5 The presentation/visualisation functions of these systems are similarly highly custom designed and often cannot accept position or message data from alternate sources for a variety of reasons including for example database schema, terminal/device identification, data transmission and update/polling rates.
Many users of such systems desire systems in which new sensing elements can be easily 20 added at low cost, a variety of communications links can be used to meet service coverage requirements. information can be presented and visualised in a uniform and harmonised manner regardless of the communications links and sensors and access to information is supported via cloud services.
The reference to any prior art in this specification is not, and should not be taken as, an 25 acknowledgement or any form of suggestion that the prior art forms part of the common general knowledge.
Summary of the Invention in one aspect of the invention, there is provided a system for managing a plurality of assets 30 comprising: an enterprise user layer; a presentation layer, a device layer; optionally a remote user layer and optionally one or more of: a visualisation layer, a service layer, an OEM
gateway layer, a gateway layer, a communications layer and an applications layer.
In another aspect, there is provided a computer-implemented system for configuring context-specific management and or tracking of a plurality of assets and i or devices the configurable system comprising: an enterprise user layer; a presentation layer; a device layer; optionally a remote user layer and optionally one or more of: a visualisation layer, a service layer, an OEM gateway layer, a gateway layer, a communications layer and an applications layer.
The application layer may be implemented in any suitable manner, for example it may be distributed between physically separate servers.
In another aspect of the invention, there is provided a server comprising an enterprise user layer for corporate operational and data management; a presentation layer to provide at least one data access option to a user, an applications layer for one or more applications; and a gateway layer to provide connectivity with one or more external devices.
In another aspect there is provided a computer-implemented system for context-specific 1 5 management and or tracking of a plurality of assets and / or devices, the system comprising an enterprise user layer, a presentation layer, a visualisation layer, a service layer, a communications layer, an applications layer, a gateway layer, a device layer and a remote user layer wherein the system optionally further comprises a plurality of gateway layers. which comprise an OEM gateway layer, a converged data gateway layer and a mobile gateway 20 layer.
In one aspect of the invention, there is provided a non-transitory computer-readable storage medium storing a computer program, the computer-readable storage medium comprising program instructions for receiving data from a plurality of assets and program instructions for receiving and executing one or more instn_totions from an enterprise user layer; and program
2$ instructions to present data associated with one or more assets via a presentation layer; and optionally program instructions to execute an application associated with an application layer.
The invention also provides a computer implemented method comprising receiving data from a plurality of assets optionally via a gateway layer; receiving and executing one or more instructions from an enterprise user layer: presenting data associated with one or more 30 assets via a presentation layer: and optionally executing an application within an application layer.
The invention also provides in an asset or device tracking or management system, a rnethod for tracking or managing a plurality of assets or devices, the method comprising: an act of receiving data from a plurality of assets optionally via a gateway layer; an act of receiving and executing one or more instructions from an enterprise user layer; an act of presenting data associated with one or more assets via a presentation layer; and optionally an act of executing an application within an application layer.
In one aspect, the invention provides a server comprising an enterprise user layer for corporate operational and data management; a presentation layer to provide at least one data access option to a user; an applications layer for one or more applications;
and a gateway layer to provide connectivity with one or more external devices. In some embodiments, the server further comprises a visualisation layer to present system users with graphical information. in some embodiments, the server further comprises a computer implemented software application layer that is distributed between physically separate servers. In some embodiments, the server further provides a service layer to support connectivity between one or more layers or parts within the system. Connectivity between the device layer and the gateway layer may also be supported by a communications layer.
In one aspect, the invention provides a computer-implemented system for configuring context-specific management and or tracking of a plurality of assets and I or devices the configurable system comprising an enterprise user layer, a presentation layer, a visualisation layer, a service layer, a communications layer, an applications layer, a gateway layer, a device layer and a remote user layer wherein the system optionally further comprise a plurality of gateway layers which comprise an OEM gateway layer and a converged data gateway layer.
In another aspect of the invention, there is provided a non-transitory computer-readable 2$ storage medium storing a computer program, the computer-readable storage medium comprising program instructions for receiving data from a plurality of assets via a gateway layer; and program instructions for receiving and executing one or more instructions from an enterprise user layer; and program instructions to present data associated with one or more assets via a presentation layer; and program instructions to execute an application associated with an application layer.
This invention pertains to an open, service oriented system of systems architecture that enables a wide variety of functionality to be implemented in networks of tracking, sensing and messaging devices where those devices are widely geo-spatially distributed and may operate
The invention also provides a computer implemented method comprising receiving data from a plurality of assets optionally via a gateway layer; receiving and executing one or more instructions from an enterprise user layer: presenting data associated with one or more 30 assets via a presentation layer: and optionally executing an application within an application layer.
The invention also provides in an asset or device tracking or management system, a rnethod for tracking or managing a plurality of assets or devices, the method comprising: an act of receiving data from a plurality of assets optionally via a gateway layer; an act of receiving and executing one or more instructions from an enterprise user layer; an act of presenting data associated with one or more assets via a presentation layer; and optionally an act of executing an application within an application layer.
In one aspect, the invention provides a server comprising an enterprise user layer for corporate operational and data management; a presentation layer to provide at least one data access option to a user; an applications layer for one or more applications;
and a gateway layer to provide connectivity with one or more external devices. In some embodiments, the server further comprises a visualisation layer to present system users with graphical information. in some embodiments, the server further comprises a computer implemented software application layer that is distributed between physically separate servers. In some embodiments, the server further provides a service layer to support connectivity between one or more layers or parts within the system. Connectivity between the device layer and the gateway layer may also be supported by a communications layer.
In one aspect, the invention provides a computer-implemented system for configuring context-specific management and or tracking of a plurality of assets and I or devices the configurable system comprising an enterprise user layer, a presentation layer, a visualisation layer, a service layer, a communications layer, an applications layer, a gateway layer, a device layer and a remote user layer wherein the system optionally further comprise a plurality of gateway layers which comprise an OEM gateway layer and a converged data gateway layer.
In another aspect of the invention, there is provided a non-transitory computer-readable 2$ storage medium storing a computer program, the computer-readable storage medium comprising program instructions for receiving data from a plurality of assets via a gateway layer; and program instructions for receiving and executing one or more instructions from an enterprise user layer; and program instructions to present data associated with one or more assets via a presentation layer; and program instructions to execute an application associated with an application layer.
This invention pertains to an open, service oriented system of systems architecture that enables a wide variety of functionality to be implemented in networks of tracking, sensing and messaging devices where those devices are widely geo-spatially distributed and may operate
3 over heterogeneous communications networks. The architecture enables decision support functionality to be distributed in the network.
The presented invention is highly scalable in terms of the number of devices that can be managed as well as the number of enterprise users that can be supported and can be applied to a wide variety of tracking, sensing and messaging activities and business needs.
There are now available extensive M2M and loT technology and product solutions to Enterprises to facilitate tracking, sensing and messaging services for fleets of vehicles, personnel working alone or in small groups in remote locations, personnel and teams engaged in dynamic operational activities for example forest and open country firefighting and similar emergency response; tracking and managing equipment, plant or other assets in remote locations; etc. A fundamental limitation of the currently available solutions is that they are often implemented as closed systems making integration across the vendor space extremely difficult.
An important technology in all applicable product solutions is the means of connecting the remote users and assets to the Enterprise operational centres. The communications technology choice for transport of data and information is either terrestrially based, typically the cellular phone network, or short burst data (SBD) over satellite networks.
The technology and products available for use at Enterprise operational centres typically comprises visualisation platforms and data servers that combine to provide a feature rich environment.
In some ernbodiments, the invention is a system of systems architecture that facilitates a system integration between systems that use either the terrestrial networks or the satellite networks and allows seamless data and information sharing between those system&
The invention supports a flexible computing device that facilitates the distribution of decision making software applications to the remote system elements thereby improving both the functional capability of the services offered.
The invention supports a flexible approach to presentation of data and information to Enterprise operational centres in that it allows harmonisation of data and information at the visualisation level using existing OEM systems or new developments and also in terms of integration with Enterprise ERP systems regardless of the method of collection or transport using services oriented approaches or propriety interfaces as desired.
The presented invention is highly scalable in terms of the number of devices that can be managed as well as the number of enterprise users that can be supported and can be applied to a wide variety of tracking, sensing and messaging activities and business needs.
There are now available extensive M2M and loT technology and product solutions to Enterprises to facilitate tracking, sensing and messaging services for fleets of vehicles, personnel working alone or in small groups in remote locations, personnel and teams engaged in dynamic operational activities for example forest and open country firefighting and similar emergency response; tracking and managing equipment, plant or other assets in remote locations; etc. A fundamental limitation of the currently available solutions is that they are often implemented as closed systems making integration across the vendor space extremely difficult.
An important technology in all applicable product solutions is the means of connecting the remote users and assets to the Enterprise operational centres. The communications technology choice for transport of data and information is either terrestrially based, typically the cellular phone network, or short burst data (SBD) over satellite networks.
The technology and products available for use at Enterprise operational centres typically comprises visualisation platforms and data servers that combine to provide a feature rich environment.
In some ernbodiments, the invention is a system of systems architecture that facilitates a system integration between systems that use either the terrestrial networks or the satellite networks and allows seamless data and information sharing between those system&
The invention supports a flexible computing device that facilitates the distribution of decision making software applications to the remote system elements thereby improving both the functional capability of the services offered.
The invention supports a flexible approach to presentation of data and information to Enterprise operational centres in that it allows harmonisation of data and information at the visualisation level using existing OEM systems or new developments and also in terms of integration with Enterprise ERP systems regardless of the method of collection or transport using services oriented approaches or propriety interfaces as desired.
4 Throughout this specification (including any claims which follow), unless the context requires otherwise, the word 'comprise', and variations such as 'comprises and .comprising'; will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.
Brief Description of the Drawings Figures 1A-1C (collectively 'Figure 1') show diagrammatic representations of an embodiment of a system architecture according to the present invention.
Figures 2A and 2B are a block diagrams of example entity relationship of certain embodiments of a system architecture according to the present invention.
1 0 Figure 3 is a block diagram of an example configuration of devices within an embodiment of a system architecture according to various aspects of the present invention.
Figure 4 is a block diagram of a example software applications within an embodiment of a system architecture according to various aspects of the present invention.
Figure 5 is a flow chart of a Device Configuration application according to one ernbodiment of the present invention.
Figure 6 is a flow chart of a Connection Management application according to one embodiment of the present invention.
Figure 7 is a flow chart of a Tracking application according to one embodiment of the present invention.
Figure 8 is a flow chart of an Association application according to one embodiment of the present invention.
Figure 9 is a flow chart of a Safety application according to one embodiment of the present invention.
Figure 10 is a flow chart of a Reconciliation application according to one embodiment of the present invention.
Figure 11 is a flow chart of a Driver Behaviour application according to one embodiment of the present invention, Detailed Description of Exemplary Embodiments
Brief Description of the Drawings Figures 1A-1C (collectively 'Figure 1') show diagrammatic representations of an embodiment of a system architecture according to the present invention.
Figures 2A and 2B are a block diagrams of example entity relationship of certain embodiments of a system architecture according to the present invention.
1 0 Figure 3 is a block diagram of an example configuration of devices within an embodiment of a system architecture according to various aspects of the present invention.
Figure 4 is a block diagram of a example software applications within an embodiment of a system architecture according to various aspects of the present invention.
Figure 5 is a flow chart of a Device Configuration application according to one ernbodiment of the present invention.
Figure 6 is a flow chart of a Connection Management application according to one embodiment of the present invention.
Figure 7 is a flow chart of a Tracking application according to one embodiment of the present invention.
Figure 8 is a flow chart of an Association application according to one embodiment of the present invention.
Figure 9 is a flow chart of a Safety application according to one embodiment of the present invention.
Figure 10 is a flow chart of a Reconciliation application according to one embodiment of the present invention.
Figure 11 is a flow chart of a Driver Behaviour application according to one embodiment of the present invention, Detailed Description of Exemplary Embodiments
5 it is convenient to describe the invention herein in relation to particularly preferred embodiments. However, the invention is applicable to a wide range of implementations and it is to be appreciated that other constructions and arrangements are also considered as falling within the scope of the invention. Various modifications, alterations, variations and or additions to the construction and arrangements described herein are also considered as failing within the ambit and scope of the present invention.
System Level Figure 1 is a block diagram of an example architecture 119 according to various aspects of the invention.
0 The architecture 119 according to these embodiments is flexible and supports various presentation formats 109 which may include maps and other GIS information displayed on computer screens '110, for access to and display of textual and tabular data supported on a variety of visualisation platforms 106, service oriented interfacing 107 using WebAPI and Internet cloud services to data centre servers 111 and various reports and documentation created from call and sensor data in (in this example) PDF and text files 112.
information presentation 109 supports intemet Web API services with pull and push functionality. The information presentation 109 relates to persons 113, 114, 115, 121 and other assets located at disparate geographical locations and connected via communications channels 103 which may be 3G/4G cellular networks 122 or satellite Short Burst Data (SBD) networks 118 or a combination of those methods. In the example architecture 119 persons 113 may use a UHF device 120 to communicate certain data which may for example include location, aoc...essibility, signalling duress, detection of man-down or network test to the extent that such features are supported by the UHF device. Persons 121 may use a 3G/4G smart phone running applications that support Applications 108 features of the example architecture 119. Persons 114 may have access to sensors that are wired in to a vehicle which may for example include a duress button, driver behaviour feedback for example in the form of one or more of light, sounds etc, text messaging functions, seat belt engagement status, fatigue sensors and a range of similar sensors types. UHF sensors 120 may be interfaced to the mobile computing platform 116 computing device via UHF base station 117 equipment.
Furthermore the UHF base station117 implements message format mapping for direct connection over the implemented satellite communications equipment 118.
The mobile computing platform 116 implements application firmware that performs a range of fumiions that include non-volatile storage of sensor data: interpretation of sensor data and
System Level Figure 1 is a block diagram of an example architecture 119 according to various aspects of the invention.
0 The architecture 119 according to these embodiments is flexible and supports various presentation formats 109 which may include maps and other GIS information displayed on computer screens '110, for access to and display of textual and tabular data supported on a variety of visualisation platforms 106, service oriented interfacing 107 using WebAPI and Internet cloud services to data centre servers 111 and various reports and documentation created from call and sensor data in (in this example) PDF and text files 112.
information presentation 109 supports intemet Web API services with pull and push functionality. The information presentation 109 relates to persons 113, 114, 115, 121 and other assets located at disparate geographical locations and connected via communications channels 103 which may be 3G/4G cellular networks 122 or satellite Short Burst Data (SBD) networks 118 or a combination of those methods. In the example architecture 119 persons 113 may use a UHF device 120 to communicate certain data which may for example include location, aoc...essibility, signalling duress, detection of man-down or network test to the extent that such features are supported by the UHF device. Persons 121 may use a 3G/4G smart phone running applications that support Applications 108 features of the example architecture 119. Persons 114 may have access to sensors that are wired in to a vehicle which may for example include a duress button, driver behaviour feedback for example in the form of one or more of light, sounds etc, text messaging functions, seat belt engagement status, fatigue sensors and a range of similar sensors types. UHF sensors 120 may be interfaced to the mobile computing platform 116 computing device via UHF base station 117 equipment.
Furthermore the UHF base station117 implements message format mapping for direct connection over the implemented satellite communications equipment 118.
The mobile computing platform 116 implements application firmware that performs a range of fumiions that include non-volatile storage of sensor data: interpretation of sensor data and
6 the mapping of that data into maximally efficient structures for minimum cost transmission over the selected satellite communications path 103. Furthermore the mobile computing platform 116 runs applications 108 either as standalone applications or as component(s) of a distributed application implementation.
Visualisation 106 can for example be supported via a number of OEM and open systems which may be closely coupled to the supporting network infrastructure and OEM
Gateways 104 or via the gateway 105.
Services 107 is functionality that implements various aspects of the presentation 109 for example pertaining to the creation of reports 112 and data centre 111 interfacing.
The application 108 pertains to a set of functionality implemented on the gateway platform 105 or a mobile computing platform 116, or both if the application functionality is distributed, which may harmonise information from heterogeneous communications network gateways 104 and provide management functionality at an individual level 113, 114,115, group 101 and configurable aggregations of individuals where 101 and 102 are illustrations. Applications may include a connection management function, a device management function which may for example include mapping of device identifiers (ID) and message structures between heterogeneous communications network gateways 104, a data storage and manipulation function, a location tracking function, a driver behaviour analysis function, ad hoc network association function, a safety related services function and various system maintenance functions, Figure 2A: System of Systems Top Level Architecture is further illustrative of the context of the invention, Enterprise User Layer The enterprise user layer 201 may for example comprise corporate operational and data management systems, functions and personnel managing those systems, functions or personnel.
The corporate operational systems and functions may be defined in policies, regulations, standard operational procedures, or business specific functional and performance specifications and other similar documents and would typically include financial, operational and technical requirements as they pertain to particular enterprises.
Visualisation 106 can for example be supported via a number of OEM and open systems which may be closely coupled to the supporting network infrastructure and OEM
Gateways 104 or via the gateway 105.
Services 107 is functionality that implements various aspects of the presentation 109 for example pertaining to the creation of reports 112 and data centre 111 interfacing.
The application 108 pertains to a set of functionality implemented on the gateway platform 105 or a mobile computing platform 116, or both if the application functionality is distributed, which may harmonise information from heterogeneous communications network gateways 104 and provide management functionality at an individual level 113, 114,115, group 101 and configurable aggregations of individuals where 101 and 102 are illustrations. Applications may include a connection management function, a device management function which may for example include mapping of device identifiers (ID) and message structures between heterogeneous communications network gateways 104, a data storage and manipulation function, a location tracking function, a driver behaviour analysis function, ad hoc network association function, a safety related services function and various system maintenance functions, Figure 2A: System of Systems Top Level Architecture is further illustrative of the context of the invention, Enterprise User Layer The enterprise user layer 201 may for example comprise corporate operational and data management systems, functions and personnel managing those systems, functions or personnel.
The corporate operational systems and functions may be defined in policies, regulations, standard operational procedures, or business specific functional and performance specifications and other similar documents and would typically include financial, operational and technical requirements as they pertain to particular enterprises.
7 The invention embodiment described herein is for a system architecture for a generic Ernergency Management Service which may comprise a single agency or multiple agencies whose function is to manage emergency events including but not necessarily limited to fire control, storm damage or other natural disasters that impact a single wide geographic area or multiple disconnected areas. Further the invention has wide application where tracking and management of personnel, machinery, equipment and plant, be that in terms of location, operational status, health and wellbeing, authentication and behaviour of personnel or control functions, that are distributed geographically be that by the nature of the geographical distance, geographical accessibility by the nature of the terrain, distance to the main business or operations centres, dispersed workforce or sirnilar operational conditions and scenarios.
Presentation Layer The system may comprise a presentation layer function 202, to present to the enterprise user a suite of data access options. In certain implementations the presentation layer 202 may be a non-functional virtual container for the visualisation layer 204 and the service layer 203. The presentation layer 202 may comprise a set of descriptions. definitions, configuration options, user instructions and other similar technical and operational information that support the enterprise user layer 201 with correct, effective and efficient operation of the system and this represents the interface 2'11 between the enterprise user layer 201 and the presentation layer 202, Visualisation Layer The system may comprise a visualisation layer 204 to present system users with screen based graphical information that displays geographical maps, representational maps or diagrams, asset and device attributes which may include the geographical location, connection status, operational status of the reporting devices and the person or persons associated with it, messages from the reporting devices which may be automatically created or manually entered by the person or persons associated with it and other similar information as may be specified by the system users. The interface 213 between the presentation layer function 202 and the visualisation layer 204 may be of any suitable type, for example, in some implementations they comprise a variety of propriety and open visualisation platforms that display and allow access to mapping. GIS data, messages, configuration and similarly related information.
The visualisation layer 204 may be supported on visualisation platforms 206 including OEM
products such as Honeywell ViewPoint:
GeoManager and similar Trimble products
Presentation Layer The system may comprise a presentation layer function 202, to present to the enterprise user a suite of data access options. In certain implementations the presentation layer 202 may be a non-functional virtual container for the visualisation layer 204 and the service layer 203. The presentation layer 202 may comprise a set of descriptions. definitions, configuration options, user instructions and other similar technical and operational information that support the enterprise user layer 201 with correct, effective and efficient operation of the system and this represents the interface 2'11 between the enterprise user layer 201 and the presentation layer 202, Visualisation Layer The system may comprise a visualisation layer 204 to present system users with screen based graphical information that displays geographical maps, representational maps or diagrams, asset and device attributes which may include the geographical location, connection status, operational status of the reporting devices and the person or persons associated with it, messages from the reporting devices which may be automatically created or manually entered by the person or persons associated with it and other similar information as may be specified by the system users. The interface 213 between the presentation layer function 202 and the visualisation layer 204 may be of any suitable type, for example, in some implementations they comprise a variety of propriety and open visualisation platforms that display and allow access to mapping. GIS data, messages, configuration and similarly related information.
The visualisation layer 204 may be supported on visualisation platforms 206 including OEM
products such as Honeywell ViewPoint:
GeoManager and similar Trimble products
8 and GAP from twolOdegrees. The functionality of the gateway 205 and message specifications visualisation platforms can display details of devices attached to the system regardless of the communications layer 208 by which they are attached, for example be that via the cellular network, the Inmarsat satellite network or the Iridium satellite network.
The visualisation layer 204 has an interface 213 to the presentation layer 202 which in this embodiment is used to aid the description of the invention.
Service Layer The system may comprise a service layer 203 to support connectivity between the gateway 205 and user enterprise data management systems. The service layer supports a WebAPI
'10 which provides cloud access to data residing on the gateway. In this example, the service layer supports a report engine, such as for example Microsoft ReportWriter which provides customisable summary reports derived from data residing on the gateway. The service layer 203 supports a Direct Data interface which provides intemet connection access to data residing on the gateway in a format which is suitable for direct automated import into corporate data processing systems. The service layer 203 facilitates customised access to data residing on the gateway 205 where the mentioned methods do not satisfy the requirements of enterprise user layer 201, In some embodiments, the service layer 203 may be implemented on the gateway layer 205:
The service layer 203 has an interface 212 to the presentation layer 202 which in this embodiment is used to aid the description of the invention.
OEM Gateway Layer In some embodiments, the system comprises an Original Equipment Manufacturer (OEM) gateway layer 206 which may be notionally thought of as a container for commercial gateways, such as those provided by Honeywell, Trimble and Iridium (see for example Figure 28). It may also be used for any other similar network connectivity which may include cellular network operator access point servers. An operator of the invention may for example have specific commercial arrangements for the connection to and data transfer between specific OEM gateways 206 and the gateway layer 205. The OEM gateway layer 206 may for example be defined by these agreements and the associated technical definition of the methods and protocols for connection to and data transfer between these specific gateways and the gateway of the invention 205.
The visualisation layer 204 has an interface 213 to the presentation layer 202 which in this embodiment is used to aid the description of the invention.
Service Layer The system may comprise a service layer 203 to support connectivity between the gateway 205 and user enterprise data management systems. The service layer supports a WebAPI
'10 which provides cloud access to data residing on the gateway. In this example, the service layer supports a report engine, such as for example Microsoft ReportWriter which provides customisable summary reports derived from data residing on the gateway. The service layer 203 supports a Direct Data interface which provides intemet connection access to data residing on the gateway in a format which is suitable for direct automated import into corporate data processing systems. The service layer 203 facilitates customised access to data residing on the gateway 205 where the mentioned methods do not satisfy the requirements of enterprise user layer 201, In some embodiments, the service layer 203 may be implemented on the gateway layer 205:
The service layer 203 has an interface 212 to the presentation layer 202 which in this embodiment is used to aid the description of the invention.
OEM Gateway Layer In some embodiments, the system comprises an Original Equipment Manufacturer (OEM) gateway layer 206 which may be notionally thought of as a container for commercial gateways, such as those provided by Honeywell, Trimble and Iridium (see for example Figure 28). It may also be used for any other similar network connectivity which may include cellular network operator access point servers. An operator of the invention may for example have specific commercial arrangements for the connection to and data transfer between specific OEM gateways 206 and the gateway layer 205. The OEM gateway layer 206 may for example be defined by these agreements and the associated technical definition of the methods and protocols for connection to and data transfer between these specific gateways and the gateway of the invention 205.
9 WO 2016/14141_1 PCUAU2016/000077 The OEM gateway layer 206 has an interface 216 to the visualisation layer 204 that is proprietary to each OEM instance and may only be accessible to those OEM
instances_ In some embodiments, the invention does not provide for access to interface 216 except in that it is a natural part of OEM gateways and their visualisation platforms.
Gateway Layer The system may comprise a Gateway layer 205 (which may be distributed) which is comprised of server hardware with suitable specifications_ An example system may for example comprise: CPU speed 2_2 Ghz, 4 GB RAM and 64 bit addressing running the Window Server 2008 operating system as a virtual server, a MicrosoftSQL
database, a PostgreSOL database and the Application layer 207 software that implements the core system functionality written in Python. The gateway will of course run on any suitable hardware and software with appropriate specifications.
In some example implementations, a mobile computing platform herein referred to as the AMC also forms part of the Gateway layer 205. The AMC (see Figure 3, item 317) acts as an 1 5 interface to sensors in the device layer 209 and communications equipment forming part of the communications layer 208, The AMC is a flexible, low cost computing platform running an operating system with hardened file management to improve operational robustness which in one embodiment may for example be a Raspberry Pi 2 hardware platform running a modified distribution of the Linux operating system.
The AMC may be implemented in a variety of configurations to support specific applications which may include aspects of the application layer 207. The AMC may have various signalling 331 and power connections 339 via the wiring loom 313 to a wide variety of sensor devices. The AMC 317 may connect 332 to the ODB tracker 310. The AMC may connect 333 to the cellular system in-vehicle interface 315. The AMC may connect 335 to the SBD satcom equipment 316.
The architecture is scalable to accommodate multiple enterprise customers, multiple OEM
gateways, multiple web services and a large base of managed devices and assets.
The message handling capacity requirements of the gateway layer 205 are mediated by the natural message transfer capacities of the communications layer 208 networks via the OEM
gateway layer 206.
In this example, the gateway layer 205 is designed to support tens of thousands of assets (for example vehick. ..";.-...3ultaneously. To achieve this requirement, the gateway cri !^.7. built using technologies that power the world's largest Internet websites, such as the Python Django Web framework and the Microsoft SQL Server 2008R2 Database and Reporting Services. The Python Django Web framework is capable of supporting thousands of simultaneous users per second. The Microsoft SQL Server is an Enterprise grade database capable of supporting hundreds of millions of records across complex relational data structures. The gateway may be hosted in any suitable manner, for example it may be hosted on a virtualised Microsoft Windows 2008R2 Server Operating System, facilitating simple and incremental upgrade of underlying hardware as the system grows and evolves.
The gateway layer 205 has an interface 214 to the services layer which in this example is embodied as SQL code for database access and WebAPI's for cloud services. The gateway layer 205 has an interface 217 to the applications layer 207 which is embodied as compiled code running on the gateway layer 205 hardware. The gateway layer 205 has an interface 222 to the OEM gateway layer 206 which is defined by agreements between and the OEM
gateway layer 206 owner/operator, Applications Layer The system may comprise an applications layer 207. The application layer 207 is generally described by Figure 4. Applications may reside wholly at the gateway layer 205 or be distributed between the gateway layer 205 and multiple instances of the AMC
317 or its variants.
The invention may comprise a set of applications which may for example include device configuration 401, connection management 402, tracking 403, driver behaviour 404, association 405, safety 406, and reconciliation 407 with the facility to incorporate additional applications. Furthermore the architecture supports expanding the applications functionality to service future enterprise requirements as they emerge.
Device Configuration An example functionality of the device configuration 401 application is generally described by Figure 5 by which the function is to allow a user of the system to define persons and devices within the system including creation, modification and deletion actions, map device identification (ID) to specific persons and assets, manage ID mapping between the different OEM gateways 206. Instances of OEM gateways 206 do not necessarily maintain or make available the associations between driver ID and communications device equipment/subscriber 10. Different instances of OEM gateways 206 may behave differently in that regard. To facilitate a dual mode cellular/satellite tracking service or a tracking service that may utilise two different SBD satcom systems it is a necessary requirement that cellular tracking data and satellite tracking data can be associated. The device configuration application 401 may perform this function.
In this example. the device configuration application maintains the data in tables in the system database. This data is accessible to other applications within the applications layer 207 Figure 2A: Application Layer Functions running on the gateway 105. Data created, stored and maintained by the device configuration 401 application may be used by the connection management 402 application and the reconciliation 407 application and is available to other applications 207 running on the gateway 105.
Connection Management The functionality of the connection management 402 application is generally described by Figure 6 by which details of the connection status of a defined device is maintained by interaction with the attached OEM gateways. The connection management 402 application:
$ 1. manages the establishment of a connection between the gateway 105 and any OEM
gateways 104:
2. maintains established connections:
3 removes an established connection, 4. maps messages received over an established gateway connection to a device ICI, 2() 5. sends messages over an established gateway connection in a format which the OEM
gateway 206 can accept and process, 6. receives user ID information based on Fob 311 or RDIF Card 303 or other identification means, maps the user ID to a device ID and disseminates the user ID
information to those attached OEM gateways 104 for display on their visualisation platform via method 25 defined in interface agreements.
Furthermore the connection management application 402 supports a least cost routing function. This application may be distributed between the gateway 105 and the instances of the AMC 317 according to design principles that minimise the cost of sending data over the communications layer 208. The choice of route selection is configurable to meet user =30 requirements which may include route preferences, financial cost constraints, data delivery WO 2()16/141411 PCT/AU2016/0000 77 integrity and similar considerations and also takes account of device capabilities for example the propensity of certain cell phones to preferentially choose a WiFi connection noting that this may in fact route to a more costly satellite connection via the AMC 317 even though a viable, lower cost 3G or 4G network connection may be available.
Data created, stored and maintained by the connection management application 402 may be used by the tracking application 403 and is available to other applications 207.
Tracking The functionality of the tracking application 403 is generally described by Figure 7 by which the geographical location of a tracking device is recorded and maintained. In the case where O a device that reports location via an AMC fails to report its location where the failure to report is decided by timer supervision or by other rules of logic embedded within the tracking application a discovery process may be initiated which attempts to locate the device by searching over the active population of AMC ,devices defined previously by an association relationship configuration activity by the association application 405. Where the device 1 5 location is found by the aforementioned search the location is updated and the device is associated with the reporting entity according to the services of the association 405 application. In a case where the device cannot be located during any given instance of a discovery process it is placed on a watch list which may be used in any subsequent invocations of the discovery process or by the reconciliation application 407.
20 The tracking application 403 may receive messages from devices representing activation of a sensor or data recorded by a sensor in which case the message received is interpreted according to message parsing rules embedded within the application and the resultant data or information stored for use by other entities within the application 407 layer and may disseminate selected data and information to attached OEM gateways 104 for display on their 25 visualisation platform.
Association The functionality of the association application 405 is generally described by Figure 8. An hierarchal association is established and maintained between specified devices and logical groups as defined by the enterprise user layer 101 appropriate to their business or 30 operational context. For example in one implementation, an example context is to know the distribution of highly mobile resources and assets deployed in a dynamic firefighting operation possibly grouped as Appliances, strike teams, operational command or similar organisational or geo-located groupings thereby enabling more effective decision making in relation to resources by operational command teams.
In the system architecture 119 example associations may be Appliances whereby a group of personnel equipped with a GPS enabled UHF Pendant 302 is associated with an AMC
installed on a specified vehicle, also called an Appliance in certain contexts. Appliances may be grouped into Strike Teams and Strike Teams associated with specified geographical areas or operational zones, noting that the OEM Gateways and Visualisation platforms support sophisticated geo-fencing capabilities for this as well as other purposes.
Such an association hierarchy may be extended to an arbitrary number of levels within the constraints of the available processing capacity of the gateway 105 and predetermined configuration limits.
The association application 405 is distributed between the gateway 105 and the instances of the AMC 317 according to design principles that minimise the messaging and data transferred between these entities so as to reduce satellite link resource requirements and related operational casts to the users.
In the example the AMC has knowledge of the group of GPS enabled UHF Pendant devices 302 assigned to it. The AMC 317 maintains the connection status of each UHF
Pendant 302 within its association group based on the UHF link connection 320. When it is determined by heuristics embedded in the association 405 application running on the AMC 317 that a UHF
connection 320 to one or more instances of a UHF Pendant 302 has been lost this information is reported to the association 405 application running on the gateway 105 which may subsequently initiate a discovery search. At the same time the subject AMC
317 may periodically check and reconcile the status of all UHF linked UHF Pendant 302 advising the association 405 application running on the gateway 105 of status changes.
In the case where an instance of a UHF Pendant 302 being recognised by two or more AMC's 317, which is possible due to the physical characteristics of the UHF
channel 320, group associations are maintained, in the following order, first as the AMC
317 to which the UHF Pendant 302 is nominally configured, herein referred to as the home group, then if lost to the home group the association will be to the group of the AMC 317 which first reports the discovery of the UHF Pendant 302. At any subsequent time if the UHF Pendant 302 instance is discovered by the home group AMC 317 it will be re-associated with that group.
In one specific instance there are up to six crew members associated with each Appliance ¨
limited to six by the number of seats in the Appliance. Crew members initial assemble at the location where the 4,7.7ance is garaged. At this time each crew member is carrying, e-q14.
individualised UHF Pendant 302 which they activate. The UHF base station 312 detects the active UHF pendants 302 and forwards the details to the AMC 317. It is possible that there is more than one Appliance and crew at the garage site and if this is the case then it is possible that all or most of the UHF pendants 302 are detected by all or most UHF base stations 312, To establish the actual disposition of crew members to Appliances the Association 405 application running on the AMC 317 runs an algorithm that uses position information of the relative locations of the AMC 317 on an Appliance and each UHF Pendant 302 and also time and speed data to validate who is actually riding on an Appliance. In essence, the heuristic logic is that UHF Pendants 302 within approximately 5m of the ACM are likely to be the crew members, then UHF pendants 302 and an ACM 317 moving at the same speed are likely to be on the same Appliance and assessment over a time window improves the integrity of the association.
In one specific instance in the active operational area a crew members may become separated from their Appliance, in this case the crew member may be detected by another UHF base station 312. Where that occurs the information is passed to the AMC
connected to that UHF base station 312 and the AMC retains a record of that contact. This process is generalised to all UHF pendants 302 and AMCs 317. By this means a track of all UHF pendants 302 is continuously updated. The association 405 application running on the gateway 105 may poll AMC's 317 in order to establish or maintain the disposition of UHF
pendants 302. Furthermore the association 405 application running on the gateway 105 may query selected AMC's 317 regarding a specific UHF Pendant 302 by its ID for its location and currently associated Appliance.
In one specific instance in an active operational area where two Appliances are active in close proximity to each other one of these Appliances may suffer a mechanical failure and become unserviceable. Further in this scenario conditions may escalate to the point of becoming an imminent clanger to life necessitating an immediate evacuation. In such a case or similar scenario up to twelve crew members may be required to mount the operational Appliance and make their escape. The UHF base station 312 on the operational Appliance will detect all UHF pendants 302 according to the already described association algorithm thereby supporting rescue actions by providing knowledge of the location and roll call.
The association application 405 design is highly flexible in that it allows an arbitrary definition of the size of groups and the number of levels of association.
Safety The functionality of the safety application 406 is generally described by Figure 9 by which in the example conditions that may reflect the safety of personnel are monitored, maintained and reported. The example supports duress conditions as either signalled by pressing the duress button 301 or 315, a man down condition detected by a UHF Pendant 302 or similarly capable device or by fatigue status determined by a fatigue sensor 309. The safety application 406 sets the safety status of the reporting device ID which is then available to the tracking application 403 which may forward the information to OEM gateways 104 or other visualisation platforms 406 for display and alerting.
Reconciliation The functionality of the reconciliation application 407 is generally described by Figure 10 by which in the example operational groups are retired from active operations to, for example, a staging area. At this time is may be a requirement to verify that all resources and assets that form any given operational group returning from active deployment have returned as expected. The reconciliation application 407 is a particular case of the association application 405 in which all the subject AMC units of the various returned Appliances are interrogated for UHF Pendant 302 connection status. An alert may be created for each missing UHF Pendant 302 unit and also a report may be created detailing the reconciled disposition of all subject resources and assets including any that are missing. The invention allows for UHF Pendant 302 units that have not been nominally assigned to any group to be included in all discovery and reconciliation processes thereby facilitating the management of ad hoc and unplanned changes to the operational resource base.
Driver Behaviour The functionality of the driver behaviour layer 404 application is generally described by Figure 11 by which various data which may include location, fatigue state, acceleration, braking, cornering and speed are sensed and analysed for a variety of driving characteristics according to a set of configurable heuristic rules or process against desired driver behaviours which may include unauthorised area access, swerving, harsh acceleration, harsh braking, harsh cornering and speeding. Furthermore location data may be used to modulate driving behaviour heuristics. Violation of desired driver behaviours are alerted to the driver via in-vehicle indicators which may include lights and audible sounds. A report is created that includes details of the driver behaviour which may be used to create a summary of driver behaviour over periods of time, The driver behaviour layer 404 is distributed between the AMC 317 and the gateway 105 with the AMC 317 responsible for collection of sensor data, analysis of that data for violations, in-vehicle violation presentations and formatting of data and information suitable for transmission and the gateway 105 responsible for storage of the data and information and 5. creation of time based driver behaviour analysis and reporting. As a part of the reporting features the gateway 105 may forward details of driver behaviour violations to the OEM
gateways 104 for immediate presentation.
Communications Layer The system may comprise a communications layer 208 to support connectivity between the device layer 209 and the OEM gateway layer 206, in some embodiments, the invention utilises one or more of a cellular phone network, the Inmarsat M2M network and the Iridium network indicated by interface 218. in any particular instance of the architecture 119 one or more of these communications paths will be available. The selection and mix of communication layer 208 technology is driven by enterprise user layer requirements.
Remote User Layer The remote user layer 210 may comprise personnel, vehicles, plant, equipment or other physical assets that may form part of the enterprise or operation. This layer has an interface 221 to the device layer 210 which are detailed in the description of the device layer 210.
Device Layer The system is comprised of a device layer 209 which is comprised of a set of OEM and designed hardware devices, some running embedded software applications and many of which act as sensors, as illustrated by Figure 3. The set of devices and their interfaces 219 and 220 used in any particular deployment of the invention may vary depending on specific enterprise user layer 201 requirements and may typically include:
1. A device which acts as an interface to sensors and communications equipment forming part of the communications layer 308 which in this embodiment is named the AMC
317..
The AMC 317 is a flexible, low cast computing platform running an operating system with hardened file management to improve operational robustness which in one embodiment may be a Raspberry Pi 2 hardware platform running a modified distribution of the Linux operating system.
2. The AMC may be implemented in a variety of configurations to support specific applications which may include the application layer 207. The AMC 317 may have various signalling 331 and power connections 339 via the wiring loom 313 to a wide variety of sensor devices, The AMC 317 may connect 332 to the ODB tracker 310. The AMC
may connect 333 to the cellular system in-vehicle interface 315. The AMC 317 may connect 335 to the SBD satcom equipment 318.
3. One or more instances of SBD satellite tracking and messaging equipment 318 4. A seatbelt engaged sensor 305 which employs a magnetic field proximity sensing method to detect when the seatbelt tongue and buckle are closer than approximately 5 cm. The detection is inferred to mean that the seat belt is fastened whilst recognising that this may be factually false. The buckle mounted sensor element is connected to the AMC
317 via a wiring loom 313 and discrete wire interface 322. The sensor does not rely on other in-vehicle seatbelt detection equipment or signalling and is fully independent of such equipment.
5. A Vehicle ignition-on sensor 306 which supports battery discharge protection. The vehicle ignition-on sensor 306 is connected to the AMC 317 via a wiring loom 313 and discrete wire interface 323. The AMC inhibits SBD satcom equipment 318 transmissions when the vehicle ignition-on sensor 306 indicates that engine is off.
6. Simple sensors including press buttons, example instances being a duress button 301 20= and a button on the cellular system in-vehicle interface 315.
Activation of the duress button causes a specific distress message handling protocol to be started with the OEM
gateway 206 Figure 2A and visualisation layer 204 Figure 2A of the example architecture 119 Figure 1 which results in high priority visual display of the condition.
Distress signal interfaces 319 and 334 directly connect the distress signal to the SBD satcom equipment 318. lt is noted that the gateway 205 Figure 2A is not involved any distress message handling protocol;
7. A personal tracking device which in this example is a UHF Pendant 302 which connects via a UHF signal 320 to a UHF base station 312, The UHF Pendant 302 and UHF
base station 312 are OEM devices which use unlicensed UHF spectrum as the communications media. The UHF Pendant 302 has a clip 337 to allow attachment to a belt OF other clothing or can be mounted in-vehicle in a custom cradle 337. A
UHF
Pendant 302 features include a button for duress activation, a button for welfare check-in, automatic man-down cigtection and GPS tracking. The UHF base station provides interface 330 to the AMC 317 via the wiring loom 313 and a dedicated distress signal 334 interface for direct connection to SDB satcom equipment 318 The UHF Pendant communicates with the UHF base station 312 using a proprietary protocol and message structures. The UHF base station 312 upon receiving a message from the UHF
pendant formats a message which it passes to the AMC 317 using a set of proprietary protocol and message structures over a 'wired serial interface 330. The AMC 317 processes messages received from the UHF base station 312 based on the message type received.
In the example architecture 119 Figure 1 the AMC 317 may use GPS tracking data to update associations according to the application 207 Figure 2A association process 405 Figure 4. Furthermore the AMC 317 may use the GPS tracking data in messages to the application 207 Figure 2A running on the gateway 205 Figure 2A for storage, processing according to various algorithms and processes which may be running as part of the on the application 207 Figure 2A on the gateway 205 Figure 2A. Furthermore the application 207 Figure 2A on the gateway 205 Figure 2A may forward data derived from UHF
pendant 302 messages to OEM gateways 206 Figure 2A and visualisation layers 204 Figure and the service layer 203 Figure 2A as controlled by the application 207 Figure 2A
running on the gateway 205 Figure 2A;
8. Devices to support driver authentication which in this example may include an RFID card 303 and RFID card reader 304 with an RFID link 342 or a key fob 311 used in association the cellular system in-vehicle interface 315 via a magnetic link 327. The RFID
card 303 and RFID card reader 304 are OEM devices connected via an RFID link 345. The RFID
card 303 may be issued by the enterprise user to personnel as a means of identification (ID) for the purposes of authentication. In the example architecture 119 Figure 1 the RFID
card 303 is used as a means for a driver to activate a connection to the system. Driver ID
details are communicated to the AMC 317 via a wiring loom 313 via interface 331 using interface 321 for the RFD card reader 304 and interface 333 for the cellular system in-vehicle interface 315. The driver details are read by the RFD card reader 304 which passes them to the AMC 317 using a set of proprietary protocol and message structures via a wired USB interface 321. The AMC extracts data fields from the received message and inserts them into a message structure design for efficient transmission over a SBD
satellite channel 335 matching the specific SBD sat= equipment 318 implemented in an instance of the example architecture 119 Figure 1, The Driver ID
authentication function is typically handled in the OEM gateways 206.
ae:=
9. A fatigue sensor 309 that implements algorithms the output of which is an indicator of the state of driver fatigue which is connected to the AMC 317 via a wiring loom 313 and discrete wire interface 326.
instances_ In some embodiments, the invention does not provide for access to interface 216 except in that it is a natural part of OEM gateways and their visualisation platforms.
Gateway Layer The system may comprise a Gateway layer 205 (which may be distributed) which is comprised of server hardware with suitable specifications_ An example system may for example comprise: CPU speed 2_2 Ghz, 4 GB RAM and 64 bit addressing running the Window Server 2008 operating system as a virtual server, a MicrosoftSQL
database, a PostgreSOL database and the Application layer 207 software that implements the core system functionality written in Python. The gateway will of course run on any suitable hardware and software with appropriate specifications.
In some example implementations, a mobile computing platform herein referred to as the AMC also forms part of the Gateway layer 205. The AMC (see Figure 3, item 317) acts as an 1 5 interface to sensors in the device layer 209 and communications equipment forming part of the communications layer 208, The AMC is a flexible, low cost computing platform running an operating system with hardened file management to improve operational robustness which in one embodiment may for example be a Raspberry Pi 2 hardware platform running a modified distribution of the Linux operating system.
The AMC may be implemented in a variety of configurations to support specific applications which may include aspects of the application layer 207. The AMC may have various signalling 331 and power connections 339 via the wiring loom 313 to a wide variety of sensor devices. The AMC 317 may connect 332 to the ODB tracker 310. The AMC may connect 333 to the cellular system in-vehicle interface 315. The AMC may connect 335 to the SBD satcom equipment 316.
The architecture is scalable to accommodate multiple enterprise customers, multiple OEM
gateways, multiple web services and a large base of managed devices and assets.
The message handling capacity requirements of the gateway layer 205 are mediated by the natural message transfer capacities of the communications layer 208 networks via the OEM
gateway layer 206.
In this example, the gateway layer 205 is designed to support tens of thousands of assets (for example vehick. ..";.-...3ultaneously. To achieve this requirement, the gateway cri !^.7. built using technologies that power the world's largest Internet websites, such as the Python Django Web framework and the Microsoft SQL Server 2008R2 Database and Reporting Services. The Python Django Web framework is capable of supporting thousands of simultaneous users per second. The Microsoft SQL Server is an Enterprise grade database capable of supporting hundreds of millions of records across complex relational data structures. The gateway may be hosted in any suitable manner, for example it may be hosted on a virtualised Microsoft Windows 2008R2 Server Operating System, facilitating simple and incremental upgrade of underlying hardware as the system grows and evolves.
The gateway layer 205 has an interface 214 to the services layer which in this example is embodied as SQL code for database access and WebAPI's for cloud services. The gateway layer 205 has an interface 217 to the applications layer 207 which is embodied as compiled code running on the gateway layer 205 hardware. The gateway layer 205 has an interface 222 to the OEM gateway layer 206 which is defined by agreements between and the OEM
gateway layer 206 owner/operator, Applications Layer The system may comprise an applications layer 207. The application layer 207 is generally described by Figure 4. Applications may reside wholly at the gateway layer 205 or be distributed between the gateway layer 205 and multiple instances of the AMC
317 or its variants.
The invention may comprise a set of applications which may for example include device configuration 401, connection management 402, tracking 403, driver behaviour 404, association 405, safety 406, and reconciliation 407 with the facility to incorporate additional applications. Furthermore the architecture supports expanding the applications functionality to service future enterprise requirements as they emerge.
Device Configuration An example functionality of the device configuration 401 application is generally described by Figure 5 by which the function is to allow a user of the system to define persons and devices within the system including creation, modification and deletion actions, map device identification (ID) to specific persons and assets, manage ID mapping between the different OEM gateways 206. Instances of OEM gateways 206 do not necessarily maintain or make available the associations between driver ID and communications device equipment/subscriber 10. Different instances of OEM gateways 206 may behave differently in that regard. To facilitate a dual mode cellular/satellite tracking service or a tracking service that may utilise two different SBD satcom systems it is a necessary requirement that cellular tracking data and satellite tracking data can be associated. The device configuration application 401 may perform this function.
In this example. the device configuration application maintains the data in tables in the system database. This data is accessible to other applications within the applications layer 207 Figure 2A: Application Layer Functions running on the gateway 105. Data created, stored and maintained by the device configuration 401 application may be used by the connection management 402 application and the reconciliation 407 application and is available to other applications 207 running on the gateway 105.
Connection Management The functionality of the connection management 402 application is generally described by Figure 6 by which details of the connection status of a defined device is maintained by interaction with the attached OEM gateways. The connection management 402 application:
$ 1. manages the establishment of a connection between the gateway 105 and any OEM
gateways 104:
2. maintains established connections:
3 removes an established connection, 4. maps messages received over an established gateway connection to a device ICI, 2() 5. sends messages over an established gateway connection in a format which the OEM
gateway 206 can accept and process, 6. receives user ID information based on Fob 311 or RDIF Card 303 or other identification means, maps the user ID to a device ID and disseminates the user ID
information to those attached OEM gateways 104 for display on their visualisation platform via method 25 defined in interface agreements.
Furthermore the connection management application 402 supports a least cost routing function. This application may be distributed between the gateway 105 and the instances of the AMC 317 according to design principles that minimise the cost of sending data over the communications layer 208. The choice of route selection is configurable to meet user =30 requirements which may include route preferences, financial cost constraints, data delivery WO 2()16/141411 PCT/AU2016/0000 77 integrity and similar considerations and also takes account of device capabilities for example the propensity of certain cell phones to preferentially choose a WiFi connection noting that this may in fact route to a more costly satellite connection via the AMC 317 even though a viable, lower cost 3G or 4G network connection may be available.
Data created, stored and maintained by the connection management application 402 may be used by the tracking application 403 and is available to other applications 207.
Tracking The functionality of the tracking application 403 is generally described by Figure 7 by which the geographical location of a tracking device is recorded and maintained. In the case where O a device that reports location via an AMC fails to report its location where the failure to report is decided by timer supervision or by other rules of logic embedded within the tracking application a discovery process may be initiated which attempts to locate the device by searching over the active population of AMC ,devices defined previously by an association relationship configuration activity by the association application 405. Where the device 1 5 location is found by the aforementioned search the location is updated and the device is associated with the reporting entity according to the services of the association 405 application. In a case where the device cannot be located during any given instance of a discovery process it is placed on a watch list which may be used in any subsequent invocations of the discovery process or by the reconciliation application 407.
20 The tracking application 403 may receive messages from devices representing activation of a sensor or data recorded by a sensor in which case the message received is interpreted according to message parsing rules embedded within the application and the resultant data or information stored for use by other entities within the application 407 layer and may disseminate selected data and information to attached OEM gateways 104 for display on their 25 visualisation platform.
Association The functionality of the association application 405 is generally described by Figure 8. An hierarchal association is established and maintained between specified devices and logical groups as defined by the enterprise user layer 101 appropriate to their business or 30 operational context. For example in one implementation, an example context is to know the distribution of highly mobile resources and assets deployed in a dynamic firefighting operation possibly grouped as Appliances, strike teams, operational command or similar organisational or geo-located groupings thereby enabling more effective decision making in relation to resources by operational command teams.
In the system architecture 119 example associations may be Appliances whereby a group of personnel equipped with a GPS enabled UHF Pendant 302 is associated with an AMC
installed on a specified vehicle, also called an Appliance in certain contexts. Appliances may be grouped into Strike Teams and Strike Teams associated with specified geographical areas or operational zones, noting that the OEM Gateways and Visualisation platforms support sophisticated geo-fencing capabilities for this as well as other purposes.
Such an association hierarchy may be extended to an arbitrary number of levels within the constraints of the available processing capacity of the gateway 105 and predetermined configuration limits.
The association application 405 is distributed between the gateway 105 and the instances of the AMC 317 according to design principles that minimise the messaging and data transferred between these entities so as to reduce satellite link resource requirements and related operational casts to the users.
In the example the AMC has knowledge of the group of GPS enabled UHF Pendant devices 302 assigned to it. The AMC 317 maintains the connection status of each UHF
Pendant 302 within its association group based on the UHF link connection 320. When it is determined by heuristics embedded in the association 405 application running on the AMC 317 that a UHF
connection 320 to one or more instances of a UHF Pendant 302 has been lost this information is reported to the association 405 application running on the gateway 105 which may subsequently initiate a discovery search. At the same time the subject AMC
317 may periodically check and reconcile the status of all UHF linked UHF Pendant 302 advising the association 405 application running on the gateway 105 of status changes.
In the case where an instance of a UHF Pendant 302 being recognised by two or more AMC's 317, which is possible due to the physical characteristics of the UHF
channel 320, group associations are maintained, in the following order, first as the AMC
317 to which the UHF Pendant 302 is nominally configured, herein referred to as the home group, then if lost to the home group the association will be to the group of the AMC 317 which first reports the discovery of the UHF Pendant 302. At any subsequent time if the UHF Pendant 302 instance is discovered by the home group AMC 317 it will be re-associated with that group.
In one specific instance there are up to six crew members associated with each Appliance ¨
limited to six by the number of seats in the Appliance. Crew members initial assemble at the location where the 4,7.7ance is garaged. At this time each crew member is carrying, e-q14.
individualised UHF Pendant 302 which they activate. The UHF base station 312 detects the active UHF pendants 302 and forwards the details to the AMC 317. It is possible that there is more than one Appliance and crew at the garage site and if this is the case then it is possible that all or most of the UHF pendants 302 are detected by all or most UHF base stations 312, To establish the actual disposition of crew members to Appliances the Association 405 application running on the AMC 317 runs an algorithm that uses position information of the relative locations of the AMC 317 on an Appliance and each UHF Pendant 302 and also time and speed data to validate who is actually riding on an Appliance. In essence, the heuristic logic is that UHF Pendants 302 within approximately 5m of the ACM are likely to be the crew members, then UHF pendants 302 and an ACM 317 moving at the same speed are likely to be on the same Appliance and assessment over a time window improves the integrity of the association.
In one specific instance in the active operational area a crew members may become separated from their Appliance, in this case the crew member may be detected by another UHF base station 312. Where that occurs the information is passed to the AMC
connected to that UHF base station 312 and the AMC retains a record of that contact. This process is generalised to all UHF pendants 302 and AMCs 317. By this means a track of all UHF pendants 302 is continuously updated. The association 405 application running on the gateway 105 may poll AMC's 317 in order to establish or maintain the disposition of UHF
pendants 302. Furthermore the association 405 application running on the gateway 105 may query selected AMC's 317 regarding a specific UHF Pendant 302 by its ID for its location and currently associated Appliance.
In one specific instance in an active operational area where two Appliances are active in close proximity to each other one of these Appliances may suffer a mechanical failure and become unserviceable. Further in this scenario conditions may escalate to the point of becoming an imminent clanger to life necessitating an immediate evacuation. In such a case or similar scenario up to twelve crew members may be required to mount the operational Appliance and make their escape. The UHF base station 312 on the operational Appliance will detect all UHF pendants 302 according to the already described association algorithm thereby supporting rescue actions by providing knowledge of the location and roll call.
The association application 405 design is highly flexible in that it allows an arbitrary definition of the size of groups and the number of levels of association.
Safety The functionality of the safety application 406 is generally described by Figure 9 by which in the example conditions that may reflect the safety of personnel are monitored, maintained and reported. The example supports duress conditions as either signalled by pressing the duress button 301 or 315, a man down condition detected by a UHF Pendant 302 or similarly capable device or by fatigue status determined by a fatigue sensor 309. The safety application 406 sets the safety status of the reporting device ID which is then available to the tracking application 403 which may forward the information to OEM gateways 104 or other visualisation platforms 406 for display and alerting.
Reconciliation The functionality of the reconciliation application 407 is generally described by Figure 10 by which in the example operational groups are retired from active operations to, for example, a staging area. At this time is may be a requirement to verify that all resources and assets that form any given operational group returning from active deployment have returned as expected. The reconciliation application 407 is a particular case of the association application 405 in which all the subject AMC units of the various returned Appliances are interrogated for UHF Pendant 302 connection status. An alert may be created for each missing UHF Pendant 302 unit and also a report may be created detailing the reconciled disposition of all subject resources and assets including any that are missing. The invention allows for UHF Pendant 302 units that have not been nominally assigned to any group to be included in all discovery and reconciliation processes thereby facilitating the management of ad hoc and unplanned changes to the operational resource base.
Driver Behaviour The functionality of the driver behaviour layer 404 application is generally described by Figure 11 by which various data which may include location, fatigue state, acceleration, braking, cornering and speed are sensed and analysed for a variety of driving characteristics according to a set of configurable heuristic rules or process against desired driver behaviours which may include unauthorised area access, swerving, harsh acceleration, harsh braking, harsh cornering and speeding. Furthermore location data may be used to modulate driving behaviour heuristics. Violation of desired driver behaviours are alerted to the driver via in-vehicle indicators which may include lights and audible sounds. A report is created that includes details of the driver behaviour which may be used to create a summary of driver behaviour over periods of time, The driver behaviour layer 404 is distributed between the AMC 317 and the gateway 105 with the AMC 317 responsible for collection of sensor data, analysis of that data for violations, in-vehicle violation presentations and formatting of data and information suitable for transmission and the gateway 105 responsible for storage of the data and information and 5. creation of time based driver behaviour analysis and reporting. As a part of the reporting features the gateway 105 may forward details of driver behaviour violations to the OEM
gateways 104 for immediate presentation.
Communications Layer The system may comprise a communications layer 208 to support connectivity between the device layer 209 and the OEM gateway layer 206, in some embodiments, the invention utilises one or more of a cellular phone network, the Inmarsat M2M network and the Iridium network indicated by interface 218. in any particular instance of the architecture 119 one or more of these communications paths will be available. The selection and mix of communication layer 208 technology is driven by enterprise user layer requirements.
Remote User Layer The remote user layer 210 may comprise personnel, vehicles, plant, equipment or other physical assets that may form part of the enterprise or operation. This layer has an interface 221 to the device layer 210 which are detailed in the description of the device layer 210.
Device Layer The system is comprised of a device layer 209 which is comprised of a set of OEM and designed hardware devices, some running embedded software applications and many of which act as sensors, as illustrated by Figure 3. The set of devices and their interfaces 219 and 220 used in any particular deployment of the invention may vary depending on specific enterprise user layer 201 requirements and may typically include:
1. A device which acts as an interface to sensors and communications equipment forming part of the communications layer 308 which in this embodiment is named the AMC
317..
The AMC 317 is a flexible, low cast computing platform running an operating system with hardened file management to improve operational robustness which in one embodiment may be a Raspberry Pi 2 hardware platform running a modified distribution of the Linux operating system.
2. The AMC may be implemented in a variety of configurations to support specific applications which may include the application layer 207. The AMC 317 may have various signalling 331 and power connections 339 via the wiring loom 313 to a wide variety of sensor devices, The AMC 317 may connect 332 to the ODB tracker 310. The AMC
may connect 333 to the cellular system in-vehicle interface 315. The AMC 317 may connect 335 to the SBD satcom equipment 318.
3. One or more instances of SBD satellite tracking and messaging equipment 318 4. A seatbelt engaged sensor 305 which employs a magnetic field proximity sensing method to detect when the seatbelt tongue and buckle are closer than approximately 5 cm. The detection is inferred to mean that the seat belt is fastened whilst recognising that this may be factually false. The buckle mounted sensor element is connected to the AMC
317 via a wiring loom 313 and discrete wire interface 322. The sensor does not rely on other in-vehicle seatbelt detection equipment or signalling and is fully independent of such equipment.
5. A Vehicle ignition-on sensor 306 which supports battery discharge protection. The vehicle ignition-on sensor 306 is connected to the AMC 317 via a wiring loom 313 and discrete wire interface 323. The AMC inhibits SBD satcom equipment 318 transmissions when the vehicle ignition-on sensor 306 indicates that engine is off.
6. Simple sensors including press buttons, example instances being a duress button 301 20= and a button on the cellular system in-vehicle interface 315.
Activation of the duress button causes a specific distress message handling protocol to be started with the OEM
gateway 206 Figure 2A and visualisation layer 204 Figure 2A of the example architecture 119 Figure 1 which results in high priority visual display of the condition.
Distress signal interfaces 319 and 334 directly connect the distress signal to the SBD satcom equipment 318. lt is noted that the gateway 205 Figure 2A is not involved any distress message handling protocol;
7. A personal tracking device which in this example is a UHF Pendant 302 which connects via a UHF signal 320 to a UHF base station 312, The UHF Pendant 302 and UHF
base station 312 are OEM devices which use unlicensed UHF spectrum as the communications media. The UHF Pendant 302 has a clip 337 to allow attachment to a belt OF other clothing or can be mounted in-vehicle in a custom cradle 337. A
UHF
Pendant 302 features include a button for duress activation, a button for welfare check-in, automatic man-down cigtection and GPS tracking. The UHF base station provides interface 330 to the AMC 317 via the wiring loom 313 and a dedicated distress signal 334 interface for direct connection to SDB satcom equipment 318 The UHF Pendant communicates with the UHF base station 312 using a proprietary protocol and message structures. The UHF base station 312 upon receiving a message from the UHF
pendant formats a message which it passes to the AMC 317 using a set of proprietary protocol and message structures over a 'wired serial interface 330. The AMC 317 processes messages received from the UHF base station 312 based on the message type received.
In the example architecture 119 Figure 1 the AMC 317 may use GPS tracking data to update associations according to the application 207 Figure 2A association process 405 Figure 4. Furthermore the AMC 317 may use the GPS tracking data in messages to the application 207 Figure 2A running on the gateway 205 Figure 2A for storage, processing according to various algorithms and processes which may be running as part of the on the application 207 Figure 2A on the gateway 205 Figure 2A. Furthermore the application 207 Figure 2A on the gateway 205 Figure 2A may forward data derived from UHF
pendant 302 messages to OEM gateways 206 Figure 2A and visualisation layers 204 Figure and the service layer 203 Figure 2A as controlled by the application 207 Figure 2A
running on the gateway 205 Figure 2A;
8. Devices to support driver authentication which in this example may include an RFID card 303 and RFID card reader 304 with an RFID link 342 or a key fob 311 used in association the cellular system in-vehicle interface 315 via a magnetic link 327. The RFID
card 303 and RFID card reader 304 are OEM devices connected via an RFID link 345. The RFID
card 303 may be issued by the enterprise user to personnel as a means of identification (ID) for the purposes of authentication. In the example architecture 119 Figure 1 the RFID
card 303 is used as a means for a driver to activate a connection to the system. Driver ID
details are communicated to the AMC 317 via a wiring loom 313 via interface 331 using interface 321 for the RFD card reader 304 and interface 333 for the cellular system in-vehicle interface 315. The driver details are read by the RFD card reader 304 which passes them to the AMC 317 using a set of proprietary protocol and message structures via a wired USB interface 321. The AMC extracts data fields from the received message and inserts them into a message structure design for efficient transmission over a SBD
satellite channel 335 matching the specific SBD sat= equipment 318 implemented in an instance of the example architecture 119 Figure 1, The Driver ID
authentication function is typically handled in the OEM gateways 206.
ae:=
9. A fatigue sensor 309 that implements algorithms the output of which is an indicator of the state of driver fatigue which is connected to the AMC 317 via a wiring loom 313 and discrete wire interface 326.
10. A Seatbelt engaged sensor 305. The seatbelt engaged sensor 305 is an invention that employs a magnetic field proximity sensing method to detect when the seatbelt tongue and buckle are closer than a magnet mounted on the retractable seat belt comes to approximately 5.3 mm from the seatbelt clasp. The detection of the magnet is inferred to mean that the seat belt is fastened whilst recognising that this may be factually false. The clasp buckle mounted sensor element is connected to the AMC 317 via a discrete wire interface 322. The sensor uniqueness of this invention is that it does not rely on other in-vehicle seatbelt detection equipment or signalling and is fully independent of such equipment.
11. A Vehicle ignition-on sensor 306. To avoid AMC 40 second restart delays which result when power is disconnected from the AMC 317, the power supply 314 may be wired directly to the vehicle battery power circuit by-passing the ignition switch.
Furthermore to avoid draining the vehicle battery power which may result from the SBD sato=
equipment 318 continuing to make transmissions when the vehicle engine is off the vehicle ignition-on sensor 306 is used to determine if the engine is running by sensing the voltage level of the battery. The vehicle ignition-on sensor 306 invention uses a method of 2(1 sensing relatively lower battery voltage to indicate that the vehicle engine is off and hence not actively charging the battery and sensing relatively higher battery voltage to indicate that the battery is being charged and by inference that the engine is running.
The vehicle ignition-on sensor 306 is connected to the AMC 317 via a direct wire interface 323 where engine off is indicated by a logical low signal. The AMC 317 inhibits SBD
sato=
equipment 318 transmissions when the vehicle ignition-on sensor 306 indicates that engine is off;
Furthermore to avoid draining the vehicle battery power which may result from the SBD sato=
equipment 318 continuing to make transmissions when the vehicle engine is off the vehicle ignition-on sensor 306 is used to determine if the engine is running by sensing the voltage level of the battery. The vehicle ignition-on sensor 306 invention uses a method of 2(1 sensing relatively lower battery voltage to indicate that the vehicle engine is off and hence not actively charging the battery and sensing relatively higher battery voltage to indicate that the battery is being charged and by inference that the engine is running.
The vehicle ignition-on sensor 306 is connected to the AMC 317 via a direct wire interface 323 where engine off is indicated by a logical low signal. The AMC 317 inhibits SBD
sato=
equipment 318 transmissions when the vehicle ignition-on sensor 306 indicates that engine is off;
12. Simple sensors including press buttons, example instances being a duress button 301 with interface 319 and a button on the cellular system in-vehicle interface 315.
13. Various lamps/LED lights, instances being LEDs on the Driver Feedback Lamp 307, LEDs on the UHF Pendant 302 and LEDs on the cellular system in-vehicle interface 315. The Driver Feedback Lamp 307 interface to the AMC 317 via a discrete wire interface 324.
14. A Driver feedback buzzer 30a connected to the AMC 317 via a discrete wire interface 325.
15. A fatigue sensor 309. The fatigue sensor 309 is an OEM device_ The fatigue sensor 309 implements algorithms the output of which is an indicator of the state of driver fatigue. The fatigue sensor 309 inter-operates with the AMC 317 via a serial interface 326 whereby the AMC 317 initialises the fatigue sensor 309 with the local time at the AMC 317 location.
Once initialised and operational the fatigue sensor 309 sends fatigue indicator data messages at regular one minute intervals by the AMC 317. The AMC 317 constructs a message containing fatigue data for efficient transmission via the SBD satcom equipment 318 to the gateway 205 Figure 2A. A control is implemented at the AMC 317 to set the rate of transmission of the fatigue messages which may be configured to be less frequent than the rate at which they are received from the fatigue sensor 309. This control enables management of system operational costs related to satellite air-time charges.
Once initialised and operational the fatigue sensor 309 sends fatigue indicator data messages at regular one minute intervals by the AMC 317. The AMC 317 constructs a message containing fatigue data for efficient transmission via the SBD satcom equipment 318 to the gateway 205 Figure 2A. A control is implemented at the AMC 317 to set the rate of transmission of the fatigue messages which may be configured to be less frequent than the rate at which they are received from the fatigue sensor 309. This control enables management of system operational costs related to satellite air-time charges.
16, An ODB Tracker 310 that allows a wireless connection 332 which may be Bluetooth between the vehicle ODB bus and the AMC 317.
17. A key fob 311 used in association the cellular system in-vehicle interface 315 via a magnetic link 327. The key fob 311 and cellular system in-vehicle interface 315 are OEM
devices and fulfil a driver ID authentication function in conjunction with an OEM gateway 206 Figure 2A:
devices and fulfil a driver ID authentication function in conjunction with an OEM gateway 206 Figure 2A:
18. A wiring loom 313 and 331 which may have a multiplicity of implementations.
19. Mechanical fittings 337 of various designs for mounting device hardware to suit specific installation requirements.
20. A power supply 314 suitable for vehicle use. The power supply interface 339 supports both light vehicle 12V systems and heavy vehicle 24V systems.
21. an OEM data interface devices for example the cellular system in-vehicle interface 315,
22. one or more instances of SBE) satellite tracking and messaging equipment 318;
23. A cellular system in-vehicle interface 315 which interfaces to the cellular unit 316 and may also interface to the AMC 317 in certain embodiments,
24. A 3G14G phone cellular unit 316 and related interfaces 336.
25. Smartphone Apps 338 running on a cellular unit 316 which may connect to the AMC 317 via a WiFi link 340 or operate via a cellular network 341.
=
=
26. Srnartphone Apps 338 which may connect to the AMC 317 via a WiFi connection 339 or connect directly via the cellular network 338;
27. Distress signals 319; 334 may connect directly to the SBD satcom equipment 318.
ABBREVIATIONS
AMC Auspace Mobile Computing platform ERP Enterprise Resource Planning loT Internet of Things M2M Machine to IVIachine ODB Object Data Base 0Ervi Original Equipment Manufacturer SBD Short Burst Data UHF Ultra High Frequency
ABBREVIATIONS
AMC Auspace Mobile Computing platform ERP Enterprise Resource Planning loT Internet of Things M2M Machine to IVIachine ODB Object Data Base 0Ervi Original Equipment Manufacturer SBD Short Burst Data UHF Ultra High Frequency
Claims (8)
1. A system for managing a plurality of assets comprising: an enterprise user layer; a presentation layer; a device layer; optionally a remote user layer and optionally one or more of; a visualisation layer, a service layer, an OEM gateway layer, a gateway layer, a communications layer and an applications layer.
2. A computer-implemented system for configuring context-specific management and or tracking of a plurality of assets and / or devices the configurable system comprising; an enterprise user layer; a presentation layer, a device layer; optionally a remote user layer and optionally one or more of: a visualisation layer, a service layer, an OEM
gateway layer, a gateway layer, a communications layer and an applications layer.
gateway layer, a gateway layer, a communications layer and an applications layer.
3. A system according to claim 1 or claim 2 further comprising a computer implemented software application layer that is distributed between physically separate servers.
4. A server comprising an enterprise user layer for corporate operational and data management: a presentation layer to provide at least one data access option to a user; an applications layer for one or more applications; and a gateway layer to provide connectivity with one or more external devices.
5. A computer-implemented system for context-specific management and or tracking of a plurality of assets and / or devices the system comprising an enterprise user layer, a presentation layer, a visualisation layer, a service layer, a communications layer, an applications layer, a gateway layer, a device layer and a remote user layer wherein the system optionally further comprises a plurality of gateway layers which comprise an OEM
gateway layer, a converged data gateway layer and a mobile gateway layer.
gateway layer, a converged data gateway layer and a mobile gateway layer.
6_ A non-transitory computer-readable storage medium storing a computer program, the computer-readable storage medium comprising program instructions for receiving data tom a plurality of assets and program instructions for receiving and executing one or more instructions from an enterprise user layer; and program instructions to present data associated with one or more assets via a presentation layer; and optionally program instructions to execute an application associated with an application layer.
7. A computer implemented method comprising receiving data from a plurality of assets optionally via a gateway layer; receiving and executing one or more instructions from an enterprise user layer; presenting data associated with one or more assets via a presentation layer; and optionally executing an application within an application layer.
8. in an asset or device tracking or management system, a method for tracking or managing a plurality of assets or devices, the method comprising: an act of receiving data from a plurality of assets optionally via a gateway layer; an act of receiving and executing one or more instructions from an enterprise user layer; an act of presenting data associated with one or more assets via a presentation layer: and optionally an act of executing an application within an application layer.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201562131216P | 2015-03-10 | 2015-03-10 | |
| US62/131,216 | 2015-03-10 | ||
| AU2015902485 | 2015-06-26 | ||
| AU2015902485A AU2015902485A0 (en) | 2015-06-26 | Improved Service Oriented System Architecture for Asset Management Networks | |
| PCT/AU2016/000077 WO2016141411A1 (en) | 2015-03-10 | 2016-03-10 | Improved service oriented system architecture for asset management networks |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2979080A1 true CA2979080A1 (en) | 2016-09-15 |
Family
ID=56879804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2979080A Abandoned CA2979080A1 (en) | 2015-03-10 | 2016-03-10 | Improved service oriented system architecture for asset management networks |
Country Status (4)
| Country | Link |
|---|---|
| AU (1) | AU2016228939A1 (en) |
| CA (1) | CA2979080A1 (en) |
| GB (1) | GB2551300A (en) |
| WO (1) | WO2016141411A1 (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190019090A1 (en) * | 2017-07-12 | 2019-01-17 | Accenture Global Solutions Limited | Field services platform |
| CN110311944A (en) * | 2019-04-23 | 2019-10-08 | 浙江互灵物联科技有限公司 | A kind of system and method that illumination control apparatus active is online |
| CN113535208A (en) * | 2021-08-05 | 2021-10-22 | 浙江万朋教育科技股份有限公司 | Method for realizing visual centralized maintenance and updating test application program based on python |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6611755B1 (en) * | 1999-12-19 | 2003-08-26 | Trimble Navigation Ltd. | Vehicle tracking, communication and fleet management system |
-
2016
- 2016-03-10 GB GB1714411.4A patent/GB2551300A/en not_active Withdrawn
- 2016-03-10 AU AU2016228939A patent/AU2016228939A1/en not_active Abandoned
- 2016-03-10 WO PCT/AU2016/000077 patent/WO2016141411A1/en active Application Filing
- 2016-03-10 CA CA2979080A patent/CA2979080A1/en not_active Abandoned
Also Published As
| Publication number | Publication date |
|---|---|
| AU2016228939A1 (en) | 2017-09-28 |
| GB2551300A (en) | 2017-12-13 |
| GB201714411D0 (en) | 2017-10-25 |
| WO2016141411A1 (en) | 2016-09-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10686687B2 (en) | Integrated personal safety and equipment monitoring system | |
| US9712953B2 (en) | Asset monitoring and tracking with a distributed Bluetooth low energy (BTLE) sensor system of heterogeneous sensors over wireless networks | |
| US7091851B2 (en) | Geolocation system-enabled speaker-microphone accessory for radio communication devices | |
| US10893402B2 (en) | Situational awareness systems and methods | |
| US8928483B2 (en) | Automated attendance tracking and event notification | |
| US9107058B2 (en) | Method and apparatus for emergency phone in a vehicle key | |
| US9247408B2 (en) | Interactive emergency information and identification | |
| CN102239709B (en) | Mobile tag local data reporting system | |
| US20040070515A1 (en) | First responder communications system | |
| US20060047543A1 (en) | Electronic emergency response management system with automated rule-based alert notifications and response deployment | |
| US9444929B2 (en) | Mobile device usage activity reporting system and method | |
| CN109901199A (en) | A kind of emergency communication rescue system based on Beidou navigation technology | |
| US20130090964A1 (en) | Time on Site and Point of Interest Tracker with Privacy Block | |
| CA2979080A1 (en) | Improved service oriented system architecture for asset management networks | |
| WO2021039443A1 (en) | Location identification system and location identification method | |
| Rathinam et al. | Bluetooth-based real-time luggage tracking and status updates | |
| JP2019144986A (en) | Lending management device, lending management method, lending management program and lending management system | |
| JP6192983B2 (en) | Emergency notification system, portable communication terminal, and emergency notification method | |
| CA3004501C (en) | Aircraft flight itinerary alerting system | |
| RU105776U1 (en) | SYSTEM OF REMOTE CONTROL OF LOCATION AND MOVEMENT OF THE OBJECT ON THE BASIS OF INFOCOMMUNICATION AND NAVIGATION TECHNOLOGIES | |
| US11279319B2 (en) | Systems and methods for identifying unauthorized vehicle use | |
| US20200320856A1 (en) | Distributed Home Security System And Method Of Responding To An Alert Condition Therefrom | |
| KR102282906B1 (en) | Public Transportation Information Service System | |
| CN105513338A (en) | Internet of vehicle system for company shuttles | |
| JP2016189093A (en) | Information distribution system, sensor node, communication node, information distribution method, and program |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Discontinued |
Effective date: 20220531 |
|
| FZDE | Discontinued |
Effective date: 20220531 |