EARLIEST PRIORITY DATE:

This Application claims priority from a Complete patent application filed in India having Patent Application No. 202021020123, filed on May 13, 2020 and titled “SYSTEM AND METHOD TO KEEP A TRACK OF AN ENTITY”.

FIELD OF INVENTION

Embodiments of a present invention relate to tracking of an entity, and more particularly, to a system and method to keep a track of the entity.

BACKGROUND Tracking of multiple entities involved in multiple events helps people to stay updated with respect to the corresponding event. The multiple events include supply chain management, a marathon, a car race, a bike race, movement and health of animals in farm, jewelry tracking, defense, laundry automation, library system and the like. The multiple entities include a runner, a vehicle, a rider and the like if the event is a marathon or a car race or a bike race, the multiple entities include animals if the event is related to an agriculture and the like. Conventional approach of tracking of such multiple entities belonging to an event could be done manually by using cameras, stop watches, timers and the like. However, the approach is less efficient, inconvenient, less reliable, time consuming as the approach is manual and manual approaches are prone to human errors. There is a plurality of approaches to automate the tracking of the multiple entities in the multiple events.

In one such approach, one or more Radio Frequency Identification (RFID) tags are coupled to the multiple entities to be tracked in an event. There are one or more checkpoints having one or more RFID tag readers installed to read the one or more RFID tags and note the time of arrival of the corresponding one or more RFID tags at the corresponding one or more checkpoints in a checkpoint file. Such approach is feasible if there is good communication network available at the one or more checkpoints as the one or more checkpoints communicate the data captured upon reading the one or more RFID tags to the central data recording station at the time of capture.

However, at remote places where it is difficult for the one or more checkpoints to communicate with the central data recording station, proper capture of the time of arrival would not be possible and hence there is possibility of addition of delay in the time of arrival captured, thereby making the approach less efficient. Further, the system installed at the one or more checkpoints includes antennas, laptop, a reader unit, a battery, and the like which are bulky and heavy. Transporting such system to remote locations and getting back is difficult and time consuming.

Hence, there is a need for an improved system and method to keep a track of an entity which addresses the aforementioned issues.

BRIEF DESCRIPTION

In accordance with one embodiment of the disclosure, a system to keep a track of one or more entities is provided. The system includes one or more processors. The system also includes a data reading subsystem operable by the one or more processors. The data reading subsystem is configured to read tag reading data from one or more tags coupled to the one or more entities upon detection within a pre-defined communication range of one or more tag readers at a plurality of checkpoints. The plurality of checkpoints includes a first checkpoint, one or more intermediate checkpoints and a final checkpoint.

Further, the tag reading data includes a tag identity at each of the plurality of checkpoints, first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint. The system also includes an identity verification subsystem operable by the one or more processors. The identity verification subsystem is configured to verify at each of the plurality of checkpoints, the tag identity of the one or more tags with respective pre-stored tag information from a central database.

Further, the system includes a data writing subsystem operable by the one or more processors. The data writing subsystem is configured to write tag writing data at one or more pre-computed memory locations in each of the one or more tags via one or more tag writers at each of the plurality of checkpoints upon verification of the tag identity of each of the one or more tags. The tag writing data includes first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint.

The data writing subsystem is also configured to write the tag reading data read by the data reading subsystem in a checkpoint file at each of the plurality of checkpoints via one or more checkpoint file managers. The system also includes a checkpoint data verification subsystem operable by the one or more processors. The checkpoint data verification subsystem is configured to verify at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the plurality of checkpoints, to keep the track of the one or more entities.

In accordance with another embodiment, a method for keeping a track of one or more entities is provided. The method includes reading tag reading data from one or more tags coupled to the one or more entities upon detection within a pre-defined communication range of one or more tag readers at a plurality of checkpoints. The plurality of checkpoints includes a first checkpoint, one or more intermediate checkpoints and a final checkpoint. The tag reading data includes a tag identity at each of the plurality of checkpoints, first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint.

