Touchpoint device

Abstract

Touchpoint devices that are installed at mass transit locations such as airports and allow users to take actions related to their travel. It is desirable to enable touchpoint devices (including self-service touchpoint devices) to interact with users using a mobile device enabling the mobile device to execute various functions required for the touchpoint device. There may be systems of such touchpoint devices, location finding systems that can be incorporated in or used with such touchpoint devices and a mobile application for interacting with such touchpoint devices.

Description

TOUCHPOINT DEVICEFIELD OF THE INVENTION

[0001] The present invention relates generally to touchpoint devices that are installed at mass transit locations such as airports and allow users to take actions related to their travel. More specifically, the present invention relates to touchpoint devices (including self-service touchpoint devices) with which users interact using a mobile device. The present invention also relates to systems of such touchpoint devices, location finding systems that can be incorporated in or used with such touchpoint devices and to a mobile application for interacting with such touchpoint devices.BACKGROUND TO THE INVENTION

[0002] There has been a move in recent years for airlines to put in place infrastructure and processes that allow users to more efficiently perform travel- related actions, such as check-in, bag drop and identity authentication. For example, airlines commonly allow users to check into a flight away from the airport using the airline’s website or mobile app. In the airport environment, airlines are increasingly providing self-service facilities that allow users to perform actions such as check-in, registering and weighing baggage, printing baggage tags, dropping baggage into the baggage handling system, undertaking identity verification and transiting from one area of the airport to another. These self- service facilities can take the form of stations or kiosks that include embedded computer hardware and a (typically touchscreen) display through which the user interacts to perform the relevant action. Depending on the service that the facility provides, the station or kiosk typically also includes peripheral hardware such as printers, scanners, scales for weighing baggage and cameras.

[0003] While recent touchpoint devices have undoubtedly streamlined various aspects of the user experience at the airport, interacting with touchpoints can still be somewhat complex and inefficient for the user. For example, users are still required to interact with multiple user interfaces on the displays of multipletouchpoint devices. The present invention aims to provide a touchpoint devices that provide a more streamlined experience for the user at the airport.

[0004] Any discussion of documents, devices, acts or knowledge in this specification is included to explain the context of the invention. It should not be taken as an admission that any of the material formed part of the prior art base or the common general knowledge in the relevant art on or before the priority date of the claims herein.SUMMARY OF THE INVENTION

[0005] According to a first aspect of the present invention, there is provided a touchpoint device for performing a touchpoint action at a travel location, the touchpoint device comprising: a location finding system configured to determine whether a mobile device is located in a target region in proximity to the touchpoint device; a network interface for establishing an operative network connection with a touchpoint service operating on network infrastructure; and a processor and computer readable medium storing computer executable instructions, which when executed by the processor cause the touchpoint device to: operate the location finding system to locate a mobile device in the target region; upon locating a mobile device in the target region, communicating a touchpoint action session message to the located mobile device, the touchpoint action session message comprising session instructions to an application executing on the located mobile device to establish a touchpoint action session with the touchpoint service.

[0006] The present invention, at least in preferred embodiments, provides a touchpoint device that provides a more streamlined experience for the user to perform touchpoint actions. In particular, touchpoint devices in accordance with embodiments of the present invention are equipped with a location finding system for locating mobile devices in local proximity to the touchpoint device, and are also in operative network connection with a touchpoint service hosted on local or remote network infrastructure. Touchpoint devices in accordance with embodiments of the present invention also include computer programs that causemobile devices that are located by the location finding system to establish a touchpoint action session with the same touchpoint service.

[0007] In some embodiments, the computer executable instructions further cause the touchpoint device to receive a touchpoint action message from the touchpoint service, the touchpoint action message comprising a touchpoint action session token assigned to the touchpoint action session.

[0008] The touchpoint action message may further comprise a travel identifier received by the touchpoint service during the touchpoint session, which in some embodiments comprises a scan of a boarding pass.

[0009] Preferably, the application executing on the located mobile device communicates touchpoint action session data to the touchpoint service during the touchpoint action session. The computer executable instructions in some embodiments further cause the touchpoint device to receive a touchpoint control message indicating whether the holder of the mobile device is permitted to perform a touchpoint action, the touchpoint service constructing the touchpoint control message by processing the touchpoint action session data.

[0010] The touchpoint service may construct the touchpoint control message by processing a time series of locations of the mobile device relative to the touchpoint device. In some embodiments, the touchpoint action session data comprises a time series of signal strength measurements made by the mobile device of location signals received from the touchpoint device, the touchpoint service computing the time series of locations from the time series of signal strength measurements.

[0011] Preferably, the touchpoint service constructs an anomaly message and communicates the anomaly message to the touchpoint device in the event that the time series of locations indicates an anomalous behaviour of the mobile device.

[0012] According to some embodiments, the touchpoint action session data comprises personalisation data pertaining to the holder of the mobile device, the computer executable instructions further causing the touchpoint device to receive a personalisation message based on the personalisation data, the touchpoint device utilising the personalisation message to assist the holder of the mobile device to perform a touchpoint action on the touchpoint device.

[0013] According to another aspect of the present invention, there is provided a computer readable medium storing computer executable instructions which when executed by a processor of a mobile device cause the mobile device to: receive a location signal from a touchpoint device having a location finding system; and establish a touchpoint action session with a touchpoint service operating on network infrastructure.

[0014] Preferably, the computer executable instructions further cause the mobile device to communicate a touchpoint action message to the touchpoint service, the touchpoint action message comprising a touchpoint action session token assigned to the touchpoint action session. The touchpoint action message may further comprise a travel identifier, which can comprise a scan of a boarding pass.

[0015] In some embodiments, the computer executable instructions further cause the mobile device to communicate touchpoint action session data to the touchpoint service during the touchpoint action session. The touchpoint action session data may comprise a time series of signal strength measurements made by the mobile device of location signals received from the touchpoint device.

[0016] The touchpoint action session data may also comprise personalisation data pertaining to the holder of the mobile device.

[0017] According to another aspect of the present invention, there is provided a touchpoint device for performing a touchpoint action at a travel location, thetouchpoint device comprising: a location finding system configured to determine whether a mobile device is located in a target region in proximity to the touchpoint device; and a processor and computer readable medium storing computer executable instructions, which when executed by the processor cause the processor to: establish a connection with a located mobile device; and launch a journey management application on the located mobile device, the journey management application: interrogating the located mobile device to identify any touchpoint data records previously communicated to the located mobile device; and utilising an identified touchpoint data record to display a user interface on the located mobile device that assists a user of the located mobile device to perform the touchpoint action.

[0018] The present invention, at least in preferred embodiments, enhances the security of passenger management flow by maintaining oversight and control over the particular touchpoint devices that are assigned to users. For example, the present invention substantially eliminates the scenario of a rogue third party impersonating a traveller at a touchpoint device.

[0019] The instructions may further cause the touchpoint device or the journey management application to communicate an action status message to a journey management server, the action status message indicating a status of the touchpoint action.

[0020] Responsive to the action status message indicating successful performance of the touchpoint action, the journey management application may utilise a subsequent identified touchpoint data record to display a user interface on the located mobile device that assists the user of the located mobile device to perform a subsequent touchpoint action at another touchpoint device.

[0021] In some embodiments, the touchpoint data records are communicated to the located mobile device by a journey management server application executing on the journey management server, the journey management serverapplication communicating the touchpoint data records to the located mobile device responsive to the located mobile device enrolling in a departure control system.

[0022] The journey management server application may communicate a set of assigned touchpoint data records to the located mobile device, the assigned touchpoint data records being selected from touchpoint devices installed at the travel location.

[0023] Each touchpoint data record typically comprises a touchpoint identifier field, a touchpoint geographical location field and a touchpoint status field.

[0024] The journey management application executes a localisation algorithm to determine a geographic location of the located mobile device, the journey management application utilising the determined geographic location to generate and display a user interface that directs the user to the another touchpoint device.

[0025] In some embodiments, the journey management application detects one or more radio signals emitted from beacons associated with the another touchpoint device to execute the localisation algorithm.

[0026] In some embodiments, the location finding system comprises a phased array antenna system.

[0027] According to another aspect, the present invention provides an antenna comprising: a plurality of spaced apart antenna elements arranged in a linear configuration, each antenna element having an antenna element signal inlet for receiving a signal that the antenna element is to emit; an antenna inlet for receiving a signal that the antenna is to emit; and a feed network having an origin end communicatively coupled to the antenna inlet and a plurality of terminal ends each communicatively coupled to one of the antenna element signal inlets, the feed network comprising a plurality of conductor lines that are arranged to definesignal paths from the antenna inlet to each antenna element signal inlet, each signal path having a defined characteristic.

[0028] In some embodiments, the plurality of conductor lines are arranged in a tree structure having a root level comprising conductor lines communicatively coupled to the antenna inlet and at least one branch level comprising conductor lines communicatively coupled to one of the antenna element signal inlets.

[0029] The branch level conductor lines may extend from the root level conductor lines in a T-junction. The branch level conductor lines that extend from a common T-junction can have different lengths.

[0030] The root level conductor lines can have a different width to branch level conductor lines.

[0031] In some embodiments, the tree structure comprises a first branch level extending from the root level and a second branch level extending from the first branch level, the second branch level comprising conductor lines communicatively coupled to one of the antenna element signal inlets.

[0032] Similarly, the first branch level conductor lines can extend from the root level conductor lines in a T-junction. The first branch level conductor lines that extend from a common T-junction can have different lengths.

