AU2015101391A4 - Method and systems for monitoring occupancy - Google Patents

Abstract

A method for maintaining a database including records indicating the presence or absence of one or more individuals in a vehicle, wherein each record is uniquely associated with an ID information, including the steps of: receiving a first communication from an event device associated with a vehicle, the first communication including at least one ID information associated with an individual; identifying a corresponding record associated with the ID information within the database; determining an incoming status associated with the ID information; and updating the corresponding record with the incoming status associated with the corresponding ID information, wherein each incoming status corresponds to the presence or absence of the individual on the vehicle associated with the event device. L-I 20a 20b 20c in .rn 1

Description

1 METHOD AND SYSTEMS FOR MONITORING OCCUPANCY FIELD OF THE INVENTION [0001] The invention generally relates to methods and systems for monitoring the presence of people in a vehicle such as in one or more school buses or other vehicles. In particular, the invention utilises near field wireless technology and/or other wireless technologies. BACKGROUND TO THE INVENTION [0002] It is a common occurrence that the attendance of particular individuals should be monitored when travelling by one or more vehicles to various locations. For example, students of a particular school or selection of schools are often transported between their residences and the school(s) using one or more school buses, and it is important to ensure all students are present on the one buses. [0003] Traditionally, a designated person (such as a teacher or driver in the school bus example) is charged with taking a roll-call before the one or more vehicles leave. This enables the designated person to record the presence of all required individuals, and to take action should there be anyone missing. [0004] This traditional method does not readily enable the communication of information regarding the presence of individuals to other interested parties. Another disadvantage is the additional responsibility placed on the designated person. SUMMARY OF THE INVENTION [0005] In light of this, it would be desirable to provide systems, devices, and methods to provide improved automation.