Further, the method includes verifying at each of the plurality of checkpoints, the tag identity of the one or more tags with respective pre-stored tag information from a central database at each of the plurality of checkpoints. The method also includes writing tag writing data at one or more pre-computed memory locations in each of the one or more tags via one or more tag writers at each of the plurality of checkpoints upon verification of the tag identity of each of the one or more tags. The tag writing data includes first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint. Further, the method also includes writing the tag reading data read by the data reading subsystem in a checkpoint file at each of the plurality of checkpoints via one or more checkpoint file managers. The method also includes verifying at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the plurality of checkpoints, for keeping the track of the one or more entities.

To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which:

FIG. 1 is a block diagram representation of a system to keep a track of one or more entities in accordance with an embodiment of the present disclosure;

FIG. 2 is a block diagram representation of an exemplary embodiment of a race tracking system to keep a track of one or more riders of FIG. 1 in accordance with an embodiment of the present disclosure;

FIG. 3 is a block diagram of an entity tracking computer or an entity tracking server in accordance with an embodiment of the present disclosure; and

FIG. 4 is a flow chart representing steps involved in a method for keeping a track of one or more entities in accordance with an embodiment of the present disclosure.

Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

DETAILED DESCRIPTION

For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.

Embodiments of the present disclosure relate to a system to keep a track of one or more entities. The system includes one or more processors. The system also includes a data reading subsystem operable by the one or more processors. The data reading subsystem is configured to read tag reading data from one or more tags coupled to the one or more entities upon detection within a pre-defined communication range of one or more tag readers at a plurality of checkpoints. The plurality of checkpoints includes a first checkpoint, one or more intermediate checkpoints and a final checkpoint.

Further, the tag reading data includes a tag identity at each of the plurality of checkpoints, first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint. The system also includes an identity verification subsystem operable by the one or more processors. The identity verification subsystem is configured to verify at each of the plurality of checkpoints, the tag identity of the one or more tags with respective pre-stored tag information from a central database.

Further, the system includes a data writing subsystem operable by the one or more processors. The data writing subsystem is configured to write tag writing data at one or more pre-computed memory locations in each of the one or more tags via one or more tag writers at each of the plurality of checkpoints upon verification of the tag identity of each of the one or more tags. The tag writing data includes first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint.

The data writing subsystem is also configured to write the tag reading data read by the data reading subsystem in a checkpoint file at each of the plurality of checkpoints via one or more checkpoint file managers. The system also includes a checkpoint data verification subsystem operable by the one or more processors. The checkpoint data verification subsystem is configured to verify at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the plurality of checkpoints, to keep the track of the one or more entities.

FIG. 1 is a block diagram representation of a system (10) to keep a track of one or more entities (20) in accordance with an embodiment of the present disclosure. The system (10) includes one or more processors (30). The system (10) also includes a data reading subsystem (40) operable by the one or more processors (30). The data reading subsystem (40) reads tag reading data from one or more tags (50) coupled to the one or more entities (20) upon detection within a pre-defined communication range of one or more tag readers (60) at multiple checkpoints (70). The multiple checkpoints (70) include a first checkpoint, one or more intermediate checkpoints and a final checkpoint. In one embodiment, the multiple checkpoints (70) are separated by one or more pre-determined distances.

Further, the tag reading data includes a tag identity and an event start time at each of the multiple checkpoints (70), first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint. In one embodiment, the one or more tags (50) include one or more Radio Frequency Identification (RFID) tags, one or more Near Field Communication (NFC) tags, and the like. In such embodiment, the one or more tags (50) include a transponder unit, a rectifier unit, a controlling unit and a memory unit.

In one embodiment, the one or more tag readers (60) include one or more RFID tag readers, one or more NFC tag readers and the like. In such embodiment, each of the one or more tag readers (60) include a signal generator unit, a processing unit and a signal receiving/ detecting unit. In one embodiment, the one or more tag readers (60) generate a reading signal having a pre-defined frequency range which the corresponding one or more tag readers (60) radiates in surrounding. In such embodiment, the reading signal radiated travels up to the pre-defined communication range. In one embodiment, when the one or more tags (50) come within the pre defined communication range of the corresponding one or more tag readers (60), the one or more tags (50) receive the reading signal radiated by the one or more tag readers (60) and responds by radiating a response signal.