[0033] At least some of the conductor lines can incorporate tapering devices to selectively modify a width of the conductor line.BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Embodiments will now be described by way of example only, with reference to the accompanying drawings in which:Figure 1 is a first high-level schematic representation of an aspect of the present invention.Figure 2 illustrates touchpoints in accordance with embodiments of the present invention.Figure 3 illustrates exemplary database structures for systems of touchpoint devices in accordance with embodiments of the present invention.Figure 4 illustrates computing operations that are performed to enrol a passenger in a journey management platform in accordance with embodiments of the present invention.Figure 5 is a schematic illustration of a travel location that implements a journey management platform according to embodiments of the present invention.Figure 6 illustrates exemplary computing operations performed by a journey management application in accordance with embodiments of the present invention after a user accepts terms of use.Figure 7 illustrates exemplary filtering operations performed by a journey management application in accordance with embodiments of the present invention.Figure 8 illustrates an exemplary algorithm that the journey management application executes to determine its geographical position.Figures 9-12 illustrate exemplary touchpoint data structures that a journey management server in accordance with embodiments of the present invention maintains as passenger proceeds through a journey management process.Figure 13 illustrates a touchpoint device security algorithm that the journey management server application in accordance with an embodiment of the present invention executes to enhance security and privacy in the journey management platform.Figure 14 illustrates additional examples of touchpoint devices in accordance with further embodiments of the present invention.Figure 15 illustrates an embodiment of a location finding system in accordance with embodiments of the present invention.Figure 16 is a magnified view of a T-junctions in the location finding system illustrated in Figure 15.Figure 17 is a second high-level schematic representation of an aspect of the present invention.Figure 18 illustrates an embodiment of a touchpoint device in accordance with embodiments of the present invention.Figure 19 illustrates computing operations that are performed to enrol a passenger in a touchpoint management platform in accordance with embodiments of the present invention.Figure 20 is a schematic illustration of handshake operations that touchpoint applications, touchpoint services and touchpoint devices according to embodiments of the present invention perform.Figure 21 is a sequence diagram further illustrating the handshake operations illustrated in Figure 4.Figure 22 is a schematic illustration of an embodiment of the present invention utilizing proximity sensors to detect the presence of a passenger.Figures 23 and 24 are schematic illustrations of the present invention utilizing facial detection routines to detect the presence of passengers who are ready for authentication.Figure 25 is a schematic illustration of a touchpoint application according to embodiments of the present invention transmitting touchpoint action session data to a touchpoint service in accordance with embodiments of the present invention.Figure 26 is a schematic illustration of actions taken by a touchpoint service in accordance with embodiments of the present invention upon detecting a deviation in continuous signal monitoring.Figure 27 is a schematic illustration of a touchpoint application according to embodiments of the present invention transmitting language information to a touchpoint service in accordance with embodiments of the present invention.Figure 28 is a is a block diagram of a computer system suitable for implementing an embodiment of the present invention.DETAILED DESCRIPTION OF THE DRAWINGS

[0035] In the following detailed description, reference is made to accompanying drawings which form a part of the detailed description. The illustrative embodiments described in the detailed description and depicted in the drawings, are not intended to be limiting. Other embodiments may be utilised and other changes may be made without departing from the spirit or scope of the subject matter presented. It will be readily understood that the aspects of the present disclosure, as generally described herein and illustrated in the drawingscan be arranged, substituted, combined, separated and designed in a wide variety of different configurations, all of which are contemplated in this disclosure.

[0036] FIG. 1 illustrates a first computing environment 100 in which aspects of the present invention are implemented. The environment 100 is a networked environment comprising a journey management server 102 in communication with a mobile device 104 over one or more communication networks 106.

[0037] Aspects of the computer processing described below are performed by a journey management server application 108 executing on the journey management server 102 and a journey management application 112 executing on the mobile device 104. As described in further detail below, the journey management server application 108 implements an end-to-end journey management platform that allows the user of the mobile device 104 to perform travel-related actions at, and remote from, a travel location 114. In the exemplified embodiment, travel location 114 is an airport, however those skilled in the art will appreciate that the present invention could readily be implemented at other mass transit locations, such as rail or sea departure points.

[0038] A number of touchpoint devices 116A, 116B, 116C are installed at travel location 114. As noted above, touchpoint devices 116A, 116B, 116C are stations or kiosks with embedded computer hardware and software through which travellers (such as users of mobile devices 104) perform travel-related actions. Such travel-related actions (hereinafter referred to as “touchpoint actions”) include processes such as check-in, identity authentication, registering and weighing baggage, printing baggage tags, dropping baggage into the baggage handling system, scanning boarding passes prior to passing through a departure gate, and the like. Also as noted above, particular touchpoint devices 116A, 116B, 116C are equipped with, or in communication with, suitable peripheral hardware (such as printers, scanners, scales etc.) to enable the device to perform its designated function.

[0039] Embodiments of the present invention facilitate travellers to interact with touchpoint devices 116A, 116B, 116C solely through the use of a mobile device 104. As exemplified in further detail below, the mobile device 104 interacts with a touchpoint device 116A, 116B or 116C through a (typically local) communication network 106, such as WIFI, Bluetooth®, RFID, NFC or the like.

[0040] While only three touchpoint devices 116A, 116B, 116C are depicted at travel location 114, in a typical environment (such as an airport), many more touchpoint devices are installed to accommodate the number of passengers passing through the travel location 114.

[0041] Journey management server 102 further includes a data storage 110 on which data collected by the journey management application 112 and transmitted to the journey management server 102 is stored. Data storage 110 is typically a storage medium such as a hard drive (or collection of hard drives). A database management system (not shown) executing on the journey management server 102 implements a database on data storage 110 for storing and retrieving data.

[0042] Journey management server 102 has been illustrated as a single system. Journey management server 102 can, however, be a scalable server system comprising multiple nodes which can be commissioned / decommissioned based on processing demands. Typically, server systems are server computers that provide greater resources (e.g. processing, memory, network bandwidth) in comparison with the computers that function as client systems, such as the mobile device 104.

[0043] In the illustrated embodiment, data storage 110 is illustrated as part of the journey management server 102. However, the data storage 110 could be a separate system in operative networked communication with the journey management server 102. For example, the data storage 110 could be a networked-attached storage device, an entirely separate storage systemaccessed via a database management system, or any other appropriate data storage mechanism.

[0044] As exemplified in further detail below, the journey management server application 112 performs various operations in response to commands received from (and initiated at) the journey management application 108. As such, when executed by the journey management server 102, the journey management server application 108 configures the journey management server 102 to provide server-side functionality to the journey management 112. To provide this functionality, the journey management server application 108 comprises one or more suitable application programs, libraries, or other software infrastructure.

[0045] Where the journey management application 112 is a web application that is executed by a web browser, the journey management server application 108 will typically be, or interact with, a web server such as a server implemented with the node.js runtime environment. Where the journey management application 112 is a native application executing on the mobile device 104, the journey management server application 108 will typically be, or interact with, an application server. Journey management server 102 may be provided with both web server and application server applications to enable it to serve both web browser and native client applications.

[0046] The journey management server 102 is typically in operative network communication with server infrastructure that executes one or more departure control systems. In other embodiments, one or more departure control systems execute on the journey management server 102 or are integrated with the journey management server application. The departure control systems manage various aspects of passenger processing and flight departure procedures and include modules that implement functions such as: passenger check-in, biometric enrolment, baggage handling, flight manifest, security checks, boarding, communication, flight reconciliation, flight documentation, standby and upgrades, flight messaging, irregular operations, and reporting and analytics. .

[0047] The journey management server 102 and mobile device 104 communicate data between each other either directly or indirectly through one or more communications networks 106. Communications network 106 may comprise a local area network (LAN), a public network (such as the Internet), or a combination of networks. Similarly, the mobile device 104 and touchpoint device 116A, 116B or 116B communicate data between each other (typically directly) through a communication network 106.

[0048] While only one mobile device 104 is depicted in environment 100, a typical environment would typically include many more mobile devices served by the journey management server 102.

[0049] While the mobile device 104 is described as “mobile” it could also be a less mobile type of computer system, such as a desktop computer. However, the mobile device is more likely to be a mobile computer such as a laptop computer, smartphone or tablet device. When executed by the mobile device104, the journey management application 112 configures the mobile device 104 to implement client-side functionality that provides the user of the mobile device 104 with a tailored end-to-end journey management service at the travel location 114.

[0050] As noted above, the journey management application 112 may be provided to the mobile device 104 as a web application that is executed by a general web browser application (such as Chrome, Edge, Safari or the like) that is installed thereon. When provided as a web application, the journey management application 112 accesses the journey management server application 108 via an appropriate uniform resource locator (URL) and communicates with the journey management server application 108 via general world-wide-web protocols (e.g. http, https, ftp) and application programming interfaces (APIs) (e.g. REST APIs). Alternatively, when the journey management application 112 is a native application, it is typically programmed to communicate with the journey management server application 108 using defined API calls.

[0051] A given mobile device 104 may have more than one client application 112 installed thereon, for example both a general web browser application and a dedicated programmatic client application.

[0052] Turning to Figure 2, embodiments of touchpoint devices 116A and 116B are exemplified in further detail. Touchpoint devices 116A and 116B take the form of stations or kiosks and include an enclosure 202 that provides the structure for the touchpoint device and houses the device’s computer processing and communication components. Touchpoint devices 116A and 116B each include a display 204 that is driven by the device’s computer processing components and displays a graphical user interface. As described in further detail below, touchpoint devices in accordance with embodiments of the present invention also allow passengers to interact with the touchpoint device through the journey management application 112 on the mobile device rather 104 than through the display 204. When operating in this mode, the graphical user interface that would otherwise be exclusively displayed on the display 204 of the touchpoint device is displayed on the mobile device 104 as a user interface of the journey management application 112. In this way, the touchpoint device 116A and 116B causes the journey management application 112 to function as a virtual console for the touchpoint device. In turn, this allows touchpoint devices to be developed more cost efficiently, for example by omitting the display 204 from the touchpoint device.

