COMPUTER-IMPLEMENTED METHOD AND SYSTEM FOR SHARING INFORMATION BETWEEN PASSENGERS AND AIR TRAFFIC MANAGEMENT STAKEHOLDERS

Abstract

A computer-implemented method and a system for providing passenger information performing the tasks of sending, from a passenger electronic device (110), personal data, device geolocation and device time-stamp information; obtaining the passenger itinerary and confirming passenger identity, by a managing unit (206), based upon a match between the personal data, passenger electronic device geolocation and time-stamp; information contained in the obtained passenger itinerary; accessing to updated air traffic information relevant to the passenger upon confirming the passenger identity and sending, by the managing unit (206), a passenger report comprising flight status information for display on the passenger electronic device (110).

Claims

1. A system for providing passenger information to a passenger, the system comprising: a passenger electronic device (110) configured to send at least personal data, device geolocation of the passenger electronic device, and device time-stamp information; a managing unit (206) configured to obtain a passenger itinerary and to confirm a passenger identity based upon a match between the personal data, the device geolocation, and the device time-stamp information, and information contained in the passenger itinerary; the managing unit (206) further configured to access updated air traffic information relevant to the passenger upon confirming the passenger identity and to send a passenger report comprising flight status information for display on the passenger electronic device (110).

2. The system of claim 1, wherein the passenger report is generated by the managing unit (206) by accessing a System Wide Information Management (SWIM) infrastructure.

3. The system of claim 1, wherein the managing unit (206) is further configured to send an automatic notification of events relevant to the passenger based upon a recent geolocation of the passenger, a present geolocation of the passenger, and an inference of a future geolocation of the passenger.

4. The system of claim 1, wherein the passenger report sent to the passenger further comprises at least one of the following information: passenger baggage weight, passenger baggage location, a passengers' position at airport, an electronic last call, and a booked connecting flight.

5. The system of claim 1, wherein the managing unit (206) is further configured to send an input request to the passenger electronic device for updating data of SWIM infrastructure or for reporting an emergency.

6. The system of claim 1, wherein the passenger electronic device (110) is further configured to receive an electronic airline ticket and to retrieve passenger identification and passenger itinerary therefrom.

7. The system of claim 1, wherein the passenger electronic device (110) is selected from the group consisting of: a home computer, an office computer, a laptop computer, a tablet computer, a cell phone, a smart watch, and an in-flight entertainment unit.

8. A computer-implemented method for providing passenger information to a passenger, the method comprising: sending, to a passenger electronic device (110), at least personal data, a device geolocation of the passenger electronic device, and device time-stamp information; obtaining a passenger itinerary and confirming passenger identity, by a managing unit (206), based upon a match between the personal data, the device geolocation and the device time-stamp information, and information contained in the passenger itinerary; accessing updated air traffic information relevant to the passenger upon confirming the passenger identity; and sending, by the managing unit (206), a passenger report comprising flight status information for display on the passenger electronic device (110).

9. The computer-implemented method of claim 8, wherein the report is generated by the managing unit (206) by accessing a System Wide Information Management (SWIM) infrastructure.

10. The computer-implemented method of claim 8, wherein the managing unit (206) is further configured to send an automatic notification of events relevant to the passenger based upon a recent geolocation of the passenger, a present geolocation of the passenger, and an inference of a future geolocation of the passenger.

11. The computer-implemented method of claim 8, wherein the report sent to the passenger further comprises at least one of the following information: passenger baggage weight, passenger baggage location, a passengers' position at an airport, an electronic last call, and a booked connecting flight.

12. The computer-implemented method of claim 8, wherein the managing unit (206) is further configured to send an input request to the passenger electronic device for updating data of a SWIM infrastructure or for reporting an emergency.

13. The computer-implemented method of claim 8 wherein the passenger electronic device (110) is further configured to receive an electronic airline ticket and to retrieve passenger identification and passenger itinerary therefrom.

14. The computer-implemented method of claim 8, wherein the device geolocation is determined by at least one of the following: a global positioning system circuitry in the passenger electronic device, an IP address of the passenger electronic device, and by triangulation.