Further, in such embodiment, upon receiving the response signal, the one or more tag readers (60), read the tag reading data stored in the memory unit of the corresponding one or more tags (50). In such embodiment, the response signal acts as a carrier of the tag reading data stored in the memory unit of the one or more tags (50). In one embodiment, the one or more tags (50) are either one or more passive tags, one or more semi-passive tags or one or more active tags. In such embodiment, the one or more passive tags are powered by the reading signal which the one or more tags (50) receive from the one or more tag readers (60).

The system (10) also includes an identity verification subsystem (80) operable by the one or more processors (30). The identity verification subsystem (80) is operatively coupled to the data reading subsystem (40). The identity verification subsystem (80) verifies at each of the multiple checkpoints (70), the tag identity of the one or more tags (50) with respective pre-stored tag information from a checkpoint database (82) located at each of the multiple checkpoints (70). In one embodiment, the checkpoint database (82) is operatively coupled to the one or more tag readers (60). In one embodiment, the tag identity includes a unique code including a string of characters and a string of numbers. In one exemplary embodiment, the one or more RFID tags store the tag reading data using an Electronic Product Code (EPC) standard. As used herein, the term “EPC” is defined as a syntax for unique identifiers assigned to physical objects, unit loads, locations, or other identifiable entity playing a role in business operations.

In one embodiment, the tag reading data read by the data reading subsystem (40) at one or more of the multiple checkpoints (70) is communicated to a central data recording station (84) via a communication subsystem (86) operable by the one or more processors (30) upon establishment of a connection between one or more of the multiple checkpoints (70) with the central data recording station (84). In such embodiment, the connection between the one or more of the multiple checkpoints (70) and the central data recording station (84) is established upon availability of a communication network. In one embodiment, the central data recording station (84) is communicatively coupled to a central database (88). In such embodiment, the central database (88) includes a local central database or a cloud central database. In one embodiment, the tag reading data read by the data reading subsystem (40) at one or more of the multiple checkpoints (70) is stored in the central database (88). In one embodiment, the central data recording station (84) includes a place including multiple controlling systems and people operating the multiple controlling systems in order to keep the track of multiple events via the one or more tags (50). In one embodiment, the multiple events include a race event, a supply chain management and the like. In one embodiment, at a start of the multiple events, the tag identity and the event start time are stored in the memory unit of the one or more tags (50) at one of one or more pre-computed memory locations. In another embodiment, at the start of the multiple events, the tag identity, the event start time and a start passcode are stored in the memory unit of the one or more tags (50) at one of the one or more pre-computed memory locations. In such embodiment, at the first checkpoint, the identity verification subsystem (80) verifies the start passcode associated to the one or more tags upon reading the tag reading data of the one or more tags.

In one embodiment, the tag reading data read at the first checkpoint includes the tag identity, the event start time and the start passcode. Further, the system (10) includes a data writing subsystem (90) operable by the one or more processors (30). The data writing subsystem (90) is operatively coupled to the identity verification subsystem (80). The data writing subsystem (90) writes tag writing data at the one or more pre computed memory locations in each of the one or more tags (50) via one or more tag writers (100) at each of the multiple checkpoints (70) upon verification of the tag identity of each of the one or more tags (50). The tag writing data includes first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint. In one embodiment, the tag writing data includes a checkpoint location, a checkpoint identifier and a tag arrival time of the one or more tags (50) at each of the multiple checkpoints (70). In one embodiment, the data writing subsystem (90) determines the one or more pre-computed memory locations using a passcode associated to each of the plurality of checkpoints (70). In another embodiment, the one or more pre-computed memory locations in each of the one or more tags (50) is pre defined for each of the multiple checkpoints (70). In such embodiment, the tag reading data read at the first checkpoint includes the tag identity and the event start time.

Furthermore, the data writing subsystem (90) also writes the tag reading data read by the data reading subsystem (40) in a checkpoint file (110) at each of the multiple checkpoints (70) via one or more checkpoint file managers (120). In one embodiment, the first checkpoint data is written by the data writing subsystem (90) at one of the one or more pre-computed memory locations in each of the one or more tags (50) via the one or more tag writers (100) at the first checkpoint upon verification of the tag identity of each of the one or more tags (50). In such embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) at the first checkpoint is computed using the start passcode. In such another embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) at the first checkpoint is pre-defined for the first checkpoint.