[0053] Touchpoint devices 116A and 116B further include a location finding system 206, which in the exemplified embodiment is a phased array antenna system. As described in further detail below, the phased array antenna system 206 comprises a plurality of antenna elements that are configured to control the phase and direction of a transmitted signal in order to generate a radiation pattern with desired characteristics. In the exemplified embodiment the phased array antenna system 206 is a passive phased array antenna system, although those skilled in the art will appreciate that a location finding system could also incorporate suitable active components.

[0054] As described in further detail below, the phased array antenna system 206 is configured to generate a respective radiation pattern 208 and 209 in front of each touchpoint device 116A and 116B. The radiation patterns 208 and 209 that the phased array antenna system 206 generates are identical and have characteristics whereby the radiation energy is almost entirely contained within a target region that coincides with the radiation pattern. In the illustrated embodiment, the target region extends out from the front of each touchpoint device 116A and 116B. In the region proximal to the touchpoint devices 116A and 116B, the radiation pattern is generally rectangular in shape. In the region distal to the touchpoint devices 116A and 116B, the longitudinal sides of each radiation pattern 208 and 209 converge inwardly to define a generally triangular shape. Outside of the target region, the strength of the radiation energy drops off very rapidly to a substantially indetectable value.

[0055] The target region corresponds to the physical space that a passenger 210 inhabits when they are interacting with a touchpoint device 116A and 116B. The location finding system 206 determines when the passenger 210 is present in the target region by interacting with one or more of the radio transceivers (such as a Bluetooth® transceiver) that are invariably incorporated into the passenger’s mobile device 104. Because of the high selectivity of the radiation pattern, the received signal strength measured by the radio transceiver of the mobile device 104 (such as by taking an RSSI measurement) is at a maximum when the mobile device 104 is present in the target area, and near zero when the mobile device 104 is outside of the target area.

[0056] The characteristics of the radiation pattern and corresponding target area is further described in the three localisation scenarios illustrated in Figure 2. In Localisation Scenario A, the passenger 210 is standing in front of touchpoint 116A but outside of the target area 208. Because the intensity of the radiation that the phased array antenna system 206 generates is substantially undetectable outside of the target area (at least by the radio transceivers typically found in mobile devices 104), the touchpoint device 116A does not register thatthere is a passenger in front of the touchpoint device wishing to perform a touchpoint action.

[0057] In Localisation Scenario B, the passage 210 is standing in front of touchpoint 116B and inside the target area 209. In this scenario, the radio transceiver in the passenger’s mobile device 104 measures a high-intensity signal that corresponds with the intensity of the radiation energy inside the target area. As described in further detail below, upon detecting and measuring the signal, the journey management application 112 transmits a response message to the touchpoint device 116B and the two devices establish a connection channel through which the passenger 210 can perform a touchpoint action.

[0058] In Localisation Scenario B, because of the selectivity and other characteristics of the radiation patterns 208 and 209, when the passenger 210 is located in target area 209, the radiation pattern generated by touchpoint device 116A is essentially undetectable by the mobile device 104. This substantially eliminates the occurrence of “false positive” detections by the touchpoint devices 116A and 116B, and also allows touchpoint devices to be installed in close proximity to each other, thereby maximising spatial efficiency at the travel location 114.

[0059] Location Scenario C is similar to Location Scenario B, but with the passenger 210 standing in the radiation pattern 208 that is generated by the location finding system 206 of the touchpoint device 116A. In this scenario, the mobile device does not detect the radiation pattern generated by touchpoint device 116B.

[0060] Turning to Figure 3, an exemplary database structure for a system of touchpoint devices 116 installed at travel location 114 is illustrated. In the illustrated embodiment, there are eight touchpoint devices 116 installed, although those skilled in the art will appreciate that any number of touchpoint devices can be identified and managed. The data storage 110 stores an aggregated record for the set of touchpoint devices 116, with the record having a field for eachindividual touchpoint device. Each field stores a geolocation address for the touchpoint device and a unique identifier. The geolocation addresses are depicted schematically in Figure 3 as ABD1 , ABD2, ABD3, ABD4, ABD5, ABD6, ABD7, ABD8. The unique identifiers are each depicted as ‘xxx’ although in practice those skilled in the art will appreciate that the journey management platform assigns each touchpoint device its own unique identifier. Touchpoint devices can be identified using a context-based naming convention going from a course context down to a fine context. In one embodiment, touchpoint devices are named starting from the airport name and proceeding down to a best-known context. For example FRA.terminal, bagdrop. xxx or LHR. boarding. JQ819. xxx.

[0061] T uring to Figure 4, the process by which a passenger 210 enrols in a journey management platform 300 in accordance with an embodiment of the present invention is illustrated. As noted above, the journey management platform is implemented by the journey management server application 108 and allows the passenger 210 to use their mobile device 104 to perform travel-related actions at, and remote from, the travel location 114. The passenger 210 typically enrols in the journey management platform 300 after, or at the same time as, checking into their flight. Those skilled in the art will appreciate that the passenger 210 will often check into their flight before arriving at the travel location 114.

[0062] After checking into their flight, the airline’s online ticketing system generates a boarding pass 302 for the passenger 210. The boarding pass 302 can be a paper boarding pass or an electronic boarding pass. The passenger 302 uses the journey management application 112 installed on their mobile device 104 to scan the boarding pass 302 and extract pertinent data therefrom. The journey management application 112 typically performs validation on the data extracted from the boarding pass and, in the event of successful validation, communicates the boarding pass data to the journey management server 102.

[0063] Upon receipt of the boarding pass data at the journey management server 102, the journey management server application 108 interrogates the datastore 110 for the aggregated record of touchpoint devices that are installed at the travel location that is indicated in the boarding pass data. The journey management server application 108 then selects a subset of the touchpoint devices that are personalised to the passenger’s 210 journey. In the embodiment illustrated in Figure 3, the journey management server application selects three touchpoints with geolocation address and id: ABD2.xxx, ABD3.xxx, ABD4.xxx. The journey management server application 108 utilises various selection criteria to construct the set of selected touchpoint devices. For example, the journey management server application 108 may select touchpoint devices to minimise the distance that the passenger needs to travel in the airport or select touchpoints to reflect current or projected passenger traffic and queues at the airport. Selection can also be based on data extracted from the boarding pass.

[0064] In some embodiments, the journey management server application 108 and the mobile device 104 engage in cryptographic operations in which the journey management application 112 generates a private key and the journey management server application 108 communicates the corresponding public key to the touchpoint devices 116 for advertising. The journey management application 112 is subsequently configured to utilise the public key to establish a session with a touchpoint device by receiving data encrypted with the public key from a broadcast radio signal (described in further detail below) and decrypting the data using the private key.

[0065] After the journey management server application 108 selects the subset of touchpoint devices, the journey management server application 108 communicates the list of selected touchpoint devices (including the geolocations of each) to the mobile device 104 in a journey management data record. In the exemplified embodiment, the journey management record includes the following fields:• Enrol ID - storing a unique identifier of the passenger’s enrolment into the journey management platform.• Flight date and time - storing the date and time of the flight as extracted from the boarding pass.• Airline - storing an identifier of the relevant airline, as extracted from the boarding pass.• Departure Airport - storing an identifier of the relevant airport, as extracted from the boarding pass.• Boarding Pass - storing an identifier of the boarding pass.• Selfie Photo - storing an image or the file name of an image of a selfie of a passenger that the passenger submits to authenticate identity against a biometric database.• Expiry - storing the expiry date of the boarding pass• Touchpoints - storing the list of selected touchpoint devices and the geolocation and identifier of each.• Bags - the number of bags associated with the booking.• Bagtags - storing an identifier for each bagtag associated with the bags of the booking.

[0066] Upon receipt of the list of selected touchpoint devices at the mobile device 104, the journey management application 112 stores the list of selected touchpoint devices for future use.

[0067] Turning to Figure 5, an example of a travel location 114 that implements a journey management platform according to embodiments of the present disclosure is illustrated. A plurality of touchpoint devices 116 are installed throughout the travel location 114. A triplet of radio beacons 502A, 502B, 502C are installed adjacent to each to each touchpoint device. In the illustratedembodiment, radio beacons 502A, 502B, 502C operate using the Bluetooth® Low Energy (BLE) standard, although those skilled in the art will appreciate that other radio communication protocols can be used such as standard Bluetooth® and WIFI.

[0068] Each radio beacon 502A, 502B and 502C includes the geolocation address and identifier of its touchpoint device in the signal that it broadcasts.

[0069] As illustrated in Figure 5, when the passenger arrives at the travel location with their mobile device 104, the radio transceiver in the mobile device detects the signal that is emitted from one or more of the radio beacons 502A, 502B, 502C. Upon detecting the signal, the journey management application 112 displays a message on the mobile device 104 and executes the programming operations illustrated in Figure 6. The journey management application 112 populates the displayed message using data from the radio beacon signals. For example, the radio beacon signal can include context data pertaining to the section or zone of the travel location 114 in which the touchpoint devices 116 are installed. In the illustrated embodiment, the journey management application 112 displays a message informing the passenger that they are in the bag drop zone and requesting the passenger to accept the terms of use of the journey management application. The journey management application 112 displays a corresponding message, using context data from the radio beacon signal, when the passenger is located in another section of the travel location, such as the check-in section or departure gate.