15. A computer program product for providing passenger information to a passenger, the computer program product comprising computer code instructions that, when executed by a processor, causes the processor to perform a computer-implemented method, the computer code instructions comprising: computer code instructions for sending, to a passenger electronic device (110), at least personal data, a device geolocation of the passenger electronic device, and device time-stamp information; computer code instructions for obtaining a passenger itinerary and confirming passenger identity, by a managing unit (206), based upon a match between the personal data, the device geolocation, and the device time-stamp information, and information contained in the passenger itinerary; computer code instructions for accessing updated air traffic information relevant to the passenger upon confirming the passenger identity; and computer code instructions for sending, by the managing unit (206), a passenger report comprising flight status information for display on the passenger electronic device (110).

16. The computer program product of claim 15, wherein the computer code instructions are configured such that the report is generated by the managing unit (206) by accessing a System Wide Information Management (SWIM) infrastructure.

17. The computer program product of claim 15 wherein the computer code instructions are configured such that the managing unit (206) is further configured to send an automatic notification of events relevant to the passenger based upon a recent geolocation of the passenger, a present geolocation of the passenger, and an inference of a future geolocation of the passenger.

18. The computer program product of claim 15, wherein the computer code instructions are configured such that the report sent to the passenger further comprises at least one of the following information: passenger baggage weight, passenger baggage location, a passengers' position at an airport, an electronic last call, and a booked connecting flight.

19. The computer program product of claim 15, wherein the computer code instructions are configured such that the managing unit (206) is further configured to send an input request to the passenger electronic device for updating data of a SWIM infrastructure or for reporting an emergency.

20. The computer program product of claim 15 wherein the computer code instructions are configured such that the passenger electronic device (110) is further configured to receive an electronic airline ticket and to retrieve passenger identification and passenger itinerary therefrom.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] A series of drawings which aid in better understanding the disclosure and which are presented as non-limiting examples and are very briefly described below.

[0018] FIG. 1 schematically shows passengers' connectivity to SWIM infrastructure.

[0019] FIG. 2 schematically shows Passenger Management System (PMS) design.

[0020] FIG. 3 shows a block diagram.

DETAILED DESCRIPTION

[0021] By enabling passengers' access to SWIM, a bidirectional communication is established. Valuable information may be exchanged between passengers and SWIM stakeholders. SWIM information may be enriched from passengers' information and passengers may benefit from the access to the SWIM information.

[0022] Although the list of possible feature is almost unlimited, next list gathers a preliminary set of main features that may be implemented in the Passengers Access to SWIM (PAtS): [0023] Passenger no-show information sharing. [0024] Passenger baggage and weight information can be shared before check-in. [0025] Passenger position in the airport, useful for instance in case of gate change. [0026] Electronic Individual Last call.

[0027] Exploitation of passengers' GPS geolocation enabled by mobile devices. [0028] Real time updated information about flight connections. [0029] Optimization of flight connections based on real time flight status. [0030] Overall system optimization due to passenger geolocation monitoring. [0031] Security. Hijacking report by passengers onboard.

[0032] FIG. 1 shows how the passengers get access to the SWIM network by using different protocols through the Passenger Management System 132 (PMS). [0033] Home PAtS 102: The passengers' connection to the IP network can be obtained through a wired/wireless access point at home or through a LTE network 122 access point. [0034] Airport PAtS 104: Passengers at the airport. The connection to the IP network can be obtained through the Airport wireless network 112 or through a LTE network 122 access point. [0035] Gate PAtS 106: Passengers at the boarding gate or onboard (airplane at the platform). The connection to the IP network can be obtained through a LTE network 122 access point or through a gatelink 128, that is a wireless communication link for on-ground aircraft wireless communication (e.g. according to standard ARINC 822). [0036] Airborne PAtS 108: Passengers are onboard and the connection to the IP network can be obtained through the cabin wireless Local Area Network 118 by means of the Inflight Entertainment System (IFE) 119 or the passengers' electronic device 110.

[0037] The passenger electronic device 110 may be a desktop computer, laptop computer, tablet, cell phone, in-flight entertainment unit or other network enabled device.