In such embodiment, the first checkpoint data includes a first checkpoint location, a first checkpoint identifier and a first checkpoint tag arrival time at which the one or more tags (50) arrive at the first checkpoint. In one embodiment, upon writing the first checkpoint data in the one or more tags (50), the tag reading data changes to the first checkpoint tag data. In one embodiment, at the first checkpoint, the first checkpoint tag data is written by the data writing subsystem (90) in the checkpoint file (110) via the one or more checkpoint file managers (120). In one embodiment, the data writing subsystem (90) generates a first checkpoint passcode depending upon the first checkpoint data. In such embodiment, the first checkpoint tag data includes the tag identity, the event start time, the start passcode and the first checkpoint data. In such another embodiment, the first checkpoint tag data includes the tag identity, the event start time, the start passcode, the first checkpoint data and the first checkpoint passcode.

In one embodiment, the tag reading data read at the one or more intermediate checkpoints includes the one or more intermediate checkpoint tag data. In such embodiment, the first checkpoint tag data is read by the data reading subsystem (40) at a second checkpoint of the one or more intermediate checkpoints via the one or more tag readers (60). In one embodiment, a second checkpoint data of the one or more intermediate checkpoint data is written by the data writing subsystem (90) at one of the one or more pre-computed memory locations in each of the one or more tags (50) via the one or more tag writers (100) at the second checkpoint of the one or more intermediate checkpoints upon verification of the tag identity of each of the one or more tags (50). In such embodiment, the one of the one or more pre-computed memory locations is determined by the data writing subsystem (90) using the first checkpoint passcode. In another embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) at the second checkpoint is pre-defined for the second checkpoint. In yet another embodiment, the data writing subsystem (90) generates a second checkpoint passcode depending upon the second checkpoint data of the one or more intermediate checkpoint data. In such embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) at the second checkpoint is pre-defined for the second checkpoint and along with the second checkpoint data, the second checkpoint passcode is written in the one or more tags (50). In one embodiment, the data writing subsystem (90) does not write over the first checkpoint tag data.

In such embodiment, the second checkpoint data of the one or more intermediate checkpoint data includes a second checkpoint location, a second checkpoint identifier and a second checkpoint tag arrival time at which the one or more tags (50) arrive at the second checkpoint of the one or more intermediate checkpoints. In one embodiment, the data writing subsystem (90) generates one or more intermediate checkpoint passcodes depending upon the one or more intermediate checkpoint data.

In one embodiment, upon writing the second checkpoint data in the one or more tags (50), the tag reading data changes to a second checkpoint tag data of the one or more intermediate checkpoint tag data. In such embodiment, the second checkpoint tag data includes the first checkpoint tag data and the second checkpoint data. In such embodiment, at the second checkpoint of the one or more intermediate checkpoints, the second checkpoint tag data is written by the data writing subsystem (90) in the checkpoint file (110) via the one or more checkpoint file managers (120). In such another embodiment, the second checkpoint tag includes the first checkpoint tag data, the second checkpoint data and the second checkpoint passcode. Further, in one embodiment, the data writing subsystem (50) writes the one or more intermediate checkpoint tag data at the one or more intermediate checkpoints in the checkpoint file (110) via the one or more checkpoint file managers (120).

In another embodiment, the tag reading data read at the final checkpoint includes all of the one or more intermediate checkpoint tag data. In such embodiment, the all of the one or more intermediate checkpoint tag data is read by the data reading subsystem (40) at the final checkpoint via the one or more tag readers (60). In one embodiment, the final checkpoint data is written by the data writing subsystem (90) at one of the one or more pre-computed memory locations in each of the one or more tags (50) via the one or more tag writers (100) at the final checkpoint upon verification of the tag identity of each of the one or more tags (50). In such embodiment, one of the one or more pre-computed memory locations is determined by the data writing subsystem (90) using one of the one or more intermediate checkpoint passcodes. In such another embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) is pre-defined for the final checkpoint. In such another embodiment, the one of the one or more pre-computed memory locations in each of the one or more tags (50) is pre-defined for the final checkpoint and along with the one or more intermediate checkpoint data, the one or more intermediate checkpoint passcodes are also written in the one or more tags (50).