[0070] In some embodiments, the journey management server application 108 executes a scheduling algorithm to dynamically assign touchpoint devices to passengers. Typically, the scheduling algorithm operates in conjunction with operations that are performed to localise the mobile device 104 (discussed below). In particular, the scheduling algorithm assigns touchpoint devices taking into account the current geographical location of the mobile device 104, the distance to travel to different touchpoint devices and whether the touchpoint devices are currently being used. In this embodiment, the geographical locationof the mobile device 104 is determined by the journey management application analysing signals received from sparsely distributed beacons. Once the geographical location of the mobile device 104 is determined, the journey management server application 108 requests a Bluetooth® session from the mobile device.

[0071] Turning to Figure 6, the computing operations 600 that the journey management application 112 executes after the user accepts the terms of use are illustrated. The process 600 commences at step 610, at which the journey management application 112 retrieves the geolocation addresses and identifiers of each touchpoint device in the list of touchpoint devices previously communicated to the mobile device 104 by the journey management server application 108. As discussed above, this list of touchpoint devices is a subset of the complete set of touchpoint devices installed at the travel location 114.

[0072] At step 620, the journey management application 112 filters the signals that the mobile device 104 detects to exclude signals apart from those transmitted by radio beacons assigned to touchpoint devices in the list of previously received touchpoint devices. The filtering operation is illustrated schematically in Figure 7, which shows the journey management application 112 filtering out signals, apart from those received from radio beacons assigned to touchpoint devices 700, 710 and 720. In the illustrated embodiment, there are a triplets of radio beacons 700A, 700B, and 700C, 710A, 710B and 710C, 720A, 720B, 720C respectively assigned to touchpoint devices 700, 710 and 720. As discussed above, each radio beacon modulates the geolocation and touchpoint identifier of its assigned touchpoint device in the signal that it broadcasts.

[0073] Returning to Figure 6, the journey management application 112 utilises the signals received from the relevant radio beacons (in the illustrated embodiment, one or more of radio beacons 700A, 700B, 700C, 710A, 710B, 710C, 720A, 720B, 720C) to map and compute the geographical position of each touchpoint device in the previously received list of touchpoint devices (in the illustrated embodiment touchpoint devices 700, 710, 720). An embodiment of aalgorithm that the journey management application 112 executes to determine its geographical position is further exemplified below.

[0074] At step 630, the journey management application 112 executes programming to prepare the mobile device 104 for sessions at the assigned touchpoint devices (namely, in the illustrated embodiment touchpoint devices 700, 710, 720). As described in further detail below, the sessions at the assigned touchpoint devices are those in which the passenger performs relevant touchpoint actions.

[0075] Turning to Figure 8, an embodiment of an algorithm 800 that the journey management application 112 executes to determine its geographical position is illustrated. The process commences at step 802, at which the journey management application 112 utilises its radio transceiver to receive signals emitted by the radio beacons installed at the travel location.

[0076] At step 804, the journey management application 112 filters the received signals using the previously received list of touchpoint devices. To perform localisation, the journey management application 112 typically focusses on the triplet of radio beacons assigned to one of the touchpoint devices in the list of previously received touchpoint devices.

[0077] At step 806, the journey management application measures 112 measures the distance from each radio beacon in the triplet. In the exemplified embodiment, the journey management application measures the distance to each beacon by first measuring the RSSI of the signal received from the respective beacon.

[0078] At step 808, the journey management application 112 utilises the measured distances to localise the mobile device 104. In the exemplified embodiment, the journey management application 112 performs localisation by defining a circle around each of the three radio beacons with a radius of the measured distance. The journey management application then localises the mobile device 104 to the area defined by the intersection of the three circles. Thejourney management application 112 typically also improves the estimation of the geographical location by taking into account factors such as signal noise, signal propagation characteristics and the quality of distance measurements.

[0079] After localising the mobile device 104, the journey management application 112, at step 810, displays a prompt on the mobile device 104 to the passenger to move to the first assigned touchpoint in the list of previously received touchpoints. In the exemplified embodiment, the journey management application 112 displays directions to the assigned touchpoint from the current location of the mobile device (as computed in step 808).

[0080] At step 812, after the mobile device 104 arrives at the assigned touchpoint device, the journey management application 112 establishes a session with the assigned touchpoint device. The operations performed by the journey management application 112 and touchpoint device to establish and operate a session are described in further detail below.

[0081] Figures 9-12 illustrate a touchpoint data structure 901 that the journey management server 102 maintains as the passenger proceeds through the journey management process by performing touchpoint actions at the assigned touchpoint devices. In the exemplified embodiment, the journey management server application 108 has assigned four touchpoints to the passenger, that are labelled as: Check-in, Bag Drop, Boarding and Hotel. The touchpoint data structure 901 also contains a status column to indicate the current status of the touchpoint action that is to be performed at each touchpoint. In the exemplified embodiment, the touchpoint status has values of: Scheduled, Processing and Used.

[0082] In Figure 9, the passenger is yet to interact with any of the assigned touchpoints 116A (for check-in), 116B (for bag drop), 116C (for hotel). This is reflected in the touchpoint data structure 901 , where the status value for the four assigned touchpoints is “Scheduled”. When initially assigning touchpoints topassengers, the journey management server application 108 sets the status value to “Scheduled” for each assigned touchpoint.

[0083] In Figure 10, the mobile device 104 is in proximity to the check-in touchpoint device 116A, with the journey management application 112 having directed the passenger to the touchpoint device 116A and the touchpoint device 116A having determined that the passenger is standing in the target region in front of the touchpoint device. In this scenario, the touchpoint device 116A communicates a touchpoint status message to the journey management server 104. Upon receipt of the touchpoint status message, the journey management server application 108 updates the status of the relevant touchpoint device to “Processing”.

[0084] Figure 11 illustrates the state of the touchpoint data structure 901 after the passenger has completed the touchpoint action at touchpoint 116A and proceeded to touchpoint 116B, which determines the passenger’s presence by utilising its location finding system. In this scenario, the touchpoint data structure records the status of the check-in touchpoint 116A as “Used” and the bag drop touchpoint 116B as “Processing”.

[0085] Figure 12 illustrates the state of the touchpoint data structure 901 after the passenger has completed touchpoint actions at each of the check-in, bag drop, boarding and hotel touchpoints. In this scenario, the touchpoint data structure records the status of all touchpoints as “Used”.

[0086] Figure 13 illustrates a touchpoint device security algorithm that the journey management server application 108 executes to enhance security and privacy in the journey management platform. To this end, the journey management server application 108 executes a timer process 402 on the journey management server 102. The timer process 402 signals the start and end of a predetermined time period to the journey management server application 108. Upon receipt of a time period expiry signal, the journey management server application executes a beacon identifier generation module 404 to generate newidentifiers for the touchpoint devices (which in the illustrated embodiment are touchpoints 116A and 116B). In the illustrated embodiment, the beacon identifier generation module 404 generates new identifiers for the touchpoint devices by rotating or otherwise reallocating the set of beacon identifiers to different touchpoint devices.

[0087] After generating the new beacon identifiers for the touchpoint devices, the beacon identifier generation module 404 generates new journey management records (or tokens) for any mobile devices (in the illustrated embodiment 104A and 104B) having journey management records with touchpoint devices identified by the earlier identifiers. The beacon identifier generation module 404 communicates the new journey management records to a synchronization module that communicates the records to the effected touchpoint devices 116A and 116B, and mobile devices 104A and 104B.

[0088] Figure 14 illustrates additional examples of touchpoint devices in accordance with further embodiments of the present invention, along with graphical user interfaces generated by the journey management application as a part of the process of the passenger performing touchpoint actions thereon.

[0089] As discussed above, the passenger 210 enrols in the journey management platform as part of the workflow of checking into their flight. Upon successful enrolment, the journey management server 102 communicates a journey management record to the mobile device that includes the list of touchpoint devices that the journey management server application 108 has allocated to the passenger 210. The journey management application 112 also displays a graphical user interface 215 on the mobile device 104 that allows the passenger to enter the number of bags that they are carrying. After receiving the input from the passenger, the journey management application 112 communicates the input to the journey management server 102, at which the journey management server application 108 updates the touchpoint data structure.

[0090] As discussed above, the journey management application 112 displays a graphical user interface on the mobile device that includes directions from the passenger’s 210 current location to the first assigned touchpoint device. In the embodiment exemplified, the first assigned touchpoint device 150 is a bag tag printer. The bag tag printer device 150 does not include any inbuilt display, but instead performs interactions with the passenger 210 through the journey management application 112 that executes on the mobile device 104.

[0091] As the passenger approaches the bag tag printer device 150, the bagtag printer device 150 utilises its location finding system to determine when the passenger 210 is standing in front of the bag tag printer device 150 in the target zone. Upon locating the mobile device 104 in the target zone, the bag tag printer device 150 and mobile device establish a connection with each other (such as a Bluetooth® connection) over which the journey management application 112 facilitates the passenger to perform a touchpoint action. In the illustrated embodiment, the touchpoint action is the passenger 150 printing one or more bag tags 152.

[0092] After establishing the connection with the bag tag printer device 150, the journey management application 112 interrogates its local storage for the most recent version of the journey management record that was communicated to the mobile device upon enrolling in the journey management platform. As noted above, the journey management record contains the list of touchpoints that the journey management server application 108 allocated to the mobile device 104. The journey management application 112 utilises the stored data about the allocated touchpoints to display a relevant contextual graphical user interface on the mobile device. In the illustrated embodiment, the graphic user interface relevant to the bag tag printer device 150 asks the passenger 112 whether they wish to print bag tags.

[0093] As described above, after the passenger performs the touchpoint action (which in the illustrated embodiment is printing one or more bag tags) the journey management application 112 updates the touchpoint record to indicatethe current status of the touchpoint action that the passenger performed at the touchpoint device (namely the bag tag printer device 150). The journey management application 112 communicates the updated touchpoint record to the journey management server 102 for the journey management server application 108 to update the relevant touchpoint data structure.