2 [0006] According to a first aspect, there is provided a method for maintaining a database including records indicating the presence or absence of one or more individuals in a vehicle, wherein each record is uniquely associated with an ID information, including the steps of: receiving a first communication from an event device associated with a vehicle, the first communication including at least one ID information, the ID information associated with an individual; identifying a corresponding record associated with the ID information within the database; determining an incoming status associated with the ID information; and updating the corresponding record with the incoming status associated with the corresponding ID information, wherein each incoming status corresponds to the presence or absence of the individual on the vehicle associated with the event device. [0007] Preferably, the first communication is received at least in part via the Internet and/or via a local wireless network. Optionally, the first communication includes vehicle identification information identifying the vehicle associated with the event device. [0008] Preferably, the first communication includes location information associated with the ID information, for example GPS coordinates. Also preferably, the first communication includes two or more ID information, each associated with a different individual. [0009] Optionally, each record includes a pre-existing status. In this case, the step of updating the at least one record may include the steps of: identifying at least one corresponding record having a pre-existing status different to the incoming status associated with the corresponding ID information and updating the identified one or more corresponding records such that the pre-existing status is made the same as the incoming status. Alternatively, or in addition, the step of updating the at least one record includes the steps of: updating each corresponding record such that the pre-existing status is made the same is the incoming status. In another alternative, which may be combined with one or both of the previous alternatives, the step of updating the at least one record includes 3 the steps of: identifying one or more records within the database having a pre existing status indicating the presence of an individual on the vehicle associated with the event device which are not identified as a corresponding record; and updating the corresponding pre-existing status of each of these records to indicate the absence of the corresponding individual on the vehicle associated with the event device. [0010] Preferably, the incoming status associated with the, or each, ID information indicates the presence of the corresponding individual on the vehicle associated with the event device. [0011] The step of updating at least one record with the incoming status may include updating the at least one record to indicate the event device from which the first communication is received. [0012] The method preferably includes the step of providing the, or each, individual with an interface device, wherein each interface is configured to communicate wirelessly with the event device. Optionally, the, or each of the, interface devices are NFC tags, each of which may optionally be selected from: passive NFC tags; and active NFC tags, and wherein the event device is an NFC reader. Alternatively, the, or each of the, interface devices may be Low Energy Bluetooth devices, preferably configured as Low Energy Bluetooth beacons, and the event device may be a Low Energy Bluetooth reader. [0013] The method preferably includes the step of providing a plurality of event devices. Optionally, each event device is a NFC reader or wherein each event device is a Low Energy Bluetooth reader or wherein each event device is selected from one of: a NFC reader; and a Low Energy Bluetooth reader. [0014] The first communication may be received by a server, said server configured for maintaining the database. The server may be further configured for performing the steps of: identifying the corresponding record within the database 4 associated with the ID information; determining the incoming status associated with the ID information; and updating the at least one corresponding record with the incoming status associated with the corresponding ID information. [0015] According to another aspect, there is provided a method of providing information regarding the occupancy of one or more vehicles, including the steps of: maintaining a database according to the first aspect; and providing to a user terminal information derived from the database indicating the occupancy of one or more individuals on one or more vehicles, wherein the occupancy of an individual is information indicating the individual being present or not present on a vehicle. [0016] The information is preferably provided to the user terminal in response to a request received from the user terminal. The user terminal may be associated with a group selected from one or more groups, and the information provided to the user terminal may be at least partly determined based on the group associated with the user terminal. The information provided to the user terminal is optionally one or more of: ID information of one or more students; total number of students on the, or each, vehicle; identification of the vehicle occupied by each student; and the location at which the, or each, student boarded and/or disembarked the or each vehicle. [0017] In embodiments, the server is further configured for providing information regarding the occupancy of one or more vehicles to the user terminal. [0018] According to another aspect of the present invention, there is provided a tracking system, including: a server, configured to maintain a database including records; one or more event devices, each associated with one of one or more vehicles; and one or more interface devices, each associated with one of one or more individuals, wherein the one or more interface devices are configured to communicate wirelessly with an event device, said communication configured to provide to the event device status information indicating a status of the individual associated with the interface device, said status corresponding the 5 individual being present or not present on the vehicle associated with the event device, wherein the one or more event devices are configured to communicate via a network with the server, said network preferably including the Internet and/or a local wireless network, said communication configured to provide one or more status information to the server, and wherein the server is configured to maintain the database by updating the database in response to receiving one or more status information from the one or more event devices, such that the records in the database indicate whether each individual is present or not present on the, or each, vehicle. [0019] The server is preferably configured to implement the method of the first aspect. [0020] The one or more interface devices may each be an NFC tag, each of which may optionally be selected from: passive NFC tags; and active NFC tags, and the one or more event devices may each be an NFC reader. Alternatively, the one or more interface devices may each be a Low Energy Bluetooth device, preferably configured as Low Energy Bluetooth beacons, and the one or more event devices may each be a Low Energy Bluetooth reader. In another alternative, each of the one or more interface devices may be selected from one of: a NFC tag; and a Low Energy Bluetooth device, and each of the one or more event devices may be selected from one of: a NFC read; and a Low Energy Bluetooth reader. [0021] Preferably, the one or more individuals are school students and wherein the one or more vehicles are school buses. [0022] The system preferably further includes: one or more user terminals configured to receive information from the server determined from the records located within the database. Each user terminal is optionally associated with one of one or more groups, and the information received from the server by a user terminal is optionally at least in part determined in dependence on the group 6 associated with the user terminal. The information received by a user terminal may include one or more of: ID information of one or more students; total number of students on the, or each, vehicle; and identification of the vehicle occupied by each student. [0023] Herein, the invention will be described with reference to the transport of students (being individuals) on one or more school buses (being vehicles). It is understood that this is merely one possible environment in which the invention may be implemented, and reference to school bus, school, students, teachers, and other entities should not be construed as limitations. For example, in the context of a school environment, other transport options are envisaged including taxis, vans, watercraft, and aircraft. The invention may also be suitable for use with adults, animals, and/or goods. [0024] The invention may be particularly advantageous, however, when implemented on school buses. School students, especially children, typically require more oversight than adults when being transported between locations. Typically, there can be a number of students per teacher (or other supervisor) which increases the burden on the teachers to account for every student. The invention advantageously allows for students to carry small, relatively inexpensive devices such as (but not necessarily limited to) NFC tags or Low Energy Bluetooth beacons, which are able to interface with the event device(s) to accurately record the presence of the student on the school bus, either automatically or through an action taken by the student, thereby recording the presence of the student on the bus. Both NFC tags and Low Energy Bluetooth beacons are advantageous as they utilise close proximity wireless technology. [0025] Another advantage of the invention is the ability to share the information easily and in a relatively automated manner with interested parties. This can assist, for example, where a plurality of school buses are transporting students together, as it allows for the total number of students present over the plurality of buses to be accurately recorded and shared between teachers and/or drivers located on the individual buses. It can also advantageously provide 7 interested parties, such as parents of the students, with access to necessary information to ensure that the individuals are present on the school bus. BRIEF DESCRIPTION OF THE DRAWINGS [0026] Embodiments of the invention will now be described with reference to the accompanying drawings. It is to be appreciated that the embodiments are given by way of illustration only and the invention is not limited by this illustration. In the drawings: [0027] Figure 1 shows a schematic overview of a tracking system according to an embodiment; [0028] Figure 2 shows vehicles suitable for use with the system; [0029] Figure 3 shows an active mode configuration of an event device and a plurality of interface devices; [0030] Figure 4 shows a passive mode configuration of an event device and a plurality of interface devices; [0031] Figure 5 shows a schematic of an event device communicating with the server; [0032] Figure 6 shows user terminals in communication with the server and associated with different groups; [0033] Figure 7a shows a method for maintaining the database for active mode embodiments; [0034] Figure 7b shows a variation of the method of Figure 7a; and 8 [0035] Figure 8 shows a method for maintaining the database for passive mode embodiments. DESCRIPTION OF PREFERRED EMBODIMENTS [0036] For the purpose of the disclosure herein, a general feature referred to in the figures is labelled with a number. Where it is necessary to distinguish specific features of the general feature, the specific features are labelled with the number of the general feature and a unique letter suffix. Reference can be made to the general feature by omitting the suffix, and one or more specific features by including the suffix. For example, Figure 1 includes groups 20, the specific groups being 20a, 20b, and 20c. [0037] Also for the purpose of the disclosure herein, for convenience, reference may be made interchangeably to "vehicles" and "school buses". Furthermore, reference will be made interchangeably to "individuals" and "students". As previously discussed, such descriptions are intended to assist with illustrating embodiments of the invention, and are not intended to be limiting. [0038] Referring first to Figure 1, there is shown an overview of an exemplary tracking system 10 according to embodiments of the present invention. The tracking system 10 includes a server 12, one or more user terminals 14, and one or more event devices 16. In the embodiments described, each of the one or more user terminals 14 and the one or more event devices 16 is in data communication ("communication") with the server 12. The data communication can be at least in part a network 18 such as the Internet through which the devices communicate. The data communication also includes cellular networks separate from the Internet. Data communication can also operate over a local wireless network, such as a Bluetooth or WiFi network. [0039] Figure 1 depicts the tracking system 10 schematically; it is not intended to limit the technology or devices employed at the server 12, the one or 9 more user terminals 14, and the one or more event devices 16. The one or more user terminals 14 in particular may be wired or wireless devices, and their connections to the network 18 may utilise various technologies and bandwidths. For example, applicable user terminals 14 include (without limitation): PC's with wired (e.g. LAN, cable, ADSL, dial-up) or wireless (e.g. WLAN, cellular) connections; and wireless portable/handheld devices such as PDA's or mobile/cellular telephones. The protocols and interfaces between the user terminals 14 and the server 12 may also vary according to available technologies, and include (again without limitation): wired TCP/IP (Internet) protocols; WiFi; Bluetooth; GPRS, WAP, 3G and/or 4G protocols (for handheld/cellular devices); and/or proprietary communications protocols. Typically, the one or more event devices 16 employ wireless communication technologies, though it can be that the wireless communication technology is in combination with wired communication technologies. [0040] The server 12 can be a single device or a plurality of interconnected devices, and includes at least one processor as well as a database, which would typically be stored on a secondary storage device of the server 12, such as one or more hard disk drives. Server 12 further includes at least one storage medium, typically being a suitable type of memory, such as random access memory, for containing program instructions and transient data related to the implementation of the invention as well as other necessary functions of the server 12. In particular, the memory contains a body of program instructions. [0041] In the embodiments described herein, the server 12 provides multiple functions. It is understood that the functions described could in fact be implemented on separate servers 12 which are in communication with one another. It is also understood that the functions could be implemented on a single server 12 configured to provide virtual environments for each function. [0042] It should be appreciated that the hardware used to embodiments of the invention may be conventional in nature or specifically designed for the purpose. The hardware shown in Figure 1 is merely one possible embodiment and any 10 other suitable structure may be utilised. For the disclosure herein, it will be assumed that the one or more event devices 16 are mobile phones (for example, so-called "smartphones"), either on their own or combined with suitable accessories such as accessories providing NFC or Bluetooth capabilities for the phones. Another possible implementation utilises hardware specifically prepared to implement the functionality of the event devices 16. [0043] Figure 1 shows three different user groups 20a, 20b, 20c, each user group 20 associated with at least one user terminal 14. The user groups 18 are distinguished by the type of information made available to them by the server 12. Each user group 20 is shown for the purpose of illustration as comprising a number of different types of user terminal 14. In practice, each user group 20 comprises one or more user terminals 14 which can be selected from any suitable type of device. A user terminal 14 can be associated with a particular group 20 based on information relating to a user of the user terminal 14 (e.g. user identifying information such as a username and password), in which case user terminals 14 are assigned to particular groups 20 dynamically. Alternatively, or in combination, user terminals 14 can be preconfigured to be associated with a particular group 20. This may be particularly suitable where a user terminal 14 corresponds to a permanent device of the tracking system 10, such as where a user terminal 14 is implemented on the same hardware as the server 12 or is permanently affixed to a vehicle. [0044] The server 12 can be implemented within the same hardware as a user terminal 14 and/or an event device 16. Similarly, it an event device 16 can be implemented within the same hardware as a user terminal 14. Where the same hardware implements multiple components of the tracking system 10, it is envisaged that a user can select between the different components, for example by activating a different graphical user interface (GUI) for each component. It is also envisaged that a user can interact with the different components within the same GUI.