In such embodiment, the final checkpoint data includes a final checkpoint location, a final checkpoint identifier and a final checkpoint tag arrival time at which the one or more tags (50) arrive at the final checkpoint. In one embodiment, upon writing the final checkpoint data in the one or more tags (50), the tag reading data changes to the final checkpoint tag data. In such embodiment, the final checkpoint tag data includes all of the one or more intermediate checkpoint tag data and the final checkpoint data. Further, in one embodiment, the data writing subsystem (90) writes the final checkpoint tag data at the final checkpoint. In such embodiment, at the final checkpoint, the final checkpoint tag data are written by the data writing subsystem (90) in the checkpoint file (110) via the one or more checkpoint file managers (120).

The system (10) also includes a checkpoint data verification subsystem (130) operable by the one or more processors (30). The checkpoint data verification subsystem (130) is operatively coupled to the data writing subsystem (90). The checkpoint data verification subsystem (130) verifies at the final checkpoint, presence of the tag writing data in the respective one or more tags (50) written by the data writing subsystem (90) at each of the multiple checkpoints (70), to keep the track of the one or more entities (20). In one embodiment, the checkpoint data verification subsystem (130) checks for the presence of the tag writing data at each of the one or more pre computed memory locations in the respective one or more tags (50) written by the data writing subsystem (90) at each of the multiple checkpoints (70). In such embodiment, when the checkpoint data verification subsystem (130) detects absence of the tag writing data at any of the one or more pre-computed memory locations in the one or more tags (50), the checkpoint data verification subsystem (130) invalidates the one or more entities and notifies a user about non-passage of the one or more entities (20) coupled to the corresponding one or more tags (50) through the corresponding multiple checkpoints (70) via a notification subsystem (not shown in FIG. 1).

FIG. 2 is a block diagram representation of an exemplary embodiment of a race tracking system (140) to keep a track of one or more riders (150) of FIG. 1 in accordance with an embodiment of the present disclosure. The race tracking system (140) uses one or more ultra-high frequency (UHF) Radio Frequency Identification (RFID) tags (160) coupled to the one or more riders (150) to keep the track of the one or more riders (150). At a start point (170) of a race, a unique bib number is allocated to each of the one or more riders (150). The unique bib number is stored in an initial pre-computed memory location of a memory of the respective one or more UHF RFID tags (160). A race start time and a start passcode are also stored in the initial pre computed memory location of the memory of the respective one or more UHF RFID tags (160). A route (180) to be followed by the one or more riders (150) include three checkpoints (190) on the way, wherein the three checkpoints (190) include a first checkpoint (190a), a second checkpoint (190b) and a final checkpoint (190c). Each of the three checkpoints (190) are separated by a finite distance till the finish line (200).

Further, the three checkpoints (190) have three RFID readers (210) and three RFID writers (220) installed, wherein a first RFID reader (210a) and a first RFID writer (220a) are installed at the first checkpoint (190a), a second RFID reader (210b) and a second RFID writer (220b) are installed at the second checkpoint (190b) and a final RFID reader (210c) and a final RFID writer (220c) are installed at the final checkpoint (190c). When the one or more riders (150) arrive at the first checkpoint (190a), the first RFID reader (210a) reads the unique bib number of each of the one or more riders (150) via a data reading subsystem (230) operable by one or more processors (240). Then, an identity verification subsystem (250) operable by the one or more processors (240), verifies the unique bib number of the respective one or more riders (150) with respective pre-stored tag information from a checkpoint database (255) located at the first checkpoint (190a).