[0094] The journey management application 112 then performs the computing operations described above to receive beacon signals from the next touchpoint in the touchpoint record, determine the geographical location of the mobile device 104, prompt the passenger to move to the next touchpoint and display directions to the next touchpoint on the mobile device 104.

[0095] In the illustrated embodiment, the next touchpoint device is a bag drop device 155. The bag drop device 155 is associated with a baggage conveyer 157 and bag tag scanner (not shown). As with the bag tag printer device 150, as the passenger approaches the bag drop device 155, the bag drop device 155 utilises its location finding system to determine when the passenger 210 is standing in front of the bag drop device 155 in the target zone. Upon locating the mobile device 104 in the target zone, the bag drop device 155 and mobile device establish a connection that the passenger 210 uses to perform the touchpoint action (namely injecting the baggage into the baggage handling system).

[0096] After connection establishment, the journey management application 112 again interrogates its local storage for the most recent version of the journey management record. This version is the journey management record as updated by the journey management application 112 after the passenger performed the touchpoint action at the previous touchpoint device. The journey management application 112 utilises updated journey management record to display the relevant contextual graphical user interface on the mobile device 104. In the illustrated embodiment, the graphic user interface 159 relevant to the bag drop device 155 provides informational material to the passenger 210 to enable them to place their baggage on the baggage conveyer.

[0097] After the passenger 210 successfully performs the baggage drop touchpoint action, the journey management application 112 updates the touchpoint record to indicate the current status of the performed touchpoint action. The journey management application 112 communicates the updated touchpoint record to the journey management server 102 for the journey management server application 108 to update the relevant touchpoint data structure.

[0098] Figure 15 illustrates an embodiment of a phased array antenna system 206 in accordance with the present disclosure. As described above, the antenna system 206 is incorporated into the present touchpoint devices and functions as a location finding system. Antenna system 206 includes a plurality of antenna elements 250A-250H arranged in a linear configuration, with the antenna elements being equally spaced apart. In the illustrated embodiment, the antenna system 206 includes eight antenna elements. As noted above, the antenna elements 250A-250H are configured to control the phase and direction of their signal emissions in order to generate the radiation pattern with desired characteristics. The antenna elements 205A-250H are formed on top of a suitable substrate 252, such as a substrate formed from FR4 material.