11 [0045] Referring to Figure 2, the event devices 16 are associated with vehicles 22, for example school buses. The tracking system 10 provides for one or more users to monitor the identities of individuals entering the, or each, vehicle 22 and/or the identities of individuals present within the, or each, vehicle 22 and optionally the identities of individuals exiting the, or each, vehicle 22. [0046] Each school bus 22 is associated with an event device 16 (optionally, there may be more than one event device 16 associated with a school bus 22, for example at entrance(s)/exit(s) of the school bus 22). The event device 16 can be permanently associated with the school bus 22, for example by being affixed to a support of the school bus 22. Alternatively, the event device 16 can be temporarily associated with the school bus 22, which may be preferable if the school bus 22 is also used for other purposes. In this case, the event device 16 includes functionality such that a user can selectively associate the event device 16 with specific school buses 22. [0047] Referring to Figures 3 and 4, the one or more event devices 16 are associated with a school bus 22. The one or more event devices 16 according to this embodiment are configured to determine the presence of students on the school bus 22. Each student is provided with an interface device 24, which is configured to interact with an event device 16 by communicating data stored on the interface device 24 to the event device 16. At least a portion of the data communicated is unique ID information associated with the interface device 24 (and therefore, with the student provided with the interface device 24). [0048] In the embodiment shown in Figure 3, the students are required to "touch on", that is, undertake an action to cause their interface device 24 to communicate with the event device 16. This embodiment is referred to as an active mode configuration, as each student is required to undertake said action. [0049] According to a particular implementation of this embodiment, the one or more event devices 16 are NFC readers and the one or more interface devices 12 24 are NFC tags or NFC capable electronic devices (such as an NFC enabled smartphone). Specifically shown in Figure 3 is an NFC capable smartphone 24a, an NFC wristband 24b, and an NFC card 24c. The NFC wristband 24b and NFC card 24c are passive devices, whereas the NFC capable smartphone 24a is an active NFC device. An advantage of using an NFC wristband 24b and/or NFC card 24c is that these are typically of low cost and may therefore be provided by the operator of the tracking system 10 or an entity utilising such a tracking system 10 (such as a school). Herein, the term "NFC tag" can include both passive and active NFC devices. [0050] According to this implementation, the "touch on" action corresponds to the student placing their interface device 24 in close proximity to the event device 16 until the event device 16 has successfully wirelessly read the content of the NFC tag. [0051] After an event device 16 has obtained the ID information from an interface device 24, the event device 16 is configured to communicate with the server 12. The event device 16 can be configured to communicate with the server 12 subsequent to each interaction event. Alternatively, the event device 16 can be configured to store the content (at least the ID information) obtained from one or more interface devices 24 until a predetermined condition is met. Once this predetermined condition is met, the event device 16 is configured to communicate with the server 12. Example predetermined conditions are the closing of the school bus doors, or the initial movement of the school bus. [0052] According to an embodiment (such as shown in Figure 2), the tracking system 10 includes a plurality of school buses 22. In this embodiment, the event device(s) 14 are configured to not only communicate the ID information to the server 12, but also information identifying the particular school bus 20 in which the student is present.