Further, upon verification, the first RFID writer (220a) writes a first checkpoint data including a first checkpoint location and a first checkpoint arrival time in a first pre computed memory location in the memory of the respective one or more UHF RFID tags (160) via a data writing subsystem (270) operable by the one or more processors (240). The first pre-computed memory location is computed using the start passcode by the data writing subsystem (270). The unique bib number, the race start time, the first checkpoint location and the first checkpoint arrival time is termed as a first checkpoint tag data. The data writing subsystem (270) also writes the first checkpoint tag data associated to each of the one or more UHF RFID tags (160) in a checkpoint file (280) via a checkpoint file manager (290) at the first checkpoint (190a). The data writing subsystem (270) generates a first checkpoint passcode depending upon the first checkpoint tag data. As the one or more riders (150) move forward to the second checkpoint (190b), the second RFID reader (210b) reads the unique bib number of each of the one or more riders (150) via the data reading subsystem (230). Then, the identity verification subsystem (250) verifies the unique bib number of the respective one or more riders (150) with the respective pre-stored tag information from the checkpoint database (255) located at the second checkpoint (190b).

Further, upon verification, the second RFID writer (220b) writes a second checkpoint data including a second checkpoint location and a second checkpoint arrival time in a second pre-computed memory location in the memory of the respective one or more UHF RFID tags (160). The second pre-computed memory location is determined using the first checkpoint passcode. The first checkpoint tag data, the second checkpoint location and the second checkpoint arrival time is termed as a second checkpoint tag data. The data writing subsystem (270) also writes the second checkpoint tag data associated to each of the one or more UHF RFID tags (160) in the checkpoint file (280) via the checkpoint file manager (290) at the second checkpoint (190b). The data writing subsystem (270) generates a second checkpoint passcode depending upon the second checkpoint tag data. As the one or more riders (150) move forward to the final checkpoint (190c), the final RFID reader (210c) reads the unique bib number of each of the one or more riders (150) via the data reading subsystem (230). Then, the identity verification subsystem (250) verifies the unique bib number of the respective one or more riders (150) with the respective pre-stored tag information from the checkpoint database (255) located at the final checkpoint (190c).

Further, upon verification, the final RFID writer (220c) writes a final checkpoint data including a final checkpoint location and a final checkpoint arrival time in a final pre computed memory location in the memory of the respective one or more UHF RFID tags (160). The final pre-computed memory location is determined using the second checkpoint passcode. The second checkpoint tag data, the final checkpoint location and the final checkpoint arrival time is termed as a final checkpoint tag data. The data writing subsystem (270) also writes the final checkpoint tag data associated to each of the one or more UHF RFID tags (160) in the checkpoint file (280) via the checkpoint file manager (290) at the final checkpoint. The one or more of the first checkpoint tag data, the second checkpoint tag data and the final checkpoint tag data are communicated to a central data recording station (300) via a communication subsystem (310) operable by the one or more processors (240) upon establishment of a connection between one or more of the three checkpoints (190) with the central data recording station (300). The connection between the one or more of the three checkpoints (190) and the central data recording station (300) is established upon availability of a communication network. The central data recording station (300) is communicatively coupled to a central database (315). The central data recording station (300) is a place which is monitoring the race.

Then, at the final checkpoint (190c), a checkpoint data verification subsystem (320) operable by the one or more processors (240), verifies presence of the first checkpoint data, the second checkpoint data and the final checkpoint data in the respective one or more UHF RFID tags (160) written by the data writing subsystem (270) at each of the three checkpoints (190), to keep the track of the one or more riders (150). If any of the first checkpoint data, the second checkpoint data and the final checkpoint data is detected to be absent at the first pre-computed memory location, the second pre computed memory location and the final pre-computed memory location in the respective one or more UHF RFID tags (160), then a race organiser (330) is notified about non-passage of the corresponding one or more riders (150) through the corresponding three checkpoints (190) via a notification subsystem (340).