[0099] Each antenna element 250A-250H is indirectly connected to the antenna signal feed point 254 by way of an intervening feed network 256. Feed network 256 has a tree structure which at the root level is divided into left 258 and right 260 branches. The left 258 and right 260 branches of the feed network 256 respectively correspond with a left subarray 262 (comprising antenna elements 250A-250D) and a right subarray 264 (comprising antenna elements 250E-250H) of antenna elements defined symmetrically about the centre line 266 of the antenna system 206.[000100] The left 258 and right 260 branches of the feed network are generally symmetrical about the centre line 266 of the antenna system. Using left branch 258 for the purpose of elucidation, the branch includes a root level microstrip line 268. In the illustrated embodiment, the root level microstrip line is 50 ohmimpedance microstrip line. Root level microstrip line 268 is divided into lines of two different diameters 270 and 272 by a Klopfenstein taper 274. Line 270 terminates in a T-junction 276 from which a first branch level microstrip line 278 extends. In the illustrated embodiment, the first branch level microstrip line 278 is 37.5 impedance microstrip line.[000101 ] T-junction 276 divides the first branch level microstrip line into first 280 and second 282 lengths. T-junction 276 is offset from the centre line 284 between antenna elements 250B and 250C and as such the first length 280 differs from the second length 282. In the illustrated embodiment, second length 282 is 2.82mm longer than first length 280.[000102] Both the first length 280 and second length 282 terminate in respective T-junctions 284 and 286 from which second branch level microstrip lines 288 and 290 extend. In the illustrated embodiment, the second branch level microstrip lines 288 and 290 are 75 ohm impedance microstrip line. The second branch level microstrip lines 288 and 290 have generally the same physical dimensions. Using second branch level microstrip line 288 for the purpose of elucidation, T- junction 284 divides microstrip line 288 into first 292 and second 294 lengths. T- junction 284 is offset from the centre line 286 between antenna elements 250A and 250B and as such the first length 292 differs from the second length 294. In the illustrated embodiment, second length 294 is 8.16mm longer than first length 292.[000103] Figure 16 provides a magnified view of one of the T-junctions 284 or 286 from which the second branch level microstrip lines 288 and 290 extend. As shown in Figure 16, the first length 280 of the first branch level microstrip line has a diameter of d2 and the first and second lengths 292 and 294 of the second level microstrip line has a diameter of di. A gap 296 is provided in the region between the first length 292 and second length 294. The inner wall of gap 296 projects from the upper wall of length 292 at an angle of 45°.[000104] The characteristics of the feed network 256, and in particular the relative lengths, diameters and impedance of the root, first and second branch microstrip lines allow the phased array antenna to generate the highly selective radiation pattern illustrated above. More specifically, the tree structure defines eight separate microstrip line conductor paths extending from the antenna signal feed point 254 to the inlet of each of the antenna elements 250A-250H. As the signal enters the signal feed point 254 and proceeds along each individual signal path, the signal phase is manipulated by the physical and electrical characteristics of the signal path so that by the time the signal arrives at the antenna element 250A-250H where it is emitted, the signal has the appropriate phase to generate the desired radiation pattern.[000105] FIG. 17 illustrates a second computing environment 101 in which aspects of the present invention are implemented. The environment 101 is a networked environment comprising a touchpoint management server 102 in communication with a mobile device 104 over one or more communication networks 106.[000106] Embodiments of the present invention provide a touchpoint device 116A that is installed at a travel location 114. Additional touchpoint devices 116B and 116C are also installed at the travel location 114. In the exemplified embodiment, travel location 114 is an airport, however those skilled in the art will appreciate that the present invention could readily be implemented at other mass transit locations, such as rail or sea departure points.[000107] While only three touchpoint devices 116A, 116B, 116C are depicted at travel location 114, in a typical environment (such as an airport), many more touchpoint devices are installed to accommodate the number of passengers passing through the travel location 114.[000108] Aspects of the computer processing described below are performed by an application 108 (referred to hereinafter as a “touchpoint service”) that executes on the touchpoint management server 102, and a touchpoint application 112 thatexecutes on the mobile device 104. As described in further detail below, the touchpoint service 108 is in operative network communication with both the touchpoint devices 116A-116C and the touchpoint applicationl 12, in each case by way of the communication network 106. These distinct network connections allow the mobile device 104 to interact with the touchpoint device e.g. 116A by way of the touchpoint service 108. The network connection between the touchpoint service 108 and the touchpoint device e.g. 116A allows the touchpoint device to make data that is received from the mobile device 104 selectively available to the touchpoint devices 116A-116C.[000109] Touchpoint management server 102 further includes a data storage 110 on which data received from the touchpoint application 112, touchpoint device e.g. 116A or an external system, is stored. Data storage 110 is typically a storage medium such as a hard drive (or collection of hard drives). A database management system (not shown) executing on the touchpoint server 102 implements a database on data storage 110 for storing and retrieving data.[000110] Touchpoint server 102 has been illustrated as a single system. Touchpoint server 102 can, however, be a scalable server system comprising multiple nodes which can be commissioned / decommissioned based on processing demands. Typically, server systems are server computers that provide greater resources (e.g. processing, memory, network bandwidth) in comparison with the computers that function as client systems, such as the mobile device 104.[000111] In the illustrated embodiment, data storage 110 is illustrated as part of the touchpoint server 102. However, the data storage 110 could be a separate system in operative networked communication with the touchpoint server 102. For example, the data storage 110 could be a networked-attached storage device, an entirely separate storage system accessed via a database management system, or any other appropriate data storage mechanism.[000112] As exemplified in further detail below, the touchpoint service 108 performs various operations in response to receiving data from the touchpoint application 112, touchpoint device e.g. 116A and external systems. As such, when executed by the touchpoint server 102, the touchpoint service 108 configures the touchpoint management server 102 to provide server-side functionality to the touchpoint application 112 and touchpoint device 116A. To provide this functionality, the touchpoint service 108 comprises one or more suitable application programs, libraries, or other software infrastructure.[000113] Where the touchpoint application 112 is a web application that is executed by a web browser, the touchpoint service 108 will typically be, or interact with, a web server such as a server implemented with the node.js runtime environment. Where the touchpoint application 112 is a native application executing on the mobile device 104, the touchpoint service 108 will typically be, or interact with, an application server. Touchpoint management server 102 may be provided with both web server and application server applications to enable it to serve both web browser and native client applications.[000114] The touchpoint management server 102 is typically in operative network communication with server infrastructure that executes one or more departure control systems. In other embodiments, one or more departure control systems execute on the touchpoint management server 102 or are integrated with the touchpoint service 108. The departure control systems manage various aspects of passenger processing and flight departure procedures and include modules that implement functions such as: passenger check-in, biometric enrolment, baggage handling, flight manifest, security checks, boarding, communication, flight reconciliation, flight documentation, standby and upgrades, flight messaging, irregular operations, and reporting and analytics.[000115] The touchpoint management server 102 and mobile device 104 and touchpoint device 116A respectively communicate data between each other either directly or indirectly through one or more communications networks 106.Communications network 106 may comprise a local area network (LAN), a public network (such as the Internet), or a combination of networks.[000116] While only one mobile device 104 is depicted in environment 100, a typical environment would typically include many more mobile devices served by the touchpoint service 108.[000117] While the mobile device 104 is described as “mobile” it could also be a less mobile type of computer system, such as a desktop computer. However, the mobile device is more likely to be a mobile computer such as a laptop computer, smartphone or tablet device. When executed by the mobile device104, the touchpoint application 112 configures the mobile device 104 to implement clientside functionality that provides the user of the mobile device 104 with a streamlined way to interact with the touchpoint device e.g. 116A and perform touchpoint actions thereon.[000118] As noted above, the touchpoint application 112 may be provided to the mobile device 104 as a web application that is executed by a general web browser application (such as Chrome, Edge, Safari or the like) that is installed thereon. When provided as a web application, the touchpoint application 112 accesses the touchpoint service 108 via an appropriate uniform resource locator (URL) and communicates with the touchpoint service 108 via general world-wide- web protocols (e.g. http, https, ftp) and application programming interfaces (APIs) (e.g. REST APIs). Alternatively, when the touchpoint application 112 is a native application, it is typically programmed to communicate with the touchpoint service 108 using defined API calls.[000119] A given mobile device 104 may have more than one client application 112 installed thereon, for example both a general web browser application and a dedicated programmatic client application.[000120] Turning to Figure 18, an embodiment of a touchpoint device 116A is exemplified in further detail. Touchpoint device 116A takes the form of an elongated divider 130 that divides a region of the travel location 114 into twoseparate passenger transit lanes. The divider 130 provides the structure for the touchpoint device 116A and houses the device’s computer processing components and operating software. A pair of generally L-shaped members 132A and 132B extend upwardly from midway along the top edge of the divider 130. L- shaped members 132A and 132B each include a respective base section 134A and 134B that is coupled to the divider 130, a respective central section 136A and 136B that extends from the respective end of base section 134A and 134B, and a respective terminal section 138A and 138B that extends generally perpendicularly from the respective end of central section 136A and 136B.[000121] Central sections 136A and 136B are generally planar in form and each extend at an acute angle from the respective planes that are defined by each base section 134A and 134B. Central sections 136A and 136B are also slightly rotated about an axis that is orthogonal to each plane that is defined by respective base sections 134A and 134B. Terminal sections 138A and 138B respectively extend in a generally perpendicular direction from the planes defined by each base section 134A and 134B.[000122] A phased array antenna system is integrated into each of the terminal sections 138A and 138B. The phased array antenna system comprises a plurality of antenna elements that are configured to control the phase and direction of a transmitted signal in order to generate a radiation pattern with desired characteristics. In the exemplified embodiment, the phased array antenna system is a passive phased array antenna system, although those skilled in the art will appreciate that the antenna could also incorporate suitable active components.[000123] The phased array antenna system functions as a location finding system and is configured to generate a respective radiation pattern in each passenger transit lane. The radiation pattern that each phased array antenna system generates are identical and have characteristics whereby the radiation energy is almost entirely contained within a target region that coincides with the radiation pattern. In the illustrated embodiment, the target region extends outfrom the front of the respective side of the divider 130. Outside of the target region, the strength of the radiation energy drops off very rapidly to a substantially indetectable value.[000124] The construction of the L-shaped members 132A and 132B and the relative location of the base sections 134A and 134B, central sections 136A and 136B, and terminal sections 138A and 138B is such that the underside of the terminal sections 138A and 138B is in a favourable orientation for the phased array antenna system to generate a suitable target region. In some embodiments, the orientation of terminal sections 138A and 138B can be adjusted to facilitate more spatially precise generation of target regions. The power level of the radiation pattern is also adjustable for this same purpose.[000125] The target region corresponds to the physical space that a passenger inhabits as they approach the touchpoint device 116A. The location finding system determines when the passenger is present in the target region by interacting with one or more of the radio transceivers (such as a Bluetooth® transceiver) that are invariably incorporated into the passenger’s mobile device 104. Because of the high selectivity of the radiation pattern, the received signal strength measured by the radio transceiver of the mobile device 104 (such as by taking an RSSI measurement) is at a maximum when the mobile device 104 is present in the target area, and near zero when the mobile device 104 is outside of the target area.[000126] An overhead camera is integrated into each of the terminal sections 138A and 138B. The overhead camera is a two-dimensional camera, a three- dimensional camera or a camera with both two-dimensional and three- dimensional capabilities. The relative location of the base sections 134A and 134B, central sections 136A and 136B, and terminal sections 138A and 138B is also such that the underside of the terminal sections 138A and 138B are in favourable orientations for operation of the overhead cameras.[000127] A handheld electronic device 140A and 1406 is respectively attached to each of the base sections 134A and 134B. Each handheld device 140A and 1406 includes an integrated (two-dimensional or three-dimensional) camera, a display 142A and 142B, audio playback circuitry and speakers.[000128] A second set of handheld devices 144A and 144B are attached to the divider 130 at adjacent locations near to the end of the top edge. Devices 144A and 144B each include displays that are oriented to face in the direction of the respective passenger transit lane. Handheld devices 144A and 144B serve to display instructions to passengers as they transit along the transit lane.[000129] LED strips 146 are provided around the periphery of each face of the divider. The LED strips 146 serve as visual guidance to passengers as they transit along the transit lane.[000130] Turing to Figure 19, the process by which a passenger 210 enrols in a touchpoint management platform in accordance with an embodiment of the present invention is illustrated. As noted above, the touchpoint management platform is implemented by the touchpoint service 108 and allows the passenger 210 to use their mobile device 104 to interact with the touchpoint device 116A by way of the touchpoint service 108. The passenger 210 typically enrols in the touchpoint platform after, or at the same time as, checking into their flight. Those skilled in the art will appreciate that the passenger 210 will often check into their flight before arriving at the travel location 114.[000131 ] After checking into their flight, the airline’s online ticketing system generates a boarding pass 302 for the passenger 210. The boarding pass 302 can be a paper boarding pass or an electronic boarding pass. The passenger 302 uses the touchpoint application 112 installed on their mobile device 104 to scan the boarding pass 302 and extract pertinent data therefrom. The touchpoint application 112 typically performs validation on the data extracted from the boarding pass and, in the event of successful validation, communicates the boarding pass data to the touchpoint management server 102.[000132] Upon receipt of the boarding pass data at the touchpoint management server 102, the touchpoint service 108 stores the geolocation address, identifiers and other parameters of touchpoint devices that are installed at the travel location that is indicated in the boarding pass data. The data storage 110 stores an aggregated record for the relevant set of touchpoint devices, with the record having a field for each individual touchpoint device. Each field stores a geolocation address for the touchpoint device and a unique identifier. The geolocation addresses are depicted schematically in Figure 3 as ABD1 , ABD2, ABD3, ABD4, ABD5, ABD6. The unique identifiers are each depicted as ‘xxx’ although in practice those skilled in the art will appreciate that the touchpoint management platform assigns each touchpoint device its own unique identifier. Touchpoint devices can be identified using a context-based naming convention going from a coarse context down to a fine context. In one embodiment, touchpoint devices are named starting from the airport name and proceeding down to a best-known context. For example FRA.terminal, bagdrop. xxx or LHR. boarding. JQ819. xxx.[000133] The touchpoint service 108 may select a subset of the touchpoint devices that are personalised to the passenger’s 210 journey. In the embodiment illustrated in Figure 3, the touchpoint service 108 selects three touchpoints with geolocation address and id: ABD2.xxx, ABD3.xxx, ABD4.xxx. The touchpoint service 108 utilises various selection criteria to construct the set of selected touchpoint devices. For example, the touchpoint service 108 may select touchpoint devices to minimise the distance that the passenger needs to travel in the airport, or select touchpoints to reflect current or projected passenger traffic and queues at the airport. Selection can also be based on data extracted from the boarding pass.[000134] Turning to Figure 20, an example of initial handshake operations that the touchpoint application 112, touchpoint service 108 and touchpoint device 116A perform is schematically illustrated. Passenger 210 approaches the touchpoint device 116A carrying the mobile device 104 that was used to enrol in the touchpoint platform. The location finding system continually generates aradiation pattern 402. As the passenger approaches the touchpoint device and comes into proximity with the radiation pattern, the touchpoint application 112 progressively receives a signal of increasing strength from the touchpoint device 116A. Upon the received signal exceeding a predetermined signal strength, the touchpoint application 112 establishes a touchpoint action session with the touchpoint service 108. The touchpoint application 112 utilizes a suitable API to reach the touchpoint service 108 and establish the touchpoint action session.[000135] The handshake operations are illustrated in further detail in the sequence diagram of Figure 21 . Typically, the initial communication in the sequence is the touchpoint e.g.116A transmitting a request to authenticate to the touchpoint service 108. The touchpoint service 108 receives the authenticate request, executes an authentication routine and communicates the result of the authentication to the touchpoint device 116A.[000136] Typically at a later point in time, the passenger 210 enrols in the touchpoint platform, arrives at the airport and is detected by the touchpoint device 116A’s location finding system as being in proximity thereto. Proximity is detected by the mobile device 104 receiving a signal of suitable strength (namely a touchpoint action session message) from the touchpoint device 116A. Receipt of the signal instructs the touchpoint application 112 to establish a touchpoint action session with the touchpoint service 108. Touchpoint application 112 establishes the touchpoint action session by transmitting a CreateNewUnitSession message to the touchpoint service 108. In response to receiving the CreateNewUnitSession message, the touchpoint service 108 executes a token creation routine that creates a token and assigns it to the touchpoint action session. After creating the token, the touchpoint service 108 transmits a TokenCreated message to the touchpoint application 112 that includes a copy of the token.[000137] Upon receipt of the TokenCreated message, the touchpoint application 112 transmits a Notification message to the touchpoint service 108. The Notification message includes the assigned token and the scanned boarding passthat the passenger was issued upon checking into their flight using the functionality discussed above. Upon receipt of the Notification message, the touchpoint service 108 relays the Notification message to the touchpoint device 116A. Upon receipt of the relayed Notification message, the touchpoint device 116A executes an msg construction routine to generate an msg message. Msg message typically contains data pertaining to whether the touchpoint device e.g. 116A successfully received the assigned token and scanned boarding pass. In other embodiments, msg message suitably contains data pertaining to the next touchpoint to which the passenger should transit. The touchpoint device 116A sends a Notification message to the touchpoint service 108 that includes the msg message. Upon receipt of the Notification message, the touchpoint service relays the Notification message (including the encapsulated msg message) to the touchpoint application 112.[000138] Returning to Figure 20, by receiving the Notification message, the touchpoint application is informed that the touchpoint device 116A has received a copy of a valid boarding pass from the passenger. The touchpoint device 116A then indicates to the passenger 210 through suitable means (such as the LED 146, display 144B, audio 142B) to proceed along the transit lane to complete the touchpoint interaction.[000139] Turning to Figure 22, an embodiment of the present invention utilizing proximity sensors to detect the presence of a passenger is schematically illustrated. As with the previous embodiment, passenger 210 approaches the touchpoint device 116A carrying the mobile device 104 that was used to enrol in the touchpoint platform and the touchpoint device 116A, touchpoint service 108 and touchpoint application complete the handshaking operations exemplified above. In addition to the location finding system generating a radiation pattern 402, overhead cameras with field of view 404 (illustrated in green) are trained in the direction of the approaching passenger. The overhead cameras (which are either two dimensional cameras or three dimensional cameras) are utilized to determine the proximity of the passenger 210 from the touchpoint device 116A using object detection / recognition methods known to those skilled in the art. Inconjunction with radiation pattern 402 and camera field of view 404, a number of additional proximity sensors 406 are located around the front edge of the divider 130 to assist in detecting the proximity of the mobile device.[000140] Turning to Figure 23, a further embodiment of the present invention utilizing a proximity sensor to detect the presence of a passenger is schematically illustrated. As with the previous embodiment, passenger 210 approaches the touchpoint device 116A carrying the mobile device 104 that was used to enrol in the touchpoint platform. In addition to the location finding system generating a radiation pattern 402, a proximity sensor with field of view 408 is trained in the direction of the approaching passenger. The touchpoint device’s 116A operating software operates the proximity sensor to capture an image of the passenger’s 210 face. In conjunction with radiation pattern 402 or in isolation, the touchpoint device’s operating software or the touchpoint service 108 executes facial detection routines to detect the presence of a passenger 210 in the vicinity of the touchpoint device 116A who is ready for authentication.[000141] Figure 24 schematically illustrates the face detection routine analyzing the size and area of the passenger’s 210 face to measure the distance between the touchpoint device 116A and the passenger 210. In an alternative embodiment, the overhead camera is used to capture a facial image of the passenger 210.[000142] Turning to Figure 25, embodiments of data that the touchpoint application 112 communicates to the touchpoint service 108 during the touchpoint action session, referred to hereinafter as “touchpoint action session data” is illustrated. As described above, after the touchpoint service 108 indicates to the touchpoint application 112 that the touchpoint device 116A has received a copy of the passenger’s 210 boarding pass, the touchpoint device 116A directs the passenger 210 to proceed along the passenger transit lane.[000143] Radiation pattern 402 is focused on the passenger transit lane. As the passenger 210 proceeds along the transit lane, the touchpoint device 116A emitsa succession of radio signals that the mobile device 104 receives. Upon receipt of each radio signal, the touchpoint application measures the strength of the received signal and communicates the measurement to the touchpoint service 108, along with a timestamp of when the signal was received.[000144] Mobile device 104 device can be in different orientations based on how the passenger 210 is conveying the mobile device 104 (such as holding in the hand, or in a front or back pocket amongst other orientations). These differences in orientation can result in differences in the signal strength when received by the mobile device 104. However, notwithstanding differences in signal strength, signal strength yields time series data of suitable fidelity for the touchpoint service 108 to analyze continuously and measure rises and dips that are correlated with the passenger transiting or not transiting through radiation pattern 402.[000145] In one embodiment, the touchpoint service 108 analyses the time series data received from the touchpoint application using Moving Average Convergence Divergence (MACD) analysis. MACD analysis of the time series data provides insights into the rises and dips of the signal strength when received by the mobile device. Those skilled in the art will appreciate that alternative methods to analyze time series data could be utilized.[000146] Figure 26 illustrates an embodiment where the touchpoint service’s 108 analysis of the time series data indicates a deviation in continuous signal monitoring. For example, an usual delay in the mobile device 104 receiving the signal is potentially indicative of the passenger 220 not proceeding along the passenger transit lane. In this event, the touchpoint service 108 transmits an anomaly detection signal to the touchpoint device 116A for display thereon, or to an agent in proximity to the touchpoint device to take appropriate corrective action.[000147] Alternatively, when the time series data indicates that the passenger has successfully completed transit along the passenger transit lane, thetouchpoint service 108 transmits a notification message to the touchpoint device 116A and the touchpoint application 112[000148] In the illustrated embodiment, touchpoint device 116A takes the form of a barrierless transit. However, those skilled in the art will appreciate that the transit could equally be controlled using a gate that is automatically opened and closed based on the analysis of the touchpoint action session data and resulting messages transmitted from the touchpoint service 108 to the touchpoint device 116A.[000149] During the touchpoint action session, in addition to the RSSI values, the touchpoint application 112 communicates data pertaining to: the proximity of the mobile device to the touchpoint device, mobile device details (vendor, OS, eye) and personalization data (such as the passenger’s preferred language).[000150] As illustrated in Figure 27, language information that the touchpoint application transmits to the touchpoint service 108 can be forwarded on to the touchpoint device 116A and used in the touchpoint action. For example, the touchpoint device can display instructions to the passenger in the passenger’s preferred language.[000151 ] Figure 28 provides a block diagram of a computer processing system 1200 configurable to implement embodiments and / or features described herein. The touchpoint devices in accordance with embodiments of the present invention will typically incorporate at least some of the components of the computer processing system 1200. System 1200 is a general purpose computer processing system. It will be appreciated that Figure 14 does not illustrate all functional or physical components of a computer processing system. For example, no power supply or power supply interface has been depicted, however system 1200 will either carry a power supply or be configured for connection to a power supply (or both). It will also be appreciated that the particular type of computer processing system will determine the appropriate hardware and architecture, and alternative computer processing systems suitable forimplementing features of the present disclosure may have alternative components to those depicted.[000152] Computer processing system 1200 includes at least one processing unit 1202. The processing unit 1202 may be a single computer processing device (e.g. a central processing unit, graphics processing unit, or other computational device), or may include a plurality of computer processing devices. In some instances all processing will be performed by processing unit 1202, however in other instances processing may also be performed by remote processing devices accessible and useable (either in a shared or dedicated manner) by the system 1200.[000153] Through a communications bus 1204 the processing unit 1202 is in data communication with a one or more machine readable storage (memory) devices which store instructions and / or data for controlling operation of the processing system 1200. In this example system 1200 includes a system memory 1206 (e.g. a BIOS), volatile memory 1208 (e.g. random access memory such as one or more DRAM modules), and non-volatile memory 1210 (e.g. one or more hard disk or solid state drives).[000154] System 1200 also includes one or more interfaces, indicated generally by 1212, via which system 1200 interfaces with various devices and / or networks. Generally speaking, other devices may be integral with system 1200, or may be separate. Where a device is separate from system 1200, connection between the device and system 1200 may be via wired or wireless hardware and communication protocols, and may be a direct or an indirect (e.g. networked) connection.[000155] Wired connection with other devices / networks may be by any appropriate standard or proprietary hardware and connectivity protocols. For example, system 1200 may be configured for wired connection with other devices / communications networks by one or more of: USB; FireWire; eSATA;Thunderbolt; Ethernet; OS / 2; Parallel; Serial; HDMI; DVI; VGA; SCSI. Other wired connections are possible.[000156] Wireless connection with other devices / networks may similarly be by any appropriate standard or proprietary hardware and communications protocols. For example, system 1200 may be configured for wireless connection with other devices / communications networks using one or more of: infrared; Bluetooth; WiFi; near field communications (NFC); Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), long term evolution (LTE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA). Other wireless connections are possible.[000157] Generally speaking, and depending on the particular system in question, devices to which system 1200 connects — whether by wired or wireless means — include one or more input devices to allow data to be input into / received by system 1200 for processing by the processing unit 1202, and one or more output device to allow data to be output by system 1200. Example devices are described below, however it will be appreciated that not all computer processing systems will include all mentioned devices, and that additional and alternative devices to those mentioned may well be used.[000158] For example, system 1200 may include or connect to one or more input devices by which information / data is input into (received by) system 1200. Such input devices may include keyboards, mice, trackpads, microphones, accelerometers, proximity sensors, GPS devices and the like. System 1200 may also include or connect to one or more output devices controlled by system 1200 to output information. Such output devices may include devices such as a CRT displays, LCD displays, LED displays, plasma displays, touch screen displays, speakers, vibration modules, LEDs / other lights, and such like. System 1200 may also include or connect to devices which may act as both input and output devices, for example memory devices (hard drives, solid state drives, disk drives, compact flash cards, SD cards and the like) which system 1200 can read datafrom and / or write data to, and touch screen displays which can both display (output) data and receive touch signals (input).[000159] System 1200 may also connect to one or more communications networks (e.g. the Internet, a local area network, a wide area network, a personal hotspot etc.) to communicate data to and receive data from networked devices, which may themselves be other computer processing systems.[000160] System 1200 may be any suitable computer processing system such as, by way of non-limiting example, a server computer system, a desktop computer, a laptop computer, a netbook computer, a tablet computing device, a mobile / smart phone, a personal digital assistant, a personal media player, a set- top box, a games console.[000161] Typically, system 1200 will include at least user input and output devices 1214 and a communications interface 1216 for communication with a network such as network 106 of environment 100.[000162] System 1200 stores or has access to computer applications (also referred to as software or programs) — i.e. computer readable instructions and data which, when executed by the processing unit 1202, configure system 1200 to receive, process, and output data. Instructions and data can be stored on nontransient machine readable medium accessible to system 1200. For example, instructions and data may be stored on non-transient memory 1210. Instructions and data may be transmitted to / received by system 1200 via a data signal in a transmission channel enabled (for example) by a wired or wireless network connection.[000163] Applications accessible to system 1200 will typically include an operating system application such as Microsoft Windows®, Apple OSX, Apple IOS, Android, Unix, or Linux.[000164] System 1200 also stores or has access to applications which, when executed by the processing unit 1202, configure system 1200 to perform variouscomputer-implemented processing operations described herein. For example, and referring to the environment of Figure. 1 above, mobile device 104 includes a touchpoint application 112 which configures the mobile device 104 to perform the described client system operations. Similarly, touchpoint management server 102 includes a touchpoint service 108 which configures the touchpoint management system 102 to perform the described server system operations.[000165] The flowcharts illustrated in the figures and described above define operations in particular orders to explain various features. In some cases, the operations described and illustrated may be able to be performed in a different order to that shown / described, one or more operations may be combined into a single operation, a single operation may be divided into multiple separate operations, and / or the function(s) achieved by one or more of the described / illustrated operations may be achieved by one or more alternative operations. Still further, the functionality / processing of a given flowchart operation could potentially be performed by different systems or applications.[000166] Variations and modifications may be made to the parts previously described without departing from the spirit or ambit of the disclosure.[000167] The present specification describes various embodiments with reference to numerous specific details that may vary from implementation to implementation. No limitation, element, property, feature, advantage or attribute that is not expressly recited in a claim should be considered as a required or essential feature. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.[000168] In the claims which follow and in the preceding description of the invention, except where the context requires otherwise due to express language or necessary implication, the word “comprise” or variations such as “comprises” or “comprising” is used in an inclusive sense, i.e. to specify the presence of the stated features but not to preclude the presence or addition of further features in various embodiments of the invention.