13 [0053] Optionally, according to this embodiment, the students are required to "touch off" from the school bus 22. This typically is required at the end of a journey, that is, when the student is dropped off at their destination. The "touch off" event can be identical to the "touch on" event already described, except that is some cases the event device 16 may be different (for example, where the school bus 22 has different doors for entering and exiting the school bus 22). The purpose of the "touch off" event is to enable the server 12 to be updated to indicate the student leaving the school bus 22. [0054] Also optionally, the event device(s) 14 are configured to communicate location information associated with the ID information. This location information includes the location (e.g. GPS coordinates) of the school bus 22 when the "touch on" or "touch off" event occurred. [0055] According to another embodiment, as shown in Figure 4, the event device 16 is configured to periodically communicate with the one or more interface devices 24, which can be referred to as the event device 16 "polling" the one or interface devices 24. This embodiment is referred to as a passive mode configuration, as each student is not required to undertake a particular action (other than having in their possession an interface device 24). [0056] Polling corresponds to the event device 16 wirelessly communicating with the, or each, interface device 24 (either sequentially, simultaneously, or according do another suitable ordering) in order to determine the presence of the interface device 24 within the school bus. The event device 16 and interface device(s) 24 of Figure 4 should be configured to allow for communication over a distance comparable to the size of the vehicle in question. The, or each, interface device 24 is configured to at least provide unique ID information associated with the interface device 24 to the event device 16. [0057] In one implementation of this embodiment, the interface device(s) 24 are relatively small and long lasting Bluetooth Low Energy "beacons", configured 14 to periodically send out a signal which is detectable by an event device 16. This signal includes at least the unique ID information associated with the interface device 24. Bluetooth Low Energy is suitable to provide for communication over distances commonly found in vehicles, in particular school buses. Typically the period will be selected to maximise the resolution of the tracking system 10 while minimising the power usage of the beacon. Resolution corresponds to the accuracy of the data on the server 12. For example, a suitable resolution may be 5 minutes. In this implementation, the event device 16 is only required to receive signals from the interface device(s) 24 rather than engaging in two-way communications, which can minimise power use by the interface device(s) 24. [0058] In another implementation, the interface device(s) 24 are configured for active two-way communication with the event device 16. This may be useful where information is required to be stored on the interface device(s) 24, such as recording the time for which the student was on the school bus 20. [0059] In either implementation, the event device 16 receives from the interface device 24, via a wireless connection, the unique ID information associated with the student (via the student's association with the interface device 24). The event device 16 then provides this identifying information to the server 12, as previously described with reference to the embodiment of Figure 3. The event device 16 can communicate continuously with the server 12 such that the server 12 receives the ID information associated with each individual interface device 24 immediately after the event device 16 receives it, or in batches (e.g. at predetermined intervals, all collected IDs are communicated to the server 12). When utilising predetermined intervals, the predetermined interval should be selected to allow for sufficient resolution of the presence of the student on the school bus 22. [0060] A schematic representation of the communication between the event device 16 and the server 12 is shown in Figure 5. The example shown in Figure 5 is applicable according to both embodiments previously described with reference to Figures 3 and 4. As the school bus 22 is mobile, it is preferred that such 15 communication is wireless, and according to the present embodiment the communication utilises wireless mobile data technology, such as 3G or 4G mobile data. In an alternative embodiment, the server 12 and event device(s) 16 are in wireless and/or wired communication over a local network, such as a WiFi or Bluetooth network, which does not require an Internet connection. The event device 16 is therefore shown in wireless communication with a mobile station 26, which allows for data to be transferred between the event device 16 and the server 12 via the Internet 18. It is possible for other wireless communication technologies to be utilised in addition to, or as an alternative to, the mobile technologies to which previous reference has been made. [0061] The event device 16 is configured to communicate at least the ID information obtained from the one or more interface devices 24 to the server 12. The server 12 stores this information in a database accessible by the server 12. In this way, the server 12 maintains a record of individuals having entered the school bus 22 and/or individuals who are currently present on the school bus 22 (that is, the server maintains a status associated with each student). An embodiment is envisaged wherein the ID information is modified in some manner by the event device 16, for example by changing the data format. [0062] Referring to Figure 6, the server 12 is accessible by one or more user terminals 14. Typically, the user terminals 14 will access the server 12 via the Internet and/or another network (such as a local wireless and/or wired network), though it may be the case that the server 12 can be accessed directly, for example where the device providing the server 12 functionality is also a user terminal 14, or in another suitable manner. For the purposes of illustration, the user terminals 14 are shown in direct communication with the server 12. As previously described, the user terminals 14 are arranged into groups 20. For ease of illustration, Figure 6 shows one user terminal 14 per group 20, however it is understood each group 20 may include one or more user terminals 14. It is also understood that different embodiments may utilise one or more groups 20, as opposed to the three shown in the figure (one group can be considered equivalent to an embodiment with no groups 20).

16 [0063] The user terminals 14 are configured to receive information regarding the presence of individuals on the school bus 22 from the server 12, usually in response to a request by the user terminal 14 to the server 12 for said information. The information can include information identifying the particular school bus 22 on which the, or each, student is present. The tracking system 10 advantageously includes one or more user terminals 14 implemented on smartphones, thereby providing a convenient portable device for operation by the user(s). [0064] The particular information provided to each user terminal 14 is determined by the group 20 to which the user terminal 14 belongs. In this sense, each group 20 corresponds to a "user profile". The server 12 can be configured to maintain records for each user terminal 14 indicating the group 20 to which the user terminal 14 belongs. Each user terminal 14 is typically operated by one or more users. It can be a property of the user which determines the group 20 of the user terminal 14 (this is particularly useful where the user terminal 14 is a temporary user terminal 14, for example a publically accessible computer). Alternatively, or in combination, the user terminal 14 is permanently associated with a particular group 20 (for example, where the user terminal 14 is a device fixed within a school bus 22 such as in the driver's compartment). [0065] According to an embodiment, one or more users are system administrators who are enabled to determine the number of groups 20 of the tracking system 10 and/or the group 20 to which each user terminal 14 belongs and/or the preconfigured information to be presented to members of the groups 20. [0066] In an example, the first group 20a corresponds to drivers of the one or more school buses 22, the second group 20b corresponds to the teachers responsible for the students, and the third group 20c corresponds to the parents/caregivers (herein parents) of each student. The information to be presented to user terminals 14 of each group is preconfigured based on the requirements of the tracking system 10.

17 [0067] In this example, the first group 20a is only provided with a total (or sum) of the number of students on the school bus 22 (or each school bus 22), and is explicitly not provided with identifying information of each student. The second group 20b is provided with both the number of students present on the school bus 22 (or each school bus 22), as well as identifying information on each student (e.g. student name and/or ID) and optionally identifying on which school bus 22 each student is located. Finally, the third group 20c is only provided with information regarding the particular student to which they are associated (e.g. the parent's particular child), which typically will include identifying information on that student. In this way, the provision of groups 20 allows a system administrator to limit or select the information provided to different users (via their user terminal 14) to that information that is required. It is envisaged that the information provided to the different groups 20 can be predetermined (for example, by a system administrator) and is not limited to the example described. [0068] When a student completes a journey on a school bus 22, the database of the server 12 is updated to indicate that the student is no longer present on the school bus 22. In this way, the information communicated to user terminals 14 from the sever 12 accurately represents (in some implementations, the accuracy is limited by a predetermined resolution) the current student occupancy of the one or more school buses 22. Advantageously, real-time or at least near-real time information is in this manner available on the occupancy of the one or more school buses 22. [0069] The following embodiments may be implemented separately or in combination as necessary. [0070] In one embodiment, a user, for example a bus driver or teacher, can be provided with the ability to manually instruct the server 12 to make the update. This may be particularly useful where a collection of students exit the school bus 22 simultaneously (an example would be where the students arrive at a common destination such as when on a field trip), and functionality may be provided for the 18 user to utilise a user terminal 20 to make a bulk update to the server 12 (for example, by selecting a "clear all" function). [0071] In another embodiment, the student is required to undertake a "touch off" action as previously described. Where the interface device 24 is an NFC tag, this would involve holding the NFC tag against an event device 14 configured to record exiting of students from the school bus 20 causing the relevant data of the NFC tag to be read by the event device 14. The event device 14 then communicates this relevant data to the server 12, optionally with additional information indicating that the student is exiting the school bus 20. The server 12 is then configured to update the database accordingly. [0072] Where the event device 14 is configured for polling the one or more interface devices 24, an embodiment automatically determines when a student has left the school bus 20. This is either determined by an event device 14 or the server 12, and results from an interface device 24 no longer being detected by the event device 14. This embodiment may be particularly advantageous where it is desirable to minimise the risk of human error resulting in a student incorrectly being recorded as having left the school bus 20 or recorded as still being on the school bus 20. [0073] Referring now to Figures 7a and 7b, a method according to an embodiment for maintaining a database on the server 12 of students present on one or more school buses 22 is shown, which may be particularly useful to active mode embodiments (see Figure 3). [0074] The server 12 waits to receive a communication from an event device 16 at standby step 50. Once a communication is received, the server 12 identifies a record in the database corresponding to the ID information at identification step 52. Where ID information associated with more than one interface device 24 is received (e.g. where the event device 16 is configured for periodic communication), the server 12 identifies a record associated with each interface 19 device 24. The server 12 then updates the, or each, record to indicate that the associated student is on-board a school bus 22, which typical includes providing information identifying the particular school bus 22 (which has previously been associated with the event device 16 presently communicating with the server 12, at update step 54. In this embodiment, the status of each student associated with received ID information is determined to be on-board. [0075] Optionally, the record may be updated with additional information such as the time the student entered the school bus 22 (which may be provided by the event device 16) and/or the time at which the server 12 received the communication from the event device 16. Other optional information is the location of the event device 16, which may correspond to GPS coordinates determined by the event device 16 (where the event device 16 is associated with a GPS receiver) included within the communication. The record can also updated with information identifying the particular event device 16 which provided the communication to the server 12. [0076] Figure 7b shows a variation to the method of Figure 7a. In this method, a further step is provided, in this example after the identification step 52 and before the update step 54. Status check step 56 corresponds to the server 12 determining the status of the, or each, student, that is, whether the, or each, student has boarded (and therefore is now on-board) or exited (and is therefore now not on-board) the school bus 22. In one embodiment, the status check step 56 corresponds to the server 12 determining from information provided by the event device 16 as to whether the student has boarded or exited the school bus 22. In another embodiment, the server 12 toggles the status of the student. In this case, if the record associated with the student current indicates the student as not being present on the school bus 22, it is changed by the server 12 to indicate the presence of the student. Likewise, if the record current indicates the presence of the student on the school bus 22, it is changed by the server 12 to indicate the absence of the student on the school bus 22.

20 [0077] Referring now to Figure 8, a method according to an embodiment for maintaining a database on the server 12 of students present on one or more school buses 22 is shown, which may be particularly useful to passive mode embodiments (see Figure 4). [0078] Similar to the method of Figures 7a and 7b, the server 12 initially waiting to receive a communication from an event device 16 at standby step 60. Once a communication is received, the server 12 identifies a record in the database corresponding to the ID information at identification step 62. Where ID information associated with more than one interface device 24 is received (e.g. where the event device 16 is configured for periodic communication), the server 12 identifies a record associated with each interface device 24. The, or each, record is then checked to determine whether the record currently indicates the presence of the student on the school bus 22 (that is, the status of the student is on-board). If not, the record is updated at update step 64 to indicate the presence of the student on the school bus 22. Each record can also optionally be updated similar to described with reference to Figure 7a at this step 64. [0079] The server 12 also then checks for records in the database which were not identified at identification step 62 which currently indicate the presence of a student on the particular school bus 22 associated with the event device 16 at maintenance step 66. These records correspond to students who have left the school bus 22, and are therefore updated to indicate that the students are not located on the school bus 22. In this way, the server 12 maintains the status of each student (i.e. whether the student is located on-board a school bus 22 or not) in the database. [0080] The methods described with reference to Figures 7a, 7b, and 8 allow the server 12 to provide up to date information (advantageously real-time or at least near real-time) to the one or more user terminals 14.

21 [0081] Further modifications and improvements may be made without departing from the scope of the present invention. In particular, the various alternative embodiments described herein can be used separately or in combination, for example it is envisaged that the tracking system 10 can include both active interface devices 24 (see Figure 3) and passive interface devices 24 (see Figure 4). This may be useful where students are provided the option of which type of interface device 24 to have, or where one type of interface device 24 is a temporary (e.g. visitor) device.

Claims (5)

1. A method for maintaining a database including records indicating the presence or absence of one or more individuals in a vehicle, wherein each record is uniquely associated with an ID information, including the steps of: receiving a first communication from an event device associated with a vehicle, the first communication including at least one ID information associated with an individual; identifying a corresponding record associated with the ID information within the database; determining an incoming status associated with the ID information; and updating the corresponding record with the incoming status associated with the corresponding ID information, wherein each incoming status corresponds to the presence or absence of the individual on the vehicle associated with the event device.

2. The method of claim 1, wherein the first communication includes vehicle identification information identifying the vehicle associated with the event device; or location information associated with the ID information, for example GPS coordinates; or two or more ID information, each associated with a different individual.

3. The method of claim 1 or 2, wherein each record includes a pre-existing status, and wherein the step of updating the at least one record includes the steps of: identifying at least one corresponding record having a pre-existing status different to the incoming status associated with the corresponding ID information and updating the identified one or more corresponding records such that the pre existing status is made the same as the incoming status; or updating each corresponding record such that the pre-existing status is made the same is the incoming status; or 23 identifying one or more records within the database having a pre-existing status indicating the presence of an individual on the vehicle associated with the event device which are not identified as a corresponding record, and updating the corresponding pre-existing status of each of these records to indicate the absence of the corresponding individual on the vehicle associated with the event device.

4. A method of providing information regarding the occupancy of one or more vehicles, including the steps of: maintaining a database according to the method of any one of the previous claims; and providing to a user terminal information derived from the database indicating the occupancy of one or more individuals on one or more vehicles, wherein the occupancy of an individual is information indicating the individual being present or not present on a vehicle.

5. A tracking system, including: a server, configured to maintain a database including records; one or more event devices, each associated with one of one or more vehicles; and one or more interface devices, each associated with one of one or more individuals, wherein the one or more interface devices are configured to communicate wirelessly with an event device, said communication configured to provide to the event device status information indicating a status of the individual associated with the interface device, said status corresponding the individual being present or not present on the vehicle associated with the event device, wherein the one or more event devices are configured to communicate via a network with the server, said network preferably including the Internet and/or a local wireless network, said communication configured to provide one or more status information to the server, and wherein the server is configured to maintain the database by updating the database in response to receiving one or more status information from the one or 24 more event devices, such that the records in the database indicate whether each individual is present or not present on the, or each, vehicle. BIGSMS PTY LTD WATERMARK PATENT AND TRADE MARKS ATTORNEYS UIP1 51 OAUOO