Furthermore, the one or more riders (150), the one or more UHF RFID tags (160), the three checkpoints (190), the three RFID readers (210), the three RFID writers (220), the data reading subsystem (230), the one or more processors (240), the identity verification subsystem (250), the checkpoint database (255), the data writing subsystem (270), the checkpoint file (280), the checkpoint file manager (290), the central data recording station (300), the communication subsystem (310), the central database (315) and the checkpoint data verification subsystem (320) are substantially similar to one or more entities (20), one or more tags (50), multiple checkpoints (70), one or more tag readers (60), one or more tag writers (100), a data reading subsystem (40), one or more processors (30), an identity verification subsystem (80), a checkpoint database (82), a data writing subsystem (90), a checkpoint file (110), a checkpoint file manager (120), a central data recording station (84), a communication subsystem (86), a central database (88) and a checkpoint data verification subsystem (130) of FIG. 1.

FIG. 3 is a block diagram of an entity tracking computer or an entity tracking server in accordance with an embodiment of the present disclosure. The entity tracking server (350) includes processor(s) (360), and a memory (370) coupled to a bus (380). As used herein, the processor(s) (360) and the memory (370) are substantially similar to a system (10) of FIG. 1. Here, the memory (370) is located in a local storage device.

The processor(s) (360), as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof.

Computer memory elements may include any suitable memory device(s) for storing data and executable program, such as read only memory, random access memory, erasable programmable read only memory, electrically erasable programmable read only memory, hard drive, removable media drive for handling memory cards and the like. Embodiments of the present subject matter may be implemented in conjunction with program modules, including functions, procedures, data structures, and application programs, for performing tasks, or defining abstract data types or low-level hardware contexts. Executable program stored on any of the above-mentioned storage media may be executable by the processor(s) (360).

The memory (370) includes a plurality of subsystems stored in the form of executable program which instructs the processor(s) (360) to perform method steps illustrated in FIG. 3. The memory (370) has following subsystems: a data reading subsystem (40), an identity verification subsystem (80), a data writing subsystem (90) and a checkpoint data verification subsystem (130).

The data reading subsystem (40) is configured read tag reading data from one or more tags (50) coupled to one or more entities (20) upon detection within a pre-defined communication range of one or more tag readers (60) at a plurality of checkpoints (70), wherein the plurality of checkpoints (70) comprises a first checkpoint, one or more intermediate checkpoints and a final checkpoint. The tag reading data comprises a tag identity at each of the plurality of checkpoints (70), first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint.

The identity verification subsystem (80) is configured to verify at each of the plurality of checkpoints (70), the tag identity of the one or more tags (50) with respective pre stored tag information from a checkpoint database (82). The data writing subsystem (90) is configured to write tag writing data at one or more pre-computed memory locations in each of the one or more tags (50) via one or more tag writers (100) at each of the plurality of checkpoints (70) upon verification of the tag identity of each of the one or more tags (50), wherein the tag writing data comprises first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint.

The data writing subsystem (90) is also configured to write the tag reading data read by the data reading subsystem (40) in a checkpoint file (110) at each of the plurality of checkpoints (70) via one or more checkpoint file managers (120). The checkpoint data verification subsystem (130) is configured to verify at the final checkpoint, presence of the tag writing data in the respective one or more tags (50) written by the data writing subsystem (90) at each of the plurality of checkpoints (70), to keep the track of the one or more entities (20).

FIG. 4 is a flow chart representing steps involved in a method (390) for keeping a track of one or more entities in accordance with an embodiment of the present disclosure. The method (390) includes reading tag reading data from one or more tags coupled to the one or more entities upon detection within a pre-defined communication range of one or more tag readers at multiple checkpoints, wherein the multiple checkpoints includes a first checkpoint, one or more intermediate checkpoints and a final checkpoint in step 400. In one embodiment, reading the tag reading data from the one or more tags coupled to the one or more entities include reading the tag reading data from the one or more tags coupled to the one or more entities by a data reading subsystem.

In one exemplary embodiment, reading the tag reading data from the one or more tags coupled to the one or more entities includes reading the tag reading data such as a tag identity and an event start time at each of the multiple checkpoints, first checkpoint tag data at the first checkpoint, one or more intermediate checkpoint tag data at the one or more intermediate checkpoints and final checkpoint tag data at the final checkpoint. In such embodiment, reading the tag reading data from the one or more tags coupled to the one or more entities includes reading the tag reading data from the one or more tags coupled to the one or more entities, wherein the one or more tags include one or more Radio Frequency Identification (RFID) tags, one or more Near Field Communication (NFC) tags, and the like.