Claims

CLAIMS1 . A touchpoint device for performing a touchpoint action at a travel location, the touchpoint device comprising: a location finding system configured to determine whether a mobile device is located in a target region in proximity to the touchpoint device; and a processor and computer readable medium storing computer executable instructions, which when executed by the processor cause the processor to: establish a connection with a located mobile device; and launch a journey management application on the located mobile device, the journey management application: interrogating the located mobile device to identify any touchpoint data records previously communicated to the located mobile device; and utilising an identified touchpoint data record to display a user interface on the located mobile device that assists a user of the located mobile device to perform the touchpoint action.

2. A touchpoint device according to claim 1 , wherein the instructions further cause the touchpoint device or the journey management application to communicate an action status message to a journey management server, the action status message indicating a status of the touchpoint action.

3. A touchpoint device according to claim 2, wherein responsive to the action status message indicating successful performance of the touchpoint action, the journey management application utilises a subsequent identified touchpoint data record to display a user interface on the located mobile device that assists the user of the located mobile device to perform a subsequent touchpoint action at another touchpoint device.

4. A touchpoint device according to claim 2, wherein the touchpoint data records are communicated to the located mobile device by a journey management server application executing on the journey management server, the journey management server application communicating the touchpoint data records to the located mobile device responsive to the located mobile device enrolling in a departure control system.