[0038] In order to offer a proper protection for SWIM sensitive information, operations and SWIM stakeholders, the passenger's connection to SWIM needs to be controlled and restricted. To this end, a Passenger Management System (PMS) 132 provides an interface that defines and establishes connections between the passenger and the SWIM infrastructure 134, assuring security, permission grant management and boundary protection by decoupling the SWIM network from the IP network used by the passengers.

[0039] The PMS 132 has the capability of connecting a passenger's electronic device 110 with multiple SWIM infrastructures as depicted in FIG. 1. Among others, infrastructures such as Meteorological Service Providers 136, Military Operations Center 138, Air Traffic Control (ATC) 140, Airline Operation Center 142, Airport & Handling Systems 144 and Flow Management System 146.

[0040] On the other hand, the PMS 132 publishes passengers' data which may be exploited by dedicated SWIM agents. The PMS 132 may provide such information to the SWIM infrastructure.

[0041] Establishing a bidirectional information flow provides an unprecedented capability which enables multiple out-of-the-box functionalities to any SWIM stakeholder.

[0042] FIG. 2 depicts a proposed design of the PMS 132. The main defined interfaces are:

[0043] Passenger Security Layer 202: Passenger secured (signed and encrypted) information with encapsulated service call request/reply.

[0044] Service Layer 204: Particular request/reply service, including passenger's information or SWIM information tailored to the passenger's requirements. Any possible service (Service 1, 2, . . . , S) is required to match the software implementation of system features. Possible services are shown below: [0045] Passenger no-show information service. [0046] Passenger baggage and weight information service. [0047] Passenger position at airport sharing service. [0048] Electronic Last call service. [0049] Position calculated using GPS enabled mobile device management service. [0050] Flight connections service. [0051] Flight status service. [0052] Managing Unit 206: Main algorithmic used for managing the passenger requests or the SWIM queries, by capturing, storing and processing the data available through the bidirectional flow of information. The Managing Unit 206 merges and fuses information from different SWIM implementations to provide the passenger with the expected information. The accessibility to the information is transparent to the end user, although internally the PMS 132 requires managing information from different sources. [0053] SWIM Security Layer 212: Implements encryption and signing algorithms needed to secure requests for a particular SWIM implementation. [0054] SWIM Interface 210: access implementation that includes communications, protocols and applications needed to get access to a particular SWIM service on a particular SWIM implementation.

[0055] The implementation of the PMS 132 is compliance with all particular implementations of the SWIM paradigm, especially the US SWIM 208, European SWIM and Australian SWIM.

[0056] In connection with the secure access to SWIM, the present embodiment may take advantage of the fact that most airlines offer electronic ticketing. The passenger having an electronic flight ticket may provide some information using an electronic device to easily get online check-in and receive his electronic boarding pass to gain entrance to the aircraft at the gate.

[0057] The electronic flight ticket may facilitate the validation or authentication of passengers when accessing to SWIM. Not only passenger identity is included in the electronic flight ticket, some other important personal information can be extracted therefrom as well. As a minimum, the electronic flight ticket comprises the passenger identity, the flight identification, and the date and scheduled time of departure. In particular, the passenger's itinerary is important to offer valuable information as indicated above.

[0058] Once the passenger is correctly identified, information can be offered that is specific to that passenger's location, itinerary.

[0059] As a way of further examples, the passenger using his electronic device may request change of seat, change of flight, or even change of airline. In response, the passenger may receive optional recommendations for reservations. Furthermore, in response to changes in their reservations additional charges or refunds against their credit card may be received. Advantageously, the passenger may make changes to rental car reservations, rail reservations, hotel accommodations, etc.

[0060] FIG. 3 depicts for a better understanding a simplified block diagram of main components showing their connections, relationships and functions that may be implemented in the systems and methods described in this document. A passenger electronic device 110 connects to the Managing Unit 206 included in PMS 132 and provides with personal data, device geolocation and device time-stamp information. The Managing Unit 206 uses these as credentials for authenticating the passenger prior to access to SWIM 208 to retrieve updated air traffic information relevant to the passenger, in particular regarding itinerary to produce a report to be displayed on the passenger electronic device 110. Likewise, the passenger may provide or share useful information to be available to conventional SWIM stakeholders.

[0061] These and other features, functions, and advantages that have been discussed can be achieved independently in various embodiments or may be combined in yet other embodiments.