In one embodiment, reading the tag reading data from the one or more tags coupled to the one or more entities upon detection within the pre-defined communication range of the one or more tag readers at the multiple checkpoints include the one or more tag readers including one or more RFID tag readers, one or more NFC tag readers and the like. In one exemplary embodiment, reading the tag reading data from the one or more tags includes communicating the tag reading data to a central data recording station via a communication subsystem.

In such embodiment, communicating the tag reading data to the central data recording station includes communicating the tag reading data to the central data recording station, wherein the central data recording station is being communicatively coupled to a central database. In one embodiment, the central data recording station being communicatively coupled to the central database include the central data recording station being communicatively coupled to the central database, wherein the central database includes a local central database or a cloud central database. In such embodiment, the central data recording station being communicatively coupled to the central database include the central data recording station being communicatively coupled to the central database, wherein the central database is used to store the tag reading data read by the data reading subsystem.

The method (390) also includes verifying at each of the multiple checkpoints, the tag identity of the one or more tags with respective pre-stored tag information from a checkpoint database located at each of the multiple checkpoints in step 410. In one embodiment, verifying at each of the multiple checkpoints, the tag identity of the one or more tags with the respective pre-stored tag information from the checkpoint database located at each of the multiple checkpoints include verifying the tag identity of the one or more tags by an identity verification subsystem. In one embodiment, verifying the tag identity of the one or more tags with the respective pre-stored tag information from the checkpoint database located at each of the multiple checkpoints include verifying the tag identity of the one or more tags with the respective pre-stored tag information from the checkpoint database, wherein the checkpoint database is mechanically coupled to the one or more tag readers. In one embodiment, verifying the tag identity of the one or more tags include verifying the tag identity of the one or more tags, wherein the tag identity includes a unique code including a string of characters and a string of numbers.

Furthermore, the method (390) includes writing tag writing data at one or more pre computed memory locations in each of the one or more tags via one or more tag writers at each of the multiple checkpoints upon verification of the tag identity of each of the one or more tags in step 420. In one embodiment, writing the tag writing data at the one or more pre-computed memory locations in each of the one or more tags via the one or more tag writers at each of the multiple checkpoints include writing the tag writing data at the one or more pre-computed memory locations in each of the one or more tags via the one or more tag writers at each of the multiple checkpoints by a data writing subsystem. In such embodiment, writing the tag writing data includes writing the tag writing data such as first checkpoint data at the first checkpoint, one or more intermediate checkpoint data at the one or more intermediate checkpoints and final checkpoint data at the final checkpoint. In one embodiment, writing the tag writing data at the one or more pre-computed memory locations of the one or more tags includes writing the tag writing data including a checkpoint location or a checkpoint identifier and a tag arrival time of the one or more tags at each of the plurality of checkpoints.

Furthermore, the method (390) also includes writing the tag reading data read by the data reading subsystem in a checkpoint file at each of the multiple checkpoints via one or more checkpoint file managers in step 430. In one embodiment, writing the tag reading data read by the data reading subsystem in the checkpoint file at each of the multiple checkpoints via the one or more checkpoint file managers include writing the tag reading data read by the data reading subsystem in the checkpoint file at each of the multiple checkpoints via the one or more checkpoint file managers by the data writing subsystem.

Furthermore, the method (390) also includes verifying at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the multiple checkpoints, for tracking of the one or more entities in step 440. In one embodiment, verifying at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the multiple checkpoints include verifying at the final checkpoint, presence of the tag writing data in the respective one or more tags written by the data writing subsystem at each of the multiple checkpoints by a checkpoint data verification subsystem.

Various embodiments of the system and method to keep the track of the one or more entities enable the tracking of the one or more entities even at remote places without compromising with actual time of arrival information of the corresponding one or more entities, thereby making the system more efficient, less time consuming and more reliable. Further, the system comprising the one or more tag readers, one or more tag writers and controlling subsystems installed at each of the multiple checkpoints is compact, thereby making transportation of the system to the one or more checkpoints and back feasible and easy.

While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein. The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependant on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.