5. A touchpoint device according to claim 4, wherein the journey management server application communicates a set of assigned touchpoint data records to the located mobile device, the assigned touchpoint data records being selected from touchpoint devices installed at the travel location.

6. A touchpoint device according to claim 1 , wherein each touchpoint data record comprises a touchpoint identifier field, a touchpoint geographical location field and a touchpoint status field.

7. A touchpoint device according to claim 3, wherein the journey management application executes a localisation algorithm to determine a geographic location of the located mobile device, the journey management application utilising the determined geographic location to generate and display a user interface that directs the user to the another touchpoint device.

8. A touchpoint device according to claim 7, wherein the journey management application detects one or more radio signals emitted from beacons associated with the another touchpoint device to execute the localisation algorithm.

9. A touchpoint device according to claim 1 , wherein the location finding system comprises a phased array antenna system.

10. An antenna comprising: a plurality of spaced apart antenna elements arranged in a linear configuration, each antenna element having an antenna element signal inlet for receiving a signal that the antenna element is to emit; an antenna inlet for receiving a signal that the antenna is to emit; and a feed network having an origin end communicatively coupled to the antenna inlet and a plurality of terminal ends each communicatively coupled to one of the antenna element signal inlets, the feed network comprising a plurality of conductor lines that are arranged to define signal paths from the antenna inlet to each antenna element signal inlet, each signal path having a defined characteristic.

11. An antenna according to claim 10, wherein the plurality of conductor lines are arranged in a tree structure having a root level comprising conductor lines communicatively coupled to the antenna inlet and at least one branch level comprising conductor lines communicatively coupled to one of the antenna element signal inlets.

12. An antenna according to claim 11 , wherein the branch level conductor lines extend from the root level conductor lines in a T-junction.

13. An antenna according to claim 12, wherein branch level conductor lines that extend from a common T-junction have different lengths.

14. An antenna according to claim 11 , wherein root level conductor lines have a different width to branch level conductor lines.

15. An antenna according to claim 11 , wherein the tree structure comprises a first branch level extending from the root level and a second branch level extending from the first branch level, the second branch level comprising conductor lines communicatively coupled to one of the antenna element signal inlets.

16. An antenna according to claim 15, wherein the first branch level conductor lines extend from the root level conductor lines in a T-junction.

17. An antenna according to claim 16, wherein first branch level conductor lines that extend from a common T-junction have different lengths.

18. An antenna according to claim 10, wherein at least some of the conductor lines incorporate tapering devices to selectively modify a width of the conductor line.

19. A touchpoint device for performing a touchpoint action at a travel location, the touchpoint device comprising: a location finding system configured to determine whether a mobile device is located in a target region in proximity to the touchpoint device; a network interface for establishing an operative network connection with a touchpoint service operating on network infrastructure; and a processor and computer readable medium storing computer executable instructions, which when executed by the processor cause the touchpoint device to: operate the location finding system to locate a mobile device in the target region; and upon locating a mobile device in the target region, communicating a touchpoint action session message to the located mobile device, the touchpoint action session message comprising session instructions to an application executing on the located mobile device to establish a touchpoint action session with the touchpoint service.

20. A touchpoint device according to claim 19, wherein the computer executable instructions further cause the touchpoint device to receive a touchpoint action message from the touchpoint service, the touchpoint action message comprising a touchpoint action session token assigned to the touchpoint action session.21 . A touchpoint device according to claim 20, wherein the touchpoint action message further comprises a travel identifier received by the touchpoint service during the touchpoint session.

22. A touchpoint device according to claim 21 , wherein the travel identifier comprises a scan of a boarding pass.

23. A touchpoint device according to claim 19, wherein the application executing on the located mobile device communicates touchpoint action session data to the touchpoint service during the touchpoint action session.

24. A touchpoint device according to claim 23, wherein the computer executable instructions further cause the touchpoint device to receive a touchpoint control message indicating whether the holder of the mobile device is permitted to perform a touchpoint action, the touchpoint service constructing the touchpoint control message by processing the touchpoint action session data.

25. A touchpoint device according to claim 24, wherein the touchpoint service constructs the touchpoint control message by processing a time series of locations of the mobile device relative to the touchpoint device.

26. A touchpoint device according to claim 25, wherein the touchpoint action session data comprises a time series of signal strength measurements made by the mobile device of location signals received from the touchpoint device, the touchpoint service computing the time series of locations from the time series of signal strength measurements.

27. A touchpoint device according to claim 26, wherein the touchpoint service constructs an anomaly message and communicates the anomaly message to the touchpoint device in the event that the time series of locations indicates an anomalous behaviour of the mobile device.

28. A touchpoint device according to claim 23, wherein the touchpoint action session data comprises personalisation data pertaining to the holder of the mobile device, the computer executable instructions further causing the touchpoint device to receive a personalisation message based on the personalisation data, the touchpoint device utilising the personalisation message to assist the holder of the mobile device to perform a touchpoint action on the touchpoint device.

29. A computer readable medium storing computer executable instructions which when executed by a processor of a mobile device cause the mobile device to: receive a location signal from a touchpoint device having a location finding system; and establish a touchpoint action session with a touchpoint service operating on network infrastructure.

30. A medium according to claim 29, wherein the computer executable instructions further cause the mobile device to communicate a touchpoint action message to the touchpoint service, the touchpoint action message comprising a touchpoint action session token assigned to the touchpoint action session.31 . A medium according to claim 30, wherein the touchpoint action message further comprises a travel identifier.

32. A medium according to claim 31 , wherein the travel identifier comprises a scan of a boarding pass.

33. A medium according to claim 29, wherein the computer executable instructions further cause the mobile device to communicate touchpoint action session data to the touchpoint service during the touchpoint action session.

34. A medium according to claim 33, wherein the touchpoint action session data comprises a time series of signal strength measurements made by the mobile device of location signals received from the touchpoint device.

35. A medium according to claim 33, wherein the touchpoint action session data comprises personalisation data pertaining to the holder of the mobile device.

Images